Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!VIOLET.BERKELEY.EDU!mwm
From: mwm@VIOLET.BERKELEY.EDU.UUCP
Newsgroups: mod.computers.68k
Subject: Re: Minix to the 68k?
Message-ID: <8702132142.AA11619@violet.berkeley.edu>
Date: Fri, 13-Feb-87 16:42:46 EST
Article-I.D.: violet.8702132142.AA11619
Posted: Fri Feb 13 16:42:46 1987
Date-Received: Sat, 14-Feb-87 14:21:24 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17
Approved: info-68k@ucbvax.berkeley.edu

>> 	Given these constraints, it should be posible to implement a
>> multi-tasking O/S without having to hassle with a MMU.

True; it's been done (as many have pointed out). However, if you're
doing C or assembler development, loose pointers, mis-typed parameters
for calls, and other things will cause the system to die. This is
enough of a pain that ASDG is marketing a ram-disk driver that tries
to recover what was in memory before the crash when it comes up.

For interpreted Pascal, or Lisp, this won't be a problem. But
someone's gotta put up with porting those things (and editors, and
compilers, and etc.) in the first place.

Even under such conditions, the result is _still_ better than an
unprotected single-tasking OS.

	<mike