Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!att!rutgers!rochester!kodak!ispd-newsserver!ism.isc.com!ico!rcd
From: rcd@ico.isc.com (Dick Dunn)
Newsgroups: comp.unix.sysv386
Subject: Re: 14 character limitation in filenames
Summary: not a win
Message-ID: <1991Feb17.042603.6863@ico.isc.com>
Date: 17 Feb 91 04:26:03 GMT
References: <1991Feb11.072316.193@ico.isc.com> <27B7F558.32E7@tct.uucp> <1991Feb16.163535.13418@ariel.unm.edu>
Organization: Interactive Systems Corporation, Boulder, CO
Lines: 13

dmckeon@hydra.unm.edu (Denis McKeon) writes:
> Since AT&T's 14 isn't enough, and BSD's to null or 255 is slower to
> read (or is it?), how about encoding the current max filename length
> following the . or .. entries (conventionally the first two dir entries).
[then goes on to describe a method]

Problem is that this isn't compatible with either of the existing, common
approaches.  If you're concerned about seriously backward compatibility,
you probably want to stay with the AT&T approach.  The BSD method doesn't
cost much in efficiency, so if you want long names it's the way to go.
-- 
Dick Dunn     rcd@ico.isc.com -or- ico!rcd       Boulder, CO   (303)449-2870
   ...But is it art?