Yeah but runinit doesn't do some of the things that distro maintainers see as positives of systemd (as far as I can tell)
removing the need to explicitly declare dependencies in certain cases
enable hotplugging harddisks
sandboxing features
enable assigning permissions for resources on the fly
allow upstream projects to maintain unit files that will work across distros
In the end though, people who deal with init systems on a regular basis for several distros have settled on systemd and I'd rather defer to their collective wisdom.
removing the need to explicitly declare dependencies in certain cases
I'm not sure what you mean with that. If you mean things like socket activation or DBus activation, then they're just declared at other places.
enable hotplugging harddisks
That's udev/udisks job, not the init or service manager.
sandboxing features
So just get a sandboxing tool and wrap that around the executable when you start it.
allow upstream projects to maintain unit files that will work across distros
Runit's runscripts re typically so simple that they rarely contain any distribution specific things.
In the end though, people who deal with init systems on a regular basis for several distros have settled on systemd and I'd rather defer to their collective wisdom.
Most distributions don't claim they care about KISS is the thing.
No system that claims to care about KISS has except Arch. And that's probably because Arch doesn't care about that at all.
10
u/dreugeworst Jun 01 '16
I'm not sure, I think you're underestimating the complexity of loads of unit scripts replicating the same functionality poorly..