The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] FORTRAN
Date: Wed, 21 Mar 2018 14:57:59 -0700	[thread overview]
Message-ID: <CANV78LRPScZsTB5D8SRfuwp+5ChBs_vy_BjkWek2CPvDZmFQmg@mail.gmail.com> (raw)
In-Reply-To: <20180321145141.EF02718C088@mercury.lcs.mit.edu>

On Wed, Mar 21, 2018 at 7:51 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

>     > From: "Steve Johnson"
>
> So, I have this persistent memory that I read, in some early Multics
> (possibly
> CTSS, but ISTR it was Multics) document, a footnote explaining the origin
> of
> the term 'daemon'. I went looking for it, but couldn't find it in a 'quick'
> scan.
>

From multician.org: http://multicians.org/mgd.html:

" daemon

A beneficent spirit. A process, not associated with a human operator, that
runs all the time and waits for requests to do something for a user. This
term is respectable English; the application to computer processes is
usually credited to M. J. Bailey, working on the design of CTSS in the
early 60s.

[JHS] "I'm working from memory here, but I think this is the story.
Although the word 'process' wasn't in the vocabulary yet, we had just
figured out that what one would now call 'system processes' were a solution
to several problems, and we were looking for a good label for them. A
British gentleman named Michael (Mick) Bailey, working on the CTSS
programming staff at MIT, suggested the word 'daemon' and quoted the OED in
support of both the meaning and spelling. Bailey's etymology was so
impeccable that questions as to whether the spelling should be simplified
to 'demon' went on for only about 30 seconds. On both CTSS and Multics, the
documentation and the process names use the spelling 'daemon.' I suspect
that the date on the memo that first used the term would be in 1962 or
1963."(note to Kirk McKusick, 24 Aug 1988)"

-- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180321/0af1ebd2/attachment.html>


  reply	other threads:[~2018-03-21 21:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 14:51 Noel Chiappa
2018-03-21 21:57 ` Charles Anthony [this message]
     [not found] <mailman.48.1521640130.3788.tuhs@minnie.tuhs.org>
2018-03-21 22:58 ` Johnny Billquist
  -- strict thread matches above, loose matches on Subject: below --
2018-03-19 15:55 [TUHS] RIP John Backus Clem Cole
2018-03-19 16:58 ` [TUHS] FORTRAN Steve Johnson
2018-03-19 17:32   ` Jon Forrest
2018-03-20 17:42     ` Paul Winalski
2018-03-20 17:47       ` George Michaelson
2018-03-19 18:47   ` Larry McVoy
2018-03-20 18:15   ` Dan Cross
2018-03-20 19:55     ` Ron Natalie
2018-03-20 20:21       ` Paul Winalski
2018-03-20 20:27         ` Warner Losh
2018-03-21  8:10         ` Peter Jeremy
2018-03-21 20:56           ` Ron Natalie
2018-03-21 21:15         ` Dennis Boone
2018-03-20 21:36       ` Clem Cole
2018-03-20 21:59         ` Ron Natalie
2018-03-20 23:00         ` Bakul Shah
2018-03-21 13:48         ` Paul Winalski
2018-03-21 20:55           ` Ron Natalie

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=CANV78LRPScZsTB5D8SRfuwp+5ChBs_vy_BjkWek2CPvDZmFQmg@mail.gmail.com \
    --to=charles.unix.pro@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).