From: Marc Rochkind <mrochkind@gmail.com>
To: The UNIX Historical Society <tuhs@tuhs.org>
Subject: [TUHS] The Mark Williams Company and Coherent
Date: Thu, 14 Mar 2024 21:45:29 -0600 [thread overview]
Message-ID: <CAOkr1zW9OtC=JExhOv=_sjb6_rV-RnCp8ozWSD+GsnFJaAdRZA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
In another thread there's been some discussion of Coherent. I just came
across this very detailed history, just posted last month. There's much
more to it than I knew.
https://www.abortretry.fail/p/the-mark-williams-company
Marc
[-- Attachment #2: Type: text/html, Size: 497 bytes --]
next reply other threads:[~2024-03-15 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 3:45 Marc Rochkind [this message]
2024-03-15 5:16 ` [TUHS] " Heinz Lycklama
2024-03-15 7:00 ` Rob Pike
2024-03-15 13:03 ` Dan Cross
2024-03-15 13:43 ` Dan Cross
2024-03-15 14:10 ` Marc Rochkind
2024-03-15 15:42 ` Theodore Ts'o
2024-03-15 14:40 ` Paul Winalski
2024-03-15 21:23 [TUHS] " Douglas McIlroy
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='CAOkr1zW9OtC=JExhOv=_sjb6_rV-RnCp8ozWSD+GsnFJaAdRZA@mail.gmail.com' \
--to=mrochkind@gmail.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).