From: random832@fastmail.com (Random832)
Subject: [TUHS] Does this mean Linux is now "officially branded UNIX"?
Date: Wed, 15 Mar 2017 11:16:23 -0400 [thread overview]
Message-ID: <1489590983.3467430.912238176.0034B198@webmail.messagingengine.com> (raw)
In-Reply-To: <58c94c4e.ywmehec4cxSvdppy%schily@schily.net>
On Wed, Mar 15, 2017, at 10:14, Joerg Schilling wrote:
> It seems that you do not understand POSIX the right way.
>
> POSIX does not invent new features but rather standardizes existing
> features
> present in existing UNIX implementations.
Yes but what I was suggesting was that this may have been a case of too
eagerly standardizing a new feature that one implementation had added
without considering whether there was a good reason to impose that
feature on other implementations.
I mean, surely not *everything* that SVr4 does is in POSIX. There must
therefore be some rationale for selecting which features, particularly
features that are not already universal, to standardize. So what was the
rationale for including this one?
next prev parent reply other threads:[~2017-03-15 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 15:04 Josh Good
2017-03-13 10:15 ` Joerg Schilling
2017-03-14 13:58 ` Nemo
2017-03-14 14:14 ` Joerg Schilling
2017-03-14 23:27 ` Josh Good
2017-03-15 11:11 ` Joerg Schilling
2017-03-15 13:42 ` Random832
2017-03-15 14:14 ` Joerg Schilling
2017-03-15 15:16 ` Random832 [this message]
2017-03-13 21:06 ` Michael-John Turner
2017-03-13 21:35 ` Clem Cole
2017-03-14 10:20 ` Joerg Schilling
2017-03-14 11:35 ` Tim Bradshaw
2017-03-13 21:51 ` Josh Good
2017-03-14 0:11 ` Wesley Parish
2017-03-13 22:30 ` Arthur Krewat
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=1489590983.3467430.912238176.0034B198@webmail.messagingengine.com \
--to=random832@fastmail.com \
/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).