From: "Ronald Natalie" <ron@ronnatalie.com>
To: "Dan Cross" <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
Date: Wed, 01 Mar 2023 02:38:22 +0000 [thread overview]
Message-ID: <em340d09b0-6a9e-47e7-990b-f62f767b2af5@a42f0ac3.com> (raw)
In-Reply-To: <CAEoi9W7kjOZUBYB2fy1+=s111PS6K1V7Uzg2++QTD1gGF0arQQ@mail.gmail.com>
I don’t know. We used it with the Intel i860 processor when we were
doing work for IBM so it was possible that is how we were hooked up with
them.
------ Original Message ------
From "Dan Cross" <crossd@gmail.com>
To "Ronald Natalie" <ron@ronnatalie.com>
Cc "Rich Salz" <rich.salz@gmail.com>; "Dave Horsfall"
<dave@horsfall.org>; "The Eunuchs Hysterical Society" <tuhs@tuhs.org>
Date 2/28/2023 9:35:44 PM
Subject Re: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
>On Tue, Feb 28, 2023 at 9:07 PM Ronald Natalie <ron@ronnatalie.com> wrote:
>>[snip]
>>At least it didn’t come with a prayer book like the Metalware compiler (which really needed all the divine intervention that it could get).
>
>Was that the one that shipped with the IBM RT? Is it just my
>imagination or did some of the error messages contain biblical
>references?
>
> - Dan C.
next prev parent reply other threads:[~2023-03-01 2:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 19:48 [TUHS] " segaloco via TUHS
2023-02-27 3:55 ` [TUHS] " Warner Losh
2023-02-27 10:57 ` Jonathan Gray
2023-02-28 18:59 ` segaloco via TUHS
2023-02-28 19:03 ` Larry McVoy
2023-02-28 19:42 ` Clem Cole
2023-02-28 19:57 ` Bakul Shah
2023-02-28 23:31 ` Dave Horsfall
2023-03-01 0:39 ` Larry McVoy
2023-03-01 1:21 ` Rich Salz
2023-03-01 1:27 ` Warner Losh
2023-03-01 2:07 ` Ronald Natalie
2023-03-01 2:35 ` Dan Cross
2023-03-01 2:38 ` Ronald Natalie [this message]
2023-03-01 3:02 ` [TUHS] IBM RT/PC compilers [was " Charles H. Sauer
2023-03-01 4:02 ` [TUHS] " George Michaelson
2023-03-01 14:12 ` [TUHS] " Chet Ramey
2023-03-02 9:05 ` Jaap Akkerhuis via TUHS
2023-03-02 19:26 ` Clem Cole
2023-03-01 2:50 ` Jonathan Gray
2023-03-01 0:31 ` Jonathan Gray
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=em340d09b0-6a9e-47e7-990b-f62f767b2af5@a42f0ac3.com \
--to=ron@ronnatalie.com \
--cc=crossd@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).