From: Daniel Tameling <tamelingdaniel@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Is OpenText Corporation the Current System V Copyright Holder?
Date: Thu, 14 Mar 2024 21:13:01 +0100 [thread overview]
Message-ID: <ZfNaTWNpp1rRmfVF@mail.gmail.com> (raw)
In-Reply-To: <aa163eab-db7e-0e91-e281-dc056f892acc@riddermarkfarm.ca>
On Thu, Mar 14, 2024 at 02:38:03PM -0400, Stuff Received wrote:
> On 2024-03-13 23:40, Steve Nickolas wrote:
> > On Wed, 13 Mar 2024, Marc Rochkind wrote:
> >
> > > Don't know the answer to your question, but last I knew the
> > > trademark (not
> > > the copyright) was transferred to The Open Group. They came up with a set
> > > of rules for what UNIX is and, as I understand it, for example, Linux is
> > > not a UNIX-like system, it is a UNIX system. (The Open Group isn't
> > > interested in implementations of the UNIX standard, only the standard
> > > itself.)
> >
> > Only those distros that paid them for the right to be called such.
>
> Not quite -- they do to pass the Single Unix Spec tests.
>
>
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
2 representive quotes:
"I was the tech lead at Apple for making Mac OS X pass UNIX
certification, and it was done to get Apple out of a $200M lawsuit
filed by The Open Group, for use of the UNIX™ trademark in
advertising.
The lawsuit was filed because the owner of Mac OS X Server kept
putting “UNIX” on the web site, and all other marketing collateral for
the Server product."
"If I were asked to do the same thing for Linux, it likely would take
five years, and two dozen people.
Linux is pretty balkanize, has a lot of kingdom building, and you have
to pee on everything to make it smell like Linux.
I could do the same in FreeBSD in about a year and a half, with a
dozen co-conspirators to run the changes through."
--
Kind regards,
Daniel
next prev parent reply other threads:[~2024-03-14 20:13 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 [this message]
2024-03-14 21:09 ` Chet Ramey
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=ZfNaTWNpp1rRmfVF@mail.gmail.com \
--to=tamelingdaniel@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).