From: Jonathan Gray <jsg@jsg.id.au>
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 12:06:24 +1000 [thread overview]
Message-ID: <ZLXzoIEf0x12QLCW@largo.jsg.id.au> (raw)
In-Reply-To: <20230718004946.4ACC518C09B@mercury.lcs.mit.edu>
On Mon, Jul 17, 2023 at 08:49:46PM -0400, Noel Chiappa wrote:
> 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).
"Berkeley's 11/45 was among the first systems that Thompson had encountered
that had two disks on the same controller!"
Twenty Years of Berkeley Unix
https://www.oreilly.com/openbook/opensources/book/kirkmck.html
> 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.)
tuhs/Applications/Dennis_Tapes/dmr_tapes.tgz
dmr_tapes/dmr2/tp/paper/p1 Nov 1973
"The PDP-11/45 on which our UNIX installation is implemented is a
16-bit word (8-bit byte) computer with 104K bytes of core memory;
UNIX occupies 42K bytes."
tuhs/Documentation/Papers/unix_cacm74.pdf July 1974
"The PDP-11/45 on which our UNIX installation is implemented is a
16-bit word (8-bit byte) computer with 144K bytes of core memory;
UNIX occupies 42K bytes."
tuhs/Distributions/Research/Dennis_v6/v6doc.tar.gz unix/p1 Jun 1975
"The PDP-11/45 on which our UNIX installation is implemented is a
16-bit word (8-bit byte) computer with 112K bytes of core memory;
UNIX occupies 53K bytes."
version from the Australian DECUS symposium (August 1977)
has the same line as as v6
tuhs/Documentation/Papers/BSTJ/bstj57-6-1905.pdf July/Aug 1978
"The PDP-11/70 on which the Research UNIX system is installed is a
16-bit word (8-bit byte) computer with 768K bytes of core memory;
the system kernel occupies 90K bytes about equally divided between
code and data tables."
v7/usr/doc/cacm/p1 matches bstj
next prev parent reply other threads:[~2023-07-18 2:06 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 [this message]
2023-07-18 13:10 ` Henry Bent
-- 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=ZLXzoIEf0x12QLCW@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--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).