From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Zilog Z80 Unix
Date: Wed, 19 Apr 2017 21:34:10 -0700 [thread overview]
Message-ID: <20170420043410.815CC124AEAD@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 19 Apr 2017 23:40:30 EDT." <CAC5iaNFwq+xwBgZuaBPemGs=7MQy=KE0f3Vffg1KLPj+_VpPOA@mail.gmail.com>
Yes, Cromemco was the company, Cromix their unix like OS.
IIRC, in 1981-83 timeframe someone I worked with had mentioned
he used to work at Cromemco and that they had a unix like OS
called Cromix. Cromemco were in Mountain View so likely they
were at the WCCF.
Even though z80 could only address 64k, their system had a
bank select under s/w control & upto 512K of RAM could be
added. Z80 didn't have a supervisor mode but still, the bank
select must have afforded enouh protection from bad pointers
crashing random processes.
On Wed, 19 Apr 2017 23:40:30 EDT Gregg Levine <gregg.drwho8 at gmail.com> wrote:
> Hello!
> That was also a board vendor. FYI: The first GASP [GetAway Special
> Program] a Space Shuttle payload made use of such a board.
> -----
> Gregg C Levine gregg.drwho8 at gmail.com
> "This signature fought the Time Wars, time and again."
>
>
> On Wed, Apr 19, 2017 at 11:09 PM, Bakul Shah <bakul at bitblocks.com> wrote:
> > On Wed, 19 Apr 2017 18:42:42 PDT "Erik E. Fair" <fair-tuhs at netbsd.org> wrote:
> >> I have a memory of having seen a Zilog Z-80 (not Z8002 like the Onyx) based
> >> Unix, possibly v6, at a vendor show or conference - perhaps the West Coast
> >> Computer Faire (WCCF) in the late 1970s or early 1980s.
> >>
> >> I recall asking the people in the booth how they managed without an MMU, and
> >> don't recall their answer. I do remember thinking that since Unix had "grown
> >> up" with MMUs to stomp on obvious pointer mistakes, the software ought to be
> >> relatively well-behaved ... you know: not trying to play "core war" with
> >> itself?
> >>
> >> I searched the TUHS archives cursorily with Google to see if this has been
> >> previously mentioned, but pretty much all Z80 CPU references have for its use
> >> in "smart" I/O devices back in the day.
> >>
> >> Does anyone else remember this Z80 Unix and who did it? Or maybe that it was
> >> a clone of some kind ... ?
> >>
> >> looking for a little history,
> >>
> >> Erik Fair
> >
> > You may be thinking of Cromemco.
next prev parent reply other threads:[~2017-04-20 4:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2017-04-20 12:34 Noel Chiappa
2017-04-20 13:41 ` Mutiny
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=20170420043410.815CC124AEAD@mail.bitblocks.com \
--to=bakul@bitblocks.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).