Earlier quoted context omitted.
Your Windows drives appear under /mnt/c, /mnt/d, etc. in WSL. So your Windows home directory is /mnt/c/Users/ffoobar. You can easily read/write Windows files from Linux, but I don't think you can do the opposite. I've used git within WSL to drive a repo on my Windows drive. WSL gives you full-blown Ubuntu 16.04 where you manage packages with apt-get. You have to look close to the bare metal to see differences. Until…
I thought it would give me total interoperability. That I could edit an movie in a windows app, run it through ffmepg, and go back to editing. Cygwin is still useful.
File System Improvements to the Windows Subsystem for Linux
31–40 of 108 posts
Re: File System Improvements to the Windows Subsystem for Linux
#32Java still doesn't work properly though =(. "mvn clean package" on one of corporate projects takes about 5 to 8 minutes in native java on Windows or Mac and it takes more than one hour in WSL. I had so much hope for WSL that I would finally have only ONE device (surface), but no, we're not there yet.
Re: File System Improvements to the Windows Subsystem for Linux
#33Java still doesn't work properly though =(. "mvn clean package" on one of corporate projects takes about 5 to 8 minutes in native java on Windows or Mac and it takes more than one hour in WSL. I had so much hope for WSL that I would finally have only ONE device (surface), but no, we're not there yet.
Re: File System Improvements to the Windows Subsystem for Linux
#34Java still doesn't work properly though =(. "mvn clean package" on one of corporate projects takes about 5 to 8 minutes in native java on Windows or Mac and it takes more than one hour in WSL. I had so much hope for WSL that I would finally have only ONE device (surface), but no, we're not there yet.
Sorry, I have to ask. Why do you need to use Java with WSL? Native methods?
Cygwin and using shared VM directories has too many glitches with things like npm, links, file system endings, etc. As Docker becomes more important, this gets even worse.
Really, developing on a Mac is just so much better than both Windows and Linux, even for Java.
Re: File System Improvements to the Windows Subsystem for Linux
#35Re: File System Improvements to the Windows Subsystem for Linux
#36Does WSL work on Windows Home, or does it require Pro? Is this an accident or by design?
https://msdn.microsoft.com/zh-tw/commandline/wsl/install_gui...
Re: File System Improvements to the Windows Subsystem for Linux
#37I was going to make another comment, but just found out while searching that WSL is //supposed// to be based on Ubuntu (20)16.04 now (instead of 14.04) I guess the next time I work with those systems I'll have to run down some upgrade / re-install directions. I wonder if that will fix the issue where I was unable to mv folders around the c:\ drive within the /mnt/c FS. (It more or less locked up to the point that I h…
FWIW, I haven't had any issues moving files before or after upgrading from 14.04 -> 16.04. I use Git in WSL, but interact with the files in both Windows and WSL without any special considerations.
However I do recall that trying to ctrl+c kill it didn't work. I don't recall what else I had/hadn't tried; I was rather busy at the time and couldn't stop to make a proper bug report.
All that mattered to me was that it completely stalled for no transparent reason and my best option was to just not even try to do real file management from the WSL environment.
Re: File System Improvements to the Windows Subsystem for Linux
#38Re: File System Improvements to the Windows Subsystem for Linux
#39Java still doesn't work properly though =(. "mvn clean package" on one of corporate projects takes about 5 to 8 minutes in native java on Windows or Mac and it takes more than one hour in WSL. I had so much hope for WSL that I would finally have only ONE device (surface), but no, we're not there yet.