On Fri, Oct 25, 2002 at 11:11:00AM +0300, Ed V. Bartosh wrote: > > Hi, Ravi! > > /Thu, 24 Oct 2002 22:12:55 -0700 (PDT)/ you wrote: > > R> The shell that goes on initrd is nash (this is on RedHat systems, > R> I don't know about others). modprobe is a symblic link to nash. > R> The man page of nash states that if it is invoked as 'modprobe' it > R> will just return success. So this can't be your problem. Not sure > R> what else can cause the message. > > System, which I use is not RedHat and modprobe is a symlink to the > insmod, as usually. I don't understand, isn't it not needed for anybody to > load modules automatically under initrd ? Isn't is so rarely task ?! I > posted my message 2 days ago and have only one (your) answer ! > > I looked into kmod sources and it seems that it's impossible to load > modules through kmod under initrd because of switching fs context to > init fs context before exec modprobe. Is it right ? If no how it is > possible to do it ? I thought initrd was primarily ment to load modules before root is mounted. So both modprobe and modules needed at boot time must be present there... (!) AFAIK, true init is execed after pivot_root... so it's fs context should not be the initrd. In fact, after pivot_root and exec init, nothing at all should refer to initrd and it should be possible to unmount it. Having non-functional modprobe seems to me like quite insane idea. To make a seamless change when pivot_rooting you could use absolute symlinks to /sbin/modprobe and /lib/modules... ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz> -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
