SCO doesn't sell UNIX

[Jim Deitch]

In article <1990Dec08.140730.9747 at digibd.com> rhealey at digibd.com (Rob Healey) writes:
>In article <1990Dec04.003651.13014 at jadpc.cts.com> jdeitch at 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
>	/etc/conf/cf.d, run configure, select menu 3, and set the
>	ETRUNC parameter to 1. Quit configure, type link_unix, install
>	the new kernel and reboot. The default behaviours on SCO UNIX
>	are POSIX conformance rather than Xenix/ATT3.2UNIX conformance,
>	where they collide, like ETRUNC, POSIX wins... There is some
>	other POSIX stuff you can turn off but I'll leave that as an
>	exercise to the reader. Tip: Read the System Administrator's
>	Guide cover to cover, it'll save you some time in the long run.
>
>	Next SCO UNIX complaint that can be solved by carefully reading
>	the manuals or release notes please? B^).
>
>		-Rob
>p.s.
>	Ya, ya, ya, I know reading manuals is for whimps but sometimes
>	it really DOES help.

That isn't what I was complaining about.  I was complaining that by
default any other unix truncates.  If SCO is shipping unix why not set
the flag off by default?  That way you are doing what the rest of the known
universe expects.


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