diff options
| author |  ghen1 <ghen1@web> | 2015-07-24 12:36:55 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-07-24 12:36:55 +0000 |
| commit | 609478c5b39a068a39b822ff6aba8ed6052eb1f0 (patch) | |
| tree | 198f218f1352975474c3396c476f168860945e39 | |
| parent | 24d0030e8898cdce9f082bbecd6f2d81581c1a08 (diff) | |
| -rw-r--r-- | doc/forum/git-annex_does_not_protect_files_on_NTFS-Fuse.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/git-annex_does_not_protect_files_on_NTFS-Fuse.mdwn b/doc/forum/git-annex_does_not_protect_files_on_NTFS-Fuse.mdwn new file mode 100644 index 000000000..e8084f6ff --- /dev/null +++ b/doc/forum/git-annex_does_not_protect_files_on_NTFS-Fuse.mdwn @@ -0,0 +1,8 @@ +I've read that git-annex probes the host filesystem to determine whether it has the necessary features for an indirect annex. Indirect annexes are supposed to protect annexed files from accidental editing: + + # echo oops > my_cool_big_file + bash: my_cool_big_file: Permission denied + +I have an NTFS drive to share files between my Windows and Linux systems (dual boot). On Linux fuse sets the file permissions to rwx for the user and nothing for the rest, and this cannot be changed. Files in the annex can be modified as in the above example. + +If git-annex detects whether a fs can handle indirect annexes or not, I suggest checking for this case if possible. |