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: 2) by cafebabe on Wednesday November 19 2014, @07:53PM
That irritates me too. I wish that -R and only -R was recurse. I think the most annoying examples are within the suite of aircrack-ng utilities. Even the second generation of a bunch of commands released together don't use consistent parameter conventions. However, if I make the comparison with GUI software, menu shortcuts (such as Alt-H for Help) are equally inconsistent.
I assume your background is weighted towards Windows or MacOS. All I see is technical debt [soylentnews.org], Not Invented Here [soylentnews.org], "WTF is RFC5452? [soylentnews.org]" and "Do you hate [google.com] disabled people? [youtube.com]"
Computer pioneers usually had a mathematical background, so stuff like y=f(g(h(x))) was bandied around without having to consider implementation details such as exception processing. However, when foo | bar | baz is stateful or starts spewing garbage, it falls outside of this mathematical paradise.
We just cannot determine what it will be yet and that alone makes it unsuitable for deployment on stable systems. Regardless, deployments will be cracked. Repeatedly. This isn't an academic issue or an opportunity for schadenfreude. Some of those systems may contain my private information and your private information.
1702845791×2