folders not being named in caps

Tyir · 03-08-2004, 11:43 PM

I dont get this behavior, and its REALLY pissing me off!!!!

im in a mounted folder, it is fat32, which may be why, but it worked before

Code:

00:43:00-/mnt/bigfat:ls
Multimedia/                    slackware-9.1-install-d1.iso*
Windows\ Installation\ Files/  slackware-9.1-install-d2.iso*
00:43:00-/mnt/bigfat:mkdir WORK
00:43:11-/mnt/bigfat:ls
Multimedia/                    slackware-9.1-install-d1.iso*  work/
Windows\ Installation\ Files/  slackware-9.1-install-d2.iso*
00:43:13-/mnt/bigfat:

unix is case sensative, so this is important!
why is this keep happening??

Tinkster · 03-09-2004, 12:59 AM

Now if I knew what exactly keeps happening?

I can't see any erratic or faulty behaviour in
what you pasted? Except, of course, that you're
using FAT32 and have directories with Caps and
spaces in the name ...

Cheers,
Tink

usernamenumber · 03-09-2004, 10:38 AM

Unix is case sensitive, but the fat32 filesystem is not, so the case of the filename is not nescessarily stored. There are some mounting arguments that you can add to your fstab or whatever that may help you with this.

From the mount manpage:

Quote:

shortname=[lower|win95|winnt|mixed]

Defines the behaviour for creation and display of filenames
which fit into 8.3 characters. If a long name for a file exists,
it will always be preferred display. There are four modes:

lower Force the short name to lower case upon display; store a
long name when the short name is not all upper case.

win95 Force the short name to upper case upon display; store a
long name when the short name is not all upper case.

winnt Display the shortname as is; store a long name when the
short name is not all lower case or all upper case.

mixed Display the short name as is; store a long name when the
short name is not all upper case.

The default is "lower".