From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Replicated, caching and offline capable network fs
Date: Fri, 13 Jul 2007 15:00:08 +0200 [thread overview]
Message-ID: <20070713130008.GA21358@nibiru.local> (raw)
Hi folks,
I'm looking for an replicated and offline capable network filesystem
which can work behind hi latency links. The only usable one I could
find is Coda, but it doesn't exactly suit my needs, some of the
drawbacks are:
* completely own security scheme (AFS style, not Unix)
* own storage, cannot export existing filesystems
* can only transfer complete files
* doesnt work well behind hi latency links (>80ms).
* not very stable
So I'm thinking about designing a new one, based on 9p :)
The idea is:
* Client side (mounting) is done via normal 9p
* Extended 9p protocol between the primary server and local cache
* Local cache stores its stuff within a local filesystem or
an database
* Files can be watched for update notification
* Batched transfers in background to prevent unnecessary blocking
Does anyone like to join me ?
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next reply other threads:[~2007-07-13 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:00 Enrico Weigelt [this message]
2007-07-13 13:44 ` erik quanstrom
2007-07-13 16:42 ` Skip Tavakkolian
2007-07-13 17:34 ` Francisco J Ballesteros
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=20070713130008.GA21358@nibiru.local \
--to=weigelt@metux.de \
--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).