From: Jeff Dike <jdike@addtoit.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Jeff Anderson-Lee <jonah@eecs.berkeley.edu>,
"'fsdevel'" <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Reiser4 Inclusion
Date: Mon, 17 Jul 2006 20:49:31 -0400 [thread overview]
Message-ID: <20060718004931.GB8092@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060717204804.GA18516@harddisk-recovery.com>
On Mon, Jul 17, 2006 at 10:48:04PM +0200, Erik Mouw wrote:
> On Mon, Jul 17, 2006 at 08:13:04AM -0700, Jeff Anderson-Lee wrote:
> > In the past I've wondered why so many experimental FS projects die this
> > death of obscurity in that they only work under FreeBSD or some ancient
> > version of Linux.? I'm beginning to see why that is so:? the Linux core
> > simply changes too fast for it to be a decent FS R&D environment!
>
> That hasn't been a problem for OCFS2 and FUSE (recently merged), and
> also doesn't seem to be a problem for GFS.
I'm been maintaining a couple (for now) out-of-tree filesystems for
UML, and have seen only minor updates needed over the course of 2.6.
Complaints about interface churn for filesystems (or anything else,
actually, since an architecture, such as UML, is exposed to nearly the
entire kernel) are imcomprehensible to me.
Jeff
next prev parent reply other threads:[~2006-07-18 0:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 3:02 Caleb Gray
2006-07-17 9:25 ` Arjan van de Ven
2006-07-17 11:48 ` Grzegorz Kulewski
2006-07-17 11:57 ` Alexander Gran
2006-07-17 14:06 ` Diego Calleja
2006-07-17 14:31 ` Grzegorz Kulewski
2006-07-17 15:51 ` Matthias Andree
2006-07-18 7:59 ` Jan Engelhardt
2006-07-18 20:47 ` Matthias Andree
2006-07-19 1:19 ` Joshua Hudson
2006-07-19 9:27 ` Tilman Schmidt
2006-07-19 11:00 ` Krzysztof Halasa
2006-07-19 11:03 ` Pekka Enberg
2006-07-19 15:32 ` Tilman Schmidt
2006-07-19 19:04 ` Valdis.Kletnieks
2006-07-19 19:12 ` Tilman Schmidt
2006-07-19 20:09 ` Valdis.Kletnieks
2006-07-19 22:36 ` Tilman Schmidt
2006-07-19 20:29 ` Jeff V. Merkey
2006-07-19 22:01 ` Matthias Andree
2006-07-19 22:34 ` Helge Hafting
2006-07-17 15:52 ` gmu 2k6
2006-07-17 15:57 ` Alexander Gran
2006-07-17 19:01 ` Horst von Brand
2006-07-17 15:13 ` Jeff Anderson-Lee
2006-07-17 15:56 ` Matthias Andree
2006-07-17 20:48 ` Erik Mouw
2006-07-18 0:49 ` Jeff Dike [this message]
2006-07-18 11:43 ` Christoph Hellwig
2006-07-17 9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10 ` Nix
2006-07-19 6:56 ` Reiser4 ACLs Marc Perkel
2006-07-19 15:03 ` Jan Engelhardt
2006-07-17 22:34 Reiser4 Inclusion linux
[not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt
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=20060718004931.GB8092@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=erik@harddisk-recovery.com \
--cc=jonah@eecs.berkeley.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome