Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Use of Resident
Message-ID: <21468@ucbvax.BERKELEY.EDU>
Date: Tue, 27-Oct-87 01:03:39 EST
Article-I.D.: ucbvax.21468
Posted: Tue Oct 27 01:03:39 1987
Date-Received: Thu, 29-Oct-87 07:24:36 EST
References: <4086@garfield.UUCP> <21428@ucbvax.BERKELEY.EDU> <21466@ucbvax.BERKELEY.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 30
Keywords: resident
To: ucbvax!ji!shs


In article <21466@> shs@ji.Berkeley.EDU.UUCP (Steve Schoettler) writes:
>In article <21428@> bryce@hoser.berkeley.edu.UUCP (Bryce Nesbitt) writes:
>>
>>If the program is NOT reusable the new resident was to treat itself as
>>a RAM disk, it would "reload" the program for each invocation.
>
>  I had an idea about a year ago but forgot about it until now.
>
>  What about sorting an exacutable file's hunks on the disk so that the data
>hunks come first?  Then rewrite LoadSeg() to first look and see if the
>program is "resident" and if so, only load in the new data hunks.
>....
>  Programs could modify variables (including globals) however they wanted
>because they would all have their own data space.

You forget that code segments have absolute references into the data
segements.  For this reason it is not possible to have multiple data
segments for multitple tasks.

(Unless the programs knew about it in advance... which is not what we
are talking about)

>  Steve Schoettler
>  ...ucbvax!ji!shs

|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce
 (")
  U	"Fanitic: One who can't change his mind, and won't change the
	 subject."