You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Windows 1803 (build 17134.112) and WSL with Ubuntu.
It appears that symlinks created from WSL outside the rootfs are properly recognized by Windows programs, e.g.:
(from bash)
cd /mnt/e/temp
mkdir dir1
ln -s dir1 dir2
(from cmd.exe)
cd /d e:\temp
dir
yields:
06/14/2018 10:36 AM <DIR> dir1
06/14/2018 10:36 AM <SYMLINKD> dir2 [dir1]
However, doing this inside the WSL's rootfs doesn't work:
(from bash)
cd ~
mkdir dir1
ln -s dir1 dir2
(from cmd.exe)
cd /d C:\Users\testuser\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs\home\testuser
dir
yields:
06/14/2018 10:37 AM <DIR> dir1
06/14/2018 10:37 AM 4 dir2
Here dir2 is not shown as a directory symlink, but instead as a test file containing the symlink target ("dir1"). Opening "dir2" from Windows Explorer or any other Windows tools doesn't work either.
The text was updated successfully, but these errors were encountered:
We are using Windows 1803 (build 17134.112) and WSL with Ubuntu.
It appears that symlinks created from WSL outside the rootfs are properly recognized by Windows programs, e.g.:
(from bash)
(from cmd.exe)
yields:
However, doing this inside the WSL's rootfs doesn't work:
(from bash)
(from cmd.exe)
yields:
Here dir2 is not shown as a directory symlink, but instead as a test file containing the symlink target ("dir1"). Opening "dir2" from Windows Explorer or any other Windows tools doesn't work either.
The text was updated successfully, but these errors were encountered: