Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!ukma!usenet.ins.cwru.edu!ncoast!allbery From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) Newsgroups: comp.unix.sysv386 Subject: Re: SCO doesn't sell UNIX Message-ID: <1990Dec14.035940.28832@NCoast.ORG> Date: 14 Dec 90 03:59:40 GMT References: <1990Dec02.213409.17190@ka3ovk.irs.GOV> <1990Dec04.003651.13014@jadpc.cts.com> <1990Dec08.140730.9747@digibd.com> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) Followup-To: comp.unix.sysv386 Organization: North Coast Public Access *NIX, Cleveland, OH Lines: 30 As quoted from <1990Dec08.140730.9747@digibd.com> by rhealey@digibd.com (Rob Healey): +--------------- | In article <1990Dec04.003651.13014@jadpc.cts.com> jdeitch@jadpc.cts.com (Jim Deitch) writes: | >Or how about instead of silently truncating a file name > 14 | >characters, giving you a nice big fat error in the middle of a make or | >something until you clear a flag? Example: Try compiling cnews and | >create the subst file for spacefor. Blows up everytime! | > | That's POSIX conformance fault not SCO specifically. cd to +--------------- That isn't true, as far as I've been able to learn. I don't know if it's a lie or a misunderstanding on the part of someone at SCO, but it is incorrect. The POSIX filename truncation vs. error business is *optional* behavior intended to allow systems with hard filename length restrictions to still support a POSIX source code environment. It is *not* required, nor even desirable (from a POSIX compliance standpoint, that is), as far as I have been able to determine. I suspect that line is just SCO trying to justify managing to break "UNIX" in yet another way while managing to conform to all applicable standards. They excel at this, from my experience with SCO "UNIX". ++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