On Mon, 2011-09-05 at 18:10 +0200, sean finney wrote: > > > > If every user has to be able to rebuild his own firmware files > then > > > > the manufacturer would be forced to open all code. > > > > > > I would say so. > > > > And you'd be TOTALLY wrong, unless the firware is a single program > where > > everything is linked together. If, as it almost certainly is, it is > just > > some sort of squashfs or similar that is unpacked at boot by the > kernel, > > then you have mere aggregation. > > That's kind of what I was getting at above. Please reconsider the > context of that answer, that as a given, the user needs to be able to > disassemble/reassemble the firmware and it was in question whether > that > was even possible. if you can't reliably take the image apart and put > it back together, what's the difference between that and an ELF file > with a really large .rodata section? Ok this would be a case of combining all the code in a single executable, which makes a big difference. Unfortunately you are still totally wrong wrt the question made. Nobody can force you to disclose code, if the firmware is not found compliant then the first option is to simply stop distributing the code completely. Of course if you want to keep distributing the code then you have to come in compliance, either by removing and replacing the GPLed portions (v2 or v3 makes no difference wrt linking executables) or by compatibly licensing your own code and distributing its source under the terms of the GPL. I find it hard to think that something including the linux kernel (which is the only reason to use cifs-utils) is transformed into a single executable all linked together. But I guess everything is possible. Simo. -- Simo Sorce Samba Team GPL Compliance Officer <simo@xxxxxxxxx> Principal Software Engineer at Red Hat, Inc. <simo@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
