From: Neil Moore <neil@s-z.org>
To: linux-kernel@vger.kernel.org
Subject: Unix code in Linux
Date: Thu, 19 Jun 2003 18:43:22 -0400 [thread overview]
Message-ID: <E19T87m-000367-SF@dirac.s-z.org> (raw)
Slashdotter lspd pointed this out in a recent thread, thereby
demonstrating that slashdot isn't completely useless.
Compare:
/usr/src/linux/arch/ia64/sn/io/ate_utils.c in Linux
to:
unix/malloc.c in UNIX 6th Edition (page 25 of the Lions code,
lines 2522--2589)
atefree() is very obviously based on Unix's mfree(), and atealloc() on
malloc(). atefree()/mfree() even have the *same leading comment*. Of
course, there are some changes, but the overall structure and many of
the details remain.
The copyright notice on ate_utils.c says:
* This file is subject to the terms and conditions of the GNU General Public
* License. See the file "COPYING" in the main directory of this archive
* for more details.
*
* Copyright (C) 1992 - 1997, 2000-2002 Silicon Graphics, Inc. All rights reserved.
This code is obviously not a trade secret, since it has been published
in the 1996 version of the Lions book. However, it is copyrighted,
and the book's (C) notice says:
. . . SCO [i.e. the Santa Cruz Operation, not The SCO Group] has
granted a license to publish solely for the purpose of creating an
educational work. SCO grants no license for any other use of this
material . . . .
What kind of license did SGI have to the Unix code ca. 2000--2002?
Did the original malloc()/mfree() appear in BSD Lite (and thus lost to
USL/Novell in the settlement)? Is there any reason to replace this
code? Is there any reason not to replace this code?
--
Neil Moore: neil@s-z.org, http://s-z.org/~neil/
next reply other threads:[~2003-06-19 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 22:43 Neil Moore [this message]
2003-06-19 23:13 ` Miquel van Smoorenburg
2003-06-20 1:13 ` Neil Moore
2003-06-20 12:27 ` Jesse Pollard
2003-06-20 13:30 Manfred Spraul
2003-06-21 8:29 ` Manfred Spraul
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=E19T87m-000367-SF@dirac.s-z.org \
--to=neil@s-z.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®