From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Archiving appliance
Date: Fri, 11 Jul 2003 09:16:30 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307110915300.22296-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.44.0307110853220.13208-100000@fbsd.cpsc.ucalgary.ca>
On Fri, 11 Jul 2003, andrey mirtchovski wrote:
> - replace NetApp with Fossil/Venti. it really sounds like a good idea. a
> fossil/venti combination gives you exactly the same thing as a NetApp, but
> it has the archival option (dumps), and no NFS as a bonus. (how about
> speed?)
netapp has snapshots however.
> cons: you need to teach your client applications to speak 9p
er ...
> cons: quite a bit. teaching NetApp to talk 9p may be quite the task. you
> still have NFS.
esp. as netapp will say market share for 9p servers is approx 0.0%
> cons: you still have to deal with NFS, and Plan 9 does not a good NFS
> server make, I've heard.
next prev parent reply other threads:[~2003-07-11 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1057912039.10046.16.camel@coffin01>
2003-07-11 15:06 ` andrey mirtchovski
2003-07-11 15:16 ` ron minnich [this message]
2003-07-11 20:22 ` Skip Tavakkolian
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=Pine.LNX.4.44.0307110915300.22296-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).