What “technical” concerns do I have with systemd?

Post by chronid » Thu, Sep 25, 2014, 8:10 AM UTC

angersock wrote: post #54

lmm wrote: post #31

Earlier quoted context omitted.

Systemd didn't used to be this invasive. There have been "better init" options for many years, none of which gained much traction. So most of us figured the community as a whole wasn't very bothered. IMO systemd has only achieved "popularity" by using some very underhanded tactics.

Is this a classic Poettering thing? How'd PulseAudio get stuck in so much stuff? Is this a pattern?

It's not really a "Poettering" thing. More like a "Red Hat" thing. They control (= their employee are mantainers and developers of) most linux core userspace programs/libraries, starting from Udev and Dbus and Upower, they/their developers make the choices that matters in that regard. It's how OSS operates.

Post by justizin » Thu, Sep 25, 2014, 10:01 PM UTC

MertsA wrote: post #99

justizin wrote: post #27

Earlier quoted context omitted.

QR codes for kernel panics is actually brilliant, because it encodes the data which would otherwise just be serialized to screen in a manner that makes it portable.

That actually might be nice but don't get your hopes up, systemd isn't actually part of the linux kernel as some conspiracy nuts would have you believe. The systemd project can't possibly just add random stuff to kernel panics, all of that code is in the kernel, not userspace. I think a little while ago there actually was some work done on making kernel panics display a QR code but I doubt it'll ever be merged in if…

I think you're right, but if that's so, then apparently all of the features the OP claims to be bloat in systemd are questionably in systemd at all, and the entire discussion is moot.

Re: What “technical” concerns do I have with systemd?

Re: What “technical” concerns do I have with systemd?