Thanks for the info Steve.
Yes, I can document my travels through init land. It may be a while before I attempt it though. Like you said, perfect is the enemy of good. Good advise regarding setting up a couple of vm's to try it.
(I'm tuning 70 this year and I'm a little slower than I used to be on the draw so to speak.)
My last foray into stuff I didn't understand and took me a while to sort through setting up a BSD firewall (OpenBSD pf) until I found your resource:
OpenBSD/pf Firewalling For the Less Gifted.
Man, that was me!
Anyway, thanks for taking the time to respond to my queries. It is much appreciated.
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, March 8th, 2023 at 12:40 AM, Steve Litt <slitt@???> wrote:
> Charles said on Tue, 07 Mar 2023 19:33:48 +0000
> > Thanks Steve.
> > It gives me a little perspective on a complicated subject by someone I
> > respect. Any thoughts on why Devuan uses sysvinit or is it just
> > personal preference by the devs? Charles
> Hi Charles,
> Devuan uses sysvinit because the perfect is the enemy of the good.
> Debian had used sysvinit for decades before Debian Jesse, so everyone
> in the Devuan project knew sysvinit like the back of their hands. s6,
> runit and OpenRC, not so much. Anything but sysvinit would have taken
> extra time and effort that could be better used to get rid of systemd
> and counter all the senseless systemd dependencies Debian was throwing
> at them.
> Speaking of the perfect being the enemy of the good, you can get
> between 10% and 80% of the benefits of runit right now. Simply continue
> to use the PID1 from sysvinit, and have sysvinit supervise the runit
> superviser by putting into /etc/inittab the following:
> respawn "$runsvdir dir_with_runit_symlinks ' log: .................'
> Only instead of the few dots I put in, you should put in 245 dots,
> because 245 (which is about the max) yields better troubleshooting help
> than just a few. What I outline above makes sysvinit's PID1 supervise
> runit's supervisor.
> Then, slowly and deliberately, shift daemons from sysvinit to runit's
> supervisor. I haven't used sysvinit in 7 years, but as I remember there
> was some sort of systemctl command to disable a sysvinit started
> daemon, so disable it immediately before placing it under runit's
> Charles, I was doing this, with daemontools instead of runit, for years
> before systemd existed. I just found daemontools (which is pretty much
> the same as runit's supervisor) to be easier to understand and deal
> with than sysvinit. Remember, there's no shame in leaving some of your
> daemons managed by sysvinit (the perfect is the enemy of the good :-).
> Of course you'll need to read runit's documentation, and you'll need to
> make some Devuan qemu VMs to experiment with.
> Please, please, I beg of you, document this journey or at least keep
> the Devuan mailing list informed.
> Steve Litt
> Autumn 2022 featured book: Thriving in Tough Times