428

So I took the plunge and installed Fedora Silverblue because of all that immutable buzz. And it's the most frustrating change I have made in almost 20 years of my distrohopping.

After installing Silverblue I configured it as usual. I installed necessary flatpaks, played with toolbox and distrobox, installed codecs, configured my bluetooth keyboard and other stuff in /etc and /var. Applied some useful tweaks I found on the web and... well... everything works. Nothing to do anymore. No issues. Nothing breaks, no dependency hell, everything runs smooth. I have nothing to tweak, tinker or configure anymore. So frustrating.

Every update is just... meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking. Booooring.

I don't have to distrohop anymore. If I want other distros I can just install them in distrobox. Other versions of apps? Something from AUR perhaps...? No problem. What's the point of distrohopping now? Other DEs? I just rebase my system to other images with almost any DE or WM I want without losing data or messing everything up (damn you, UBlue!).

I don't even have to reinstall the damn thing cause every time I update the system or rebase it to another image it's like reinstalling it.

Silverblue killed distrohopping for me. Really frustrating.

you are viewing a single comment's thread
view the rest of the comments
[-] Telorand@reddthat.com 6 points 3 weeks ago

It's immutable (aka. atomic), which means the system files cannot be changed, even by root. System updates come as complete system snapshots of the core filesystem, and everything else exists in containers or filesystem overlays (user directory is still writeable). Containers and the user's home directory are unaffected by the updates, so the update process is typically much safer overall.

If an update does break something, you can easily do rpm-ostree rollback, and everything will be working again. On top of that, you can swap between versions with a simple rebase command (e.g. swap between Silverblue and Kinoite, Kinoite and Bazzite).

[-] biribiri11@lemmy.ml 5 points 3 weeks ago

It’s immutable (aka. atomic), which means the system files cannot be changed, even by root.

This is a definite “well um actually” moment, but technically immutability can be switched off at any time with chattr, and “true” immutability will not be achieved until full image signing is commonplace. You can see the ideas laid out here: https://github.com/ostreedev/ostree/issues/2867

It does let you do cool things though, like install nix: https://github.com/dnkmmr69420/nix-installer-scripts/blob/main/installer-scripts/silverblue-nix-installer.sh

[-] Vilian@lemmy.ca 1 points 3 weeks ago

don't use that use this https://github.com/DeterminateSystems/nix-installer

up-to-date, full support silverblue, don't need to unlock the filesystem, full support for selinux too, they create the /etc/nix forlder and mount it on /nix

[-] biribiri11@lemmy.ml 1 points 3 weeks ago

Yeah, I was just linking the other one because its usage of temporarily disabling immutability is more apparent. That one also disables immutability temporarily to install nix.

this post was submitted on 09 Jun 2024
428 points (94.0% liked)

Linux

45530 readers
2087 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS