From: Will Senn <will.senn@gmail.com>
To: Clem cole <clemc@ccc.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Upgrading from 11/40 to 11/45 in Unix v6
Date: Sun, 30 Dec 2018 21:31:34 -0600 [thread overview]
Message-ID: <A81530EA-2DF1-4BFA-93AE-6666E9C67E13@gmail.com> (raw)
In-Reply-To: <7AEB778A-EBC9-4A89-8E3B-A771FF5FC9B3@ccc.com>
> On Dec 30, 2018, at 8:43 PM, Clem cole <clemc@ccc.com> wrote:
>
> The primary difference between the 11/40 class and 11/45 class is separate I/D space which I sometimes refer to as the 17th address bit because it allows you a full 64k of data space as well as a 64k of instructions space.
>
Do you know of some commonly used at the time v6 programs that needed that much space?
> After you are booted, a 45 class machine will run 40 class binaries unchanged. 40 class machines can not run a.outs that are seperate I/D.
Good to know.
> You’ll probably want to configure a kernel for the 45 class machine. Look at the differences in the *.s files in the kernel. IIRC there is a different file for 40 class and 45 class systems
I read about this in ’Setting up Unix Sixth Edition” and I see the source comments. It looks pretty straightforward to configure the system for separate I/D. Is there any material difference between doing it at install time vs having run on 11/40 for a while and moving the disk over to the 11/45 later?
On a related note, how difficult is it to copy the system from rk to hp? I know I can rebuild, but I’m sure there’s a quicker/easier method...
> That said if you running the simh I would recommend going all the way to an 11/70 configuration because you can set it up for 4M of main memory.
Maybe this will be the next upgrade :).
next prev parent reply other threads:[~2018-12-31 3:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 2:25 Will Senn
2018-12-31 2:43 ` Clem cole
2018-12-31 3:31 ` Will Senn [this message]
2018-12-31 14:55 ` Clem Cole
2018-12-31 15:05 ` ron
2018-12-31 15:53 ` Clem Cole
2018-12-31 17:30 ` ron
2018-12-31 18:20 ` Paul Winalski
2018-12-31 23:36 ` [TUHS] Useful Unix tools + Usenix tapes Warren Toomey
2019-01-01 1:30 ` Clem cole
2019-01-01 1:58 ` Clem cole
2019-01-01 2:00 ` Clem cole
2019-01-01 2:08 ` Nigel Williams
2019-01-01 2:17 ` Warren Toomey
2019-01-01 8:18 ` Warren Toomey
2018-12-31 2:47 ` [TUHS] Upgrading from 11/40 to 11/45 in Unix v6 Clem cole
2018-12-31 3:08 ` Will Senn
2018-12-31 3:15 ` Clem cole
2018-12-31 6:51 Noel Chiappa
2018-12-31 15:06 ` Will Senn
2018-12-31 15:50 ` Clem Cole
2018-12-31 15:53 ` Warner Losh
2018-12-31 15:59 ` Clem Cole
2019-01-01 1:56 ` Eric Allman
2018-12-31 17:20 Noel Chiappa
2018-12-31 18:38 Noel Chiappa
2018-12-31 20:06 ` Warner Losh
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=A81530EA-2DF1-4BFA-93AE-6666E9C67E13@gmail.com \
--to=will.senn@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@tuhs.org \
/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).