> What tangible thing does systemd do that hurts your usage of the OS?
Well, binary logging, for a start. Usurping DNS.
Actually, let's not go down that path - it would be a long argument, and I've already lost it, years ago.
> would you ever notice that I have done that?
Umm, yes.
My case isn't that systemd is bad; it's that I objected to Debian making systemd the default init, and that it's not very easy to make a non-default init the active init. I have a preference, I don't think I have to justify it, but the Debian change made it hard for me to exercise that preference. That's all.
I always feel like journald was not fully complete before major distros swapped over to systemd. I like the problems it was trying to solve and I get the reasons journald went with a binary database file.
I’ve personally been burned multiple times at work by log monitors missing log messages due to logrotate. It isn’t often, but often enough I’m glad for the solution.
The thing that hurt was that they did all this work for better structured data and then the only remote logging solution (that was really usable) at the time was syslog. Remote logging has gotten better depending on what sort of central logging vendor you’re using.
Well, binary logging, for a start. Usurping DNS.
Actually, let's not go down that path - it would be a long argument, and I've already lost it, years ago.
> would you ever notice that I have done that?
Umm, yes.
My case isn't that systemd is bad; it's that I objected to Debian making systemd the default init, and that it's not very easy to make a non-default init the active init. I have a preference, I don't think I have to justify it, but the Debian change made it hard for me to exercise that preference. That's all.