The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Paco López" <pc.lpz.snchz@gmail.com>
Cc: The Eunuchs Historical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] UNIX or unix
Date: Sat, 9 Nov 2019 19:43:59 +0000	[thread overview]
Message-ID: <CAG0r6upi+d2QfZOo=pdVVbnf0HVqc2meoZYC5LKX_77FQ1Zg7w@mail.gmail.com> (raw)
In-Reply-To: <2ce9495a-b877-91be-ff5b-5516b8269562@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

An excerpt from The Jargon File:

Some people are confused over whether this word is appropriately ‘UNIX’ or
‘Unix’; both forms are common, and used interchangeably. Dennis Ritchie
says that the ‘UNIX’ spelling originally happened in CACM's 1974 paper The
UNIX Time-Sharing System because “we had a new typesetter and troff had
just been invented and we were intoxicated by being able to produce small
caps.” Later, dmr tried to get the spelling changed to ‘Unix’ in a couple
of Bell Labs papers, on the grounds that the word is not acronymic. He
failed, and eventually (his words) “wimped out” on the issue. So, while the
trademark today is ‘UNIX’, both capitalizations are grounded in ancient
usage; the Jargon File uses ‘Unix’ in deference to dmr's wishes.

at: http://catb.org/jargon/html/U/Unix.html

El sáb., 9 nov. 2019 a las 17:28, Nemo Nusquam (<cym224@gmail.com>)
escribió:

> I was reading the comments on Hackaday on UNIX at 50
> (https://hackaday.com/2019/11/05/will-the-real-unix-please-stand-up/).
> As expected, a lot of manure but some interesting comments from
> seemingly knowledgeable people.
>
> One comment
> (
> https://hackaday.com/2019/11/05/will-the-real-unix-please-stand-up/#comment-6192977),
>
> from a DDS, stated that (s)he worked at The Bell and they wrote it
> "unix" (lower-case) to distinguish it from MULTICS.  Anyone care to
> comment on this?
>
> N.
>

[-- Attachment #2: Type: text/html, Size: 2110 bytes --]

  reply	other threads:[~2019-11-09 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 17:20 Nemo Nusquam
2019-11-09 19:43 ` Paco López [this message]
2019-11-09 20:36 ` Derrik Walker v2.0
2019-11-09 21:05   ` Mary Ann Horton
2019-11-09 21:23     ` Clem Cole
2019-11-10  0:07       ` Steve Johnson
2019-11-11  8:07         ` Dr Iain Maoileoin
2019-11-11 19:58           ` Dave Horsfall
2019-11-09 19:39 Noel Chiappa

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='CAG0r6upi+d2QfZOo=pdVVbnf0HVqc2meoZYC5LKX_77FQ1Zg7w@mail.gmail.com' \
    --to=pc.lpz.snchz@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).