Systemd 260 Drops SysV Init Support in Major Cleanup Update

The release of systemd 260 marks one of the most significant updates in recent versions, introducing sweeping changes that modernize the Linux ecosystem while phasing out long-standing legacy components.

🚨 End of System V Init Support

One of the biggest shifts in this release is the full removal of System V init script compatibility. Tools and components such as systemd-sysv-generator, systemd-sysv-install, and rc-local.service have been eliminated.

This effectively ends support for traditional SysV init scripts, meaning any systems or applications still depending on them must transition to native systemd unit files to remain functional.

⚙️ Higher System Requirements

Systemd 260 also updates its baseline requirements across key components:

• Minimum supported Linux kernel is now 5.10 (newer versions recommended)
• Updated dependencies include:
  • glibc 2.34
  • OpenSSL 3.0
  • Python 3.9

These changes reflect a push toward newer, more secure, and better-performing system foundations.

🧱 Introduction of “mstack”

A major new feature in this release is mstack, designed to simplify how services and containers are structured and deployed.

With mstack:

• Overlay filesystems and bind mounts can be defined using a structured directory layout
• Applications can be packaged as self-contained environments describing their runtime setup

To manage this, a new command-line utility called systemd-mstack has been added, allowing administrators to create and control these configurations directly.

📊 New Metrics and Reporting System

Systemd 260 introduces a modern reporting framework for collecting system-level data:

• Components can expose structured information via Varlink endpoints under /run/systemd/report/
• A new tool, systemd-report, allows this data to be gathered in JSON format

This provides a unified and standardized way to monitor and analyze system behavior.

🔗 Expanded Use of Varlink

The release continues to expand the role of Varlink as an inter-process communication (IPC) mechanism:

• A new service registry for discovery has been added
• Additional Varlink interfaces now complement existing D-Bus functionality

This indicates a gradual shift toward broader adoption of Varlink across systemd components.

🔋 Power Management and System Enhancements

Updates to logind improve how power-related states are reported, especially regarding inhibitor conditions. This may require adjustments in desktop environments and related tools to fully support the new behavior.

Other notable additions include:

• New unit options such as BindNetworkInterface= and MemoryTHP=
• Improvements to user namespace handling

🌐 Networking Improvements

Networking capabilities have also been enhanced:

• Expanded configuration options in systemd-networkd
• Integration with ModemManager, enabling direct handling of cellular connections

📦 Container and Image Workflow Updates

Systemd 260 brings improvements to container and image management:

• Better support for OCI images
• Updates to tools like systemd-nspawn and systemd-vmspawn
• Alignment with the new mstack-based deployment model

📌 Final Thoughts

Systemd 260 is a major step forward, focusing on modernization while removing outdated features. Although the removal of SysV support may require adjustments for older systems, the introduction of mstack, enhanced reporting, and improved container workflows signals a clear direction toward a more streamlined and future-ready Linux environment.

For more information, see the changelog.