The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 12:06:04 -0600	[thread overview]
Message-ID: <56686D8C.30705@gmail.com> (raw)
In-Reply-To: <20151209175024.5180118C0C7@mercury.lcs.mit.edu>

Noel,

Comments below:

On 12/9/15 11:50 AM, Noel Chiappa wrote:
>      > From: Will Senn
>
>      > my now handy-dandy PDP11/40 processor handbook
>
> That's good for the instruction set, but for the memory management hardware,
> etc you'll really want one of the {/44, /45, /70, /73, etc} group, since only
> those models support split I+D.
I have the pdf for the /70, but I just ordered a new paper copy on 
Amazon, call me old fashioned :).
>
>      > the 18 bits holding the word 000407
>
> You mean '16 bits', right? :-)
Yes you are correct, 5 octal digits, only 16 bits used for instructions.

>      > This means that branches are to 9th, 10th, 11th and 7th words,
>      > respectively. It'll be a while before I really understand what the
>      > ramifications are.
>
> Only the '407' is functional. (IIRC, in early UNIX versions, the OS didn't
> strip the header on loading a new program into memory, so the 407 was actually
> executed.)  The others are just magic numbers, inspired by the '407' - the
> code always starts at byte 020 in the file.
OK. This is up as my next investigation and it will be guided by 
Lions'... figuring out exactly how programs get loaded in v6 and 
secondarily v7.

Thanks,

Will



  reply	other threads:[~2015-12-09 18:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 17:50 Noel Chiappa
2015-12-09 18:06 ` Will Senn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-19 13:27 Noel Chiappa
2015-12-10  4:50 Noel Chiappa
2015-12-09 22:16 Noel Chiappa
2015-12-09 22:31 ` Clem Cole
2015-12-09 22:47   ` John Cowan
2015-12-09 23:39     ` Steve Nickolas
2015-12-10  0:24       ` Clem Cole
2015-12-10  0:23     ` Clem Cole
2015-12-10  1:08       ` Greg 'groggy' Lehey
2015-12-10  9:42         ` Jacob Ritorto
2015-12-10  1:19       ` John Cowan
2015-12-10 10:06     ` Oliver Lehmann
2015-12-10 19:50       ` Will Senn
2015-12-09 22:01 Noel Chiappa
2015-12-09 14:56 Noel Chiappa
2015-12-09 16:37 ` Will Senn
2015-12-09 14:24 Noel Chiappa
2015-12-09 13:30 Noel Chiappa
2015-12-09 14:43 ` Ronald Natalie
2015-12-09 20:41 ` Dave Horsfall
2015-12-09  5:17 Noel Chiappa
2015-12-09  5:55 ` Mark Longridge
2015-12-09 11:31 ` Ronald Natalie
2015-12-09  4:53 Noel Chiappa
2015-12-09 14:38 ` Will Senn
2015-12-09 14:56   ` Clem Cole
2015-12-09 15:07     ` Clem Cole
2015-12-09 16:29       ` Will Senn
2015-12-09 14:59   ` Hellwig Geisse
2015-12-09 17:55 ` Will Senn
2015-12-09  3:33 Will Senn

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=56686D8C.30705@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).