Re: Why isn't init PID 1?

From: H. Peter Anvin (hpa@zytor.com)
Date: Wed Jan 31 2001 - 18:33:09 EST

Next message: Stephen C. Tweedie: "Re: [Kiobuf-io-devel] RFC: Kernel mechanism: Compound event wait /notify + callback chains"
Previous message: Bernd Eckenfels: "Re: reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel)"
In reply to: Igmar Palsenberg: "Re: Why isn't init PID 1?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Followup to: <Pine.LNX.4.21.0102010057470.11152-100000@server.serve.me.nl>
By author: Igmar Palsenberg <maillist@chello.nl>
In newsgroup: linux.dev.kernel
>
> Yes. First program to run get PID 1.
>
> Solution : fork() in init and load the modules in the child.
>

Or finish your script with "exec init".

-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Stephen C. Tweedie: "Re: [Kiobuf-io-devel] RFC: Kernel mechanism: Compound event wait /notify + callback chains"
Previous message: Bernd Eckenfels: "Re: reiserfs min size (was: [2.4.1] mkreiserfs on loopdevice freezes kernel)"
In reply to: Igmar Palsenberg: "Re: Why isn't init PID 1?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jan 31 2001 - 21:00:41 EST