From: Clem cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Upgrading from 11/40 to 11/45 in Unix v6
Date: Sun, 30 Dec 2018 21:47:19 -0500 [thread overview]
Message-ID: <7B94CDEC-8E1B-4546-B8C8-A2DE09A94AED@ccc.com> (raw)
In-Reply-To: <D905D4FB-5DEE-4D30-829B-7079CE50D8B4@gmail.com>
One other thought. The basic v6 has and RP driver in it. I’ve forgotten if RP06 was in there but the RP04 certainly was by then. Check the driver rp.c to see what is configured. But either way you should configure the system to use the largest drive v6 has.
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Dec 30, 2018, at 9:25 PM, Will Senn <will.senn@gmail.com> wrote:
>
> Dear Unix Enthusiasts,
>
> We are seriously considering upgrading our PDP 11/40 clone (SIMH), to a PDP 11/45 (preferably another SIMH) for our Unix v6 installation. Our CEO was traveling and met a techie in first class (seriously, first class?) who told him that we needed one. I thought I had better ask some folks who have gone before about it before we jumped on the bandwagon. By way of background, Our install is pretty small with a few rk’s and 256K of ram along with a few standard peripherals, and some stuff our oldtimers refuse to part with (papertape, card punch, etc). It has fairly low utilization - a developer logs in and writes code every few days and the oldtimers hunt the wumpus and play this weird Brit game about cows. It could be considered a casual development and test environment and an occasional gaming console.
>
> Here is what I would like to know that I think y’all might be particularly equipped to answer:
>
> 1. Are there any v6 specific concerns about upgrading?
>
> 2. Why should we consider taking the leap to the 11/45? Everything seems to work fine now.
>
> 3. If we jump in and do the upgrade, how can we immediately recognize what has changed in the environment? I.e what are some things that we can now do that we couldn’t do before?
>
> 4. If we just insert our current diskpacks into the new system, will it just boot and work? Or what do we need to before/after booting to prepare/respond to the new system?
>
> 5. Is 256K enough memory or what configuration do y’all recommend?
>
> 6. Is there anything else we need to know about?
>
> Regards,
>
> Will
>
> Sent from my iPhone
next prev parent reply other threads:[~2018-12-31 2:47 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
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 ` Clem cole [this message]
2018-12-31 3:08 ` [TUHS] Upgrading from 11/40 to 11/45 in Unix v6 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=7B94CDEC-8E1B-4546-B8C8-A2DE09A94AED@ccc.com \
--to=clemc@ccc.com \
--cc=tuhs@tuhs.org \
--cc=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).