Re: final(?) no-daemon kmod diffs for linux-2.1.96

H. Peter Anvin (hpa@transmeta.com)
16 Apr 1998 05:13:42 GMT


Followup to: <199804151932.MAA00368@adam.yggdrasil.com>
By author: "Adam J. Richter" <adam@yggdrasil.com>
In newsgroup: linux.dev.kernel
>
> While the changes to the create_thread call in kernel/kmod.c
> that appeared in 2.1.96 cleverly solve the problem of chrooting after
> the ramdisk terminates, they do not solve the problem for ramdisks
> that do not exit, but rather do "exec chroot /mnt /sbin/init".
>

That wouldn't make init pid 1, though.

I do agree that the right thing to do is to have initrd mount the new
root filesystem, and communicate it to the kernel somehow (for example
via /proc/sys), but the kernel needs to be aware of the transition
event so it can make init pid 1.

-hpa

-- 
    PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD  1E DF FE 69 EE 35 BD 74
    See http://www.zytor.com/~hpa/ for web page and full PGP public key
        I am Bahá'í -- ask me about it or see http://www.bahai.org/
   "To love another person is to see the face of God." -- Les Misérables

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu