Systemd is one of the more controversial elements in Linux and continues to raise some serious concerns about security, performance, and the future of Linux.

What Is Systemd?

Systemd initially started as an init system, the initial process a Linux system runs that is responsible for starting everything else. The init system controls the bootup process, helps load the right kernel modules for the available hardware, and manages the various other processes on the system.

Systemd was designed to replace System V init (sysvinit, or SysV) that the majority of Linux distros used at the time. One of the developers’ primary goals was to make a faster init system, especially for startup, by making systemd launch processes concurrently, rather than sequentially like SysV.

Over time, systemd evolved far beyond the original goals, and has grown to take over a number of features and functionality that would traditionally be handled by other utilities.

Controversies Surrounding Systemd

Despite the many benefits systemd offers, and its standing as the most widely used init system on Linux, the project has drawn its fair share of controversy and sparked the ire of large portions of the Linux community. There are several reasons for this.

• Systemd takes a monolithic approach to managing system services that flies in the face of the Unix philosophy of having one app or service do one thing and do it well. Instead, systemd handles a slew of services and functions that would traditionally be handled by different utilities under previous init systems.
• In addition, as systemd has grown, many applications require it to function correctly. Even applications that can function without it may require quite a bit of additional work in order to make them function.
• Lead developer Lennart Poettering has also been a source of concern for some users. Poettering has not always been the most receptive to feedback or concerns, and left Red Hat for Microsoft in 2022.

The Latest Update Raises Far More Concerns

DJ Ware, a YouTuber with decades of experience as a system admin, goes into detail about some of the issues with the latest Systemd 257 version. The issues can be broken down into a couple of main concerns.

As DJ Ware points out, systemd’s growing footprint and feature creep have led to a situation where the service now controls so much of the Linux system that it essentially makes it one massive fail point. To make matters worse, much of systemd’s functionality is abstracted, making it difficult to see exactly what it is doing in some situations.

“Let’s look at what I have observed with systemd on Fedora 42,” explains DJ Ware. “Over 3,000 systemd-related kernel thread spawn at boot. 25 to 35 systemd services come up and are active. In layman’s terms, systemd was supposed to be the guy who opens the building in the morning. Now he’s also the security guard, the janitor, the building inspector, the heating guy, and the one who decides who gets mail. Whether you ask for them all to be there or not they’re just there.”

Existing Options and Alternatives

Users who share DJ Ware’s concerns have limited options available to them. The fact remains that the virtually all of the mainstream Linux distros have long since made the switch to systemd. Given the system’s inherent feature creep, it’s unlikely that any of them will be replacing the init system anytime soon, as doing so could break functionality of some software, services, and scripts.

Having said that, there are a number of distros that do not rely on systemd, using the older System V or the runit init system.

MX Linux is another option, and likely the easiest options for users to transition to. MX Linux is a Debian-based distro that uses SysV. MX primarily uses Debian repos, giving users access to its wide range of software, but also maintains its own repos for specific applications and tools.

One of the things that sets it apart from other options is the fact that it includes systemd purely for compatibility reasons, but it is not enabled. The MX Linux About Us page explains how it works.

Because the use of systemd as a system and service manager has been controversial, we want to be clear about its function in MX Linux. Systemd is included by default but not enabled. You can scan your MX system and discover files bearing systemd* names, but those simply provide a compatibility hook/entrypoint when needed.

MX Linux uses systemd-shim, which emulates the systemd functions that are required to run the helpers without actually using the init service. This means that SvsVinit remains the default init yet MX Linux can use crucial Debian packages that have systemd dependencies such as CUPS and Network Manager. This approach also allows the user to retain the ability to choose his/her preferred init on the boot screen (GRUB).

Devuan Linux is one of the most well-known alternatives for systemd critics. Devuan was forked off of Debian when the latter adopted systemd. Given Debian’s popularity and large user base, Devuan provides one of the easiest options for users looking to make the move away from a systemd-based distro. Devuan mirrors Debian’s package repos, but patches any apps requiring systemd so they can run without it. This gives Devuan users one of the biggest advantages Debian provides, namely access to an extremely large collection of software. Devuan also gives users the ability to choose their init system, with sysvinit, runit, and OpenRC officially supported.

Artix Linux is an Arch-based distro that relies on the OpenRC init system, although it also offers dinit, runit, and S6. Being Arch-based means that Artix is a rolling release distro. It also has its own repos, much like Devuan, so that any software requiring systemd can be patched to be compatible with non-systemd init systems. Being Arch-based, Artix may not be suitable for new users.

Void Linux is another option, using runit as its init system. Void is something entirely different from the other entries on this list, as it is not based on anything. Instead, Void is a completely independent distro, with its own repos and unique package manager. Void is also a rolling release distro but, unlike Arch, is not bleeding edge. That means that software is continuously updated, so the user does not have to do major upgrades every year or so, but the software is only pushed to users when it has been thoroughly tested and vetted. That being said, Void is easily one of the hardest distro on this list for new users.

Gentoo uses OpenRC instead of systemd, giving users yet another option. Gentoo is not a distro for new users, however, and emphasizes building software from source instead of relying on binary like other distros do. Gentoo developers recently expanded the availability of binary packages, but anyone using the distro is likely still going to eventually end up building software from source.

Slackware is another systemd-free distro, relying on SysV for its init system. Slackware holds the distinction of being the oldest Linux distro still alive and in development. That being said, its development pace is far slower than many other distros, and it is also not a new user-friendly distro.

What Does the Future Hold?

It’s difficult to say what the future holds with any certainty. Systemd has been around for a decade and a half, with near Universal adoption within the Linux community. While it is entirely possible that something will replace it, it will only happen if more and more users grow concerned with systemd, and it will certainly not happen overnight.

In the meantime, users who want to avoid the issues raised by systemd should look at the above solutions. For new users, or those wanting a no-fuss replacement, MX Linux is probably the best choice, followed closely by Devuan. Artix will be somewhat more difficult, especially for new users, but will still be far easier than Void, Gentoo, or Slackware.