Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Guest Moderator, John B. Chambers)
Newsgroups: mod.std.unix
Subject: Re: Case sensitive file names
Message-ID: <6412@ut-sally.UUCP>
Date: Fri, 21-Nov-86 16:11:54 EST
Article-I.D.: ut-sally.6412
Posted: Fri Nov 21 16:11:54 1986
Date-Received: Fri, 21-Nov-86 21:49:42 EST
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 29
Approved: jbc@sally.utexas.edu

References:


>From bu-cs!bzs@harvard.UUCP Wed Nov 19 07:19:28 1986
Date: Tue, 18 Nov 86 21:35:03 EST
From: bu-cs!bu-cs.BU.EDU!bzs@harvard.UUCP (Barry Shein)


The problem with a file system where you cannot have ReadMe and
README is that you are throwing away possibilities. This also
means that I cannot have tmp01234A, tmp01234B, ... , tmp01234a, ...

I fear that although many people have applications that are small and
have small requirements they should not place restrictions on those
with large requirements, use your imagination, consider MasterCard's
data base for a moment or some of the multi-library catalog systems
people are building, they may need (and have machines that have no
trouble with) many thousands of files who's names may serve as primary
keys (why not, it's one way to guarantee write-through on update...)

Next they'll be telling us we should only allow 16-bit ints because
any number larger than 16-bits is hard to type in and error prone
anyhow.

I still suggest the use of 'stty lcase' if that's what you want
(alias run 'stty -lcase; \!* ; stty lcase' :-)

	-Barry Shein, Boston University



Volume-Number: Volume 8, Number 58