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] 5ESS Operating Systems Today?
Date: Tue, 14 Mar 2023 04:22:33 +0000	[thread overview]
Message-ID: <ZELGZJ0lNtB4mlaNM38XkylKSMVlV6cFzMcRxpwyajCY5MGgit0j8Sspk_gCpQ2Q1J5sjgJHJmJuU80HO6bq3KXfaT6zDY9a4Qu4M5lVJj4=@protonmail.com> (raw)

Starting this in TUHS due to UNIX relevance, but with the heavy disclaimer this should quickly diverge to COFF if it drifts into foreign waters.

I've gotten to reading about 5ESS lately, and it seems there are many in use still today.  I found myself wondering what the evolution has looked like as far as computing hardware and operating systems involved.  DMERT ran on the 3B-20D supporting the 5ESS systems in the early 80s, at the same time that UNIX 4.x was making rounds on the 3B-20S.

A 5ESS manual from 2001[1] mentions UNIX RTR (Real-Time Reliable) of the DMERT lineage.  Wikipedia[2] suggests 5ESS is still very much in use and mentions more modern systems like VCDX; its "Sun Microsystems SPARC workstation runs the UNIX-based Solaris (operating system) that executes a 3B20/21D processor MERT OS emulation system."  This sounds like the Lucent 3B20 emulator.

Is there still a line of UNIX RTR/DMERT being maintained to this day?  Or are users left with other avenues to keep their hardware updated if necessary?

[1] - https://documentation.nokia.com/cgi-bin/dbaccessfilename.cgi/235600510_V1_5ESS%20Switc
[2] - https://en.wikipedia.org/wiki/5ESS_Switching_System

- Matt G.

                 reply	other threads:[~2023-03-14  4:22 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='ZELGZJ0lNtB4mlaNM38XkylKSMVlV6cFzMcRxpwyajCY5MGgit0j8Sspk_gCpQ2Q1J5sjgJHJmJuU80HO6bq3KXfaT6zDY9a4Qu4M5lVJj4=@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).