From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] Some notes on running UNIX v6 in 2015, using SimH and a healthy dose of documentation
Date: Thu, 3 Dec 2015 12:46:47 -0600 [thread overview]
Message-ID: <56608E17.5@gmail.com> (raw)
In-Reply-To: <20151203152150.C571C18C084@mercury.lcs.mit.edu>
Noel,
Thank you for writing and responding to my writeup. I have replied
inline, below:
On 12/3/15 9:21 AM, Noel Chiappa wrote:
> > From: Will Senn <will.senn at gmail.com>
>
> > I am studying Unix v6 using SimH and I am documenting the process
>
> I did a very similar exercise using the Ersatz11 simulator; I have a lot
> of stuff about the process here:
>
> http://www.chiappa.net/~jnc/tech/V6Unix.html
>
Thanks for reminding me about your work. I had scanned it briefly when I
was first starting down this road, but wrote it off because I wasn't
using the Ersatz11 simulator. With the background I have now, it should
be translate into my current frame and be useful. I haven't tried
tackling the time problem yet, but I will keep your document in mind
along with Wolfgang's fixes for ctime:
http://www.tuhs.org/Archive/PDP-11/Bug_Fixes/V6enb/
>
> > the PDP architecture
>
> Technically, a PDP-11 ...
Oops. I will be more careful in how I refer to the PDP-11 from now on.
> The only differences I could discover between the two are that in the Wellsch
> versions i) a Western Electric rights notice (which prints on booting) has
> been added to ken/main.c, and the Unix bootable images; and ii) the RK pack
> images do have, as you noted, the bootstrap in block 0.
Thanks for this. I will update my note appropriately.
> > Note: sh is critically important, don't muck it up :). The issue is
> > that if you do, there really isn't an easy way to recover.
>
> One should _never_ install a new shell version as '/bin/sh' until it has been
> run and tested for a while (for the exact reason you mention). Happily, in
> Unix, as far as the OS is concerned, the command interpreter is just another
> program, so it's trivial to name a new binary of the shell 'nsh' or
> something, and run that for a while to make sure it's working OK, before
> installing it as '/bin/sh'.
This is a duh moment for me. I will change the note to reflect testing
first, then copy over.
>
> > a special file (whatever that is)
>
> Special files are UNIXisms for 'devices'. _All_ devices in Unix appear as
> 'special files' in the file system, usually (but not necessarily) in /dev -
> that location is a convention, not a requirment of the OS.
>
I have since learned a lot more about this and will update the note.
Regards,
Will
next prev parent reply other threads:[~2015-12-03 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 15:21 Noel Chiappa
2015-12-03 17:27 ` Random832
2015-12-03 18:46 ` Will Senn [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 15:42 Noel Chiappa
2015-12-03 18:54 ` Will Senn
2015-12-04 0:52 ` Greg 'groggy' Lehey
2015-12-04 21:33 ` Win Treese
2015-12-04 22:00 ` John Cowan
2015-12-02 21:37 Will Senn
2015-12-03 0:20 ` Warren Toomey
2015-12-03 2:37 ` Will Senn
2015-12-03 4:11 ` Dave Horsfall
2015-12-03 4:18 ` Will Senn
2015-12-03 6:05 ` Peter Jeremy
2015-12-03 12:59 ` John Cowan
2015-12-04 6:22 ` Dave Horsfall
2015-12-04 6:38 ` Greg 'groggy' Lehey
2015-12-04 14:52 ` John Cowan
2015-12-04 18:17 ` Ronald Natalie
2015-12-04 18:33 ` Gregg Levine
2015-12-04 22:36 ` Greg 'groggy' Lehey
[not found] ` <CAKt831GfmmKQ75TRy1tCmmbnx4CGLmjy12zns6-c+_oJB+h2dA@mail.gmail.com>
2015-12-04 19:13 ` SZIGETI Szabolcs
2015-12-04 12:41 ` Peter Jeremy
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=56608E17.5@gmail.com \
--to=will.senn@gmail.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).