The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tuhs@rops.org (Roger Willcocks)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Mon, 1 Mar 2004 00:46:35 -0000	[thread overview]
Message-ID: <005701c3ff26$a6425130$2301a8c0@burton> (raw)
In-Reply-To: <20040229232810.GI49757@wantadilla.lemis.com>

> 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.

Portions of this product are based in part on the work of the Regents of the
University of California, Berkeley and its contributors. Because Microsoft
has included the Regents of the University of California, Berkeley, software
in this product, Microsoft is required to include the following text that
accompanied such software:

Copyright 1985, 1988 Regents of the University of California. All rights
reserved.

Redistribution and use in source and binary forms are permitted provided
that the above copyright notice and this paragraph are duplicated in all
such forms and that any documentation, advertising materials, and other
materials related to such distribution and use acknowledge that the software
was developed by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived from this
software without specific prior written permission. THIS SOFTWARE IS
PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
FOR A PARTICULAR PURPOSE.
---snip---

although I would question whether there's an acknowledgement in all related
advertising materials...

--
Roger


----- Original Message ----- 
From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: "Paul Ward" <asmodai at ao.mine.nu>
Cc: "Wesley Parish" <wes.parish at paradise.net.nz>; <TUHS at minnie.tuhs.org>
Sent: Sunday, February 29, 2004 11:28 PM
Subject: Re: [TUHS] Microsoft, SCO, and a certain License



----- Original Message ----- 
From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: "Paul Ward" <asmodai at ao.mine.nu>
Cc: "Wesley Parish" <wes.parish at paradise.net.nz>; <TUHS at minnie.tuhs.org>
Sent: Sunday, February 29, 2004 11:28 PM
Subject: Re: [TUHS] Microsoft, SCO, and a certain License


> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
>



  reply	other threads:[~2004-03-01  0:46 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 [this message]
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='005701c3ff26$a6425130$2301a8c0@burton' \
    --to=tuhs@rops.org \
    /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).