summaryrefslogtreecommitdiff
path: root/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment
blob: aa6eb9345a1ca254d8f9bf39c79e76915b1b8a9a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 1"
 date="2013-06-10T17:22:11Z"
 content="""
encfs appears to not allow creation of hard links to files:

[[!format sh \"\"\"
joey@gnu:~/tmp/other_empty_dir>ln me me2
ln: failed to create hard link `me2' => `me': Operation not permitted
\"\"\"]]

According to the documentation, this is a limitation when using External IV Chaining. And only a problem if you choose paranoia mode when setting up encfs.

git-annex uses hard links in a limited number of code paths, most notably `git annex add` uses them when locking down files.

encfs seems like something I'd like to interoperate well with git-annex. So, it seems worthwhile to break out lack of hard links support from the other limitations currently lumped into \"cripped file system\". I've done so.

----

Also made it stop setting direct mode on bare repositories, although that configuration had no effect anyway.
"""]]