From: Clem Cole <clemc@ccc.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: Alan Coopersmith <alan.coopersmith@oracle.com>,
Marc Rochkind <mrochkind@gmail.com>,
"tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection
Date: Thu, 27 Jun 2024 10:59:40 -0400 [thread overview]
Message-ID: <CAC20D2NMtgiWjFKkTRUWNVNkTjWeUpei=EYFgWuHKWexok-gcQ@mail.gmail.com> (raw)
In-Reply-To: <CALMnNGgbHpLEzi5m_fAph6+RPSuVqOO=jXpa4BDbUXXedcDdwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
Boy, I hate people rewriting history. As someone who lived it, it is just
not the case. I do not doubt that rms will try to take credit, but I think
a few of us there should send notes to Open Group.
FYI: Jim Issak was a marketing guy from Charles River Data Systems, which
is abbreviated C-R-D-S, and the firm always spelled out the letters. But
the rest of us pronounced it CRuDS—adding an "u" and pronouncing it—which I
was referred to in my first email.
When the P1003 committee was established, Jim was aware of the naming
issue, particularly after the CRDS experience. There was a great argument
in one of the early meetings about whether it should just be a "*Portable
Operating System*" as opposed to a "*Portable Operating System Interface*."
The concern was that we were starting with the System Call API or interface
[which we had inherited from /usr/group) but planned from the beginning
(even in /usr/group days) to be more than the system call API. As I said,
we started with the System API as that would be hard enough to find common
ground -- remember DEC, in particular, was pushing for VMS-like stuff (case
folding in file names). As you can see, we agree to use an add interface.
Hal's comment about it being called IEEEIX is strange. I do not remember it
ever being called that, and as an editor, I can say that I have no memories
of using that term. Could someone at IEEE in NYC try to call it the same? I
did not hear it or remember any document that used it, so I do not know
what he is talking about. It was not something I generated, and to have
done that would have taken edits.
I wonder if Open Group has the full SCCS files. I kept it in SCCS
originally and generated some of the documentation Jim needed for IEEE with
SCCS commands.
ᐧ
ᐧ
ᐧ
On Thu, Jun 27, 2024 at 10:29 AM Andy Kosela <akosela@andykosela.com> wrote:
>
>
> On Thursday, June 27, 2024, Chet Ramey via TUHS <tuhs@tuhs.org> wrote:
>
>> On 6/26/24 8:44 PM, Clem Cole wrote:
>>
>>> rms had nothing to do with the name posix. I have no idea where that
>>> comment came from.
>>>
>>
>> http://www.opengroup.org/austin/papers/posix_faq.html
>>
>>
>>
> Richard confirms it on his own website, too.
>
> https://www.stallman.org/articles/posix.html
>
> --Andy
>
[-- Attachment #2: Type: text/html, Size: 5140 bytes --]
next prev parent reply other threads:[~2024-06-27 15:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 17:56 [TUHS] " segaloco via TUHS
2024-06-26 18:32 ` [TUHS] " Ori Idan
2024-06-26 18:42 ` Marc Rochkind
2024-06-26 20:07 ` Aron Insinga
2024-06-26 23:28 ` Peter Yardley
2024-06-26 18:35 ` Marc Rochkind
2024-06-26 18:43 ` James Johnston
2024-06-26 18:52 ` segaloco via TUHS
2024-06-26 19:34 ` Heinz Lycklama
2024-06-26 20:01 ` Charles H Sauer (he/him)
2024-06-27 2:36 ` [TUHS] Re: arithmetic, " John Levine
2024-06-27 3:41 ` Charles H. Sauer
2024-06-26 20:29 ` [TUHS] " Marc Rochkind
2024-06-26 21:17 ` Rich Salz
2024-06-26 21:20 ` Alan Coopersmith via TUHS
2024-06-26 21:28 ` Warner Losh
2024-06-26 21:49 ` Rich Salz
2024-06-26 21:53 ` Steffen Nurpmeso
2024-06-27 0:44 ` Clem Cole
2024-06-27 1:11 ` [TUHS] Origin of the name POSIX (was: ANSI (C) vs IEEE (POSIX) Standards Body Selection) Greg 'groggy' Lehey
2024-06-27 2:12 ` [TUHS] " Ron Natalie
2024-06-27 2:37 ` Warner Losh
2024-06-27 14:19 ` Steffen Nurpmeso
[not found] ` <CAC20D2M+75ohjTPcTBmBkejeaWjQQjWCkf=4ZYrP4Bk0MCamKA@mail.gmail.com>
2024-06-27 3:02 ` Clem Cole
2024-06-27 3:03 ` Clem Cole
2024-06-27 3:08 ` Clem Cole
2024-06-27 8:20 ` Eric E. Bowles via TUHS
2024-06-27 11:56 ` John S Quarterman
[not found] ` <CAEoi9W4ZSVCVsJJ8pdBuBobeeXOkwsey0kM6DWBnPiuSd_7TQA@mail.gmail.com>
[not found] ` <CANCZdfoghuf4n=HDgRJXDJ5VqZ=rCtmq_0WadaR6kj8QmcoVQQ@mail.gmail.com>
2024-06-27 13:42 ` John S Quarterman
2024-06-27 11:58 ` Dan Cross
2024-06-27 14:34 ` Clem Cole
2024-06-27 15:05 ` [TUHS] Re: Origin of the name POSIX Heinz Lycklama
2024-06-27 13:57 ` [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection Steffen Nurpmeso
2024-06-27 14:22 ` Chet Ramey via TUHS
2024-06-27 14:29 ` Andy Kosela
2024-06-27 14:59 ` Clem Cole [this message]
2024-06-27 4:12 ` Wesley Parish
2024-06-27 4:52 ` G. Branden Robinson
2024-06-26 19:47 ` Aron Insinga
2024-06-27 5:02 ` Nevin Liber
2024-06-26 20:36 ` Stuff Received
2024-06-26 22:33 ` James Johnston
2024-06-26 20:32 ` Clem Cole
2024-06-26 22:04 ` Heinz Lycklama
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='CAC20D2NMtgiWjFKkTRUWNVNkTjWeUpei=EYFgWuHKWexok-gcQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=akosela@andykosela.com \
--cc=alan.coopersmith@oracle.com \
--cc=mrochkind@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).