Messages in this thread | | | From | Robin Rosenberg <> | Subject | Re: JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) | Date | Thu, 12 Feb 2004 16:55:39 +0100 |
| |
On Thursday 12 February 2004 09.54, you wrote: > Andy Isaacson wrote: > > Why on earth is JFS worried about the filename, anyways? Why has it > > *ever* had *any* behavior other than "string of bytes, delimited with /, > > terminated with \0" ? > > Perhaps for the same reason that these other in-tree filesystems are > sensitive to the character encoding: > > Joliet (ISO-9660 extension), FAT/VFAT, NTFS, BeFS, SMBFS, CIFS. > > Those filesystems will also fail, or give unexpected behaviour (such > as bytes being changed to '?'), if you pass them names which are not > in the appropriate encoding.
Definitely a good reason. It seem many assume file names are a local thing, but this is not so. Now consider the case with an external firewire disk or memory stick created on a machine with iso-8859-1 as the system character set and e.g xfs as the file system. What happens when I hook it up to a new redhat installation that thinks file names are best stored as utf8? Most non-ascii file names aren't even legal in utf8.
-- robin
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |