I still have to learn a bit more on how to use it though.

That was my reason for supporting that ideal. But you do you.

A new chapter in SysVinit's history began when Jesse Smith (DistroWatch administrator) took over its maintenance in 2022. There have been several new releases of SysVinit since then, including two releases this year. With each release there are additional enhancements (e.g., minor bug fixes).

I never knew this. I was under the assumption that there had been no new development on sysvinit in years.

SysVinit was being used in UNIX in the late 1980s. I'm not sure when the augmentation happened: Based on the years written inside the source files, it may have been 2004. Judging from earliest git commit, it may have been 2012. If someone knows the history better, please jump in with the correct year when insserv and startpar were born. I can safely say it was sometime in the 21st Century My point is that the addition of these scripts was a major enhancement.

A new chapter in SysVinit's history began when Jesse Smith (DistroWatch administrator) took over its maintenance in 2022. There have been several new releases of SysVinit since then, including two releases this year. With each release there are additional enhancements (e.g., minor bug fixes).

Thank you for the answer.

I am with Devuan since ASCII was Testing and I discovered that ASCII supported my method of encryption/automatic decryption during bootup I used to use with my Debian installations before systemd. For some reason I started with openRC.

My experience that openRC did not care for non-critical but irritating error messages, understanding that openRC is more or less just an add-on to sysvinit, reading some of the forum entries and comments from fsmithred and ralphronnquist pointing to sysvinit as the primary init system made me try this on all my installations I have done from last year onward, and I miss nothing.

I have moved back from openrc

Hello.

I would like to ask, what is the reason for this? Why did you come back to sysvinit territory?

Hmmm ... Sharp.
You may have a something there.

From when all init software thing came into my field of view a few years ago, (as a workstation/desktop/laptop user) I could really not understand the benefits of whatever other choice I had besides the default sysvinit software I had running in my system.

I mean ...
WTF4?

ie: to what advantage?   <- key question for anyone with a workstation / desktop / laptop / netbook / RPi / etc.

What I did realise right away (10+ years of MS registry maintenance under my belt) was what a radical change / departure from what Linux is the advent of systemd brought along, so I looked for something else and found Devuan Jesse.

Thanks for that.

Best,

A.

We had a lot of this around 10 years ago:

"sysvinit lacks service supervision"
"you must be a server sysadmin (as per above)"
"no I'm just some random opinionated fanboi twat who read lots of Poettering's blogs - in 10 years from now I will be sneering at those who are reluctant to move to Wayland".

My FreeBSD servers run what they need to run using BSD init. systemd units have been less reliable and less untuitive and more difficult to manage.

This "migrate and upgrade" bollocks comes from the proprietary mindset, where every migration and upgrade is profit for Big Tech corporations.