From: Tom Perrine <tom.perrine+tuhs@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: On the uniqueness of DMR's C compiler
Date: Wed, 8 May 2024 10:49:02 -0700 [thread overview]
Message-ID: <CAJq=PCWR4zmqan=1m20CLDSvxu5G2Wk6pcpNTGeJnOQUDiOqJA@mail.gmail.com> (raw)
In-Reply-To: <fb33c2d0-bd7f-4730-9b4d-1313fd16dff1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi Jon (and others),
I was part of the KSOS (later KSOS-11 and KSOS-32) team at LOGICON, which
picked up a follow-on contract to use KSOS-11 in a true multi-level-secure
production environment. Our target was SYSTEM_LOW as TOP SECRET.
Yes, we used that compiler for all the KSOS kernel and all the trusted
user-space code.
KSOS-11 only ran on PDP-11/70, and it did use split I&D.
I have access to the KSOS-11 source code, and have been trying to rebuild
that OS, BUT I haven't been able to find that Modula compiler.
KSOS-11 was a very small kernel, but there was a set of libraries that
presented a UNIX system call interface, so it could run some PWB userspace
tools, if they were re-compiled.
I'm using the term KSOS-11, as there was a follow-on project (KSOS-32) that
ported the original PDP KSOS to 11/780. I wrote a completely new (simpler)
scheduler, the bootstrap and memory management layer for that one.
And, for "reasons", the entire KSOS project at Logicon was shut down just a
week or so after the first user login to KSOS-32.
KSOS-11 itself and some multi-level applications did ship to DoD customers,
and it ran MLS applications for the Navy and USAFE.
--tep
ps. Jon was kind enough to remind me that we had corresponded about this in
the past -and- to remind me to send to the list, and not just him :-)
On Wed, May 8, 2024 at 9:08 AM Jon Forrest <nobozo@gmail.com> wrote:
> There was also a Modula2 compiler for the PDP-11 from a university in the
> UK,
> propably York. It was used to some degree at Ford Aerospace for the
> KSOS secure Unix project. I think it required separate I&D.
>
> Jon
>
[-- Attachment #2: Type: text/html, Size: 2197 bytes --]
next prev parent reply other threads:[~2024-05-08 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 20:59 [TUHS] " Paul Ruizendaal
2024-05-07 22:07 ` [TUHS] " Rob Pike
2024-05-08 9:35 ` Paul Ruizendaal
2024-05-08 13:12 ` Rob Pike
2024-05-08 15:51 ` Clem Cole
2024-05-08 16:07 ` Jon Forrest
2024-05-08 17:49 ` Tom Perrine [this message]
2024-05-08 17:05 ` Adam Sampson
2024-05-08 17:45 ` Al Kossow
2024-05-08 18:12 ` Clem Cole
2024-05-08 18:12 ` Clem Cole
2024-05-09 1:27 ` Lawrence Stewart
2024-05-31 12:00 ` Paul Ruizendaal
2024-05-31 12:21 ` Peter Yardley
2024-05-08 11:09 ` Michael Kjörling
2024-05-09 20:40 ` Paul Ruizendaal via TUHS
2024-05-09 20:57 ` Al Kossow
2024-05-08 18:29 Douglas McIlroy
2024-05-10 17:28 ` Paul Winalski
2024-05-11 9:16 ` Ralph Corderoy
2024-05-11 13:42 ` G. Branden Robinson
[not found] <171519201646.4052234.694570138790187562@minnie.tuhs.org>
2024-05-09 3:39 ` Paul McJones
2024-05-09 3:46 ` Warner Losh
[not found] <171535904627.4052234.5321502833323676423@minnie.tuhs.org>
2024-05-10 18:55 ` Paul McJones
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='CAJq=PCWR4zmqan=1m20CLDSvxu5G2Wk6pcpNTGeJnOQUDiOqJA@mail.gmail.com' \
--to=tom.perrine+tuhs@gmail.com \
--cc=tuhs@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).