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 at this point even openrc is old and there's stuff like runit, s6, dinit, ... ready to take its place

@sys64738 tbh i dont even know about most of these because systemd has been my swiss knife for everything for a long time

the one time i had to touch sysvinit was the last time i'd rather have to touch it, and thankfully the Grey Beard at our company cleaned up the single-digit debian VM that contained it

@sys64738 @ShadowJonathan

openrc predates systemd by a year, and iirc both runit and s6 are about the same age as well -- the only "newer" one here is dinit

all of them except runit are still maintained and getting newer features to this day though, unlike sysvinit, so idk why anything would need to take openrc's place... we can coexist
@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