remove mention of mount option case=dir
(turned out to be unnecessary)
This commit is contained in:
parent
d9c2a632f5
commit
5135730467
1 changed files with 1 additions and 1 deletions
|
@ -141,7 +141,7 @@ The following steps are tested on Windows 10 21h1 with Ubuntu 18.04/20.04 and ar
|
|||
Do the following:
|
||||
|
||||
1. Enable Developer mode in Windows settings so that symlinks can be created without elevated privileges.
|
||||
2. Mount the NTFS drive with metadata option. This line can be added in `/etc/fstab`: `C: /mnt/c drvfs metadata,case=dir`. I prefer to also add `uid=1000,gid=1000,fmask=0133,dmask=0022`.
|
||||
2. Mount the NTFS drive with metadata option. This line can be added in `/etc/fstab`: `C: /mnt/c drvfs metadata`. I prefer to also add `uid=1000,gid=1000,fmask=0133,dmask=0022`.
|
||||
3. Create an empty directory where your repo will be. Then enable case sensitivity `setfattr -n system.wsl_case_sensitive -v 1 <path>`. This attribute will be automatically and recursively applied to any future subdirectories. If setfattr(1) errs out with permission denied, you can also effect the same change in CMD.EXE / Windows Powershell as admin with `fsutil file setCaseSensitiveInfo <path> enable`. You can check that the setting is enabled with `getfattr -n system.wsl_case_sensitive <path>` under WSL1.
|
||||
4. Create the repo however you like (see steps below for cloning a repo with ssh). Immediately after `git annex init`, do `git config annex.crippledfilesystem true`. If you set `crippledfilesystem` before init, then git annex will try to enter an adjusted branch and trigger the first bug. If you do not set `crippledfilesystem` after init, you will trigger the second bug when doing `git annex add`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue