Xref: utzoo news.software.b:3318 comp.unix.xenix:8209
Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!dogie.macc.wisc.edu!uwvax!umn-d-ub!umn-cs!nic.MR.NET!hal!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: news.software.b,comp.unix.xenix
Subject: Re: B News' Directory permission problem in /tmp
Message-ID: <1989Oct25.015422.18947@NCoast.ORG>
Date: 25 Oct 89 01:54:22 GMT
References: <8910220254.AA05389@decwrl.dec.com> <37127@looking.on.ca> <1989Oct23.152647.27702@utzoo.uucp>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: news.software.b
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 22

As quoted from <1989Oct23.152647.27702@utzoo.uucp> by henry@utzoo.uucp (Henry Spencer):
+---------------
| In article <37127@looking.on.ca> brad@looking.on.ca (Brad Templeton) writes:
| >Unix 3.2 is POSIX compliant.  That means that if you pass a filename longer
| >than 14 chars, it is not truncated, the open fails.
| 
| It should be noted that "POSIX compliant" does not suffice as an explanation
| for this particular behavior.  This behavior is *optional* in POSIX; the
| alternative is the way Unix historically did it, i.e. just ignore the extra
| characters.  That is, blame AT&T, not POSIX, for this decision.
+---------------

Henry, this was SCO's choice.  I don't recall 386/ix having this particular
wart.

++Brandon
-- 
Brandon S. Allbery:  allbery@NCoast.ORG, BALLBERY (MCI Mail), ALLBERY (Delphi)
uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu bsa@telotech.uucp
*(comp.sources.misc mail to comp-sources-misc[-request]@backbone.site, please)*
*Third party vote-collection service: send mail to allbery@uunet.uu.net (ONLY)*
>>>	 Shall we try for comp.protocols.tcp-ip.eniac next, Richard?	    <<<