4 ms·
One of the main problems was the speed with which systemd was rolled out on all the major Linux distros, despite it being relatively immature and very controver
by pmoriarty 9y ago
One of the main problems was the speed with which systemd was rolled out on all the major Linux distros, despite it being relatively immature and very controversial at that.
The second major issue is it growing way out of the bounds of being just an init replacement, thereby violating the so-called Unix Philosophy of doing one-thing well. For a user app to do that is one thing, but for a core OS component to do that just smells way too much like forcing Linux to be more like Windows, which a lot of hard-core Linux users are ideologically opposed to.
The third major issue is that on most major Linux distros, users are not given an easy way to avoid using systemd, no matter how much they hate it or oppose it.
The fourth issue is the apparent arrogance of the people responsible for systemd, and their off-hand dismissal of mature and widely respected unix conventions.
The fifth problem is that when systemd breaks, troubleshooting and fixing it can be a lot harder than doing the same with an init script.
All of this adds up to a storm of controversy that the systemd people mostly brought upon themselves. Had they just been more humble about their creation and waited until it was mature and well-tested and did all the wonderful things they claim it could and should do instead of stuffing what was widely seen as a broken-by-design piece of garbage down everybody's throat, maybe much of the Linux community wouldn't have been nearly so outraged by it.
- DamonHD 9y ago3: Users are not given an easy way to avoid using libc or the kernel calls or ASCII text either, so that a non-issue unless you already decided that it's important not to use those things.
- setr 9y agoBy virtue of being controversial, which is not true of your examples, this does indeed add to its list of issues
- jbverschoor 9y agoI'm sorry. But the "Unix" way is to do one thing well. Why is it that every single app needs to support a "daemon" mode? It is the biggest pain in the but. I love systemd. Finally a sane solution on linux.
- JdeBP 9y agoYou weren't looking very hard for such solutions, obviously, as you missed 20 years of stuff. The idea that applications do not have to have their own code to daemonize had been around for about a decade and a half before systemd was even an idea, and there were plenty of toolsets that one could employ to manage daemons where exactly this idea was part of the design. I myself was explaining not to make this design mistake before the turn of the century. * http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.ht... * http://jdebp.eu./FGA/daemontools-family.html http://jdebp.eu./FGA/daemontools-family.html * http://blog.darknedgy.net/technology/2015/09/05/0/ http://blog.darknedgy.net/technology/2015/09/05/0/
- kpil 9y agoYes it's nice to have a proper process manager. Is just that it's obvious that the feature creep tendencies are strong, and a lot of tangential daemons and tools are affected. All in all, I've come to the conclusion that it's probably for the better, but I must admit that even small things like an embedded 'more' implementation seems a bit off somehow.
- phil21 9y agoYou like the one sane thing systemd does - very few folks argue that it's implementation of unit files and friends is a bad thing. Other init systems were progressing in the same direction though. The problem is everything under the hood. Have you ever tried to debug a wedged Linux server with a somewhat esoteric startup issue these days? It's exceedingly difficult, and not simply because you need to learn an new tool chain. It's simply made many things opaque and replaced other bits no one sane would ever expect (e.g. having to remember systemd re-implements 'rm' and the quirks that brings, etc.) As a cranky systemd-hater I also love the unit/service files - they work great, and as you say one tool that does it well. And systemd excels at making any random program a reliable and standardized daemon. Why does it also need it's own dns resolver? If I were simply an end-user or developer making apps to run on linux I'd love systemd. It's when you're maintaining the bare metal where you start to see it's lesser known and more ugly parts.
- m45t3r 9y ago> One of the main problems was the speed with which systemd was rolled out on all the major Linux distros, despite it being relatively immature and very controversial at that. When Debian/Ubuntu defaulted to systemd, systemd already had 5 years of existence. In Mageia, 2 years, while Arch Linux, took 2.5 years. Fedora was the only distro that ready adopted systemd by default very soon, in a year and half [1]. Compare this to upstart, that had an initial release in August 24, 2006 and adopted in the same year in Ubuntu 6.10 (and by default, since I don't know any distro that maintained a compatibility shim for those who didn't want to use upstart, like happens in systemd nowadays). > The second major issue is it growing way out of the bounds of being just an init replacement, thereby violating the so-called Unix Philosophy of doing one-thing well. For a user app to do that is one thing, but for a core OS component to do that just smells way too much like forcing Linux to be more like Windows, which a lot of hard-core Linux users are ideologically opposed to. However, systemd is not a single binary. Each additional funcionality is shipped in different binaries, so the init part only cares about init, journal part only cares about journal, etc. This also happens in other projects. GNU Coreutils (ls, date, cut, du, df, echo, mkdir, etc.) for example, is a collection of binaries that do each its own part. It does as much sense of calling systemd violating Unix Philosophy because it has multiple funcionality implemented in the same source code as calling GNU Coreutils violating Unix Philosophy by the same reason. > The third major issue is that on most major Linux distros, users are not given an easy way to avoid using systemd, no matter how much they hate it or oppose it. This only became a problem after systemd it seems. Ubuntu/Fedora only offered upstart, Arch only offered BSD-style init, Debian only offered SysVinit, etc... After systemd was adopted by default people started to whine to maintainers support multiple init systems, increasing the burden of maintance without obvious benefits (who are gonna fixes the bugs if the majority of developers are running something else?). > The fourth issue is the apparent arrogance of the people responsible for systemd, and their off-hand dismissal of mature and widely respected unix conventions. Well, the community is as bad or even worse than the maintainers, IMO. > The fifth problem is that when systemd breaks, troubleshooting and fixing it can be a lot harder than doing the same with an init script. Sure, however writing scripts was much worse since even the simpler things are incredible difficult to get right with scripts (want to get the PID of a daemonized process? PID files, except that now you can have racing conditions and possible problems with locking). I recently migrated a script init-style startup file (used by a thin systemd service) to a native systemd service in my current work. Nobody understood the script file very well, while the .service native systemd file is much simpler and obvious about what is doing. > All of this adds up to a storm of controversy that the systemd people mostly brought upon themselves. Had they just been more humble about their creation and waited until it was mature and well-tested and did all the wonderful things they claim it could and should do instead of stuffing what was widely seen as a broken-by-design piece of garbage down everybody's throat, maybe much of the Linux community wouldn't have been nearly so outraged by it. Using words like "broken-by-design" without given reasonable arguments will only make your argument less convincing, you know? [1]: https://en.wikipedia.org/wiki/Systemd https://en.wikipedia.org/wiki/Systemd [2]: https://en.wikipedia.org/wiki/Upstart https://en.wikipedia.org/wiki/Upstart
- how_gauche 9y ago> instead of stuffing what was widely seen as a broken-by-design piece of garbage down everybody's throat Here's the thing I don't understand. I don't want to get too deep into my bona fides, but I'm a "real professional" who's been in this industry twenty years now. I've been running Linux since it came on a stack of floppy disks. I've managed clusters of Sun machines, I've worked end-user IT support, I've deployed BSD on routers, I've carried the pager at Google, I've spent years and years at small startups writing the code, crimping cables, wiring racks, deploying the code, waking up at 3am when the code breaks. So when I read an opinion like this, the only conclusion I can draw is these people are out to lunch, because to me it's clear that the systemd suite is so much better than the steaming pile it's replacing. The tools are consistent, composable, well documented, and fast. Binary logging is superior in every way (checksums, log shipping, metadata, search). It's got amazing sandboxing support right out of the box and makes it easy to configure (PrivateTmp, PrivateDevices, PrivateUsers, ProtectSystem, CapabilityBoundingSet, SystemCallFilter, NoNewPrivileges, MemoryDenyWrite, etc). It gives you fine-grained control over cpu scheduling and limits. It doesn't litter .pid and .lock files all over your system because the shitty bash script couldn't figure out the daemon died. The systemd-nspawn tool is chroot, but done correctly this time. Socket activation is totally awesome. Love user sessions -- systemd starts my emacs daemon and mail fetcher for me when I log in, sends their log output to the journal like every other service, and restarts them when they fall over. I chafe when I have to login to an older CentOS or Ubuntu system that doesn't have it. TL;DR: smells like Dunning-Krueger to me
- darksim905 9y agoAs someone who is a heavy Windows user, this whole thing confuses me. Someone comes along, similar to Stallman who embraces Linux in the truest form: they build something for you. It has faults. It may not be great, but it does some things well. And somehow, it creeps over & takes over. On more than one comment here, people complained about how fast systemd (not systemD) took over -- and yet, is that the author (Pottering or whatever?) fault? I think not -- this is your fault. Your friends. Mine. My friends. The random dev in the corner who found it useful & uses it & realizes the potential. I'd be curious to see what the Amazons, WalMarts & other large ''small service Linux-y thingy'' do to get so big & scale so fast: are they not essentially using CoreOS, many containers & making use of systemd to the fullest extent possible? I just don't get it. Linux is all about choice (and yet nobody realizes too much choice is bad - just look at all the distros you have). Someone fixes it all for you & you get upset. Someone takes power away from Sysadmins & shifts it just a little more to Devs because they can't get work done. You get upset (I am admittedly in that camp) but, from the people that I hear good things about systemd, I hear great* things that convince me it's wonderful. The bad camp can't say the same thing on the same scale: it's just blame & resentment & frustration because they can't articulate what they don't like about it other than "It isn't the Linux way!!11Oneoneon1on1!! M$"
- viraptor 9y ago> is that the author (Pottering or whatever?) fault? Yes, he's got technically good ideas, but not a great experience with either security or large systems. He's also terrible at receiving critical feedback which makes this unlikely to change. Some people chose systemd for the positive technical merits and others disagree. But just because his ideas got popular, it doesn't make him right and without blame for other behaviour. We have enough bad, popular leaders recently. Ideally, I'd like systemd with each project split out with separate leadership and without Pottering. Nobody getting a pwnie award should be a leader of a large project.