The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Work I've done with a PDP-11 simulator
Date: Sun,  4 May 2014 19:54:26 -0400 (EDT)	[thread overview]
Message-ID: <20140504235426.4EF2418C0AA@mercury.lcs.mit.edu> (raw)

    > On Sat, May 03, 2014 at 06:20:55PM -0400, Gregg Levine wrote:

    > What he said. I believe we all are interested.

OK, I have whipped up some material on how to bring V6 up under Ersatz-11.
See here:

  http://ana-3.lcs.mit.edu/~jnc/tech/unix/V6Unix.html

That page covers i) how to get the emulator, V6 Unix disks, and what you need
to do start it running, and then ii) some of the initial steps to take past
that to improve to working environment. Included in that are a couple of
things I tripped over, and how to avoid them.

The latter part assumes you want to do something more than just start it, so
you can see it start up; it includes coverage of the commands that work with
the emulator's "DOS device" to do things like read files off the host machine
into the Unix; a serious problem on V6 Unix having to do with 21st Century
dates; a 'more' command for V6 Unix (Vanilla V6 was back before the days of
video terminals... :-); the ability to TELNET into the emulator; and some
useful Windows commands (e.g. to read files out of the Unix into the host
machine, and create blank disk pack files); and finally configuration file
for the E11 emulator.


There is more content/pages coming: the start of an 'advanced things you can
do to improve your V6 Unix' page, which includes the new C compiler [the
'vanilla' V6 C compiler does not handle longs, unsigned, casts, and a bunch
of other things]; tar; the Standard I/O library; etc is already there, but
unfinished. And I have some material on things you can trip over in porting
stuff back and forth (I found some doozies trying to make V6 commands run
under Windoze), etc. But that will be later.


For now, I'm interested in hearing: of any errors or issues with the first
page; whether people find it completely incomprensible, or totally fantastic
(or whereever on the axis between them it lies); what additional topics I
should cover; etc, etc.

Let me know! And enjoy your V6 experience!
	
	Noel



             reply	other threads:[~2014-05-04 23:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 23:54 Noel Chiappa [this message]
2014-05-05  1:53 ` John Cowan
2014-05-05  8:10   ` SPC
  -- strict thread matches above, loose matches on Subject: below --
2014-05-12 19:10 Noel Chiappa
2014-05-12 20:59 ` SPC
2014-05-12 17:06 Noel Chiappa
2014-05-12 17:20 ` SPC
2014-05-12 19:50 ` John Cowan
2014-05-12 14:49 Noel Chiappa
2014-05-11 23:13 Norman Wilson
2014-05-12  5:29 ` John Cowan
2014-05-11 16:16 Norman Wilson
2014-05-11 16:45 ` John Cowan
2014-05-11 22:19   ` pechter
2014-05-11  3:26 Noel Chiappa
2014-05-11  3:13 Noel Chiappa
2014-05-11  4:20 ` 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  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-05 15:32 Noel Chiappa
2014-04-30  2:19 Noel Chiappa
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

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=20140504235426.4EF2418C0AA@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).