9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <knapjack@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 killer applications?
Date: Wed, 17 Nov 2004 16:06:09 -0800	[thread overview]
Message-ID: <6e35c062041117160648281cc8@mail.gmail.com> (raw)
In-Reply-To: <a8cd96ac64b3a8fabd70e1b2204b5245@collyer.net>

On Wed, 17 Nov 2004 15:16:39 -0800, geoff@collyer.net <geoff@collyer.net> wrote:
> Actually /sys/src/fs with a WORM jukebox strikes me as a better
> archival system than venti, especially if one is really concerned
> about immutability.

I think more about longevity and sheer size.  I think in Sean's
original paper or the wiki it mentions making arenas some reasonable
size -- say 650MB -- so you can make archival copies of the arenas in
case of disaster.  Burn an archival-quality copy to CD (or multiple
CDs) and store them away for seven years in redundant locations, and
you're well on your way to meeting a whole slew of legal requirements.
 If you get paranoid about the live arenas, you can always go back and
compare checksums against the archived versions.

Plus, if you're saving seven years' worth of data, venti seems a
little more efficient at using the available storage space (*WARNING*
-- layman speaking).  Now, using WORM drives for venti arenas might be
even better....

I did chuckle at the statement about shredability, because I often
picture RIAA or the BSA rooting through someone's venti archive
looking for copyrighted material.  That MP3 deleted two days later
just lingers, waiting for the right lawyer to come along.

-Jack


  reply	other threads:[~2004-11-18  0:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 15:33 Brantley Coile
2004-11-17 16:51 ` Matthias Teege
2004-11-17 17:52 ` Jack Johnson
2004-11-17 18:06   ` Dave Lukes
2004-11-17 23:16   ` geoff
2004-11-18  0:06     ` Jack Johnson [this message]
2004-11-18  5:32       ` vdharani
2004-11-18  1:56         ` Tim Newsham
2004-11-18  3:54           ` Jack Johnson
2004-11-18  0:59 ` Kenji Okamoto
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 17:25 Benjamin Huntsman
2004-11-17 20:34 ` Vester Thacker
2004-11-16 21:24 Benjamin Huntsman
2004-11-16 16:07 David Leimbach
2004-11-16 16:11 ` Fco. J. Ballesteros
2004-11-15 19:28   ` Steve Simon
2004-11-16 16:17   ` andrey mirtchovski
2004-11-16 17:07     ` matt
2004-11-16 17:15     ` rog
2004-11-17  0:15       ` Charles Forsyth
2004-11-17  1:08         ` Kenji Okamoto
2004-11-17  8:58           ` Richard Miller
2004-11-17 15:01             ` Ronald G. Minnich
2004-11-16 21:14     ` Jack Johnson
2004-11-16 16:37 ` Matthias Teege
2004-11-17 20:53 ` Vester Thacker
2004-11-22 20:16   ` Dan Cross

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=6e35c062041117160648281cc8@mail.gmail.com \
    --to=knapjack@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).