[lkml]   [1998]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: final(?) no-daemon kmod diffs for linux-2.1.96
Followup to:  <>
By author: "Adam J. Richter" <>
In newsgroup:
> 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.

PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See for web page and full PGP public key
I am Bahá'í -- ask me about it or see
"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

 \ /
  Last update: 2005-03-22 13:42    [W:0.022 / U:0.508 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site