Date: Tue, 24 Feb 1998 14:01:43 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG, dima@dnttm.ru Subject: Re: cvs commit: src/sys/msdosfs direntry.h msdosfs_conv.c msdosfs_lookup.c msdosfs_vfsops.c msdosfs_vnops.c msdosfsmount.h Message-ID: <19980224140143.53881@nagual.pp.ru> In-Reply-To: <199802241037.NAA02154@tejblum.dnttm.rssi.ru>; from dima@tejblum.dnttm.rssi.ru on Tue, Feb 24, 1998 at 01:37:41PM %2B0300 References: <199802231644.IAA29299@freefall.freebsd.org> <199802241037.NAA02154@tejblum.dnttm.rssi.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 24, 1998 at 01:37:41PM +0300, Dmitrij Tejblum wrote: > "Andrey A. Chernov" wrote: > > Always create DOS name in uppercase > > Always view DOS name in lowercase > > This imply that noone can see names like README.TXT on msdos filesystem. When > someone creates a file with such name, it becomes 'readme.txt'. But if someone > creates file 'README.TEXT', the name will remain same. This is odd, i believe. The reason is simple: non-uppercase names not understanded by majority of programs and filesystem checks under DOS. Making non-uppercase name in DOS breaks DOS! > A workaround could be to always write long file name. I.e. never return 1 in > unix2dosfn. It is still not compatible with Windows 95, of course, but Windows > 95 is not fully compatible with itself in this issue. This workaround is already active since long file name preserving case _always_ written if you have Win95 file system. I.e. two names written at once: 1) DOS uppercased name. 2) Win95 name preserving case (if you not turn off Win95 support) In msdosfs you'll see Win95 name first, if it present. -- Andrey A. Chernov <ache@nietzsche.net> http://www.nagual.pp.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980224140143.53881>