The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
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: Wed, 2 Dec 2015 20:37:14 -0600	[thread overview]
Message-ID: <565FAADA.3040401@gmail.com> (raw)
In-Reply-To: <20151203002042.GA7042@www.oztivo.net>

Warren,

Thanks for the comment. I appreciate your feedback and will make 
appropriate changes.

Next? I have been reading Lyons and it has taken me some time to develop 
enough background knowledge to make sense of his notes. A surface read 
of the notes will give a novice reader some idea of the major 
architectural components of the system, but a deeper read will require 
the reader to have knowledge beyond what is required of most modern 
software developers (PDP-11 architecture, assembly language, and UNIX 
are prerequisite). It will also require access to a lab where the ideas 
covered can be experimented with. A modern reader might be intrigued 
from a historical perspective, but may not be compelled to go to the 
trouble of learning enough about the past to recreate it or even see the 
its relevance to the present or future.

Access in 2015 to a working UNIX v6 environment on a PDP-11 ala 1975 is 
as unlikely as it sounds. However, using SimH to simulate a functional 
PDP-11, with peripherals, a UNIX v6 tape image from 1975, and the 
documentation from that period, which, thanks to TUHS is now accessible, 
it becomes possible to establish a laboratory from which to experiment. 
The resulting environment is not only historically interesting, but 
technically interesting, as well.

Many of the interesting bits about our current systems, even seemingly 
unexplainable things like magic numbers, have their genesis and rational 
in this early system. The v6 kernel weighs in at around 10k lines of 
code with a limited set of peripherals and yet it packs in features that 
were either unavailable in larger more established systems or may have 
been present in some form, but were orders of magnitude more lines of 
code and attendant complexity. It was and remains an amazing operating 
system and worthy of contemporary study.

So, I was thinking that next up, I would write up notes to help the 
modern reader engage with v6 more easily in order to follow works like 
Lyons. Right now, I am working on notes related to using the v6 assembly 
and c languages to produce working code. While this may seem trivial to 
folks who are expert, or who have worked in the actual environments, it 
is not really so trivial for me or for other folks brought up on more 
modern computing platforms and I would like to both understand the 
workflows and to document them for others.

Regards,

Will



> On Wed, Dec 02, 2015 at 03:37:42PM -0600, Will Senn wrote:
>> I am studying Unix v6 using SimH and I am documenting the process,
>> http://decuser.blogspot.com/2015/11/installing-and-using-research-unix.html
> That's a great writeup Will. The only comment I have is a pedantic one:
> can you write "pdp" as "PDP-11"?
>
> Otherwise, it's highly readable, explain why you did things the whay you
> did, and someone else should be able to read your notes and reproduce your
> work.
>
> What do you plan to do next?
>
> Cheers, Warren




  reply	other threads:[~2015-12-03  2:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 21:37 Will Senn
2015-12-03  0:20 ` Warren Toomey
2015-12-03  2:37   ` Will Senn [this message]
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
2015-12-03 15:21 Noel Chiappa
2015-12-03 17:27 ` Random832
2015-12-03 18:46 ` Will Senn
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

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=565FAADA.3040401@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).