Date: Sun, 4 May 1997 23:04:34 -0400 (EDT)
From: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
Reply-To: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
To: Ben Schollnick <bscholl AT eznet DOT net>
cc: opendos AT delorie DOT com
Subject: Re: A few FS notions
In-Reply-To: <Pine.LNX.3.95.970501194036.29686C-100000@shell1.eznet.net>
Message-ID: <Pine.LNX.3.95.970504230140.9064C-100000@capslock.com>
Organization: Total disorganization.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Thu, 1 May 1997, Ben Schollnick wrote:

> > [snip]
> > > What I would like to request is:
> > > - Node tree (versus FAT)
> > > - Case sensitivity
> > 
> > Not being much of an UNIX user myself, I have to ask:  Why is a case
> > sensitive filesystem an advantage?  I get frustrated when *.zip won't
> > match SOMETHING.ZIP; I'm sure lots of other DOS users would, too.
[SNIP]
> 	"This is a test" == "THIS IS A TEST" == "this is a test" 
> 
> 	Are all the same file.  Even when you save a file, it would all
> work the same... (In otherwords, it still checks for the file first, and
> only saves "one" case version).

I don't like this scheme myself, it's the same as W95's.  When
you unzip a UNIX file into the filesystem that has 2 files with
the same name but differing case they overwrite eachother.  I've
had this happen millions of times in DOS with make files.  There
typically is a file "makefile" and another "Makefile".  Usually
the "Makefile" is a UNIX makefile, and the other one is DOS or
some other OS, unfortunately the one that is kept is the last one
in the archive which varies...

Just my $10

Mike A. Harris        |             http://blackwidow.saultc.on.ca/~mharris
Computer Consultant   |                  Coming soon: dynamic-IP-freedom...
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
Email: mharris at blackwidow.saultc.on.ca  <-- Spam proof address

LINUX: Lost your video after running a game or DOSemu, email me for fix.