1 patch for repository zooko@dev.allmydata.org:/home/darcs/tahoe-lafs/trunk: Fri Jan 28 08:07:00 MST 2011 zooko@zooko.com * docs: edit running.html, change "http://allmydata.org" to "http://tahoe-lafs.org" in NEWS and README.txt, add Josh Wilcox to CREDITS for his contribution of doc patches New patches: [docs: edit running.html, change "http://allmydata.org" to "http://tahoe-lafs.org" in NEWS and README.txt, add Josh Wilcox to CREDITS for his contribution of doc patches zooko@zooko.com**20110128150700 Ignore-this: 133a97d7c9e9401f2754d83f64733d1d ] { hunk ./CREDITS 130 E: ravi@p-static.net D: converted docs from .txt to .rst +N: Josh Wilcox +D: docs + replace ./Makefile [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org hunk ./NEWS 68 - We now host binary packages so that users on certain operating systems can install without having a compiler. - + - Use a newer version of a dependency if needed, even if an older version is installed. This would previously cause a VersionConflict error. (#1190) replace ./NEWS [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org hunk ./README.txt 26 See `TGPPL.PDF`_ for why the TGPPL exists, graphically illustrated on three slides. .. _quickstart.html: http://allmydata.org/source/tahoe-lafs/trunk/docs/quickstart.html -.. _COPYING.GPL: http://tahoe-lafs.org/trac/dupfilefind/browser/COPYING.GPL -.. _COPYING.TGPPL.html: http://tahoe-lafs.org/source/dupfilefind/trunk/COPYING.TGPPL.html -.. _TGPPL.PDF: http://tahoe-lafs.org/~zooko/tgppl.pdf +.. _COPYING.GPL: http://allmydata.org/trac/dupfilefind/browser/COPYING.GPL +.. _COPYING.TGPPL.html: http://allmydata.org/source/dupfilefind/trunk/COPYING.TGPPL.html +.. _TGPPL.PDF: http://allmydata.org/~zooko/tgppl.pdf replace ./README.txt [A-Za-z_0-9\-\.] allmydata.org tahoe-lafs.org hunk ./docs/running.html 14

How To Run Tahoe-LAFS

This is how to run a Tahoe-LAFS client or a complete Tahoe-LAFS grid. First you - have to install the Tahoe-LAFS software, as documented in install.html.

This is how to run a Tahoe-LAFS client to connect to an + existing grid, or how to set up a complete Tahoe-LAFS grid. First + you have to install the Tahoe-LAFS software, as documented + in install.html.

The tahoe program in the bin directory is used to create, start, and stop nodes. Each node lives in a separate base hunk ./docs/running.html 24 directory, in which there is a configuration file named tahoe.cfg. Nodes read and write files within this base directory.

A grid consists of a set of storage nodes and client nodes - running the Tahoe-LAFS code. There is also an introducer node that - is responsible for getting the other nodes talking to each other.

A grid consists of a set of storage nodes + and client nodes (also known as gateway nodes) + running the Tahoe-LAFS code. There is also an introducer + node that is responsible for getting the other nodes talking + to each other. Which grid of storage servers your client will + connect to is determined solely by the introducer—if you configure + your node to connect to a certain introducer then your node will + only use those storage servers provided by that introducer. If you + configure your node to connect to a new introducer of your own + creation (see below), then your node will not connect to any + storage servers until you've created some storage servers and told them + to register themselves with that introducer.

If you're getting started we recommend you try connecting to the the hunk ./docs/running.html 39 - public test grid as you only need to create a client node. - When you want to create your own grid you'll need to create the - introducer and several initial storage nodes (see the note about - small grids below).

+ public test grid—you will need to create only a gateway node + to do that. When you want to create your own grid you'll need to + create the introducer and several initial storage nodes (see the + note about small grids below).

If the Tahoe-LAFS bin directory is not on your PATH, then in all the command lines below, specify the full path to bin/tahoe.

hunk ./docs/running.html 129

The SFTP and FTP frontends

You can access your Tahoe-LAFS grid via any SFTP or - FTP client. + FTP client. See FTP-and-SFTP.rst for how to set this up. On most Unix platforms, you can also use SFTP to plug Tahoe-LAFS into your computer's local filesystem via sshfs. hunk ./docs/running.html 133 - +

The SftpFrontend page on the wiki has more information about using SFTP with Tahoe-LAFS.

hunk ./setup.py 6 # Tahoe-LAFS -- secure, distributed storage grid # -# Copyright © 2008-2010 Allmydata, Inc. +# Copyright © 2008-2011 Allmydata, Inc. # # This file is part of Tahoe-LAFS. # } Context: [setup: adjust tests to use the new interface of check_requirement which has a 3-tuples instead of a 2-tuple zooko@zooko.com**20110128141546 Ignore-this: d4c6197c78c156e7ae3c3444d81db9ed fixes #1339 ] [src/allmydata/__init__.py: fix #1339, give an indication in the --version[-and-path] output of when the imported setuptools is distribute, and use a separate element in _vers_and_locs_list tuples for information other than the package name and location. This also changes slightly how the sqlite version is reported. david-sarah@jacaranda.org**20110128054150 Ignore-this: 47e8d2afed1f8114681e9094dc93276 ] [TAG allmydata-tahoe-1.8.2b1 warner@lothar.com**20110126061431] Patch bundle hash: 76ceb24dbc21423b2d4f23de7a3124fbd10240c7