> One of the reasons why FAT is badly b0rken is the damn 'text mode'. I.e.
> automagical translation of \r\n to \n and back. It is *wrong*. Not to
> mention the fact that it screws up on binaries and relies on the list
> of known extensions (barf) to do its magic. Or that renaming such files
> changes their visible contents. Worse yet, open, rename, read, close,
> open, read again and there you go - second read may return something
> pretty different. IMO such thing has no place in the kernel...
It's quite horrible.. the only reason I use it is to access some
data from an old DOS partition once in a while. I can live without
fat support (or use an older kernel to cp the data then nuke the
partition) I was just curious why it would be broken deliberately.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/