From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cdrom floppy tape etc, media mount point
Date: Thu, 18 Jul 2002 09:06:20 -0700 [thread overview]
Message-ID: <3D36E77C.9070102@nas.com> (raw)
In-Reply-To: <dd8c4466.0207171331.345d985a@posting.google.com>
>>thus, having done:
>>
>> autodir /n
>>
>>you can do, say:
>>
>> mount /srv/factotum /n/bletheridoo
I was thinking about this last night on the drive home.
Though I realize things will probably change with the new fileserver, I
was thinking about how to get dump functionality from venti as-is. It
occurred to me that one should be able to do something like:
vac -svf $home/vac/`{date -n} -h ventiserver /n/hullabaloo
run via cron, then have a variation on autodirfs that rebuilds the
directory trees dump-style (or some custom style: 2002/Feb/20) based on
the contents of $home/vac, and calls vacfs when traversing to the
appropriate date.
(tangent ahead -- leave while you can)
My mind then started wandering to a coat-check style Web service where
you'd post a file or set of files and vac would return a "ticket" so you
could retrieve it later. Maybe your resume that you only use once a
decade, or some file you'd like to share with friends that lies
somewhere in between needing security and being public information.
It also reminded me of the work done at PARC with small handheld devices
called PARCTABs that have minimal storage, running much like a Plan 9
terminal. One thing I remember reading about them is that they were
designed so people could treat them as if they had storage, so you could
drag documents to the Tab, walk down the hall and copy them to another
workstation, workboard, etc. In reality, the data never moved, but the
representation of the data behaved as if it did, just like icons for
files on a local hard drive.
The part that makes me smile the most in Sean's paper is where he says,
"For a user, it appears that vac compresses any amount of data down to
45 bytes." I think my wristwatch will hold 45 bytes. I can only
imagine how many vac fingerprints a cell phone could hold. Where vac
fingerprints are more powerful than PARCTABs, in my opinion, is that
they're not tied to the network, per se. Fingerprints can be stored on
flash media and popped in a pocket, written on a 3x5 index card and
dropped in the mail, kept on a USB keychain, sent via pager, etc.
With a vacfs port to Inferno and the Inferno IE plug-in (or vacfs
support like WebDAV), you might be able to utilize vac URLs like
vac://hullabaloo/64daefaecc4df4b5cb48a368b361ef56012a4f46. I think it
would/will be fun to experiment with vac fingerprints as tickets for
data using extremely small, cheap devices or Web interfaces or
combinations of the two, along the same lines as Sean's idea of
implementing SFSRO on top of venti.
All of this, of course, for read-only data.
I also wonder if there might be a convenient way to do chaffing and
winnowing using a venti archive, given the amalgam of blocks.
Sorry for the blather. I'm prone to it.
-Jack
next prev parent reply other threads:[~2002-07-18 16:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 13:34 rog
2002-07-16 15:19 ` Scott Schwartz
2002-07-18 9:50 ` Ben
2002-07-18 16:06 ` Jack Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 11:45 Russ Cox
2002-07-18 11:19 rog
2002-07-16 16:09 rog
2002-07-16 15:35 rog
2002-07-16 14:42 ` Sam
2002-07-16 15:39 ` Scott Schwartz
2002-07-16 7:39 Fco.J.Ballesteros
2002-07-15 16:45 rog
2002-07-15 16:02 ` Sam
2002-07-15 16:52 ` Lucio De Re
2002-07-15 19:21 ` Scott Schwartz
2002-07-16 12:26 ` Martin C.Atkins
2002-07-15 16:33 okamoto
2002-07-12 16:16 anothy
2002-07-12 10:44 okamoto
2002-07-12 10:37 Fco.J.Ballesteros
2002-07-12 10:32 okamoto
2002-07-12 10:20 Fco.J.Ballesteros
2002-07-15 9:30 ` Ben
2002-07-12 10:15 okamoto
2002-07-12 7:40 Fco.J.Ballesteros
2002-07-12 2:47 okamoto
2002-07-12 2:17 anothy
2002-07-12 2:07 okamoto
2002-07-12 9:03 ` Don
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=3D36E77C.9070102@nas.com \
--to=fragment@nas.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).