aboutsummaryrefslogtreecommitdiff
path: root/content/blog/2020-01-26-steam-on-ntfs.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/2020-01-26-steam-on-ntfs.md')
-rw-r--r--content/blog/2020-01-26-steam-on-ntfs.md22
1 files changed, 11 insertions, 11 deletions
diff --git a/content/blog/2020-01-26-steam-on-ntfs.md b/content/blog/2020-01-26-steam-on-ntfs.md
index 74d1e71..187aaba 100644
--- a/content/blog/2020-01-26-steam-on-ntfs.md
+++ b/content/blog/2020-01-26-steam-on-ntfs.md
@@ -13,11 +13,11 @@ Screenshot](https://img.cleberg.net/blog/20200125-the-best-linux-software/steam.
If you want to see how to install Steam on Linux, see my other post: [Linux
Software](../linux-software/).
-Are you having trouble launching games, even though they've installed
-correctly? This may happen if you're storing your games on an NTFS-formatted
-drive. This shouldn't be an issue if you're storing your games on the same
-drive that Steam is on, but some gamers prefer to put Steam on their main drive
-and game files on another SSD or HDD.
+Are you having trouble launching games, even though they've installed correctly?
+This may happen if you're storing your games on an NTFS-formatted drive. This
+shouldn't be an issue if you're storing your games on the same drive that Steam
+is on, but some gamers prefer to put Steam on their main drive and game files on
+another SSD or HDD.
To fix this problem, you'll need to try a few things. First, you'll need to
install the `ntfs-3g` package, which is meant for better interoperability with
@@ -44,12 +44,12 @@ mkdir /mnt/steam_library
```
To automatically mount drives upon system boot, you will need to collect a few
-items. The UUID is the identification number connected to whichever drive
-you're using to store Steam games.
+items. The UUID is the identification number connected to whichever drive you're
+using to store Steam games.
-Drives are usually labeled similar to `/dev/nvme0n1p1` or `/dev/sda1`, so
-you'll need to find the line in the output of the command below that correlates
-to your drive and copy the UUID over to the `/etc/fstab` file.
+Drives are usually labeled similar to `/dev/nvme0n1p1` or `/dev/sda1`, so you'll
+need to find the line in the output of the command below that correlates to your
+drive and copy the UUID over to the `/etc/fstab` file.
```sh
sudo blkid | grep UUID=
@@ -72,7 +72,7 @@ sudo nano /etc/fstab
Each drive you want to mount on boot should have its own line in the
`/etc/fstab` file that looks similar to this:
-``` config
+```config
UUID=B64E53824E5339F7 /mnt/steam_library ntfs-3g uid=1000,gid=1000 0 0
```