SoylentNews is people
SoylentNews
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.
(Score: 0) by Anonymous Coward on Monday September 29 2014, @04:32AM
Bollocks, I've tested this on workstations, laptops and servers. You can even skip a step: apt-get install sysvinit-core will remove systemd for you.
Most packages only depend on an init system provider, they don't care which one it is. The only thing I lost was NetworkManager which is never installed on servers anyway and easily replaced with wicd or equivalent on laptops.
(Score: 1) by hendrikboom on Tuesday September 30 2014, @11:14PM
The only thing I lost was NetworkManager
So does NetworkManager now depend on systemd? When did this dependency appear in jessie/testing? About a month or so ago? That's when my wifi stopped working properly.
Also in the last month the file manager in xfce stopped having the permissinos it needs to mount USB sticks. Is there a similar problem there?