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: 5, Insightful) by Anonymous Coward on Tuesday August 19 2014, @01:20PM

    by Anonymous Coward on Tuesday August 19 2014, @01:20PM (#83050)

    We finally got rid of the ugly bloated out bash script hacks that people for some reason think is in line with the unix philosophy and instead we went to simple .ini file formats and very neat daemon control with a beautiful parallel start implementation.

    It's poorly engineered crap, talk about throwing out the baby with the bathwater!

    Systemd needs exorcising while we still have the chance. Replacing a traditional unix init is not a difficult task but replacing systemd is already a non-trivial undertaking.

    Starting Score:    0  points
    Moderation   +5  
       Insightful=4, Underrated=1, Total=5
    Extra 'Insightful' Modifier   0  

    Total Score:   5