The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Ron Natalie" <>
To: "Tom Teixeira" <>,
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Thu, 14 Jul 2022 20:39:44 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

It can do subnets, but it can’t deal with long haul (over the greater 
internet) time delays.

------ Original Message ------
From "Tom Teixeira" <>
Date 7/14/2022 4:32:55 PM
Subject [TUHS] Re: Unix V8 Chaosnet, any takers?

>On 7/14/22 2:19 PM, Ron Natalie wrote:
>>Note, I don’t know what you’re planning, but Chaos couldn’t take any propagation delay.   It’s really limited to a LAN implementation as originally designed.
>It definitely had subnet routing, and as I recall, the KL10's and other machines with front end I/O processors generally used chaosnet routing between the host itself and the rest of the network. i.e. the I/O processor was on one subnet, the host on a second subnet and the rest of the "LAN" was on the other side of the I/O processor. My recollection is that unlike an IP router, a Chaosnet node had only one address, and routing tables determined which device to send the data on.
>And LCS definitely had multiple coax cable runs with each run a subnet with routing between. But with a maximum of 256 subnets, routing was much simpler.
>I wonder how much benefit is available from using network switches rather than collision detection and retransmit, though the virtual token was supposed to reduce collisions somewhat.

  reply	other threads:[~2022-07-14 20:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 11:08 [TUHS] " Lars Brinkhoff
2022-07-14 16:37 ` [TUHS] " John Floren
2022-07-14 17:00   ` Lars Brinkhoff
2022-07-14 17:51     ` segaloco via TUHS
2022-07-14 18:19       ` Ron Natalie
2022-07-14 20:32         ` Tom Teixeira
2022-07-14 20:39           ` Ron Natalie [this message]
2022-07-15  0:33             ` Grant Taylor via TUHS
2022-07-15  4:29               ` Erik E. Fair
2022-07-14 19:36       ` Lars Brinkhoff
2022-07-14 21:50         ` segaloco via TUHS
2022-07-16  6:38           ` Lars Brinkhoff
2022-07-16 14:05             ` Warner Losh
2022-07-15  8:51 Paul Ruizendaal via TUHS
2022-07-15 10:25 Noel Chiappa
2022-07-15 11:53 ` Theodore Ts'o
2022-07-16  6:59 ` Lars Brinkhoff
2022-07-16 15:51 Noel Chiappa
2022-07-16 17:02 ` Warner Losh
2022-07-16 20:02 Paul Ruizendaal
2022-07-17 23:39 Noel Chiappa
2022-07-18  1:01 ` Ron Natalie
2022-07-18 17:07 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).