Hi Tony look below for comments/answers
-----Oprindelig meddelelse-----
Fra: Tony Nugent <[EMAIL PROTECTED]>
Til: Søren Lambæk <[EMAIL PROTECTED]>
Cc: Linux Config Email List <[EMAIL PROTECTED]>
Dato: 2. maj 2000 04:26
Emne: Re: Sv: Long filenames on vfat not working?
>Now you didn't say that you were referring to a "fat32 cdrom
>partition". No, this isn't right... the two (fat32 and data cdroms)
>are very different beasts.
I am refering to BOTH:
On my secondary HD partition 1 ( hdb1 ) i have a fat32 long name filesystem.
in the CD-rom drive i have a CDROM with long filenames.
They both act the same regarding the long filenames being truncated to 8.3 format
without the "~1" thing.
>> The trouble here is that i am using the "vfat" option when mounting
>> the "fat32" drive. If I was mounting as msdos shouldn't i see msdos
>> "short" filenames ( "abcdef~1.txt" )? What i get is filenames like
>> "abcdefgh.txt" instead of "abcdefghijklmnop.txt"
>
>This looks like you haven't got the kernel nls_cp* codepage module
>extensions (eg, nls-cp437.o nls_iso8859-1.o etc) available. (I could
>be wrong).
Now this might look interesting!
I should be able to see those with "lsmod" right?
>
>> When mounting the CD I use the iso9660 option and get the same
>> filename tweak as described before.
>
>What as before? The long names (ie, working), or the short 8.3 names
>(not working)?
Well both ;-) actually the CD contains long filenames but the dont show
same symptoms as with the hdb1 fat32 partition.
>And IIRC vfat uses msdos (fat), and both modules should be
>automagically loaded by the kerneld daemon (kernel 2.0.x) or by the
>kernel itself (kernel 2.2.x).
with "lsmod" I see both "vfat" and "fat".
I am running red hat 6.0 with kernel 2.2.x from the redhat
media i havent done any kernel tweaking yet. ;-)
>The filesystem on a CDROM is quite different... it has a iso9660
>format filesystem -- NOT vfat.
>
>The standards for iso9660 specify 8.3 filenames and other restrictions
>such as 8-deep directory levels and so on.
>
>In order to overcome these limitations, some extensions were added:
>
>- RockRidge -- allows unix filesystem extensions.
>- Joliet -- allows vfat (fat16/32) long file name extensions
>
>If you mount a CDROM, it is (almost) always an iso9660 filesystem.
>The kernel - if it has the right drivers compiled into it and/or the
>right modules available for loading - will (should) automatically
>detect the presence of either or both RockRidge and Joliet extensions
>and act accordingly.
>
>In short, for reading CDROMs you need to have the CDROM driver
>available (usually compiled into the kernel by default), then the
>kernel will load the appropriate nls_* codepage module
>(nls_iso8859-1).
I didn't know to setup the cdrom when installing, so i do "insmod mcd mcd=0x340,5"
to load the cd driver.
I will check with "lsmod" if the "nls_iso8859-1" module get's loaded when mounting the
cd.
>
>For reading/writing to vfat filesystems on either hard drive or
>floppy, the vfat, fat and nls_cp437 modules all need to be loaded.
>And they should be loaded automagically by the kernel.
Again I will check for the presence of "nls_cp437" with "lsmod".
Thanks a lot for helping out.
I will let you know what i find out regarding those nls_* modules.
To me it sounds like this could be where the trouble are.
regards
Søren Lambæk
