Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Re: RESIDENT
Message-ID: <8706040242.AA11827@cogsci.berkeley.edu>
Date: Wed, 3-Jun-87 22:42:46 EDT
Article-I.D.: cogsci.8706040242.AA11827
Posted: Wed Jun  3 22:42:46 1987
Date-Received: Sun, 7-Jun-87 05:28:39 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 72

>>-------
>>For reasons other that the one above I have been working on a "RESIDENT".
>>Beat on me hard enough and I will finish and release it.
>
>Yay.  Do it.

The snag I ran into while writting my new hyper-fancy RESIDENT was that to
do it "right" I needed a new segment loader.  That turned out to be just a
little bit too hairy a problem without "official" support.  UnLoadSeg() was
much easier... :-)

Naturally BSS hunks are supported.  Shared or exclusive TEXT is supported
along with shared or exclusive DATA.

The "Magic" mentioned along with several hyper-kludges related to the
segment loader work as planned, but the overall picture is far from
complete:

In addition to the segment loader there is a need for the ability to write
a true compatible CLI [complete with BCPL-dirty Exec()] that can then
understand the new resident segments properly.	CLI-Resident is just the
thing but...  but...

*
With the BCPL compatible Exec(), and segment loader modifications, that
will wrap up what's needed for the CLI.  I still need a leap of insight to
do this seamlessly from the Workbench.	(When in doubt, plagiarize!  Where
are those BSD 4.3 docs?)
--> short of that, ideas? comments? <--


>>-------
>>Back in November I wrote an expose on the dangers of RESIDENT.

I still maintain that the old RESIDENT is *NOT* defective. Taking a look
at what's in mine right now:

run
x	(execute, really)
cd
list
type
hex

All those are 100% compatible.	(BTW: nearly all of the RESIDENT compatible
BCPL commands in my C: directory have been replaced with 68000 eqivalents,
written with RESIDENT compatibility in mind.)
(No flames about C programs not working with the old RESIDENT.	That's what
the new one is all about, ok?)


> It needs a CLI/Shell that understands "sticky" text segments.
> In other words, I don't think a RESIDENT command
> in and of itself will do the trick.  But you knew that.

(Yup, that's in the plan...)


>> BTW:  resident was initially released on a disk with no distribution
>> restrictions printed on it, and it does not contain a copyright notice.
>
> Wasn't it released to developers only, under the terms of the
> non-disclosure agreement?

What non-disclosure agreement?

-------------
         Ack!  (NAK,EOT,SOH)
 |\ /|  .
 {o O} .  bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce
 ( " ) 
   U      Single tasking?  Just say *NO!*