From: Andy Kosela <akosela@andykosela.com>
To: "chet.ramey@case.edu" <chet.ramey@case.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Mike Karels has died
Date: Tue, 4 Jun 2024 22:35:53 +0200 [thread overview]
Message-ID: <CALMnNGgERO=GZKFSEtpmBgjOxBEmk2=preq4yojyKYXDke3PdQ@mail.gmail.com> (raw)
In-Reply-To: <58f15238-c5f3-4e51-920b-c718ff616cff@case.edu>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
On Tuesday, June 4, 2024, Chet Ramey via TUHS <tuhs@tuhs.org> wrote:
> Sad, horrible news.
>
> https://www.facebook.com/groups/BSDCan/permalink/10159552565206372/
>
>
He was the BSD giant. Rest in Peace. I remember one particular Computer
Chronicles episode from 1989 which featured Mike.
https://youtu.be/lkyyAKTvmx0?si=9fKp2pmF_e7HeVpk
--Andy
[-- Attachment #2: Type: text/html, Size: 803 bytes --]
next prev parent reply other threads:[~2024-06-04 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 19:23 Chet Ramey via TUHS
2024-06-04 20:35 ` Andy Kosela [this message]
2024-06-05 23:47 ` [TUHS] " Alan Coopersmith via TUHS
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='CALMnNGgERO=GZKFSEtpmBgjOxBEmk2=preq4yojyKYXDke3PdQ@mail.gmail.com' \
--to=akosela@andykosela.com \
--cc=chet.ramey@case.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).