Well, I see nobody wants to jump on this
From additional searches, it looks like the answer is either "42" or "dr. dr. it hurts when I do this ... then don't do that". Below are a number of links I found that discuss this problem and it seems there is no "one size fits all" solution for the VFAT filename and iochar set issue. Anyone interested in reading up on this, check on the links below (note that this is also documented somewhat in the vfat.txt from the kernel docs).
Hopefully this will save someone else some search time - even if there is no clear answer !!
Some interesting discussions on this issue:
Debian bug report discussing this issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443514
https://launchpad.net/ubuntu/+bug/62321
This one discusses the issue in the "How to Mount FatFileSystems"
http://www.nslu2-linux.org/wiki/HowT...FATFileSystems
This one concludes that unless you are using funny punctuation/chars
in the file names, it is not needed:
http://www.linux.net.nz/pipermail/nz...st/005606.html
This one thinks it is a bug to have that as a default:
http://sidux.com/PNphpBB2-viewtopic-t-4787.html
This one discusses the vfat and conversion and concludes that the
iocharset does NOT make sense and does not work as often expected:
http://lkml.org/lkml/2006/7/13/63
See this link for an interesting discussion on why there is no
correct answer ?
http://linux.derkeiler.com/Mailing-L...4-06/4755.html
This one talks about which charset to use (or not use) and points to
the vfat.txt documentation.
http://cateee.net/lkddb/web-lkddb/FA...IOCHARSET.html
This one discusses this exact issue and points to the vfat.txt and kernel documentation as well as discussing the "shortname" option.
http://ubuntuforums.org/showthread.php?t=137159
mikey



Adv Reply


Bookmarks