The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mutiny.mutiny@rediffmail.com (Mutiny )
Subject: [TUHS] Zilog Z80 Unix
Date: 20 Apr 2017 13:41:38 -0000	[thread overview]
Message-ID: <1492691693.S.3763.29563.f4-235-222.1492695698.7643@webmail.rediffmail.com> (raw)
In-Reply-To: <20170420123409.BA37918C0B3@mercury.lcs.mit.edu>

not to forget Sun&nbsp;UNIX&nbsp;0.7 (Sun-1) From: jnc at mercury.lcs.mit.edu (Noel Chiappa)Sent: Thu, 20 Apr 2017 18:04:53To: tuhs at tuhs.orgCc: jnc at mercury.lcs.mit.eduSubject: Re: [TUHS] Zilog Z80 Unix&nbsp; &nbsp;&gt; From: &quot;Erik E. Fair&quot;&nbsp; &nbsp;&gt; I have a memory of having seen a Zilog Z-80 .... based Unix, possibly v6&nbsp; &nbsp;&gt; ... I recall asking the people in the booth how they managed without an&nbsp; &nbsp;&gt; MMU, and don&#39;t recall their answer. I do remember thinking that since&nbsp; &nbsp;&gt; Unix had &quot;grown up&quot; with MMUs to stomp on obvious pointer mistakes, the&nbsp; &nbsp;&gt; software ought to be relatively well-behavedI don&#39;t know about the Z80 part, but for the MMU aspect, recall that the firstcouple of versions of PDP-11 Unix ran on a model (the -11/20) which didn&#39;thave an MMU (although, as mentioned before here, it apparently did later use athing called a KS11, the specifications for which seem to be mostly lost).A
 lthough recall the mention of calling out &quot;a.out!&quot;, as to the hazards ofdoing so...And of course there was the &#39;Unix for an LSI-11&#39; (LSX), although I gather thatwas somewhat lobotomized, as the OS and application has to fit into 56KBtotal.So it was possible to &#39;sorta kind-of&#39; do Unix without an MMU.&nbsp; Noel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170420/f96825b2/attachment.html>


  reply	other threads:[~2017-04-20 13:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 12:34 Noel Chiappa
2017-04-20 13:41 ` Mutiny  [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-20  1:42 Erik E. Fair
2017-04-20  2:54 ` Jason Stevens
2017-04-20  3:09 ` Bakul Shah
2017-04-20  3:40   ` Gregg Levine
2017-04-20  4:34     ` Bakul Shah
2017-04-20  4:50       ` Warner Losh
2017-04-20  7:03       ` Wesley Parish
2017-04-20  7:32         ` Wesley Parish
2017-04-20  4:32   ` Rik Schneider
2017-04-20 13:05 ` Clem Cole
2017-04-22 21:07   ` Dave Horsfall
2017-04-22 23:59     ` Clem cole
2017-04-23  0:01     ` Clem cole
2017-04-23  0:13     ` Larry McVoy
2017-04-24  0:04       ` Greg 'groggy' Lehey
2017-04-24  0:40         ` Larry McVoy
2017-04-23  5:14   ` Wesley Parish
2017-04-23  5:14   ` Wesley Parish
2017-04-20 21:32 ` Dave Horsfall
2017-04-20 21:59   ` Larry McVoy
2017-04-20 22:33     ` Steve Nickolas
2017-04-20 23:28     ` Pete Turnbull
2017-04-20 23:19   ` Harald Arnesen
2017-04-21  0:03     ` Andy Kosela
2017-04-23 17:58 ` Michael Welle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1492691693.S.3763.29563.f4-235-222.1492695698.7643@webmail.rediffmail.com \
    --to=mutiny.mutiny@rediffmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).