6 ms·
Man, I feel like the Linux world is moving to systemd but this whole process has been like pulling teeth. I'm totally unaffected by this but even I'm feeling wo
by arcticbull 7y ago
Man, I feel like the Linux world is moving to systemd but this whole process has been like pulling teeth. I'm totally unaffected by this but even I'm feeling worn out on it. Feels like brexit, honestly -- nobody's enthusiastic about either systemd or sysv init, ok, fine, its happening but... ugh.
- jakeogh 7y agoThe real mistake is having the arg in the first place. https://news.ycombinator.com/item?id=21842994 https://news.ycombinator.com/item?id=21842994
- ernst_klim 7y ago> nobody's enthusiastic The vast majority of people are fine with it, it's just the loud minority opposes it. The bulk of linux userbase is systemd only: Centos, Ubuntu, Arch, Opensuse, Fedora. I think these 5 have already 90+% of installations.
- kijin 7y agoFine doesn't mean enthusiastic. Most people are just going along with the trend with no strong preference either way. I'm actually quite fond of systemd now that I'm used to it, but I wouldn't have "moved" to systemd if it wasn't for the major distros making the choice for me.
- oaiey 7y agoAre not the distros who design the composition of the actual overall system the exact right people to make this call? In an ideal world (and by your comment I assume you are close to it) you do not care or maybe even realize which startup system the system utilizes.
- int_19h 7y agoThat is only true for a casual user's desktop, maybe. If you're a power user or a server admin, you will likely be setting up services, or diagnosing their failures, at some point - and then the features and the ergonomics of the init system are very relevant.
- oaiey 7y agoTrue, the server admins are indeed seeing systemd, however they choose the distribution before.
- thayne 7y agoI suspect most people don't really care. People who are enthusiastic are the ones driving the move to systemd. People who hate it, complain about it.
- usr1106 7y agoDebian has certainly more than 10%. Especially in small server space or embedded Linux many just install Debian because its a simple and stable option. That does not change your point about systemd adoption. Debian has been in practice systemd only for how many years?
- PopeDotNinja 7y ago> Debian has certainly more than 10% And way more than 10% if we consider that Ubuntu is built on Debian.
- asdfaoeu 7y agoUbuntu doesn't have sysvinit so isn't relevant here.
- the_why_of_y 7y agoDebian has not in fact been systemd only; the GR that is being discussed in this thread replaces a decision by the Technical Committee from 2014: https://lists.debian.org/debian-devel-announce/2014/08/msg00001.html https://lists.debian.org/debian-devel-announce/2014/08/msg00... For the record, the TC expects maintainers to continue to support the multiple available init systems in Debian. That includes merging reasonable contributions, and not reverting existing support without a compelling reason. However, in practice Debian users tend not to replace systemd's PID1 with the sysvinit-core package, as it is installed on a negligible fraction of Debian systems. https://qa.debian.org/popcon-graph.php?packages=systemd%2C+sysvinit-core&show_installed=on&show_vote=on&show_old=on&show_recent=on&show_nofiles=on&want_percent=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 https://qa.debian.org/popcon-graph.php?packages=systemd%2C+s...
- Karunamon 7y agoI'm not sure you can rely on popcon to make decisions like that.. anyone who doesn't explicitly opt in, and anyone who installs on a system with limited internet access (i.e. probably most enterprise users) won't be counted.
- ckastner 7y ago> The vast majority of people are fine with it Exactly. As confirmed by this vote.
- krzyk 7y agosystemd looks like it was forced somehow on distros. I was happy with sysvinit, no issues with it as a simple user on laptop. But now I have issues with systemd once a month, I really hate that thing and don't see any benefits.
- majewsky 7y ago> systemd looks like it was forced somehow on distros. Distros adopted systemd because it solves a huge waste of time that distributors have to deal with: maintaining init scripts. systemd unit files are distro-agnostic and can thus be maintained upstream. (There's also other useless idiosyncrasies that systemd plowed over, so there's even less work for distributors to do. Or rather, more time to do actually interesting work to differentiate their distribution.)
- despera 7y agoPackage maintainers have far, far worse problems to deal with than some shell scripts that are trivial most of the time for alternative init systems like openRC. Also, hopefully, no maintainer in his (security-wise) right mind use upstream provided system files as-is.
- gizmo686 7y agoThey are changing a core component of a piece of infrastructure used by a large a diverse set of people for a (relatively) diverse set of usecases; and said infrastructure has central governing body; while many of the big players have a public decision making process. Sure, bazaars are nice, but times like this really make me appreciate cathedrals.
- kick 7y agoThere are better init systems than both of those. runit is one of them, daemontools is another. NB. runit is a daemontools clone that isn't written by Bernstein.
- mixmastamyk 7y agoI like many of the bernstein tools, but daemontools is not one of them.
- kick 7y agoWhy not? It's simple, it's efficient, and it gets out of your way.
- mixmastamyk 7y agoBeen five years so hard to remember, but something about restarting daemon was a chore and strange datetime format in logs left a bad taste.
- hvdijk 7y agodaemontools does not support "start service B once service A is up and running", it can only do "start service A before starting service B". For services that take a while after starting before they are ready, such as databases, that can be a problem. Traditional sh init scripts were able to handle this as most such services could fork and exit once they were ready, but fork and exit is incompatible with daemontools. Some daemontools clones have ways to handle this, but IIRC daemontools itself does not.
- filterfish 7y agonosh being one of those.
- cpach 7y agoRunit seems interesting. Feel free to expand regarding it’s benefits compared to systemd! The main selling point seems to to be less complexity. Are there any drawbacks/gotchas one should be aware of?
- jsolson 7y agoI'm also mostly disconnected from this, which honestly makes me a fan of systemd. Today (literally) I wanted to launch Xilinx hw_server as a daemon that my peers could restart if it broke itself (it's... prone to doing so). While I could write an init script that knew about PID files, creating a systemd unit was _vastly_ easier. Yeah, it's not Unix, but UNIX is also sort of terrible for anything that's not a one-shot, no?
- jankotek 7y agoSome people love systemd. Finally you can reliably manage system daemons, WinNT had this 20 years ago.
- JdeBP 7y agoUnix had it in 1988, before Windows NT existed. (-: * http://jdebp.uk./FGA/unix-service-access-facility.html http://jdebp.uk./FGA/unix-service-access-facility.html
- ThrowawayR2 7y agoDoesn't really count if it never made it to any of the mainstream UNIX implementations; your own citation notes that it's a forgotten technology. Linux certainly never had it at any point in the past.
- JdeBP 7y agoIt's a good thing that it made it to AT&T Unix System 5 Release 4, then, so that it really counts.
- gwd 7y agoThe real problem I have with systemd isn't the technology itself, as much as the attitude of the people who run it. Off the top of my head, issues I've seen with systemd: * At some point there was no way to say, "bring up this service once the network is up". I mean, there was technically a "network" target, but it considered "localhost" as a network. So if, say, you have automounted NFS, the automounter starts running before your main interface has DHCP. This setup been a widely-used configuration for decades; the systemd maintainers didn't care. * At some point, if you typed "reboot ; exit" in an ssh session, the "reboot" would hard-kill your ssh session and your shell before the "exit" would be run; so your ssh connection would then hang until the machine came up again and refused a TCP resend request. * The whole thing with systemd reading the kernel's command-line, deciding that "debug" was meant for it, and spamming the logs making it completely unable to boot; and forcing the kernel to introduce a work-around to hide "debug" from systemd. * The whole interface renaming thing that's happening in Debian now; every time our project has upgraded our test systems from jessie to stretch, and then stretch to buster, we've had to spend dozens of man-hours figuring out why our network configurations aren't working. The problem here isn't so much that there are these sorts of bugs; the problem is that there seems to be an attitude of, "Well my set-up works; yours doesn't matter." That's not the attitude such a core piece of infrastructure should have. Compare this to Linus' nearly fanatical insistence that things in userspace should continue to work. If Lennart Pottering had the same attitude towards breaking existing systems that Linus has, systemd would probably be incredibly popular.
- thawaway1837 7y agoThe first few points you mention appear to be fixed. That doesn’t seem to align with the idea that the maintainers don’t care.
- Boulth 7y ago> forcing the kernel to introduce a work-around to hide "debug" from systemd. I thought the workaround patch was not merged?
- JoshTriplett 7y ago
- blihp 7y agoMoved... past tense. The bulk of distros completed the move a while ago. Sure, systemd has it's issues (notably scope creep) but for most use cases it is arguably an improvement.
- superkuh 7y agoThe problem isn't so much systemd as an init system as systemd as an everything system. I gave an all-in systemd distro a try this year but quickly went back to something more relaxed after realizing just how bad systemd timers are compared to crontab. It takes writing two 15 line config files and then a long system call to get it to reload the config. It'd be fine for just init but as it swallows more system processes it gets unweildly fast.
- SahAssar 7y agoOn the other hand systemd timers are a lot more powerful with stuff like RandomizedDelaySec and WakeSystem. They can also depend on other units, so that a timer only fires if the system has certain services/devices/mounts/whatever.
- despera 7y agoWell "the world", whoever is part of that set, can move wherever wants to. The problem is that in the name of a forced unification that supposedly will do a greater good for the great scheme "linux on desktop" many from that "world" are really into scorched-earth tactics. There is absolutely no technical reason why different worlds cannot coexist, at least in our case.