Yeah that option doesn’t work for me either, tried to remove plasma de but only the plasma-de bundle was removed.
So, Chris Titus was right, after all.
That’s not how that works! ![]()
If you would see his video now for the first time, you can’t disagree.
I am devastated. ![]()
What do you guys recommend instead? Which distro would be closest to CL please?
- stateless
- immutable (is this the same thing as “stateless”?)
- rolling
- systemd boot
- Wayland
- GNOME
Hmm… I think this hits your spot: https://projectbluefin.io
I will not use anything Gnome-related, also not touching anything Debian-based.
Also, I am searching for more server uses.
It will be uCore, Alpine, or Rocky Linux. I have to see how I feel. Each option has its pros and cons.
But all of the options would work.
Alpine is simple. Almost too simple.
Rocky Linux is based on RedHa… IBM.
And uCore… that’s… I’m not sure if I can see the red line. The more I read, the more tedious it seems. I’m not sure if the developers themselves know what they want / wanted to achieve.
Thanks. I don’t think Bluefin is rolling though. Is it?
It’s based on fedora silverblue. At least it’s the same family…
It’s all points you mentioned, also “rolling”.
Fedora Silverblue is not a (true) rolling release.
Another option for you :
If you don’t mind the atomic requirement, just a very solid german rolling distro, try :
Thanks. blendOS looks fantastic indeed! Bluefin (a semi-rolling distro recommended by @pamalosebi) also looks great. I know Manjaro, and like it too, however, at this point in time, my order of preference would be:
- Aeon (cannot be installed w/Ventoy, which is a pita)
- Bluefin
- blendOS
[Edit: the more I read, the more I become convinced that I should start off with blendOS instead of Aeon!]
I follow BlendOS since a while.They have the same issues as VanillaOS. In this list you can add RegataOS, Aeon… Aeryn…
Which is stability. Mostly through small community size (which leads to less testing) and / or small team of devs.
Nobara for example, also has just one main dev… But they grew a big community. That made it really stable very fast. With many hands testing things out.
I am not sure why Fedora Silverblue is not rolling. I will have to check the definition for “rolling”.
With silverblue (or based on) you will never have to deal with major updates. Like Fedora 40 → 41. And you get all the new stuff very fast… isn’t that “rolling”?
And no “rolling” issues whatsoever.
Rolling distros have their own negatives too (nicely dealt with by Manjaro).
If you want community + immutable + stability, you can’t beat Silverblue.
If you want community + rolling + stability, Manjaro is a solid choice.
But as Manjaro slightly delays updates to prevent problems, they are almost similarly up to date.
Estimated community members :
| Distribution | Direct Estimate | With Ecosystem Overlap Considered |
|---|---|---|
| Nobara | 500–2,000 | 500–2,000 |
| Fedora Silverblue | 10,000–25,000 | 50,000–100,000+ (Fedora total) |
| Manjaro | 20,000–60,000 | 20,000–60,000 |
| BlendOS | 200–1,000 | 200–1,000 |
| Clear Linux | 2000-3000 | 2000-3000 |
Still in testing stages, but eventually…
Alright guys, so I am ready to pull the trigger; here’s the question: if you were to choose today between the following, and were primarily interested in (a) stability and (b) access to applications, which one would you go for?
- Aeon
- Silverblue
- Bluefin
- blendOS
Just name one please. Many thanks!
Manjaro
(a) The most stable rolling distro
(b) Access to full AUR, almost any application you can imagine
-
An immutable Linux OS limits user flexibility, making custom configurations or installing third-party software more difficult.
-
Security through immutability can create a false sense of safety, while vulnerabilities in read-only images or containers can still be exploited.
-
Recovery from corruption or misconfiguration may be harder without writable layers or traditional state tracking.
-
Updates in immutable systems are often atomic and OS-wide, which can introduce downtime or break dependent user applications unexpectedly.
-
Immutable systems can still be compromised if an attacker gains root access and tampers with runtimes or in-memory processes.
Immutable doesn’t mean immune ![]()
You’ve missed the “between the following” bit ![]()
(Not to mention that Manjaro is not (yet) immutable.)
