from the introducer and put it into this directory, then use
"<code>tahoe run</code>". After that, the node should be off and running. The first
thing it will do is connect to the introducer and get itself connected to
- all other nodes on the grid. By default, "<code>tahoe create-client</code>
+ all other nodes on the grid. By default, "<code>tahoe create-client</code>"
creates a client-only node, that does not offer its disk space to other nodes.
To configure other behavior, use "<code>tahoe create-node</code>" or see
<a href="configuration.rst">configuration.rst</a>.</p>
"<code>tahoe ls tahoe:</code>" and "<code>tahoe cp LOCALFILE
tahoe:foo.txt</code>" to work with your filesystem. The Tahoe-LAFS CLI uses
similar syntax to the well-known scp and rsync tools. See <a
- href="frontends/CLI.txt">CLI.txt</a> for more details.</p>
+ href="frontends/CLI.rst">CLI.rst</a> for more details.</p>
<p>As with the WUI (and with all current interfaces to Tahoe-LAFS), you are
responsible for remembering directory capabilities yourself. If you create
<p>You can access your Tahoe-LAFS grid via any <a href="http://en.wikipedia.org/wiki/SSH_file_transfer_protocol">SFTP</a> or
<a href="http://en.wikipedia.org/wiki/File_Transfer_Protocol">FTP</a> client.
- See <a href="frontends/FTP-and-SFTP.txt">FTP-and-SFTP.txt</a> for how to set this up.
+ See <a href="frontends/FTP-and-SFTP.rst">FTP-and-SFTP.rst</a> 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 <code>sshfs</code>.
<h3>The WAPI</h3>
<p>Want to program your Tahoe-LAFS node to do your bidding? Easy! See <a
- href="frontends/webapi.txt">webapi.txt</a>.</p>
+ href="frontends/webapi.rst">webapi.rst</a>.</p>
<h2>Socialize</h2>