dev/ /path/to/ntfs/drive/mount/point ntfs error=remount-ro,x-gvfs-show,defaults,rw,permissions,inherit,acl,umask=000,dmask=027,fmask=133,uid=1000,gid=1000,windows_names,compression 0 0
HOW TO CHANDE PROTON INSTALL DRIVE UPDATE
Sudo chown -R YOURUSERNAME:YOURUSERGROUPNAME /opt/NTFSSteamLibraryįstab: (Please note below, if your uid and gid for your account are not 1000, update those IDs to match your account accordingly) Sudo mkdir -p /opt/NTFSSteamLibrary//compatdata So I edited my fstab and files with the following:Ĭreate the compatdata mount point and give it your user permissions: I was able to work around this with some bind mounting through placing the compatdata folder on an ext4 partition. The colon isn't allowed on ntfs drives since that denotes a drive letter. However, proton creates a wine drive under /path/to/drive/mount/SteamLibrary/steamapps/compatdata//pfx/, and part of that is a symlink to proton's c drive "c:". PLEASE NOTE THIS IS PROBABLY NOT A SUPPORTED CONFIGURATION-įor anyone who's curious, I did some minor testing with ntfs and symlinks and they generally seem to work okay. valve github pages sucks it makes an ass ton of assumptions or fails to explain an umber of things. The company states that the program is still in the early stages of development, which explains why it did not reveal screenshots of the software. The official Proton desktop app for Windows, macOS and Linux, will be based on Electron. and i highly doubt it will you'd think they can make a 1 click fix. Proton desktop app for Windows, macOS and Linux. blanket execute will always be a risk, so i actually hope that doesn't become a default ever. Maybe proton can avoid needing these permitions in the future, but it's unlikely (they are required now for a reason). That is one among a couple other reasons why using ntfs for proton is discouraged in the long run, even if it is nice to have for initial testing when steam gamers start migrating to linux or dual-booting
so the workaround is "use this owner and permitions for everything inside the ntfs partition" that is due to ntfs being a lousy partitioning / file system for linux because it doesn't support storing permitions for each folder and file in it. while for security reasons it is a really bad idea to use a blanquet "anything in this whole partition can be executed" as a default linux setting. It will likely always require the extra hoop-jumping, due to proton needing execute permissions on some folders/files to work properly. Ntfs on linux for proton is valid as a temporary workaround, but bad as a permanent solution
Originally posted by cdoublejj:this still requires a work around? wtf?
0 kommentar(er)
