The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Gregg Levine <gregg.drwho8@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] AOS and IBM/RT [Re: Amdahl UTS, AIX/370, AIX/ESA
Date: Fri, 22 Nov 2019 23:40:29 -0500	[thread overview]
Message-ID: <CAC5iaNFu2R+FzLjvkdcnim3KPcN+Zw9vqSVrXBZb80D25Uq4Wg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P7NkytxA8gmKdpkpHfm6D1RXuBCp2tabj6ieRkd7EKCQ@mail.gmail.com>

Hello!
Clem by chance do you remember what the error message response was? It
would be interesting to see what phrases were used. For example, on
the IBM side of things, a fellow Adam and I both know, coded an entire
application so that everything it said and did would be in Klingonese.
No I do not remember which one it was, and what have you, I only
remember it surfacing during his talk at the IBM offices here in town,
during the early years of running Tux on the IBM S/390 systems.

I also find it strange that sometimes even Google is thinking in that language.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature fought the Time Wars, time and again."

On Thu, Nov 21, 2019 at 3:09 PM Clem Cole <clemc@ccc.com> wrote:
>
>
>
> On Thu, Nov 21, 2019 at 2:53 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>>
>>     > From: Arnold Robbins
>>
>>     > The Bell Labs guys in some ways were too.
>>
>> And there's the famous? story about the Multics error messages in Latin,
>> courtesty of Bernie Greenberg. One actually appeared at a customer site once,
>> whereupon hilarity ensued.
>
> One of my favorite stories of the same vein was a masscomp story.   We were chasing a rare event (as I recall it was when we first were debugging Multiprocessor stuff and it a lock order problem).  But we could not get the customers to tell us about what was happening, since the system recovered quickly, but we might kill a process. We had done a few releases and make a few changes but we could never reproduce it.
>
> I never knew who it was but someone ??Jack Burness if I had to guess?? put out a patch with a couple of error messages in Klingon and dumped a bunch of information.  Sure enough this was noticed, customer stopped, we got the needed data, as they reported the error.  But it was a high visibility customer, so the president (Mr. Potatohead) got a phone call.   Fossil (our boss) made us swear it would never happen again, but he defended us to the President.   We found the bug ;-)

  reply	other threads:[~2019-11-23  4:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:53 Noel Chiappa
2019-11-21 20:08 ` Clem Cole
2019-11-23  4:40   ` Gregg Levine [this message]
2019-11-23 12:51     ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2019-11-06 20:31 Pat Barron
2019-11-06 20:28 Pat Barron
2019-11-03 21:05 [TUHS] " Kevin Bowling
2019-11-04  3:39 ` Gregg Levine
2019-11-05 17:30   ` Clem Cole
2019-11-05 22:11     ` [TUHS] one element of one of M factions of N companies [Re: " Charles H Sauer
2019-11-06  0:06       ` Theodore Y. Ts'o
2019-11-06  3:36         ` Charles H. Sauer
2019-11-06  7:59           ` [TUHS] AOS and IBM/RT " SPC
2019-11-06 15:51             ` Charles H Sauer
2019-11-07 22:40               ` Grant Taylor via TUHS
2019-11-08  4:39                 ` Jason Stevens
2019-11-21  6:26             ` Al Kossow
2019-11-21 11:58               ` Dan Cross
2019-11-21 13:07                 ` Brad Spencer
2019-11-21 14:19                   ` Dan Cross
2019-11-21 16:16                     ` Chet Ramey
2019-11-21 20:53                       ` Dan Cross
2019-11-21 16:43                     ` greg travis
2019-11-21 19:41                       ` arnold
2019-11-21 20:21                         ` Jon Steinhart
2019-11-21 17:33                   ` Charles H Sauer
2019-11-21 17:36                     ` Dan Cross
2019-11-21 18:11                     ` Brad Spencer
2019-11-21 17:29                 ` Charles H Sauer
2019-11-22 20:38                 ` Al Kossow

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=CAC5iaNFu2R+FzLjvkdcnim3KPcN+Zw9vqSVrXBZb80D25Uq4Wg@mail.gmail.com \
    --to=gregg.drwho8@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).