purplecas.blogg.se

Change permissions on external hard drive time machine
Change permissions on external hard drive time machine












change permissions on external hard drive time machine change permissions on external hard drive time machine

This is controlled by the umask value which defaults to 0000 in WSL. This is kind of separate from the mounting problem but newly created files and directories in the “real” Linux directory structure also get a bad set of default permissions: 0666 for files and 0777 for directories.

  • fmask value masks out the group and others execute bit for just filesįiles should now show up with a comfortable permission setting of 0644 and directories with 0755 if they’re mounted under /mnt.
  • unsets) the group and others write bit for both files and directories It partially affects the underlying Windows permissions for more details see the Dev Blog link above.
  • metadata turns on a mostly parallel of file permission metadata that allows WSL file permissions changes to be persisted.
  • The options key is a bit more interesting:.
  • The enabled key is probably unnecessary but it explicitly turns on automounting (default is true).
  • change permissions on external hard drive time machine

  • The automount section changes the settings for drives that are automounted under /mnt.
  • You can read the “official” Microsoft documentation on their Dev Blog but here is my explanation line-by-line: enabled = true options = "metadata,umask=22,fmask=11" What it Does The short version is to add this section to your WSL instance’s /etc/wsl.conf (the file probably does not exist, just create it): The fix has two pieces: fixing how WSL mounts Windows drives and then fixing the permissions for newly created files. What this means in practice is that every file has permissions 0777 which causes me issues because git will preserve the execute bit on tracked files. The good news is that WSL can “mount” Windows drives under /mnt, the bad news is that it does an awful job of emulating anything near good Linux file permissions. I have not done a ton of research but it appears that the emulated Linux filesystem is sandboxed and is stored on actual disk in some place that is not human friendly. Fortunately Microsoft introduced Windows Subsystem for Linux (WSL) a while ago so I can now have my cake and eat it too. I used Cygwin in the past but I really like the familiarity of the Ubuntu toolchain. git) without having to boot-up a virtual machine. Windows 10 is my daily driver at home so I need a way to use some Linux command-line utilities (e.g.














    Change permissions on external hard drive time machine