9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] magic loopback
Date: Tue, 19 Sep 2006 18:07:11 -0500	[thread overview]
Message-ID: <944652eb9310f5c6ddbc5430e800286a@quanstro.net> (raw)
In-Reply-To: <b7794bea35847e9cfd51993563537397@hamnavoe.com>

i realize that venti doesn't speak 9p at all. but what i don't understand is
while what you say is theoretically true, there is currently no way
to tell venti to post to /srv.  venti demands and address (-a) that it announce(2)s.

why does venti not have a -s argument?  and, since you mention it,
why doesn't venti use 9p?  it would seem that authentication would be
critical if you're running venti on a separate machine from the fossil.
and it would seem that using announce wouldn't make sense if one
always ran fossil and venti on the same machine.

so what's the part that i'm missing?

- erik

On Tue Sep 19 03:08:52 CDT 2006, 9fans@hamnavoe.com wrote:
> > if fossl+venti on the
> > same machine is a common setup, shouldn't they should be able to communicate without the 
> > network stack?
> 
> Venti doesn't speak 9p2000 (it has its own RPC protocol), so it can't
> just be mounted from a local /srv like normal Plan 9 services.
> 


  reply	other threads:[~2006-09-19 23:07 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 [this message]
2006-09-19 23:25           ` Russ Cox
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=944652eb9310f5c6ddbc5430e800286a@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).