From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 52eceb77 for ; Sat, 23 Nov 2019 12:52:24 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id C54239C164; Sat, 23 Nov 2019 22:52:23 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E01F193D74; Sat, 23 Nov 2019 22:51:49 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="JI1eTQ5F"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id BE08F93D74; Sat, 23 Nov 2019 22:51:46 +1000 (AEST) Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com [209.85.222.177]) by minnie.tuhs.org (Postfix) with ESMTPS id 2BB3C93D71 for ; Sat, 23 Nov 2019 22:51:46 +1000 (AEST) Received: by mail-qk1-f177.google.com with SMTP id v23so894424qkg.2 for ; Sat, 23 Nov 2019 04:51:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xSIwvt+uSb2ZYKFnIn/TijjBdVjMKkXBIZjMT9s1K5I=; b=JI1eTQ5F5NXJNKHc35YLjIkAVHPh5A1ZP+oHcN/6e9JSBMaf0BuD5kSsG1jqgNiKBA /1fTi5MSW/pkLc7mpmL/Wj+2ZqYuJcWuoAaUFswhbCu8S4/FT0UN4Uf6asMa0lO0vPIH UAXryXweaibTbgoY5Ju0FH+WXzCbGYld/ydZA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xSIwvt+uSb2ZYKFnIn/TijjBdVjMKkXBIZjMT9s1K5I=; b=di9ehh0ORphKBCvSzXr2AS22YDiaM5iSy+XwMDPQAdbGZ2hVF3YM97j2xCAqcVHhlj eEDzoPy6qE4ww61splE/6wvdF4B8qAECCf7wmJeHU/yBEE1DAm3zeWUBlQaW704SJ1+g LMztENc1Y/taiaaJeOx9LXmbvBWhY2dOCnMzwnUBe8eJXw8jYLDj0BaUaPKmmhOXDutO hmRf5k3dDnnSVpfigRr12VtZXXWfw2MwJfYblb+djH0ToUI3Ja+Q7inonxorwNndDrQP GdczH3CDjHtqTKDelz7XI5xbyy+GdgjbNekDdjDadNu6YfA+5hR9tft/yooIe5TqKk66 YOcQ== X-Gm-Message-State: APjAAAXNOArrbWLlCrrQ5Y06I4CGCCxMQB7ODHGSpY4iwnzeHKGygMaL 77QYst5UdxE4Jj2s+1kyQdvm9Two7zLf9pWpipUytw== X-Google-Smtp-Source: APXvYqyTXTm6Etm7ItIhhN+DdM7SWPslB+7g26fmYxu/xPYsP/H/ILCdQRpVDOT5h0MoPJgTB14+0wSAc2m6Pyfl8Ao= X-Received: by 2002:a37:4b97:: with SMTP id y145mr17647014qka.133.1574513504987; Sat, 23 Nov 2019 04:51:44 -0800 (PST) MIME-Version: 1.0 References: <20191121195327.0C30918C080@mercury.lcs.mit.edu> In-Reply-To: From: Clem Cole Date: Sat, 23 Nov 2019 07:51:33 -0500 Message-ID: To: Gregg Levine Content-Type: multipart/alternative; boundary="00000000000028c30d059802fe46" Subject: Re: [TUHS] AOS and IBM/RT [Re: Amdahl UTS, AIX/370, AIX/ESA X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000028c30d059802fe46 Content-Type: text/plain; charset="UTF-8" No I don't remember Many details on this one as I did not do it. As I said I think it was a Burness message in the graphics subsystem, but I cannot swear to it. I just remember the time frame and what happened. Roger Gourd's reaction was priceless when Mr Potatohead called us on it. It was one of the times I really learned to respect Roger. That said, Ill see what I can find by asking around. On Fri, Nov 22, 2019 at 11:41 PM Gregg Levine wrote: > 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 wrote: > > > > > > > > On Thu, Nov 21, 2019 at 2:53 PM Noel Chiappa > 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 ;-) > -- Sent from a handheld expect more typos than usual --00000000000028c30d059802fe46 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No I don't remember Many details on this one as = I did not do it.=C2=A0 As I said I think it was a Burness message in the gr= aphics subsystem, but I cannot swear to it. =C2=A0 =C2=A0 I just remember t= he time frame and what happened.=C2=A0 Roger Gourd's reaction was price= less when Mr Potatohead called us on it.=C2=A0 It was one of the times I re= ally learned to respect Roger. =C2=A0

That said, Ill see what I can find by asking around.=C2=A0

On Fri, Nov 22, 2019 at 11:41 PM Gregg Levine <gregg.drwho8@gmail.com> wrote:
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 langu= age.
-----
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> wro= te:
>>
>>=C2=A0 =C2=A0 =C2=A0> From: Arnold Robbins
>>
>>=C2=A0 =C2=A0 =C2=A0> The Bell Labs guys in some ways were too.<= br> >>
>> 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.=C2= =A0 =C2=A0We were chasing a rare event (as I recall it was when we first we= re debugging Multiprocessor stuff and it a lock order problem).=C2=A0 But w= e could not get the customers to tell us about what was happening, since th= e 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 bu= nch of information.=C2=A0 Sure enough this was noticed, customer stopped, w= e got the needed data, as they reported the error.=C2=A0 But it was a high = visibility customer, so the president (Mr. Potatohead) got a phone call.=C2= =A0 =C2=A0Fossil (our boss) made us swear it would never happen again, but = he defended us to the President.=C2=A0 =C2=A0We found the bug ;-)
--
Sent from a handheld expect more typos t= han usual
--00000000000028c30d059802fe46--