From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] etymology of cron
Date: Thu, 24 Dec 2015 16:52:33 -0800 [thread overview]
Message-ID: <563cf28905c1795afe24eb45fc0cfe49.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <20151224230506.GM14449@eureka.lemis.com>
This has been a somewhat bizarre and troubling thread, all in all.
Would anybody want to discuss the origin of 'ls'? Or 'at'?
Steve
PS: (that was NOT a serious suggestion!)
> On Thursday, 24 December 2015 at 10:17:53 -0500, John Cowan wrote:
>> Clem Cole scripsit:
>>
>>> Rik in his role as the editor of ;login is going to try work with Doug
>>> and
>>> to get something "published" into the next edition which should satisfy
>>> the
>>> Wikipedia folks. There is a minor issue is that Rik is technically
>>> past
>>> the deadline but due to the holiday, there are a few days of grace that
>>> the
>>> workers putting the issue together have said they will thankfully try
>>> to
>>> handle.
>>>
>>> So maybe we can have get this fixed shortly.
>>
>> I don't think so. Is ;login: a peer-reviewed journal? It doesn't
>> look like it to me.
>
> One of the original references was from the proceedings of an AUUG
> conference. From personal experience I can confirm that the level of
> review for the conferences fell far short of what USENIX did.
>
>> Still, the current state says:
>>
>> The origin of the name cron is from the Greek word for
>> time, ???????????? (chronos), according to its author Ken
>> Thompson[2][better source needed]. Others have suggested that the
>> name comes from the Greek God Chronos[3] or that it is an acronym
>> for "Command Run On Notice"[4] or "Commands Run Over Night",[5]
>> but the references lack substantiation.
>>
>> Even if someone is still grumbling on the talk page, that doesn't
>> substantially misrepresent anything that I can see.
>
> Yes, that last sentence was my update. As I mentioned in an earlier
> message, I think that it's appropriate that it should stay, if only to
> stop people making the claim again in a more forceful manner.
>
> But it would be nice to be able to remove the [better source needed].
> It seems that there's only one person objecting to the changes. I've
> asked him on the talk page what he really wants.
>
> 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 prev parent reply other threads:[~2015-12-25 0:52 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- 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: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=563cf28905c1795afe24eb45fc0cfe49.squirrel@webmail.yaccman.com \
--to=scj@yaccman.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).