SoylentNews

Debian General Resolution to Prevent Init System Coupling Fails to Pass

posted by janrinok on Wednesday November 19 2014, @11:25AM   
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"

• Re:Interesting split of the anti-vote (Score: 2) by cafebabe on Thursday November 20 2014, @03:57AM

  by cafebabe (894) on Thursday November 20 2014, @03:57AM (#117985) Journal

  You do one thing and do it well, because it's possible to verify a simple tool with a clearly defined role actually does what it's supposed to do, and not more, and doing that is the key to keeping a sane system that works as it should.

  As fairly well defined and protocol specific examples, some of problems in bind and Apache httpd have occurred due to the conflated role of serving authoritative data and caching data from other servers. Neither of these implementations are doing one thing well.

  --
  1702845791×2

  Parent

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