3 ms·
To be fair, systemd started when Poettering was at Red Hat. He was EEEing Linux even before he was at Microsoft :^)
by coldacid 4y ago
To be fair, systemd started when Poettering was at Red Hat. He was EEEing Linux even before he was at Microsoft :^)
- thrown_22 4y agoRedhats whole business model was to make linux too complex to understand by anyone not at redhat.
- john_alan 4y agoIs systemd bad?
- bombela 4y agoIt felt it was being forced on me when various distributions switched to it. And it was something new and buggy to learn that I didn't wanted to deal with. The general idea behind it are good in my opinion. But the problem is how confusing and slow the god damn thing is. Try overriding a service definition? You must know to set exec to empty string before you are allowed to override it. Really first line sets to "" second to the value you want. Just weird. Try getting the logs of the service you just edited and restarted? Wait 10s on a flagship computer for the 5 lines of log to show up. Systemd stores logs in binary. That takes more storage space than gzipped text. While being about 100x or more slower than zcat and co.
- john_alan 4y agointeresting thanks, seems more user friendly largely than init.d though, maybe I'm just a Linux noob.