From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Fossil Venti question...
Date: Mon, 27 Dec 2004 10:02:41 -0800 [thread overview]
Message-ID: <3e1162e60412271002c338bb8@mail.gmail.com> (raw)
Perhaps I'm just having difficulty absorbing the relationship. Fossil
is the filesystem server that [optionally?] uses Venti for block
storage? I don't believe my Plan 9 system [currently down due to
hardware failure :(] had Venti but did have fossil.
Do I really want to use Venti with Fossil? Why? I've read some about
how it works but I guess I've missed out on the "use cases" of it.
Fossil seems to have the capability of being the write once system,
making a great archival system, but I don't quite understand the
"why?" for Venti just yet.
Any clarification or pointer to documentation would be greatly
appreciated. I guess I'm not as interested in what it is as why it
is.
Dave
next reply other threads:[~2004-12-27 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 18:02 David Leimbach [this message]
2004-12-27 18:12 ` Tiit Lankots
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=3e1162e60412271002c338bb8@mail.gmail.com \
--to=leimy2k@gmail.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).