From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Does this mean Linux is now "officially branded UNIX"?
Date: Tue, 14 Mar 2017 11:20:47 +0100 [thread overview]
Message-ID: <58c7c3ff.58sDuibEjTWHXZvE%schily@schily.net> (raw)
In-Reply-To: <CAC20D2MO-fwNq2qg0DAbPr4NTX5aTwcN_+SQ=MWu5jiL2RVBwg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Clem Cole <clemc at ccc.com> wrote:
> ???Or in there case, negative value. RH likes to have the world believe
> they are Linux. They don't want anything lessening their brand.
> Certification would make RH < UNIX I suspect which is not what they want.
> Certification has always been about the ISV's, and if they can convince the
> ISV to test on their implementation directly (and they have) they don't
> need it.
RH did make several strange things that did make me wonder whether they are
really an OSS company, but they have a person working in the OpenGroup core
team.
This person (Eric Blake) usually helps to connect to developers from glibc, but
he of course knows about the problems GNU software has with the POSIX standard.
He is one of the active people in the teleconferences and he does not try to
bend POSIX to follow what is in use on RH-Linux.
I remember several cases where he helped to convince GNU people to make their
programs POSIX 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-14 10:20 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
2017-03-13 21:06 ` Michael-John Turner
2017-03-13 21:35 ` Clem Cole
2017-03-14 10:20 ` Joerg Schilling [this message]
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=58c7c3ff.58sDuibEjTWHXZvE%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).