The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Derrik Walker v2.0" <dwalker@doomd.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] UNIX or unix
Date: Sat, 9 Nov 2019 15:36:06 -0500	[thread overview]
Message-ID: <af88bb05-eb1b-811b-7329-5a149fd27c4e@doomd.net> (raw)
In-Reply-To: <2ce9495a-b877-91be-ff5b-5516b8269562@gmail.com>

On 11/9/19 12:20 PM, Nemo Nusquam wrote:
> 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.

It was always my understanding, based totally on hearsay from engineers 
from both Sun and SGI back in my early days with it, UNIX is the OS, 
while unix, or vmunix is the kernel. Unix was deprecated by the time it 
became a real commercial product.

So, right or wrong, I've always used UNIX for the OS, and unix, or 
vmunix as appropriate, to refer to the kernel.

- Derrik

-- 


Derrik Walker v2.0
dwalker@doomd.net
https://www.doomd.net

"Those UNIX guys, they think weird!" -- John C. Dvorak


  parent reply	other threads:[~2019-11-09 20:36 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 [this message]
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=af88bb05-eb1b-811b-7329-5a149fd27c4e@doomd.net \
    --to=dwalker@doomd.net \
    --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).