From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] etymology of cron
Date: Tue, 22 Dec 2015 20:44:07 -0500 (EST) [thread overview]
Message-ID: <20151223014407.07322440AE@lignose.oclsc.org> (raw)
Perhaps Wikipedia would be satisfied if we could get
Ken to write a letter to some current published journal,
saying that he's the one who named cron, he's heard
people are interested in how it got that name, here's
how. We could then cite that as a reference.
On the other hand, this may be an example of the
degree to which one should trust Wikipedia. The
`command run on notice' acronym claim is backed up
by an article from the AUUG (Hi Warren!) Proceedings,
1994, in which the first reference to cron gives
that explanation with no further reference.
If that's the quality of reference they accept, there
is simply no reason to take anything they publish
as gospel. Sorry.
Norman Wilson
Toronto ON
Proud that no one has yet made a spurious Wikipedia
page asserting the etymology of my personal domain
name.
next reply other threads:[~2015-12-23 1:44 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 1:44 Norman Wilson [this message]
2015-12-23 2:07 ` Lyndon Nerenberg
2015-12-23 2:19 ` Milo Velimirovic
2015-12-23 2:27 ` Lyndon Nerenberg
2015-12-23 2:36 ` Greg 'groggy' Lehey
2015-12-23 4:53 ` Larry McVoy
2015-12-23 13:45 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 20:31 Noel Chiappa
2016-01-03 14:26 Noel Chiappa
2016-01-02 23:14 Norman Wilson
2016-01-02 23:18 ` Greg 'groggy' Lehey
[not found] <mailman.1.1451005554.3365.tuhs@minnie.tuhs.org>
2015-12-25 18:41 ` David
2015-12-25 20:46 ` Marc Rochkind
2015-12-25 22:22 ` Greg 'groggy' Lehey
2016-01-02 19:56 ` Marc Rochkind
2016-01-02 21:06 ` Clem Cole
2016-01-02 22:22 ` Greg 'groggy' Lehey
2016-01-03 1:26 ` Ronald Natalie
2016-01-03 10:30 ` Jacob Goense
2016-01-03 15:32 ` Ronald Natalie
2016-01-03 18:00 ` John Cowan
2016-01-03 12:10 ` Jacob Goense
2016-01-03 15:22 ` Ronald Natalie
2016-01-13 19:48 ` Jeremy C. Reed
2016-01-13 20:02 ` Ronald Natalie
2016-01-04 2:26 ` Kurt H Maier
2015-12-23 17:19 Norman Wilson
2015-12-23 19:04 ` John Cowan
2015-12-23 19:41 ` SZIGETI Szabolcs
[not found] <mailman.20.1450886678.3292.tuhs@minnie.tuhs.org>
2015-12-23 17:09 ` Johnny Billquist
2015-12-23 14:38 Noel Chiappa
2015-12-23 18:58 ` John Cowan
2015-12-23 13:36 Norman Wilson
2015-12-23 13:53 ` Clem Cole
2015-12-24 15:01 ` Clem Cole
2015-12-24 15:17 ` John Cowan
2015-12-24 23:05 ` Greg 'groggy' Lehey
2015-12-25 0:52 ` scj
2015-12-25 1:05 ` Larry McVoy
2015-12-25 2:07 ` Greg 'groggy' Lehey
2015-12-25 2:28 ` Dave Horsfall
2015-12-25 16:21 ` Marc Rochkind
2015-12-23 16:04 ` John Cowan
2015-12-23 23:49 ` Greg 'groggy' Lehey
2015-12-23 13:30 Norman Wilson
2015-12-23 0:27 Doug McIlroy
2015-12-23 0:40 ` Greg 'groggy' Lehey
2015-12-23 1:11 ` John Cowan
2015-12-23 1:59 ` Greg 'groggy' Lehey
2015-12-23 2:01 ` David Ryskalczyk
2015-12-23 2:14 ` Greg 'groggy' Lehey
2015-12-23 2:32 ` jason-tuhs
2015-12-23 2:44 ` Lyndon Nerenberg
2015-12-23 2:59 ` John Cowan
2015-12-23 4:05 ` Random832
2015-12-23 4:27 ` John Cowan
2015-12-23 0:46 ` Warren Toomey
2015-12-23 6:47 ` Dave Horsfall
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=20151223014407.07322440AE@lignose.oclsc.org \
--to=norman@oclsc.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).