Hacker News Reader

Comment by dschuetz | Hacker News Reader

This systemd train has to stop. Why isn't Poettering just forking the Linux kernel for his very own systemd-OS distribution? If any of the Linux distributions I'm using touches the home directory because of Poettering's say-so in that video I'll cease using and supporting them.

View on HN

Isn't anyone free do make what they want and see if the market takes it up? Anyway, this week's Linux Action News [0] has a nice breakdown of the features, I think it is better to discuss the merit and downsides of this that to just shouting: "Stop the systemd, pulse-audio, any-new-feature-that-scares-unix-natives -train."

[0] https://linuxactionnews.com/

No. Because this nonsense will break my systems.

What is this? Some crazy guy makes significant changes to a standard, the distribution maintainers will just gobble it up (as per usual) and then I have to weigh the pros and cons instead of complaining and fixing/adapting my systems e.g. wasting time because of a crazy guy's ideas?

There is no market in OSS. It's either use it or leave it. But even in OSS there are established standards which are relied upon! Poettering doesn't care about that, because he likes change.

Red hat and Ubuntu LTSs have 5 year's worth of support.

Taking 5 year's to learn something new is your problem.

This guy has become the bogeyman of OSS. Does he have some sort of mind control that makes distributions pick up systemd?

Why is he crazy because he's suggesting change?

You missed out the step where the knowledgeable people who run and have to support most of the major distros adopted systemd. When's that going to backfire? Any day now, right?

I don't understand your last paragraph. Did the guy behind systemd use OSS or leave it?

If systemd-adoption would make it harder to maintain a distro, the distros would not have adopted it.

Instead, systemd solves a lot of problems for distro maintainers. The didn't just "gobble it up", they made a very measured choice to adopt it.

Now what were those problems, specifically, for distros, that weren't caused by systemd eating and replacing previous solutions, which suddenly became unmaintained and unsupported?

(I'm looking especially at udev and all the dbus hookery.)

Have you perchance tried Void Linux? I wanted to try it, but didn't get around to do it yet.

It's nice:) Rolling release, works well for me. Does require semi-regular tinkering in my experience (usually because of issues in packages getting shifted around). I tend to view Alpine and Void as a nice pairing; Alpine has releases and is stable and reliable. Void is rolling release and requires more tinkering, but it's a nice system if you don't mind that.

Reply on news.ycombinator.com