6 ms·
> The userspace ABI is stable and intended not to cause anything targeting it to become a derived work. But once again, this seems to be a way in which the kern
by tsimionescu 5y ago
> The userspace ABI is stable and intended not to cause anything targeting it to become a derived work. But once again, this seems to be a way in which the kernel project seems to think it has the power to interpret the GPL. In their minds, targeting the userspace ABI doesn't make a derived work, but writing a module does, unless it only targets GPL_ONLY symbols, in which case for some reason it isn't.
I think this whole part applies as much to the text of the GPL itself as to the common Linux explanation. The GPL draws a distinction between dynamic linking, static linking, and use over a network or through a CLI style interface to decide if a work is a derived work of the GPL program. But, this distinction is just a novel legal theory proposal at best - there is nothing in copyright law that would make the GPL distinctions authoritative.
A license simply doesn't get to decide what constitutes a derived work - that's entirely up to copyright law itself and the court system to decide.
On the other hand, unless and until Congress decides to explicitly legislate how copyright should apply to software, the courts can very well take common industry practice into consideration for judging what is and is not a derived work of a program, and in this sense the Linux kernel developers' opinion is in no way less impactful than the proposals in the GPL itself.
Furthermore, in a matter of contract law (so assuming that the work is indeed judged to be derived according to copyright law, but now judging whether the GPL may offer some relevant exemptions), the stated intentions and interpretations of the parties of the contract are indeed relevant. If there is a long history of kernel developers publicly stating that as long as you are not using GPL_ONLY symbols, your work should not be considered to be under the purview of the GPL, and if this has not been commonly publicly contested, I think that in an actual trial this will matter much more than other interpretations of the GPL.
- temac 5y ago> I think this whole part applies as much to the text of the GPL itself as to the common Linux explanation. The GPL draws a distinction between dynamic linking, static linking, and use over a network or through a CLI style interface to decide if a work is a derived work of the GPL program. I just rechecked and it does not seem the GPLv2 does such things. I've not rechecked for v3, but from memory it does not do that either. I completely agree with you that clear intent is important though.
- mustache_kimono 5y agoI think she/he's trying to say -- the FSF draws such distinctions, but I think you're right the GPLv2 doesn't, and these are all just post-hoc rationalizations.
- tsimionescu 5y agoI explained more in another comment, but you're right, I had some confusion. The GPL itself makes no such claims, but the FSF does; also, the LGPL directly implies that programs that dynamically link an LGPL library are derived works of that library, but makes an exemption from the normal GPL requirements for such programs. Further, the FSF draws a distinction between linking (either statically or dynamically, which they believe makes your program a derivative work) and calling through a CLI or over a network (which they believe does not make your program a derivative work, except if the data structures exchanged through the CLI/network are complex enough).
- Borealid 5y agoI think there's some confusion in the above post. The relevant "derived work" definition for the purpose of linking isn't one stemming from copyright law, it's the one in the GPL itself. This is because the GPL defines what licensees are permitted to do with the licensed work, and it imposes restrictions on those rights. Copyright law by default lets you make very little use of the software - the GPL broadens that out to include various forms of use, if (and only if) "derived works" fall within its scope. You could ignore the GPL and static-link a piece of software to a GPLed library, but if you did so, you'd legally need a different right to use the GPLed library, because you hadn't complied with its license terms and so only have your minimal rights to use someone else's intellectual property. Said differently, the GPL doesn't try to apply itself to "derived works" because of some contralegal dictum they don't have a different creative origin. It merely says "you have two choices - license the things you link with OUR stuff under OUR terms, or you don't have the right to use our stuff".
- jarpadat 5y agoThe main problem with the interpretation that the GPL sets conditions for use of software is that it specifically claims it does not: > Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, Now there are some ways to try to do an end-run around this clause, it does raise some questions about how you get the right to run the program without "this License". But if we take the text seriously, it disclaims any restrictions on use. This is the part where the derivative work standard comes in. Because if the GPL doesn't set conditions on use, your use of the software doesn't require complying with that license. The GPL would only enter in if you are going beyond mere use, e.g. are you making a legal derivative work (not the GPL definition) (Not legal advice.)
- Borealid 5y agoI find it difficult to imagine a situation in which you could use the library without copying the library. How would you obtain the code to execute it? Someone must distribute it to you, and/or you must copy it. Those are the governed actions. EDIT: note that the GPL broadly doesn't impose restrictions on interacting with a program over a network ("using" a server), which is why the AGPL exists.
- hnfong 5y agohttps://lore.kernel.org/lkml/20031206211900.GA9034@thunk.org/ https://lore.kernel.org/lkml/20031206211900.GA9034@thunk.org... Theodore Ts'o (2003) [Incidentally this issue is at the heart of Oracle v Google. I find it fascinating how the tech community in general seems to not realize these are the same things.] Quote: But that aside, does the Open Source community really want to push for the legal principal that just because you write an independent program which uses a particular API, the license infects across the interface? That's essentially interface copyrights, and if say the FSF were to file an amicus curiae brief support that particular legal principle in an kernel modules case, it's worthwhile to think about how Microsoft and Apple could use that case law to f*ck us over very badly. It would mean that we would not be able to use Microsoft DLL's in programs like xine. It would mean that programs like Crossover office wouldn't work. It would mean that Apple could legally prohibit people from writing enhancements to MacOS (for example, how do all of the various extensions in Mac OS 9 work? They link into the operating system and modify its behaviour. If they are therefore a derived work of MacOS, then Apple could screw over all of the people who write system extensions of MacOS.)