From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: A few comments on porting the Bourne shell
Date: Mon, 2 Jan 2023 13:48:19 -0500 [thread overview]
Message-ID: <CAEoi9W7a-qWv5=9zA6bTx+54R95LoaBV-LEDjrh0XgzeYif-xw@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7A==NC+W+H+kZbUZ6AK2O-cUjwjUz_Gx_HY_BKfeeBqA@mail.gmail.com>
[Apologies for resending; I messed up and used the old Minnie address
for COFF in the Cc]
On Mon, Jan 2, 2023 at 1:36 PM Dan Cross <crossd@gmail.com> wrote:
>
> On Mon, Jan 2, 2023 at 1:13 PM Clem Cole <clemc@ccc.com> wrote:
> > Maybe this should go to COFF but Adam I fear you are falling into a tap that is easy to fall into - old == unused
> >
> > One of my favorite stores in the computer restoration community is from 5-10 years ago and the LCM+L in Seatle was restoring their CDC-6000 that they got From Purdue. Core memory is difficult to get, so they made a card and physical module that could plug into their system that is both electrically and mechanically equivalent using modern semiconductors. A few weeks later they announced that they had the system running and had built this module. They got approached by the USAF asking if they could get a copy of the design. Seems, there was still a least one CDC-6600 running a particular critical application somewhere.
> >
> > This is similar to the PDP-11s and Vaxen that are supposed to be still in the hydroelectric grid [a few years ago the was an ad for an RSX and VMS programmer to go to Canada running in the Boston newspapers - I know someone that did a small amount of consulting on that one].
>
> One of my favorite stories along these lines is the train signalling
> system in Melbourne, running on a "PDP-11". I quote PDP-11 because
> that is now virtualized:
> https://www.equicon.de/images/Virtualisierung/LegacyTrainControlSystemStabilization.pdf
>
> Indeed older systems show up in surprising places. I was once on the
> bridge of a US Naval vessel in the late '00s and saw a SPARCstaton 20
> running Solaris (with the CDE login screen). I don't recall what it
> was doing, but it was a tad surprising.
>
> I do worry about legacy systems in critical situations, but then, I've
> been in a firefight when the damned tactical computer with the satcomm
> link rebooted and we didn't have VHF comms with the battlespace owner.
> That was not particularly fun.
>
> - Dan C.
next prev parent reply other threads:[~2023-01-02 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52FB6638-AEFF-4A4F-8C2E-32089D577BA0@planet.nl>
[not found] ` <464819f0-d2f6-2a60-6481-a194f4428b4d@case.edu>
[not found] ` <20221230200246.GW5825@mcvoy.com>
[not found] ` <88f83b4c-b3f9-ed87-b2fa-560fb369742a@makerlisp.com>
[not found] ` <20221231035931.GG5825@mcvoy.com>
[not found] ` <BD716565-29A2-4959-AA20-339E91DBF789@iitbombay.org>
[not found] ` <20221231044049.GI5825@mcvoy.com>
2022-12-31 11:57 ` [COFF] fmt Strings. (Was: A few comments on porting the Bourne shell) Ralph Corderoy
[not found] ` <alpine.BSF.2.21.9999.2212311516330.69068@aneurin.horsfall.org>
[not found] ` <528f0c53-ccc2-88a1-5a7b-120362c648dd@mhorton.net>
[not found] ` <CAC20D2NZbBa9PK_F50iWVn+t7m8=_mcw4mR2mKcTgDbdqxJi=w@mail.gmail.com>
[not found] ` <20230102165120.GK25547@mcvoy.com>
[not found] ` <E977D385-604F-49A9-83FD-8C5270623066@gmail.com>
[not found] ` <20230102174304.GM25547@mcvoy.com>
[not found] ` <E4339ED1-73F4-4BBB-92EF-B9D5A92C5096@gmail.com>
[not found] ` <CAC20D2Pf-rLL8NqoJ7RcXHjrq4crQKC=K25218fuM0yd0rQNDA@mail.gmail.com>
[not found] ` <CAEoi9W7A==NC+W+H+kZbUZ6AK2O-cUjwjUz_Gx_HY_BKfeeBqA@mail.gmail.com>
2023-01-02 18:48 ` Dan Cross [this message]
2023-01-02 19:53 ` [COFF] Re: [TUHS] A few comments on porting the Bourne shell Adam Thornton
[not found] ` <8ca17d52-a25a-dbbf-e1f0-d743b8884cfa@in-ulm.de>
[not found] ` <b689c244-3ea9-4fd6-bb45-a59d131071d6@app.fastmail.com>
[not found] ` <CAK0pxsH6bWTLVApE_vDhATmMgaF+nwc5D3pSz4srtwGS-8Ux_A@mail.gmail.com>
2023-01-03 23:02 ` [COFF] Re: [TUHS] Re: Command Line Editing in the Terminal Driver (Was: A few comments on porting the Bourne shell) Adam Thornton
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='CAEoi9W7a-qWv5=9zA6bTx+54R95LoaBV-LEDjrh0XgzeYif-xw@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=clemc@ccc.com \
--cc=coff@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).