From: "Fariborz 'Skip' Tavakkolian" <fst@real.com>
To: 9fans@cse.psu.edu, 9fans@cse.psu.edu
Subject: Re: [9fans] Persistent cache for cfs
Date: Sat, 12 May 2001 10:35:28 -0700 [thread overview]
Message-ID: <3.0.5.32.20010512103528.018b9100@mail.real.com> (raw)
In-Reply-To: <20010512130225.4B64F199E1@mail.cse.psu.edu>
Stash is exactly what I was shooting for. There are a couple
of distributed fs options on the Linux/*BSD side with OpenAFS (IBM) and
Coda (CMU); Both use a cache to continue operating when disconnected.
Their models have too much unnecessary overhead for Plan9.
At 09:02 AM 5/12/01 -0400, presotto@plan9.bell-labs.com wrote:
>What plan 9 could use is a stash, something that stores files
>you accessed recently, perhaps picking them up lazily. That way,
>you could disconnect and keep working. You'ld still need a
>local file system like Unix's root file system because you need
>some guaranteed files, or you could just provide a set of files
>that the stash absolutely has to have, in addition to what it
>caches. It would be a nice and useful project for someone to
>do. There was a lot of good work some years ago at Columbia
>and other places. No idea where it went.
next prev parent reply other threads:[~2001-05-12 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 13:02 presotto
2001-05-12 17:35 ` Fariborz 'Skip' Tavakkolian [this message]
2001-05-16 8:43 ` Matthew Weigel
2001-05-18 8:35 ` Douglas A. Gwyn
2001-05-18 14:50 ` Douglas A. Gwyn
2001-05-21 8:39 ` Matthew Weigel
2001-05-21 14:26 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2001-05-12 4:26 Fariborz '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=3.0.5.32.20010512103528.018b9100@mail.real.com \
--to=fst@real.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).