From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pwd
Date: Wed, 15 Aug 2001 18:44:10 +0200 [thread overview]
Message-ID: <20010815184409.H29491@cackle.proxima.alt.za> (raw)
In-Reply-To: <200108151633.MAA07522@augusta.math.psu.edu>; from Dan Cross on Wed, Aug 15, 2001 at 12:33:59PM -0400
On Wed, Aug 15, 2001 at 12:33:59PM -0400, Dan Cross wrote:
>
> CPU servers get around this by either not asking for a password at all
> and having a local KFS file system (started by the kernel) off of which
> they'll start the auth server, or, if talking to a file server, by
> timing out and saying, ``okay, I'll use the key that's in my nvram to
> authenticate myself to the file server....'' (the file server also
> knows it's own key, so that's okay) and then starting up the auth
> server.
>
This does baffle me. I'm sure 2ed had the option to tell the
AUTH server (CPU server, to be exact) that there it was
authoritative, without waiting for a timeout. But I could
never figure out if it was 0.0.0.0 (which caused a panic) or
one of 0.1.0.0 or 0.0.1.0 or whatever or how to make it work.
Pity, because I'm sure I had it all working (2ed, that was)
until I lost the NVRAM and now I have to press enter for each
IP detail _and_ wait for the timeout and I have no idea how to
put that Humpty-Dumpty together again.
++L
next prev parent reply other threads:[~2001-08-15 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 11:40 pac
2001-08-14 14:48 ` Dan Cross
2001-08-15 14:31 ` pac
2001-08-15 16:33 ` Dan Cross
2001-08-15 16:44 ` Lucio De Re [this message]
2001-08-15 17:55 ` Dan Cross
2001-08-16 14:23 ` pac
2001-08-17 16:04 ` Dan Cross
2001-08-14 16:22 Russ Cox
2001-08-15 14:26 ` pac
2001-08-16 1:05 forsyth
2001-08-17 16:47 forsyth
2001-08-17 17:59 ` Dan Cross
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=20010815184409.H29491@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).