3 ms·
I hadn’t considered how this being in the upstream kernel would make it possible to run my WSL2 on NTFS natively. That’s pretty cool. I’m sure there’s still som
by ecnahc515 5y ago
I hadn’t considered how this being in the upstream kernel would make it possible to run my WSL2 on NTFS natively. That’s pretty cool. I’m sure there’s still some stuff to figure out, but still pretty awesome.
- phkahler 5y agoDoesn't WSL2 already have the ability to read NTFS somehow? Isnt this just an optimization?
- flatiron 5y agoIt’s a network mount. Hence it’s “don’t use it cause it’s shitty” reputation.
- zamadatix 5y agoWell you could do that too but you'd lose permissions between the two (NTFS supports POSIX permissions but Linux doesn't and vice versa with Windows permissions). The blog post is really about making any Linux mountable FS available to the Windows side of WSL2 without NT needing to support it. E.g. it doesn't matter if the drive is NTFS or Ext4 or BobYourUncleFS as long as the Linux kernel can mount the FS you can mount it in WSL2 and access it from Windows without NT needing to support the OS. It also already works in reverse, volumes mounted in Windows (including NTFS) can also be shared with WSL2. It's really just their integrated-into-the-OS version of VM guest filesystem sharing.
- int_19h 5y agoWhat's the point, though? You still can't have two kernels accessing the same filesystem directly, so if you give direct access to Linux in WSL, Windows loses it.