From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] System III - TCP/IP
Date: Mon, 9 Nov 2015 01:45:18 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1511090115510.57799@aneurin.horsfall.org> (raw)
In-Reply-To: <20151108071102.GA7290@mcvoy.com>
On Sat, 7 Nov 2015, Larry McVoy wrote:
> Just getting back to email (spent the day taking pictures at a hockey
> tournament).
A typical Canadian :-) There is only one game, and it's called Cricket;
where else can you see a sport that can take five days, and ends up in a
draw?
[...]
> I tend to agree with whoever said 2.11BSD. If you have to do 16 bit and
> you want all the goodies, 2.11BSD is where you want to be. Back porting
> all that stuff to System III really makes me ask the question of "why?".
> Why bother? I get that it could be like a mountain you want to climb,
> if that's the case, cool. But I never saw System III as much of a cool
> mountain. I think there were some cool parts, didn't the PWB and DWB
> come form System III? If so, those where the things I'd want to have
> ported forward. Other than that, what's the System III attraction?
I thought PWB (makers of "make") came from Harvard? Other than that, Sys
III/V was presented by suits; enough said. System III was, well, what
System V was going to be like... It never had TCP/IP, only BNU (i.e. UUCP
with a jazzed-up name).
Gahh... I still have flash-backs to that awful "cu" command,
Perhaps it's my experience with Lionel Singer et al, but I really learned
to hate SysIII/V...
> If you actually have a need to have this work and have networking then
> once again Clem has the right idea, grab one of those boards. (And once
> again I want to meet Clem in person, lot of love for the Masscomp work
> and all his stories).
Indeed.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2015-11-08 14:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 19:03 Oliver Lehmann
2015-11-07 19:20 ` Larry McVoy
2015-11-07 20:27 ` Cory Smelosky
2015-11-08 7:11 ` Larry McVoy
2015-11-08 7:22 ` John Cowan
2015-11-08 8:20 ` Cory Smelosky
2015-11-08 14:45 ` Dave Horsfall [this message]
2015-11-08 17:04 ` Steve Nickolas
2015-11-09 4:34 ` Larry McVoy
2015-11-07 21:28 ` Clem Cole
2015-11-07 22:07 ` Cory Smelosky
2015-11-07 22:13 ` Oliver Lehmann
2015-11-08 5:10 ` Derek Fawcus
2015-11-08 5:39 ` Nick Downing
2015-11-08 9:40 ` Oliver Lehmann
2015-11-08 13:38 ` Oliver Lehmann
2015-11-09 0:21 ` Nick Downing
2015-11-09 8:15 ` Oliver Lehmann
2015-11-09 8:16 ` Oliver Lehmann
2015-11-09 9:40 ` Oliver Lehmann
2015-11-09 9:40 ` Oliver Lehmann
2015-11-09 22:36 ` Nick Downing
2015-11-09 0:31 ` Nick Downing
2015-11-11 1:54 ` Cornelius Keck
2015-11-11 6:46 ` Oliver Lehmann
2015-11-08 15:52 Noel Chiappa
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=alpine.BSF.2.11.1511090115510.57799@aneurin.horsfall.org \
--to=dave@horsfall.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).