VFAT not endian safe?
Michael R. Zucca
mrz5149 at acm.org
Tue Oct 2 11:40:48 EST 2001
I'm trying to share a file system between macos and linux that is capable
of long filenames. Since there's no HFS+ support yet, I decided to go with
Unfortunately, it seems when I write files on the linux side, all the
filenames appear as "" and the files will not open under MacOS. When I
produce files under macos, linux lists the filenames as a series of
This was all rather confusing until I mounted the VFAT partition with an
option to show unknown unicode characters as two byte hex sequences. This
revealed that linux was reading/writing the name bytes in the wrong endian
A closer look at the VFAT code seems to indicate that unicode names are
handled in the native endian order by mistake instead of being converted to
little endian. Looking around the other FS code, I wonder if this is a
I'm using at benh 2.4 from about a month ago. Does anybody know if there is
work underway to fix this problem or should I go ahead and start plugging
away at it?
Michael Zucca - mrz5149 at acm.org - http://www.mdc.net/~mrz5149/
"I will choose a path that's clear. I will choose Freewill. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev