:Andreas Jellinghaus writes:
:> > # cd /sbin
:> > # mv init init.real
:> > # echo '#! /bin/sh\nmount -n -t devfs none /dev\n/sbin/init.real' > init
:> > # chmod a+x init
:>
:> did you try this one ?
:
:Er, no, since I never needed that.
:
:> as far as i know, you can't run init as slave process.
:
:Really? Why not?
:
:Anyway, see my announcement of v23 of my patch. I've added a config
:option to mount devfs at boot time.
:
>From past experience, I have learned you cannot cleanly shutdown or reboot
the system if init is not running with a PID of 1. When reading this
message on the list, I recalled seeing something about this in the
sysvinit README.RIGHT.NOW file:
HOW TO NON DESTRUCTIVELY TEST THE NEW INIT:
Install *just* the init binary as /sbin/init.new. Now reboot the system,
and stop your bootloader so you can give arguments on the command line.
. . . . .
boot: linux init=/sbin/init.new
YOU CANNOT SHUTDOWN IN A CLEAN WAY AFTER THIS. Your best bet is to use
the "-n" flag to shutdown. This is because init is not running as
process #1 if you use this method. Anyway, if this works, you can remove
the old init and copy the new init into place.
IF I am incorrect, them I have a very bad memory and the sysvinit docs
need to be fixed :)
-----
Sean M. Kelly
smkelly@zombie.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu