From: Ish Rattan <ratta1i@mail.cmich.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] apu/auth standalone..
Date: Thu, 29 Jun 2000 08:29:43 +0000 [thread overview]
Message-ID: <395A44DF.5F6F12CD@mail.cmich.edu> (raw)
In-Reply-To: <200006280040.UAA23336@cse.psu.edu>
presotto@plan9.bell-labs.com wrote:
> Was keyfs running? Was it mounted inthe namespace of the
> session you were running it in? Is /adm/keys owned by the
> same user netkey was running as and the as you were running as?
Well, I am afraid that I have no answers to the questions. I followed the
steps in
`Configuring a standlone cpu/authentication server' in the document `Getting
started
with Plan9'. I have tried a number of times without success.
Things go haywire with
auth/changeuser bootes
as noted earlier.
- ishwar
next prev parent reply other threads:[~2000-06-29 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 0:39 presotto
2000-06-29 8:29 ` Ish Rattan [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-29 11:58 presotto
2000-06-28 16:21 miller
2000-06-27 23:07 forsyth
2000-06-27 15:13 Ish Rattan
2000-06-27 15:17 ` 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=395A44DF.5F6F12CD@mail.cmich.edu \
--to=ratta1i@mail.cmich.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).