this post was submitted on 21 Jun 2026
64 points (80.8% liked)
Linux
65904 readers
567 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Out of curiosity, as someone who's never used Bazzite/other uBlue/SilverBlue/etc, what makes it difficult for new users? I definitely agree with Nix and Qubes though (and SecureBlue to some extent).
Basically, anything that isn't packaged as a flatpak needs to be installed from the CLI using distrobox containers, which will go over the heads of the majority of new users.
I can’t tell you how many times I’ve had to bonk the immutable Stans over the head with this logic, but it never works. They install bazzite, play their game of choice on steam and occasionally use their web browser and “ALL NEW USERS MUST USE BAZZITE ITS SO EASY”
Any distro is easy when you use it like a fucking Sony PlayStation.
Lol, but so true.
Not Arch or NixOS lol
Can't you use homebrew?
You can and it works very well now
I have zero experience with that. 😄
FWIW, uBlue has been brewing for almost three years now for their CLI stuff: see this issue tracker and this blogpost from Bluefin's creator.
The distrobox workflow overall has mostly been superseded by better alternatives^[There's sysext with its (WIP) manager, Brew Tap to tap into homebrew casks and some peeps even use coldbrew. And last, but definitely not least,
nixsupport has improved over the years. And if you just want to usednf, RakuOS' innovative hybrid design allows just that; an image-based core you can't touch (like the other 'immutables'), butdnfworks and is applied through a persistent overlay.]. Though, for completeness' sake, openSUSE's atomic offering continues to heavily rely on Distrobox. But, in their defense, I think their atomic offerings are simply better^[Fedora's container images are tied to its major release versions. Hence, every 7-13 months you're required to set them up from scratch if you'd like to continue using them 😅. Even if this process can be streamlined, it's IMO very cumbersome regardless. In openSUSE's case, the containers are based on Tumbleweed. Which, has a rolling release cadence. Hence, it was meant to be used indefinitely.] suited for it.Thank you very much for the detailed and well-sourced write-up! I've saved it for later when I get to drill down on this.
It kind of proves OP's point though: distros do come with a lot of idiosyncrasies of "how things are done around these parts".
It has been my pleasure 😊. I really appreciate your kind words 🤍.
Absolutely. But, I think it's nuanced and the lines are becoming increasingly blurry. If something based on Fedora can become something based on Arch (and vice-versa), if almost any distro has multiple releases/channels/braches, if software for/from any distro can be installed on every other distro, then... at what point is it truly "around these parts" rather than "with those not-hardcoded system specifications"? Kinda like how DEs can be (un)installed, and how those come with implications on how some stuff is done...
There's a ton of added friction when doing things outside the basic 'install Flatpak app'. Security generally comes at the price of being difficult to use.
For new users it also means virtually every guide or there on fixing an issue or installing extra software won't apply.
If you install home brew 90% of the issues go away.
The problem is that most Linux software assumes it can do whatever it wants, and immutable distros do not let you write to the system files.
This creates confusion, because you see a guide for Fedora and it said
dnf install xyz, but dnf doesn’t work. The solution is to add it to your image tree (no) or to create a toolbox with that package (complicated, requires setup, gets complicated if your tool needs access to Wayland for clipboard or something).Bazzite solves this by using brew, which is a package manager built for macOS which has had immutable systems for years. Brew solves most of the issues.
For me by the time I went immutable it just made more sense to go full declarative with nix, but nix is also a steeper learning curve.
Not the one you asked, but I think the answer lies in the bold part:
For example, I can't imagine any of the uBlue projects causing major difficulties. Though, edge cases do exist; adding kernel mods can still be a bitch, even if there are efforts to improve this.