Thus, to Linux, (which only receives Linux file metadata), the file may be reported as empty, may not even exist, or may have some metadata, but that metadata may not reflect the file's details resulted in the file's contents being corrupted. permissions, owner, access/update timestamps, etc.). The problem arises when, for example, you use a Windows app/tool to open, create and/or modify a file under your distro root: Since the file was created with a Windows tool, the file won't have any Linux file metadata (e.g. If you create the files directly from Windows you'll mess up things because win32 apps knows nothing about Linux and its file metadata You can see that by running fsutil file layout lxss\root and notice the $EA stream there. Linux files in WSL root file system are created specially with POSIX permissions stored in NTFS extended attributes. See What’s new for WSL in Windows 10 version 1903?Īgain there's still the warning that you must NOT access your Linux files via the AppData folder!įor older versions of Windows 10 see below from bash or enter \\wsl$\ directly in Explorer's address bar Since Windows 10 version 1903 it's possible to access Linux files from Windows with \\wsl$\.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |