> it does everything you want it to do It does everything no one asked it to. I'm sure they will come up with obscure reasons why the next perfectly working to

> it does everything you want it to do It does everything no one asked it to. I'm sure they will come up with obscure reasons why the next perfectly working tool has to be destroyed and redone by the only authority - the LP team. Like cron, sudo and yes - logging. > journalctl -D ... will give you what you want Look, I don't need the help of journalctl to grep through text. I can simply grep thru text. > I used it in embedded systems Good luck in a few years when you are flying home on the next Boeing 737-MAX-100800 and it fails mid flight because systemd decided to shut down some service because fuck you that's why. > it does not follow the 'everything is a file philosophy' It does not follow 'everything is a separate simple tool working in concert with others'. systemd is a monolith disguised to look like a set of separate projects. > don't want to spend time understanding it, it is hardly the fault of the tool It is, if we had proper tools for decades and they did work. I'm not a retrograde guy, quite the opposite, but the ideology that LP and the rest are shoving down our throats brings up natural defiance. > there will be many Ah-ha moments No doubts. systemd unit files and systemd-as-PID1 is excellent. It was NOT excellent for the whole time but now it is. The rest? Designed to frustrate and establish dominance, that's it.