Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!uunet!shelby!agate!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: comp.unix.sysv386
Subject: Re: 14 character limitation in filenames
Message-ID: <1991Feb7.041610.5167@NCoast.ORG>
Date: 7 Feb 91 04:16:10 GMT
References: <20711@hydra.gatech.EDU> <1991Feb1.003532.15719@NCoast.ORG> <.H599ZF@xds13.ferranti.com>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR)
Followup-To: comp.unix.sysv386
Organization: North Coast Public Access Un*x (ncoast)
Lines: 22

As quoted from <.H599ZF@xds13.ferranti.com> by peter@ficc.ferranti.com (Peter da Silva):
+---------------
| In article <1991Feb1.003532.15719@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
| > "Silliness"?  I still fail to understand why everyone wants to be able to
| > create files with humongous names --- I don't enjoy typing 14 character file
| 
| I find 14 a little limiting on occasion, but I've never run out of space
| in the 30-character file names on AmigaOS. Since just doubling the size
| of a directory entry would give you 30 character filenames, why bother with
| complicated stuff like the BSD system?
+---------------

We see eye to eye on this.  255 character file names are ridiculous; if my
file name gets *that* long, as far as I'm concerned the file name is a file in
itself.

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY