this post was submitted on 25 Sep 2023
122 points (99.2% liked)
Steam Deck
14850 readers
38 users here now
A place to discuss and support all things Steam Deck.
Replacement for r/steamdeck_linux.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to the Steam Deck in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is the best summary I could come up with:
Queued up into the Btrfs file-system driver's "for-next" branch ahead of the Linux 6.7 cycle is the Temp-FSID (Same-FSID) feature that is being pursued for use by Valve's Steam Deck game console.
Such same-fsid mounting is hereby added through the usage of the filesystem feature "temp-fsid" - when such feature is used, btrfs generates a random fsid for the filesystem and leverages the long-term present metadata_uuid infrastructure to enable the usage of this secondary "virtual" fsid, effectively requiring few non-invasive changes to the code and no new potential corner cases.
In order to prevent more code complexity and corner cases, the temp-fsid feature is not allowed when the metadata_uuid flag is present on the fs, or if the device is on fsid-change state.
This functionality has been queued into kdave/linux.git's for-next branch where Btrfs material is staged ahead of the next Linux kernel cycle.
Thus this new Btrfs feature will be found in Linux 6.7 barring any issues from appearing between now and the merge window opening around early November.
This Btrfs feature was also mentioned last week at OSS EU 2023 as part of Valve's upstream contributions to Linux.
The original article contains 462 words, the summary contains 190 words. Saved 59%. I'm a bot and I'm open source!