Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mcnc!ece-csc!hand
From: hand@ece-csc.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Networking Amigas + MMU's
Message-ID: <3322@ece-csc.UUCP>
Date: Sat, 18-Apr-87 17:09:14 EST
Article-I.D.: ece-csc.3322
Posted: Sat Apr 18 17:09:14 1987
Date-Received: Sat, 25-Apr-87 05:04:38 EST
References: <8704080809.AA04117@cory.Berkeley.EDU> <12822@watnot.UUCP>
Reply-To: hand@ece-csc.UUCP (Steven Hand)
Organization: North Carolina State University, Raleigh, NC
Lines: 23
Summary: Look at how VAX/VMS does it.

In article <12822@watnot.UUCP> ccplumb@watnot.UUCP (Colin Plumb) writes:

>There is, admittedly, one catch... libraries.  I'll have to look over the
>interface to see if something can be done.  They could always be made
>relocatable, but it would be nice not to have to.  How do other machines
>handle shared libraries?
>
>So, we can just divide 4 gig into quarters... private, (public) chip,
>public fast, and mappable (for debuggers).

The VMS operating system for the VAX handles shared virtual memory and also
allows processes to share code.  I also seem to remember reading that BSD 4.2
was going to allow shared memory but they ran out of time to implement it.

These are old issues, and we should definitely look at other machines
before reinventing the wheel (as has happened too many times in the micro
world).

Steve Hand	         decvax!mcnc!ece-csc!hand     
Box 7911
ECE Department
NC State Univ.           (919) 737-2336 ext. 34
Raleigh, NC 27695        (919) 834-4375