On Tue, Jul 14, 2020, at 3:44 AM, Lennart Poettering wrote: > If however they share the same kernel/boot menu item between multiple > versions of the OS tree, then I'd always embedd which version to boot > in the fs itself by default, Yep, that's how it works today - ostree only touches the BLS configs if it needs to, which is: - If you are changing the kernel/initramfs or kernel arguments - If you are changing the number of "deployments" > I am sorry, what? rpm-ostree has a grub module it needs to operate? No, but ostree does have "bootloader backends" which regenerate bootloader configs from BLS because it needs to support bootloaders that haven't yet implemented it. E.g. we shipped OSTree since RHEL7 and I didn't want to require patching GRUB there, plus u-boot is widely used still (with ostree too) and apparently doesn't support it yet either. The real nightmare was https://github.com/ostreedev/ostree/pull/2044 when we found out the hard way that because we don't update BIOS grub (neither with `yum update` nor `rpm-ostree`) when we tried to hard require BLS some people lost all the ostree bootloader entries... Anyways, we don't use that in FCOS (or FIoT as Peter mentioned). Silverblue-with-Anaconda still does but I think it's just a matter of adding https://github.com/coreos/coreos-assembler/commit/311768c2b14775f4ad18dad05a9e4dfd2e6387b6 to Anaconda. _______________________________________________ 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
