Stories
Slash Boxes
Comments

SoylentNews is people

Debian General Resolution to Prevent Init System Coupling Fails to Pass

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

novak writes:

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.
Debian General Resolution to Prevent Init System Coupling Fails to Pass | Log In/Create an Account | Top | 179 comments | Search Discussion
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 cockroach on Wednesday November 19 2014, @12:00PM

    by cockroach (2266) on Wednesday November 19 2014, @12:00PM (#117599)

    Gah, HTML fail. Sorry 'bout that.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 3, Funny) by Konomi on Wednesday November 19 2014, @12:05PM

    by Konomi (189) on Wednesday November 19 2014, @12:05PM (#117601)

    We have forever immortalised your mistake on the Internet *evil laugh*.

  • (Score: 2) by The Mighty Buzzard on Wednesday November 19 2014, @12:06PM

    by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Wednesday November 19 2014, @12:06PM (#117602) Homepage Journal

    Heh, yeah. <blockquote> or <quote> are I think what you were going for. We pondered <q> as well but it's apparently part of the html spec and used for in-sentence quoting.

    --
    My rights don't end where your fear begins.

    • (Score: 2) by cockroach on Wednesday November 19 2014, @12:08PM

      by cockroach (2266) on Wednesday November 19 2014, @12:08PM (#117603)

      Heh yep, I must be spending too much time on bad forums. I hereby promise to henceforth always use the preview button.

    • (Score: 0) by Anonymous Coward on Wednesday November 19 2014, @02:22PM

      by Anonymous Coward on Wednesday November 19 2014, @02:22PM (#117667)

      Not to sound like a stupid n00b but is there an easy way to escape the angle brackets and HTML tags on SN? I can use the escape codes but they are turned into their respective characters after a preview and will not render come the next preview or posting.

      I would like to request that the Soylent dev team change the parser for the Comment box to eliminate the substitution of characters for their escape codes after a preview. We can then see the expected characters in the preview window and make the corrections in the text field. To me, the rendering of an escape code in the input field after a preview is an annoying bug. I have to edit the post off-line to preserve the escape codes and copy-paste to keep things sane.

      • (Score: 2) by The Mighty Buzzard on Wednesday November 19 2014, @02:30PM

        by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Wednesday November 19 2014, @02:30PM (#117674) Homepage Journal

        &lt;foo&gt; should be what you're looking for, for now. This behavior will be the default and not screw up (it does right now) when you hit preview with the 14.12 update most likely though. Been doing a lot of work on removing filtering of user input and only and properly filtering output.

        --
        My rights don't end where your fear begins.