Stories
Slash Boxes
Comments

SoylentNews is people

Rumblings of a Debian Fork Amidst Anger Over systemd

posted by n1 on Sunday September 28 2014, @06:27AM   Printer-friendly
from the yet-another-systemd-story dept.

An Anonymous Coward writes:

Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.

Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.

 
This discussion has been archived. No new comments can be posted.
Rumblings of a Debian Fork Amidst Anger Over systemd | Log In/Create an Account | Top | 141 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: 0) by Anonymous Coward on Sunday September 28 2014, @12:00PM

    by Anonymous Coward on Sunday September 28 2014, @12:00PM (#99164)

    Luckily a reboot for servers is a rare occaision (one would hope).

    Even on a rolling release distro like arch, It used to be kernel upgrades only. I could skip minor kernel releases for months unless I knew there was an issue. Now with systemd, there's so many packages not to be upgraded that it's impossible to keep track of what exactly is going on. Basically, I wait until I start seeing weird log messages about missing PAM modules and the like. Wait until I'm next on site (because if something goes wrong with pid 1...) and reboot then. For offshore cloud based servers, I run a backup and cross my fingers before rebooting.

    Systemd -- the spanner in the works.

  • (Score: 1, Informative) by Anonymous Coward on Sunday September 28 2014, @12:34PM

    by Anonymous Coward on Sunday September 28 2014, @12:34PM (#99183)

    Jesus Christ. Are these log messages about missing PAM modules showing up in systemd's binary logs? As an AIX admin, all of this stupidity from the systemd crowd really blows my mind. The fact that their software can fuck up PAM while logging about it to an unreadable binary log file is just astoundingly dumb.