Greetings.

Steve Litt - 14.12.25, 11:53:43 CET:
> Joel Roth via Dng said on Sat, 13 Dec 2025 19:42:14 -1000
>
> >I believe reading that runit supports sysvinit scripts,
> >so you won't have to do any fiddling to change over.
>
> If runit supports sysvinit scripts that's news to me, but I think those
> immense scripts are the #1 reason not to use sysvinit. The #2 reason is
> that if you write a daemon for sysvinit, your daemon must background
> itself at just the right time. Except for those two things, sysvinit is
> just fine.

Runit may be able to support a lot through to its shell boilerplate for
initializing one of its three stage.

Runit in Debian, /etc/runit/2 =>

[…]
#sysv emulation
   #90 sec timeout (async timeout) for each script to start, then it detaches
   #to avoid getting stuck at boot. see #838480-msg#49
if [ "$runsv_dir" != solo ] && [ ! -e /etc/runit/no.emulate.sysv ]; then
        /lib/runit/async-timeout /lib/runit/run_sysv_scripts '/etc/rc2.d'
fi
[…]

It needs to do that as long as there is no 100% coverage of native Runit
service directories in Debian.

I bet they have or try to remove Sysvinit support from Systemd, but for
Runit there is neither the same amount of developers working on it nor
the same amount of pressure to get rid of compatibility support.

Of course anyone can contribute to improve the coverage of runit service
directories in Debian further either by contributing to package
runit-services or when meeting a friendly and cooperative maintainer
like I did for Incus directly to the package. I am running Runit
supervised Incus in production on my private server and soon I will do
the same on a freelance work server. I contributed both ways and enjoyed
doing this work.

Best,
--
Martin