I know many people who run with microos based things, they set up nightly updates and if it updates it auto reboots.
and for the pixls.us infra I reboot or restart things when ever things got updated. I made sure that the outages are short but I will not wait for rebooting. that gets done every time right away. if people want HA, they can donate and/or help maintaining the infra to make it HA.
99.99% availability seems to be doing fine so far 
For desktop usage I am OK with having to reboot occasionally, and I donât mind doing it for kernel updates, since those are comparatively rare. But doing it multiple times a week would be a PITA.
That said, both Ubuntu and Red Hat offer livepatching the kernel these days as an enterprise feature (for Ubuntu there is a free tier, donât know about RHEL).
In any case, from my perspective the immutable base distro concept creates more problems than it solves; a plain vanilla package based distros of any flavor (Debian, RH, âŚ) work pretty seamlessly for my purposes. But I understand it is a personal preference.
Which is precisely why I avoid immutable distros. (I used to use Fedora, until they started going so strongly toward immutability.)
At least for me the concept works great but everyone has their preferences. I run fedora atomic (bazzite) and run topgrade on startup. Updates happen in the background and I shut down my devices every day so the next base image update will be online without much delay. Compared to vanilla Fedora where I regularily checked for updates and got frequent reboot prompts this is a relief. Also on my HP Omen Notebook bazzite runs way better then Workstation, which had all shorts of minor issues.
Aurora is KDE only, the Fedora atomic variants with gnome are Silverblue and Universal Blues bluefin image.
Not sure what does it mean. I run Fedora almost exclusively and I donât even know what is immutability in distros. Standard Workstation plus XFCE work fine for me.
Thank you, I should have said I donât know them because I donât want to use them in any way.
For a ton of people it might actually be the proper solution. TBH i would probably still stick most of the apps into the base image instead of flatpak or appimage.
For many people who just want to use their computer it will be 100% the perfect setup. if you want to tinker maybe not so much.
e.g. if my non techie family parts want to have a linux i would mostlikely go down that route because it will be the safest appraoch for them.
afaik in microos we have an automatic failsafe that it boots the previous snapshot if the new one does not work.
so they will always be back in a safe state and i can debug.
so do not discard that idea too early. it has its merits.
Thanks! I was about to ask. I had no what immutable meant In this context.
Hi Tamas-
Aurora is KDE only. There is also a similar platform called Bluefin which is the Gnome version.
You all want Tumbleweed anyway. you just dont know it yet.
There are choices within the platform as to when you get updates. I go with the weekly, which usually shows up Sunday. My computer is on all the time, but I shutdown Sunday evening and the new update shows up on boot.
In use, the updates are unobtrusive. It takes a cmd line entry to see whether one is available. In the KDE version, the updates available indicator in the status bar shows if there are firmware or flatpak updates. No action needs to be taken as they will also update.
Thanks, I am using Sway, I think Fedora has an atomic spin for that but for the time being I will stick to plain vanilla packages. I am keeping an eye on the technology though.
Linux Mint seems to be the least annoying distro for me.
Linux Mint (MATE desktop with Compiz and Emerald) works for me, as an aesthetic and practical combination. I wonât change unless I really have to, eg Mint changes, like Ubuntu did once.
When I have something that suits, I donât change.
I used to use the same combination, but the lack of easy colour profile management in Mate put me off using it.
I havenât reached the understanding/need of that as yet.
Preferably users shouldnât have to worry about things like these, so when I started using Aurora I decided to leave auto updates turned on and just go about with my life. Iâve attempted to not think about rebooting or updates to see what happens if I donât. Apparently updates happen, but I donât notice them. I probably shutdown my computer once a week or so. This behavior has not caused me any trouble AFAIK. Everything just worksâ˘ď¸.
From what I understand, the atomic update model is specifically designed to be safe and non-disruptive, so you have flexibility in when you reboot. But Iâm just a photographer running Linux. Please correct me if Iâm wrongâŚ
If you want, you can turn off automatic updates and run ujust update before youâre ready to reboot and and system, Flatpaks, and Distroboxes (with the packages installed inside the Distroboxes) are updated all at once.
Seems nice. Would have been a good option if there was a Plasma version.
I used non atomic/immutable distros in an atomic fashion before I switched to Aurora. I ran Manjaro and Tumbleweed with software via Flatpak and Homebrew.
I do not want my OS package manager to share dependencies and packages between the stuff I install as a user and the OS underpinnings; it has always seemed wrong to me. Iâm happy that the atomic/ostree approach has matured so much during the last years.
This is funny, Iâve been using Aurora for over a year and I booted up my old laptop, which still runs Tumbleweed, only to reply to this thread . While booting I thought to myself: I probably shouldnât be writing anything about how much I disliked Tumbleweed; so I wonât.
