mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank klein <frnk_kln@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Copyright / licensing question
Date: Wed, 2 Feb 2005 06:49:15 -0800 (PST)	[thread overview]
Message-ID: <20050202144915.94462.qmail@web42106.mail.yahoo.com> (raw)

Hi,
 I have got an offer to write a book on Linux
filesystems. In this I would like to cover existing
filesystems like ext3, xfs etc. I would also cover
embedded file systems such as jffs,ROMfs,cramsf etc.

I am having some licensing questions. It would be
really great if you can clarify on them

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 ??

2. I will write some custom drivers also for
illustration. For this I shall include kernel headers.
I also intend to put this in the book. From whom I
need to take permission regarding this ? The book will
be supported by a web-site. I have no problems in
releasing my custom code under GPL. But Am I violating
any license by putting the code in the book ?

Please CC me

Thanks

yours
Frank Klein



		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 

             reply	other threads:[~2005-02-02 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 14:49 Frank klein [this message]
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
2005-02-03 12:04 linux
2005-02-03 13:04 ` 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=20050202144915.94462.qmail@web42106.mail.yahoo.com \
    --to=frnk_kln@yahoo.com \
    --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®