http://bugzilla.novell.com/show_bug.cgi?id=523352 User jeffm@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=523352#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |RESOLVED CC| |jeffm@novell.com Resolution| |WORKSFORME --- Comment #1 from Jeff Mahoney 2009-09-02 13:22:03 MDT --- This isn't a bug or a problem, it's the default behavior of the vfat file system as documented in the mount(8) man page: Mount options for vfat [...] 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. This mode is the default. 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. So, given your examples: 901.ROM -> 901.rom (all upper case -> gets displayed in lower case) aaa.ROM -> aaa.ROM (mixed case, stored as a long name) 90a.ROM -> 90a.ROM (mixed case, stored as a long name) +.ROM -> +.ROM (+ isn't allowed in a regular fat file name, so it necessitates a long name) .. the behavior is consistent with shortname=mixed. If you mount with -oshortname=mixed, then you'll end up with the results you're expecting. Closing as WORKSFORME. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.