安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
此主題已被鎖定 
討論區規矩與守則
檢舉此篇文章
NTFS is not a POSIX-type filesystem and does not support (normal) per file/directory UNIX ownership and/or permissions. Those credentials still however being fundamental to the UNIX model, Linux mounts an NTFS filesystem with filesystem-wide "pretend" credentials, specifically and unless adjusted through mount-parameters as root:root and ugo=rwx -- at least the historically used NTFS-3G userspace NTFS driver does; Arch may or may not at this time use the new-ish NTFS3 kernelspace one which in turn may or may not act differently by default. Dunno.
The above is to say that NTFS is a bad fit for a UNIX-type system and should not be used period, other than for its intended purpose of sharing a filesystem with a dual-boot copy of Windows on the same machine. But note that at least as far I still know (I do not and have not for a long time dual-booted) sharing a Steam library between Steam on dual-boot Windows and Linux is not possible or a bad idea anyway: at least historically the same credential issue as above would cause Steam on Linux to constantly redownload games in an NTFS-hosted library.
That is, you very preferably reformat your library disk with a proper UNIX-type filesystem; ext4 normally on Linux. Only if that's definitively not an option should you choose to use what I referred to above and adjust credentials manually.
Specfically for your mentioned :steam and 770 you'd use "gid=steam,umask=007". If you mount the filesystem at boot through /etc/fstab this is also where you specify such. F.e.
In any case -- not using NTFS in Linux is as said a better idea anyway so do that if at all possible.
I'm using a EXT4 system for my 2nd HDD
Here's the FSTAB config:
UUID=3ada7550-9bf8-4afc-8962-0b8f658e7fba /mnt/newhdd ext4 defaults,noatime 0 1
I.e., sorry, but makes no sense. As in, not at all. A chmod/chgroup is not volatile on ext4.
I thought I formatted this HDD to ext4
Should I reformat it then? Maybe that will fix it?
Let us any case verify. Make sure that you play or try to play through Steam one of the games in the library so as to make sure all potential auto-triggers have been triggered and use simply "mount" in a terminal to see what is mounted how on /mnt/newhdd.
I'd still be surprised to see ext4.
I used the mount command, and it gave me
"/dev/sdb1 on /mnt/newhdd type ext4 (rw,noatime)"
Have you installed Steam as a native package (i.e., via pacman in your case) or as a flatpak?
I do by the way assume that both machine-local users use the same Steam account? If not then you would be sharing a library between Steam accounts rather than just UNIX-accounts and the issue would not so much be needing to reset credentials for latter; sharing a library between Steam accounts supposedly just doesn't work indeed -- although just steamapps/common could supposedly (and "generally") be linked....
I also assume that not concurrent access to that single library from both machine-local user accounts is being attempted? If it is, yes, don't do that.
Thinking...
I do in fact suppose ownership of files could change, although not on reboot but after "usertwo" launches steam, and although your chown implied user as such to not be the issue, your users primary group may get set on new files and that's supposedly not the group "steam"...
More info is needed as to your setup I'm afraid.
Yes, the storage for the 2nd HDD is indeed setup on /mnt/newhdd/
I've installed it native via pacman
And I share my library with another user, but that other user has his own Steam account
I wanted to share my games with another user so he could use my computer and play all my games without fiddling with anything important or even my account in general
And I've found out that certain games will also refuse to run if they were installed by another user, with the error message on the terminal being something amongst the lines of "pfx is not owned by you", and although usually deleting said folder allows the game to run properly, there has to be better ways to solve this.
(a note is that a current bug as to the discovery for those "eligible accounts" is that users may need to login to "Friends & Chat" -- lower-right corner of the Steam client -- while setting up)
Once you have that set up you are not yet sharing disc space for the games as such, since the sharing users would "need" to download and install to his/her own library -- but once setup you can in fact and as said supposedly link steamapps/common from a common source.
In any case though first set up family-sharing. Another Steam account can't just play your games, at least not those that in fact use Steam DRM. Disc-space sharing is then a secondary hack after things work without...
Family sharing was enabled from the very beginning
It's just the permissions and the whole ♥♥♥♥♥♥ library and permissions thing that's been making the proccess hard to deal with.
Anyways. I just tested things (mind you, on a Debian base) and have it working. First off and just to be explicit also for readers: once family-share has been set up things basically work as is and the only part of the matter left is physically sharing a bunch of game data over two distinct UNIX accounts. If the shared-to account doesn't mind downloading and installing private copies of the games you don't need any of this.
If he/she however does mind, "bindfs" works. I.e., also referring to my above worry about "primary group" there's too many potential or real ownership issues to just flat-out share but you can use bindfs to bind-mount the libraries into e.g. the home-directories with "fake" permissions.
To wit, I have my shared-from Steam-account's library at say /data/SteamLibrary and have two UNIX-users yujah:steam (with its Steam account shared-from) and guest:steam (with its Steam-account shared-to) that bind-mount it into their homes as
A note is that you may want --mirror and/or --map rather than the above --force-user and --force-group but seems to work for me; "man bindfs" for details. I will assume that "bindfs" is available from the Arch repo.
Hope it helps.
I do appreciate the help though