Ænðr E. Feldstraw<p><a href="https://mastodon.social/tags/TodayILearned" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TodayILearned</span></a>: <a href="https://mastodon.social/tags/WSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WSL</span></a> lets us mount mapped <a href="https://mastodon.social/tags/NTFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NTFS</span></a> and <a href="https://mastodon.social/tags/FAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FAT</span></a> drives from <a href="https://mastodon.social/tags/MSWindows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MSWindows</span></a> to <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> using what <a href="https://mastodon.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> calls <a href="https://mastodon.social/tags/DrvFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DrvFS</span></a>. You may, like I did, find it impossible to install <a href="https://mastodon.social/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystem</span></a> driver separately into your Linux distro. And asking $ which drvfs may turn up empty. That's because it's a built-in WSL tool. Just use it as documented below: that worked for me. <br><a href="https://blogs.msdn.microsoft.com/wsl/2017/04/18/file-system-improvements-to-the-windows-subsystem-for-linux/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blogs.msdn.microsoft.com/wsl/2</span><span class="invisible">017/04/18/file-system-improvements-to-the-windows-subsystem-for-linux/</span></a></p>