The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: clemc@ccc.com, brantley@coraid.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Unix for PDP11/20 w/o mmu or paging option
Date: Fri, 17 Sep 2021 17:21:47 -0400	[thread overview]
Message-ID: <202109172121.18HLLlB8061859@ultimate.com> (raw)
In-Reply-To: <D2970D93-34A2-4BF4-82E7-9F8EC1F65665@coraid.com>

I was commenting based on the Boot Procedures man page on pg 5 of the pdf at:
https://www.bell-labs.com/usr/dmr/www/pdfs/man71.pdf
on dmr's "Unix Manual, first edition" page:
https://www.bell-labs.com/usr/dmr/www/1stEdman.html

which makes no reference to the rk disk, but does talk about loading up
initial files.

The page for init (pdf p.11) mentions that the usr directory is
mounted from the rk disk.

The rf0 page (pdf p3) at
https://www.bell-labs.com/usr/dmr/www/pdfs/man41.pdf
says
  "writing is inherently very dangerous since a file system resides there"

The description of seek on the special files really slapped me in the
face for the first time!

The tty page in the man41 file ever so slightly advances my theory
that the interrupt character on the PDP-7 console (0176 or rather 0376)
could have been generated by the "ALT MODE" key on the console Teletype.

But regarding memory management, I foolishly put my foot in the gopher
hole of assumption that the earliest kernel on hand required the
mystery MMU, without verifying by reading the code, and forgetting
that "editions" refer to dates the manual was published, and that the
fragmentary fossil record that is the earliest surviving code (which
was in a constant state of evolution) doesn't align with the manuals.

Mea culpa, for adding any confusion!

  parent reply	other threads:[~2021-09-17 21:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 15:35 Noel Chiappa
2021-09-17 18:28 ` Phil Budne
2021-09-17 19:43   ` Clem Cole
2021-09-17 19:51     ` Brantley Coile
2021-09-17 20:07       ` Clem Cole
2021-09-17 21:21       ` Phil Budne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-17 20:18 Noel Chiappa
2021-09-17 20:47 ` Clem Cole
     [not found] <2007825471.713023.1631887763341.ref@mail.yahoo.com>
2021-09-17 14:09 ` Roland via TUHS
2021-09-17 14:33   ` Warner Losh
2021-09-17 15:32     ` Clem Cole
2021-09-17 16:04       ` Roland via TUHS
2021-09-17 16:14         ` Clem Cole
2021-09-17 16:44           ` Roland via TUHS
2021-09-17 16:13       ` Warner Losh
2021-09-17 16:17         ` Clem Cole
2021-09-17 16:05     ` Roland via TUHS

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=202109172121.18HLLlB8061859@ultimate.com \
    --to=phil@ultimate.com \
    --cc=brantley@coraid.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@minnie.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).