From: Roland via TUHS <tuhs@minnie.tuhs.org>
To: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Unix for PDP11/20 w/o mmu or paging option
Date: Fri, 17 Sep 2021 16:05:04 +0000 (UTC) [thread overview]
Message-ID: <205429669.748473.1631894704660@mail.yahoo.com> (raw)
In-Reply-To: <CANCZdfoiTcxy9UL2U=-4ADg+=hSE1-Fd9rB2qociZHtLa5rBBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
Hi Warner,
Thanks for your reply!
V5 is the earliest Unix we have contemporary images from. We have fragments from everything else earlier, including files scavenged/recovered from early DECtapes and some code recovered from kernel listings from a Unix course that was put together by Bell Labs...
What I foundon Wikipedia about Unix V5 is that is needs an MMU. " 5th Edition Targetedthe PDP-11/40 and other 11 models with 18 bit addresses." Because it uses18 bit address space it probably expects 248K of memory. My machine does nothave a paging option or mmu. So I think that means that I can't use V5 unfortunately...
The Unix 1972 project that some TUHS members did. I think it's in the TUHS distribution archive, but also on github. I think Warren Toomey's repo is the canonical one https://github.com/DoctorWkt/unix-jun72 but https://github.com/c3x04/Unix-1st-Edition-jun72 has a couple of newer fixes for a docker file to contain the simh simulator. I'm unsure what hardware that's supported, though. The machine file suggests:
rk03/rk11 177400 disk RK
dc11 174000 tty? (not supp?)
tc11/tu56 177340 dec tape DTn (not showing up in simh?)
rf11/rs11 177460 fixed head disk RF
kw11-l 177546 clock CLK
pc11 177550 paper tape PTR/PTP
asr-33 177560 tty? TTI, TTO
which has an RK03, not sure how close that is to an RK05, so some tweaks may be needed.
That RK03 isa Diablo 31. It uses the same packs and same interface as the RK05 and is 100%compatible. The RK05 was build by Digital itself and not by Diablo any more. I have the TC11/TU56, PC11, asr33 tty and KW11-L line clock as well. So that is almost the complete list of devices you showed here...
So if it is possible to generate a RK03/RK05 disk image from that simulator then I think I can put that on a real RK05 disk pack. But I'm completely new in this old Unix era... So if anyone could help to generate such an image then it would be a great help!
Regards, Roland
[-- Attachment #2: Type: text/html, Size: 4382 bytes --]
next prev parent reply other threads:[~2021-09-17 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2021-09-17 20:18 Noel Chiappa
2021-09-17 20:47 ` Clem Cole
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=205429669.748473.1631894704660@mail.yahoo.com \
--to=tuhs@minnie.tuhs.org \
--cc=roelof_klaas@yahoo.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).