Stories
Slash Boxes
Comments

SoylentNews is people

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: 2) by WillR on Tuesday August 19 2014, @03:15PM

    by WillR (2012) on Tuesday August 19 2014, @03:15PM (#83114)
    Really? From where I sit (admittedly not a developer or a packager), a hundred bash scripts that persist in a given distro for years (maybe decades) with only minor revisions, that are all run with root privileges at every boot, and that only one or two maintainers really understand looks like an absolutely huge attack surface...
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 4, Insightful) by VLM on Tuesday August 19 2014, @05:18PM

    by VLM (445) on Tuesday August 19 2014, @05:18PM (#83173)

    LOL thats kind of the point, if bash has a priv esc hole, its going to be found probably well before it becomes an "init system" issue. Also if it has a hole it was probably found in December of 1995 which is great seeing as I've kept up with patches since them. Systemd, probably none of the above. You'll find your bugs the hard way.

    "that only one or two maintainers really understand" No they're not that hard. And fairly well standardized. Much simpler to learn and understand than the internals of the replacements. Which is scary.

  • (Score: 4, Funny) by mrider on Tuesday August 19 2014, @07:31PM

    by mrider (3252) on Tuesday August 19 2014, @07:31PM (#83211)

    a hundred bash scripts that persist in a given distro for years (maybe decades)

    Because all-new code is bug free, while old code accumulates bugs like barnacles.

    --

    Doctor: "Do you hear voices?"

    Me: "Only when my bluetooth is charged."