The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] etymology of cron
Date: Wed, 13 Jan 2016 13:48:18 -0600 (CST)	[thread overview]
Message-ID: <alpine.NEB.2.11.1601131323570.10673@t1.m.reedmedia.net> (raw)
In-Reply-To: <948AFCDE-4254-4EA8-900C-77A91C0C8F7A@ronnatalie.com>

On Sun, 3 Jan 2016, Ronald Natalie wrote:

> > Thread "[ih] A laugh and a question" at
> > http://mailman.postel.org/pipermail/internet-history/2006-March/thread.html
> > was what inspired me to bring fuzzballs up in simh.
> 
> There were some inaccuracies in that piece as well which is why 
> history is sometimes fun.  It was definitely December 82 Not 83 
> because it was a few days before LINK 0 was going to be shut off on 
> the APRANET and we were scrambling to convert our machines to TCP.  
> As Clem and I have discussed in a side conversation, it was Gurwitz?s 
> contribution to 4.1a rather than 4.2a (was there a 4.2a even)?

I also looked at Muuss's own story long ago on his webpage.

And see corresponding bug entry from December 1983 and the same 
unattributed bug fix (revision 6.3)

https://groups.google.com/forum/#!original/net.unix-wizards/Dzh14xPrbiA/XAYJHc7VSgcJ

https://github.com/weiss/original-bsd/commit/195492fc6b05470d246fbedd4d2cf5c77d1d63b9

So his own story says impetus of his ping is a meeting in Norway in July 
1983. This year may be off.  RFC 828 of August 1982, said a planned IFIP 
technical committee meeting would be held in Norway in 1982.

His story says in December 1983 he quickly coded up his Unix ping but 
needed kernel support for it to work and required some hardware fixes 
before his "first" ping packet.

But his bug report (linked above) recorded as bugs/4.2BSD/sys/38 seems 
to suggest he already had a "ping" program that could have been in the 
4.2BSD release (which came out earlier in 1983).  I wonder what 
triggered the 20% packet loss with ping and maybe always was there since 
his year-earlier implementation (or maybe some other kernel change broke 
it or maybe he extended his ping to be able to show that).

His kernel fix was integrated at CSRG the next month (1984) and his ping 
was not added to BSD SCCS until April 1985. That ping revision had the 
comments saying it was December, 1983 and for "4.2".

The confusing thing is why notice the 20% loss even on software loopback 
driver (per bug ticket) when his story says other hardware needed to be 
fixed too before first ping. I think he may have skipped some of the 
history when he wrote his story.

(I tried to write this story up in my BSD history book but now became 
more confused :)


  reply	other threads:[~2016-01-13 19:48 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
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 [this message]
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=alpine.NEB.2.11.1601131323570.10673@t1.m.reedmedia.net \
    --to=reed@reedmedia.net \
    /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).