The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Is OpenText Corporation the Current System V Copyright Holder?
Date: Thu, 14 Mar 2024 17:09:17 -0400	[thread overview]
Message-ID: <8b94da15-3ea0-4131-9f7c-fb1fcc064ea4@case.edu> (raw)
In-Reply-To: <ZfNaTWNpp1rRmfVF@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]

On 3/14/24 4:13 PM, Daniel Tameling wrote:

> People here might enjoy this first hand account of making MacOS fit
> for the certification:
> 
> https://www.quora.com/What-goes-into-making-an-OS-to-be-Unix-compliant-certified

Terry Lambert and Len Lattanzi (Len was the one I primarily dealt with).
He never did admit why he sent so many small posix-mode fixes, but I
appreciated them. This was mid-2004.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  reply	other threads:[~2024-03-14 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  0:33 [TUHS] " segaloco via TUHS
2024-03-14  2:13 ` [TUHS] " Marc Rochkind
2024-03-14  2:25   ` Warner Losh
2024-03-14  3:40   ` Steve Nickolas
2024-03-14 18:38     ` Stuff Received
2024-03-14 19:51       ` Warner Losh
2024-03-14 20:13       ` Daniel Tameling
2024-03-14 21:09         ` Chet Ramey [this message]
2024-03-14  8:31 ` John Cowan
2024-03-14 15:50 ` Warner Losh
2024-03-14 16:50   ` segaloco via TUHS

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=8b94da15-3ea0-4131-9f7c-fb1fcc064ea4@case.edu \
    --to=chet.ramey@case.edu \
    --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).