On `bootctl install`, two EFI boot entries are registered: one for the primary sd-boot binary and one for a fallback. On `bootctl update`, the existing primary binary is rotated to the fallback path before the new version is installed, so the fallback entry always points to the previous known-good binary. ``` $ sudo bootctl install ... Created EFI boot entry "Linux Boot Manager". Created EFI boot entry "Fallback Linux Boot Manager". $ sudo bootctl update Copied "/boot/EFI/systemd/systemd-bootaa64.efi" to "/boot/EFI/systemd/systemd-boot-fallbackaa64.efi". Copied "/usr/lib/systemd/boot/efi/systemd-bootaa64.efi" to "/boot/EFI/systemd/systemd-bootaa64.efi". $ efibootmgr ... Boot0004* Linux Boot Manager HD(...)/\EFI\systemd\systemd-bootaa64.efi Boot0005* Fallback Linux Boot Manager HD(...)/\EFI\systemd\systemd-boot-fallbackaa64.efi ``` Fixes: #23805
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release
