For the record, it does work, it’s just buggy and inconsistent as hell on both the Linux filesystem support side and the Steam side. It’s not my problem, it’s Linux’s and Steam’s. Things that don’t work shouldn’t work a little bit and then break other stuff permanently. That’s just not a tolerable behavior for mainstream software.
You’re trying to use an open source OS with a proprietary closed-source filesystem. The reason it’s buggy is because the driver you’re using for accessing the NTFS partition is reverse engineered at a “best effort” degree. The driver isn’t complete (will never be until Microsoft open sources it), and one of the things that’s a sore point is running executables from an NTFS partition. Steam just does not handle it well and that’s not Steam’s fault or their problem to fix, nor is it Linux’s fault or their problem to fix. Frankly, it’s not even Microsoft’s fault either because they’re under no obligation to release their source code.
It’s not my problem
It’s 100% your problem.
Things that don’t work shouldn’t work a little bit and then break other stuff permanently. That’s just not a tolerable behavior for mainstream software.
You don’t use your cellphone as a hammer and complain that cellphones aren’t tough enough when the screen breaks. You don’t say “that’s just not tolerable behaviour from a mainstream consumer product”.
The solution here is to separate your Steam library between games you play on Windows and Linux. Or simply to commit to just one OS for gaming. If you choose Windows for that, that’s perfectly fine. No one is going to give you a hard time over that. You use whatever works for you.
But please understand that your whole argument here is that you created a setup that’s unstable (which is fine, I learned the hard way too), were told it’s unstable and why, then in the next breathe complained that it’s not your fault, it’s everyone else’s.
NTFS is a garbage filesystem in my opinion anyways.
Alright, you made three comments, I’m not responding to each of them. The response is the same anyway.
For one thing, the idea isn’t to find the “best FS”, it’s to find the best FS to share across a dual boot setup. The common suggestion is, in fact, to stick with NTFS. Which is broadly correct, it does seem to be the better option among those available. For the record, this isn’t about the quality of NTFS anyway, the same issues apply when using other cross-platform FSs, which is why I volunteered the info that I tried other FS options.
That is not a ridiculous use case, it is not an edge case. Another self-contradicting frequent recommendation among Linux cheerleading places is to start migrating with a dual boot setup and Steam absolutely supports importing pre-existing libraries from mounted external drives. Hell, this is a fundamental piece of functionality on the Steam Deck, even. I haven’t gone off spec for any piece of this. Every part of this setup is supposed to work.
This isn’t using a cellphone as a hammer and being shocked that it breaks, it’s using it as a camera and finding out all the pictures are out of focus. Using supported features in supported drivers and applications is not user error just because the implementation of the features is buggy.
This is an exhausting conversation every time. People insist that Linux is finally ready (it is inevitable, someone said) to take over for Windows, but when people bring up legitimate technical issues the answer is consistently that oh, well, this works fine on AMD cards, and HDR isn’t that important anyway and who needs surround sound on a PC anyway, and why would you possibly want to share 100GB game installs across two systems in the first place?
If your answer is that dual boot setups just aren’t viable, then great, but that means Linux itself is not viable for a whole host of use cases, including mine. I suppose that’s the ultimate takeaway here. Which I find, let me be clear, a shame.
it’s to find the best FS to share across a dual boot setup
It just doesn’t exist. NTFS is proprietary and really the only choice for a Windows setup, and for Linux NTFS just isn’t a good choice. The only reason people recommend it is that it’s the path of least friction for users that comes out of the box. I’ve tried installing and using an EXT4 driver in Windows and it’s not painless process, and functionality was serviceable at best, but this was at least 5 years ago, so it might be better now.
That is not a ridiculous use case, it is not an edge case. Another self-contradicting frequent recommendation among Linux cheerleading places is to start migrating with a dual boot setup and Steam absolutely supports importing pre-existing libraries from mounted external drives.
True, but generally you would migrate your game data from a mounted NTFS drive to a FOSS filesystem.
This is an exhausting conversation every time.
Yes, the ever changing landscape of tech is exhausting. Like Windows barfing all over itself during updates (I had to reinstall my wife’s desktop just a couple weeks ago because a Windows update completely destroyed itself), which has been a regular issue for many years now. And that doesn’t even touch on the myriad of other issues Windows consistently has, nevermind all the privacy issues with Recall and ads within the OS, or OneDrive without permission uploading all user’s local documents, deleting them (edit: from the local drive), and them holding the data hostage when the OneDrive account doesn’t have enough purchased space for it all.
People insist that Linux is finally ready (it is inevitable, someone said) to take over for Windows, but when people bring up legitimate technical issues the answer is consistently that oh, well, this works fine on AMD cards, and HDR isn’t that important anyway and who needs surround sound on a PC anyway
There are always growing pains, but they are getting less and less with each release. Remember that these growing pains are a result of hardware and software makers ignoring Linux, and the reduction of pains are being tackled mostly by volunteer work. But as the userbase grows, so will support for these things and the pains will eventually go away.
If your answer is that dual boot setups just aren’t viable, then great, but that means Linux itself is not viable for a whole host of use cases
No, Linux is absolutely viable for most use cases. Dual boot setups are fine also even with mounting NTFS partitions on Linux, what you’re doing is saying “my specific use case of storing games on an NTFS partition isn’t ideal, so it doesn’t work for anyone”.
If you really insist on using it, there ARE ways to do it, but it’s an advanced setup, Take a look here (at your own risk):
I did take a look there. I had it working before it broke.
I disagree that the growing pains are steadily going down, too. Maybe I’m just old, but to me the golden age of Linux “just working” is definitely not now. It was the early days of Ubuntu where the hardware itself was simple but the drivers were already new enough to be fairly standardized.
The thing that killed Linux getting bigger then was the lack of software support. Who knows where we’d be if those early “easy” distros had better, more hassle-free translation layers available.
Now? This is a mess by comparison. You have Nvidia with a near-monopoly on GPUs pushing proprietary features as a selling point, crazy multi-GPU laptops with a bunch of custom drivers, weird form factors, touchscreens, pens, arbitrary framerates and resolutions… it’s complete chaos. I’m not surprised Linux struggles to keep up (and Windows buckles under the pressure), but it still makes it harder to swtich.
Anyway, let this be a note that the handling of third party FSs and external mounted drives in Linux should get much better and Steam should start giving non-SteamOS distros some love, because some of these library bugs are old.
I disagree that the growing pains are steadily going down, too. Maybe I’m just old, but to me the golden age of Linux “just working” is definitely not now.
Well, you can disagree all you like, but it doesn’t line up with reality. Hell, I even have my parents on Linux and it’s working great for them. Since setting them up with Linux the amount of times I have to connect to their computer or even drive over there has gone down to nearly zero.
The thing that killed Linux getting bigger then was the lack of software support.
You actually have that backwards, but that’s neither here nor there. The reality is that Linux is more compatible than ever. Most services that anyone uses is done online in a browser. Most Steam games work out of the box, not including live-service and multiplayer games with prohibitive anticheat. Even most non-Steam games work without much fuss. Lutris makes many games a one-click installation.
it’s complete chaos.
Not really. It may seem that way, but it’s just the fast progress of tech. Frankly, Linux leads that progress because of its monopolistic use in servers.
let this be a note that the handling of third party FSs
Not going to happen, unless you want to have a chat with Microsoft.
external mounted drives in Linux should get much better
There’s no issues with external drives in Linux beyond the usual stuff every OS deals with.
Steam should start giving non-SteamOS distros some love
Steam has worked swimmingly on other distros well before SteamOS was ever a thing.
You either misread or ignored what I actually wrote, so maybe give it another look. Specifically, I said the issue with Linux in the early 2000s was lack of software support, not now.
For the record, there is plenty wrong with the way Linux handles external drives, at least UX-wise. For one thing Dolphin mounts them differently than a mount command, which is insane. In the case of Samba shares it also mounts them in an entirely different location, which is extra insane. And the whole thing keeps a distinction between drives included as part of the system and external drives, even if the external drives are fixed, so if you want to add your extra hard drives to the navigation path for software you either have to go messing with fstab (which is both risky and terrible UX for newcomers) or manually click them every time you reboot your PC.
By comparison on Windows any time you mount a drive it just gets a drive letter and as long as you don’t remove it it stays there. Samba shares, optical media, USB drives, hard drives… doesn’t matter, mount it as a drive, assign it a letter, navigate to it consistently for the foreseeable future. It’s just better.
Oh, and when digging for solutions to my issues I found some of the same problems I’m encountering reported as bugs in threads from 2020, with the same workarounds being suggested in threads all the way from then to now. So your definition of “swimmingly” may not be the same as mine.
And you’re wrong about Linux being less of a hassle now, too, anecdotes aside. Although I’m not surprised, given that your parents probably aren’t trying to game on a modern HDR monitor. “Everything works on a browser” isn’t a good argument for Linux. It’s a good argument for getting your parents a tablet and calling it a day (which, incidentally, is what I did with mine and I haven’t had to troubleshoot it, either; Chrome is Chrome).
Well, then Linux is not an option, then.
For the record, it does work, it’s just buggy and inconsistent as hell on both the Linux filesystem support side and the Steam side. It’s not my problem, it’s Linux’s and Steam’s. Things that don’t work shouldn’t work a little bit and then break other stuff permanently. That’s just not a tolerable behavior for mainstream software.
You’re trying to use an open source OS with a proprietary closed-source filesystem. The reason it’s buggy is because the driver you’re using for accessing the NTFS partition is reverse engineered at a “best effort” degree. The driver isn’t complete (will never be until Microsoft open sources it), and one of the things that’s a sore point is running executables from an NTFS partition. Steam just does not handle it well and that’s not Steam’s fault or their problem to fix, nor is it Linux’s fault or their problem to fix. Frankly, it’s not even Microsoft’s fault either because they’re under no obligation to release their source code.
It’s 100% your problem.
You don’t use your cellphone as a hammer and complain that cellphones aren’t tough enough when the screen breaks. You don’t say “that’s just not tolerable behaviour from a mainstream consumer product”.
The solution here is to separate your Steam library between games you play on Windows and Linux. Or simply to commit to just one OS for gaming. If you choose Windows for that, that’s perfectly fine. No one is going to give you a hard time over that. You use whatever works for you.
But please understand that your whole argument here is that you created a setup that’s unstable (which is fine, I learned the hard way too), were told it’s unstable and why, then in the next breathe complained that it’s not your fault, it’s everyone else’s.
NTFS is a garbage filesystem in my opinion anyways.
Alright, you made three comments, I’m not responding to each of them. The response is the same anyway.
For one thing, the idea isn’t to find the “best FS”, it’s to find the best FS to share across a dual boot setup. The common suggestion is, in fact, to stick with NTFS. Which is broadly correct, it does seem to be the better option among those available. For the record, this isn’t about the quality of NTFS anyway, the same issues apply when using other cross-platform FSs, which is why I volunteered the info that I tried other FS options.
That is not a ridiculous use case, it is not an edge case. Another self-contradicting frequent recommendation among Linux cheerleading places is to start migrating with a dual boot setup and Steam absolutely supports importing pre-existing libraries from mounted external drives. Hell, this is a fundamental piece of functionality on the Steam Deck, even. I haven’t gone off spec for any piece of this. Every part of this setup is supposed to work.
This isn’t using a cellphone as a hammer and being shocked that it breaks, it’s using it as a camera and finding out all the pictures are out of focus. Using supported features in supported drivers and applications is not user error just because the implementation of the features is buggy.
This is an exhausting conversation every time. People insist that Linux is finally ready (it is inevitable, someone said) to take over for Windows, but when people bring up legitimate technical issues the answer is consistently that oh, well, this works fine on AMD cards, and HDR isn’t that important anyway and who needs surround sound on a PC anyway, and why would you possibly want to share 100GB game installs across two systems in the first place?
If your answer is that dual boot setups just aren’t viable, then great, but that means Linux itself is not viable for a whole host of use cases, including mine. I suppose that’s the ultimate takeaway here. Which I find, let me be clear, a shame.
It just doesn’t exist. NTFS is proprietary and really the only choice for a Windows setup, and for Linux NTFS just isn’t a good choice. The only reason people recommend it is that it’s the path of least friction for users that comes out of the box. I’ve tried installing and using an EXT4 driver in Windows and it’s not painless process, and functionality was serviceable at best, but this was at least 5 years ago, so it might be better now.
True, but generally you would migrate your game data from a mounted NTFS drive to a FOSS filesystem.
Yes, the ever changing landscape of tech is exhausting. Like Windows barfing all over itself during updates (I had to reinstall my wife’s desktop just a couple weeks ago because a Windows update completely destroyed itself), which has been a regular issue for many years now. And that doesn’t even touch on the myriad of other issues Windows consistently has, nevermind all the privacy issues with Recall and ads within the OS, or OneDrive without permission uploading all user’s local documents, deleting them (edit: from the local drive), and them holding the data hostage when the OneDrive account doesn’t have enough purchased space for it all.
There are always growing pains, but they are getting less and less with each release. Remember that these growing pains are a result of hardware and software makers ignoring Linux, and the reduction of pains are being tackled mostly by volunteer work. But as the userbase grows, so will support for these things and the pains will eventually go away.
No, Linux is absolutely viable for most use cases. Dual boot setups are fine also even with mounting NTFS partitions on Linux, what you’re doing is saying “my specific use case of storing games on an NTFS partition isn’t ideal, so it doesn’t work for anyone”.
If you really insist on using it, there ARE ways to do it, but it’s an advanced setup, Take a look here (at your own risk):
https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
I did take a look there. I had it working before it broke.
I disagree that the growing pains are steadily going down, too. Maybe I’m just old, but to me the golden age of Linux “just working” is definitely not now. It was the early days of Ubuntu where the hardware itself was simple but the drivers were already new enough to be fairly standardized.
The thing that killed Linux getting bigger then was the lack of software support. Who knows where we’d be if those early “easy” distros had better, more hassle-free translation layers available.
Now? This is a mess by comparison. You have Nvidia with a near-monopoly on GPUs pushing proprietary features as a selling point, crazy multi-GPU laptops with a bunch of custom drivers, weird form factors, touchscreens, pens, arbitrary framerates and resolutions… it’s complete chaos. I’m not surprised Linux struggles to keep up (and Windows buckles under the pressure), but it still makes it harder to swtich.
Anyway, let this be a note that the handling of third party FSs and external mounted drives in Linux should get much better and Steam should start giving non-SteamOS distros some love, because some of these library bugs are old.
Well, you can disagree all you like, but it doesn’t line up with reality. Hell, I even have my parents on Linux and it’s working great for them. Since setting them up with Linux the amount of times I have to connect to their computer or even drive over there has gone down to nearly zero.
You actually have that backwards, but that’s neither here nor there. The reality is that Linux is more compatible than ever. Most services that anyone uses is done online in a browser. Most Steam games work out of the box, not including live-service and multiplayer games with prohibitive anticheat. Even most non-Steam games work without much fuss. Lutris makes many games a one-click installation.
Not really. It may seem that way, but it’s just the fast progress of tech. Frankly, Linux leads that progress because of its monopolistic use in servers.
Not going to happen, unless you want to have a chat with Microsoft.
There’s no issues with external drives in Linux beyond the usual stuff every OS deals with.
Steam has worked swimmingly on other distros well before SteamOS was ever a thing.
You either misread or ignored what I actually wrote, so maybe give it another look. Specifically, I said the issue with Linux in the early 2000s was lack of software support, not now.
For the record, there is plenty wrong with the way Linux handles external drives, at least UX-wise. For one thing Dolphin mounts them differently than a mount command, which is insane. In the case of Samba shares it also mounts them in an entirely different location, which is extra insane. And the whole thing keeps a distinction between drives included as part of the system and external drives, even if the external drives are fixed, so if you want to add your extra hard drives to the navigation path for software you either have to go messing with fstab (which is both risky and terrible UX for newcomers) or manually click them every time you reboot your PC.
By comparison on Windows any time you mount a drive it just gets a drive letter and as long as you don’t remove it it stays there. Samba shares, optical media, USB drives, hard drives… doesn’t matter, mount it as a drive, assign it a letter, navigate to it consistently for the foreseeable future. It’s just better.
Oh, and when digging for solutions to my issues I found some of the same problems I’m encountering reported as bugs in threads from 2020, with the same workarounds being suggested in threads all the way from then to now. So your definition of “swimmingly” may not be the same as mine.
And you’re wrong about Linux being less of a hassle now, too, anecdotes aside. Although I’m not surprised, given that your parents probably aren’t trying to game on a modern HDR monitor. “Everything works on a browser” isn’t a good argument for Linux. It’s a good argument for getting your parents a tablet and calling it a day (which, incidentally, is what I did with mine and I haven’t had to troubleshoot it, either; Chrome is Chrome).