From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Sun, 29 Feb 2004 20:34:03 +1300 [thread overview]
Message-ID: <200402292034.03414.wes.parish@paradise.net.nz> (raw)
I know the SCO topic's been done to death, and all, but I was thinking about
the Microsoft purchase of a Unix license (apparently) for their MS SFU
(Windows Services For Unix) which contrary to the plain meaning of the name,
is essentially a Unix (apparently OpenBSD, according to rumour) box on top of
the Windows kernel and Win32 API.
The question is, wouldn't that put Microsoft and the SCO Group in breach of
the settlement between AT&T and Berkeley? If Win SFU _is_ OpenBSD, and
Microsoft have bought a license to run it from the SCO Group of all people,
isn't that in effect picking a fight with Theo de Raadt?
This isn't definite, of course - some details I'm not sure of. But I think if
this is so, we have some very interesting few years to look forward to.
--
Wesley Parish
* * *
Clinersterton beademung - in all of love. RIP James Blish
* * *
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."
next reply other threads:[~2004-02-29 7:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 7:34 Wesley Parish [this message]
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
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=200402292034.03414.wes.parish@paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/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).