On Mon, Jul 3, 2017 at 12:35 PM, Adam Van Ymeren adam@vany.ca wrote:
It's unfortunate that systemd is seen as necessary to get these shorter service files for service declaration. Or that sysvinit requires you to write long complicated init scripts.
Rather than replacing the init system, it would be possible to write a standalone tool to interpret service files that sysvinit can call.
This works because sysvinit and other early UNIX init systems are written as separate components, that interact by running other exectuables/commands. This is the opposite to how systemd is architected where it moves more functionality into the same executable, making it less flexible and extensible as a result.
Of course that's possible! It's just that (AFAIK) nobody has done it yet. I'm sure the users of non-systemd init systems would appreciate such a tool, given the increasing number of projects that ship with only systemd service files upstream.
The question remains: who's going to write it?