From 6972df3c54eb79b432c73cf1181593fef68c09eb Mon Sep 17 00:00:00 2001 From: davidsarah <> Date: Thu, 1 Jul 2010 02:45:12 +0000 Subject: [PATCH] Tahoe->Tahoe-LAFS [Imported from Trac: page Capabilities, version 10] --- Capabilities.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Capabilities.md b/Capabilities.md index 516f80b..9946ea6 100644 --- a/Capabilities.md +++ b/Capabilities.md @@ -22,7 +22,7 @@ but updated to take into account literal caps and immutable directories: 13: unknown/future capability strings -In Tahoe, directories are built out of mutable files (a directory is really +In Tahoe-LAFS, directories are built out of mutable files (a directory is really just a particular way to interpret the contents of a given mutable file), and non-directory mutable files aren't used very much. All normal data files are uploaded into immutable files by default. @@ -63,11 +63,11 @@ redesign of the server protocol.) We then use the somewhat-vague term "rootcap" to refer to a cap (usually a directory write cap) that is not present inside any directory, so the only -way to ever reach it is to remember it somewhere outside of Tahoe. It might -be remembered in the allmydata.com rootcap database (indexed by account name -plus password), or it might be remembered in a ~/.tahoe/private/aliases file, -or it might just be written down on a piece of paper. The point is that you -have to start from somewhere, and we refer to such a starting point as a -"rootcap". +way to ever reach it is to remember it somewhere outside of a Tahoe-LAFS +filesystem. It might be remembered in the allmydata.com rootcap database +(indexed by account name plus password), or it might be remembered in a +~/.tahoe/private/aliases file, or it might just be written down on a piece +of paper. The point is that you have to start from somewhere, and we refer +to such a starting point as a "rootcap". ``` \ No newline at end of file