> It is perfectly possible to say "m" to all types of disks and all > filesystems. But then your kernel will not be able to access the > disk. Your boot disk must be built into your kernel.
i thought initrd solved that problem by allowing modules to be loaded into a ram disk before the disk was accessible (because grub/lilo directly support reading the initrd fiel from the disk). am i wrong? in which case which modules have to be built in for initrd to work? i had a similar problem when i first moved to 2.4 kernels and it turned out to be a not recent enough modutils. all i did was take the .config from kernel-image-2.4.14 copy it into the new src tree of 2.4.16 and run "make oldconfig". i *should* have everything i need, and i've confirmed via diff that it doesn't look significantly different from my old 2.4.14 config file. adam.
