Hi,
On Fri, 2006-06-09 at 11:47 -0400, Jeff Garzik wrote:
> think about The Experience: Suddenly users that could use 2.4.x and
> 2.6.x are locked into 2.6.18+, by the simple and common act of writing
> to a file.
No.
The default is --- user writes to file on 2.6.18+, goes back to 2.4, and
everything still keeps on working just fine.
Or, user says "I *specifically* request this feature that I *know* is
not compatible with older kernels", and then they get just that.
Extents are not going to be on by default. Please, we've got more sense
than that!
Just like the developer who says "I *specifically* code for this fancy
new vmsplice syscall" gets exactly the same.
--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]
