From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Brenner Subject: Re: GPLv2 for cifs-utils existing? Date: Sat, 03 Sep 2011 09:39:17 +0200 Message-ID: <4E61D9A5.6010303@arcor.de> References: <240043230.241860.1314945935851.JavaMail.ngmail@webmail12.arcor-online.net> <20110902064023.51a3c945@tlielax.poochiereds.net> <20110902124740.GB15846@cobija.connexer.com> Reply-To: brennersimon-KvP5wT2u2U0@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: In-Reply-To: <20110902124740.GB15846-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org> Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Thanks for all your answers so far! > That's to say that if you are distributing a single installable > firmware file for your router, and it contains GPL'd software, you would > arguably need to provide source for the entire work generating the > firmware file. And this isn't specific to v3 of the GPL either, AFAIK, > it's kind of the point of the license to begin with. So how is it when, say, a router manufacturer has its own (proprietary + closed) file format for the firmware files. Within the firmware he uses several GPL projects (v2 or v3) as well as some own closed projects which he doesn't want to be seen by everyone. Would the manufacturer then have to provide all source code, even its own which he originally wanted to keep private? How about the toolchain he used to compile all the stuff? If every user has to be able to rebuild his own firmware files then the manufacturer would be forced to open all code. Can you clarify that for me? Thanks! -Simon.