Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Posted Nov 15, 2019 16:27 UTC (Fri) by mirabilos (subscriber, #84359)Parent article: Debian reconsiders init-system diversity
1. elogind is not new, it’s been there since before buster *and* is included in the buster release, but the other packages that had a hard dependency on it need to adjust their Depends. (I’ve done this successfully on a buster system by editing two lines in /var/lib/dpkg/status to the effect that even network-manager works.) It’s been usable as-is for some time already, just the “can substitute for systemd” part is new (and almost solved in unstable for a while).
2. “merging” is completely the wrong phrasing. elogind is an alternative, and it must be installed by hand and does not affect the default systemd configuration.
This directly bleeds over into…
3. Md is telling nonsense as usual: the new installations use systemd *because* there are dependencies on it from certain packages many people install. People did not have the *option* to use elogind without going through extreme hoops until very recently in unstable (and even then, switching is… interesting). So the statistics are utterly skewed.
Posted Nov 15, 2019 17:25 UTC (Fri)
by smurf (subscriber, #17840)
[Link] (2 responses)
Posted Nov 15, 2019 21:58 UTC (Fri)
by mirabilos (subscriber, #84359)
[Link] (1 responses)
And hmm yes, that was, in reflection, badly worded. Sorry about that.
Posted Nov 16, 2019 7:12 UTC (Sat)
by smurf (subscriber, #17840)
[Link]
Posted Nov 17, 2019 12:45 UTC (Sun)
by lobachevsky (subscriber, #121871)
[Link]
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity
Debian reconsiders init-system diversity