3 ms·
I feel like the anti-systemd folks are just helping systemd by portraying the only two choices as systemd and classic init. It used to be the consensus that the
by geofft 9y ago
I feel like the anti-systemd folks are just helping systemd by portraying the only two choices as systemd and classic init. It used to be the consensus that there were real problems solved by non-classic init systems, of which there were several decent options, systemd being the most popular but also the most controversial. I think there are serious problems with systemd and I want a decent featureful init / boot-ordering system, but given the choice between classic init and systemd I'd definitely pick systemd.
As an example of the most basic improvements over classic init, here's a paper from 2001 from OpenBSD about dependency-based init with no runlevels: https://www.usenix.org/legacy/event/usenix01/freenix01/full_papers/mewburn/mewburn_html/ https://www.usenix.org/legacy/event/usenix01/freenix01/full_...
Since this is Debian-based, does "classic init" in this context mean they're using insserv? That's definitely not "classic," but it's definitely a better option IMO. If so, are they interested in helping out with maintaining insserv in Debian? It hasn't seen a maintainer upload for almost five years, and help is requested: https://bugs.debian.org/834284 https://bugs.debian.org/834284
- _jal 9y agoI don't know who the "anti-systemd folks" you're talking to are, but I haven't seen that. I see several different projects using several different inits, including, yes, "classic init". The only folks I hear talking about One True Init (which will also take over completely unrelated functions, poorly) are the systemd folks. Also, it sounds like you're unaware of the distinction, but the BSDs have never had sysvinit-style runlevels. You can kinda hack them in if you like, but there's no native notion of runlevel; you get single-user or multi-user.
- ginreaper 9y agoI think the biggest issue of SystemD was not only the controversial development process, but the dependencies of other projects like udev into SystemD's repo and packaging.
- digi_owl 9y agoBingo. Rarely if ever have i seen someone considered anti-systemd as being pro-sysv. What they are pro however is init diversity. With sysv, it was relatively easy to slot in a different init as the admin wanted. A distro i have used for some time, Gobolinux, may use the sysv init binary for example. But it forgoes the usual sysv layout for one more akin to just a rc.local. But with systemd it is systemd, and only systemd, because systemd is so "invasive". And the real worry is when third party developers assume systemd as the default and make it hard, or resist, supporting alternatives.