SCO doesn't sell UNIX

[Jim Deitch]

In article <1990Dec02.213409.17190 at ka3ovk.irs.GOV> brown at ka3ovk.irs.GOV (Ken Brown) writes:
>In article <1990Dec1.225346.16828 at NCoast.ORG> allbery at ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
>>
>>There are more examples; I have a long list at work describing differences
>>between SCO Pseudnix and UNIX.
>>
>>+---------------
>>|        I've done the first 3, now all you bashers who have obviously spent
>>|        more time on SCO UNIX 3.2v2 than me fill in the rest!
>>+---------------
>>
>
>I've got another one.  As part of SysV, AT&T in their infinite wisdom
>decided to move the mail spool directory from /usr/spool/mail to
>/usr/lib/mail.  Seemed like a strange move to me, with no obvious benefits
>but, hey, it was their baby.  They can do as they wish.
>
>SCO comes along and decides to move it back to /usr/spool/mail.  This means
>that it is no longer safe to install mailers on SCO systems since the
>install programs will assume that SCO is SysV UNIX and default to the
>SysV standard.
>
>I'm not sure who I'm more pissed at -- AT&T for deciding to 'fix' something
>that wasn't broken, or SCO for deciding that they knew the 'right' way
>to do things -- thereby creating Pseudnix (I love that word).

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!

-- 
ARPANET:    jadpc!jdeitch at nosc.mil
INTERNET:   jdeitch at jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch