From: James Horey <jhorey@cs.unm.edu>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] authentication help
Date: Mon, 9 Feb 2004 17:54:48 -0700 [thread overview]
Message-ID: <200402091754.48633.jhorey@cs.unm.edu> (raw)
Hi, I recently installed both a Plan 9 cpu/auth server and a Plan 9 terminal
following the instructions on the Wiki pages. I am now trying to get the
Plan 9 terminal to authenticate and use the cpu/auth server, but am running
into some trouble.
When I run "cpu -h <auth/cpu ip addr> -c ls /" on the cpu/auth server, I
receive what I expect (a listing of all the files). However when I run that
same command on my Plan 9 terminal, I receive "srvauth::auth server protocol
botch".
Finally for curiousity, I tried using "drawterm -a <ip> -c <ip>" on my Linux
box and received this warning: "cannot authenticate with p9". If this has
anything to do with my /lib/ndb/local file, I would be glad to attach them.
Thanks for anybody that can help!
-James Horey
next reply other threads:[~2004-02-10 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 0:54 James Horey [this message]
2004-02-10 0:33 ` andrey mirtchovski
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=200402091754.48633.jhorey@cs.unm.edu \
--to=jhorey@cs.unm.edu \
--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).