In recent weeks, systemd has both embraced slopcoding and laid the groundwork for age verification built right into systemd-based Linux distributions, there’s definitely been an uptick in people talking about alternative init systems. If you want to gain understanding in a rather classic init system, OpenBSD’s is a great place to start.
OpenBSD has a delightfully traditional init system, which makes it a great place to start learning about init systems. It’s simple and effective. There’s a bit of a counter movement in the IT and FOSS worlds rebelling against hyperscaler solutions pushing down into everyone’s practices. One of the rallying cries I’ve been seeing is to remind people that You Can Just Do Things™ on the computer. The BSD init system, and especially OpenBSD’s is something of a godparent to this movement.
↫ Overeducated-Redneck.netinit(8)just runs a shell script to start the computer, and You Can Just Do Things™ in the script to get them to happen on boot.
My main laptop is currently in for warranty repairs, but once it returns, I intend to set it up with either OpenBSD or a Linux distribution without systemd (most likely Void) to see how many systems I can distance from systemd without giving myself too much of a headache (I’m guessing my gaming machine will remain on systemd-based Fedora). I’m not particularly keen on slopcoding and government-mandated age verification inside my operating systems, and I’m definitely feeling a bit of a slippery slope underneath my feet.
I have my limits.
This was the same in Slackware.
(My very first Linux. Though there was no Debian or Redhat back in those days)
There is a basic init (sysvinit?, which is actually based on BSD variants), and for everything else you want to do, there is /etc/rc.local. All others, including the user database are still text configs under /etc.
Now, is everything as easy, and plug and play like systemd? Not of course. It won’t renegotiate your network daemons if you switch from cable to wireless, or update your primary printer automatically based on location without some work. At least out of the box.
But everything is possible. One can actually do all those.
I think we will need to go old school. I have been tolerating systemd, as I did not like their methods, but the goals were acceptable. But that no longer holds true after they are shoehorning user tracking, and unique machine id fingerprinting, and giving up on privacy.
Edit:
I googled for modern “systemd-free” distributions, if Slackware is too old school. (Though it is still alive)
Without any ranking: Devuan (a debian clone), Void, Alpine, and Artic (Arch clone?).
I would also include Gentoo, which … is technically not systemd-free, as it allows you to build your own distribution in your way. But of course one can choose OpenRC instead.
On my ThinkPad W530 (and 4 sticks of RAM), FreeBSD lasts for 5h doing actual work on a battery that currently holds 51W of capacity.
Yes, it won’t autonegotiate anything, but in openbox I get a very nice right click menu with the networks that I have configured and when I want to switch from wired to wifi, I right click, point to network, pick the interface. Bonus for not having wifi broadcasting discovery requests every time.
It is incredibly smooth, there’s almost nothing running in the background (making the system incredibly responsive). Less crap in the background means more time with the CPU in low power states. Two weeks ago, I moved my ThinkPad P1 Gen 4 to Debian just because I was already getting too annoyed dealing with the hybrid GPU situation (can’t fully disable the NVIDIA), and having to figure out ACPI calls to keep it off, etc.. the battery was not lasting long but I am hoping it will get better with time.
You only install what you need, making the system very smooth. Even KDE on FreeBSD is quite a pleasant experience, even though half of the widgets won’t work. =)
So yea, autoconfigure plugandplay everything and live with the life of bloat or spend a day or two setting it up and have a way smoother system? That’s the dilemma. If manually configuring things would be easier for people who are not tech experts, I think many people would be happy to spending a day setting things up and not worrying that things will go belly up.
Last week, my P1’s Windows installation went belly up (Started BSOD-ing after an update) and I am working from a VM in VirtualBox. Won’t even boot in safe mode. -> if we can give non-technical people a computer experience devoid of this crap, would be great.
Shiunbird,
Yes, this is a pain, and even on my AMD APU with AMD discrete GPU, I had something similar. The iGPU is not directly wired to the displays anymore, and all output has to go through dGPU, even if you are not actively using it or gaming or something else.
It used to be the opposite, but then the gaming performance was not great. Now the dGPU is always on, and consumes power draining the battery.
(Way back in time there was a hardware switch for output, none of these shenanigans were necessary)
I have not used them, but for nvidia, there seems to be tools like supergfxd if you want to give it a try. They claim to be able to manage power states better.