5 ms·
I was averse to systemd initially, and held on to my legacy init for as long as I could until my distro totally switched over and just stopped supporting the le
by bee_rider 4y ago
I was averse to systemd initially, and held on to my legacy init for as long as I could until my distro totally switched over and just stopped supporting the legacy stuff.
At that point, I realized I don't actually want to manage an init system. Which further lead me to the realization that I wasn't actually working with the thing very often, and brought into question my qualifications for having strong opinions on the topic.
I see lots of arguments against systemd that, to my untrained eyeball, seem pretty compelling, and lots of groups who are doing the actual, non-hypothetical work who seem to've ignored the arguments and switched over.
- irthomasthomas 4y agoI use and develop on devuan. I can't see any reason to add systemD, a so-called init system that uses binaries and extends it's tenticals in to every part of the OS. You aren't running linux anymore, you are running systemD. It is an abomination, and I will never adopt it.
- kaba0 4y agoYou didn’t mention any single factual reason to not adapt it. Isn’t the usual unix tools just little binaries? Also, IPC can very easily bloat the problem domain to much harder levels because now you have to deal with (de)serialization as well. So doing the same thing what systemd does with pipes would be an unholy mess.
- irthomasthomas 4y agoI mentioned two, the binaries and the long tentacles. To be clear, I was talking about systemd using binaries in place of plain text LOG files. Both those choices are a huge break from linux philosophy. I expected systemd pros would know I was talking about that. Enjoy your systemd. But don't hate on me for prefering linux.
- kaba0 4y agoWhat are long tentacles? As for log files, I don’t see how is it different than a pdf or any other standard.
- irthomasthomas 4y agoSystemd has extended its reach far beyond that of an init system. Long tentacles. Hence I say you are using systemd, not linux.
- growse 4y ago> Systemd has extended its reach far beyond that of an init system. Long tentacles. Hence I say you are using systemd, not linux. You could make the same argument about KDE, or Gnome. It's not a good one. Systemd isn't trying to be just "an init system". You know Linux is just a kernel, right (now's the time for that copypasta I think)?
- gnulinux 4y ago"Abomination" is not a good enough argument. Systemd is very useful, and in order for someone to convince me not to use it, I need to see a good argument against it. "It's too big, it's an abomination" don't have clear technical implications, therefore don't make good technical arguments.
- irthomasthomas 4y agoI didn't tell you not to use. I said I don't see any reason for me to use it. I prefer the simplicity of text based LOG files over binary files requiring that you use the systemd API that was changing regularly the last time I touched it.
- growse 4y ago> I didn't tell you not to use. I said I don't see any reason for me to use it. I prefer the simplicity of text based LOG files over binary files requiring that you use the systemd API that was changing regularly the last time I touched it. Modern syslog implementations (e.g. rsyslog) will write journald log events in plaintext, if you're desperate to have plain-text-on-disk.
- bee_rider 4y agoThe reason to "add" systemD is that most of the major distros use it anyway, and so to avoid it I'd have to specifically go out of my way to find one like devuan.
- eternityforest 4y agoMost of the arguments are theoretical or probabilistic. It's true that more code means more places for bugs to hide. It's also true that systemd and it's fans(myself included) don't really care about init freedom. Obviously, no self respecting FOSSer is going to sabotage alternatives actively, but we don't use or know the alternatives, so there could be subtle bugs. But systemd does work. It's not what I would call buggy. It doesn't appear to impede performance. And very consistently, whenever I think "Oh, how do I do X", there's a clean and purely declarative way to do it, that hooks into all the logging and monitoring perfectly. Systemd goes a long way to making Linux work like an OS, rather than a build-an-os kit. The people who are against it tend to be very security conscious. Not "I use 2FA" conscious, but "I will wholesale refuse to visit a popular site that I believe is selling my telemetry data" level. A lot of the others are enthusiasts. They want to control and understand the machines they own, and don't want any black boxes, and they are almost as grossed out by anything "overkill" as most people are by a drawer of urine. They don't care if it's tucked away, they don't like it being there and don't trust it, no matter how well it performs who who did a 3rd party audit. Systemd seems highly inappropriate for people who really like the old Linux modular kit approach, or anyone who doesn't like big things. But the majority of big corporate and average home users seem to love it, and I wouldn't want a distro without it. The arguments against it are valid, but usually only if you share the same values they tend to be based on.
- cykros 4y agoIt's existence as an alternative for those who want it doesn't bother me so much. It's watching other projects that existed for years without relying on it tacking it on as a dependency that got worrisome. It DOESN'T particularly follow the Unix philosophy, but that's okay -- not everything needs to be Unix. At the end of the day, things seem to have washed out over the past few years, and folks who want to run systems without it seem relatively unimpeded at this point (heck, my Bluetooth stack on Slackware 15 worked out of the box). As long as the anti-systemd crowd keeps things constructive with parallel structures, the future seems bright. And if the systemd proliferation brings users and thus big company driver support, so much the better. I just hope it is done in a way that the benefits can be shared in an init-system agnostic sort of way where possible.