From: James Frew <frew@ucsb.edu>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Capitalization question: UNIX/Unix and MULTICS/Multics?
Date: Wed, 11 May 2022 11:08:28 -0700 [thread overview]
Message-ID: <8dae07f5-7782-7e56-85c7-8d19fea8349b@ucsb.edu> (raw)
In-Reply-To: <CAEoi9W7c0QuqF2wQTj9CoWw+=zsDLwPXXn7Arop8BwH_k+Jsmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
The Book (https://mitpress.mit.edu/books/multics-system - I've always
assumed this is the canonical non-mimeographed reference) uses "Multics".
/Frew
On 2022-05-11 10:13, Dan Cross wrote:
>
> This is tangentially related to Unix, and came up randomly at work
> yesterday.
>
> In Kernighan's Unix memoir, on page 9, he touches briefly on the
> typography of "Unix":
>
> "(Multics was originally spelled MULTICS, but the lower-case version
> is less visually jarring; as with UNIX versus Unix and some other
> all-caps words, I’ll use the nicer-looking form even though it’s not
> historically accurate.)"
>
> Here, he is talking about interning at MIT in 1966. bwk would
> certainly know better than me, but I can find no historical reference
> to this "MULTICS" spelling; is anyone familiar with that? The earliest
> reference I can find (the 1965 paper from the FJCC:
> https://dl.acm.org/doi/pdf/10.1145/1463891.1463912) uses the more
> "Multics" styling, but it may have been typeset later.
>
> Alternatively, could someone send me Brian's email address?
>
> - Dan C.
>
[-- Attachment #2: Type: text/html, Size: 2689 bytes --]
next prev parent reply other threads:[~2022-05-11 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 17:13 Dan Cross
2022-05-11 18:08 ` James Frew [this message]
2022-05-11 19:57 Noel Chiappa
2022-05-11 23:47 Douglas McIlroy
2022-05-12 0:34 ` Dan Cross
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=8dae07f5-7782-7e56-85c7-8d19fea8349b@ucsb.edu \
--to=frew@ucsb.edu \
--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).