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?
(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://skarnet.org/software/systemd.html
https://the-world-after-systemd.ungleich.ch/
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
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.
i like systemd
I’ve never used another init system, but i see no problem with systemd. The declaritive approach makes things very robust. Surely some things can be improved, but it’s a good tool.
Edit: Also managing user services the same way is nice.
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.
To my understanding that actually solves issues. A lot of ppl already prefer other tools like doas since sudo is basically “too big” for what it does.
More code means more potential bugs. run0 has to my knowledge significantly less code. And the benefit of not relying on SUID.
In the end, you do you. The big distros will adopt what is good for them and good to maintain. You do not have to use it.
A lot of man-hours went into engineering it. Very smart people from many distros went over it, kicked its tires and deemed it good enough to replace old SysV. We’ve been through this, if you don’t like it for some reason, use something else.
It’s just software, people, it’s not a frelling religion.
We’ve been through this, if you don’t like it for some reason, use something else.
My god. Yes, we’ve been through this. You can’t just replace Systemd on most distros, because to have the alternatives in the repo, they would have to provide a bunch of shims and wrappers or have two different repos entirely. This is why i dislike Systemd, btw.
And before you start with Gentoo; yes, there it works, because it’s source based and Openrc is basically the wrapper.
Did you read my post at all? Maybe I am not clear enough.
I don’t care for systemd, I don’t dislike it I don’t like it. I don’t use it but merely because I never felt the need to use it, or I would have use it.
What people think of the non technical reasons given in the links/post is what I am asking. Is it just FUD or there is a valid base to them?
You provided 15 links.
Are you seriously expecting somebody to walk you through each one?
You’re claiming not to care either way about systemd and yet you’ve provided 15 sources against it and apparently done zero research into why it has been so widely adopted.
I really love all the 5+ years old articles about why systemd sucks.
It’s not perfect but it’s so much better than the plethora of different init methods Linux used to have. Also managing sysv init scripts sucked really bad.
It’s lightweight, most of it is optional, it’s declarative, it makes managing your systems much easier and it just works.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.
I don’t understand what you are talking about.
I like reading a post with a clear topic and reasoning, unfortunately it’s not obivous to me.
Something like “I dislike systemd because XY. What do you think?” Would help me.
I don’t dislike systemd, I never cared about systemd.
Do I need to start caring now due to all those non technical issues?
(Tldr added to top post)
Why do you feel a need to form an opinion on this based on what others think?
Exchange of opinions is a great way to learn and broaden your views.
In that case why not share your opinion?
Instead you’ve claimed you’re neutral and shared links to the views of 15 other people.
You haven’t even provided any context on these articles. Or quoted anything from them that you are concerned about.
Everything about this screams you’re asking in bad faith just hoping to waste people’s time or start an argument.
Where did you get this idea?
I didn’t knew about Microsoft taking over the fsf either, and I am getting concerned about the real freedom behind my beloved Linux.
I think you are confusing FSF with the Linux Foundation, and you can see MS as part of the platinum LF members. Was that it, or you really meant FSF?
You are right… I will fix the top post
Gentoo user here too. I once switched to systemd, but didn’t stay using it for too long. Back then some things didn’t work with systemd. Nowdays my systems use seatd instead of logind or elogind. Some have musl toolchain. It’s just simpler, currently, for me to use OpenRC on all of my setups. But the thing I most disliked with systemd was that it cannot work without journald.
How is musl? Does it make a difference on glibc?
It’s supposed to be more strict about standards… and maybe lighter in resources. I’ve been only testing it. Curiosity driven choice. 😉
Fellow gentooer! I love how much you can actually decide by yourself how to craft your system with Gentoo.
OpenRC just rocks, a few lines of bash and all is set. But indeed is not for everybody… (Joking).
Systemd has more features than old SysV init scripts. Particularly around detecting events and taking actions such as starting firewalls when joining networks, turning on battery tools when unplugged from a charger, starting new services when connected to a dock etc.
The other things it does, it does more reliably than sysV init scripts. It starts services concurrently, provides a profiler to improve start up time, contains much less code, provides better security to tapping into the container features of Linux.
Security is actually where Systemd has troubles generally. It has more CVE tgan all other init together. And reliability (esp. starting order of services) is another weak point.
Anyway what you describe is done at DBUS level which has nothing to do with an init system. I do have DBUS and works just fine as it would with OpenRC or SystemD either.
SystemD doesn’t really help with all that, with OpenRC never had issues with that.
I don’t know what systemd does and now I’m too afraid to ask.jpg
Also obligatory fuck microsoft, go crawl and Embrace other stuff.
I was impressed they resisted calling it micro$oft. That’s the usual sign of somebody adopting the tribal views of others.
It feels a bit childish to call it microshit, micropenis, micro$oft etc if there is no specific context IMO.
I think when systend goes into systemv, a systemb is born almost a year later
LoL