From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more factotum nitpicks
Date: Thu, 14 Nov 2002 01:47:50 -0500 [thread overview]
Message-ID: <20e7458b0f62a8a87853b91fe6d12996@plan9.bell-labs.com> (raw)
Whenever a client calls up an authentication
server, it knows what domain it is expecting
to find there. The server can discriminate
based on what domain the client asks for.
This would have been useful when setting
up sources, for example, which has two different
auth domains -- one for the kfs file server you
know as `sources' and one for the rest of the machine.
We did this with some ugly namespace tricks.
It would be nice if it were easier.
Russ
next reply other threads:[~2002-11-14 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 6:47 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 2:09 presotto
2002-11-14 6:37 ` Roman V. Shaposhnick
2002-11-14 1:28 Roman V. Shaposhnick
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=20e7458b0f62a8a87853b91fe6d12996@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).