Hi,
On Fri, 2006-06-09 at 11:56 -0400, Jeff Garzik wrote:
> Think about how this will be deployed in production, long term.
>
> If extents are not made default at some point, then no one will use the
> feature, and it should not be merged.
Features such as ACLs and SELinux are still not on by default and are
most *definitely* used. This is a bogus argument.
> And when extents are default, you have this blizzard-of-feature-flags
> stealth upgrade event occur _sometime_ after they boot into the new fs
> for the first time.
No. I don't see it ever being forced on in the kernel by default, so
there will be no such "stealth upgrades".
Rather, if it is "made default", that will be done by setting the flag
by default on newly-created filesystems in mke2fs. We won't be playing
magic on existing filesystems.
And to avoid confusion, I am *entirely* open to the idea of making it
only ever default to on in mke2fs at some point in the future where we
batch a set of incompat features with the "ext4" label, so that "mke2fs
-O ext4", or "mke4fs", would set it. That has already been proposed on
ext2-devel; we're nowhere near the stage of making that default yet.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
