The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Fri, 29 Jun 2018 18:31:28 -0700	[thread overview]
Message-ID: <20180630013128.GC18031@mcvoy.com> (raw)

I've told this story so much that my kids hear me start it and go "is that
the Unix guy?  Yeah, we've heard this".  And I think many of you have heard
it as well so you can hit delete, but for the newbies to the list here goes.

Decades ago I was a grad student at UWisc and pretty active on comp.arch
and comp.unix-wizards (I was not a wizard but I've lived through, and
written up, the process of restoring a Masscomp after having done some
variant of rm -rf / so a stupid wizard wanna be?)

From time to time, some Unix kernel thing would come up and I'd email
...!research!dmr and ask him how that worked.  

He *always* replied.  To me, a nobody.  All he cared was that the question
wasn't retarded (and I bet to him some of mine were but the questions showed
that I was thinking and that was good enough for him).  I remember a long
discussion about something, I think PIPEBUF but not sure, and at some point
he sent me his phone number and said "call me".  Email was too slow.

So yeah, one of the inventors of Unix was cool enough to take some young
nobody and educate him.  That's Dennis.

I've tried to pass some of that energy forward to my kids, telling them
that if you want to learn, smart people like that and they will help you.

Dennis was a humble man, a smart man, and a dude willing to pass on what
he knew.

I miss him and cherish the interactions I had with him.

             reply	other threads:[~2018-06-30  1:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  1:31 Larry McVoy [this message]
2018-06-30  1:45 ` Jon Forrest
2018-06-30 18:43   ` Steve Johnson
2018-06-30  2:27 ` [TUHS] Masscomp oops [was: Any Good dmr Anecdotes?] Mike Markowski
  -- strict thread matches above, loose matches on Subject: below --
2018-07-18  9:42 [TUHS] Any Good dmr Anecdotes? Hendrik Jan Thomassen
2018-07-03  7:27 arnold
2018-07-02 19:55 Paul Ruizendaal
2018-07-01 16:35 Norman Wilson
2018-06-29  7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51   ` John P. Linderman
2018-06-30  0:50   ` Steve Johnson
2018-06-30 11:44     ` Arrigo Triulzi
2018-06-30 22:42       ` Arthur Krewat
2018-06-30 23:29         ` Arrigo Triulzi
2018-07-01  4:17           ` Larry McVoy
2018-07-01 11:42           ` ron
2018-07-01  5:29       ` Dave Horsfall
2018-07-01  8:28         ` Arrigo Triulzi
2018-07-01 11:34         ` ron
2018-07-09 16:30           ` Random832
2018-07-09 17:13             ` Clem Cole
2018-07-10  5:54               ` arnold
2018-07-10  6:09                 ` George Michaelson
2018-07-10  7:19                   ` arnold
2018-07-11  0:20                     ` Noel Hunt
2018-07-11  1:31                       ` Larry McVoy
2018-07-11  1:37                         ` George Michaelson
2018-07-11  1:37                         ` ron minnich
2018-07-11  3:12                           ` Larry McVoy
2018-07-13  9:08                       ` ches@Cheswick.com
2018-07-13 14:10                         ` ron
2018-07-10 14:10                 ` Clem Cole
2018-07-03 17:34       ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30  0:06   ` Greg 'groggy' Lehey
2018-06-30 14:20   ` John P. Linderman

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=20180630013128.GC18031@mcvoy.com \
    --to=lm@mcvoy.com \
    --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).