From: Clem cole <clemc@ccc.com>
To: Jacob Ritorto <jacob.ritorto@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] System III on 11/34 + rl02
Date: Tue, 23 Oct 2018 23:21:19 -0400 [thread overview]
Message-ID: <34E96877-0DFF-4988-B07D-C0EFA42482C5@ccc.com> (raw)
In-Reply-To: <CAHYQbfDevqhniVE3U3PFtdgb1V4hLz4YWkxendwHWVyXg_PUsQ@mail.gmail.com>
Should be pretty easy particularly since the rl0x is supported in the BSD environment
That said why mess with PWB 3.0 on an 11? BSD 2.9 will be more interesting. Also if you have a 40 class system like the 34 of 34A see if you can find an Able Enable board. The memory will make a huge difference.
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Oct 23, 2018, at 10:59 PM, Jacob Ritorto <jacob.ritorto@gmail.com> wrote:
>
> Hi,
> Was wanting to put together a fully functional (meaning able to load the whole distro and recompile itself) and "reliable" System III machine made of real, albeit not terribly sexy parts. I have (4) working rl02 drives and an 11/34, so I feel like there's a chance it could work. I'll have to build it on the emulator, of course, then vtserver it over to the real hw in chunks.
>
> But the blocker is that System III only supports rl01, not rl02, which kills the 'full distro' prospect.
>
> Would anyone know if it's trivial to modify the source for the rl01 driver to just add double the blocks, thereby supporting rl02? Or am I wildly underestimating the task at hand? Has this been done before? Tips?
>
> thx
> jake
next prev parent reply other threads:[~2018-10-24 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 2:59 Jacob Ritorto
2018-10-24 3:21 ` Clem cole [this message]
2018-10-25 1:22 ` Jacob Ritorto
2018-10-24 11:23 Noel Chiappa
2018-10-25 10:56 Noel Chiappa
2018-10-26 3:27 ` Jacob Ritorto
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=34E96877-0DFF-4988-B07D-C0EFA42482C5@ccc.com \
--to=clemc@ccc.com \
--cc=jacob.ritorto@gmail.com \
--cc=tuhs@minnie.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).