From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Masscomp sources? was looking for 4.1a BSD full kernel source
Date: Thu, 1 Dec 2016 11:06:05 -0500 [thread overview]
Message-ID: <CAC20D2NOtbC88SHsNUzr9wjkW-AFRGZb-jNzXSd0VLmRXwuohQ@mail.gmail.com> (raw)
In-Reply-To: <20161201153059.GL2620@mcvoy.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
below...
On Thu, Dec 1, 2016 at 10:30 AM, Larry McVoy <lm at mcvoy.com> wrote:
> By the way, the "getting started with sockets" document that came with
> the 4.1a BSD based Masscomp version of the OS is by far the nicest
> introduction to sockets that I've ever seen.
Thank you. You made my day. I lead the coms group when that was done and
while I did not write the document, the doc writer that did, worked under
my direction..
> I used to have a copy
> but lost it. Any chance of finding that?
Maybe - I'll ask her if she kept it. I don't think I ever had the master.
FYI: its troff of course ;-)
> Are the Masscomp sources
>
> around?
Maybe, I my knowledge they were never put on-line and Concurrent owns the
IP (little know fact - Masscomp is actually the legal entity that still
stands year later - I'll fill you in offline). As for the sources need to
do some hunting.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161201/d6eadaf9/attachment.html>
next prev parent reply other threads:[~2016-12-01 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 8:30 [TUHS] " Paul Ruizendaal
[not found] ` <0f3795f4-fb98-3370-510c-347a272dddae@aueb.gr>
2016-12-01 10:40 ` Paul Ruizendaal
2016-12-01 14:27 ` Clem Cole
2016-12-01 15:30 ` [TUHS] Masscomp sources? was " Larry McVoy
2016-12-01 16:06 ` Clem Cole [this message]
2016-12-01 20:13 ` [TUHS] " Paul Ruizendaal
2016-12-01 21:28 ` Clem Cole
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=CAC20D2NOtbC88SHsNUzr9wjkW-AFRGZb-jNzXSd0VLmRXwuohQ@mail.gmail.com \
--to=clemc@ccc.com \
/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).