Mon Mar 21 23:22:39 MDT 2011 wilcoxjg@gmail.com * docs: fix broken hyperlink and edit wording New patches: [docs: fix broken hyperlink and edit wording wilcoxjg@gmail.com**20110322052239 Ignore-this: 4c51a6faab9811a0e9180918b1578807 ] { hunk ./docs/running.html 14

How To Run Tahoe-LAFS

-

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.

+

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 quickstart.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 101

Create a new directory (with the button labelled "create a directory"). Your web browser will load the new directory. Now if you want to be able to come back to this directory later, you have to bookmark it, or otherwise - save a copy of the URL. If you lose URL to this directory, then you can never + save a copy of the URL. If you lose the URL to this directory, then you can never again come back to this directory.

You can do more or less everything you want to do with a decentralized hunk ./docs/running.html 107 filesystem through the WUI.

+

The CLI

Prefer the command-line? Run "tahoe --help" (the same } Context: [test: increase timeout on a network test because Francois's ARM machine hit that timeout zooko@zooko.com**20110317165909 Ignore-this: 380c345cdcbd196268ca5b65664ac85b I'm skeptical that the test was proceeding correctly but ran out of time. It seems more likely that it had gotten hung. But if we raise the timeout to an even more extravagant number then we can be even more certain that the test was never going to finish. ] [docs/configuration.rst: add a "Frontend Configuration" section Brian Warner **20110222014323 Ignore-this: 657018aa501fe4f0efef9851628444ca this points to docs/frontends/*.rst, which were previously underlinked ] [web/filenode.py: avoid calling req.finish() on closed HTTP connections. Closes #1366 "Brian Warner "**20110221061544 Ignore-this: 799d4de19933f2309b3c0c19a63bb888 ] [Add unit tests for cross_check_pkg_resources_versus_import, and a regression test for ref #1355. This requires a little refactoring to make it testable. david-sarah@jacaranda.org**20110221015817 Ignore-this: 51d181698f8c20d3aca58b057e9c475a ] [allmydata/__init__.py: .name was used in place of the correct .__name__ when printing an exception. Also, robustify string formatting by using %r instead of %s in some places. fixes #1355. david-sarah@jacaranda.org**20110221020125 Ignore-this: b0744ed58f161bf188e037bad077fc48 ] [Refactor StorageFarmBroker handling of servers Brian Warner **20110221015804 Ignore-this: 842144ed92f5717699b8f580eab32a51 Pass around IServer instance instead of (peerid, rref) tuple. Replace "descriptor" with "server". Other replacements: get_all_servers -> get_connected_servers/get_known_servers get_servers_for_index -> get_servers_for_psi (now returns IServers) This change still needs to be pushed further down: lots of code is now getting the IServer and then distributing (peerid, rref) internally. Instead, it ought to distribute the IServer internally and delay extracting a serverid or rref until the last moment. no_network.py was updated to retain parallelism. ] [TAG allmydata-tahoe-1.8.2 warner@lothar.com**20110131020101] Patch bundle hash: b37c8f7cc8e4d92f968be16ceaf271802a07fac3