4 ms·
Microsoft had to warn users that they would corrupt the original WSL subsystem if they touched Linux files using Windows tools: > DO NOT, under ANY circumstanc
by GeekyBear 6mo ago
Microsoft had to warn users that they would corrupt the original WSL subsystem if they touched Linux files using Windows tools:
> DO NOT, under ANY circumstances, access, create, and/or modify Linux files inside of your `%LOCALAPPDATA%` folder using Windows apps, tools, scripts, consoles, etc.
They did overcome that problem eventually, but by then everyone had moved on to WSL2.
- pjmlp 6mo agoThat is no different from having file systems problems across OSes, as old as there are multiple OSes. Even Linux best practices for SMB access have been as read only.
- GeekyBear 6mo agoSorry, but WSL1 was unstable by Microsoft's own admission. That's why Microsoft abandoned it in favor of WSL2 running real Linux in a VM.
- pjmlp 6mo agoNope, Microsoft redid the design due to the amount of Linux syscalls that were still left to implement. What is this goal post moving? First the was file system access, then it became being unstable, what is going to be the next point? Let me make it easier, WSL 1.0 did not support the syscalls for X Windows implementation.
- GeekyBear 6mo ago> What is this goal post moving? First the was file system access, then it became being unstable, what is going to be the next point? If you can't touch the Linux files with Windows tools without corrupting them, your implementation is unstable. WSL1 was unstable, unfit for purpose, and never worked properly. It was abandoned in favor of just running real Linux in a VM.