Message-Id:	<199705020030.UAA19370@keeper.albany.net>
Comments:	Authenticated sender is <jamesl AT mail DOT albany DOT net>
From:	"Jim Lefavour" <jamesl AT mail DOT albany DOT net>
Organization:	No Way Out
To:	Ben Schollnick <bscholl AT eznet DOT net>, opendos AT delorie DOT com
Date:	Thu, 1 May 1997 08:32:21 -0500
MIME-Version:	1.0
Subject:	Re: A few FS notions
Reply-to:	jamesl AT albany DOT net
References:	<Pine DOT OSF DOT 3 DOT 95 DOT 970501094820 DOT 20452B-100000 AT unicorn DOT it DOT wsu DOT edu>
In-reply-to:	<Pine.LNX.3.95.970501194036.29686C-100000@shell1.eznet.net>

> 
> On Thu, 1 May 1997, Evan Dickinson wrote:
> 
> > On Wed, 30 Apr 1997, Benjamin D Chambers 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.
> 
> 	I believe the design of HPFS is better in relationship for Case
> support.
> 
> 	HPFS is Case-insensitive for *RETRIEVAL*, but stores the "case"
> you type in for the filename...
> 
> 	In otherwords, when you save the file, your also saving the
> filename's case:
> 
> 	IE:
> 
> 		"This is a Test"
> 
> 	would be stored just like that....But any filecomparision's are
> case *INSENSITIVE*.
> 
> 	"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).
> 
> 			Benjamin
In that matter, you could use ext2 (which is definately freely 
available) and create the search function so that it is 
case-insensitive, either by default or by command line switch...

Jim

jamesl AT albany DOT net http://www.albany.net/~jamesl/
Please also visit: 
http://www.geocities.com/SiliconValley/Pines/9244/

- Raw text -