Iain Buchanan wrote:
On Tue, 2006-02-07 at 17:33 -0800, Ryan Tandy wrote:
Iain Buchanan wrote:
[snip]
I left them as is, and compiled nsl_utf8 as a module (so I don't have to
restart). When I load the module and plug in the
drive, /var/log/messages now shows:
Feb 7 22:07:18 orpheus FAT: utf8 is not a recommended IO charset for
FAT filesystems, filesystem will be case sensitive!
but the drive still mounts...
This is a warning, not an error. You can use Unicode on vfat
filesystems, but it's not recommended as vfat is not usually used in a
case sensitive context.
So what do I do if I don't want it to be case sensitive? If I don't
load nls_utf8, then I can't access the drive... But to access the drive
I need nls_utf8...
hmmm....
From man mount:
Mount options for fat
(Note: fat is not a separate filesystem, but a common part of the
msdos, umsdos and vfat filesystems.)
<snip>
codepage=value
Sets the codepage for converting to shortname characters
on FAT and VFAT filesystems. By default,
codepage 437 is used.
<snip>
iocharset=value
Character set to use for converting between 8 bit
characters and 16 bit Unicode characters. The
default is iso8859-1. Long filenames are stored on disk
in Unicode format.
Try compiling the nls_iso8859-1 module, and mount the drive using that
iocharset. The man page notwithstanding, the default CP and iocharset
can both be changed in the kernel config.
If that doesn't work, then I've misunderstood the error/warning, and you
need to look at the 'utf8' option for vfat in man mount.
--
[email protected] mailing list
