Ian Jackson's general resolution to prevent init system coupling has failed to pass, the majority vote deciding that the resolution is unnecessary. This means that not only will Debian's default init be systemd, but packages will not be required to support other init systems. Presumably, this means that using other init systems on Debian (without using systemd as a base) will not be possible without major workarounds, or possibly at all. It also leaves the future of Debian projects such as kFreeBSD unclear, as systemd is linux specific.
The vote results can be found here
The winners are:
Option 4 "General Resolution is not required"
(Score: 3, Informative) by cafebabe on Wednesday November 19 2014, @12:54PM
In a month when two decade old bugs were found in Windows and bash, you'd expect people to have enough foresight to see that they'll be finding systmemd security [seclists.org] flaws [seclists.org] for the next two decades. Not using symlinks, shell scripts and/or globbing to boot a system does not change the fact that symlinks, shell scripts and globbing still exists [soylentnews.org] but is certainly a method to introduce new problems. Specifically, reducing boot time by a faction of a second has caused considerable reduction in reliability and security and has greatly increased the coupling of components. However, anyone who notes this supposedly hates [google.com] disabled people [youtube.com].
1702845791×2