@mr_MADAFAKA@lemmy.ml to Steam Deck@sopuli.xyz • 2 months agoSteamOS 3.6: How the Steam Deck atomic updates are improvingwww.collabora.comexternal-linkmessage-square20fedilinkarrow-up1112cross-posted to: steamdeck@lemmit.onlinesteamdeck@lemmy.mllinux_gaming@lemmit.online
arrow-up1112external-linkSteamOS 3.6: How the Steam Deck atomic updates are improvingwww.collabora.com@mr_MADAFAKA@lemmy.ml to Steam Deck@sopuli.xyz • 2 months agomessage-square20fedilinkcross-posted to: steamdeck@lemmit.onlinesteamdeck@lemmy.mllinux_gaming@lemmit.online
minus-square@warmaster@lemmy.worldlinkfedilink2•2 months agoSo, desync should end up in Bazzite too, right?
minus-square@SuperIce@lemmy.worldlinkfedilinkEnglish5•2 months agoBazzite uses rpm-ostree. It’s a very different system under the hood.
minus-square@warmaster@lemmy.worldlinkfedilink2•2 months agoBut Steam OS is inside a container. Wouldn’t that container be using desync now?
minus-square@SuperIce@lemmy.worldlinkfedilinkEnglish8•2 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.