steamos-teardown

Fwiw there's a really nice write-up on how Steam Deck does A/B updates, using rayc and casync/desync. https://github.com/randombk/steamos-teardown/blob/master/doc... Also Collabora had a nice update on tuning work they did. https://www.collabora.com/news-and-blog/news-and-events/stea... I'm a little surprised they use casync and multiple partitions, given that root is on btrfs. As they have it is more reliable if anything does go bad, so makes sense, but: given that steam decks are on a given snapshot of the btrfs system, it seems like they could just send an incremental update to the next release and try to boot that. Oh ah, that breaks down if, like me, you disable the readonly root.

Hi Everyone! While tinkering with the Steam Deck, I was shocked at the lack of public documentation for how the OS itself works. Valve has made numerous customizations to the upstream Arch OS, and I felt it's high time we started a community effort to consolidate our findings and document these changes. I'm currently aiming for a more technical audience, but see this branching out into guides and utilities for non-technical audiences in the future. For anyone interested in contributing or just simply curious about how the Steam Deck works on the software side, please take a look!