From: Marc Donner <marc.donner@gmail.com>
To: John Cowan <cowan@ccil.org>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bringing a Chainsaw
Date: Sat, 10 Dec 2022 04:10:26 -0500 [thread overview]
Message-ID: <CALQ0xCDhcBbN7E+bKmyNKk=N6qkQZA2=gG3NQkXFCdUTUp_96Q@mail.gmail.com> (raw)
In-Reply-To: <CAD2gp_RTt6B=uQjDm52v14jGpa=_t5ATcEVLD7euvUYd6T2e3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Interesting. I never heard “branch to Fishkill” until today.
On Sat, Dec 10, 2022 at 1:54 AM John Cowan <cowan@ccil.org> wrote:
>
>
> On Fri, Dec 9, 2022 at 4:50 PM Marc Donner <marc.donner@gmail.com> wrote:
>
> (Recently I mentioned to Doug McIlroy that I had infiltrated IBM East
>> Fishkill, reputedly one of the largest semiconductor fabs in the world,
>> with UNIX back in the 1980s. He suggested that I write it up and share it
>> here, so here it is.)
>>
>
> Some editions of the Jargon File contain an entry for _branch to
> Fishkill_, defined as "Any unexpected jump in a program that produces
> catastrophic or just plain weird results" and attributed to IBM. Are you
> familiar with this term? Did it have a specific reference within IBM?
>
> In any case, this is a great story!
>
--
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>
[-- Attachment #2: Type: text/html, Size: 2327 bytes --]
next prev parent reply other threads:[~2022-12-10 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 21:49 [TUHS] " Marc Donner
2022-12-09 22:49 ` [TUHS] " Rich Morin
2022-12-10 6:54 ` John Cowan
2022-12-10 9:10 ` Marc Donner [this message]
2022-12-10 16:54 ` Adam Sampson
2022-12-10 17:15 ` Marc Donner
2022-12-11 22:23 ` Marc Donner
2022-12-11 22:47 ` John Cowan
2022-12-11 22:50 ` Marc Donner
2022-12-12 1:32 ` John Cowan
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='CALQ0xCDhcBbN7E+bKmyNKk=N6qkQZA2=gG3NQkXFCdUTUp_96Q@mail.gmail.com' \
--to=marc.donner@gmail.com \
--cc=cowan@ccil.org \
--cc=douglas.mcilroy@dartmouth.edu \
--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).