linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@osdl.org, Theodore Tso <tytso@mit.edu>,
	ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Mingming Cao <cmm@us.ibm.com>,
	linux-fsdevel@vger.kernel.org,
	Erik Mouw <erik@harddisk-recovery.com>
Subject: Re: [PATCH 2/5] Register ext3dev filesystem
Date: Thu, 10 Aug 2006 15:08:43 -0500	[thread overview]
Message-ID: <1155240524.12082.14.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <44DB8EBE.6060003@garzik.org>

On Thu, 2006-08-10 at 15:53 -0400, Jeff Garzik wrote:
> Theodore Tso wrote:
> > On Thu, Aug 10, 2006 at 11:20:22AM +0200, Erik Mouw wrote:
> >> On Wed, Aug 09, 2006 at 06:17:22PM -0700, Mingming Cao wrote:
> >>> Register ext4 filesystem as ext3dev filesystem in kernel.
> >> Why confuse users with the name "ext3dev"? If a filesystem lives in
> >> fs/blah/, it's registered as "blah" and can be mounted with "-t blah".
> >> Just register the filesystem as "ext4" and mark it "EXPERIMENTAL" in
> >> Kconfig.
> > 
> > We had this discussion on LKML.  There were those who were concerned
> > that it would not be enough just to mark it be EXPERIMENTAL.
> 
> I _want_ to agree with Erik, but I must agree:  CONFIG_EXPERIMENTAL is 
> pretty worthless in practice :(  It's not maintained rigorously, and 
> distros _always_ enable it, because otherwise they would often omit key 
> drivers that people actively use.
> 
> So, while my own personal preference would be to follow Erik's 
> suggestion...  thinking realistically, an fstype change from "ext3dev" 
> to "ext4" is a far more obvious-to-users method of creating a 
> devel/production line of demarcation.

IF it's decided to register the file system as ext3dev (Would ext4dev
make more sense?), I would prefer the config options and code continues
to simply use ext4.
-- 
David Kleikamp
IBM Linux Technology Center


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-08-10 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:17 [PATCH 2/5] Register ext3dev filesystem Mingming Cao
2006-08-10  9:20 ` [Ext2-devel] " Erik Mouw
2006-08-10 17:33   ` Randy.Dunlap
2006-08-10 17:59   ` Theodore Tso
2006-08-10 19:53     ` Jeff Garzik
2006-08-10 20:08       ` Dave Kleikamp [this message]
2006-08-10 20:22         ` John Stoffel
2006-08-10 20:24         ` Jeff Garzik
2006-08-10 21:05           ` Mingming Cao
2006-08-10 20:23       ` Erik Mouw
2006-08-10 20:27         ` Jeff Garzik
2006-08-15 15:25 ` Pavel Machek
2006-11-20 10:14 ` Sander

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=1155240524.12082.14.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=erik@harddisk-recovery.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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).