The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jcapp@anteil.com (Jim Capp)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Fri, 5 Mar 2004 10:50:22 -0500	[thread overview]
Message-ID: <20040305155022.GA24027@anteil.com> (raw)
In-Reply-To: <1078501214.3788.20.camel@ablate.merit.edu>

On Fri, Mar 05, 2004 at 10:40:14AM -0500, Larry J. Blunk wrote:
> 
>  Microsoft and SCO have been very coy about what it is that Microsoft
> actually licensed.  I believe the closest they have come to explaining
> it can be found in a Byte interview by Trevor Marshall --
> http://www.byte.com/documents/s=8276/byt1055784622054/0616_marshall.html
> where Chris Sontag of SCO is quoted as saying that Microsoft merely
> licensed an "applications interface layer."
> 
>   I take this to mean they are probably talking about header files
> like errno.h, signal.h, etc.   I believe that Microsoft development
> products have iterations of these and they only have Microsoft copyright
> notices in them (no AT&T or BSD notices).   SFU would have them
> as well, although I'm not sure what copyright notices are on those.
> SCO claims that the lack of a copyright notices violates the USL vs.
> BSDi settlement.  Of course, this claim is extremely tenuous (since
> Microsoft's headers files origination likely predates the settlement
> and were derived independently from public sources).
> 
>   In the end, I strongly suspect this was a way for Microsoft to funnel
> money to SCO to attack Linux as opposed to Microsoft claims of
> "respecting Intellectual Property Rights."
>  

I think it's very odd that Microsoft would need a license from SCO
at all.  Isn't it true that before there was SCO, there was Microsoft
XENIX?  I find it hard to believe that Microsoft would have divested itself
of all rights in XENIX (including the headers above) when spinning off
SCO.




  reply	other threads:[~2004-03-05 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29  7:34 Wesley Parish
2004-02-29  7:54 ` Greg 'groggy' Lehey
2004-02-29 16:25   ` Jon Snader
2004-02-29 23:54     ` Kurt Wall
2004-02-29 14:48 ` Paul Ward
2004-02-29 23:28   ` Greg 'groggy' Lehey
2004-03-01  0:46     ` Roger Willcocks
2004-03-01  0:53       ` Greg 'groggy' Lehey
2004-03-05 15:40 ` Larry J. Blunk
2004-03-05 15:50   ` Jim Capp [this message]
2004-03-05 21:36 [TUHS] Microsoft,SCO,and " zme
2004-03-05 23:38 ` Greg 'groggy' Lehey

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=20040305155022.GA24027@anteil.com \
    --to=jcapp@anteil.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).