From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Work I've done with a PDP-11 simulator
Date: Tue, 29 Apr 2014 22:19:54 -0400 (EDT) [thread overview]
Message-ID: <20140430021954.6E6FB18C0FC@mercury.lcs.mit.edu> (raw)
Hello, all: I'm working (long-term) on a project to bring back to life the
V6+ Unix system (it wasn't vanilla V6 - it looks like it had some PWB stuff
added) that was used on a number of machines at the Laboratory for Computer
Science at MIT in the late 70s - early 80s.
As part of that, I've been playing with bringing up V6 on a PDP11 simulator,
and have written some stuff that would probably be useful to anyone who's
interested in bringing up Unix on a PDP-11 simulator.
I used the Ersatz-11 simulator from D-Bit (for no particularly good reason,
except it runs under Windoze, and the "FAQ on the Unix Archive and Unix on
the PDP-11" page said it was the fastest).
I have been very pleased with this simulator; it is indeed fast (my simulated
11/70 runs at about 100 MIPS on a relatively elderly Athlon, which is about
30 times as fast as a real one used to :-), and it has lots of nice features
(e.g. you can TELNET in to a terminal port on the simulated PDP-11).
It also has this nice virtual device that allows a program running on the
simulated PDP-11 i) access to files in the Windows file system, and ii) to
issue commands to the emulator. I have written a V6 driver for it (should be
fairly easy to adapt to V7 or later), and a suite of Unix commands to grab a
file off the Windows file system (both binary and text mode), and issue
various commands to the simulator.
Finally, I have a number of Windows commands to do various useful things,
such as read a file off a simulated Unix V6 file system (hosted in a Windows
file), including ports of a number of Unix commands (e.g. ncheck, nm, etc); I
don't detail them all here as I don't want this email to get too long (and
boring).
I'm not sure if anyone's interested in any of this; if so, I can send
in more info (or whip up a Web page, whichever would be better).
I also ran into a number of pitfalls on the way to getting V6 running, using
RK05 disk images from the TUHS archive, and I can do a short writeup on 'How
to bring up V6 under Ersatz-11' if anyone's interested.
Noel
next reply other threads:[~2014-04-30 2:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 2:19 Noel Chiappa [this message]
2014-05-03 22:14 ` SPC
2014-05-03 22:20 ` Gregg Levine
2014-05-03 22:22 ` Larry McVoy
2014-05-05 13:50 ` Kurt H Maier
2014-05-04 23:54 Noel Chiappa
2014-05-05 1:53 ` John Cowan
2014-05-05 8:10 ` SPC
2014-05-05 15:32 Noel Chiappa
2014-05-11 0:51 Noel Chiappa
2014-05-11 0:57 ` Larry McVoy
2014-05-11 1:27 ` John Cowan
2014-05-11 1:58 ` Larry McVoy
2014-05-11 2:40 ` John Cowan
2014-05-11 2:06 Noel Chiappa
2014-05-11 2:31 ` Gregg Levine
2014-05-11 2:34 ` Gregg Levine
2014-05-11 17:21 ` Clem Cole
2014-05-11 17:24 ` Clem Cole
2014-05-11 18:50 ` Ronald Natalie
2014-05-11 3:13 Noel Chiappa
2014-05-11 4:20 ` John Cowan
2014-05-11 3:26 Noel Chiappa
2014-05-11 16:16 Norman Wilson
2014-05-11 16:45 ` John Cowan
2014-05-11 22:19 ` pechter
2014-05-11 23:13 Norman Wilson
2014-05-12 5:29 ` John Cowan
2014-05-12 14:49 Noel Chiappa
2014-05-12 17:06 Noel Chiappa
2014-05-12 17:20 ` SPC
2014-05-12 19:50 ` John Cowan
2014-05-12 19:10 Noel Chiappa
2014-05-12 20:59 ` SPC
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=20140430021954.6E6FB18C0FC@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).