• 2 Posts
  • 113 Comments
Joined 2 years ago
cake
Cake day: November 10th, 2023

help-circle



  • This is not correct.

    The Linux kernel has had support for the NTFS file system since 2021. The issues detailed in the article you linked to explicitly refer to issues with Proton and Steam, which require characters that are illegal in the NTFS specification and symbolic links, which the spec does not support.

    Sure, you may bump up against these limitations in other apps, but it is a hard crash in Steam and Lutris, which is why the distro has the article.




  • Bazzite is pretty great, but being an immutable OS has pros and cons, especially if you run into weird edge cases (unsupported hardware, weird sound issues, general weirdness). Because you can’t modify the base OS, you won’t have access to use “normal” methods to try and solve the problem whatsoever, as opposed to running a non-atomic Arch/Fedora/Debian-based distro where you have access to a full package manager and init/systemd. But if they’re on somewhat mature hardware, it’s basically an appliance that is significantly harder to fuck up.

    If disk space isn’t a huge issue, my recommendation among friends is to use Steam in Windows to create Archives to back up anything you don’t want to spend a lot of time redownloading. Then, once in Linux, drop in a new SSD and/or make a new ext4 partition exclusively for Steam games, add it to Flatseal, then use Steam on Linux to restore from the archive file. After that, Steam will download the proton distributable and some Linux middleware, and you’re mostly good to go.

    Takes a while to copy files to and from the archives, especially if one of those scratch disks is a SATA SSD, but always much faster than doing it over the network.


  • Bazzite has ntfs3/ntfs-3g available for mounting (this was merged with the main Linux kernel in 5.15 back in 2021), but it’s not supported to format disks as NTFS in the gui, if I recall.

    You’re correct with the fact that Steam/Proton uses the colon character in file paths, which are an illegal character on ntfs, so if you wanted to share a Steam library specifically you need to use the symlink workaround. But this is specific to Steam/Proton and not a generality for e.g., Plex/JellyFin/OMV or general storage.


  • Where exactly are you looking?

    In Disks, in Files, or in Plex?

    The GNOME Disks app will tell you if it sees the physical disks and partitions, and let you set up mounting options. Hit the Mount button (Play icon) to mount the partition once, or hit the Config button (Gear icon) to configure automatic mounting. For media disks, you probably want to mount at startup, and I’d recommend setting the “ldentify As” field to “Label” (which will also give it a “friendly” path like /var/mnt/Media).

    In GNOME Nautilus/Files, you may see the disks, but unless they’ve been set to automount, there are lots of reasons why it may have failed (most commonly the dirty bit was set on the disk due to unclean dismount, fix with fsck command).

    Finally, in Plex or other apps (notably Steam, if you have a separate Steam games partition), there’s a design choice in Bazzite/Atomic Linux distributions to use Flatpaks for most applications. Flatpaks sandbox the app from most of the rest of the OS, including disk access. This is intentional, but annoying if you do not know about it. Use another app called Flatseal to modify the permissions on the app’s Flatpak to allow it to access the other disk under “File System”, as granularly as it makes sense, (or just all disks if you’re a chaos demon). You can also do this using the flatpak override command, but you need to know the application identifier.