From: Jesse Pollard <jesse@cats-chateau.net>
To: Neil Moore <neil@s-z.org>, linux-kernel@vger.kernel.org
Subject: Re: Unix code in Linux
Date: Fri, 20 Jun 2003 07:27:02 -0500 [thread overview]
Message-ID: <03062007270201.27242@tabby> (raw)
In-Reply-To: <E19T87m-000367-SF@dirac.s-z.org>
On Thursday 19 June 2003 17:43, Neil Moore wrote:
> 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 . . . .
I believe the original malloc/free code came from the "C programming language"
way back around 1975-79".
Almost all of the base allocators came out of that book. And it was listed
only as "a memory allocator", and the algorithms go back even farther. (I was
taught that one using a fortran array around 1973.. and was told then that
it had been used by IBM/CDC/... for memory allocation in assembler...)
Really.. there are only so many different ways to allocate memory, and this is
one of the most basic. Lisp interpreters always had the most elaborate and
complete ones, including this one. It is only slightly more complex than the
old stack "mark/release" allocator in Pascal.
next prev parent reply other threads:[~2003-06-20 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 22:43 Unix code in Linux Neil Moore
2003-06-19 23:13 ` Miquel van Smoorenburg
2003-06-20 1:13 ` Neil Moore
2003-06-20 12:27 ` Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
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=03062007270201.27242@tabby \
--to=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@s-z.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