From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
Date: Sat, 26 Jul 2008 15:10:37 -0400 [thread overview]
Message-ID: <20080726190827.1EA211E8C1C@holo.morphisms.net> (raw)
In-Reply-To: <0A2908D4-84FC-4C4F-B12D-87D4573A82D4@gmail.com>
> The reason I ask is that I missed that step the first time I tried to
> set up the CPU/Auth server, but I've since gone through it all again
> carefully more than once, and I stll get "connection rejected" with
> my Ken's file server. (Yes I know fossil/venti is the current
> standard, but what can I say, I'm, perhaps irrationally, or at least
> non-rationally, attached to the old file server.)
"connection rejected" is a message the file server prints
in the IL stack. I believe it has nothing to do with
authentication, but I also don't know what the criteria
are for rejection.
You can test connectivity using aux/9pcon:
cpu% aux/9pcon -n tcp!web.mit.edu!9fs
aux/9pcon: dial: connection refused
cpu%
If it does connect (which I doubt), you can try starting
a 9P session:
cpu% aux/9pcon -n tcp!sources.cs.bell-labs.com!9fs
Tversion 8192 9P2000
-> Tversion tag 65535 msize 8192 version '9P2000'
<- Rversion tag 65535 msize 8192 version '9P2000'
Tattach 1 -1 rsc ''
-> Tattach tag 3 fid 1 afid -1 uname rsc aname
<- Rattach tag 3 qid (0000000000000002 0 d)
cpu%
9pcon has no prompt; I typed the Tversion and Tattach lines.
Your server will probably reply to the Tattach with an Rerror;
sources is special.
Russ
next prev parent reply other threads:[~2008-07-26 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 13:40 g.pavelcak
2008-07-26 16:15 ` Russ Cox
2008-07-26 18:28 ` Gregory Pavelcak
2008-07-26 18:50 ` [9fans] CPU Server Wiki, auth/keyfs, erik quanstrom
2008-07-26 19:10 ` Russ Cox [this message]
2008-07-27 13:33 ` [9fans] CPU Server Wiki, auth/keyfs, and password for the machine Gregory Pavelcak
2008-07-27 14:42 ` [9fans] CPU Server Wiki, auth/keyfs, erik quanstrom
2008-07-27 14:55 ` Skip Tavakkolian
2008-07-27 15:40 ` Gregory Pavelcak
2008-07-27 16:48 ` erik quanstrom
2008-07-28 10:17 ` Gregory Pavelcak
2008-07-28 10:49 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080726190827.1EA211E8C1C@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).