From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Mon, 1 Mar 2004 11:23:42 +1030 [thread overview]
Message-ID: <20040301005342.GR49757@wantadilla.lemis.com> (raw)
In-Reply-To: <005701c3ff26$a6425130$2301a8c0@burton>
On Monday, 1 March 2004 at 0:46:35 -0000, Roger Willcocks wrote:
>> Hmm. In that case, Microsoft *is* abusing the OpenBSD license by not
>> stating clearly that the code is derived in part from OpenBSD.
>
> See Q306819 -
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306819 - Release
> Notes for Windows XP Contained in the Relnotes.htm File:
>
> ---snip---
> This product includes software developed by the University of California,
> Berkeley and its contributors.
>
> ...
> ---snip---
>
> although I would question whether there's an acknowledgement in all
> related advertising materials...
I suspect that that's sufficient. The advertising clause has always
been a bone of contention.
Greg
--
Note: I discard all HTML mail unseen.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20040301/bee44c87/attachment.sig>
next prev parent reply other threads:[~2004-03-01 0:53 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 [this message]
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=20040301005342.GR49757@wantadilla.lemis.com \
--to=grog@lemis.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).