Victor Lowther <[email protected]> writes: > On Wed, 2009-07-15 at 18:46 +0100, Jon Fairbairn wrote: >> Hi. I have a laptop with a slightly peculiar setup that mkinitrd >> fails. See <https://bugzilla.redhat.com/show_bug.cgi?id=506356>
>> ./dracut -l --drivers " yenta_socket rsrc_nonstatic usb_storage ata_generic >> pata_acpi" ... > > That is a little bit of an odd setup. Granted. > Are there any initramfs packages that do the Right Thing without any > special tweaking for your config? I don't know. Up until now I've not been interested in initramfs in the abstract, so I've only ever used the mkinitrd that comes with redhat/fedora on this setup. As I say in the bug report, it worked in fedora 9, and it only requires a small change of order of the commands in the initrd's init to make it work on fedora 11 -- it includes the right modules. Whether it working on fedora 9 was good management or good luck, I can't say. I'm not sure I understand the import of the question. Given that dracut will produce a working initrd if told what modules to include, isn't it a matter of picking through /sys and such to find what modules are involved in driving the devices that constitute /dev/root and then making sure they are loaded in the initrd? -- Jón Fairbairn [email protected] -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
