Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262492AbVBBS6W (ORCPT ); Wed, 2 Feb 2005 13:58:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262345AbVBBS4c (ORCPT ); Wed, 2 Feb 2005 13:56:32 -0500 Received: from mx1.redhat.com ([66.187.233.31]:1671 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S262471AbVBBSwT (ORCPT ); Wed, 2 Feb 2005 13:52:19 -0500 Date: Wed, 2 Feb 2005 13:52:18 -0500 (EST) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Frank klein cc: linux-kernel@vger.kernel.org Subject: Re: Copyright / licensing question In-Reply-To: <20050202144915.94462.qmail@web42106.mail.yahoo.com> Message-ID: References: <20050202144915.94462.qmail@web42106.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 979 Lines: 23 On Wed, 2 Feb 2005, Frank klein wrote: > 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 ?? Reproducing GPL code is legal, though you may want to make sure that the copyright notice on the book doesn't accidentally try to prohibit your readers from further distributing said code ;) -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/