On Fri, 19 Sep 2003, Peter M�ller Neergaard wrote: > Of course this does not preclude the modules from being available at > boot time. When the modules resides in /lib/modules/... they cannot be > loaded before I have mounted / and that cannot happen before the files > system has been checked. Is that what the initrd images in /boot are > for?
Yes, that is precisely what initrd images are for; they contain whichever module(s) will be required to mount the root filesystem. This is also why you can't just use an initrd from a different kernel version, as modules must be compiled for that exact kernel to be able to be loaded at all. > If so this explains my trouble. Somehow the process of upgrading to > kernel 2.4.21-0.25mdk went haywire. I ended up with a useless initrd > image and decided that it was easiest just to ignore it since it boots > fine without. Not to sound contentious, but the behavior you describe is hardly the sort of thing that I would describe as booting "fine" ... :-/ -- Bill Mullen [EMAIL PROTECTED] MA, USA RLU #270075 MDK 8.1 & 9.0 "Listen, here's the thing. If you can't spot the sucker in your first half hour at the table, then you *are* the sucker." - Mike McDermott
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
