Skip Navigation

Systemd (apparently this issue is still so hot that a D or a d makes a difference, whatever)

UPDATE: after many comments, let me be clear that i have nothing against systemd at a technical level. It indeed solves issues that people had and found it's way in most mainstream distros for good reasons, beside being pushed by Redhat and Debian, which makes for basically every other mainstream distro out there without much choice. I never used it long enough to judge it, and i dont intend to judge it from a technical point of view. I am worried that such a centra piece of technology deeply interwined with linux is under direct control of IBM and Microsoft (who is the employer of the systemd lead). This might mean nothing, or this could be important for the long time future of linux freedom.

I have recently been exposed to a lot of stuff against systemd.

I know its an old debate that has inflamed people for a long time, I am not looking into restarting it as I never took a stance into it in the past anyway.

I am myself a almost 30+ years power user of Linux and I have never used systemd much myself since it never fixed any issues I had with the previous approaches, and since I am a good user of Gentoo, always loved the freedom to just keep using OpenRC and din't ever bother with systemd.

I like the Unix approach and at the same time, if it is not broken don't fix it, is my basic idea. So my approach to systemd has been not of dislike, rather of I don't care, I don't need it. And I never needed it anyway.

After reading trough most of the links below I start to think that maybe my stance could be more than simple technical.

What are other lemmy-ers idea on all this?

I didn't knew about Microsoft taking over the Linux Foundation either, and I am getting concerned about the real freedom behind my beloved Linux.

TLDR: I don't dislike systemd, I never cared about systemd. Do I need to start caring now due to all this non technical issues?

Note: i a copying verbatim the following article to stress that these are not my personal opinions and that i didnt do a proper research on the topic, except reading (most) of the links below.


(The following is a post on the #libreware telegram channel on the 7th/8th of February 2025)

Lennart Poettering intends to replace "sudo" with #systemd's run0. Here's a quick PoC to demonstrate root permission hijacking by exploiting the fact "systemd-run" (the basis of uid0/run0, the sudo replacer) creates a user owned pty for communication with the new "root" process.

This isn't the only bug of course, it's not possible on Linux to read the environment of a root owned process but as systemd creates a service in the system slice, you can query D-BUS and learn sensitive information passed to the process env, such as API keys or other secrets.

https://fixupx.com/hackerfantastic/status/1785495587514638559

Nitter mirror: https://xcancel.com/hackerfantastic/status/1785495587514638559

Here are some links about #systemd #alternatives for #Linux in no particular order. Which are your favorite alternatives and distros?

https://suckless.org/sucks/systemd/

https://unixsheikh.com/articles/the-real-motivation-behind-systemd.html

https://sysdfree.wordpress.com/

https://nosystemd.org/

https://skarnet.org/software/systemd.html

https://the-world-after-systemd.ungleich.ch/

https://ewontfix.com/14/

https://forums.debian.net/viewtopic.php?t=120652

https://www.devuan.org/os/announce/

https://www.devuan.org/os/init-freedom

https://thehackernews.com/2019/01/linux-systemd-exploit.html

https://judecnelson.blogspot.com/2014/09/systemd-biggest-fallacies.html

https://chiefio.wordpress.com/2016/05/18/systemd-it-keeps-getting-worse/

https://systemd-free.artixlinux.org/why.php

Some more added here too: https://start.me/p/Kg8keE/priv-sec

#systemd #Linux

61 comments
  • Systemd provides a modern user space which fixes a huge number of problems. At first I found it difficult to learn but it had things I needed and I made the effort. I will always be nostalgic about things before systemd because I started using linux in the mid 90s.

    I'm not going to throw away my GPU and multi-core CPU and go back to a 386 running dos because multithreaded applications and speculative execution scare me. There is no way to match what modern systems can do by taking old architectures and just adding more gates or faster clock speeds. And there are parallels in software architecture.

    There is absolutely nothing wrong with running a BSD or a non-systemd linux distro if you like. They are still perfectly usable in a lot of situations doing the same stuff people did for years in these systems. If you have a server with a static set of devices that runs a fixed set of services at startup you don't really need systemd. I still have some systems like that but systemd also handles those cases more efficiently and robustly.

    You see these sort of link dumps from people who think vaccines cause autism or that some diet will cure cancer. Whatever the intention behind it I always associate it with a bad faith attempt to fuck with people's heads by bamboozling them with more information than they can rationally analyze.

    Believe what you want but you might want to consider that all the experts working on systemd and using it productively might know their shit.

  • How do you know a post was written by a systemd hater? Easy, they'll spell it with a big D for some reason. It reminds me of how Norwegian rabid anti-cyclists are unable to spell "cyclist" for some reason.

    Claiming you don't want to restart an old debate and then trying to restart it anyway is pretty funny.

    You might also want to keep in mind that you can't really force an init system on Linux distros. Systemd became the norm through being preferred, as in, the people using and maintaining it think it's good. At this point you might as well be ranting about how "LinuX is evil somehow" and we should all be using GNU HURD or Minix or something.

    Also: Haven't thought about suckless in well over a decade, maybe closer to two? I guess way back in the day I was kinda intrigued by their ideas and used some of their products; these days I'd rather see them as something between an art shop and people who are playing a somewhat unusual game with themselves, but not particularly relevant to mainstream software engineering.

    • I am not debating it's good or bad from a technical perspective, i don't care, i am sure it's good otherwise why use it at all.

      Why are you focusing on that? I never said it's been forced, i never said its bad or evil, i never discredited it.

      I think it's worth understanding if the non technical points are just FUD or not, i worry about the future of Linux, not the future of it's init system whatever it is, all it need to do is satisfy it's function and OpenRC do it as well as systemd (there, with the small d is it different?).

      I was under the impression SystemD was the name, with the capitals and all. Will fix the top post if this is somehow offending you. Whatever.

  • Systemd is a good init system. Better than any of the alternatives, although they've also come a long way since systemd first came around. It's also a weird interconnected mess of a thousand other things that probably shouldn't all be lumped together into a single project. Half of them are absolutely vital to the vast majority of Linux systems, and half of them are unused and neglected and no one has touched them in years, but they're all stuck together in one weird project for some reason.

    That's kind of the exact same sort of situation xorg was in 20 years ago. I am concerned that systemd is going to turn into the next xorg, but really those concerns are the only reason most people should consider an alternative. If you don't care about that, you probably don't need to worry about systemd.

  • I personally don't really care much about the init system. For most of my linux journey i was using arch, then void, then nixos, and now i'm back on void, so i jumped between systemd and runit for a bit. I never chose to use void because of its init system though, i just prefer its package manager. I found both systemd and runit to be fairly simple to use and it just gets out of my way. Poettering working for microsoft has concerned me a little bit, but if i'm being honest that's just me wearing the tin foil hat. I will say though that at this point, if something were to happen to void and i had to move back to arch, i might try using artix just for the style points, and because of me already being familiar with runit anyway.

    • Yes, that is one point. Having the main dev working for "the enemy". Systemd being developed by the main dev who is at microsoft? To me that rings some bells.

      He will keep doing a great job, he is paid for this, but the point is that microsoft could try to control linux a bit too much, and so is IBM...

61 comments