Am 19.12.2016 um 15:52 schrieb Marc Joliet:
> That is incorrect, systemd allows for overriding files in
> /etc/systemd/system/${unit_name}.d/*.conf.
Then this is very new.
> Furthermore, service units can
> read environment variables from a file via EnvironmentFile.
Initscripts can do the same.
> I'm not convinced that you actually understand systemd particularly well. It
> seems to me that if you want to develop an informed opinion about it, you
> should:
You don't need to be convinced. It's sufficient that I know systemd
pretty well from the beginning when the Poettering fanboys of Arch Linux
forced this crap onto the Arch Linux users, while they regularly were
telling that they don't force it onto their users, that it will be only
optional.
> a) Read the official documentation (don't just rely on what others say; even
> when well-intentioned, people can say stupid things).
I did read all of Poettering's insults against his critics in his oh so
"technical" documentation. Thanks!
> b) Try to set up and/or run a systemd-based system, and seriously try to grok
> it. Only then will you be able to compare it to other init systems properly.
I already had to do it. That's why I went back from Arch Linux to
Gentoo. And that's why I'm currently trying out Devuan on my RasPi.
Looks pretty good so far. They even have a 64 bit image for the Pi 3.
And I already couldn't read those crappy binary systemd log files on a
correctly working POSIX system.
Btw., yes, systems without systemd boot a lot faster than systems with
systemd. Same experience made someone else here on the mailing list. I
forgot who it was.
So, yes, I know exactly what I'm talking about.
And, yes, systemd is broken by design and just a PITA.
Heiko Baums
