On 8 April 2013 17:37, Theodore Ts'o <tytso@xxxxxxx> wrote: > There shouldn't be any crap; just a an error message indicating that > "the file system has features which this implementation doesn't > understand". At least, if the implementation was competently > coded.... (ext2/3/4 has feature bitmasks that make it very clear what > features are required so that an implementation can mount the file > system read/write or read/only). Right, the design side of it is fine. But then you end up with people making filesystems which aren't necessarily backwards compatible (and aren't aware of this), then try to share with other extX implementations; or boot an older Linux kernel (eg plugging an ext3 device on a newer box to an older box.) Now, ext3 is a bit more mature nowdays so people aren't _always_ hitting this corner case. But I do recall earlier on when things were moving forward quite quickly, people would create drives on Linux machine X that couldn't be read or written to on Linux machine Y. I'm not knocking extX here; I'm just pointing out that exposing things as a set of capability flags doesn't magically fix interoperability. It just stops you from scribbling crap where it shouldn't be. Adrian -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
