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
UPDATE: This can be a possible solution, but might not be what OP needs.
Wineprefixes don't work right on NTFS filesystems because some files contain colons, which is a reserved character in NTFS and FAT.
If you look inside the game's wineprefix, the
dosdevicesdirectory will typically have two symbolic links: one namedc:that points to thedrive_cdirectory, and another namedz:that points to the filesystem root (plus a few others that are irrelevant). These will appear as lettered drives for programs running inside Wine. If the wineprefix is on an NTFS partition, those files can't be created because their names contain an invalid character.You'll have to either relocate the wineprefixes to an ext4 or btrfs partition (I don't know if you can do that on Steam), or format the NTFS drive using ext4 or btrfs.
It's not related to the issue, mounting a device usually requires elevated privileges. The same thing happens when it is mounted through fstab, except the process that mounts it already has elevated privileges. Access to the filesystem is not affected by this.
Ah ok i think i get why it doesn't work through the auto mount, but i still don't understand why it works completely fine if i mount it through steam? What is different when steam mounts it?
I don't know for sure, but I have an idea.
By default, Steam creates wineprefixes in
~/.steam/steam/steamapps/compatdata/GAME_ID. This is located in the user home, which should be a Linux filesystem (ext4, btrfs, and similar). If the drive is mounted statically through fstab, the prefixes are created on the mounted drive. If the drive is mounted dynamically, Steam might think it's a USB stick, likely with a FAT32 filesystem, and preemptively create the prefixes inside the user home to ensure compatibility.I'll have to do some testing once I get home.
This could very well be the anwser. there are in fact c: and z: in
~/.steam/steam/steamapps/compatdata/0/pfx/dosdevicesalthough i couldn't find an indicator that those are actually in use when launching a game through steam
They're definitely both used. When a program is started in a Wine environment, those symlinks are the only way it can access the filesystem: game files in
.../steamapps/commonthroughz:; settings and saved games (normally in the Windows user's home directory) throughc:.You can run
wine explorer.exeto open a Windows Explorer implementation and check out what the Linux filesystem looks like in Windows. You can even add new lettered drives usingwinecfg, although I wouldn't try it with Steam's prefixes.