From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Does this mean Linux is now "officially branded UNIX"?
Date: Mon, 13 Mar 2017 11:15:43 +0100 [thread overview]
Message-ID: <58c6714f.IBfM/wqgeKrLugki%schily@schily.net> (raw)
In-Reply-To: <20170312150410.GH27536@naleco.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Josh Good <pepe at naleco.com> wrote:
> Hello all.
>
> I was perusing the list of officially branded UNIX systems, according to
> the "UNIX 03" specification and tests done by the Open Group, and I
> found there listed something called "Huawei EulerOS 2.0".
>
> https://www.opengroup.org/openbrand/register/xy.htm
>
> Intriguing, ain't it?
>
> So I went to Wikipedia, to see what it has to say about such a beast.
>
> https://en.wikipedia.org/wiki/Single_UNIX_Specification#EulerOS
>
> And I quote: "EulerOS 2.0 for the x86-64 architecture were certified as
> UNIX 03 compliant. The UNIX 03 conformance statement shows that the
> standard C compiler is from the GNU Compiler Collection (gcc), and that
> the system is a Linux distribution of the Red Hat family."
They would need to mention how they passed the test.
Given that there have been many problems last time, there was a collaboration
between the Linux people and the OpenGroup:
http://www.opengroup.org/personal/ajosey/tr20-08-2005.txt
I would guess that this company dod modify software inorder to become compliant.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2017-03-13 10:15 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 [this message]
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
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=58c6714f.IBfM/wqgeKrLugki%schily@schily.net \
--to=schily@schily.net \
/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).