From: Brian Beattie <beattie@beattie-home.net>
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: 21 Oct 2003 10:29:51 -0400 [thread overview]
Message-ID: <1066746593.1294.0.camel@kokopelli> (raw)
In-Reply-To: <Pine.LNX.4.44_heb2.09.0310211406170.8365-100000@nexus.cs.bgu.ac.il>
On Tue, 2003-10-21 at 08:07, Nir Tzachar wrote:
> >
> > 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.
what does "self stabilizing" mean in this context?
> bye
bye bye
--
Brian Beattie | Experienced kernel hacker/embedded systems
beattie@beattie-home.net | programmer, direct or contract, short or
www.beattie-home.net | long term, available immediately.
"Honor isn't about making the right choices.
It's about dealing with the consequences." -- Midori Koto
next prev parent reply other threads:[~2003-10-21 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.44.0310070757400.4688-100000@sundance.cse.ucsc.edu>
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 [this message]
2003-10-23 13:58 ` Pavel Machek
2003-10-24 9:28 ` Nir Tzachar
2003-10-23 17:46 ` Daniel Egger
2003-10-23 18:47 ` Eric Sandall
2003-10-23 23:15 ` Daniel Egger
2003-10-24 15:45 ` srfs - a new file system.--OT Gadgeteer
2003-10-24 9:26 ` srfs - a new file system Nir Tzachar
2003-10-22 4:57 ` Erik Andersen
2003-10-22 10:16 ` Nir Tzachar
2003-10-22 10:21 ` Nir Tzachar
2003-10-22 16:05 ` Valdis.Kletnieks
2003-10-22 19:38 ` Erik Andersen
2003-10-23 5:20 ` Miles Bader
2003-10-23 5:37 ` Valdis.Kletnieks
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=1066746593.1294.0.camel@kokopelli \
--to=beattie@beattie-home.net \
--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