>Number:         21121
>Category:       kern
>Synopsis:       msdosfs displays 8.3 names all upercase
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 13 04:03:00 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Martin Husemann
>Release:        NetBSD 1.6R
>Organization:
>Environment:
System: NetBSD night-porter.duskware.de 1.6R NetBSD 1.6R (PORTER) #3: Sat Apr 12 20:26:22 CEST 2003 martin@insomnia.duskware.de:/mnt/src/sys/arch/i386/compile/PORTER i386
Architecture: i386
Machine: i386
>Description:

The msdos filesystem has two ways to store file names. The optional (long) names
are case-preserving. If a directory entry does not have a longname extension,
it's 8.3 file name is displayed in all uppercase.

This behaviour matches old DOS behaviour.

It is unusual, strange, and complicated to deal with (ever used filename 
completition on a msdos partition?) - and it is different from what windows
shows (in the explorer) nowadays. Windows itself is inconsistent in its
behaviour between command prompt and explorer - but I dare to say most people
would expect the names to be lowercase.

It would be good if the display of 8.3-only file names could be either all-
lowercase (default) or all-uppercase (as it is now), depending on a mount
option.

I have to admit that the notion of uppercase/lowercase is a bit more complex
in the non-ASCII world, and AFAICT we still need a good solution for msdosfs
vs. non-ASCII/non-ISO-8859-1 locales anyway (for the always case-insensitive
file name matching).

>How-To-Repeat:
Mount a msdosfs partition and compare the file names to what the windows
explorer shows for the same partition.
>Fix:
n/a
>Release-Note:
>Audit-Trail:
>Unformatted: