Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
CachyOS does this just fine with bootable BTRFS snapshots before and after each update, without forcing me to use Flatpaks that don’t support all of the features of the normal apps or else break the immutability. For example, it’s not possible to get all Discord features working in Flatpak (even with tinkering) due to inherent limitations of Flatpak.
The real problem is config drift. You have to maintain a lot of little fixes over time as you operate vanilla Linux. I’ve run fedora atomic (and rebased to bazzite when it got fairly big) since it launched years ago with only one relatively minor hiccup that was resolved by a single line in terminal (rpm-ostree rebase). You can layer stuff over it to modify the base image and clear it if something breaks, whereas manually removing critical packages and being sure to clear every file would be a nightmare on any other distro. It’s an extremely hands off experience that works just like git does and is very bullet proof and reproducible.
I like putting it on old people’s computers. It’s perfect for a seamless experience.
It’s a little more effort to maintain compared to something like nix, but Arch (including CachyOS) doesn’t have the same config drift problem as distros like Debian, because it has pacdiff to let you consolidate any updated defaults with your own settings.
Yeah, a file system snapshot is another way of achieving safe upgrades. There are upsides and downsides of all approaches though.
Rolling back to a btrfs snapshot might be harder than just picking the other ostree image in GRUB. And you still have the problem where old binaries might be running when only the new binaries/libraries exist on disk. But it also saves space on disk compared to an immutable distro, and it’s much easier to make changes to system files. Every approach is a compromise.
It’s literally just picking which snapshot you want to boot in the boot loader and then accepting the prompt to make that one the new default after you’ve verified it works. It’s not possible for old binaries to be running.
I’m talking about when you update the system. Unless you reboot to do the update, the system can be using outdated binaries until you reboot. Apt will tell you about them, but I don’t know about other package managers.
Yeah rolling back snapshots is way more annoying than ostree and is kinda a shotgun solution. Also ostree saves more disk space.