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: 2) by present_arms on Sunday September 28 2014, @11:32AM

    by present_arms (4392) on Sunday September 28 2014, @11:32AM (#99153) Homepage Journal

    Can't argue with any of those points, POST on a server is a bane sometimes. Luckily a reboot for servers is a rare occaision (one would hope). I personally will be avoiding systemd with a passion, I'm pretty sure there will be more forks happening as more distros move to systemd.

    --
    http://trinity.mypclinuxos.com/
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by present_arms on Sunday September 28 2014, @11:37AM

    by present_arms (4392) on Sunday September 28 2014, @11:37AM (#99156) Homepage Journal

    apt-get install systemd
    Reading Package Lists... Done
    Building Dependency Tree... Done
    E: Couldn't find package systemd

    This is what I like to see :D

    --
    http://trinity.mypclinuxos.com/
    • (Score: 2) by maxwell demon on Sunday September 28 2014, @12:22PM

      by maxwell demon (1608) on Sunday September 28 2014, @12:22PM (#99178) Journal

      As a workaround you could create and install a package "sanity" which declares conflict with systemd. Then any attempt to install systemd will tell you that you'd first have to remove sanity.

      Now all you have to do is to make the kernel package depend on sanity, and systemd cannot be installed any more. :-)

      --
      The Tao of math: The numbers you can count are not the real numbers.
      • (Score: 2) by present_arms on Sunday September 28 2014, @12:58PM

        by present_arms (4392) on Sunday September 28 2014, @12:58PM (#99194) Homepage Journal

        That's actually a cool idea :)

        --
        http://trinity.mypclinuxos.com/
        • (Score: 0) by Anonymous Coward on Sunday September 28 2014, @01:19PM

          by Anonymous Coward on Sunday September 28 2014, @01:19PM (#99198)

          A better idea is for Debian to just not include systemd at all.

          • (Score: 2) by present_arms on Sunday September 28 2014, @02:58PM

            by present_arms (4392) on Sunday September 28 2014, @02:58PM (#99221) Homepage Journal

            Right, but it seems to be a done deal and anyone objecting seems to be silenced, it's heartbreaking that a once great distro is willing to be this stupid.

            --
            http://trinity.mypclinuxos.com/
  • (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.