3 ms·
One of the things I really liked about WSL1 was the integration with Windows. This caused some bugs but made other task a lot simpler. For example editing a fil
by wnevets 6y ago
One of the things I really liked about WSL1 was the integration with Windows. This caused some bugs but made other task a lot simpler. For example editing a file that existed in the Windows file system with a Windows application and then actually processing it with a linux binary worked really well most of the time.
With WSL2 you are expected to only interact with files in the linux filesystem with linux. I'm sure this made a bunch of easier for the dev team but it kinda ruins WSL for me.
I still haven't figured out how to call a binary that exist in the linux vm from Windows or how to interact with the windows network from linux.
- baq 6y agore files - you can mount an nfs export in WSL and Windows 10 comes with a opt-in NFS server - or perhaps try samba. re network - if you mean localhost, that's probably impossible due to WSL2 being a vm unless the folks at MS invent some deep black magic. you should be able to use the LAN interface IP address, though.