[4ggr0]

> rpm-ostree is a PITA

yup...at first i thought, "at work i have to manage rpm-ostree servers, so why not use the same tech at home?", well, because the tech is freaking buggy, annoying and deprecated already (imagemode/bootc).

Bazzite also had strange issues with the XBOX controllers i use, those issues went away with CachyOS. in the end it doesn't matter that much, on both i use(d) KDE Plasma. GF also uses the PC with her own useraccount to play her games. overall very satisfied, can't complain.

don't lynch me, decided to go for the pretty standard instead of Sway or Hyprland, as i feared that this would bring more issues with gaming. maybe that's an irrational fear, who knows.

[hollerith]

Bazzite is built using imagemode/bootc; is it not?

I'm trying to understand the "deprecated already" in your first paragraph. (All I know about rpm-ostree is from using and adminning a distro that relies on rpm-ostree. I.e., I don't know much.)

Here is my guess as to what you mean: Bazzite could continue to use imagemode and bootc while replacing rpm-ostree with something better, and maybe you'll give Bazzite another look after that happens.

[4ggr0]

Fedora Atomic and RHEL used to ship with rpm-ostree, new versions are now using bootc. the base philosophy is still to ship the OS as an image, but bootc goes more into layering like docker-images, so that you can deploy changes a bit more easily/dynamically.

they're different technologies with bootc being the new kid. bootc means "bootable containers". rpm-ostree has not much to do with containers and is more like managing your OS with git-logic.

forget about "imagemode", that's the marketing-term RedHat uses for bootc.

i imagine bazzite will migrate to bootc sooner or later, but of course that requires a new way to build and ship it.

[hollerith]

Bazzite is part of Universal Blue. Source: https://universal-blue.org/#images.

The first paragraph of the home page of https://universal-blue.org/ ends with "We produce a diverse set of continuously delivered operating system images using bootc."

Another author explains: "Bazzite utilizes bootc to manage the base image for your system, pin specific versions, and perform rollbacks when needed. For systems with customized software via layered packages, rpm-ostree becomes essential for installing, upgrading, and managing those additions."

"Why do this? Each tool is chosen for its strengths: bootc offers robust control over base images, ensuring that your core system remains unchanged unless you explicitly update it, while rpm-ostree provides flexibility for managing additional software without compromising the integrity of the atomic base. This separation helps maintain stability and security. Bazzite uses bootc for managing system images and rpm-ostree for adding layered packages."

Source: https://knowledgebase.frame.work/en_us/how-to-manage-bazzite...

Of course, nothing I wrote contradicts your assertion that rpm-ostree "is freaking buggy, annoying", but it does cast doubt in my mind on your belief that bootc can by itself completely replace rpm-ostree.

Thanks for your reply.

[4ggr0]

oh, oops, thanks for correcting me in that case! turns out i know even less about that stuff than i thought...