Unfortunately, this leaves you with files that can’t be accessed by Windows applications.
This is what allows Linux applications running in WSL to use file names that differ only by case, just like they can on real Linux, even with that global registry key set. The Windows Subsystem for Linux uses another mechanism, which itself bypasses that registry key, allowing us to perform case sensitive file system operations. Since Windows XP, this has been the default.
However, for compatibility reasons, there is a global registry key that overrides this behavior when this key is set, all file operations are case insensitive, even when the FILE_FLAG_POSIX_SEMANTICS flag is specified. Applications can pass the FILE_FLAG_POSIX_SEMANTICS flag to the CreateFile API to indicate that they want the path to be treated as case sensitive. The Windows NT family of operating systems (including Windows 10) has always had the ability to perform case sensitive file system operations. As of insider build 17110, this behavior is the default. We use this ability in the Windows Subsystem for Linux to give you better interoperability when using case sensitive files, and you can also use it yourself with regular Windows applications. Starting with Windows insider build 17093, we’ve introduced a new way to handle case sensitive files in Windows: per-directory case sensitivity. While File Explorer would show both files, only one would be opened regardless of which one you clicked. Since Windows applications treat the file system as case insensitive, they cannot distinguish between files whose names only differ in case. However, using those files in Windows was not really possible. This means, among other things, that you can create files whose names differ only by case (e.g. If you have used the Windows Subsystem for Linux, you’re probably aware that it allows you to treat your Windows file systems (mounted under /mnt/c, /mnt/d, etc.) as case sensitive.
0 kommentar(er)
