Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ucla-cs!sdcrdcf!ism780c!tim
From: tim@ism780c.UUCP
Newsgroups: comp.sys.m68k
Subject: Re: Was Re: Recent Motorola ad seen in Byte
Message-ID: <5896@ism780c.UUCP>
Date: Mon, 6-Apr-87 15:33:37 EST
Article-I.D.: ism780c.5896
Posted: Mon Apr  6 15:33:37 1987
Date-Received: Thu, 9-Apr-87 00:42:27 EST
References: <8704050506.AA25220@cory.Berkeley.EDU>
Reply-To: tim@ism780c.UUCP (Tim Smith)
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 19

In article <8704050506.AA25220@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
<	An MMU a UNIX system doesn't make.  It takes a lot more than a mere
< MMU to make a *real* UNIX system smooth.  When your talking 'real' systems,
< your talking enough complexity that having the MMU internal or external
< doesn't really make a difference.

My point was not that internal MMUs are in some way better than external
MMUs ( they aren't ).  My point was that when the MMU is not on the same
chip as the CPU, it often gets left off.  An internal MMU will beat the
pants off of a nonexistent MMU!

With a '386, the hardware guys would have to to do a lot of extra work to
stop me from running Unix.  With a 680xx, they have to do some extra work
to let me to run Unix.
-- 
Tim Smith			"And if you want to be me, be me
uucp: sdcrdcf!ism780c!tim	 And if you want to be you, be you
Compuserve: 72257,3706		'Cause there's a million things to do
Delphi or GEnie: mnementh	 You know that there are"