From: "John P. Linderman" <jpl.jpl@gmail.com>
To: William Pechter <pechter@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] UNIX System names - since UNIX was a Trademark
Date: Fri, 31 Aug 2018 20:10:59 -0400 [thread overview]
Message-ID: <CAC0cEp_7jwxdywgs8es0qSBJty3D92BM192-coNEz-EuVQi+pg@mail.gmail.com> (raw)
In-Reply-To: <3b0a2895-4a6b-48c4-87da-cc1018d7b665.maildroid@localhost>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
We always referred to HP-UX as "H-Pukes".
On Fri, Aug 31, 2018 at 11:17 AM, William Pechter <pechter@gmail.com> wrote:
> UNIX is a trademark of AT&T
> AT&T is a modem test command.
>
> -----Original Message-----
> From: Clem Cole <clemc@ccc.com>
> To: Dave Horsfall <dave@horsfall.org>
> Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
> Sent: Fri, 31 Aug 2018 10:42
> Subject: Re: [TUHS] UNIX System names - since UNIX was a Trademark
>
> Dave Horsfall's comment about AIX made me think. The joker in me has
> always been impressed by how marketing people 'missed' the obvious
> pronunciations that would lead to serious
>
> jokes.
> Some of the more memorable ones from the UNIX world that I knew: AIX ->
> "aches", CRDS -> "cruds", HP-UX -> HP "yucks" and "hockey pucks" and my
> favorite: RHEL -> "our hell"
>
> I bet there are more and others I did know/consider ;-)
>
> That said, I did hear a pro-VMS person in ZKO (*i.e.* a DECie) once tried
> refered to "DEC Ultrix" as Dirty Tricks, but I never heard that one take
> off/be repeated outside of ZKO.
>
> For history we probably should try to collect them, although I fear the
> context of the joke in the future may be lost.
>
>
> Clem
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 1939 bytes --]
next prev parent reply other threads:[~2018-09-01 0:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:25 [TUHS] cat -v and other complaints Clem Cole
2018-08-29 22:34 ` Dave Horsfall
2018-08-29 23:36 ` Larry McVoy
2018-08-30 1:14 ` Clem cole
2018-08-30 1:15 ` Clem cole
2018-08-30 2:43 ` Kevin Bowling
2018-08-30 2:59 ` George Michaelson
2018-08-31 0:27 ` Dave Horsfall
2018-08-31 0:41 ` Dan Cross
2018-08-31 1:58 ` Larry McVoy
2018-08-31 11:38 ` ron
2018-08-31 14:41 ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13 ` Eric Wayte
2018-08-31 15:17 ` William Pechter
2018-08-31 15:25 ` Clem Cole
2018-09-01 0:10 ` John P. Linderman [this message]
2018-09-01 0:18 ` ron
2018-09-01 0:55 ` Nemo
2018-09-01 7:37 ` Dave Horsfall
2018-09-01 13:54 ` Nemo
2018-09-01 17:03 ` Paul Winalski
2018-09-03 1:14 ` Robert Brockway
2018-09-30 20:57 ` Lyndon Nerenberg
2018-10-01 16:26 ` Paul Winalski
2018-09-01 0:00 ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01 3:37 ` Andrew Warkentin
2018-09-03 18:04 ` Cág
2018-09-03 18:11 ` Kurt H Maier
2018-09-03 18:56 ` Cág
2018-09-04 6:10 ` Andy Kosela
2018-09-04 6:41 ` ron minnich
2018-09-04 9:34 ` Andy Kosela
2018-09-04 10:23 ` Dan Cross
2018-09-04 14:22 ` ron minnich
2018-09-06 20:02 ` Andy Kosela
2018-09-06 20:49 ` ron minnich
2018-09-06 21:55 ` Andy Kosela
2018-09-07 1:59 ` Dan Cross
2018-09-07 4:40 ` Andy Kosela
2018-09-30 21:32 ` Lyndon Nerenberg
2018-09-03 20:08 ` Bakul Shah
2018-09-03 20:41 ` Kurt H Maier
2018-09-03 21:46 ` Bakul Shah
2018-09-04 0:52 ` Kurt H Maier
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=CAC0cEp_7jwxdywgs8es0qSBJty3D92BM192-coNEz-EuVQi+pg@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=pechter@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).