From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Update on Fossil+Venti Stuff
Date: Wed, 21 Mar 2007 14:24:30 -0700 [thread overview]
Message-ID: <20070321212430.9477B5B09@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 21 Mar 2007 16:17:12 EDT." <9ab217670703211317o1958d9b3u647f6ac4fac758cd@mail.gmail.com>
Sounds to me like you want fossil to be a true cache --
lazily writing to venti as more space is needed (or at
regular intervals) and reading back from venti if something
is needed and not in cache.
I wonder if doing so would simplify fossil.... its size
would become a function of peformance (to control data
spill/fill rates). And one would have to always use
fossil+venti and never just fossil. Not to mention venti
then becomes the true file server and one can imagine
building other front end cache filesystems.
> This would be fine with me, however, it seems that, by doing
> this, there's no way to get all of my mp3s listed in a single
> directory -- they would be archived by snapshot date / number, and I'd
> have to search through all of those to get a full list of music.
You can always bind(1) all the snapshots under your music
directory!
next prev parent reply other threads:[~2007-03-21 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:17 Devon H. O'Dell
2007-03-21 21:02 ` Martin Neubauer
2007-03-21 21:05 ` erik quanstrom
2007-03-21 21:24 ` Bakul Shah [this message]
2007-03-22 10:04 ` Richard Miller
2007-03-23 5:17 ` Devon H. O'Dell
2007-03-23 6:14 ` Martin Neubauer
2007-03-23 6:27 ` Devon H. O'Dell
2007-03-23 6:54 ` Martin Neubauer
2007-03-23 14:24 ` David Leimbach
2007-03-23 15:04 ` Devon H. O'Dell
2007-03-23 15:10 ` Richard Miller
2007-03-23 15:29 ` Devon H. O'Dell
2007-03-23 15:39 ` Richard Miller
2007-03-23 15:47 ` Devon H. O'Dell
2007-03-23 19:23 ` Steve Simon
2007-03-23 15:47 ` Richard Miller
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=20070321212430.9477B5B09@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).