Messages in this thread | | | Subject | Re: JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) | From | Dave Kleikamp <> | Date | Thu, 12 Feb 2004 07:28:05 -0600 |
| |
On Wed, 2004-02-11 at 18:45, 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" ?
The problem that was addressed in OS/2 was that one user using locale A would create some files using non-ascii characters. Then a user using locale B would access these files, but the characters in those names did not make sense in his locale. Storing the file names in unicode allowed the characters to always translate to the correct characters in the user's locale, when the charset allowed it. I'm not familiar enough with the European locales to give specific examples. It was never an issue in the U.S. :^)
The OS/2 kernel has locale information for each process, so this actually works very well there. I will admit that it was a mistake not to change the default behavior when we ported this to Linux.
> I read your response about OS/2, and maybe I'm just slow, but I don't > see what that has to do with anything. > > Does JFS on AIX have the same buggy behavior?
I know that JFS1 did not. I'm not sure about JFS2, since it was ported from the same OS/2 code base.
> What behavior was the code originally designed to implement, on OS/2? > Why was that behavior chosen rather than "filenames are a string of > bytes"?
I hope I explained that well enough above.
> Feel free to point to a "Design of the OS/2 JFS interface" document if > such exists and answers my question. :) > > -andy -- David Kleikamp IBM Linux Technology Center
- 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/
| |