[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: non-free firmware in kernel modules, aggregation and unclear copyright notice.

> > The GPL applies to distributing a Linux binary I just made even
> > though nobody ever chose to apply the GPL to the binary I just made
> > only because the binary I just made is a derivative work of the
> > Linux kernel, and the authors of that work chose to apply the GPL to
> > it.

> How can the binary be a derivative work when it does *not* contain
> firmware, but suddenly cease to be a derivative work if one *does*
> add firmware into it?

	Because, the argument would go, the binary with the firmware linked in is
not a work, it is two works that are aggregated because there's a license
boundary between them. The argument would be that the binary with the
firmware is *a* *derivative* *work* of the Linux kernel source. The "a" is a
critical part of the argument that cannot be omitted. Showing that the
linked binary was two works would be sufficient to significantly weaken the
argument that it can't be distributed.

	You can't argue that only the GPL gives you the right to distribute the
result, regardless of what it is, because there are other sources of such
rights. These include fair use, first sale, and the fact that the law does
not create a special right to restrict the distribution of lawfully-created
derivative works (to licensees of the original work).

	My point is not simply that the question of whether or not linking creates
a single work that is a derivative work of all the things linked is
important to the question of whether you can distribute GPL'd works linked
with non-GPL'd works. And the standard is copyright law, not what the GPL
says. (Though that's also important, because then you would have even more


Reply to: