So, from my notes:

#voidlinux: symlink a service's name from /etc/sv/ to /var/service to enable a service then sv up & down will become available for that service.
#chimeralinux: dinitctl, kinda like systemctl
#devuan: update-rc.d <service> default to get it on the runlevels, then enable/disable to do fun things. Only do update-rc.d remove when the package is removed from the system.. Gotcha

Take that systemd (?)

｢ The biggest change in SysVinit 3.14 is overcoming the 127 character per line limit of inittab files that has been there for roughly the past three decades. With SysVinit moving forward, inittab lines can be up to 253 characters long... Those with really long inittab lines are really best off punting off that logic to a shell script that can then be called from the inittab ｣

https://www.phoronix.com/news/SysVinit-3.14-Released

@krishean that's not how #systemd works.

SystemD was created because #SysVinit was shit and noone fixed it or made something better.

• Same with #PipeWire: #ALSA & #OSS are really janky!

#Wayland is the future as #Xorg is being #EoL'd.

• #Linux as a Kernel works fine, so no reason to replace it.

For the shitty #GlibC we have alternatives like #bionic and espechally #musl!

https://www.youtube.com/watch?v=o_AIw9bGogo

@joel I mean, #SystemD wasn't done by #Poettering because he had no hobbies - far from it.

• #SysVinit sucks and #Linux needs to modernize and change solely because many components like #Xorg, #OSS / #ALSA and #OpenGL are to be retired or are already only on life support.

SystemD, like #Wayland and #PipeWire is a "necessary evil" because the preexisting solutions are slow, not adaptive, cumbersome or just don't work well at all (i.e. mixed (#DPI & #HiDPI) screens with #X11 are just broken!

• People had years if not over a decade to fix those but they didn't and it's clear that a new & clean slate was necessary...

I think I've become spoiled and/or too accustomed to #Systemd, because last Thursday I tried to switch my home server (an old netbook) from #Debian to #Devuan and I failed miserably. Not because it was too difficult, but because it was... tiring.

See, like many #Linux users, I like to mess around with computers and learn new things, but at this stage in my life I have other things to think about instead of configuring #sysvinit and learning again how to set up a service to run without login.

Change Between #sysvinit and #systemd in #MXLinux

https://itsfoss.com/mxlinux-sysvinit-systemd/

SysVinit: The Traditional Approach
SysVinit, the traditional init system used in UNIX and Linux systems, has been around since the 1980s. It follows a straightforward approach to system initialization: it runs a sequence of scripts in a specific order to bring the system to a usable state.

More and Complete at: https://machaddr.substack.com/p/systemd-sysvinit-runit-and-openrc

Been playing a little with #antiX currently. Really need #Debian based system. That good old #sysvinit feeling (#runit is also offered)
#Debian sure comes in many forms

#SysVinit 3.10 Resolves Bootlogd Loop Issue

https://linuxiac.com/sysvinit-3-10-resolves-bootlogd-loop-issue/

@nuintari @stefano no, it's not inherently bad because if #SysVinit and all the.otherbthings were fine, noone would've even considered adoping #systemd.
https://infosec.space/@kkarhan/112660144122509736

Claiming "it's #RHEL's fault" also goes way too short, cuz they - like #SUSE and #Canonical - do weird stuff all the time.

• Unlike say #snap vs. #flatpak, there's a reason we have systemd and no say #upstart being adopted.

OFC you can get non-systemd distros and for #embedded applications, the tradeoff of "space" vs. "complexity reconfiguring" stuff does make even a classic init script sufficient (i.e. some #InternetOfShit device that isn't expected to constantly switch WiFi networks doesn't need a config more complex than the config
txt from #RaspberryPiOS)...