The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Mary Ann Horton <mah@mhorton.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Were cron and at done at the same time? Or one before the other?
Date: Tue, 8 Dec 2020 11:05:39 -0800	[thread overview]
Message-ID: <20201208190539.GA3303@mcvoy.com> (raw)
In-Reply-To: <c22ff9c1-63c0-bd85-da8e-0df4cd99ff6a@mhorton.net>

Doesn't it stand to reason that cron would come first, isn't at implemented
with an entry in a crontab?

On Tue, Dec 08, 2020 at 10:51:05AM -0800, Mary Ann Horton wrote:
> My V6 manual has cron(VIII) - documentation of /usr/lib/crontab - but no
> mention of at.
> 
> This is consistent with my recollection - I first saw at in V7.
> 
> ?????? Mary Ann
> 
> On 12/8/20 10:11 AM, ron minnich wrote:
> >When I got into Unix in 1976 cron and at were both there.
> >
> >I got to wondering for no particular reason which came first -- I had
> >always assumed cron, but ...?
> >
> >Anyone know?

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

  reply	other threads:[~2020-12-08 19:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 18:11 ron minnich
2020-12-08 18:51 ` Mary Ann Horton
2020-12-08 19:05   ` Larry McVoy [this message]
2020-12-08 19:20     ` Michael Kjörling
2020-12-09  2:00       ` Dave Horsfall
2020-12-08 19:39   ` Clem Cole
2020-12-09  4:35 M Douglas McIlroy
2020-12-09 15:40 ` Clem Cole
2020-12-09 15:46   ` Niklas Karlsson
2020-12-09 16:01   ` Bakul Shah
2020-12-09 16:11     ` Clem Cole
2020-12-09 17:05       ` Bakul Shah
2020-12-09 17:42         ` Dan Stromberg
2020-12-09 23:46           ` Nemo Nusquam
2020-12-14 20:28     ` Dave Horsfall
2020-12-14 22:23       ` Thomas Paulsen
2020-12-14 23:04         ` Andrew Hume
2020-12-14 23:59       ` Harald Arnesen
2020-12-17  4:08         ` John Cowan
2020-12-15  2:57       ` Bakul Shah
2020-12-15  3:05         ` Warner Losh
     [not found]   ` <CAC20D2PXZY9aWgDf-RknROs6JbKEUjzbQ2BRzfTgTR07pXni3g@mail.g mail.com>
2020-12-09 16:04     ` John Foust
2020-12-09 16:40   ` Warner Losh
2020-12-09 16:53     ` Jon Steinhart
2020-12-09 16:58   ` Theodore Y. Ts'o
2020-12-09 19:58     ` Dan Cross
2020-12-09 20:30       ` Will Senn
2020-12-13  1:07       ` Theodore Y. Ts'o
2020-12-13  1:56         ` Jon Steinhart
2020-12-13  2:58           ` Theodore Y. Ts'o
2020-12-13  3:07             ` Jon Steinhart
2020-12-13 16:49               ` Theodore Y. Ts'o
2020-12-13  3:02         ` Dan Cross
2020-12-09 23:22     ` Bakul Shah
2020-12-09 23:44       ` Steffen Nurpmeso
2020-12-09 23:51         ` Steffen Nurpmeso
2020-12-12  2:56   ` Dave Horsfall
2020-12-12 19:10     ` scj
2020-12-09 19:25 Noel Chiappa
2020-12-13  2:02 Noel Chiappa
2020-12-13  2:08 ` Clem Cole

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=20201208190539.GA3303@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=mah@mhorton.net \
    --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).