From: Daira Hopwood Date: Fri, 31 Jul 2015 17:21:47 +0000 (+0100) Subject: Change some instances of "filesystem" that were missed to "file store". X-Git-Url: https://git.rkrishnan.org/vdrive/%22news.html/simplejson/encoder.py.html?a=commitdiff_plain;h=7309aed524f3bc44ec4035d35556118eea6416ba;p=tahoe-lafs%2Ftahoe-lafs.git Change some instances of "filesystem" that were missed to "file store". Signed-off-by: Daira Hopwood --- diff --git a/docs/about.rst b/docs/about.rst index 6df61229..e6d5612d 100644 --- a/docs/about.rst +++ b/docs/about.rst @@ -45,7 +45,7 @@ Here's how it works: A "storage grid" is made up of a number of storage servers. A storage server has direct attached storage (typically one or more hard disks). A "gateway" communicates with storage nodes, and uses them to provide access to the -filesystem over protocols such as HTTP(S), SFTP or FTP. +file store over protocols such as HTTP(S), SFTP or FTP. Note that you can find "client" used to refer to gateway nodes (which act as a client to storage servers), and also to processes or programs connecting to @@ -72,7 +72,7 @@ An alternate deployment mode is that the gateway runs on a remote machine and the user connects to it over HTTPS or SFTP. This means that the operator of the gateway can view and modify the user's data (the user *relies on* the gateway for confidentiality and integrity), but the advantage is that the -user can access the filesystem with a client that doesn't have the gateway +user can access the file store with a client that doesn't have the gateway software installed, such as an Internet kiosk or cell phone. Access Control diff --git a/relnotes.txt b/relnotes.txt index e9471652..d7f671b3 100644 --- a/relnotes.txt +++ b/relnotes.txt @@ -1,7 +1,7 @@ -ANNOUNCING Tahoe, the Least-Authority File System, v1.10.2 +ANNOUNCING Tahoe, the Least-Authority File Store, v1.10.2 The Tahoe-LAFS team is pleased to announce version 1.10.2 of -Tahoe-LAFS, an extremely reliable distributed storage system. +Tahoe-LAFS, an extremely reliable decentralized storage system. Get it here: https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst @@ -25,12 +25,11 @@ were fixed too. See the NEWS file [1] for details. WHAT IS IT GOOD FOR? -With Tahoe-LAFS, you distribute your filesystem across -multiple servers, and even if some of the servers fail or are -taken over by an attacker, the entire filesystem continues to -work correctly, and continues to preserve your privacy and -security. You can easily share specific files and directories -with other people. +With Tahoe-LAFS, you distribute your data across multiple +servers. Even if some of the servers fail or are taken over +by an attacker, the entire file store continues to function +correctly, preserving your privacy and security. You can +easily share specific files and directories with other people. In addition to the core storage system itself, volunteers have built other projects on top of Tahoe-LAFS and have diff --git a/setup.py b/setup.py index 190c339c..035b0c9c 100644 --- a/setup.py +++ b/setup.py @@ -419,7 +419,7 @@ if version: setup_args["version"] = version setup(name=APPNAME, - description='secure, decentralized, fault-tolerant filesystem', + description='secure, decentralized, fault-tolerant file store', long_description=open('README.rst', 'rU').read(), author='the Tahoe-LAFS project', author_email='tahoe-dev@tahoe-lafs.org',