[pdimitar]

I don't care where the files are. You're fixating on an implementation detail.

I want commands that achieve my goals. Where they get their info from I couldn't care less.

It seems you're more interested in reverse-engineering your system than actually doing something with it. Which is your right of course, but surely you can see how that can't be the priority of everyone.

[traverseda]

I think you're missing the point that you can have both, a system that works well and adheres to basic unix philosophy.

[pdimitar]

And you claim systemd is not working well, which is factually not true.

[traverseda]

It is true, across a bunch of different metrics I listed. Also an embarrassing amount of privilege escalation bugs.

I mean I don't know what you'd accept as evidence that it wasn't working well, but if you get an idea of what could actually change your mind on this let me know. I feel like I've more than documented the issues I've personally had with it.

[pdimitar]

I don't put your experience into question, I'm stating that I never replicated it.

I have 5 Linux machines and systemd made my life little better on all of them due to using the same commands and not having to pay attention to distro differences. I periodically backup logs and configs, I scan for errors and post them in private channels, I'm able to monitor if a service fell on its face, I have a small naive resource meter, and a few others.

I'm not an advanced sysadmin by any meaning of the word, but I know enough to make my life easier. Maybe you're using your machines in a very different manner that make systemd crap the bed? I'm merely saying that it doesn't do that for me.