"Garry T. Williams" gtwilliams@gmail.com writes:
The analogy is placing a script in /etc/init.d and then linking its name in the /etc/rc5.d directory.
I find this much simpler than the sysvinit schemes.
You have taken well over 100 lines to give a description about how to get a daemon started with systemd, not to mention the hours you must have spent reading all the documentation to figure out how to do what you wanted.
It took you only 2 lines to describe how to do the same thing with sysvinit.
I don't understand how you can find systemd "much simpler" than sysvinit. Where and how is it simpler than sysvinit? It takes only about 2% of the effort, if that much, to start a daemon with sysvinit than it takes to do the same with systemd.
For systemd, you even have to learn a whole new "programming language" to create configuration files which is useless anywhere else. Efficiency is negative here.