From: Pavel Machek <pavel@ucw.cz>
To: Nir Tzachar <tzachar@cs.bgu.ac.il>
Cc: Eric Sandall <eric@sandall.us>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: srfs - a new file system.
Date: Thu, 23 Oct 2003 15:58:51 +0200 [thread overview]
Message-ID: <20031023135850.GF643@openzaurus.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44_heb2.09.0310211406170.8365-100000@nexus.cs.bgu.ac.il>
Hi!
> > This sounds fairly similar to Coda[0], which is already in development and use.
> >
>
> not at all.
>
> coda is not self stabilizing at all.
> srfs is also a totally distributed file system -> see the doc.
> bye
Yes, but perhaps differences can be localized to userspace daemon,
having same kernel part for coda and srfs?
That would be *good*.
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-10-23 20:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 4:11 fs test suite Pat LaVarre
2003-10-07 14:17 ` Randy.Dunlap
2003-10-07 14:59 ` Zachary Peterson
2003-10-07 17:16 ` Randy.Dunlap
2003-10-07 18:54 ` Pat LaVarre
2003-10-07 18:58 ` Randy.Dunlap
2003-10-07 19:26 ` Pat LaVarre
2003-10-20 9:12 ` srfs - a new file system Nir Tzachar
2003-10-20 21:00 ` Eric Sandall
2003-10-21 12:07 ` Nir Tzachar
2003-10-21 14:29 ` Brian Beattie
2003-10-21 16:59 ` Jan Harkes
2003-10-23 13:58 ` Pavel Machek [this message]
2003-10-24 9:28 ` Nir Tzachar
2003-10-22 4:57 ` Erik Andersen
2003-10-22 10:16 ` Nir Tzachar
2003-10-22 14:22 ` Jan Harkes
2003-10-23 7:50 ` Nir Tzachar
2003-10-23 12:33 ` Jan Hudec
2003-10-23 20:12 ` Pat LaVarre
2003-10-24 9:21 ` Nir Tzachar
2003-10-24 12:08 ` Matthew Wilcox
2003-10-24 19:14 ` Nir Tzachar
2003-10-24 14:38 ` Jan Harkes
2003-10-24 19:16 ` Nir Tzachar
2003-10-24 20:11 ` Andreas Dilger
2003-10-24 20:24 ` Pat LaVarre
2003-10-24 20:38 ` Andreas Dilger
2003-10-24 20:52 ` Pat LaVarre
2003-10-24 21:00 ` Nir Tzachar
2003-10-24 21:22 ` Pat LaVarre
2003-10-24 23:03 ` Nir Tzachar
2003-10-25 0:23 ` Bryan Henderson
2003-10-25 10:37 ` Nir Tzachar
2003-10-24 21:15 ` Andreas Dilger
2003-10-24 20:53 ` Nir Tzachar
2003-10-25 8:01 ` Jan Hudec
2003-10-22 10:21 ` Nir Tzachar
2003-10-25 9:27 ` Implementing writepage Charles Manning
2003-10-25 16:18 ` David Woodhouse
2003-10-25 22:40 ` Charles Manning
2003-10-26 10:25 ` David Woodhouse
2003-10-26 15:28 ` Matthew Wilcox
2003-10-26 18:47 ` Mark B
2003-10-26 20:40 ` Charles Manning
2003-10-26 21:04 ` David Woodhouse
2003-10-26 20:54 ` Charles Manning
2003-10-27 8:34 ` Nikita Danilov
2003-10-27 8:39 ` David Woodhouse
2003-10-27 8:43 ` Nikita Danilov
2003-10-27 8:46 ` David Woodhouse
2003-10-27 8:52 ` Nikita Danilov
2003-10-27 9:06 ` David Woodhouse
2003-10-27 9:08 ` David Woodhouse
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=20031023135850.GF643@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=eric@sandall.us \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzachar@cs.bgu.ac.il \
/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