Path: utzoo!utstat!utgpu!attcan!uunet!pdn!hargen
From: hargen@pdn.paradyne.com (Bill Hargen)
Newsgroups: news.software.b
Subject: Re: spacefor under sysV3.2
Message-ID: <1990Jun1.213223.27809@pdn.paradyne.com>
Date: 1 Jun 90 21:32:23 GMT
References: <1990May23.205735.3150@hawkmoon.MN.ORG>
Sender: usenet@pdn.paradyne.com (0000-USENET News Administrator(0000))
Organization: AT&T Paradyne, Largo, Florida
Lines: 19

In article <1990May23.205735.3150@hawkmoon.MN.ORG> det@hawkmoon.MN.ORG (Derek E. Terveer) writes:
>When you run build, it asks for the type of system to use when constructing a
>spacefor program.  I stated that is was either usg or sysv (i can't remember
>which right now -- but it was fairly obvious).  The spacefor program that was
>then created simply did not work under esix 5.3.2-c (which is a sysV3.2
>system).  However, the only change required by me to get it to work was to
>change the "nr = 2" to "nr = 1" in the awk script.  See below.

I had a similar problem on a Counterpoint System 19K, which is sysV3.0 with
Berkley network stuff added.  I discovered that the version of spacefor as
built for Xenix makes the same change (nf=3, nr=1) and works fine.  The
machine is definitely NOT running Xenix or anything remotely decended from
it, but telling build to use the Xenix model saves me from editing spacefor.

--
Bill Hargen				AT&T Paradyne
{uunet,peora}!pdn!hargen		Mail stop LG-132
Phone: (813) 530-8655			P.O. Box 2826
					Largo, FL  34649-2826