On Thu, Nov 10, 2022, at 6:08 PM, Robbie Harwood wrote:
Ben Cotton <bcotton(a)redhat.com> writes:
> By design, ostree does not manage bootloader updates as they can not
> (yet) happen in a transactional, atomic and safe fashion.
As we've talked about before, it's not possible to make updates
transactional. It involves, per spec and depending on processor
architecture, updating multiple files in different directories,
potentially on different filesystems entirely, one of which is fat32.
EFI/FedoraA
EFI/FedoraB
NVRAM bootorder uses A then B
Update the bootloader in EFI/FedoraB
At any point of failure, only the EFI/FedoraA bootloader path is used. Once everything in
EFI/FedoraB is committed to stable media, set bootnext FedoraB. If the boot fails,
automatic failback to FedoraA. If the boot succeeds, bootupd can change bootorder. B then
A.
?
--
Chris Murphy