▲ 345 ▼ Bazzite sees a massive jolt in installs in late June and early July, catapulting it to over 86k active devices. It has doubled the number of active devices since November. (lemmy.ml) submitted 3 weeks ago* (last edited 3 weeks ago) by marcie@lemmy.ml to c/linux@lemmy.ml 93 comments fedilink hide all child comments 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.
[–] ranzispa@mander.xyz 3 points 3 weeks ago (1 child) I see, that is a really nice feature! No idea why this is not something already safely handled my normal package managers. permalink fedilink source parent hideshow 2 child comments replies: [–] hperrin@lemmy.ca 8 points 3 weeks ago* It’s cause of the way an immutable system works. In an immutable system, the entire system is an image. Two are stored on disk. One is active, and the other is usually the previous image. When you update, it overwrites the old image. The current image stays untouched. It’s only once the new image is completely written to disk that it’s marked as the current image. Package managers are working on the currently running system. They write over the only set of system files, and they can only do that one file at a time, so you can rely on the file system’s journal to make sure each file is correctly written, but there’s nothing preventing the system from being only half updated. If a package relies on a package that hasn’t been installed yet, and the update fails before it gets installed, that package is broken. In a system like Ubuntu or Fedora, that’s mostly ok, because packages are always built for the kernel and library versions available throughout the lifecycle of the release. So a half updated system is probably fine and will continue the update when rebooted. But for rolling releases like Arch, or for a release upgrade like Ubuntu 25.10 to Ubuntu 26.04, a failed update might mean a broken system. permalink fedilink source parent
[–] hperrin@lemmy.ca 8 points 3 weeks ago* It’s cause of the way an immutable system works. In an immutable system, the entire system is an image. Two are stored on disk. One is active, and the other is usually the previous image. When you update, it overwrites the old image. The current image stays untouched. It’s only once the new image is completely written to disk that it’s marked as the current image. Package managers are working on the currently running system. They write over the only set of system files, and they can only do that one file at a time, so you can rely on the file system’s journal to make sure each file is correctly written, but there’s nothing preventing the system from being only half updated. If a package relies on a package that hasn’t been installed yet, and the update fails before it gets installed, that package is broken. In a system like Ubuntu or Fedora, that’s mostly ok, because packages are always built for the kernel and library versions available throughout the lifecycle of the release. So a half updated system is probably fine and will continue the update when rebooted. But for rolling releases like Arch, or for a release upgrade like Ubuntu 25.10 to Ubuntu 26.04, a failed update might mean a broken system. permalink fedilink source parent
