Slash Boxes

SoylentNews is people

posted by janrinok on Wednesday November 19 2014, @11:25AM   Printer-friendly
from the I-hope-we-don't-regret-this dept.

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"

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by cafebabe on Wednesday November 19 2014, @07:53PM

    by cafebabe (894) on Wednesday November 19 2014, @07:53PM (#117824) Journal

    For example in one program 's' may mean recurse sub-directories and 'r' means turn the text red. Then in the next program 'r' means recurse and s means something totally different unless you use capital S.

    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.

    Stuff like systemd I can see *why* they did it.

    I assume your background is weighted towards Windows or MacOS. All I see is technical debt [], Not Invented Here [], "WTF is RFC5452? []" and "Do you hate [] disabled people? []"

    Yet the chaining of events creates a giant storm of bad in/bad out sometimes.

    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.

    It will be 10 years before whatever systemd ends up being, that it finally calms down and people undo the damage and creates a decent consistent startup/service interface out of it.

    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.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2