From: Adrian Bunk <bunk@stusta.de>
To: Theodore Tso <tytso@mit.edu>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Proposal and plan for ext2/3 future development work
Date: Sat, 1 Jul 2006 11:42:06 +0200 [thread overview]
Message-ID: <20060701094206.GA17588@stusta.de> (raw)
In-Reply-To: <20060630151432.GA21675@thunk.org>
On Fri, Jun 30, 2006 at 11:14:32AM -0400, Theodore Tso wrote:
> On Fri, Jun 30, 2006 at 12:39:48PM +0200, Andi Kleen wrote:
> > "Theodore Ts'o" <tytso@mit.edu> writes:
> > >
> > > 1) The creation of a new filesystem codebase in the 2.6 kernel tree in
> > > /usr/src/linux/fs/ext4 that will initially register itself as the
> > > "ext3dev"
> >
> > Why not call it ext4 from the beginning too? Calling the directory
> > differently from the file system can only cause confusion.
> >
> > I assume if it's marked very experimental people who value their data
> > will avoid it for the time being.
>
> There were a lot of people who were concerned that simply marking it
> CONFIG_EXPERIMENTAL might not be enough for to make it very clear that
> the filesystem format is still changing. In order to address this
> concern, we want /etc/fstab to make it abundantly clear that the
> filesystem format itself is not necessarily stable, and that new
> features are being added that might not be supported on older
> kernels.
>...
What about a dependency on CONFIG_BROKEN?
This will require everyone who wants to use it to manually edit the
Kconfig file for removing the dependency - which sounds like a good
idea.
> - Ted
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-07-01 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 23:55 Proposal and plan for ext2/3 future development work Theodore Ts'o
2006-06-30 1:14 ` Jeff Garzik
2006-06-30 1:59 ` Joel Becker
2006-06-30 17:13 ` Badari Pulavarty
2006-06-30 18:24 ` Joel Becker
2006-06-30 19:17 ` Steve Lord
2006-06-30 19:29 ` Badari Pulavarty
2006-06-30 10:39 ` Andi Kleen
2006-06-30 15:14 ` Theodore Tso
2006-07-01 9:42 ` Adrian Bunk [this message]
2006-07-01 10:29 ` Theodore Tso
2006-06-30 11:09 ` Patrick McFarland
2006-06-30 23:44 ` Mingming Cao
2006-07-24 13:04 ` Guillaume Chazarain
2006-07-24 18:11 ` Jeff Garzik
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=20060701094206.GA17588@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.