okay why are we still even bothering with sysv-init

yes sure systemd is having Another Altercation right now, but surely we can't just use openrc at this point and save us major headaches, right?

@ShadowJonathan

fwiw nothing is *actually* using sysvinit except debian as one of it's init alternatives

gentoo and alpine does ship with sysvinit (or busybox init for alpine, which is like sysvinit but with only the basics to launch e.g. openrc) by default, but all that sysvinit does in those systems is exec openrc then wait
@navi @ShadowJonathan alpine does not ship with sysvinit by default
@ptrc @ShadowJonathan isn't busybox init the same config? inittab

i'm not talking about a specific implementation but the design, aka inittab (and often init.d/rcS for "true" sysvinit systems), which sucks
@navi @ShadowJonathan they aren't drop-in compatible, no, mostly because of the "identifier" field, which on bbinit is device (so, e.g. tty1) instead
not to mention bbinit lacks half the functionality, supporting just the bare minimum to get OpenRC running
@ptrc @ShadowJonathan

fair enough

i do wonder if i can get distros to use openrc-init after i improve the supervision for ttys