systemd-boot

systemd-boot
Name	systemd-boot
Developer	systemd project
Released	2015
Operating system	Linux
License	LGPL
Website	systemd

systemd-boot systemd-boot is a lightweight UEFI boot manager that is part of the systemd project. It provides a minimalist EFI stub loader interface for launching Linux kernels and operating system images, designed for integration with systemd-based distributions such as Arch Linux, Fedora, Debian, and Ubuntu. systemd-boot focuses on straightforward configuration, fast boot times, and compatibility with UEFI features including Secure Boot and EFI variables.

Overview

systemd-boot acts as an EFI executable that the UEFI firmware invokes to enumerate and launch boot entries stored on the EFI System Partition (ESP). It reads simple configuration files to present a menu and to load kernel images, initramfs files, or EFI applications such as rEFInd, GRUB, or Windows Boot Manager. Integrations exist with distribution installers from Red Hat, SUSE, openSUSE, Gentoo, and derivatives maintained by projects like Canonical and Debian Project. The component stems from broader Freedesktop.org and GitHub-hosted collaboration and aligns with projects such as systemd-timesyncd, systemd-resolved, and udev.

Features and design

systemd-boot emphasizes simplicity and conformity to UEFI standards including support for EFI variables, the EFI runtime services defined by the Unified Extensible Firmware Interface Forum, and kernel command-line handling consistent with Linux kernel conventions. It features fast initialization comparable to minimalist launchers used in CoreOS and Alpine Linux, and interoperates with firmware implementations from vendors like Intel, AMD, Dell, HP, and Lenovo. The design favors declarative entry files similar in spirit to configuration approaches from systemd-journald and systemd-networkd, enabling predictable behavior favored by distributions such as NixOS and Guix System.

Installation and configuration

Installing systemd-boot typically involves copying the EFI binary onto the ESP and creating a loader configuration directory with entries. Distributions often provide utilities or scripts in installer environments like those used by Anaconda (software), Calamares, or Debian-Installer. Administrators edit files under the ESP's loader directory to define titles, kernel paths, and options compatible with kernels from Linux kernel releases and initramfs generated by dracut, initramfs-tools, or mkinitcpio. Tools such as efibootmgr interoperate for boot order management alongside vendor UEFI setup utilities provided by American Megatrends, Insyde Software, and Phoenix Technologies.

Boot entry management

Boot entries for systemd-boot are plain-text files specifying paths and options, making them manageable by configuration management systems like Ansible, Puppet, Chef, and SaltStack. Entries can reference kernels from distributions like Arch Linux, Fedora, openSUSE Tumbleweed, Debian Stable, or custom kernels built from LINUX From Scratch sources. Automatic entry generation can be performed by distribution-provided scripts, initramfs hooks, or tools like os-prober that detect other operating systems including Microsoft Windows, FreeBSD, or NetBSD. The approach parallels declarative boot entry schemes used by projects such as coreos-boot and simplifies dual-boot setups documented in community resources maintained by Arch Wiki and Debian Wiki.

Security and secure boot

systemd-boot supports Secure Boot by loading signed EFI binaries and verifying signatures against platform keys. It can work with signing tools and frameworks used by MokManager, shim (software), sbsigntool, and the x509 infrastructure employed by many distributions. Secure Boot workflows in environments like Red Hat Enterprise Linux, SUSE Linux Enterprise, and Ubuntu Advantage leverage key enrollment, shim-based boot chains, and signed kernels to maintain chain-of-trust from firmware to userland. systemd-boot's reliance on UEFI runtime services aligns it with platform attestations performed by Trusted Platform Module implementations and vendor key management approaches from Microsoft Corporation's firmware key program.

Comparison with other boot loaders

Compared to legacy boot loaders like GRUB 2, LILO, and multiboot managers such as rEFInd, systemd-boot offers a narrower, EFI-centric feature set prioritizing simplicity and integration with systemd-oriented distributions. GRUB provides more scripting, filesystem drivers, and rescue features used by Red Hat, Debian, and GNU-based systems, while rEFInd supplies a graphical and discovery-focused interface favored by macOS dual-booters and hardware dealers such as Apple Inc.. systemd-boot's minimalism parallels the philosophies of projects like systemd-sysv-generator and complements the lightweight init approaches seen in BusyBox-based embedded systems and Yocto Project variants.

Development and history

systemd-boot originated within the systemd project, which itself evolved from work by developers associated with freedesktop.org, hosted development on GitHub, and coordinated contributions from individuals connected to organizations like Red Hat, Intel, and SUSE. Its design choices reflect trends in the broader Linux ecosystem toward UEFI adoption and streamlined boot paths influenced by initiatives such as UEFI Secure Boot adoption and container-focused platforms like Docker and Kubernetes. Over time, community contributions from distributions including Arch Linux, Fedora Project, Debian Project, and vendors like Canonical have shaped its integration, packaging, and documentation across installer systems and maintenance tools.

Category:Boot loaders