From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] help connect a terminal to kfs or Standalone CPU
Date: Fri, 13 Sep 2002 16:44:41 -0400 [thread overview]
Message-ID: <3a9aa271c31a53ec4d3778370b5caa11@plan9.bell-labs.com> (raw)
did you rename the auth files as directed in cpurc?
can you connect to the auth server using
con -l 'tcp!$auth!ticket'
(ctl-\, q will quit)
?
next reply other threads:[~2002-09-13 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 20:44 Russ Cox [this message]
[not found] <20020915160003.13605.25991.Mailman@psuvax1.cse.psu.edu>
2002-09-16 17:47 ` William Gunnells
-- strict thread matches above, loose matches on Subject: below --
2002-09-14 21:18 Russ Cox
[not found] <20020914160005.21633.45193.Mailman@psuvax1.cse.psu.edu>
2002-09-14 20:43 ` William Gunnells
[not found] <20020912160003.27268.89675.Mailman@psuvax1.cse.psu.edu>
2002-09-13 19:50 ` William Gunnells
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=3a9aa271c31a53ec4d3778370b5caa11@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).