The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Unix on PDP8?
Date: Tue, 28 Nov 2017 18:26:08 -0500	[thread overview]
Message-ID: <007501d368a0$45b740d0$d125c270$@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2NpvCWkPSju9dQMyBHjYYdwoCDUY9McXQRmyAPHZU+WSw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]

Ø  People like me did not start to "port" UNIX until the 16 bit micro's show up -- i.e. the 68000, Z8000, 8086 where you could build a 'microcomputer' that was close to the power of the 'minicomputer' for a lot less money.

 

 

 Mike Muuss’s standard answer to any question was that we could put UNIX on it.    This is how he wrested the RSTS-running PDP-11/45 away from the EE department to start with (only proviso is that he had to get Basic+ running on it).    At BRL, he picked up a bunch of PDP-11 variants that were lying around (particularly an 11/34-based RJE system for the Cyber mainframe.    We pitched the card reader but used the printer, the vector general graphics system, and the DQ-11/modem combo).    Then when BRL commissioned the HEP to be built and nobody had a clue what software to put on it, we launched into the port on the HEP.   This was 1982.   It our first foray into a non PDP/VAX platform.    

 

Amusingly, I had a manager show up in my office and tell me that in a few years they would have the performance of a VAX in a little cubic foot box I could have on my desk all to myself and I’d be happy.    It was then I coined “Ron’s rule of computing.”   Our expectations grow with the technology.   Ron always needs a computer “this” (holding my hands out to approximately the width of a 780 cpu cabinet) big.    It worked for many years but I have to admit around 2000 or so, I started being happy with comptuers about the size of 2 drawer filing cabinets.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171128/84518f5b/attachment.html>


  reply	other threads:[~2017-11-28 23:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 19:55 Will Senn
2017-11-28 20:24 ` Clem Cole
2017-11-28 23:26   ` Ron Natalie [this message]
2017-11-29  6:56 ` Lars Brinkhoff
2017-11-29 14:05   ` Clem Cole
2017-11-30  0:53     ` Robert Swierczek
2017-11-30  8:34     ` emanuel stiebler
2017-11-29 14:31   ` Ron Natalie
2017-11-29 22:11     ` Dave Horsfall
2017-11-29 22:28       ` Warren Toomey
2017-11-29 23:12         ` Dave Horsfall
2017-11-30  1:17     ` Robert Swierczek
2017-11-30  2:37       ` Dave Horsfall

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='007501d368a0$45b740d0$d125c270$@ronnatalie.com' \
    --to=ron@ronnatalie.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).