The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Will pdp 11/04 run unix?
Date: Thu, 30 Jul 2020 09:53:31 -0400	[thread overview]
Message-ID: <CAC20D2MQJEtOtA4-wVwuqe=6z+FgYb3yTWr1F79zpwKi1mhCgg@mail.gmail.com> (raw)
In-Reply-To: <c92651d9-74ff-8c58-0a27-4038e7e02c82@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

PDP 11/04, like 11/03,11/05, 11/15, 11/20 lacks an MMU.    So the
traditional releases from Research, USG, UCB will not boot.
That said, V1 which ran without it might work with some tweeking as they
did not yet have one.  And if you could find a KS-11 MMU that Ken and
Dennis had for the 11/20 (which was designed by DEC CSS), theoretically
next versions could be made to run.   The problem is that while many of us
have looked a: we can not find a KS-11 in real life (CSS did make that
many), b: we can't even find documentation about it (Ken's surviving code
is the best doc we have).

FYI:  go to bitsavers and download a copy of the PDP-11 Processor
Handbook, but note the data.  You probably will want (at least) both
an early and a later one, as the later ones often dropped details about
some of the models that were not being manufactured.   For instance, I have
a couple of different ones, and the '78 version really one talks about
04/34/45/55/60 - the previous processors like 03/15/40 are not included.
So you need an early 70's version to include them, and later versions for
the 44/90 etc.

BTW:  Page 4 of same, have a graphic showing the HW requirements for the
DEC OS's. On the X-axis is the OS, the Y axis the model.  RT-11, MUMPS-11,
RSX-11M, RS-11S are the only OS's that were supported for the 04.

Here is a hint, if the processor could not support RSTS, it is unlikely it
could support UNIX.



On Thu, Jul 30, 2020 at 9:17 AM Will Senn <will.senn@gmail.com> wrote:

> The question is can I run Unix on a PDP 11/04? I've dug around and it's
> unclear to me, so I'm asking y'all.
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>
>

[-- Attachment #2: Type: text/html, Size: 3006 bytes --]

  reply	other threads:[~2020-07-30 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 13:16 Will Senn
2020-07-30 13:53 ` Clem Cole [this message]
2020-07-30 14:01   ` Clem Cole
2020-07-30 13:47 Noel Chiappa
2020-07-30 14:08 ` Ronald Natalie
2020-07-30 16:13 ` Warner Losh
2020-07-30 18:00   ` Heinz Lycklama
2020-07-30 18:55 ` Angelo Papenhoff
2020-07-30 17:20 Noel Chiappa
2020-07-30 21:37 Noel Chiappa
2020-07-31  7:10 ` Angelo Papenhoff

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='CAC20D2MQJEtOtA4-wVwuqe=6z+FgYb3yTWr1F79zpwKi1mhCgg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@gmail.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).