NetBSD Problem Report #21121

Received: (qmail 3999 invoked by uid 605); 13 Apr 2003 11:02:20 -0000
Message-Id: <200304131102.h3DB2GgX002613@night-porter.duskware.de>
Date: Sun, 13 Apr 2003 13:02:16 +0200 (MEST)
From: Martin Husemann <martin@duskware.de>
Sender: gnats-bugs-owner@netbsd.org
Reply-To: martin@duskware.de
To: gnats-bugs@gnats.netbsd.org
Subject: msdosfs displays 8.3 names all upercase
X-Send-Pr-Version: 3.95

>Number:         21121
>Category:       kern
>Synopsis:       msdosfs displays 8.3 names all upercase
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 13 11:03:00 +0000 2003
>Closed-Date:    Wed May 23 06:12:41 +0000 2018
>Last-Modified:  Wed May 23 06:12:41 +0000 2018
>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:

From: Olaf Seibert <rhialto@polderland.nl>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/21121: msdosfs displays 8.3 names all upercase
Date: Wed, 16 Apr 2003 01:16:18 +0200

 On Sun 13 Apr 2003 at 13:02:16 +0200, Martin Husemann wrote:
 > 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.

 As far as I know (but it has been a long time since I last looked at it)
 there is a bit or other indicator somewhere that a name is supposed to
 be all lowercase. Of course this does not seem to be supported by all
 versions of MS-DoS.

 > >How-To-Repeat:
 > Mount a msdosfs partition and compare the file names to what the windows
 > explorer shows for the same partition.

 It has a definite tendency to display the file "FILENAME.EXT" as
 "Filename.ext", just because it is all-uppercase and fits in 8.3, even
 if you specifically named the file in all uppercase. Don't take that
 exploder thing too seriously.

 -Olaf.
 -- 
 ___ Olaf 'Rhialto' Seibert - rhialto@       -- Woe betide the one who feels
 \X/ polderland.nl  -- remorse without sin - Tom Poes, "Het boze oog", 4444.
Responsible-Changed-From-To: kern-bug-people->jdolecek 
Responsible-Changed-By: jdolecek 
Responsible-Changed-When: Sun Jun 29 21:42:00 UTC 2003 
Responsible-Changed-Why:  
I'd look at this eventually. 
Responsible-Changed-From-To: jdolecek->kern-bug-people
Responsible-Changed-By: wiz@NetBSD.org
Responsible-Changed-When: Sun, 15 Apr 2012 21:41:26 +0000
Responsible-Changed-Why:
Back to role account, jdolecek left


State-Changed-From-To: open->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Wed, 23 May 2018 06:12:41 +0000
State-Changed-Why:
The -l option of mount_msdos fixes this.


>Unformatted:

Home	PR Database Search