The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Research UNIX PDP 11/45
Date: Tue, 18 Jul 2023 09:10:34 -0400	[thread overview]
Message-ID: <CAEdTPBfTgRWc4aQFJguA5d4nwiOHL=4B=TY5=HiTv2J_=vDS0g@mail.gmail.com> (raw)
In-Reply-To: <20230718004946.4ACC518C09B@mercury.lcs.mit.edu>

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

On Mon, 17 Jul 2023 at 20:49, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Henry Bent
>
>     > there will be a lengthy addendum shortly.
>
> The most useful thing is probably this:
>
>   https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/low.s
>
> which lists exactly what was there; not only the types, but how many of
> each
> there are. This is from 'nsys', which is slightly before the actual V4, so
> it's quite early. 'low.s' is inherently machine-specific; i.e. different
> machines would share most kernel files identically, but _not_ this one -
> unless they had _absolutely identical_ device sets. So this one is
> _probably_
> the one from the /45 in picture.
>
> It shows:
>
>   RK11
>   RF11
>   PC11
>   TC11
>   TM11
>
>   1xKL11
>   12xDC11
>   1xDP11        (synchronous serial)
>   1xDN11        (dial-out asynch control)
>
>   1xDR11C       (parallel port to -11/20)
>   2xDC11        (Screw Works voice synthesizer)
>   1xDR11A       (voice response unit)
>   1xDR11C       (C/A/T typesetter)
>
> (Line printer, card reader and RP11 are commented out; more about the RP11
> in a later message.
>
>
> There's also this:
>
>   https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/11-45
>
> which is a bit hard to interpret, but I think might list what's in each
> rack:
> the TC11, RK11 (early ones), RF11 and TM11 (early ones) were large custom
> wire-wrapped backplanes which bolted into the front or back of a 19 inch
> rack; this:
>
>   https://gunkies.org/wiki/RK11-C_disk_controller
>
> has an image of such an RK11. The "MOS 16-24" is probably a reference to an
> MS11:
>
>   https://gunkies.org/wiki/MS11_Semiconductor_Memory_System
>
> which had to mount in the CPU backplane. The "MM" entries are likely core
> memory units; probably MM11-K's:
>
>   https://gunkies.org/wiki/MM11-K_core_memory
>
> since they seem to be 4KW each. (Maybe MM11-E's or 'F's, though; those are
> also 4KW each.) I'm not sure what they "PL"s are - probably Plessey core?
> Anyway,it looks like the machine had 104KB total.
>
>
> This file:
>
>   https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/ken/conf.c
>
> lists all the types of devices on the machine. One oddity is that it lists
> two RK11's; but if you look at the RK11 driver:
>
>   https://minnie.tuhs.org/cgi-bin/utree.pl?file=V4/nsys/dmr/rk.c
>
> it's only set up to handle one physical controller. But there is this:
>
>   #define       JRK     1       /* temp */
>
>         if (bp->b_dev.d_major==JRK)
>                 d = bp->b_dev.d_minor;
>         else
>                 d = bp->b_blkno%3;
>
> so the two different major device entries appear to handle the same disks
> in
> different ways ("d = bp->b_blkno%3" will spread a virtual drive across
> three
> physical drives).
>
>
> Memory, it would have been hard to say (UNIX even then sized memory at
> start
> up) but then I found that '11-45' file. I also found a copy of the CACM
> version of the UNIX paper:
>
>   https://people.eecs.berkeley.edu/~brewer/cs262/unix.pdf
>
> which says the machine had 144KB (so they had added 40KB more at that
> point).
> (I seem to recall someone had scanned the SOSP version; I didn't save the
> pointer, but if someone knows where it is, it would be interesting to look,
> and see what it says - they seemed to update this paper on a regular basis
> -
> the copy included with V6 talks about the -11/70.)
>
> The system at that point had "a 1M byte fixed-head disk .. four moving-head
> disk drives which each provide 2.5M bytes on removable disk cartridges, and
> a single moving-head disk drive which uses removable 40M byte disk packs"
>
> The RS11 disks for the RF11 were 512KB, so either they'd added a second
> one,
> or switched to an RS04 (but that's a MASSBUS device). The big disk was an
> RP03 so they had added an RP11, which wasn't present earlier.
>
>         Noel
>

Noel,
Thank you very much for this thoroughly researched and documented
explanation.  I hope that it will be of use to others as well.

-Henry

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

  parent reply	other threads:[~2023-07-18 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  0:49 Noel Chiappa
2023-07-18  2:06 ` Jonathan Gray
2023-07-18 13:10 ` Henry Bent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-17 22:32 Noel Chiappa
2023-07-17 22:51 ` segaloco via TUHS
2023-07-17 23:05   ` Henry Bent
2023-07-18  4:40 ` Angelo Papenhoff
2023-07-17 19:43 [TUHS] " Henry Bent
2023-07-17 22:13 ` [TUHS] " Clem Cole
2023-07-18  6:25   ` Lars Brinkhoff

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='CAEdTPBfTgRWc4aQFJguA5d4nwiOHL=4B=TY5=HiTv2J_=vDS0g@mail.gmail.com' \
    --to=henry.r.bent@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@tuhs.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).