mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-01-29 15:43:54 +00:00
Change some instances of "filesystem" that were missed to "file store".
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
parent
befa4babea
commit
7309aed524
@ -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
|
||||
|
15
relnotes.txt
15
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
|
||||
|
2
setup.py
2
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',
|
||||
|
Loading…
x
Reference in New Issue
Block a user