From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] SYSV & TCP/IP on the VAX...
Date: Tue, 26 May 2009 16:59:05 -0700 [thread overview]
Message-ID: <20090526235905.GE3873@bitmover.com> (raw)
In-Reply-To: <46b366130905261657g4a82caf3s41cc5be2c8253d4c@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Tue, May 26, 2009 at 07:57:01PM -0400, Jason Stevens wrote:
> On Tue, May 26, 2009 at 7:48 PM, Larry McVoy <lm at bitmover.com> wrote:
> > I added TCP/IP to SCO which is some sort of sys v thing (I think, it's
> > been a lot of years). 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.
>
> I've seen lots of sco stuff say it's SYSV... like Xenix 2.3.4 ... So I
> guess it's not outside of that realm. It's too bad SCO never did
> bundle the dev kit & networking or that Linux thing probably never
> would have gained commercial traction.. but then that's just my wild
> guess.
I doubt it - we (bitkeeper folks) still support sco and it sucks. It's
like time stood still and nothing was added.
> > But why would you want it? It was a steaming pile of sh*t.
>
> Morbid curiosity I guess... seeing as it's basically all but dead. I
> guess the SYSV stuff we ran on the 3B2's was more modern, and 'usable'
> just as SYSVr3 (AIX) certainly was/is.
The 3b2's were ok. I liked the ATT Unix PC, 3b1 (?). My roomate and
I in college both bought those and did a lot of hacking on them.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2009-05-26 23:59 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 [this message]
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
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=20090526235905.GE3873@bitmover.com \
--to=lm@bitmover.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).