From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Microsoft, SCO, and a certain License
Date: Mon, 1 Mar 2004 09:58:10 +1030 [thread overview]
Message-ID: <20040229232810.GI49757@wantadilla.lemis.com> (raw)
In-Reply-To: <197818621475.20040229144830@ao.mine.nu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
On Sunday, 29 February 2004 at 14:48:30 +0000, Paul Ward wrote:
> Wes ðu hal Wesley,
>
> On Sunday, February 29, 2004, 7:34:03 AM, ure freond feorran awrat:
>
> WP> I know the SCO topic's been done to death, and all, but I was thinking about
> WP> the Microsoft purchase of a Unix license (apparently) for their MS SFU
> WP> (Windows Services For Unix) which contrary to the plain meaning of the name,
> WP> is essentially a Unix (apparently OpenBSD, according to rumour) box on top of
> WP> the Windows kernel and Win32 API.
>
> WP> The question is, wouldn't that put Microsoft and the SCO Group in breach of
> WP> the settlement between AT&T and Berkeley? If Win SFU _is_ OpenBSD, and
> WP> Microsoft have bought a license to run it from the SCO Group of all people,
> WP> isn't that in effect picking a fight with Theo de Raadt?
>
> Found in "ls":
> Copyright (c) 1991, 1993, 1994 The Regents of the University of California. All
> rights reserved. Copyright (c) 1996, 1998 Softway Systems Inc.
>
> $OpenBSD: strlen.c,v 1.3 1996/08/19 08:34:19 tholo Exp $
> $OpenBSD: strcpy.c,v 1.4 1996/08/19 08:34:14 tholo Exp $
> $OpenBSD: strncpy.c,v 1.2 1996/08/19 08:34:22 tholo Exp $
> $OpenBSD: strncmp.c,v 1.3 1996/08/19 08:34:21 tholo Exp $
> $OpenBSD: strlcpy.c,v 1.4 1999/05/01 18:56:41 millert Exp $
> $OpenBSD: fts.c,v 1.15 1998/03/19 00:30:01 millert Exp $
> $OpenBSD: strcmp.c,v 1.3 1996/08/19 08:34:12 tholo Exp $
> $OpenBSD: memset.c,v 1.2 1996/08/19 08:34:07 tholo Exp $
> $OpenBSD: strcat.c,v 1.4 1996/08/19 08:34:10 tholo Exp $
> $OpenBSD: memchr.c,v 1.2 1996/08/19 08:34:04 tholo Exp $
>
> There are a few OpenBSD CVS tags in libc.a as well.
Hmm. In that case, Microsoft *is* abusing the OpenBSD license by not
stating clearly that the code is derived in part from OpenBSD.
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/7a359a68/attachment.sig>
next prev parent reply other threads:[~2004-02-29 23:28 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 [this message]
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=20040229232810.GI49757@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).