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
VolFS, that is 99.999% compatible with Linux but accessing it with Windows is not supported.
One can't use his/her favorite windows editor on its files
One can't copy them around with Windows Explorer
DrvFS, which does not support symbolic links nor the execute bit.
One can't work on any project with git or else it will freak out because of all the permissions
One can't work on any project which uses symbolic links
which means one can't realistically work on neither filesystems.
wouldn't it be possible for DrvFS to support the execute bit via NTFS extended attributes ? Same for symbolic links. We don't actually need them to have any meaning on Windows. It's completely fine if one can run a .exe file no matter if it has a execute bit or not and that one sees a an empty file if it's a symbolic link on windows.
That would make DrvFS good enough for 99% of the software and one could use the windows tools they are used to and love to work with.
The text was updated successfully, but these errors were encountered:
@marcosdiez -- have you tried git config core.filemode false? It doesn't work for 99% of projects but I suspect it works for more than half.
Symlinks do work on DrvFs these days. Though if you create a symlink in Linux, it can't be used in Windows yet. That's covered by this ticket and this UserVoice.
As of today, on WSL, we have two filesystems:
which means one can't realistically work on neither filesystems.
wouldn't it be possible for DrvFS to support the execute bit via NTFS extended attributes ? Same for symbolic links. We don't actually need them to have any meaning on Windows. It's completely fine if one can run a .exe file no matter if it has a execute bit or not and that one sees a an empty file if it's a symbolic link on windows.
That would make DrvFS good enough for 99% of the software and one could use the windows tools they are used to and love to work with.
The text was updated successfully, but these errors were encountered: