From 092b29409cc2f04e2bff4f72a376091b206d6776 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 10 Jun 2013 17:22:11 +0000 Subject: Added a comment --- ...ent_1_5c5be012e1171ef108f38825d72791b6._comment | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment diff --git a/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment b/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment new file mode 100644 index 000000000..aa6eb9345 --- /dev/null +++ b/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment @@ -0,0 +1,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. +"""]] -- cgit v1.2.3