Having shell scripts that you can read and edit makes so much more sense.
Putting a script in a directory to have it run at startup makes sense. Systemd's approach of "registering a service" is hell.
Having logs in plain text is beautiful. Having to use special software to read logs is hell.
About the logs, yes, plain text files, commands and pipes are great, but journalctl is really great too. It is powefull and includes everything you might need to inspect logs with accuracy in the same tool.
Just to clarify: I'm not a fanboy, I'm just pragmatic.
until you're forced to run a rescue system without systemd and try to read logs. And don't say that it doesn't happen, because that situation is 99%.
Why would you limit what can be done based on the current abilities of a rescue system?
- You create a new whatever.service text file with some data=value pairs and put it in /etc/systemd/system. Doing this is at least only 25% as hard as learning bash.
- systemctl daemon-reload
- systemctl start whatever.service
Not hard.