The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] etymology of cron
Date: Sun, 3 Jan 2016 10:22:21 -0500	[thread overview]
Message-ID: <948AFCDE-4254-4EA8-900C-77A91C0C8F7A@ronnatalie.com> (raw)
In-Reply-To: <251affe807c70da8983a241ea7ed9c20@xs4all.nl>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]


> 
> 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 remember pouring over the 4.1a/4.1c/4.2 stuff doing the user mode conversions for our machines.    I really disliked the berknet host table format (alas this has persisted longer than ping) and there was not yet a program that converted the table that the NIC distributed to that format.    I rewrote rhost (and it’s related functions) to read the NIC host tables directly.    I also wrote a program to periodically retrieve the table from the NIC.

Later someone provided a program to build a BSD-style host table from NIC table.    We inadvertantly blew up this program when we added a machine, coincidentally called BRL-ZAP to the table.    It was the first ethernet-connected laser printer (an Imagen Imprint-10) we had.   I just put 68000 as the CPU type without thinking about it.   I got some irate emails from people thinking I’d crashed their program intentionally given the hostname.   Apparently the conversion program used YACC and an incorrect grammer to parse the table.   They had assumed that machine types always began with a letter.    To me the fact that they had used YACC was overkill (my direct reading program didn’t do so), the file was essentially a bunch of fields separated with COLONS (and in some fields subdivided by commas).    There was some file that every UNIX machine was already parsing continually without the need for a grammar similarly formatted (/etc/passwd anybody?).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2284 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160103/b463ce9e/attachment.bin>


  reply	other threads:[~2016-01-03 15:22 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 [this message]
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=948AFCDE-4254-4EA8-900C-77A91C0C8F7A@ronnatalie.com \
    --to=ron@ronnatalie.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).