40 ms·
This is a very detailed article, and I appreciate it and will need to study it carefully. But I think that the major argument it is making is "systemd is a med
by geofft 11y ago
This is a very detailed article, and I appreciate it and will need to study it carefully.
But I think that the major argument it is making is "systemd is a mediocre service manager; similar tools existed before systemd, and were better." That is a very different argument from "we would be better off with sysvinit," which seems to be the primary argument I see in practice: if you're arguing things like "do one thing and do it well," "shell scripts are great and debuggable," "init should reap children and nothing else," "there's too much code in pid1," "I don't want to learn something new," etc., you're making that form of argument.
If there is general consensus from studied opponents of systemd that something systemd-like is an obviously good idea, great. Let's move on, acknowledge the network effects of systemd, and build something that can feasibly be the shinier, newer, better, securer systemd. Which might even be based on an existing system like s6. But then the path forward has to be either improving systemd or replacing it, not continuing with sysvinit.
I am in practice a pro-systemd person, but that's only because my realistic alternatives, for my use case, are sysvinit and Upstart. I have no idea how I'd start to build a system that used something like s6. I would happily admit there is extensive room for improvement in systemd, but we UNIX folks have been working with worse-is-better and rough-consensus-and-running-code for decades.
If the general consensus is that a systemd-style service manager is great, but it should not be pid 1, that's an argument worth making, but I don't see much focus in this article on that.
If the general consensus is that everything can be done with sysvinit, this article doesn't make that case at all. (But I suspect that's not the general consensus.)
- lobster_johnson 11y agoTalking about "general concensus" is hard because there are a lot of different viewpoints, and depends on how much of the debate one is exposed to. I have seen people compare systemd unfavourably to daemontools, s6, runit, Solaris' SMF, and Apple's launchd, to mention a few. I've never seen anyone so reactionary that they suggest that SysV is in any way or shape the better alternative. A lot of people are unhappy with SysV, but if they don't like systemd, they would probably consider sticking with SysV to be the lesser of two evils. > Let's move on, acknowledge the network effects of systemd, and build something that can feasibly be the shinier, newer, better, securer systemd. Unfortunately, I think that for those who don't like systemd, their criticisms (its design is a monolithic, intrusive, all-consuming, all-or-nothing ball of yarn contrary to Unix philosophy about small, composable programs cooperating over standard protocols) cannot be solved by improving systemd itself, at least not without a huge undertaking to redesign and break it apart, somehow.
- rodgerd 11y ago> I've never seen anyone so reactionary that they suggest that SysV is in any way or shape the better alternative. Unfortunately it's... a position that is not as rare as it ought to be. Some of the frustration and heat undoubtedly comes from the fact that while reasonable people can disagree about the best way to implement many of the goals of systemd, it's hard to take anyone seriously when they propose that SysV init is "more Unix" or technically better. > ...cannot be solved by improving systemd itself I suspect the most fundamental impediment is that upstream simply aren't interested in radical changes to how it works - it would be like trying to convince Linus that Linux needs to be a microkernel, or Theo that he needs to start using Rust for OpenBSD. Any replacement for systemd is probably going to have to do what systemd did (and what daemontools and runit didn't achieve) and create a broad buy-in, with the additional overhead of working with at least some of the systemd dbus interfaces for compatibility.
- skarnet 11y agoIt's important to realize that "a replacement for systemd" is neither achievable nor desirable. systemd has grown fast and conquered large market shares because it was backed up by a company, which put a lot of money and manpower into it - to write it, to integrate it, to advertise it. The only thing that has not been correctly funded in systemd is research and design. systemd is only Open Source if you read the license; all its other aspects are proprietary - it's software made by a company and aiming to capture a market. It is impossible to compete with systemd on the same grounds, because no real Open Source developers will have as many resources as Red Hat. And even if it was possible, the result of such an attempt would simply be another integrated behemoth, powered by money and marketing instead of good technical decisions. (Or even worse, powered by ideology - can you imagine a systemd-like controlled by the FSF?) In the end, the situation for the users would be even worse than it is today. You don't fight Goliath with Goliath; you don't fight Microsoft's hegemony by buying Apple products. About interface compatibility: the author of the DnE article (vezzy-fnord) has written uselessd, and finally abandoned the project because the systemd interfaces are so tightly integrated with the systemd design in the first place that it's impossible to be compatible without simply being a systemd clone, which he did not want uselessd to be. No, interface compatibility is not an option, because it would simply acknowledge the validity and superiority of the systemd architecture, and nobody wants a copy of systemd. I believe that the way to provide an alternative to systemd is to provide all the functionality that the systemd users like, but in a technically better, less integrated, more unixish way. With s6, s6-linux-init and s6-rc, I now have respectively a process supervision system, a simple init process and a service manager, which should be sufficient for a majority of applications. The next important thing that sysadmins like in systemd seems to be cgroup management, so I'd like to study the thing soon and assess what needs to be done next; but for now, I believe that the s6 family of programs is now viable as a serious alternative to systemd, and I would love to give it a broader audience.
- 9mit3t2m9h9a 11y agoWell, note that the article is mostly about the core systemd service management part. The article also clearly studies quality of design and implementation, accepting core goals of systemd core as they are. One problem with «shinier, newer, better, securer systemd» is that many systemd opponents want something less shiny. And systemd is big and shiny enough that _even_ sysvinit is better. Most arguments for sysvinit you list are, for example, arguments for s6: s6 is just a supervision suite with no other ambitions, PID 1 during the normal operation (not boot/shutdown) is s6-svscan — a 32 KiB executable, and the part that requires debugging — service launch scripts — can still be a shell script. I am a systemd hater (at least for my patterns of desktop use — systemd can be mostly fine on some servers) and my opinion of systemd is that it is mediocre as a service management, has bad logging system bundled (is https://bugs.freedesktop.org/show_bug.cgi?id=69934#c7 https://bugs.freedesktop.org/show_bug.cgi?id=69934#c7 fixed? can the systemd-bundled logging system give me the last 20 lines of the log without reading all 100 MiB of the log file — it previously could not?), and breaks my workflow hard (nothing similar to startx can be implemented by design http://lists.freedesktop.org/archives/systemd-devel/2012-February/004614.html http://lists.freedesktop.org/archives/systemd-devel/2012-Feb... for example), and systemd updates make systemd try to control more of the system which I explicitly do not want controlled automatically (I have a very handy binding for standby, and I do not want the notebook to suspend on lid close; I have multiple network configuration scripts for each of three typical locations and choose between them depending on whether I plan to move around more than transfer multiple-GiB files; killing all this autoconfig requires work). I would probably use uselessd just to avoid bothering if NixOS shipped it instead of full systemd; it doesn't so it is more comfortable for me to use a NixPkgs-based system with init=/bin/sh and minimal hand-written init scripts than stock systemd. I was capable to use systemd almost fine until systemd has ensured that startx-like functionality is impossible to get. Edit: a typo
- digi_owl 11y agoI suspect the startx issue is related to why they introduced the su alternative recently, PAM based session tracking.
- rc4algorithm 11y ago> I would happily admit there is extensive room for improvement in systemd, but we UNIX folks have been working with worse-is-better and rough-consensus-and-running-code for decades. You're understanding "worse is better" backwards. It means "starkly simple to the point of being initially off-putting is better". In this context, it means (in part) "be a big boy and learn how to write a shell script". (Not to be too condescending, but I think that captures the Unix perspective here.)
- ised 11y agoYes. I like how you use the word "initially".