SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.
SoylentNews
posted by
janrinok
on Wednesday November 19 2014, @11:25AM
from the I-hope-we-don't-regret-this dept.
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.
Debian General Resolution to Prevent Init System Coupling Fails to Pass
|
Log In/Create an Account
| Top
| 179 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Celebrate Hannibal Day this year. Take an elephant to lunch.
(Score: 2) by canopic jug on Wednesday November 19 2014, @02:12PM
On the server side of things, you still have Debian/kFreeBSD. You wouldn't have many changes to migrate to that. However, for the desktop/notebook or embedded systems you are SOL unless FreeBSD supports your hardware, either raw FreeBSD or processed as Debian/kFreeBSD or PC-BSD. OpenBSD is another option, for some hardware, but because of the tight support lifecycle, you would be looking at upgrades/reinstalls every year.
Money is not free speech. Elections should not be auctions.
(Score: 0) by Anonymous Coward on Wednesday November 19 2014, @03:18PM
There was a submission here a few weeks ago about how kFreeBSD will likely be ended soon, thanks to systemd.