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: 4, Insightful) by morgauxo on Tuesday August 19 2014, @03:19PM

    by morgauxo (2082) on Tuesday August 19 2014, @03:19PM (#83115)

    Linux is supposed to be about options. Distros are making it hard to NOT use systemd.

    I want to see Linux be a major player on the desktop. Why? Because I use Linux and I want to be sure that the 'mainstream' software I want is/remains available to me. For that we need a market. For example, for years there was no up to date Flash player. Flash sucks but unfortunately at the same time a great deal of internet content required Flash. There were options for Linux but none of them was perfect. Today that is not an issue but I would like to see things like Netflix, Amazon, etc... working on MY desktop.

    Apparently to be popular we need something like Systemd? I don't get it. Using an openrc based distro I don't remember having to edit config files, startup scripts, etc to do desktop stuff. I only did that when I was setting up server processes. Whatever... we had multiple startup systems to chose from for years. Why does it suddenly have to be just one, systemd!?!?

    I see no problem with desktop 'normal user' based distros using something like Systemd. Just don't take away my option to use one of the more Unixy ways. This really should be low level stuff. Applications shouldn't care and I should still be able to use all the same applications as the 'normal user'.

    Starting Score:    1  point
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 0) by Anonymous Coward on Tuesday August 19 2014, @03:33PM

    by Anonymous Coward on Tuesday August 19 2014, @03:33PM (#83122)

    Apparently to be popular we need something like Systemd?

    If you want any traction with this OS the answer to that is yes.

    MS used to have the *exact same problem*. I remember well autoexec/config.sys/win.ini hell. All of the 'old' ways are still there (see autoruns). But MS makes it pretty clear what the 'right way' is. It makes it extremely easy to program to as the API is known and well documented. Honestly, at this point (having used linux since it fit on a couple of floppies) it is embarrassing. The big distros are just starting to 'hey maybe we should look similar for things like steam'. My synology uses one way to init something my android another my tv yet another and my desktop another and my servers yet another way. I can not program to that and have a well tested product. Which is sad as linux/bsd have a very rich programming environment. But it takes lots of tinkering to get to the point where things run on all systems. Time I could be better spending adding something cooler to my product.

    • (Score: 2) by morgauxo on Tuesday August 19 2014, @04:09PM

      by morgauxo (2082) on Tuesday August 19 2014, @04:09PM (#83143)

      Nope, still don't get it.

      What are you setting up? Most modern end-user oriented distros autodetect everything! It just works!
      Or, if it doesn't it almost always means you have unsuported hardware. Systemd can't fix that!
      What is Systemd replacing that a 'normal' computer user would EVER have touched or even seen?
      If you are spending hours configuring openrc or some other startup scripts you must be doing something that this new target audience will not be interested in anyway!