would the concaternating approach allow the move mount when switching to the rootfs ? our readonly filesystems will soon be img files under /boot as well (as i understood one of the short term targets is currently to achieve a 2 partition setup) so i dont see an issue with loop mounting just another img if that helps droppping the duplication of (compressed) 10-15MB of modules inside the initrd and allows us to maintain the modules completely separated from the rootfs snap.
i also understand that we will soon start to use squashfs everywhere for snap content, so a squashfs img feels kind of logical for the modules as well. i don't understand "In any case, the filesystem containing the modules for the initramfs needs to be loaded by the bootloader, not by the kernel." is there a technical issue i am missing or do you refer to "best habit" with this ? if i load the modules.img from inside the running initramfs i'm far past the bootloader, the system-boot partition is currently vfat everywhere on snappy and vfat is compiled into all our kernels, as is loop device and ext3/4 support. so this would technically be enough to loop mount a modules.img from the initrd. -- 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
