The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@tuhs.org, douglas.mcilroy@dartmouth.edu
Subject: [TUHS] Re: Robert Morris's UUCP
Date: Thu, 16 Jan 2025 09:07:13 -0700	[thread overview]
Message-ID: <202501161607.50GG7DMW344260@freefriends.org> (raw)
In-Reply-To: <CAKH6PiX0MdMLF9KjQDUSbQbnq_opdzdnkMatU9NE3vD4itBKXQ@mail.gmail.com>

Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:

> > I often repeat a throwaway sentence that UUCP was Lesk,
> > building a bug fix distribution mechanism.
>
> > Am I completely wrong? I am sure Mike said this to me mid 80s.
>
> That was an important motivating factor, but Mike also had an
> unerring anticipatory sense of public "need".  Thus his programs
> spread like wildfire despite their bugs. UUCP itself is the premier
> example. Its popularity impelled its inclusion in v7 despite its
> woeful disregard for security.
>
> > Does anyone have [Robert Morris's UUCP CSTR]? Doug?
>
> Not I.

I have just sent him an email directly asking if he
has a copy.  If anything comes of it I'll send it on.

Thanks,

Arnold

  reply	other threads:[~2025-01-16 16:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 16:04 [TUHS] " Douglas McIlroy
2025-01-16 16:07 ` arnold [this message]
2025-01-16 19:29 ` [TUHS] " Marc Donner
2025-01-16 20:53   ` Alexander Schreiber
2025-01-17  1:35 ` Aaron
  -- strict thread matches above, loose matches on Subject: below --
2025-01-15 16:24 Norman Wilson
2025-01-16  6:42 ` George Michaelson
2025-01-15 15:31 [TUHS] " arnold
2025-01-15 15:51 ` [TUHS] " Chet Ramey via TUHS
2025-01-16  7:52   ` arnold
2025-01-16 16:39     ` Chet Ramey via TUHS
2025-01-16 16:47       ` Chet Ramey via TUHS
2025-01-16 19:48         ` Warren Toomey via TUHS
2025-01-16 16:50       ` Dan Cross
2025-01-16 16:54         ` Chet Ramey via TUHS
2025-01-16 19:15           ` arnold

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=202501161607.50GG7DMW344260@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@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).