|
|
|
|
|
by dmm
2562 days ago
|
|
> I believe your last statement is incorrect. If you distribute binary GPL'd software such as the Linux kernel you also have to provide the exact source used to generate those binaries. Because ip cameras are shipped with binary Linux kernel images they should also provide either the exact source used or an offer of how to get the source. > For example, programs compiled by gcc (GPL) are not considered derived works Yep you're right. We probably just misunderstood each other. I was specifically referring to GPL'd components like Linux & Busybox, not any applications that happen to be running on top of them. |
|
These kind of devices can lead to an interesting situation.
Let's say you make Linux-based IP cameras. You accompany every single one you ship with a CD-ROM containing the complete source code. This completely satisfies your GPL obligation with regard to that unit.
As a consumer, I buy one of your cameras. I have no use for the CD-ROM, check my trash collection company website to find out if CD-ROMs go in trash or recycling, and come next collection day it is gone.
A few months later I don't need the camera any more and sell it used on eBay.
The buyer eventually realizes it is a Linux-based camera and wants the source code.
Q: Who, if anyone, is obligated to provide that source code?
A: As far as I can tell, no one!
You are off the hook because you accompanied every binary copy you distributed with the source code. You would only be obligated to third parties if you had elected to distribute the binary without source and accompany it with a written offer to provide the source.
I'm off the hook because my distribution falls under the first sale doctrine, which basically says that if you own a lawfully made particular copy it is not a violation of copyright to sell that particular copy.