Re:Systemd, ten years later: a historical and technical retr...
by JdeBP on Sunday May 17, 2020 @04:20AM
(#23210550)
The person who wrote the headlined article also wrote commentary back in 2014 on discussions of systemd, which highlighted the false dichotomy that people propound that the decision is between van Smoorenburg init+rc and systemd. You are doing that very thing, years later.
That was never the case, especially so for Debian that you mention. In the Debian Hoo-Hah, the choices were van Smoorenburg init+rc, OpenRC, Upstart and systemd; the latter three being the main contenders, as was acknowledged partway through the affair. In Fedora and Ubuntu, the choice was between Upstart and systemd, Upstart having been what they used for some years before systemd.
* https://web.archive.org/web/20141222234706/http://uselessd.d...
Re:Systemd, ten years later: a historical and technical retr...
by rezonant on Saturday May 16, 2020 @07:25PM
(#23208058)
I do want to say that despite my comment here, seems like projects like Devuan, Void, and Arch are doing OK with this, in concert with projects like elogind and eudev etc that forego systemd while providing compatible replacements.
Re:Systemd, ten years later: a historical and technical retr...
by martinflack on Sunday May 17, 2020 @03:11PM
(#23214452)
> Debian found itself in a position where the amount of work to sustain a non-systemd path in a systemd-dominated ecosystem would be too much work _for them_
Just as a side note for the interested, there is a project named Devuan that launched to keep alive a Debian sans systemd.
(I've never run it myself; I just happen to know it exists.)
That being said, SysV init is (in fact) terrible. I'd say put the effort into something that can supercede systemd some day. That part of the problem is tractable, though success is quite a long-shot given its entrenchment.