On Tue, Oct 18, 2005 at 03:38:55PM +0200, Martin Wilck wrote: > Rusty Russell wrote: > > >Martin Wilck <[EMAIL PROTECTED]> wrote: > > > >>0. the module loading tool runs during boot with PID 1. > > > >I do not understand how this can happen. request_module() cannot occur > >until usermodehelper_init() is called. This is only done once the init > >thread is spawned, which should take pid 1. > > The process I am talking about was running in init's context. It _was_ > the initrd's init process, actually. > > >Also, reparenting should happen to the process in the kernel which is > >"child_reaper", even if another process were to have PID 1... > > I saw the phenomenon I described happen, at least withn vanilla kernel > 2.6.12-rc5 on Redhat EL3.0. > > Here are two references; > > http://lkml.org/lkml/2005/6/7/93 > http://www.uwsg.indiana.edu/hypermail/linux/kernel/0506.3/0354.html
So, can someone remind me what is calling modprobe? The seems certain to be there. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
