In the case that a new user is installing a client node with the
preconceived intent of user some elses' introducer, s/he might (as I did)
skip the documentation concerning the introducer.  If this occurs s/he might
be confused as to the nature of the "introducer.furl" (as I was).
Hopefully this will preempt this error.
  Since, the furl address is now _also_ referred to in the tahoe.cfg, it's
nice that there's a link to that documentation immediately after the client
paragraph.

  Will the introducer directory continue to contain it's furl reference as
"introducer.furl"?

--J
-- 
"It is an unavoidable fact of life that servers can fail, or can turn out to
be malicious..."
--Zooko, Warner and Co.
http://allmydata.org

At the edge
Symbols become subtleties
Consensus Conceptions
Where we dance

ZZ --> <esc>:wq

Hacking --> Yacking --> Yakking --> .... --> Yak-Wrangling
Tue Mar 10 16:28:50 PDT 2009  [email protected]
  * Disambiguate nature of introducer.furl.
    If a naive user is attempting to create a client and attach to an existing 
grid with no previous experience creating introducers it's easy to be confused 
about the nature of "introducer.furl", this should make it harder to 
misinterpret.   In particular I was confused because the volunteer grid wiki 
made no explicit mention of "introducer.furl".  
diff -rN -u old-tahoe/docs/running.html new-tahoe/docs/running.html
--- old-tahoe/docs/running.html 2009-03-10 17:17:37.000000000 -0700
+++ new-tahoe/docs/running.html 2009-03-10 17:17:37.000000000 -0700
@@ -38,7 +38,7 @@
 
     <p>To construct a node run 
"<cite><strong>path-to-the-tahoe-bin-directory</strong>/tahoe 
create-client</cite>", which will
     create <cite>~/.tahoe</cite> to be the node's base directory. Acquire a 
copy
-    of the <cite>introducer.furl</cite> from the introducer and put it into 
this
+    of the <cite>introducer.furl</cite> file from the introducer and put it 
into this
     directory, then run 
"<cite><strong>path-to-the-tahoe-bin-directory</strong>/tahoe start</cite>". 
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, a 
node

Attachment: patch.darcspatch.bz2
Description: BZip2 compressed data

_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev

Reply via email to