Xref: utzoo news.software.b:3316 comp.unix.xenix:8199
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: news.software.b,comp.unix.xenix
Subject: Re: B News' Directory permission problem in /tmp
Message-ID: <1989Oct24.214243.418@virtech.uucp>
Date: 24 Oct 89 21:42:43 GMT
References: <8910220254.AA05389@decwrl.dec.com> <37127@looking.on.ca> <1989Oct23.152647.27702@utzoo.uucp>
Organization: Virtual Technologies Inc.
Lines: 23

In article <1989Oct23.152647.27702@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
> 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.

This is not a "feature" of standard System V Rel 3.2 as released by Interactive,
and Bell Tech.  When the poster mentioned it in this group I assumed it was
a "feature" of SCO UNIX 3.2.  So don't blame AT&T nor POSIX, just blame SCO.





-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+