Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!news.cs.indiana.edu!att!emory!gatech!mcnc!rti!mozart!sasdvp
From: sasdvp@unx.sas.com (David V. Phillips)
Newsgroups: comp.sys.apollo
Subject: Re:  malloc(3), diskspace, fix
Message-ID: <1990Nov09.144445.14149@unx.sas.com>
Date: 9 Nov 90 14:44:45 GMT
References: <9010261942.AA18426@richter.mit.edu>
Organization: SAS Institute Inc.
Lines: 16

In article <9010261942.AA18426@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
>
>There is an easy workaround at SR10 for the fact that programs now
>allocate enough disk space immediately, rather than as the virtual
>memory is actually used. The Aegis binder, /com/bind, has a switch
>named -vm_sparse or -sparse_vm (or something like that) that gives
>the SR9.7 style behavior.
>
  Umm, yeah, but what about applications created under SR9.7 that cannot
  be recompiled/relinked under SR10?  Is there any way to get those to 
  avoid allocated space immediately?
-- 
David Phillips  sasdvp@dev.sas.com
"They that can give up an essential liberty to obtain a little temporary
safety deserve neither liberty nor safety". -- Benjamin Franklin (1759)
"Gun control is being able to hit your target." -- Me.