On Sat, Aug 29, 2015 at 08:30:13AM -0000, Oliver Grawert wrote: > to not duplicate the modules we should instead ship a "modules.img" file > in /boot/$bootloader/a|b/ that the initrd can loop mount on startup.
The modules that are shipped in the initramfs are, by definition, those modules that may be required in order for the kernel to access the root filesystem. If the modules are not required in order to access the root filesystem, they should not be included in the initramfs in the first place. If they *are* required in order to access the root filesystem (in one or more configurations), then providing these modules in a separate file on the /boot partition which will be accessed *from the initramfs* is not viable because the /boot partition is on the same device as the root filesystem and will require the same drivers in order to access it. The kernel does support concatenating multiple initramfs into a single image. This may be a workable option for what you're trying to accomplish. In any case, the filesystem containing the modules for the initramfs needs to be loaded by the bootloader, not by the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490115 Title: build a fully generic initrd.img without modules To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1490115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
