mr_MADAFAKA@lemmy.ml to Steam Deck@sopuli.xyz · 7 months agoSteamOS 3.6: How the Steam Deck atomic updates are improvingwww.collabora.comexternal-linkmessage-square20fedilinkarrow-up1112arrow-down12cross-posted to: [email protected][email protected][email protected]
arrow-up1110arrow-down1external-linkSteamOS 3.6: How the Steam Deck atomic updates are improvingwww.collabora.commr_MADAFAKA@lemmy.ml to Steam Deck@sopuli.xyz · 7 months agomessage-square20fedilinkcross-posted to: [email protected][email protected][email protected]
minus-squarewarmaster@lemmy.worldlinkfedilinkarrow-up2·7 months agoSo, desync should end up in Bazzite too, right?
minus-squareSuperIce@lemmy.worldlinkfedilinkEnglisharrow-up5·7 months agoBazzite uses rpm-ostree. It’s a very different system under the hood.
minus-squarewarmaster@lemmy.worldlinkfedilinkarrow-up2·7 months agoBut Steam OS is inside a container. Wouldn’t that container be using desync now?
minus-squareSuperIce@lemmy.worldlinkfedilinkEnglisharrow-up8·7 months agoYou seem to have a misunderstanding of how Bazzite works. It’s just a custom Fedora Atomic spin that includes things like the deck firmware updates, drivers, and gamescope. It does not run SteamOS in a container.
So, desync should end up in Bazzite too, right?
Bazzite uses rpm-ostree. It’s a very different system under the hood.
But Steam OS is inside a container. Wouldn’t that container be using desync now?
You seem to have a misunderstanding of how Bazzite works. It’s just a custom Fedora Atomic spin that includes things like the deck firmware updates, drivers, and gamescope. It does not run SteamOS in a container.