From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from minnie.tuhs.org (minnie.tuhs.org [IPv6:2600:3c01:e000:146::1]) by inbox.vuxu.org (Postfix) with ESMTP id 01FF021143 for ; Wed, 8 May 2024 19:49:25 +0200 (CEST) Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 4F1E043327; Thu, 9 May 2024 03:49:21 +1000 (AEST) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) by minnie.tuhs.org (Postfix) with ESMTPS id 2CC1043326 for ; Thu, 9 May 2024 03:49:16 +1000 (AEST) Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-51f12ccff5eso6030687e87.1 for ; Wed, 08 May 2024 10:49:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715190554; x=1715795354; darn=tuhs.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=sf//22w9D5WWY+SOuUFpD2ytNy5poPfH4glq7R0auw4=; b=gbXBIV7wVBaVzNldkQwLxWfoP/VTaXivWxWiQzKHDawqgysGOJiSkr4ZPRN4CPltdG RNP28WpCaH6qfPPzTlpgFuX2atvH82zOJnBazXVCNxB3WegfNjhaoipY1jdJI/jvbD+c DeW9HWwKfyEGFqOgfyfkRYOMgY1E2SV6mT3KCAKzu3uUpxaHsLOi8CV8tnNKQdinkPUP MQYnsYQGAAQY0sqsRiCnXcOF5rc+nsfsV4TLQQ4Mcd28cKn30h3m35pYIJqJudO2jdMh RqE2WtmhP7E6zuhBf1JnxCQrNiYUJeGSt1PEa1uFa5lgrnxQCOslBaxSXJ6jL50Jx/Hz XzSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715190554; x=1715795354; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=sf//22w9D5WWY+SOuUFpD2ytNy5poPfH4glq7R0auw4=; b=SzK5iUqZRtCvJRnHJb8+xbIU+Gbz57gDfNdh56UUBeC2/AmYvgqPtnxmTehCPWo8id liUj+Iufv0qRFaXjLDC/I3OumpllNb3Doc27Mb7ue+/kas8sb+THOBTNmLlY3mYQsPAP x2lOuDPDSAyhI2g8XrzQv/3bpYGCwemvYiZKL9HOhk62PelEJVVFOvPci/vmeUgKM3Hv ipoUZvhhPaPlttPrlKHiQqEMJNI71adsH8RSWGhEBN7EPeo5lBvQZYlcN6uO2EndyqcU VRt82eEc5ynEBTYarPhCFlUKTJwLVDZALfdH5PHYwD3FDnKE7uG9okW8YNmK3A4o4dPw cPug== X-Gm-Message-State: AOJu0YzmDlxITHVDG5OJzOnpoWK2A1VEn/UHAZY6OQ32sHcjwSejMCj+ XyzRihzkle56vM4tN51U2n5/FxEfIhIi8h4pMGfFbSV4cWTB4MTxiXq3WflS/W0DXXRYJ0G4LQX +vqOjlTol0C+VUxBVvzouu9UiSZaRrkWB X-Google-Smtp-Source: AGHT+IFnvH892sWZCxoCHnFSLehQ6h6P/oHcmUBzmub3m5lKYwFrxcXmwGhuI9cewu0eKDJN7brcwTqwABKpA58ivDE= X-Received: by 2002:ac2:42cb:0:b0:51b:5490:1b3a with SMTP id 2adb3069b0e04-5217cc45912mr2030412e87.53.1715190553489; Wed, 08 May 2024 10:49:13 -0700 (PDT) MIME-Version: 1.0 References: <18efd14f-4da6-4771-ad6a-901c6cb6105d@planet.nl> <57a37626-728c-4f34-b08b-a4f521f1db03@planet.nl> In-Reply-To: From: Tom Perrine Date: Wed, 8 May 2024 10:49:02 -0700 Message-ID: To: tuhs@tuhs.org Content-Type: multipart/alternative; boundary="000000000000a9baf50617f4eba5" Message-ID-Hash: LJEYFEZHPFVOOYSPLX63KPJB6EXE7E6D X-Message-ID-Hash: LJEYFEZHPFVOOYSPLX63KPJB6EXE7E6D X-MailFrom: tom.perrine@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: On the uniqueness of DMR's C compiler List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000a9baf50617f4eba5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Jon Forrest 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 > --000000000000a9baf50617f4eba5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 environm= ent. Our target was SYSTEM_LOW as TOP SECRET.

Yes,= we used that compiler for all the KSOS kernel and all the=C2=A0trusted use= r-space code.

KSOS-11 only ran on PDP-11/70, and i= t 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 w= as a very small kernel, but there was a set of libraries that presented a U= NIX system call interface, so it could run some PWB userspace tools, if the= y were re-compiled.

I'm using the term KSOS-11= , as there was a follow-on project (KSOS-32) that ported the original PDP K= SOS 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 custome= rs, and it ran MLS applications for the Navy and USAFE.

--tep

ps. Jon was kind enough to remind me t= hat we had corresponded about this in the past -and- to remind me to send t= o the list, and not just him :-)


On Wed, May 8, 2024 = at 9:08=E2=80=AFAM Jon Forrest <nobo= zo@gmail.com> wrote:
There was also a Modula2 compiler for the PDP-11 from a univers= ity 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
--000000000000a9baf50617f4eba5--