The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wb@freebie.xs4all.nl (Wilko Bulte)
Subject: [TUHS] IANAL. Kimball has ruled
Date: Thu, 17 Jul 2008 19:04:07 +0200	[thread overview]
Message-ID: <20080717170407.GA95756@freebie.xs4all.nl> (raw)
In-Reply-To: <alpine.LNX.1.10.0807171024440.14160@xenau.zenez.com>

Quoting Boyd Lynn Gerber, who wrote on Thu, Jul 17, 2008 at 10:33:12AM -0600 ..
> On Thu, 17 Jul 2008, Jose R. Valverde wrote:
> > I have to change my opinion on SCO to consider them now UNIX zealots. As 
> > I read it, I guess Sun was worried by possibly non-ATT code in SVRX, and 
> > may be by Novell's assertions, so they shielded themselves: if I'm not 
> > wrong that means OpenSolaris is safe and the responsibility for that 
> > relies totally on SCO.
> > 
> > SCO thus was willing to take any risks regarding third parties with 
> > respect to opening up SVRX derived Solaris. That was very bold and 
> > valiant (though seeminglymay be wrong) from them. Why they decided to 
> > allow open sourcing via Sun instead of Unixware is their choice. I guess 
> > they thought it would play better for them to sell a 'closed' Unixware 
> > as an 'enhanced' or 'better product' than open solaris. It also fits 
> > within Caldera's previous opening other ancient UNIX.
> > 
> > My guess is they were for opening SVRX as a way to increase market share 
> > of UNIX against LINUX but preferred Sun to open _their_ version instead 
> > of opening SCO's own. At the same time they must have thought that a 
> > combined attack on Linux would drive most people off Linux towards 
> > opensource UNIX and that corporate interests would prefer SCO's closed 
> > Unixware to Sun's open source solution in line with tradition.
> 
> Caldera/SCO was trying to get everything opensourced.  They released 
> OpenUNIX 8.0 which was UnixWare 7.1.2.  They had reached an agreement with 
> every one and were about to release everything a the big expo in Jan/Feb 
> east cost.  It was to be a joint IBM/SCO announcement, when IBM suddenly 
> decided against it and were addamanly now doing everything to stop it.  
> IBM was the "big bad guy".  What I never could understand is how the roles 

** lawyers **

that is the keyword here :)

Wilko



  reply	other threads:[~2008-07-17 17:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  8:18 Jose R. Valverde
2008-07-17 15:55 ` Gregg C Levine
2008-07-17 15:58   ` Larry McVoy
2008-07-17 16:18   ` Bryan Cantrill
2008-07-17 17:12     ` John Cowan
2008-07-17 17:27       ` Larry McVoy
2008-07-17 17:32         ` Michael Kerpan
2008-07-17 16:33 ` Boyd Lynn Gerber
2008-07-17 17:04   ` Wilko Bulte [this message]
2008-07-17 20:51   ` Michael Davidson
     [not found] <mailman.1871.1216314893.89381.tuhs@minnie.tuhs.org>
2008-07-17 19:55 ` Pepe
2008-07-17 20:22   ` Bryan Cantrill
2008-07-17 22:30     ` Pepe
2008-07-17 20:40   ` Boyd Lynn Gerber
2008-07-18 14:10   ` Jose R. Valverde
2008-07-18 17:03 Michael Davidson

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=20080717170407.GA95756@freebie.xs4all.nl \
    --to=wb@freebie.xs4all.nl \
    /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).