Date: Thu, 20 Feb 1997 09:04:39 +0000
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: [opendos-developer] Potential serious FS problem
To: opendos-developer AT mail DOT tacoma DOT net
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <330C13A7.3013@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <199702191424 DOT JAA17066 AT keeper DOT albany DOT net>
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

Jim Lefavour wrote:
> 
> I just realized - whatever FS we use, we have to be careful.  Most
> DOS programs expect filenames to be uppercase, and many are written
> so that filenames are all treated that way - if we introduce a
> case-sensitive fs, we may BREAK many programs, however, as files may
> be installed  in varied case (some lower, some upper, etc. )
> 
> How can this problem be avoided?  Should we disable case sensitivity
> in our fs?  We are trying to maintain compatibility with dos
> software, after all... :)
> 

That's what rename (move, whatever) is for.

However, there could be an api call to enable/disable case sensitivity,
or it could be an install/compile option.

Anyway, any non dos file system itself is not compatable with many dos
programs, so why worry?

Bill
-- 
Leave others their otherness.