3 ms·
I actually like some things of the init daemon part of systemd. But systemd is not only an init daemon anymore and the systemd developers work actively to cut
by chronid 11y ago
I actually like some things of the init daemon part of systemd.
But systemd is not only an init daemon anymore and the systemd developers work actively to cut off everything that is not systemd (see the udev saga as an example) or make idiotic decisions (NTP server defaults?). And that, in addition to some other things (why should udev be part of systemd? Why should be there an arbitrary limitation in core files size? See also [1] for more) left me very worried. And I don't like journald at all, rsyslog does almost everything already.
And the way Fedora integrated kdbus before it was put into the mainline kernel? That's ridiculous, sorry.
The need to make another 'su' because the older one was not good enough in the mind of the developers?
And now 'systemctl is-system-running'? Wat?
1. http://suckless.org/sucks/systemd http://suckless.org/sucks/systemd
- digi_owl 11y ago> But systemd is not only an init daemon anymore and the systemd developers work actively to cut off everything that is not systemd (see the udev saga as an example) http://www.landley.net/notes-2015.html#05-07-2015 http://www.landley.net/notes-2015.html#05-07-2015 is a lovely entry from Rob Landley about trying to maintain an alternative to udev, and getting the runaround by GregKH and Kay Sievers. > or make idiotic decisions (NTP server defaults?). Love the excuse for that. "Systemd is not meant for end users, and distros should set their own servers anyways". Its like anyone thats not a developers working for/on the large name distros are users (aka consumers, aka mooo) and should shut up and accept what the distros ship.