| |||||||||||
Embedded Linux and the GPLEmbedded Linux and the GPLPosted Jun 11, 2003 19:43 UTC (Wed) by sethml (subscriber, #8471)Parent article: Embedded Linux and the GPL I find this portion of the article very misleading: In particular, a Linux-powered gadget is supposed to come with either (1) a copy of the source for the code running inside, or (2) a written offer to ship the source anytime in the next three years.This is simply not true. A Linux-powered gadget is supposed to come with a copy (or offer of a copy) of the source for the GPL code running inside, and any code directly linked to GPL code. In most cases this won't include the build system used to package software for the device and it won't include the source for any proprietary software that runs under the kernel. In many cases, an embedded device manufacturer can respond to a GPL query with "download the 2.4.20 kernel from kernel.org, apply patches found at http://..., and compile with this .config file." - which gives you access to the source to the GPL code they're using, but is not at all useful for changing any aspect of their device.
(Log in to post comments)
Embedded Linux and the GPL Posted Jun 11, 2003 23:17 UTC (Wed) by piman (subscriber, #8957) [Link] You were doing okay until your last point. You're correct in that they only need to provide the GPLd and linked-to-GPLd code, and not all code (unless other software in the system has a similar copyleft license, in which case, that must be followed for that code too). However, a pointer to kernel.org or other sources is NOT sufficient to satisfy the terms of the GPL. They have to provide it (or a written offer to receive it, from them, valid for three years) themselves.
|
|||||||||||