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] CSRC Involvement in Non-UNIX AT&T Software Projects
Date: Fri, 07 Jun 2024 05:00:09 +0000	[thread overview]
Message-ID: <tj1yKQomOEXaaB6xPPnGPtH4u1UOC6LQ4IG9eo5YVxnEAuCw__ScXlbzMixJCT1zqFpuBnth_hxbTuFlOuc0-KMLylNrDA0hKSECvH1oXAs=@protonmail.com> (raw)

I'm reading about the Automatic Intercept System as discussed in BSTJ Vol. 53 No. 1 this evening.  It is a stored program control call handling system designed to respond to calls with potential forwarding or disconnection messages.  Reading through the description of the operating system for AIS got me wondering:

What with the growing experience in the CSRC regarding kernel technologies and systems programming, was there ever any crossover regarding UNIX folks applying their developments to other non-UNIX AT&T systems projects or vice versa, perhaps folks who worked primarily on switching and support software bringing things over to the UNIX development camp?  In other words, was there personnel cross-pollination between Bell System UNIX programmers and the folks working on stuff like AIS, ESS switching software, etc.?  Or were the aims and implementation of such projects so different that the resources were relatively siloed?

I would imagine some of these projects were at least developed using UNIX given the popularity and demands of PWB.  That's just my hunch though, some BSTJs also describe software development and maintenance taking place on S/360 and S/370 machines and various PDPs.  Indeed the development process for AIS mentioned above, as of late 1971, involved assembly via S/360 software and then system maintenance and debugging via an attached PDP-9.  

- Matt G.

             reply	other threads:[~2024-06-07  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  5:00 segaloco via TUHS [this message]
2024-06-07  5:32 ` [TUHS] " Kevin Bowling
2024-06-07 11:44 [TUHS] " Douglas McIlroy

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='tj1yKQomOEXaaB6xPPnGPtH4u1UOC6LQ4IG9eo5YVxnEAuCw__ScXlbzMixJCT1zqFpuBnth_hxbTuFlOuc0-KMLylNrDA0hKSECvH1oXAs=@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).