Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!news.cs.indiana.edu!msi.umn.edu!cs.umn.edu!quest!digibd!rhealey
From: rhealey@digibd.com (Rob Healey)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO doesn't sell UNIX
Message-ID: <1990Dec08.140730.9747@digibd.com>
Date: 8 Dec 90 14:07:30 GMT
References: <1990Dec1.225346.16828@NCoast.ORG> <1990Dec02.213409.17190@ka3ovk.irs.GOV> <1990Dec04.003651.13014@jadpc.cts.com>
Organization: DigiBoard Incorporated, St. Louis Park, MN
Lines: 23

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
	/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.