s6 VS ublue

A (rare) good critique to systemd can be found here. Written by the developer behind s6, which happens to be scheduled to replace OpenRC on Alpine Linux. For completeness-sake, some of the main reasons why Alpine doesn't prefer systemd do not apply on most other distros.

It got mass-adopted while being imperfect, so that's to be expected. Thankfully its inception and the criticism that followed have paved the way for the likes of dinit and s6.

this page and this page, both by Laurent Bercot, creator of s6.

Of the two I have experience with, runit is simpler and thus easier to get the hang of than s6-rc/s6. Though the s6 (not s6-rc) docs at the author's site contain a lot of info (including apologetics and rationales) that applies almost equally well to runit

systemd: Yes; it's awaiting its "PipeWire". Thankfully, the likes of s6 and dinit are very promising. Though I can actually appreciate that systemd is addressed. As ultimately it helps in raising awareness that will benefit whatever software will replace it eventually.

Arguably this is less troublesome to solve compared to the other concerns. As we're inevitably waiting for the system supervision suite that will be to systemd what PipeWire has been to PulseAudio. I'm very optimistic about this as both s6 and Dinit are shaping up lovely.

Using the s6-service add command I added a service called "libvertd" when I ment to put "libvirtd". Now when I run s6-db-reload it spits out a error message saying "undefined service name libvertd". But I cant remove it using s6-service remove libvertd because that just spits out a generic help message and doesn't change anything. I also couldn't find documentation on https://skarnet.org/software/s6/ or https://skarnet.org/software/s6-rc/ as the command just *doesn't* exist on those pages. (also no man or info page).

I myself use Fedora Silverblue with a https://ublue.it/ -based custom image, and I use home-manager for shell configuration. Sure, my GNOME layout isn't declarative, but basically everything else is. Pair that with one of the best NVIDIA driver experiences and the strong feeling of stability, it's better than most other Linuxes rn.

Take a look at ublue.it

This is a fundamental misunderstanding of immutable systems. You still have full control over what’s on your computer, you just don’t exercise that control by making irreversible changes to your core system while it’s running. You can use e.g. rpm-ostree, or even better, build a custom image with exactly the changes you want that updates and ships directly to your computer whenever you want it to.

Have you considered the Sericea(Sway) immutable Fedora spin at ublue.it?

Have you considered the nvidia images at ublue.it? They make silverblue and nvidia easy.

Try the ublue images, they have one for deepin. It’s a variant on fedoras immutable silverblue image, you could either use their iso on http://ublue.it or install silverblue and rebase to the deepin image via:

ublue.it

This is indeed a blind spot. Thanks for pointing that out! Silverblue -to my knowledge- doesn't do a lot to address this. Though, 3rd-party tools like Home Manager and the suite of applications developed by the folks over at uBlue might be able to limit this to a minimum. Though I'm not sure if it surpasses NixOS in this regard; for the uninitiated. Though, to my knowledge, this requires special attention and depends on the specifics of the NixOS system in question.

This hasn't been for nought as even openSUSE's Aeon (and all their immutable offerings) ship Distrobox instead. Vanilla OS also ships Distrobox instead of Toolbx. Heck, even the folks over on uBlue\1]) always mention Toolbx with Distrobox and vice versa. And it wouldn't surprise me if most of them prefer to use Distrobox instead.