> In article <cistron.Pine.LNX.3.95.981113113553.338A-100000@chaos.analogic.com>,
> Richard B. Johnson <root@chaos.analogic.com> wrote:
> >> On Thu, Nov 12, 1998 at 08:39:53PM +0100, Miquel van Smoorenburg wrote:
> >> > Alas not. If you pass init=/what/ever, the kernel starts an
> >> > internal pseudo init and starts the /what/ever as a child (usually
> >> > it has PID 8 or so).
> >
> >Alas yes. I wish you would try this stuff before you argue.
>
> It depends on whether you are talking about 2.0.x or 2.1.x
>
> Mike.
> --
With init=/bin/bash, you can mount proc over the r/o file-system
using the '-n' option. You will see that init is PID 1. The kernel
pseudo processes have higher PIDs.
When you `exec`, the current task is overwritten with the new code.
No fork occurs. The PID remains the same. Try it, you'll like it.
This allows you to perform fs maintenance with bash as init, then
exec /sbin/init. The SYSV startup occurs with the correct init PID of 1
Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.1.127 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/