Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!uplherc!esunix!bambam!bpendlet
From: bpendlet@bambam.UUCP (Bob Pendleton)
Newsgroups: comp.arch
Subject: Re: IBM PC prehistory
Message-ID: <384@bambam.UUCP>
Date: 17 Jan 90 16:26:38 GMT
References: <1990Jan16.055625.8255@esegue.segue.boston.ma.us>
Organization: Evans & Sutherland Computer Corp., Salt Lake City, Utah
Lines: 23

From article <1990Jan16.055625.8255@esegue.segue.boston.ma.us>, by johnl@esegue.segue.boston.ma.us (John R. Levine):
> In article <380@bambam.UUCP> bpendlet@bambam.UUCP (Bob Pendleton) writes:
>>> I would suggest that an MMU is necessary for anything which wants to 
>>> implement fork() while allowing two tasks to occupy memory at once.
> 
>>My conclusion is that you've never heard of a relocating loader.
> 
> Don't be so rude, he's right.

When I wrote that line it seemed perfectly OK. But rereading I see
that it IS rude as hell. I'm sorry. I did not mean to be rude.

I didn't mean to be wrong either. But I am. Since you cannot identify
(aliasing) every pointer created in a running program you can't adjust
the value of the pointers when you copy them.

			Bob P.

-- 
              Bob Pendleton, speaking only for myself.
UUCP Address:  decwrl!esunix!bpendlet or utah-cs!esunix!bpendlet

                      X: Tools, not rules.