Comment Re:uh (Score 1) 124
By this time, there are a lot of replies to you, but I'll try to add a little more context.
I think a lot of the "visceral hate for systemd" comes from not only the "it's not the Unix way" mindset, but that systemd comes across as "change for the sake of change". From my probably limited perspective, I don't feel that it really gives much of value, but it has made my life harder. I have new commands to learn, new text files in strange places to learn/create, and it's honestly hard to debug. A shell init script is easy to find and easy to debug, add a "set -x" to the top and then watch to see what went wrong and fix it. While there might be a way to do that with systemd unit files, I've never seen a way to see every command it does. Logging at the earlier stages is also pretty spotty (having your system fail to boot and not finding any logs is really maddening -- happened only once, but it never happened under init-scripts because there was always a *text* log somewhere). Leonard should be verbally smacked for creating binary log files, even if there is a text *option*.
I understand how/why we have systemd. There was a lot of arm twisting by Redhat, and the people that like/need it the most are the distro maintainers, not people doing sys-admin work -- who are the ones that tend to feel the pain the most. I admin my home machine and a few at work. Most of the time, stuff just works, but when it doesn't work systemd is extremely annoying and I feel the hate because I sort of have to relearn the unit file stuff all over again because I touch them so infrequently, unlike an init [shell] script that was created from a template and is easy to work on. Yes, we've adapted; but it was forced on us for what appears to be little good reason, therefore many of us are not fine with it. HTH...