Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] Apollo Domain/OS
Date: Wed, 22 Jan 2020 13:42:34 -0500	[thread overview]
Message-ID: <CAC20D2NQOcd9adkOtczKG8KKK1p-ii66_48-vUr1-eHOepKfRA@mail.gmail.com> (raw)
In-Reply-To: <25618b7a-d831-fd56-80fb-41da1f65887f@nomadlogic.org>

moving to COFF

On Wed, Jan 22, 2020 at 1:06 PM Pete Wright <pete at nomadlogic.org> wrote:

> I also seem to remember him telling me about working on the patriot
> missile system, although i am not certain if i am remembering correctly
> that this was something he did at apollo or at another company in the
> boston area.
>
The Patriot was/is Raytheon in Andover, MA not Apollo (Chelmsford - two
towns west).   Cannot speak for today, but when it was developed the source
code was in Ada.   I knew the Chief Scientist/PI for the original Patriot
system (who died of a massive stroke a few years back -- my wife used to
take care of his now 30-40 yo kids when they were small and she was a tad
younger).

During the first Gulf War, he basically did not sleep the whole first
month.   As I understand it, Raytheon normally took 3-6 months per SW
release.  During the war, they put out an update every couple of days and
Willman once said they were working non-stop on the codebase, dealing with
issues they have never seen or have been simulated.  I gather it was quite
exciting ... sigh.   We got him to give a couple of talks at some local
IEEE functions describing the SW engineering process they had used.

Willman was one of the people that got me to respect Ada and the job his
folks had to do. To once told me, that at some point, Raytheon had a
contract supporting the Polaris System for the US Navy.   The Navy had long
ago lost the source.   They had disassembled and were patching what they
had.  Yeech!!!!  He also once made another comment to me ( in the late
1980s IIRC) that the DoD wanted Ada because they want the source to be part
of the specifications and wanted a language that was more explicit that
they could use for those specs.   I have no idea how much that has proven
to be true.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200122/a3db7ad2/attachment.html>


       reply	other threads:[~2020-01-22 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEoi9W4o-qPs9JskMCmca+c9M3pqcmL3kPcANQ4Jb=cwJkVkSg@mail.gmail.com>
     [not found] ` <DEE23024-04E3-4A37-AD17-41EC725B8B0A@eschatologist.net>
     [not found]   ` <CAC20D2MBb=UavxQkePdvC20W7WJUEaw9xcuGQGh-c=2rkAxP_Q@mail.gmail.com>
     [not found]     ` <20200121230025.GL15860@mit.edu>
     [not found]       ` <CAFH29tpWuSsx8V6ErSCXP_JU6wS9m18KQFFCciKYiUbJd5TUjA@mail.gmail.com>
     [not found]         ` <CABH=_VS6mEDC1gorq44T98P0CyfnvjNqjpUJFWbbSjdq7bAUMQ@mail.gmail.com>
     [not found]           ` <25618b7a-d831-fd56-80fb-41da1f65887f@nomadlogic.org>
2020-01-22 18:42             ` clemc [this message]
2020-01-22 18:51               ` pete

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=CAC20D2NQOcd9adkOtczKG8KKK1p-ii66_48-vUr1-eHOepKfRA@mail.gmail.com \
    --to=coff@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).