From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] 2.9 kernel compile
Date: Wed, 11 Feb 2015 11:37:38 -0500 (EST) [thread overview]
Message-ID: <20150211163738.8DFC518C096@mercury.lcs.mit.edu> (raw)
> From: Cory Smelosky <b4 at gewt.net>
> Only the 11/23+ can, early rev 11/23s couldn't go above 256K.
Correctamundo on the last part, but not the first. I have both 11/23+'s and
11/23's, and I can assure you that Rev C and later 11/23's (the vast majority
of them) can do more than 256KB. See:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/1123.eco
for more.
Noel
next reply other threads:[~2015-02-11 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 16:37 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-12 15:44 Noel Chiappa
2015-02-12 15:27 Noel Chiappa
2015-02-13 2:20 ` Dave Horsfall
2015-02-12 13:47 Noel Chiappa
2015-02-12 14:16 ` Jacob Ritorto
2015-02-13 2:15 ` Dave Horsfall
2015-02-12 3:43 Noel Chiappa
2015-02-11 21:14 Noel Chiappa
2015-02-12 3:23 ` Jacob Ritorto
2015-02-11 16:20 Noel Chiappa
2015-02-11 16:27 ` Cory Smelosky
2015-02-11 20:32 ` Jacob Ritorto
2015-02-11 20:38 ` Jacob Ritorto
2015-02-12 9:50 ` Dave Horsfall
2015-02-11 15:47 Jacob Ritorto
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=20150211163738.8DFC518C096@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).