Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by LaminatorX on Friday September 19 2014, @05:47AM   Printer-friendly
from the voice-from-on-high dept.

Systemd has turned into the Godzilla of Linux controversies. "Everywhere you look it's stomping through blogs, rampaging through online discussion threads, and causing white-hot flames that resemble Godzilla's own breath of death," writes Jim Lynch. Now Sam Varghese reports at iTWire that although Linus Torvalds is well-known for his strong opinions, when it comes to systemd, Torvalds is neutral. "When it comes to systemd, you may expect me to have lots of colorful opinions, and I just don't," says Torvalds. "I don't personally mind systemd, and in fact my main desktop and laptop both run it."

Oh, there's been bitter fights before. Just think about the emacs vs vi wars. Or, closer to systemd, the whole "SysV init" vs "BSD init" differences certainly ended up being things that people had "heated discussions" about. Or think about the desktop comparisons.

I'm not really sure how different the systemd brawls are from those. It's technical, but admittedly the systemd developers have also been really good at alienating people on a purely personal level too. Not that that is anything particularly new under the sun _either_: the (very) bitter wars between the GPL and the BSD license camps during late-80s and early-90s were almost certainly more about the persons involved and how they pissed off people than necessarily deeply about other differences (which existed, obviously, but still).

Torvalds was asked if systemd didn't create a single point of failure which makes a system unbootable if it fails. "I think people are digging for excuses. I mean, if that is a reason to not use a piece of software, then you shouldn't use the kernel either."

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 jackb_guppy on Friday September 19 2014, @12:09PM

    by jackb_guppy (3560) on Friday September 19 2014, @12:09PM (#95445)

    I got into a war withe systemd last weekend. System was doing strange things, requesting authorization (user password) on each plugging and unplugging of the USB stick or drive. Trying to access the network, again the authorization panels. I rebooted and rebooted and rebooted, it fainlly went away. It was like a function was not starting correctly and there was no word what that function was. I came close to reloading back to 12.04.

    Do I like systemd? -- do not care one way or another. But the above was not a good user experience.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by kaszz on Friday September 19 2014, @12:26PM

    by kaszz (4211) on Friday September 19 2014, @12:26PM (#95451) Journal

    No debugging ability?

  • (Score: 2) by cafebabe on Friday September 19 2014, @08:10PM

    by cafebabe (894) on Friday September 19 2014, @08:10PM (#95633) Journal

    Of course there is. You just have to go through those binary logs...

  • (Score: 2) by kaszz on Friday September 19 2014, @08:41PM

    by kaszz (4211) on Friday September 19 2014, @08:41PM (#95652) Journal

    Which differs depending on version that needs a special source code with special recursive dependencies that requires download and chat room help. Which depends on the network you were trying to repair.. ? :D

    In another world one would just read the text log and change the text based configuration file?

    SystemD seems like a development with good intentions but without experience and foresight. But the path to debug hell is often paved with a nice vision that doesn't match the full reality.