😂. No worries fam.

I’m so confused now as I’m trying to understand why you answered that way 😅.

But, if I understood you correctly, you didn’t refer to Silverblue and Kinoite as immutable, because it is possible to apply changes to them and these changes will even stick through reboots etc. Hence, you don’t deny that some parts are (in fact) deniable, but find that Atomic simply better describes what these distros actually do. And thus are better suited to set up the right expectations.

But, allow me to ask the following question then; do you think NixOS is immutable?

So, you referred to immutable in the absolute sense? If not, would you be so kind to mention distros/systems that you actually refer to as immutable?

Thank you for clarifying what you didn’t write nor mean. Could you be so kind to explain what you did mean with what’s quoted below?

Those are not immutable, especially on the file system.

For grannies, I like to go with Endless OS. Curiously, it combines aspects of the two most named distros under this post; based on Debian and utilizing OSTree (like Fedora Atomic does).

It’s often overlooked (for some reason), but actually combines the best of both worlds:

• Over two years of support (since release), while Fedora Atomic only offers 13 months of support since release
• Automatic updates are enabled by default and updates are applied atomically in the background, while Debian(-based) are not capable of atomic updates
• Does not even offer installing software through apt and doesn’t even have it’s own rpm-ostree counterpart. Instead, it goes all-in on Flatpak.

The only thing that might give something like Fedora Atomic an edge would be by installing any of the opinionated uBlue images (like Aurora/Bazzite/Bluefin etc.) that just apply and ship fixes for you (without requiring you to do anything for it) and that are even capable of automatically applying updates to major releases for you in the background. This is basically just hands-off mode.

So you’re saying that most directories in /usr and (also) some other directories in / are not read-only during runtime (under regular system maintenance/management) on Fedora Atomic?