The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] etymology of cron
Date: Sat, 2 Jan 2016 16:06:12 -0500	[thread overview]
Message-ID: <CAC20D2PpHAysRAwbuv+v=UT=9NJ1S4AUXVTd7mD0HO1t6APbmA@mail.gmail.com> (raw)
In-Reply-To: <CAOkr1zWj-hQfJYm6WQykB5HO0aJr+X2LHepL=S4ieL1rQObGOA@mail.gmail.com>

Marc - thank you for bird dogging this.  I think the email from Ken to
Brian, and the email from Doug should be enough to close the issue for ever.

This is of course how history gets rewritten - which is a sad statement.
As I a wise man said ( Ben Franklin maybe??), history is often written by
those that were never there.

On Sat, Jan 2, 2016 at 2:56 PM, Marc Rochkind <rochkind at basepath.com> wrote:

> To update this thread:
>
> The wording from my last edit to the Wikipedia article on cron is still
> there, although one of the references has been removed, and the phrase
> "better source needed" has been added. That part is OK with me, and I
> actually agree with it--a better source *is* needed.
>
> But at least the article at this point no longer says that cron is an
> acronym.
>
> [To Greg Lehey: As anyone can edit the article, you could could add a
> paragraph about bogus claims as to what cron means if you want, but, in my
> opinion, the article is better without this distracting discussion.]
>
> On Fri, Dec 25, 2015 at 3:22 PM, Greg 'groggy' Lehey <grog at lemis.com>
> wrote:
>
>> On Friday, 25 December 2015 at 10:41:54 -0800, David wrote:
>> > It has been updated again:
>> >
>> >  The origin of the name cron is from the Greek word for time,
>> > ???????????? (chronos).[2][3] (Ken Thompson, author of cron, has
>> > confirmed this in a private communication with Brian Kernighan.)
>>
>> Yes, but you've removed the reference to the incorrect expansions.  As
>> I noted at some length earlier in this thread, that's not appropriate.
>> It ignores the fact that people have made these claims, it removes the
>> comment that they're unsubstantiated, and it prepares the field for
>> somebody else to make the claim again, with possibly even more bizarre
>> expmanations.  I won't back it out yet, because I can see further
>> changes coming from other directions.  Once again this Tedickey
>> character has been very active.
>>
>> Greg
>> --
>> Sent from my desktop computer.
>> Finger grog at FreeBSD.org for PGP public key.
>> See complete headers for address and phone numbers.
>> This message is digitally signed.  If your Microsoft MUA reports
>> problems, please read http://tinyurl.com/broken-mua
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160102/ded70cae/attachment.html>


  reply	other threads:[~2016-01-02 21:06 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2016-01-13 20:31 Noel Chiappa
  -- strict thread matches above, loose matches on Subject: below --
2016-01-03 14:26 Noel Chiappa
2016-01-02 23:14 Norman Wilson
2016-01-02 23:18 ` Greg 'groggy' Lehey
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  1:44 Norman Wilson
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
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='CAC20D2PpHAysRAwbuv+v=UT=9NJ1S4AUXVTd7mD0HO1t6APbmA@mail.gmail.com' \
    --to=clemc@ccc.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).