Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 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: 2) by arashi no garou on Wednesday November 19 2014, @07:32PM

    by arashi no garou (2796) on Wednesday November 19 2014, @07:32PM (#117814)

    I wholeheartedly second this. Slackware takes getting used to as there is zero dependency resolution, but (at least for me) that's a blessing in disguise as for one thing, I only end up with the packages I truly need, and two, I've learned a ton over the years about how GNU/Linux really works under the hood thanks to it. I've taken what I learned exploring Slackware and applied it to other distros like Arch and Debian, to fix issues there that would otherwise have required a lot of search-and-try sessions.

    As for installing software and libraries, you have the choice of using Slackware binary packages, rolling your own packages via Slackbuilds (highly recommended, and can be semi-automated via sbopkg), using a third party package manager like slapt-get which emulates Debian's apt system, or building and installing from source (also highly recommended, especially if you are interested in tweaking or patching the code before compiling/installing, or if there isn't an existing Slackbuild for that program).

    I don't know if Slackware will ever cave to the systemd cabal, but I highly doubt it. And if they ever do, well you can take a lot of what you learn in Slackware and apply it to LFS, Gentoo, and *BSD.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Arik on Wednesday November 19 2014, @07:52PM

    by Arik (4543) on Wednesday November 19 2014, @07:52PM (#117823) Journal
    It is a blessing, and I never thought it was in disguise. When I first heard about the .deb concept my reaction was 'that actually sounds like a rather bad idea' and while I respect Debian and have used it on occasion where it was a good fit for the job, I still think all the automagical package stuff is a misfeature. Debs arent as brittle as RPMs in practice but the whole system is just a mass of unnecessary complexity to solve 'problems' that have never bothered me.

    I also agree it seems highly unlike Mr Volkerding will ever package systemd. He was way ahead of the crowd in saying no to GNOME and PAM and we thank him for it.
    --
    If laughter is the best medicine, who are the best doctors?