No subject

>                 Unrecognized actions (like initdefault) will cause init to emit an
>                      error message, and then go along with its business.  All actions are
>                      run in the reverse order from how they appear in /etc/inittab.
> 
>              <process>:

That would imply that, for the following config file:

> ::sysinit:/bin/mount -t proc /proc /proc
> ::sysinit:/bin/mount -t ext2 -o remount,rw /dev/ram0 /

... the /dev/ram0 is remounted before /proc is mounted.

This is not true, as proven by this:

> ::restart:/sbin/init
> ::shutdown:/bin/umount -a -r
> ::shutdown:/sbin/swapoff -a
> ::ctrlaltdel:/sbin/reboot
> tty1::askfirst:/bin/sh
> ::respawn:/sbin/syslogd -n
> ::sysinit:/bin/busybox echo 4
> ::sysinit:/bin/dhcpcd -d -B -D -L /var/lib/dhcp -c /etc/dhcp/script
> ::sysinit:/bin/busybox echo 3
> ::sysinit:/bin/ash -c 'for i in $(/bin/grep eth /proc/net/dev | cut -d : -f 1); do ifconfig $i up; done'
> ::sysinit:/bin/busybox echo 2
> ::sysinit:/bin/mount -t ext2 -o remount,rw /dev/ram0 /
> ::sysinit:/bin/busybox echo 1
> ::sysinit:/bin/mount -t proc /proc /proc
> ::sysinit:/bin/busybox echo 0

The first thing shown on the screen is "4", not "0" as we'd expect by
the above docs.

What order is the correct (ie intended) way?

Allan