Re: GPL V3 and Linux - Dead Copyright Holders

[Luke-Jr <luke@dashjr.org>]

On Monday 06 February 2006 22:38, Kyle Moffett wrote:
> On Feb 06, 2006, at 16:07, David Schwartz wrote:
> >> The LGPL deals with only derivative works. The GPL also deals with
> >> mere *linking*. If glibc were GPL'd, it would be illegal to make
> >> an OS based on it with a single C program incompatible with the GPL.
> >
> > The only way the GPL can control work Y because it affects work Z
> > is because Y is a derivative work of work Z. If it's not, then the
> > works are legally unrelated, and no matter what the GPL says, it
> > can't affect work Y.
>
> To say this more simplistically, the LGPL essentially says "Even if
> dynamic linking constitutes making a derivative work, we allow you to
> dynamically link, so long as the rules are followed for the LGPL code
> to which you link".  The GPL essentially says "If dynamic linking is
> making a derivative work, then these rules apply to the whole
> derivative work and all of its constituent parts".

Does the "if" clause exist? If not, then by distributing the original 
software, the distributor is agreeing to abide by the GPL terms for anything 
linking with it. If the linking code is not GPL-compatible, the distributor 
cannot legally distribute the GPL'd component.

> Whether or not an NVidia binary module is a derivative work is left
> up to the courts to decide.  It _may_ be legal (don't trust me,
> consult your lawyer) to have a very simple cross-platform interface
> and some BSD-licensed glue. 

They might have a legal loophole if dynamic linking doesn't constitute a 
derivative work *and* nVidia doesn't distribute Linux (thus does not need to 
agree to GPL terms).
-
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/