public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@hist.no>
To: linux@horizon.com
Cc: frnk_kln@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: Copyright / licensing question
Date: Thu, 03 Feb 2005 14:04:12 +0100	[thread overview]
Message-ID: <4202214C.6090907@hist.no> (raw)
In-Reply-To: <20050203120454.5815.qmail@science.horizon.com>

linux@horizon.com wrote:

>I'll respond in terms of U.S. law; if you want something else, please
>mention it.
>
>You might find a lot of useful information at
>http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter9/index.html
>http://www.usg.edu/admin/legal/copyright/#part3d3a
>http://en.wikipedia.org/wiki/Fair_use
>ttp://www.nolo.com/lawcenter/ency/article.cfm/ObjectID/C3E49F67-1AA3-4293-9312FE5C119B5806/catID/2EB060FE-5A4B-4D81-883B0E540CC4CB1E
>
>  
>
>>1. For explaining the internals of a filesystem in detail, I need to
>>   take their code from kernel sources 'as it is' in the book. Do I need
>>   to take any permissions from the owner/maintainer regarding this ?
>>   Will it violate any license if reproduce the driver source code in
>>   my book ??
>>    
>>
>
>This is exactly the sort of "Comment and criticism" that is anticipated
>and covered by the fair use exemption.  In judging whether the use is
>fair, 17 USC 107 says:
>  
>
Nice analysis, but is it necessary in this case?
GPL is somewhat special, in that it allows unlimited distribution of
unmodified and modified code, as long as:
1. The copyright notice remains - trivial to do in a book by keeping the
    copyright notices.  A book tend to have a copyright notice of its own,
    where he may mention the different licence/copyright for the code parts.
2. He offer the sources to anyone interested - again trivial because the
    book actually distributes the source in written form.  So he won't 
need to
    set up a ftp server the way binary vendors usually have to.

So I believe he'll be fine as long as he makes it clear that the source 
code listings
have a different copyright from the rest of the book - i.e. people can 
copy and use that
code in all the ways the GPL permits.

"Fair use" and such is nice to have, but one doesn't need to invoke it 
when the
source code in question already offer a unlimited redistribution 
licence.  Printing the
code in some book is just redistribution, after all.  He have to make 
sure he prints the GPL
along with the code, that's about it.

Helge Hafting



  reply	other threads:[~2005-02-03 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 12:04 Copyright / licensing question linux
2005-02-03 13:04 ` Helge Hafting [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-02 14:49 Frank klein
2005-02-02 15:07 ` Arjan van de Ven
2005-02-02 18:52 ` Rik van Riel
2005-02-02 23:11 ` Thomas Gleixner
2005-02-02 23:27   ` Charles Cazabon
2005-02-03  0:46     ` H. Peter Anvin
2005-02-03  8:40     ` Helge Hafting

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=4202214C.6090907@hist.no \
    --to=helge.hafting@hist.no \
    --cc=frnk_kln@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.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