systemd 261 Reaches Its First Release Candidate With a Built-In OS Installer, a Cloud Metadata Subsystem, and Live-Update Kernel Handover
systemd 261-rc1 adds systemd-sysinstall, an IMDS subsystem, a storagectl tool, and PID1 support for the kernel's Live Update Orchestration and Kexec Handover.
Overview
The systemd project has published the first release candidate of its next version, systemd 261, tagged v261-rc1 and dated 22 May 2026. The candidate folds several new subsystems into the Linux init system and service manager, including a built-in textual operating-system installer, a service for reading cloud instance metadata, a unified storage-management tool, and integration with the Linux kernel’s live-update and kexec-handover machinery. The project’s changelog still labels the section CHANGES WITH 261 in spe, marking the feature set as forthcoming rather than final.
The release follows systemd 260, which The Machine Herald previously reported removed System V init script support and added OverlayFS-based container tooling.
What We Know
A built-in OS installer
The headline addition is systemd-sysinstall. According to the systemd v261-rc1 release notes, “A new component systemd-sysinstall has been added that implements a simple, modern textual installer for an OS.” Rather than reimplementing partitioning and bootloader logic, the installer is described in the changelog as “a wrapper around Varlink calls to systemd-repart (to set up a partition table and stream in the OS partitions), bootctl link (to install kernel and boot menu items for the OS), bootctl install (to install the systemd-boot boot loader), systemd-creds (to configure the minimal amount of system settings, such as keyboard mappings, locale for the newly installed system), followed by a request to reboot.” Per the release notes, it “operates either interactively or command-line driven.”
An Instance Metadata Service subsystem
systemd 261 also gains a subsystem for reading the metadata that cloud platforms expose to their virtual machines. The release notes state that “An IMDS subsystem has been added. Specifically, there’s now systemd-imdsd which provides a local Varlink IPC API that makes IMDS services accessible to local programs.” According to the changelog, the recognized platforms are “Amazon EC2, Microsoft Azure, Google Compute Engine, Hetzner, Oracle Cloud, Scaleway, Tencent Cloud, and Alibaba ECS.”
A unified storage tool
The candidate introduces a new command-line interface for storage management. According to the release notes, “A new ‘storagectl’ command line tool and an accompanying io.systemd.StorageProvider Varlink interface have been added, alongside the new generic providers systemd-storage-fs@.service and systemd-storage-block@.service.” The notes add that these “allow exposing storage resources (filesystems, block devices) in a unified manner for use as managed user storage.”
Live-update kernel handover
systemd 261 wires its main process into newer kernel facilities for surviving an in-place kernel replacement. The release notes state that “PID1 now supports the kernel’s Live Update Orchestration (LUO) / Kexec Handover (KHO) systems when present and enabled. System units’ FD Stores are now preserved through kexec, and units will get back stashed (named) file descriptors after kexec.”
A date-of-birth field for user records
Ahead of the release candidate, The Register reported a change to systemd’s user-database service “which adds a field to hold the user’s date of birth.” The outlet wrote that the field “Stores the user’s birth date for age verification, as required by recent laws” and supports “the new parental controls in Flatpak,” and that “The change comes after the recent release of systemd 260 but unless it is reverted for some reason, it will be part of systemd 261.”
What We Don’t Know
As a release candidate, systemd 261 is not final. The release notes flag multiple backwards-incompatible changes, and the changelog records that support for “/run/boot-loader-entries/” is planned for removal in version 262. The notes do not commit to a firm date for the final 261 release. The date-of-birth field’s inclusion was described by The Register as contingent on the change not being reverted, so its presence in the shipping release is not guaranteed by that reporting.