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 HiThere on Thursday November 20 2014, @08:01PM

    by HiThere (866) Subscriber Badge on Thursday November 20 2014, @08:01PM (#118225) Journal

    OK. But I have one system, so it's both a desktop and a server. Until I'm assured that systemd won't cause problems, I'm just going to avoid it, and everything linked to it. Since my system *is* a desktop as well as a server, well...

    The question, really, is "Is systemd actually a desirable way to go?". I haven't encountered anything that makes me say yes, so I don't want to commit to it. Particularly as it seems to be an increasingly intrusive and entangling system. I don't mind building things from source, though. (Well, most things.) If I must, I can cut my main system off from the internet and communicate intermittently through a laptop, but that would be much less desirable than finding some better way. But stable is good enough, so there's no hurry. And maybe I'll even be convinced that its a good idea.

    --
    Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by Marand on Thursday November 20 2014, @09:59PM

    by Marand (1081) on Thursday November 20 2014, @09:59PM (#118264) Journal

    Yeah, I totally get that. I use a VPS for stuff I need up reliably, and for home stuff it doesn't matter much if I mix desktop+server bits because if the desktop is down I've got bigger concerns than worrying about mpd or my LAN-only httpd not running. I can afford to experiment a bit. Though I still refuse to let systemd become init, and I'm going to continue to refuse to do that for as long as possible.

    I don't necessarily think systemd's a great way to go, but neither was HAL, which is why it ended up superseded eventually. Meanwhile I'm just going to hold out as long as possible using sysv init, and if I start having issues with the non-init side of systemd (right now the only part that seems to run is logind, so the annoyance is minimal) I'll just throw it out and deal with clunkier USB storage mounting.

    Either way -- sticking with stable or using shim -- the idea's same. The situation isn't exactly dire yet, so it's a bit premature to be freaking out and switching to BSD. By the time it gets to that point, the entire landscape could change again. That's what happened not long after I finally got forced into using HAL. "Damn I'm stuck with it now. Oh look it's deprecated, yay" :)