Steam Deck: add configuration to preserve etc files starting with SteamOS 3.6 #12
Labels
No labels
Compat/Breaking
Context/drive-by
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status/Fixed On Main
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix-installer#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Starting with SteamOS 3.6, files in /etc are now preserved on a whitelist (with files not in it moved to /etc/previous). Currently as of this beta these nix-related files are not kept:
A file can be created inside /etc/atomic-update.conf.d/ to keep these on updates.
Since 3.6 is a beta, the default list might change, so it might be a good idea to wait and see first.
Beta notes for 3.6.0: https://store.steampowered.com/news/app/1675200/view/4213757668851885208
The default list of preserved files: https://gist.github.com/ihaveamac/871bba4e0627112581c78871c540abbc
Testing again, it also needs to preserve these files which were removed following an OS update:
I just noticed the Determinate Installer does this now: https://github.com/DeterminateSystems/nix-installer/pull/1355
Bump, it would be nice if this was implemented since it would make setup on modern SteamOS easier. Otherwise I would have to manually add the files, or use the detsys installer first.
@ihaveamac wrote in #12 (comment):
We recently rebased on top of modern DetSys Installer, so this fix is now backported. For reasons, the installer from the website isn't yet updated. The installer built from
mainbranch of the Forgejo repo should handle this, though.I'll close this issue once we've updated the installer on the website. In the meantime, if you could test the installer from the
mainbranch, it would be very helpful!