o1bigtenor via Dng said on Mon, 30 May 2022 17:07:44 -0500

>On Mon, May 30, 2022 at 5:03 PM o1bigtenor <o1bigtenor@???>

>Not trying to start any kind of 'holy war' but was thinking of using
>SysV init unless there are some great arguments where another option
>is better - - - that is something that needs its own advice.

Before I continue, I was quite happy with sysvinit 1998 to whenever
upstart took over. Sysvinit does the job.

In my opinion the difference between sysvinit and OpenRC is not enough
to walk away from the familiar sysvinit.

Now, because runit exists, I would never again start up my daemons
using sysvinit. Instead, I would do one of the two following:

1: Use sysvinit for PID1, and:
    A: Start runit in /etc/inittab as a respawn
    B: For each daemon:
        i: Disable the daemon in sysvinit
        ii: Enable it in runit

2: Use runit as a complete init system

If I were using Devuan (my Daily Driver Desktop (DDD) is Void), I would
choose alternative 1 because it's simple and sticks with what I know. If
I were using a native runit distro like Void I'd use alternative 2.

I think #1 is a great way to slowly wade from the shallow end of to the
deep end.

SteveT

Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm