Re: Kernel 2.2.1 and sysvinit 2.76 possible bug

Richard B. Johnson (root@chaos.analogic.com)
Thu, 25 Feb 1999 15:13:31 -0500 (EST)

I am not copying everybody here because I don't think they know.
I am sure Alan et all are quite aware that init, as the "father
of all other processes" has to have a PID of 1 to maintain SYS-V
compatibility. This means that whatever happens, init must not die.

If you have an init that dies, it is broken. It is either miscompiled
or coded incorrectly.

Init also has to have a signal handler to get the return status
of children created by defective user programs so that, regardless
of how may broken programs are executed, you don't have a bunch
of zombies cluttering up process-slots.

Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.1 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
Wisdom : It's not a Y2K problem. It's a Y2Day problem.

-
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/