Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
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: 1) by Fauxlosopher on Thursday November 20 2014, @08:38AM

    by Fauxlosopher (4804) on Thursday November 20 2014, @08:38AM (#118045) Journal

    I agree that systemd is the problem, and that up until recently, Debian worked just fine. (Slackware and Debian are the two distros I've chosen to use most often.)

    The progression of events, including this most recent vote, appear to suggest that those who are actually holding Debian's reins do not agree with us, and that they desire that systemd be included in Debian going forward. The risk that I and others see is that systemd will soon cease to be an option, and will become mandatory. Combined with questionable-at-best design decisions such as binary logs, the justification offered to replace the entire init system is completely farsical. First-time init script setup admittedly can be a bit crufty in certain situations, but in those same situations, almost the entirety of the initial system configuration could be considered crufty - for that reason, others hire people like myself to take care of those systems for them, and for anyone with a modicum of familirarity with Linux basics, init script customization is so far down the list of annoyances as to not even register on the radar.

    To administrative "end users" like myself, systemd came out of nowhere to solve a problem that didn't exist and also created tremendous uncertainty in the process.

    Thus, the only obvious solution for those in my situation is to jettison Debian now, and focus on traditionalist Linux distributions... and/or investigate the BSDs.