*** Immutable Directories
-Tahoe-LAFS can now create and handle immutable directories (#XXX). These are
+Tahoe-LAFS can now create and handle immutable directories (#607). These are
read just like normal directories, but are "deep-immutable", meaning that all
their children (and everything reachable from those children) must be immutable
objects (i.e. immutable/literal files, and other immutable directories).
*** "tahoe backup" now creates immutable directories, backupdb has dircache
The "tahoe backup" command has been enhanced to create immutable directories
-(in previous releases, it created read-only mutable directories) (#XXX). This
+(in previous releases, it created read-only mutable directories) (#828). This
is significantly faster, since it does not need to create an RSA keypair for
each new directory. Also "DIR-IMM" immutable directories are repairable, unlike
"DIR-RO" read-only mutable directories (at least in this release: a future
command from reading their contents), instead of throwing an exception and
terminating the backup process. It also skips over symlinks, because these
cannot be represented faithfully in the Tahoe-side filesystem. A warning
-message will be emitted each time something is skipped. (#729, #850, #641) XXX
+message will be emitted each time something is skipped. (#729, #850, #641)
*** "create-node" command added, "create-client" now implies --no-storage
services. It is a more general-purpose replacement for "tahoe create-client".
The default configuration has storage service enabled. For convenience, the
"--no-storage" argument makes a tahoe.cfg file that disables storage
-service. (#XXX)
+service. (#760)
"tahoe create-client" has been changed to create a Tahoe-LAFS node without a
storage service. It is equivalent to "tahoe create-node --no-storage". This
** Performance Improvements
Download of immutable files begins as soon as the downloader has located the K
-necessary shares (#XXX). In both the previous and current releases, a
+necessary shares (#928, #287). In both the previous and current releases, a
downloader will first issue queries to all storage servers on the grid to
locate shares before it begins downloading the shares. In previous releases of
Tahoe-LAFS, download would not begin until all storage servers on the grid had
ANNOUNCING v1.6 of Tahoe-LAFS
-The Tahoe-LAFS team is pleased to announce the immediate
-availability of version 1.6 of Tahoe-LAFS, an extremely
-reliable distributed key-value store and cloud filesystem.
+We are pleased to announce the immediate availability of
+version 1.6 of Tahoe-LAFS, an extremely reliable distributed
+data store.
Tahoe-LAFS is the first cloud storage system which offers
"provider-independent security" -- meaning that not even your
http://allmydata.org/source/tahoe/trunk/docs/about.html
Tahoe-LAFS v1.6.0 is the successor to v1.5.0, which was
-released August 1, 2009. In this major new release, we've added
-deep-immutable directories (cryptographically unalterable
-permanent snapshots), greatly increased performance for some
-common operations, and improved the help text, documentation,
-command-line options, and web user interface. The FUSE plugin
-has been fixed. We also fixed a few bugs. See the release notes
-for details:
+released August 1, 2009 [1]. This release includes major
+performance improvements, usability improvements, and one major
+new feature: deep-immutable directories (cryptographically
+unalterable permanent snapshots). See the release notes for
+details.
http://allmydata.org/source/tahoe/trunk/relnotes.txt
-In addition to the core storage system itself, a crop of
-related projects have sprung up to extend it and to integrate
-it into operating systems and applications. These include
-frontends for Windows, Macintosh, JavaScript, and iPhone, and
-plugins for Hadoop, bzr, duplicity, TiddlyWiki, and more. See
-the Related Projects page:
+In addition to the core storage system itself, volunteers have
+developed related projects to integrate it with other
+tools. These include frontends for Windows, Macintosh,
+JavaScript, and iPhone, and plugins for Hadoop, bzr, duplicity,
+TiddlyWiki, and more. As of this release, contributors have
+added an Android frontend and a working read-only FUSE
+frontend. See the Related Projects page on the wiki:
http://allmydata.org/trac/tahoe/wiki/RelatedProjects
ANNOUNCING Tahoe, the Least-Authority File System, v1.6
-The Tahoe-LAFS team is pleased to announce the immediate
-availability of version 1.6 of Tahoe-LAFS, an extremely
-reliable distributed key-value store and cloud filesystem.
+We are pleased to announce the immediate availability of
+version 1.6 of Tahoe-LAFS, an extremely reliable distributed
+data store.
Tahoe-LAFS is the first cloud storage system which offers
"provider-independent security" -- meaning that not even your
http://allmydata.org/source/tahoe/trunk/docs/about.html
Tahoe-LAFS v1.6.0 is the successor to v1.5.0, which was
-released August 1, 2009 [1]. This release offers major
+released August 1, 2009 [1]. This release includes major
performance improvements, usability improvements, and one major
new feature: deep-immutable directories (cryptographically
-unalterable permanent snapshots), See the NEWS file [2] for
+unalterable permanent snapshots). See the NEWS file [2] for
details.
of Allmydata, Inc. [12], a provider of commercial backup
services. Allmydata founded the Tahoe-LAFS project and
contributed hardware, software, ideas, bug reports,
-suggestions, demands, and they employedg several Tahoe-LAFS
+suggestions, demands, and they employed several Tahoe-LAFS
hackers and instructed them to spend part of their work time on
this Free Software project. Also they awarded customized
t-shirts to hackers who found security flaws in Tahoe-LAFS (see
-the Hack Tahoe-LAFS Hall Of Fame [13]). After discontinuing funding of
-Tahoe-LAFS R&D in early 2009, Allmydata, Inc. has continued to
-provide servers, co-lo space, bandwidth, and small personal
-gifts as tokens of appreciation. (Also they continue to provide
-bug reports.) Thank you to Allmydata, Inc. for their generous
-and public-spirited support.
+the Hack Tahoe-LAFS Hall Of Fame [13]). After discontinuing
+funding of Tahoe-LAFS R&D in early 2009, Allmydata, Inc. has
+continued to provide servers, co-lo space, bandwidth, and small
+personal gifts as tokens of appreciation. (Also they continue
+to provide bug reports.) Thank you to Allmydata, Inc. for their
+generous and public-spirited support.
This is the third release of Tahoe-LAFS to be created solely as
a labor of love by volunteers. Thank you very much to the
projects / tahoe-lafs / tahoe-lafs.git / commitdiff