From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] connecting venti: no route
Date: Sat, 9 Dec 2006 14:38:45 +0000 [thread overview]
Message-ID: <6ce2c4c0835957c1ada4c120ade59f50@quintile.net> (raw)
In-Reply-To: <88a477560612090439v6c8e746bna86ad809c8f54356@mail.gmail.com>
Sounds correct to me.
The magic that parses this and sets up venti is
in /sys/src/9/boot/local.c.
I cannot see fossil started with a -h to give it a host/ip to attach to.
>From my reading of this file you may have fallen through the cracks in
the config used. I think people generally use either a combined venti and
fossil server or completely seperate machines.
I must admit I have not read the code carefully and have already opened
a bottle (its chirstmas after all) but perhaps this gives you a lead in.
-Steve
next prev parent reply other threads:[~2006-12-09 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 12:39 Matthias Teege
2006-12-09 13:09 ` Lucio De Re
2006-12-09 14:22 ` erik quanstrom
2006-12-09 14:38 ` Steve Simon [this message]
2006-12-09 19:16 ` Georg Lehner
2006-12-09 22:41 ` erik quanstrom
2006-12-09 16:36 ` Heiko Dudzus
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=6ce2c4c0835957c1ada4c120ade59f50@quintile.net \
--to=steve@quintile.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).