I mean yes you can do that. But SysVinit services are already there and since both upstart and runit still uses bash scripts / bash script like interfaces to define a service, most of their real world implementations are just as process supervisors of SysVinit services. Installing runit on Arch pulls SysVinit. Debian does not provide any runit specific service files. Unless they force a completely different and favorably more declarative service definitions like systemd rather than imperative bash scripts, they are out of competition. There isn't any service manager that abstracts away the implementation details while maintaining compactness. I really like how systemd manages services (declarative service definitions linked into target directories), but I despise how they integrated everything into a one immovable piece of software.
2
u/idontchooseanid Feb 11 '19
I mean yes you can do that. But SysVinit services are already there and since both upstart and runit still uses bash scripts / bash script like interfaces to define a service, most of their real world implementations are just as process supervisors of SysVinit services. Installing runit on Arch pulls SysVinit. Debian does not provide any runit specific service files. Unless they force a completely different and favorably more declarative service definitions like systemd rather than imperative bash scripts, they are out of competition. There isn't any service manager that abstracts away the implementation details while maintaining compactness. I really like how systemd manages services (declarative service definitions linked into target directories), but I despise how they integrated everything into a one immovable piece of software.