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 22:15:02 -0500 [thread overview]
Message-ID: <E2A667E7-A2D7-4117-85FD-7A44C6546239@ccc.com> (raw)
In-Reply-To: <26F1EC5A-CA9E-4A76-977B-325F2EC0BA88@gmail.com>
Right. hp.c. - RH controller.
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Dec 30, 2018, at 10:08 PM, Will Senn <will.senn@gmail.com> wrote:
>
>
>
>> On Dec 30, 2018, at 8:47 PM, Clem cole <clemc@ccc.com> wrote:
>>
>> 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.
>>
>
> It looks like hp.c is an rp04 driver. That’s an easy upgrade... pretty sure I saw an rp04 laying around somewhere :) I’ll do that one tonight.
>
>
> Thanks,
>
> Will
next prev parent reply other threads:[~2018-12-31 3:15 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 ` [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 [this message]
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=E2A667E7-A2D7-4117-85FD-7A44C6546239@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).