From: jsnader@ix.netcom.com (Jon Snader)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Sun, 29 Feb 2004 11:25:49 -0500 [thread overview]
Message-ID: <20040229162549.GA90365@ix.netcom.com> (raw)
In-Reply-To: <20040229075430.GD49757@wantadilla.lemis.com>
On Sun, Feb 29, 2004 at 06:24:30PM +1030, Greg 'groggy' Lehey wrote:
>
> The most important detail is whether it was, in fact, derived from
> OpenBSD. This sounds very unlikely to me. If it were the case, why
> would they pay anything to SCO?
>
I have no idea whether Microsoft based SFU on OpenBSD or not, but
the conventional wisdom on Groklaw, the SCOX Yahoo Finance Board,
and similar domains that are following the SCO issue is that Microsoft's
purchase of the license was a backdoor way of financing an attack on
Linux. I don't whether that's true either, but it does provide an
answer to your question.
jcs
next prev parent reply other threads:[~2004-02-29 16:25 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 [this message]
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
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=20040229162549.GA90365@ix.netcom.com \
--to=jsnader@ix.netcom.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).