Messages in this thread | | | Date | Sun, 6 Aug 2000 20:36:20 +0200 (CEST) | From | Urban Widmark <> | Subject | Re: VFAT fs bug report |
| |
On Sun, 6 Aug 2000, Denis Vlasenko wrote:
> Since I am new to Linux and Unix in general, I will not try > to write patches. I'll just describe what I have seen. > > I use RedHat Linux, my kernel version is 2.2.5.
Try 2.2.16 or the latest 2.2.17-pre it may work better for you. If that fails try the latest 2.4.0-test version.
And if that fails someone has sent a patch for vfat in 2.4.0-test that I haven't had time to test but that I can forward to you if the "plain" version does not work. (but I think that was about it not working properly for 16 bit codepages, for cyrillic I assume you are using cp866<->koi8-r and those are both 8bit so it shouldn't matter).
> Some observation with disk editor showed that Cyrillic shortnames > wasn't in upper case. I presume you aren't willing to
Hmm. 2.2 vfat does not try to do any case conversion but 2.4 does. Maybe you should try the 2.4 version first.
> We need more general (Unicode-aware?) strnicmp() ant toupper() in
Probably. I believe a unicode version of toupper()/tolower() would help (at least) vfat and ncpfs support "long/short" name conversions. smbfs has (had, depending on which version you look at) options to convert into upper/lower that only works for us-ascii ...
/Urban
- 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/
| |