The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Memory on Lion's v6
Date: Sun, 27 Feb 2022 23:09:02 -0700	[thread overview]
Message-ID: <CANCZdfrHa63KoqVvQuYF6301LbxSNZgu-AAkm=vhXDh50ysxZQ@mail.gmail.com> (raw)
In-Reply-To: <4e3c05d2-2496-b917-f1f4-1c6cba9ef58a@gmail.com>

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

On Sun, Feb 27, 2022, 10:51 PM Will Senn <will.senn@gmail.com> wrote:

> Does anybody know how much memory was configured on the PDP-11 that Lion's
> used for the commentary system. Here's what the book says about the system:
>
> ; from lions, page 1
> ; The code selection presumes a "model" system consisting of:
> ; PDP11/40 processor;
> ; RK05 disk drives;
> ; LP11 line printer;
> ; PC11 paper tape reader/punch;
> ; KL11 terminal interface.
>
> I usually add the mag tape, too
> ; TM10 magnetic tape - not in lions, but super handy
>
> It seems like he must have had an MMU and 128k memory, but I don't know.
> I'm hoping y'all remember, know, or can otherwise divine the correct value.
> I've run with no MMU - crash on boot. I've also run with less memory, but
> then cc won't build mkconf, when I have the TM10 enabled kernel loaded. As
> a reminder, his book was published in 1977.
>

V6 required the PDP-11 MMU. There are all kinds of code that writes
directly to the memory mapping registers. So Lions had to have had an MMU.
I'd imagine he had at least 128k of RAM, but likely not much more since the
budgets for these machines at the time in Australia was notoriously tight.

Warner

Thanks,
>
> Will
>

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

  reply	other threads:[~2022-02-28  6:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  5:48 Will Senn
2022-02-28  6:09 ` Warner Losh [this message]
2022-02-28 15:48 ` Clem Cole
2022-02-28 23:27   ` Andrew Hume
2022-03-01 15:31     ` Andrew Hume
2022-03-01  1:25 ` Bakul Shah
2022-03-01  0:44 Noel Chiappa
2022-03-02  1:19 Noel Chiappa
2022-03-02  2:15 ` Warner Losh
2022-03-02  2:26 Noel Chiappa

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='CANCZdfrHa63KoqVvQuYF6301LbxSNZgu-AAkm=vhXDh50ysxZQ@mail.gmail.com' \
    --to=imp@bsdimp.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).