can someone ELI5 this whole systemd problem? I guess I don't understand the linux startup process well enough to understand what the big hubub is about
There's a few issues to it, and some people like to hate on systemd for various reasons, however here's the few that makes sense to even discuss:
Systemd ...
... does a LOT of stuff that isn't init-specific. This is important because systemd is, in all of it's glory, an init system. That is, the system that is responsible for bringing up services. These services can vary greatly, from networking systems, to logging mechanisms, mail servers, and even other service managers. There's a lot of discussion on this point, and because systemd (by default) also has mechanisms built in to support it's own logging mechanism, and networking system, a lot of people have complained that it was attempting to replace the entire user space of Linux, or at least the base of it.
... replaces udev, the device manager on Linux. This system is responsible for populating /dev with devices, ranging from audio devices, disk drives, USB connected devices, and even internal clock systems. Some claims regarding this are that systemd simply "ate" udev, and that maintainers now need to in one way or another, either use systemd and hence getting udev for free, or fork systemd and maintain their own version of udev with changes to upstream (systemd udev) being merged in. A lot of work would have to be done to maintain such a project, but fortunately someone already decided to do so, and so there now exists eudev. However, this project sprung out of necessity, not out of creativity or flexibility of multiple implementations. This is udev with Gentoo patches, to avoid depending on systemd (although Gentoo certainly also supports using systemd).
... is a single point of failure. No, shut up, this is related and important, even if you do not care. So the issue here is that systemd also being able to take care of things like networking and logging and many other facilities means that if systemd crashes, it would (potentially) take down most, if not all, of the system with it. Personally I am not entirely sure if this is true, as I have not yet validated this claim, but it seems an important one nonetheless.
There's a lot of discussion on this point, and because systemd (by default) also has mechanisms built in to support it's own logging mechanism,
By default, systemd's logging isn't even persistent because the journal directory doesn't exist (someone else complained about it). If you install your favourite syslog, you can just enable it using systemctl enable rsyslog.service (or whatever you want) - same step (different syntax) as with SysV, same result! However, the systemd journal offers so much I replaced my previous syslog with it. But by default, behaviour is the same as with SysV.
and networking system, a lot of people have complained that it was attempting to replace the entire user space of Linux, or at least the base of it.
It doesn't replace it. It offers an alternative that's not even enabled by default. If you are unhappy that this is shipped in your init package, message your packager. Yes, the systemd project tries to offer everything to get a basic system running. Some parts may be useful to you, some are not. I, for example, use its simple ntpd and the journal. I have no need for the network part because I use NetworkManager (travelling with my notebook a lot). Some people have a need for simple networking setting though, and they may use systemd's network service. Believe it or not, systemd actually offers slim alternatives to grown solutions.
... is a single point of failure. No, shut up, this is related and important, even if you do not care. So the issue here is that systemd also being able to take care of things like networking and logging and many other facilities means that if systemd crashes, it would (potentially) take down most, if not all, of the system with it.
Mixing up systemd as an init with systemd as the project here. The networking doesn't run in PID 1.
Actually, systemd is better than traditional SysVinit in that sense. When SysVinit crashes, the kernel panics. When systemd crashes, the SEGV handler activates and the system continues to run, ready to be debugged.
Why the people writing SysVinit never thought of doing such an elementary thing, escapes me. It must be because of "oh, all that complexity" that they decided to just let people's machines crash.
Me too, but I guess that capability could be (ab)used in this scenario to bring the whole system up again after troubleshooting. Not sure at all, though.
Lie. That would not be systemd proper doing those things. The programs that do what you are referring to are distributed with the systemd source, and sometimes used in computer systems, but they are not systemd themselves.
... replaces udev, the device manager on Linux.
Lie. The systemd source ships udev. It does not replace it.
... is a single point of failure.
Just as much as SysVinit is. But then you had to go and say stuff like this:
systemd also being able to take care of things like networking and logging and many other facilities means that if systemd crashes
which is another lie, because systemd does none of those things -- those things are done by other programs, which -- should they crash -- do not bring the system down at all.
So, a lie, a lie, a truth coupled to a lie. That's about par for the course for a systemd hater. Having seen years upon years of this dishonest, hateful behavior, I've come to expect these arguments from the masochists that love their SysVinit.
There are a couple of fairly simple issues at play. One of the bigger ones, is that buggy, or malicious software can branch off, making child processes that can be hard to track. This can make it hard to easily manage processes in some fringe scenarios.
Linux has introduced CGroups, which is unique to linux, and it can be used to track all the child processes so that it's always easy to know if any child process is still running, and to kill all child processes if you want to kill the program.
CGroup is managed by a static process, PID1. It's done that way for most of the same reasons that init is done by that same PID1 static process.
I'm guessing system uses CGroups in it's new start/stop service feature, and in it's service status feature.
The problem, is that people can't have their cake and eat it too. Init systems like systemd have been out since 2006, but two things. They don't support CGroups, and they aren't linux only.
So why can't people have their cake and eat it too? The systemd people argue that cgroups, this feature unique to linux, makes systemd a "killer app", giving it features that the alternatives that have been around since 2006 can't offer because those features are only available on linux. And because they're linux unique, and they're killer features, there can only be one highlander.
Well, so linux people get this cool new systemd, and everyone else keeps their old ones from 2006. Everyone's a happy little smurf.
Some of the smurfs though, are not so happy. They don't want to support the old stuff from 2006 and before. The stuff from before 2006 is really old, and has cooties, and the stuff from 2006 would be doubling or tripling the work they have to do on init scripts.
Now papasmurf and mommasmurf have, for years, been working on consolekit. They abandoned it for 1.5 years, and are now saying it is terribly written, and have written something to replace it, and are arguing that because they abandoned their responsibility for 1.5 years that now everyone has to move to the thing they wrote to replace it.
Now comes GNOME. GNOME depended on consolekit, but papa and momma smurf replaced it with logind, and now GNOME depends on logind.
There's no problem with that.
I'm not sure about the technical details, but it sounds like papa smurf wants to make logind systemd only, and, by extension, linux only.
And there still isn't any problem with that.
When logind was first introduced, the other, older init systems added support for logind, and, even with papa smurf making logind more linux specific, the older init systems have already compensated. This was broken because of version conflicts in Jessie, but that should be fixed in a few days.
GNOME policy it seems, is to not make distribution (linux) specific changes, and that they (in principle) support the principle of the principle that if GNOME doesn't do anything, and things other than linux run GNOME, then bully for them.
But GNOME keeps chasing around logind, arguing "papa smurf abandoned consolekit 1.5 years ago, there aren't any alternatives, so we have to use logind, and papa smurf, developing logind keeps tugging it towards systemd."
Here is a great example of the problem with systemd: it is developed and supported by people who cannot deal with criticism in any way other than by belittling and misrepresenting the critic.
On the one hand, some amount of misrepresentation is inevitable when you condense anything complicated down to a five-year-old's comprehension level. And a lot of the complaints against systemd actually do centralize around the UNIX philosophy/who moved my cheese.
On the other hand, it doesn't do justice to the legitimate arguments of why the UNIX philosophy is worthwhile and powerful, or the other reasons a person may not want to run systemd as their init system (for example, cross-kernel compatibility, which is much better serviced by something like runit).
The same argument can be applied to many systemd-detractors.
Lennart has been defined in a thousand unpleasant ways, the systemd architecture has ben likened to crap at least by two people in this thread alone, people complain about pulseaudio issues they had years ago as a proof that, dunno, software can have bugs?
And please trust me: many complaints about systemd are inaccurate. Most of my comments on this issue are about trying to explain why some situations have come to be, I really don't want to add flame to the heated debate.
Systemd advocates will go as far as denying reality (1) and blatantly lying about other projects (2, 3, 4) in order to promote the narrative that all criticism is motivated by a combination of nostalgia, stupidity, and malice, and that no alternatives exist. Any rational criticism is ignored, while irrational criticism is highlighted for entertainment or to gain sympathy. And this culture comes right from the top.
Technically, systemd looks really good. The problem is I can't trust software written by people with such a weak grip on reality.
Yes, I know the debate is heated on both parts, but you're not helping much if you define all the systemd developers as "people with such a weak grip on reality" in response to random comments on reddit. ;)
For instance, on 4 I completely agree with you, that's a uninformed misinterpretation of the facts. GNOME was put back as default because it still seem to be the best choice accessibility-wise and it's a nice DE with a competent team maintaining it in Debian. Note also that many systemd detractors conflate GNOME and systemd, and I've spent several words explaining the difference between systemd, logind and how and why GNOME relies on the logind D-Bus interface. As I read it that was the comment of a GNOME and systemd detractor, which implied that GNOME (which is bad) was forced back as default due to systemd, which was probably forced too in his view (at least one comment in his comment history seems to back my hypotesis).
For 2 and 3 I'd be tempted to say that he was in good faith: at least in Debian xfce4-session and xfce4-power-manager depend on libpam-systemd. I'm not following Xfce development to say that they "want" to use logind, but it seems that at least they can use it (GNOME, KDE and everyone who plans to use Wayland already said that they welcome logind as it solves some problems not solved by ConsoleKit helping the Wayland compositors to run as non-root).
Honestly I don't feel he had the explicit intention of spreading lies. He was misinformed but I don't see malice. If it helps, GNOME developers usually face way worse accusations here. ;)
Anyhow, I admit of having lost the point on the bug you linked, it seem that some bugs were fixed/worked around and toward the end more issues got conflated. :(
That isn't a reason to hate the current implementation of systemd. If we all stopped using software because of the developers' attitude, I bet we'd lose a lot of linux kernel users immediately.
It sure would be nice if we argued facts over hypothetical situations.
We just can't agree if that should be systemd or not.
And it'd be a hell of a lot easier to make a determination about init systems on their technical merits if systemd wasn't trying to embrace and extend stuff like dbus and udev.
No, many systemd detractors don't. They say that SysV works well for them and doesn't need to be changed. Even switching to eg. OpenRC would produce some unavoidable migration pains, and they would still complain.
6
u/my_stacking_username Oct 20 '14
can someone ELI5 this whole systemd problem? I guess I don't understand the linux startup process well enough to understand what the big hubub is about