From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] sources.cs.bell-labs.com
Date: Thu, 31 Jul 2008 12:25:06 -0400 [thread overview]
Message-ID: <20080731162314.D59851E8C3B@holo.morphisms.net> (raw)
In-Reply-To: <2dea59d2b7fd00f5614f7b412ca65b77@9srv.net>
> Is this just 'listen -N' in fossilcons(8)?
> Given that listen and users are fossil-wide, rather
> than fsys-wide, it seems like duplicating what
> sources is doing at a "normal" Plan 9 installation
> would involve running a second fossil. If -N were
> on open (which seems reasonably close to open
> having -A), that wouldn't be the case. Correct?
That depends on what you mean by "duplicating what
sources is doing." Sources runs two fossils (one it boots
from and one it serves to the world) in two different
authentication domains. You could pull that off with
a single fossil instance (i.e., 9P and its clients could deal
with seeing different authentication domains for different
file systems), but it would be a fair amount of work to get
everything lined up right. Much easier just to run
two different fossils. Putting -N on open would be just
one of many changes.
If you had just one authentication domain, then
having an open -N would let you make one of your
file systems not require authentication, like sources,
but still use a single 9P port. I'm not sure how useful
that really is.
Russ
next prev parent reply other threads:[~2008-07-31 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 10:40 Roman V. Shaposhnik
2008-07-30 10:51 ` gdiaz
2008-07-30 11:05 ` Roman V. Shaposhnik
2008-07-30 11:20 ` Roman V. Shaposhnik
2008-07-30 13:29 ` Russ Cox
2008-07-30 15:27 ` a
2008-07-31 16:25 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 11:57 erik quanstrom
2008-07-17 13:01 ` ron minnich
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=20080731162314.D59851E8C3B@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).