From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] SYSV & TCP/IP on the VAX...
Date: Tue, 26 May 2009 17:25:45 -0700 [thread overview]
Message-ID: <3D000973-4335-4060-BE7E-84006251BB7B@orthanc.ca> (raw)
In-Reply-To: <20090526234802.GD3873@bitmover.com>
>I think Lachman (where I was working at the
> time) did a lot of streams based TCP/IP, they may have done one for
> the vax.
Pre-SVR4 it was pretty much Lachman and Wollongong addons for pure
SYSV releases.
> But why would you want it? It was a steaming pile of sh*t.
Amen! It's a bloody miracle the Lachman code worked at all (on the 3B2
at least). The Wollongong code was better. But both faithfully
reproduced all the original BSD libc bugs.
next prev parent reply other threads:[~2009-05-27 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 23:45 Jason Stevens
2009-05-26 23:48 ` Larry McVoy
2009-05-26 23:57 ` Jason Stevens
2009-05-26 23:59 ` Larry McVoy
2009-05-27 0:10 ` Jason Stevens
2009-05-27 3:06 ` John Cowan
2009-05-27 3:35 ` Jason Stevens
2009-05-27 4:05 ` M. Warner Losh
2009-05-27 0:32 ` Lyndon Nerenberg
2009-05-27 1:06 ` Corey Lindsly
2009-05-27 4:36 ` Gregg C Levine
2009-05-27 0:25 ` Lyndon Nerenberg [this message]
2009-05-27 17:39 Brian S Walden
2009-05-27 18:20 ` Larry McVoy
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=3D000973-4335-4060-BE7E-84006251BB7B@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).