Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!decvax!decwrl!jumbo!jg
From: jg@jumbo.UUCP
Newsgroups: comp.windows.x
Subject: Re: Long names in System V
Message-ID: <776@jumbo.dec.com>
Date: Sat, 4-Apr-87 15:38:10 EST
Article-I.D.: jumbo.776
Posted: Sat Apr  4 15:38:10 1987
Date-Received: Sun, 5-Apr-87 13:15:07 EST
References: <040187.111854.dan@ibm.com> <311@desint.UUCP>
Reply-To: jg@jumbo.UUCP (Jim Gettys)
Distribution: world
Organization: DEC Systems Research Center
Lines: 21

In article <311@desint.UUCP> geoff@desint.UUCP (Geoff Kuenning) writes:
>In article <040187.111854.dan@ibm.com> DAN@IBM.COM ("Walter E. Daniels Jr.") writes:
>Hear, hear!  Even better, how about if MIT admits that some of us are
>stuck with Neanderthal systems, and renames every file to be TWELVE
>characters or shorter?

This has been done in V11; all file names will be 12 characters or less
for systems in the beta and final release to cooperate with
RCS and SCCS.  Large amounts of effort have been going into making the
code as portable as possible, and not only to various variants of Unix.

>While we're at it, can we *please* get rid of the uppercase characters
>in file names?  This is a major pain with no gain.  

You are the first person to compain about this in recent memory.
I find it easier to parse names of files if there is some way to tell where
one word begins and ends.  This is particularly important once you have
abbreviated file names to live within 12 characters.  For example,
XChkMskEv.c I find easier to deal with than xchkmskev.c would be.

				Jim Gettys