The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Spider (and back to quiz)
Date: Fri, 24 Jan 2020 02:59:23 +0100	[thread overview]
Message-ID: <13430143-695E-4DBD-A443-9ECCA0FB4283@planet.nl> (raw)

There is more in that issue of BSTJ, and indeed it seems this was a precursor.

https://ia801905.us.archive.org/25/items/bstj51-6-1147/bstj51-6-1147_text.pdf
https://ia801603.us.archive.org/0/items/bstj51-6-1167/bstj51-6-1167_text.pdf

The first paper makes mention of repeaters starting to self oscillate, and a redesign being underway.

There is a possibility that a Unix PDP11 was connected to this earlier network prior to Spider existing, in which case the accepted quiz answer would be wrong.


>> Ugh. Memory lane has a lot of potholes. This was a really long time ago. 
> 
> Many thanks for that post - really interesting!
> 
> I had to look up "Pierce Network", and found it described in the Bell Journal:
> https://ia801903.us.archive.org/31/items/bstj51-6-1133/bstj51-6-1133_text.pdf
> 
> In my reading the Spider network is a type of Pierce network.
> 
> However, the network that you remember is indeed most likely different from Spider:
> - it was coax based, whereas the Spider line was a twisted pair
> - there was more than one, whereas Spider only ever had one (operational) loop
> 
> Condon and Weller are acknowledged in the report about Spider as having done many of its hardware details. The report discusses learnings from the project and having to tune repeaters is not among them (but another operational issue with its 'line access modules’ is discussed).
> 
> All in all, maybe these coax loops were pre-cursors to the Spider network, without a switch on the loop (“C” nodes in the Pierce paper). It makes sense to first try out the electrical and line data protocol before starting work on higher level functions.
> 
> I have no idea what a GLANCE G is...





                 reply	other threads:[~2020-01-24  2:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=13430143-695E-4DBD-A443-9ECCA0FB4283@planet.nl \
    --to=pnr@planet.nl \
    --cc=tuhs@minnie.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).