From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] magic loopback
Date: Tue, 19 Sep 2006 19:25:14 -0400 [thread overview]
Message-ID: <ee9e417a0609191625u2c09b16i87d10b7791d4aba7@mail.gmail.com> (raw)
In-Reply-To: <944652eb9310f5c6ddbc5430e800286a@quanstro.net>
/srv just connects file descriptors. It doesn't have listen and announce.
So unless you are posting 9P sessions to /srv
(in which case the kernel takes care of multiplexing
the many clients who open /srv/your-service), posting
to /srv is dramatically less useful than announcing a
network address: there's no way to keep clients separate.
9P is not a very good model for Venti. At best the 9P realization
would be a single file /venti-rpc that clients could open and
use to issue real RPCs.
Russ
next prev parent reply other threads:[~2006-09-19 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 20:02 erik quanstrom
2006-09-18 3:18 ` erik quanstrom
2006-09-18 8:56 ` Richard Miller
2006-09-18 23:16 ` erik quanstrom
2006-09-19 8:04 ` Richard Miller
2006-09-19 23:07 ` erik quanstrom
2006-09-19 23:25 ` Russ Cox [this message]
2006-09-19 23:36 ` erik quanstrom
2006-09-20 0:54 ` Russ Cox
2006-09-20 9:48 ` Charles Forsyth
2006-09-20 9:55 Fco. J. Ballesteros
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=ee9e417a0609191625u2c09b16i87d10b7791d4aba7@mail.gmail.com \
--to=rsc@swtch.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).