Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!cbosgd!ukma!david From: david@ukma.UUCP (David Herron, NPR Lover) Newsgroups: net.micro.68k Subject: Re: Re: Re: Re: Info on OS9 Operating System Message-ID: <2283@ukma.UUCP> Date: Thu, 10-Oct-85 11:34:02 EDT Article-I.D.: ukma.2283 Posted: Thu Oct 10 11:34:02 1985 Date-Received: Sat, 12-Oct-85 21:32:16 EDT References: <347@wlbr.UUCP> <9500001@datacube.UUCP> <126@mcrware.UUCP> <275@graffiti.UUCP> <138@mcrware.UUCP> Reply-To: david@ukma.UUCP (David Herron, NPR Lover) Organization: Univ. of KY Mathematical Sciences Lines: 27 In article <138@mcrware.UUCP> kim@mcrware.UUCP (Kim Kempf) writes: >> 2) True, but... I don't want to do serious work on a machine without >> an MMU any more. It's so frustrating... even sickening... to watch >> a lost pointer or bad copy of foocalc blow away everything & write >> garbage over a:\*.* >> >The MMU does a little more than protect memory. It allows manipulation of a >process' logical address spaces. In fact, the UNIX fork system call CANNOT >operate without an MMU (or some type of segment/base register allocation >scheme [ala 80*86]). Tell that to the people who put together V6 Mini Unix. We ran that sucker on a PDP-11/10. NO mmu in that beast. And it regularly died every time you had a pointer fault in your C program. It was bad enough that the friend of mine that ran the machine patched up the shell so it would sync every time it printed a prompt or ran a program. This way he wouldn't have to fix the disk so often. (No fsck). Sorry, I don't know any details of the system -- The only time I really looked at V6 was as an intelectual exsercise, I needed to understand the basic design structure of Unix. -- David Herron, ukma!david@ANL-MCS.ARPA, cbosgd!ukma!david (Soon -- david@UKMA.BITNET, and (hopefully) david@ukma.csnet) Hackin's in me blood! My mother was known as Miss Hacker before she married!