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: 1) by jbernardo on Sunday September 28 2014, @07:46AM

    by jbernardo (300) on Sunday September 28 2014, @07:46AM (#99107)

    According to the church of LP, repeating the fact that pulseaudio has issues is an ad hominen attack on their god, the infallible developer Lennart.Just check one guy posting as "interested" on the "boycott systemd site" thread on phoronix.

    I really should reply to him, but it is like punching walls.Nothing gets through - and worst, as he has such a view of LP and his works that even the facts that pulseaudio was unusable for ages and is still unstable could all be false, he won't acknoledge that no mather waht, the issue is always alsa drivers or users...