The executive summary here is that at the moment additional bootloader data like the extlinux modules in /boot/extlinux and the grub2 splash screens in /boot/grub2/themes don't fit into the OSTree model. I don't have a way to update that data in an atomic/safe fashion.
For more background:
Now what I'm thinking is that changing the Fedora extlinux package is high risk, and also wouldn't solve things like the grub2 splash screens.
The simplest option is to declare that this additional data in /boot is only laid down exactly once, by the installer. Basically for OSTreePayload, what Anaconda would do is simply copy all data in the tree's /boot into the target /boot. OSTree itself would not do this on upgrades.
If we choose this path, it would still be nice to offer a mechanism (perhaps even a standardized one that detected the active bootloader) and updated it.
On the other hand, if we killed grub2 splash screens, then extlinux would likely be the odd man out here. Any data points for how the other bootloaders work?
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
