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: 1, Interesting) by Anonymous Coward on Sunday September 28 2014, @07:11AM

    by Anonymous Coward on Sunday September 28 2014, @07:11AM (#99098)

    Today It's impossible to have a reasonable laptop experience in Debian without systemed; being reasonable the same as a year ago: suspend/hibernate working, and network management just working.

    Now, for wifi, Systemd is a necessary dependency of plasma-nm, so I'm stuck with cnetworkmanager, and that of suspending stopped working stopped working.

    Taking that into account, and the future KDM dependence on logind, points my computers future possibly on lumina.

    Which is sad, given that I'm one of the KDE translators (to galician)

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Total Score:   1  

  • (Score: 2) by Marand on Sunday September 28 2014, @10:54AM

    by Marand (1081) on Sunday September 28 2014, @10:54AM (#99143) Journal

    Now, for wifi, Systemd is a necessary dependency of plasma-nm, so I'm stuck with cnetworkmanager, and that of suspending stopped working stopped working.

    Switch to wicd instead of networkmanager. You'll be happier long-term: in addition to not having insane dependencies, it's a lot less fussy and not prone to random breakage like NM has been in the past. I found wicd to be far more reliable on my laptop, as well as just nicer to use overall.

    Only (potential) negative I can think of offhand is that the GUI bits aren't as fancy as the NM ones, but that could just as easily be considered a pro instead of a con.

    • (Score: 0) by Anonymous Coward on Sunday September 28 2014, @11:21AM

      by Anonymous Coward on Sunday September 28 2014, @11:21AM (#99149)

      or just use good ol' /etc/network/interfaces

      • (Score: 0) by Anonymous Coward on Monday September 29 2014, @04:40AM

        by Anonymous Coward on Monday September 29 2014, @04:40AM (#99464)

        That is going to get real old real quick if you actually use your laptop as a portable system. You want to manually configure wpasupplicant for every hotspot you connect to?