The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Rochkind <mrochkind@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Is OpenText Corporation the Current System V Copyright Holder?
Date: Wed, 13 Mar 2024 20:13:56 -0600	[thread overview]
Message-ID: <CAOkr1zVwzT4FrOtJP+mJS=X_zz0wOnUgtS-PDsckxVTJHCs9hg@mail.gmail.com> (raw)
In-Reply-To: <9oGrJHb6s-fL1f5PDMKtnl-JN1Rea-AeDxEgkFiqJgAWEt7v6WUauLschmaq0ESqCnyAXwepvx7DKq9W6u3VRb8J5I8GJF7VmIpl87cy3-A=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]

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.)

Things change, and my information is a few years old. For all I know Elon
Musk owns it all now. ;-)

Marc

On Wed, Mar 13, 2024 at 6:34 PM segaloco via TUHS <tuhs@tuhs.org> wrote:

> Did some reading today, curious on the current state of things with AT&T's
> UNIX copyright genealogy.  The series of events as I understand it are:
>
> AT&T partners with Novell for the Univel initiative.
>
> Novell then acquires System V and USL from AT&T.
>
> Novell sells UNIX System V's source to SCO, but as the courts have ruled,
> not the copyright.
>
> Novell gets purchased by Microfocus.
>
> Microfocus gets purchased by OpenText Corporation.
>
> Does this make OpenText the current copyright holders of the commercial
> UNIX line from AT&T.
>
> What got me looking a bit closer into this is curiosity regarding how the
> opening of Solaris and the CDDL may impact publication of UNIX code between
> System III and SVR4.  I then felt the need to refresh on who might be the
> current copyright holder and this is where the trail has lead me.
>
> My understanding too is that Sun's release under the CDDL set the
> precedent that other sub-licencees of System V codebases are also at
> liberty to relicense their codebases, but this may be reading too far into
> it.  There's also the concern that the ghost of SCO will continue to punish
> anyone else who tries with costly-but-doomed-to-fail litigation.  Have
> there been any happenings lately with regards to getting AT&T UNIX
> post-PDP-11 opened up more in the world?  Reading up a bit on OpenText's
> business, they don't seem like they're invested in the OS world, seems that
> their primary sector is content management.  Granted, there's certainly
> under-the-radar trading of bits and pieces, but it would be nice to have
> some more certainty about what can happen out in the open.
>
> - Matt G.
>


-- 
*My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 2915 bytes --]

  reply	other threads:[~2024-03-14  2:14 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 ` Marc Rochkind [this message]
2024-03-14  2:25   ` [TUHS] " 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
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='CAOkr1zVwzT4FrOtJP+mJS=X_zz0wOnUgtS-PDsckxVTJHCs9hg@mail.gmail.com' \
    --to=mrochkind@gmail.com \
    --cc=segaloco@protonmail.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).