From: Kevin Bowling <kevin.bowling@kev009.com>
To: Dave McGuire <mcguire@lssmuseum.org>, Tom Lyon <pugs@ieee.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Unix, IBM, 370
Date: Sat, 2 Nov 2019 18:02:44 -0700 [thread overview]
Message-ID: <CAK7dMtCGq+waap+fM5OP0Ff=ScmedvAZ3wRzyU-tjyBiMicpEA@mail.gmail.com> (raw)
In-Reply-To: <CAAOGWQhAnQvU6ro_sdj1iP0eRk5uWkUKxHebdwFfUsr8dFJ9zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
Tom,
In case you ever pass through Pittsburgh, Dave has 370s of various flavor
and some pdp-11s. I’d be pretty entertained trying to get this running in
some capacity on real iron in the future when I visit Dave.
I may put out another form to see if people would be interested in doing an
event there.
In the meantime thanks for recovering and posting this.
Regards,
Kevin
On Wed, Oct 30, 2019 at 8:57 PM Tom Lyon <pugs@ieee.org> wrote:
> Hi, folks. Tom Lyon here - this UNIX 370 stuff was recovered by Stephen at
> LCM+L from DECtapes that I've had sitting around for 40+ years.
> You can read all about the Princeton/Amdahl project here:
> https://akapugs.blog/2018/05/12/370unixpart1/
>
> If anyone wants to get serious with the code, you'll need Hercules with a
> VM/370 image as well as a PDP-11 emulator running V6. There's not a lot
> beyond the kernel, I got the shell working enough to prove that fork
> worked, and then ran out of steam because of the awful communication
> problems between the PDP and the IBM. [ But that was my start as a
> networking guy ]. I personally haven't had time to do anything with the
> recovered bits.
>
> I've been lurking on TUHS for a while - a special Hi to Ken Thompson and
> Steve Johnson. I owe a lot to each of them. Read about my summer at Bell
> with the Interdata 8/32 here:
> https://akapugs.blog/2018/05/16/belllabspart1/
>
> On Mon, Oct 28, 2019 at 9:04 PM Warren Toomey <wkt@tuhs.org> wrote:
>
>> All, the second Unix artifact that I've been waiting to announce has
>> arrived. This time the LCM+L is announcing it. It's not the booting PDP-7.
>>
>> So, cast your eyes on https://www.tuhs.org/Archive/Distributions/IBM/370/
>>
>> Cheers, Warren
>>
>> P.S Thanks to Stephen Jones for this as well.
>>
>
>
> --
> - Tom
>
[-- Attachment #2: Type: text/html, Size: 3232 bytes --]
prev parent reply other threads:[~2019-11-03 1:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 4:04 Warren Toomey
2019-10-29 5:07 ` Warner Losh
2019-10-29 5:19 ` Adam Thornton
2019-10-29 7:14 ` SPC
2019-10-29 15:10 ` Warner Losh
2019-10-29 15:22 ` SPC
2019-11-05 4:12 ` Grant Taylor via TUHS
2019-10-31 3:56 ` Tom Lyon
2019-10-31 4:16 ` Larry McVoy
2019-10-31 7:51 ` arnold
2019-10-31 13:51 ` Tom Lyon
2019-10-31 14:10 ` arnold
2019-10-31 14:22 ` Larry McVoy
2019-10-31 14:24 ` SPC
2019-10-31 15:31 ` Charles H Sauer
2019-11-01 16:52 ` Clem Cole
2019-11-03 7:05 ` arnold
2019-11-03 21:16 ` Clem Cole
2019-11-04 14:43 ` arnold
2019-11-05 14:15 ` Clem Cole
2019-10-31 15:10 ` Heinz Lycklama
2019-11-01 16:40 ` Clem Cole
2019-10-31 8:09 ` SPC
2019-10-31 15:12 ` Warner Losh
2019-11-03 1:02 ` Kevin Bowling [this message]
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='CAK7dMtCGq+waap+fM5OP0Ff=ScmedvAZ3wRzyU-tjyBiMicpEA@mail.gmail.com' \
--to=kevin.bowling@kev009.com \
--cc=mcguire@lssmuseum.org \
--cc=pugs@ieee.org \
--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).