3 ms·
Did you notice I haven't mention systemd in my comment at all? And other than this first sentence, I am not going to mention it in this comment at all. The imp
by theamk 4y ago
Did you notice I haven't mention systemd in my comment at all? And other than this first sentence, I am not going to mention it in this comment at all.
The important thing is not who won, but the fact that the idea of writing init scripts in bash/sh has lost. Almost no one wants to maintain yet another incomplete or buggy shell script implementating of "start", "stop" and "status" commands. It is declarative way now - somehow define the command, arguments, user etc.. and let init system handle start/stop.
(Yes, there are still ancient systems like Slackware which use plain bash and have no plans to change. But even FreeBSD is pushing toward declarive: look at [0], does this look like a simple shell script which makes it cleat what's going on?)
[0] https://docs.freebsd.org/en/articles/rc-scripting/#rcng-daemon https://docs.freebsd.org/en/articles/rc-scripting/#rcng-daem...
That's why the people who advocate sysvinit get so little support. Try advocating for runit or daemontools or launchd or openrc or even SMF ( :) ), this will get you further.
- Maursault 4y ago> Did you notice I haven't mention systemd in my comment at all? That's how whataboutism works. It's a special type of tu quoque argument. > That's why the people who advocate sysvinit get so little support. I don't think there are any sysvinit advocates, only those advocating for simplicity & against complexity.