The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Early 70's WECo "Turnkey Systems"? Re: S.S. Pirzada UNIX Paper
Date: Fri, 29 Dec 2023 06:30:28 +0000	[thread overview]
Message-ID: <zFQ2VeVz6SbcdomqtNgWGt6JNdz4VYzkEWG_Psgj5w0q0gQgC153N2R8sase_V9cjb_qHlZ4X0QlKBQY2JBVg2XQe35CAZ5AFfJedtUZDWw=@protonmail.com> (raw)

In S.S. Pirzada's 1988 paper[1], page 35, section 3.3.2, he writes:

"Some operating telephone companies and the switching control center system (SCCS) group in Holmdel, NJ decided to use UNIX to collect maintenance data from their switches and for administration purposes. Other departments also started building applications on top of UNIX, some part of turnkey systems licensed by Western Electric (WECo)."

This is describing the situation before the establishment of USG in September 1973.  I'm curious, does anyone recall what some of these pre-USG WECo "turnkey systems" were?

The things that come to mind when I think of that phrase don't come about for several years, such as the 5ESS and other work surrounding Bellmac stuff.  The SCCS UNIX connection describes what becomes CB-UNIX if I understand the situation correctly, but that stays a bit afield from the more conventional pool that is dipped into for WECo needs.  Switching and UNIX all kinda come back together with DMERT on 1A/3B-API and 5ESS, but again that's late 70s R&D, early 80s deployment, not this time period, leaving me terribly curious what WECo would've been bundling UNIX with and shipping out to telcos.  The famous early use of UNIX in the Bell System is typography, and WECo did have involvement with Teletype equipment, so perhaps something along those lines?

If it helps set the scene, a binder I recently picked up from ~1972 describing Western Electric test sets distributed to telcos describes the following additional classes of such documents:

Shop Services - Special non-standard products
Public Telephones - System standard public telephone equipment
Data Communications - Teletypewriter and Data Sets
Subscriber Products - System standard PBX's, station equipment and special services
Non-Subscriber Products - Microwave, cable, power equipment, etc.
Non-Bell Equipment Index - Non-Bell System manufactured communication equipment

Unfortunately haven't seen any of the other binders yet but I've been keeping an eye out, one or another might describe something WECo was shipping around that had some UNIX up in it.  Nothing in this binder seems computer-y enough to run an operating system, just lots of gauges, dials, and probes.  Luckily it is quite clear what data test sets are designed for 103-data set maintenance so I have fodder for seeking Dataphone tools...

Anywho, happy soon to be new year folks, I'm excited to see what turns up next year!

- Matt G.

[1] - https://spiral.imperial.ac.uk/bitstream/10044/1/7942/1/Shamim_Sharfuddin_Pirzada-1988-PhD-Thesis.pdf

             reply	other threads:[~2023-12-29  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29  6:30 segaloco via TUHS [this message]
2023-12-29  7:28 ` [TUHS] " Jonathan Gray
2023-12-29 19:44   ` Warner Losh

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='zFQ2VeVz6SbcdomqtNgWGt6JNdz4VYzkEWG_Psgj5w0q0gQgC153N2R8sase_V9cjb_qHlZ4X0QlKBQY2JBVg2XQe35CAZ5AFfJedtUZDWw=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.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).