The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cym224@gmail.com (Nemo)
Subject: [TUHS] And now ...
Date: Mon, 11 Jul 2016 08:07:17 -0400	[thread overview]
Message-ID: <CAJfiPzw0z6rcQXHvgu8Dne29hYyxYSA0LBD_pMOCsTbMTzL+SA@mail.gmail.com> (raw)
In-Reply-To: <20160711120047.GA7921@minnie.tuhs.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

On 11 July 2016 at 08:00, Warren Toomey <wkt at tuhs.org> wrote:
> after the brief but illuminating detour on character sets and the
> evolution of human languages, we now return you to the Unix Heritage
> mailing list :-)
>
> [ Please! ]
>
> Cheers, Warren

ACK but I cannot resist one last item:  UNIX in the OED.

Additions 1993

Unix, n. Computing.
(ˈjuːnɪks)
Also UNIX.

[f. as a play on the earlier *Multics n., with uni- one for multi-
many (after the relative compactness of the newer system) and with
phonetic respelling of -ics as -ix.]

A proprietary name for a multi-user operating system orig. designed
for use with minicomputers.

   1973 Bell Lab. Rec. LI. 200 Some of the concepts, especially for
file-handling, appeared in a time-shared operating system called UNIX,
which was designed and implemented at Bell Labs.    1978 Bell Syst.
Techn. Jrnl. LVII. 1991 C‥is sufficiently expressive and efficient to
have completely displaced assembly language programming on UNIX.
1983 Austral. Personal Computer Aug. 66/2 Xenix, the Microsoft
implementation of Unix disk operating systems for microcomputers.
1985 Official Gaz. (U.S. Patent Office) 29 Oct. tm63/1 UNIX‥.For
computer programs‥. First use 12-14-1972.    1986 Trade Marks Jrnl. 5
Mar. 522/2 Unix‥Computer programmes, computing apparatus; [etc.]
1989 N.Y. Times 25 Oct. d1/4 A wider industry agreement on a single
Unix standard would also increase the possibility that Unix will be
widely adopted in the business computer market.


      reply	other threads:[~2016-07-11 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 12:00 Warren Toomey
2016-07-11 12:07 ` Nemo [this message]

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=CAJfiPzw0z6rcQXHvgu8Dne29hYyxYSA0LBD_pMOCsTbMTzL+SA@mail.gmail.com \
    --to=cym224@gmail.com \
    /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).