From: Clem Cole <clemc@ccc.com>
To: Tom Lyon <pugs78@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: "UNIX/370: A Feasibility Study" by W.A. Felton (Bell TM)
Date: Wed, 19 Jul 2023 12:50:56 -0400 [thread overview]
Message-ID: <CAC20D2Nud_HNVFgif4gjzv8B+_y=LzObBy2R64eTYryjxiL4uQ@mail.gmail.com> (raw)
In-Reply-To: <CANxB0bQFg3Z9V9w-84_hUFQ_2YQWnhipeW8s_i3uCBU_+bd=7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
T'was afraid of that. Shame really.
Tx
Clem
ᐧ
On Wed, Jul 19, 2023 at 12:12 PM Tom Lyon <pugs78@gmail.com> wrote:
> I have no knowledge of any preserved UNIX/370 stuff from Bell.
>
> On Wed, Jul 19, 2023 at 9:09 AM Clem Cole <clemc@ccc.com> wrote:
>
>> Tom - do you know if any of the technical work for this survived? As an
>> old TSS hacker, I'd love to see this run again on Hercules.
>>
>> Also, any idea if either of these documents in the references still
>> exist: B. G. Prieve, "UNIX/370 - A Proposal,” MF 8224-780928.01 and S.
>> L. Gaede, "High Capacity UNIX - Exploration of UNIX/370," MF 5521-780901.01.
>> ᐧ
>>
>> On Tue, Jul 18, 2023 at 8:58 PM Tom Lyon <pugs78@gmail.com> wrote:
>>
>>> A friend found this doc which as far as I can tell is not online
>>> anywhere yet. Preliminary sketch for the UNIX/370 effort at Bell based on
>>> TSS/370. Apparently started at Holmdel, I had always thought Indian Hill.
>>>
>>>
>>> https://drive.google.com/file/d/1zrnKJ7fT1yrt_9r8QJHtZm7cI9EQEw76/view?usp=sharing
>>>
>>> Please archive!
>>>
>>
[-- Attachment #2: Type: text/html, Size: 3448 bytes --]
next prev parent reply other threads:[~2023-07-19 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 0:58 [TUHS] " Tom Lyon
2023-07-19 16:08 ` [TUHS] " Clem Cole
2023-07-19 16:12 ` Warner Losh
2023-07-19 16:12 ` Tom Lyon
2023-07-19 16:50 ` Clem Cole [this message]
2023-07-19 21:52 ` Marc Donner
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='CAC20D2Nud_HNVFgif4gjzv8B+_y=LzObBy2R64eTYryjxiL4uQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=pugs78@gmail.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).