The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pepe@naleco.com (Pepe)
Subject: [TUHS] V8 - V10?
Date: Fri, 23 May 2008 16:05:28 +0200	[thread overview]
Message-ID: <20080523140526.GA22206@d600.naleco.com> (raw)
In-Reply-To: <mailman.5.1211508001.31735.tuhs@minnie.tuhs.org>

> Date: Thu, 22 May 2008 18:10:33 +0200
> From: "Jose R. Valverde" <jrvalverde at acm.org>
> Subject: Re: [TUHS] V8 - V10
> 
> 	Solaris has been open sourced and is heavily System V based. Novell 
> argues now SCO was not entitled to, and so the Sun-SCO agreement that made it
> possible is probably void.
> 
> [...]
> 	There remains the issue of the flow of SystemV licenses money to Novell
> after and if it is open sourced... I don't know how much that is, nor how much
> it might be 4-10 years from now when the SCO appeals are heard. So my evaluation
> is probably faulty.

I concur with your opinion.

If Novell could not get paid from The SCO Group of the percentage (about
90%) they are entitled to of the SVRX License Payment SUN made to The SCO
Group, and of the SVRX License Payment Microsoft made to The SCO Group
(because, you know, The SCO Group has filled for bankruptcy), then they are
probably going to action on the basis of said Licenses being void, or at
least in being void the part of such Licenses that allows to Sub-license
the material changing the terms of the License, or changing the License
altogether. According to this hypothesis on the future, in case The SCO
Group cannot find the money to pay Novell, Novell will probably try to
renegotiate such Licenses directly with SUN and Microsoft. Microsoft
will probably just return the material instead of paying for it (as they
don't need it), but SUN is in a totally different position.

SUN has now OpenSolaris, which was made possible by that License they got
from The SCO Group. So SUN will renegotiate and pay Novell to legalize
the SVRX License they got from The SCO Group which allowed them to
"open-source" Solaris.

Only after Novell gets that payment(s), either from The SCO Group or
SUN, will they consider "open-sourcing" the historical SVRX and
classical UNIX code. Otherwise, they could hardly monetize on it, as
they currently have the opportunity to do.

Regards,

-- 
Pepe
pepe at naleco.com




       reply	other threads:[~2008-05-23 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1211508001.31735.tuhs@minnie.tuhs.org>
2008-05-23 14:05 ` Pepe [this message]
2008-05-22  5:05 Aharon Robbins
     [not found] <mailman.5.1211335201.23443.tuhs@minnie.tuhs.org>
2008-05-21 18:52 ` Pepe
2008-05-21 19:31   ` John Cowan
2008-05-22  0:45     ` Pepe
2008-05-22  0:54       ` Larry McVoy
2008-05-22  4:59         ` Al Kossow
2008-05-22  9:09         ` Wesley Parish
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20 18:58 Aharon Robbins
2008-05-21 12:31 ` John Cowan
2008-05-22  5:07 ` Warren Toomey

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=20080523140526.GA22206@d600.naleco.com \
    --to=pepe@naleco.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).