From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] who can write venti archives?
Date: Thu, 11 Dec 2003 15:20:14 +0100 [thread overview]
Message-ID: <30be412e87fde5a21492ddd0e732787a@plan9.escet.urjc.es> (raw)
In-Reply-To: <323520958f5dc4952a92683a3a2c47bd@caldo.demon.co.uk>
> to prohibit all but fossil and authsrv-related connections
> to the file serving machine; in particular venti wouldn't
> appear directly on the network.
What we do, in case that helps, is to make venti listen only in
a loopback interface, so that at least you have to log into the
file server to connect to venti. Later, fossil listens on the network
for foreigners to mount it.
hth
next prev parent reply other threads:[~2003-12-11 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 10:44 okamoto
2003-12-11 13:23 ` Charles Forsyth
2003-12-11 14:20 ` Fco.J.Ballesteros [this message]
2003-12-12 2:03 ` okamoto
2003-12-12 3:19 ` Russ Cox
2003-12-12 4:03 ` okamoto
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=30be412e87fde5a21492ddd0e732787a@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).