From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] First Unix that could run on a PDP-11 with QBUS
Date: Sun, 27 Jul 2014 01:39:36 -0400 (EDT) [thread overview]
Message-ID: <20140727053936.4AAB91DE381@lignose.oclsc.org> (raw)
Many Q-bus devices were indeed programmed exactly as if
on a UNIBUS. This isn't surprising: Digital wanted their
own operating systems to port easily as well.
That won't help make UNIX run on a Pro-350 or Pro-380,
though. Those systems had standard single-chip PDP-11
CPUs (F11, like that in the 11/23, for the 350; J11,
like that in the 11/73, for the 380), but they didn't
have a Q-bus; they used the CTI (`computing terminal
interconnect'), a bus used only for the Pro-series
systems. DEC's operating systems wouldn't run on
the Pro either without special hacks. I think the
P/OS, the standard OS shipped with those systems, was
a hacked-up RSX-11M. I don't know whether there was
ever an RT-11 for the Pro. There were UNIX ports but
they weren't just copies of stock V7.
I vaguely remember, from my days at Caltech > 30 years
ago, helping someone get a locally-hacked-up V7
running on an 11/24, the same as an 11/23 except is
has a UNIBUS instead of a Q-bus. I don't think they
chose the 11/24 over the 11/23 to make it easier to
get UNIX running; probably it had something to do with
specific peripherals they wanted to use. It was a
long time ago and I didn't keep notebooks back then,
so the details may be unrecoverable.
Norman Wilson
Toronto ON
next reply other threads:[~2014-07-27 5:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 5:39 Norman Wilson [this message]
2014-07-27 6:02 ` John Cowan
2014-07-27 14:10 ` Bill Pechter
2014-07-27 17:16 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2014-07-28 13:27 Noel Chiappa
2014-07-28 22:23 ` Dave Horsfall
2014-07-29 9:46 ` Warren Toomey
2014-07-29 9:56 ` Dave Horsfall
2014-07-29 14:33 ` Clem Cole
2014-07-29 13:10 ` Milo Velimirović
2014-07-27 3:26 Noel Chiappa
2014-07-27 5:49 ` Dave Horsfall
2014-07-28 22:04 ` Warren Toomey
2014-07-28 22:38 ` Warner Losh
2014-07-29 9:06 ` SPC
2014-07-29 13:28 ` Clem Cole
2014-07-27 2:37 Mark Longridge
2014-07-28 15:57 ` Ron Natalie
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=20140727053936.4AAB91DE381@lignose.oclsc.org \
--to=norman@oclsc.org \
/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).