this post was submitted on 01 Oct 2024
31 points (94.3% liked)
Linux
47949 readers
1713 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've done my tests, and it looks like I may have been incorrect.
Point 1. While I was right to suspect the
:character, I discovered that it is permitted in NTFS and only reserved in Windows. When an NTFS volume is mounted in Linux, it only becomes a problem if thewindows_namesoption is used. Sometimes it is used, sometimes it isn't, and I don't know when.Point 2. The other thing I found is that Wine only works if the wineprefix is owned by the user. NTFS doesn't understand Unix-style file ownership and permissions, so it must determine the uid, gid, and umask when the volume is mounted. When mounted with OP's fstab entry, it will default to root, so every file (including the wineprefixes) within the volume will appear as being owned by root, which prevents Wine from starting.
This might also explain why mounting the drive dynamically worked, as it probably used
udisks2to mount it as the user.The solution may be as simple as specifying the
uidandgidmount options. In a system with a single user, they should both be 1000, but you can check them by runningecho $UID $GID.The modified fstab entry should be:
This will present all files as being owned by the user, and should allow wine to run.
Point 3. That being said, mixing Windows and Linux is still not a good idea. I don't know what will happen if you create wineprefixes on NTFS. Windows might see the invalid filenames and shit itself. I tried doing it on a new NTFS volume and Windows wouldn't even mount it.
If you really want to keep the game files on the NTFS volume, you might have better luck trying your own symlink fuckery. If you have the Steam library on the NTFS device, you could try moving the
.../SteamLibrary/steamapps/compatdatadirectory to a Linux filesystem, then creating a symlink incompatdata's place that points to the moved directory. This method moves the problematic files outside the volume.The second method involves bringing the game files on the NTFS volume into the default Steam library on the Linux filesystem using a bind mount -- a way to mount a directory at a different mount point. In essence, this replaces the
.../steamapps/commondirectory with that on the NTFS volume, and avoids creating wineprefixes inside the NTFS filesystem in the first place.sudo mount --bind /mnt/games/SteamLibrary/steamapps/common ~/.local/share/Steam/steamapps/commonto create the bind mount manually.