On Sun, Sep 09, 2007 at 01:40:11PM +0200, Davide Mancusi wrote: > pinniped ha scritto: >> That is (somewhat) correct; the scripts which create the initrd image >> will normally (in the default install) put all framebuffer, acpi, >> filesystem, and hard disk drivers into the image. Have a look in >> /etc/initramfs-tools/initramfs.conf to get some idea what goes on. > > I did, but the only way I found to control modules included in the initrd > is the MODULES option in initramfs.conf (presently set to MODULES=most). I > can't see any way to exclude "floppy" (I could specify a list, of course, > but how do I know what modules are included by "most"?). you can look in the initrd itself, google for instructions on unpacking it, or wait for madduck (and others) to notice this thread and pipe up about it. You can mess around with initrd all you want without serious risk. Just rename the current working initrd to something sensible; mess around with the configs and build a new one and try it on a reboot. If it fails, reboot again and select the known working one by editing your grub parameters and try again. You certainly won't go very far wrong by selecting MODULES=dep or whatever it is. That will then only insert the modules that are required to boot the system based on the current hardware (not sure what foo it uses to do this) requirements. But it will certainly get you a smaller initrd and may help with certain persistently loaded modules (like floppy). > > I wonder what you get in initramfs.conf if you do not select to load > "floppy" when installing. Does it get loaded anyway? > I suspect that these are completely seperate processes. A
Attachment:
signature.asc
Description: Digital signature