docs: a few small edits to try to guide newcomers through the docs

These edits were suggested by my watching over Jake Appelbaum's shoulder as he completely ignored/skipped/missed install.html and also as he decided that debian.txt wouldn't help him with basic installation. Then I threw in a few docs edits that have been sitting around in my sandbox asking to be committed for months.
This commit is contained in:
Zooko O'Whielacronx 2010-03-03 15:19:02 -08:00
parent b76b588872
commit 34a50b857a
5 changed files with 13 additions and 9 deletions

11
README
View File

@ -1,11 +1,14 @@
Welcome to the Tahoe-LAFS project [1], a secure, decentralized,
Welcome to the Tahoe-LAFS project--a secure, decentralized,
fault-tolerant filesystem. All of the source code is available under
a Free Software, Open Source licence (or two).
Please see docs/about.html for an introduction, docs/install.html for
install instructions, docs/running.html for usage instructions.
To get started please read
* docs/install.html
* docs/about.html
* docs/running.html
Finally, see docs/known_issues.txt for things that you need to know
about if you are relying on Tahoe to store your valuable data.
[1] http://allmydata.org
http://tahoe-lafs.org

View File

@ -1,7 +1,7 @@
= Debian Support =
One convenient way to deploy a Tahoe grid is via debian packages.
One convenient way to install Tahoe-LAFS is with debian packages.
== Building Debian Packages ==

View File

@ -10,11 +10,11 @@
<body>
<h1>About Tahoe-LAFS</h1>
<p>Welcome to <a href="http://allmydata.org/trac/tahoe-lafs">the Tahoe-LAFS project</a>, a secure, decentralized, fault-tolerant filesystem. <a href="about.html">About Tahoe-LAFS.</a>
<p>Welcome to <a href="http://tahoe-lafs.org">the Tahoe-LAFS project</a>, a secure, decentralized, fault-tolerant filesystem. <a href="about.html">About Tahoe-LAFS.</a>
<h1>How To Install Tahoe-LAFS</h1>
<p>This procedure has been verified to work on Windows, Cygwin, Mac, many flavors of Linux, Solaris, FreeBSD, OpenBSD, and NetBSD. It's likely to work on other platforms. If you have trouble with this install process, please write to <a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev">the tahoe-dev mailing list</a>, where friendly hackers will help you out.</p>
<p>This procedure works on Windows, Cygwin, Mac, many flavors of Linux (including Debian), Solaris, FreeBSD, OpenBSD, and NetBSD. It's likely to work on other platforms. If you have trouble with this install process, please write to <a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev">the tahoe-dev mailing list</a>, where friendly hackers will help you out.</p>
<h2>Install Python</h2>
@ -26,7 +26,7 @@
<p>Download the 1.6.1 release zip file:</p>
<pre><a
href="http://allmydata.org/source/tahoe/releases/allmydata-tahoe-1.6.1.zip">http://allmydata.org/source/tahoe/releases/allmydata-tahoe-1.6.1.zip</a></pre>
href="http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.6.1.zip">http://allmydata.org/source/tahoe-lafs/releases/allmydata-tahoe-1.6.1.zip</a></pre>
<h2>Build Tahoe-LAFS</h2>

View File

@ -1,5 +1,6 @@
#!/usr/bin/env python
# WARNING. There is a bug in this script so that it does not simulate the actual Tahoe Two server selection algorithm that it was intended to simulate. See http://allmydata.org/trac/tahoe-lafs/ticket/302 (stop permuting peerlist, use SI as offset into ring instead?)
import random

View File

@ -212,7 +212,7 @@ class TahoeFileTarget:
PUT(self.url, inf)
# TODO: this always creates immutable files. We might want an option
# to always create mutable files, or to copy mutable files into new
# mutable files.
# mutable files. ticket #835
class TahoeDirectorySource:
def __init__(self, nodeurl, cache, progressfunc):