That systemd Thing: A Debate With No Ending

https://eggflix.foolbazar.eu/videos/watch/dd6ab9d5-1ef9-4c35-91fa-e0885a1bcf50

Ok fam, after about a week of being a complete and utter newbie ingesting tutorials about #Linux I think I am finally understanding two things: what distros are, and that for some reason my brain will correlate ANY technical topic with food.

Linux is ice cream
Linux families are particular flavors of ice cream
And like ice cream, there’s basically certain core flavors, many specific flavors, and always the potential to invent new flavors. The ice cream landscape seems to break out something like this to a newbie:

Vanilla - Debian; French Vanilla - Ubuntu; Vanilla Bean - LMDE
Chocolate - Red Hat; Chocolate Chip - Fedora; Chocolate chocolate chip - Alma;
Fruit, Strawberry - Arch; Fruit, Peach or Cherry or pretty much any other fruit - any other Arch
Caramel - Gentoo; Vanilla Caramel Swirl - Redcore
Neapolitan and Spumoni - When you do super custom stuff like make Ubuntu have rolling release distro using Arch’s package system with Gentoo’s OpenRC for the init system
Exotic, like cucumber or ranch or avocado - Everything else that isn’t one of the other big buckets like SUSE, Solus, Quirky, LFS, Zeroshell, Vine, etc.
Nuts - Slackware (I mean this in an affectionate way, butter pecan is my fav!)
Gelato - BSD
Chocolate Gelato - Solaris

Like ice cream, Linux can have toppings too:
Sauce - init systems; and some people hate chocolate sauce - systemd
Whipped cream. Yeah sure there’s different brands and differences in texture or flavor a bit, but they’re basically all doing the same stuff - Packaging
Cherry - the GUI. It’s only there for looks, you could absolutely eat the ice cream without it, but most diners expect it on their sundae

Distros - An ice cream sundae. All the things (flavor, toppings, what it’s served in) are presented to you at once. Oooor some of the more lean ones are more like an ice cream cone
Eating a pint of ice cream right outta the freezer container - CLI

I'm now gonna try Arch Linux with inits I haven't tried/not yet familiar. I'm curious how it'll all go, lol.

I'm open for any suggestions on what inits to try other than OpenRC, runit, dinit, s6, and sysvinit cos I've already done those, but I'm also open to hear your thoughts and if I should also try them on Arch as well.

#arch #archlinux #linux #opensource #freesoftware #foss #busybox #openrc #runit #dinit #s6 #s6-rc #sysvinit

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

7 seconds. Not bad, but look at that RAM usage...

220 MiB ! That's actually lightweight!
530 MiB with xorg+xfce 4.18. Still lightweight !

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

How To List All Running Daemons In Linux #Linux #Daemon #Process #Initsystem #Systemd #SysVinit #OpenRC #Linuxcommands #Linuxbasics #Linuxhowto #Linuxadministration
https://ostechnix.com/list-all-running-daemons-in-linux/

@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...