Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!tank!gargoyle!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: comp.unix.xenix
Subject: Re: SCO upgrade policy
Summary: Check the size of programs running under emulation; you'll choke!
Message-ID: <1990Mar9.181214.1453@ddsw1.MCS.COM>
Date: 9 Mar 90 18:12:14 GMT
References: <1990Mar6.121935.763@aucs.uucp> <1018@fiver.UUCP> <511259@nstar.UUCP>
Reply-To: karl@mcs.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc. - Mundelein, IL
Lines: 26

In article <511259@nstar.UUCP> larry@nstar.UUCP (Larry Snyder) writes:
>In article <1018@fiver.UUCP>, palowoda@fiver.UUCP (Bob Palowoda) writes:
>> From article <1990Mar6.121935.763@aucs.uucp>, by 870646c@aucs.uucp (Barry Comer):
>>    Please explain what "large base" of Xenix programs do not run on UNIX.
>> 
>
>For one - multiview runtime which is linked into the kernel - how in earth
>does one get "run time multiview for Xenix" linked into the Unix (386/ix)
>kernel?

There is another problem with running Xenix programs under "emulation" --
look at the "SZ" column sometime when you are executing some of these.

We have one package that normally occupies about 400K of core (as measured
by the "SZ" parameter in ps) when running.  Running the Xenix package on ISC
produces over 800K of allocated memory for the process -- or twice as much
space in use!  OUCH.

On the other hand, lots of that may never be used, and thus be paged out
once and that will be that.  That I don't know with any certainty.

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910]
Macro Computer Solutions, Inc.   "Quality Solutions at a Fair Price"