The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dr Iain Maoileoin <iain@csp-partnership.co.uk>
To: Steve Johnson <scj@yaccman.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] UNIX or unix
Date: Mon, 11 Nov 2019 08:07:11 +0000	[thread overview]
Message-ID: <9893DFE0-5D7A-4733-846D-23C0106B2DBA@csp-partnership.co.uk> (raw)
In-Reply-To: <dd12696689734189ef3ab82609f441db99b2c3ab@webmail.yaccman.com>

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


> On 10 Nov 2019, at 00:07, Steve Johnson <scj@yaccman.com> wrote:
> 
> I remember a story I heard second hand.   The Bell System had so many acronyms that they published  yearly a small book with all the acronyms in the Bell System.   Somebody (Ken?, Doug?) got a call one year that they wanted to include UNIX in the book, so would we please tell them what UNIX stood for.   The reply was that UNIX was not an acronym.  So the caller said: "OK.  We won't put it in the book..."
> 
> Steve
> 
> 
> 
> ----- Original Message -----
> From: "Clem Cole" <clemc@ccc.com>
> To:"Mary Ann Horton" <mah@mhorton.net>
> Cc:<tuhs@minnie.tuhs.org>
> Sent:Sat, 9 Nov 2019 16:23:04 -0500
> Subject:Re: [TUHS] UNIX or unix
> 
> 
> In fact ATT legal had a document they sent to all commercial licensees around 1980 on proper use of the name.  I wonder if I still have/can find a copy.  But the lawyers were pretty clear. It was UNIX with ™ and later the R with a circle around beside the all caps letters after they registered it.  
I was not just commercial licensees.  I remember seeing a copy of that letter.  We were a Scottish University who had a legit tape sent from AT&T/Bell Labs for academic use.

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

  reply	other threads:[~2019-11-11 10:02 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
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 [this message]
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=9893DFE0-5D7A-4733-846D-23C0106B2DBA@csp-partnership.co.uk \
    --to=iain@csp-partnership.co.uk \
    --cc=scj@yaccman.com \
    --cc=tuhs@minnie.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).