Messages in this thread | | | Date | Wed, 16 Jan 2002 20:29:58 +0100 | From | Andreas Ferber <> | Subject | Re: Query about initramfs and modules |
| |
On Tue, Jan 15, 2002 at 04:01:17PM -0800, Greg KH wrote: > > This also solves the "coldplug" problem, where you need to load > pci/usb/foobus drivers _after_ init has started. To do this you need to > rely on scanning the busses from userspace and loading the needed > drivers. Why reimplement this scanning logic, as the kernel already did > all of this (and usually did a much better job at it) during the boot > process before init started.
Hmm. AFAICS this also implies that one would have to put /all/ drivers for /any/ hardware possibly plugged in at boot time on the initramfs. Or will /sbin/hotplug provide the ability to just put requests it can't resolve with the modules on the initramfs into some sort of queue file, which is read by /sbin/coldplug (or whatever) later on in the boot process to load drivers for those from the real root fs?
> And this allows lots of horrible "boot over NFS" and other network > code/hacks in the kernel to be moved out of kernel space, and into > userspace, where it really belongs.
Having to put all drivers for all PCI/USB/whatever stuff on the initramfs will likely be a problem (regarding disk space) for people who need to boot the kernel from a floppy disk without having to change disks during boot (think of nfsroot without etherboot).
Andreas -- Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG --------------------------------------------------------- +49 521 1365800 - af@devcon.net - www.devcon.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |