Stories
Slash Boxes
Comments

SoylentNews is people

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

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.
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:27PM

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

    can't imagine servers would have a big dependency on systemd... most debian servers would be better off sticking with tried and trusted sysvinit

    gnome doesn't really have any business being on a server

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

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

    GNOME 3 doesn't really even have much business being on a workstation.

  • (Score: 0) by Anonymous Coward on Sunday September 28 2014, @02:38PM

    by Anonymous Coward on Sunday September 28 2014, @02:38PM (#99217)

    can't imagine servers would have a big dependency on systemd...

    Err, systemd logind and systemd networkd for starters and of course they have their own (much maligned) journald and are about to add dhcp and ntp daemons. If only there were a light weight alternative that started processes and kept itself the hell off the rest of the system. We could call it 'initd'.