From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5216 invoked from network); 2 May 2022 14:54:06 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 2 May 2022 14:54:06 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id CB0FD9D456; Tue, 3 May 2022 00:54:04 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 4431B9D431; Tue, 3 May 2022 00:50:58 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="gEJEuLRG"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id B0F709D431; Tue, 3 May 2022 00:50:55 +1000 (AEST) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) by minnie.tuhs.org (Postfix) with ESMTPS id E05899CE23 for ; Tue, 3 May 2022 00:50:54 +1000 (AEST) Received: by mail-wr1-f42.google.com with SMTP id e24so19854855wrc.9 for ; Mon, 02 May 2022 07:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JdzNhYstaI3TAlA+nKHZs5Kj8UJUkZph1aHQPcRjdVo=; b=gEJEuLRGvhlk2BdGKJJUYXKtKYKCpoX4fpFb9DLe6Ovb1Ssi3AGZdfTWdKUx0G6L5h fhLLnKnhWxhWD/1eSONMpxaA01WwTLNzrWoEzHXTS5mS+ZZN9x5kR7GpXcSSx7M6jtkR OHNsUEzVlDv8aWpQPsJRlcQcQi9W3g/xNz93eIIaCSQ4fPJv8A4RZv9Rp/H7HKrTd6gO cXiBnVAjCdcUY5L5aq2Up4iLH2FPUi9nPsL6l23P/R3DlNCzrrJjIxvTNno73lDX2ltR 4QncC56mBXWvIOOTI4udOgkK4+EeuBeWAIX0r6UeLskdO+BnFR7IUWIkGcarfB/9JAuu atkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JdzNhYstaI3TAlA+nKHZs5Kj8UJUkZph1aHQPcRjdVo=; b=cDjnGkyBw2tb4fLZL0jrWilL94NDmeLOut6jDeLwKxtcoQSAzlXx7NWWWH+0BBPfDp uTaVGptp3nhnShVjUkA754sLYc2clazQuiO25h8TfEsnyU8pBQXerFQBa2oi3JrOlUd5 LygBxW6/GAxRZWZqnK0E7Az5PsSY/LG9ZVLhBK80LduRAAYCo29NaUy5ACA5oKGy+Mc6 h0W8IzPwLTsXKCEzidiIJep4h9FMHf8xrg0iyw7nrFXRGuwzNd7FOAD5LVf4R/kSaeSi bylAgQDdf9RHNlXa0ePHq9J5sV1+5hWxt4Dm8hw5GtHCUU/ZxAlDEZgvv1z1hcUeEyDz omTg== X-Gm-Message-State: AOAM531ReDgty0nyLv1eEIW+F0BbaSdxO2B8Qnaa5zgfktEvN86t7sCx SmxV3lC5YzEeoDeqsaBevIS2SxchK+dLBMprLGICJLCXa8A= X-Google-Smtp-Source: ABdhPJzbSgQpiWM9hKAnSDrJ8wAlLhiiGL8bGNiaZuRtfIxk9emf1KB9L9IWIqCQxbUnafc+Faz8cg7tmyKrQagipQg= X-Received: by 2002:adf:d234:0:b0:20a:d063:e48 with SMTP id k20-20020adfd234000000b0020ad0630e48mr9651200wrh.112.1651503053273; Mon, 02 May 2022 07:50:53 -0700 (PDT) MIME-Version: 1.0 References: <57977CE7-DDCC-4861-BBD2-843B9B9F51C2@ronnatalie.com> <202205020242.2422g30m074857@ultimate.com> In-Reply-To: From: ron minnich Date: Mon, 2 May 2022 07:50:41 -0700 Message-ID: To: Miod Vallat Content-Type: text/plain; charset="UTF-8" Subject: Re: [TUHS] First Unix-like OSes not derived from AT&T code? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" Someone mentioned the weird message format on AIX. IBM, in many things, was out there ahead of everyone. One of those areas was in "the message catalog", sample doc here: https://www-40.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3SA380673/$file/ieam600_v2r3.pdf For every message there was a short identifier that was the message catalog id, the one that sticks in my mind from years as an operator is IEA013I, which is not in that doc ... IEA013E is, however. This was useful for internationalization. IOW, IBM got it i8n well ahead of a lot of us, in the 19[67]0s or so? The message catalog did not change; the allegedly human readable message was in the local language, if that applied. Which comes to a prank we pulled on a friend. One evening in 1977, we replaced all shell messages with IBM message catalog style messages, and then set that as their login shell. As you might guess, they were *not* amused ;-) On Mon, May 2, 2022 at 7:16 AM Miod Vallat wrote: > > > The RT 4.3 port was called AOS (for the, "Academic Operating System"). It > > was mostly Tahoe with NFS and came with most of the sources, but some bits > > were distributed only as object code: I believe some of the MM bits? > > Perhaps the MMU code? I vaguely recall this being one of the things people > > had a hard time with when trying to port Reno and 4.4 to the RT. > > What was delivered as binary was the Advanced Floating-Point Accelerator > microcode. > > At the end of the AOS work circa 1996, most of the kernel was 4.4, > except for the network stack which was 4.3-Reno, and the VM system which > was still 4.3 (hence no mmap). > > > The port was fairly faithful; the C compiler was a bit strange "High C" or > > "Hi C", bit GCC was available after a while, but had some bug and could not > > compile the kernel. > > The compiler was Metaware High C. GCC could not be used to compile the > kernel sources unchanged, because one of the locore->trap.c paths was > relying upon the stack layout used by the compiler. With that fixed, gcc > could be used to build a working kernel. > > Miod