tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Tahoe->Tahoe-LAFS 

[Imported from Trac: page Capabilities, version 10]
davidsarah 2010-07-01 02:45:12 +00:00
parent 9b30a0a639
commit 6972df3c54
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
Capabilities.md

@ -22,7 +22,7 @@ but updated to take into account literal caps and immutable directories:
13: unknown/future capability strings <anything else>
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".
```