On Wed, Oct 15, 2025 at 3:25 PM Chris Murphy <[email protected]> wrote: > > > > On Wed, Oct 15, 2025, at 6:15 AM, Stephen Smoogen wrote: > > > Is there a way that there could be a new tool in the systemd family which > keeps multiple boot partitions in sync for booting purposes? > > > I thought it was going to be part of https://github.com/coreos/bootupd but > I'm not sure of the status. > > In an idea universe there'd be an "origin" copy of /boot and /efi, and the > sync tool would sync from "origin" rather than treating one of the satellite > drives as a sort of primary or canonical copy. > > It would be super cool to have the option to push a NEWEFI directory with the > updated binaries, and use an EFI BootNext variable. If the next boot fails, > the update didn't work, and the reboot automatically reverts to the EFI > directory. If the boot works, the the tool could atomically replace EFI/ with > NEWEFI/ to complete the update.
This is what I was hoping for too. Or at least using bootupd to get to the same level that SUSE does with perl-Bootloader and shim-install where the install to the ESP and OS boot space are handled as transaction triggers. The larger hope is that bootupd could also unify and simplify the user experience for managing boot code updates for weird platforms like ARM and RISC-V where the OS is (sadly) responsible for board firmware and DeviceTrees (even though I wish it weren't). -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
