From: Larry McVoy <lm@mcvoy.com>
To: Josh Good <pepe@naleco.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Surprised about Unix System V in the 80's - so sparse!
Date: Wed, 17 Mar 2021 14:26:18 -0700 [thread overview]
Message-ID: <20210317212618.GA24642@mcvoy.com> (raw)
In-Reply-To: <20210317203335.GA5249@naleco.com>
On Wed, Mar 17, 2021 at 09:33:37PM +0100, Josh Good wrote:
> And that's it. The communications part only deals the Micnet (a serial-port
> based local networking scheme), and UUCP. No mention at all of the words
> "Internet" or "TCP/IP", no even in the Index.
SCO got Lachman's TCP/IP stack (that they bought from Convergent) just
after this timeframe. I know because I did the port. Also open sourced
a sw (STREAMS watch) program I wrote so you could tune the kernel (kernel
defaults yielded horrible performance). I still have that code if anyone
cares, can't imagine it is interesting.
next prev parent reply other threads:[~2021-03-17 21:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:33 Josh Good
2021-03-17 20:57 ` Adam Thornton
2021-03-17 21:04 ` Al Kossow
2021-03-17 21:38 ` Larry McVoy
2021-03-17 21:08 ` Jim Capp
2021-03-17 21:26 ` Larry McVoy [this message]
2021-03-17 21:29 ` Henry Bent
2021-03-17 21:40 ` Larry McVoy
2021-03-17 21:42 ` Henry Bent
2021-03-18 5:10 ` Wesley Parish
2021-03-18 1:15 ` [TUHS] XENIX or UNIX? (was: Surprised about Unix System V in the 80's - so sparse!) Greg 'groggy' Lehey
2021-03-18 1:21 ` George Michaelson
2021-03-20 0:12 ` Tony Finch
2021-03-18 23:05 ` [TUHS] Surprised about Unix System V in the 80's - so sparse! Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-03-19 1:45 ` Richard Salz
2021-03-19 2:01 ` Larry McVoy
2021-03-19 2:06 ` Chris Torek
2021-03-19 2:59 ` Earl Baugh
2021-03-19 17:27 ` Chris Torek
2021-03-17 23:18 M Douglas McIlroy
2021-03-17 23:22 ` George Michaelson
2021-03-18 1:23 ` Richard Salz
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=20210317212618.GA24642@mcvoy.com \
--to=lm@mcvoy.com \
--cc=pepe@naleco.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).