On Tue, Jan 21, 2020 at 11:25:29AM +0100, Hans de Goede wrote: > For the size problem one approach which I think is worthwhile at least > for the x86/workstation case is making one initrd with the most common > stuff in there (say i915,nouveau and amd GPU drivers + NVME and AHCI > disk support, maybe some eMMC support) and another which contains > "everything" and then rework the dracut host-only code so that we can > leverage it to figure out which variant we want. Yeah, the important thing is that we have known values - there's no real problem with there being a large number of known values, so shipping multiple images (potentially to be combined if necessary) is entirely reasonable from that perspective. > So b it is, I actually suggested b. on a discussion about how to set > the keyboard map for the initrd (for full disk encryption) which currently > is a problem for rpm-ostree / SilverBlue which uses pre-generated > initrds with no custom config in there. Ok. I'll look into adding support to grub for reading some files and assembling them into an image. My rough idea here would be something like: configinitrd file1 file2 file3 initrd initramfs1.img initramfs2.img CONFIG where the first command generates the image and the second command causes it to be placed at the end of the final cpio blob? -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
