The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul McJones <paul@mcjones.org>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Happy birthday Morris worm
Date: Mon, 4 Nov 2019 10:10:26 -0800	[thread overview]
Message-ID: <116B676F-5917-481A-9634-0E6C5F702B9B@mcjones.org> (raw)
In-Reply-To: <mailman.3.1572832803.30037.tuhs@minnie.tuhs.org>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

Another possible source of inspiration — including the name “worm” — were the publications by John Shoch and Jon Hupp on programs they wrote at Xerox PARC around 1979-1980 and published in 1980 and 1982:

John F. Shoch and Jon Hupp:
 The “Worm" Programs — Early Experience with a Distributed Computation.
Xerox SSL-80-3 and IEN 159. May 1980, revised September 1980
http://www.postel.org/ien/pdf/ien159.pdf

John F. Shoch and Jon Hupp:
 The “Worm" Programs — Early Experience with a Distributed Computation.
CACM V25 N3 (March 1982)
http://www.eecs.harvard.edu/~margo/cs261/background/shoch.pdf

> On Nov 3, 2019, Paul Winalski <paul.winalski@gmail.com> wrote:
> 
> On 11/2/19, Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>> wrote:
>> 
>> the notion of a self propagating thing
>> was quite novel (even if it had been theoretically discussed in many places
>> prior to the worm, and even though others had proven it via slower moving
>> vectors of BBS).
> 
> Novel to the Internet community, perhaps, but an idea that dates back
> to the 1960s in IBM mainframe circles.  Self-submitting OS/360 JCL
> jobs, which eventually caused a crash by filling the queue files with
> jobs, were well-known in the raised-floor world.
> 
>> In hindsight people like to point at it and what a terrible thing it was,
>> but Robert just got there first.
> 
> Again, first on the Internet.  Back in 1980 I accidentally took down
> DEC's internal engineering network (about 100 nodes, mostly VAX/VMS,
> at the time) with a worm.  ...
> 
> Robert Morris worked as an intern one summer in DEC's compiler group.
> The Fortran project leader told Morris about my 1980 worm incident.
> So he certainly had heard of the concept before he fashioned his
> UNIX/Internet-based worm a few years later.
> 
> -Paul W.


[-- Attachment #2: Type: text/html, Size: 15419 bytes --]

       reply	other threads:[~2019-11-04 18:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3.1572832803.30037.tuhs@minnie.tuhs.org>
2019-11-04 18:10 ` Paul McJones [this message]
2019-11-04 18:57   ` Bakul Shah
2019-11-04 19:24     ` Richard Salz
2019-11-05  3:48       ` Lawrence Stewart
2019-11-05 16:04         ` Ronald Natalie
2019-11-06 10:37           ` arnold
2019-11-06 13:35             ` Ronald Natalie
2019-11-04 19:25     ` SPC
2019-11-04 20:27     ` Dan Cross
2019-11-04 22:10       ` Michael Kjörling
2019-11-05  0:25     ` Anthony Martin
2019-11-15 14:31 [TUHS] Happy birthday, " Doug McIlroy
2019-11-15 14:39 ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2019-11-13 13:47 [TUHS] Happy birthday " Doug McIlroy
2019-11-12 22:24 Norman Wilson
2019-11-12 20:56 Norman Wilson
2019-11-12 22:00 ` Dave Horsfall
2019-11-13  7:35 ` arnold
2019-11-02 14:12 Doug McIlroy
2019-11-02 20:12 ` Warner Losh
2019-11-03 17:12   ` Paul Winalski

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=116B676F-5917-481A-9634-0E6C5F702B9B@mcjones.org \
    --to=paul@mcjones.org \
    --cc=paul.winalski@gmail.com \
    --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).