Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by janrinok on Tuesday August 19 2014, @12:04PM   Printer-friendly
from the you-either-love-it-or-hate-it dept.

The good people over at Infoworld have published a story outlining why they feel systemd is a disaster.

Excerpt from Infoworld:

While systemd has succeeded in its original goals, it's not stopping there. systemd is becoming the Svchost of Linux—which I don't think most Linux folks want. You see, systemd is growing, like wildfire, well outside the bounds of enhancing the Linux boot experience. systemd wants to control most, if not all, of the fundamental functional aspects of a Linux system—from authentication to mounting shares to network configuration to syslog to cron. It wants to do so as essentially a monolithic entity that obscures what's happening behind the scenes.

 
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 Tuesday August 19 2014, @02:51PM

    by Anonymous Coward on Tuesday August 19 2014, @02:51PM (#83100)

    i'm still hold a fading hope that debian sticks with sysvinit as default

    if not, it will always be an option

  • (Score: 2, Informative) by bucket58 on Tuesday August 19 2014, @03:47PM

    by bucket58 (1305) on Tuesday August 19 2014, @03:47PM (#83128)

    Be scared. The Debian systemd package maintainers and their friends are doing a fine job at extinguishing any means to run non-systemd init in Debian.

    • (Score: 3, Interesting) by FatPhil on Wednesday August 20 2014, @08:44AM

      by FatPhil (863) <{pc-soylent} {at} {asdf.fi}> on Wednesday August 20 2014, @08:44AM (#83444) Homepage
      "are doing"? "Have done", more like.

      I've been Debian-only for 14 years. My next install (one of my servers needs replacing soon, I'd like it to be replaced in a controlled fashion rather than a panic) will be something else, definitely something non-systemd. Perhaps Gentoo, but I've not liked their way of unrolling loops in the past. But to be honest, I might even leave the Linux fold and hit one of the BSDs.
      --
      Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
  • (Score: 5, Informative) by cykros on Tuesday August 19 2014, @07:35PM

    by cykros (989) on Tuesday August 19 2014, @07:35PM (#83214)

    Debian may let you down, but there's always that distro that's even older than Debian kicking around, and I really don't see Patrick Volkerding giving us a Slackware that uses systemd. We're still using lilo, ALSA, and sysvinit here in the slack world...though you don't hear about us as much, because our documentation and organized, accessible system really minimizes the need for massive forums over every little thing someone might want to do with the "user friendly" "easy" modern systems that have been fed to the masses.

    And, failing that, there's always the BSD world. With Linux distros racing to abandon the Unix philosophy, people who like the Unix way are being left with little choice other than to return to Unix. I'll be sticking with Slack personally, but definitely am a bit less hopeful about the future of Linux than I was 10 years ago with all of these recent trends.