Story

Who's Afraid of Systemd?

Preview

Might be a bad idea (Score: 4, Interesting)

by evilviper@pipedot.org on 2015-07-26 21:22 (#FGWD)

At the risk of reigniting the flames, I think |. should have at least one systemd story that isn't negative and conspiratorial. Besides, maybe the issue can be hashed-out in on-topic comments, instead of spilling-over into all other stories.

Re: Might be a bad idea (Score: 0)

by Anonymous Coward on 2015-08-03 07:27 (#G8HT)

Great, one. Where? A friend of mine who runs Linux as his home OS is now seriously annoyed. A recent upgrade included SystemD. Something borked the video card driver. The interupt for boot isn't working. Nothing could fix the issue. Problem diagnosis was painfil. Liken this to regressing back to Linux of 1995. He solved the problem by regressing back and now has Upstart working. A huge waste of his time. For what? How does SystemD help here? Screwing with the init so users can't diagnose problems? Stuffing up the init order causing fatal boot? This is an end user. Today he has removed the problem - Systemd. Tomorrow he is looking for a new OS or an easy way to get rid of it.

Re: Might be a bad idea (Score: 2, Insightful)

by billshooterofbul@pipedot.org on 2015-08-03 14:21 (#G9MP)

What do you mean by " the interrupt for boot" ? If its not getting to grub, or gummiboot that's not a systemd issue. Sounds like the update screwed up things. Rather than systemd. He's probably trying sysvinit style debugging techniques for systemd.

Moderation

Time Reason Points Voter
2015-08-03 21:53 Insightful +1 evilviper@pipedot.org

Junk Status

Not marked as junk