public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: davids@webmaster.com
Cc: "Jeff V. Merkey" <jmerkey@utah-nac.org>,
	alex@alexfisher.me.uk, linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Wed, 16 Nov 2005 09:39:34 -0700	[thread overview]
Message-ID: <437B60C6.7040308@wolfmountaingroup.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKIEDBIBAB.davids@webmaster.com>

David Schwartz wrote:

>>If you even take 2 minutes to actually inspect the NVIDIA video
>>driver sources
>>(extract the .run file with --extract-only, and cd to usr/src/nv)
>>you'll find
>>the "glue" which is provided as source, but not under the GPL,
>>does indeed
>>#include kernel headers at compile time.
>>
>>It does not distribute them, however, but it is completely nonsensical to
>>class this as having "no dependency". It has a compile time and runtime
>>dependency on the current kernel. What driver wouldn't?
>>    
>>
>
>	If I write source code that includes "stdio.h", I can do whatever I want
>with that source code, and I'm not bound by the license of any particular
>file that happens to be called "stdio.h". On the other hand, if I compile
>that source code including *your* "stdio.h" file, the resulting compiled
>output is likely a derived work of your file.
>
>	So the source code is not a derivative work of any GPL'd files. The
>compiled driver may be, precisely because it contains bits and pieces of the
>header files.
>
>	DS
>
>
>
>  
>
Correct.

Jeff

  reply	other threads:[~2005-11-16 18:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 17:49 Would I be violating the GPL? Alexander Fisher
2005-11-01 16:43 ` Jeff V. Merkey
2005-11-01 19:15   ` Alistair John Strachan
2005-11-16 15:26     ` David Schwartz
2005-11-16 16:39       ` Jeffrey V. Merkey [this message]
2005-11-01 20:32   ` Rob Landley
2005-11-01 20:46   ` Arjan van de Ven
2005-11-01 19:00 ` Michael Buesch
2005-11-01 17:44   ` Jeff V. Merkey
2005-11-01 19:12     ` Michael Buesch
2005-11-01 20:46       ` Alexander Fisher
2005-11-01 21:06         ` linux-os (Dick Johnson)
2005-11-02  9:49         ` Giuliano Pochini
2005-11-02 14:54           ` Alex Lyashkov
2005-11-02 15:29             ` Nix
2005-11-02 15:42               ` Alex Lyashkov
2005-11-02 16:16               ` linux-os (Dick Johnson)
2005-11-02 17:26                 ` Nix
2005-11-02 15:55             ` Giuliano Pochini
2005-11-10 19:02           ` Jan Engelhardt
2005-11-10 19:12             ` Lennart Sorensen
2005-11-17 21:23               ` Jan Engelhardt
2005-11-18 15:19                 ` Lennart Sorensen
2005-11-18 15:25                   ` Jan Engelhardt
2005-11-18 21:55                   ` Petr Vandrovec
2005-11-01 22:04     ` Rob Landley
2005-11-01 19:58   ` Lee Revell
2005-11-01 20:30     ` Jeff V. Merkey
2005-11-01 20:57     ` Alexander Fisher
2005-11-02 16:12 ` Stuart MacDonald
2005-11-03 12:44 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 22:21 linux
2005-11-02 22:47 ` linux-os (Dick Johnson)
2005-11-03  3:50 ` Rob Landley
2005-11-04  0:57   ` Horst von Brand

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=437B60C6.7040308@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=alex@alexfisher.me.uk \
    --cc=davids@webmaster.com \
    --cc=jmerkey@utah-nac.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