Skip to contentSkip to conversation

Would I be violating the GPL?

DISCUSSION [email protected] 4 participants 4 messages Nov 2, 2005 – Nov 4, 2005

lore
Share & tools
lore
#0 lore raw

Amongst the various arguments here for declaring a binary kernel module a drived work based on including kernel headers, please take a step back and remember that what's sauce for the goose is sauce for the gander.

The basic question is, does the user of the headers require the permission of the author of the headers to distribute the resultant object code? If the answer is "no", then the question of the terms of that permission (the GNU GPL or otherwise) doesn't arise.

I'd like to argue that people interested in free software should want the answer to be "no", and should not try to establish precedents to the contrary, and that asserting the claim could boomerang unpleasantly.

Suppose EvilCo produces an EvilOS and provides a series of headers for interfacing to EvilOS. Further suppose that EvilOS is not very good about enforcing user/kernel separation and a lot of the headers describe kernel-internal data structures that a user might nonetheless want to hook into.

Now, if I write a piece of software that runs on EvilOS, or even a device driver to connect some hardware to EvilOS, do I want to need EvilCo's permission to distribute a percompiled version? Do I want them to claim proprietary rights in the source code because it refers to symbols defined in their headers?

Or would I rather that such names and references are considered "Scenes a faire" (standard boilerplate) for software that runs on EvilOS, and as such not subject to copyright law?

Looking at all the crap companies are trying to impose about publishing benchmarks, think before claiming that copyright law gives you some authority, lest that claim be used against you. I don't see such claims being widely asserted by commercial companies, so I'm strongly disinclined to try to start an arms race in that direction.

(There is a bit of that in the game console market, but that's enforced by not giving you the headers until you agree to an NDA with lots of conditions.)

In particular, it's a lot harder to argue that such a claim is ridiculous if you're making the same claim yourself. And it's not at all clear to me that the benefit is worth that cost.

Feel free to argue that the cost is worth it; what worried me was that it wasn't clear that people were considering the flip side of the arguments at all. (Of course, there are a lot more mailing list archives than I've read; I may just have missed it.)

#1 lore raw
Quoted 45 lines · On Wed, 2 Nov 2005 [email protected] wrote:

Amongst the various arguments here for declaring a binary kernel module a drived work based on including kernel headers, please take a step back and remember that what's sauce for the goose is sauce for the gander.

The basic question is, does the user of the headers require the permission of the author of the headers to distribute the resultant object code? If the answer is "no", then the question of the terms of that permission (the GNU GPL or otherwise) doesn't arise.

I'd like to argue that people interested in free software should want the answer to be "no", and should not try to establish precedents to the contrary, and that asserting the claim could boomerang unpleasantly.

Suppose EvilCo produces an EvilOS and provides a series of headers for interfacing to EvilOS. Further suppose that EvilOS is not very good about enforcing user/kernel separation and a lot of the headers describe kernel-internal data structures that a user might nonetheless want to hook into.

Now, if I write a piece of software that runs on EvilOS, or even a device driver to connect some hardware to EvilOS, do I want to need EvilCo's permission to distribute a percompiled version? Do I want them to claim proprietary rights in the source code because it refers to symbols defined in their headers?

Or would I rather that such names and references are considered "Scenes a faire" (standard boilerplate) for software that runs on EvilOS, and as such not subject to copyright law?

Looking at all the crap companies are trying to impose about publishing benchmarks, think before claiming that copyright law gives you some authority, lest that claim be used against you. I don't see such claims being widely asserted by commercial companies, so I'm strongly disinclined to try to start an arms race in that direction.

(There is a bit of that in the game console market, but that's enforced by not giving you the headers until you agree to an NDA with lots of conditions.)

In particular, it's a lot harder to argue that such a claim is ridiculous if you're making the same claim yourself. And it's not at all clear to me that the benefit is worth that cost.

Quoted 4 lines

Feel free to argue that the cost is worth it; what worried me was that it wasn't clear that people were considering the flip side of the arguments at all. (Of course, there are a lot more mailing list archives than I've read; I may just have missed it.)

This is certainly one of the most intelligent discourses I've heard in some time about the subject. Some claim that if it runs inside the kernel, it's "obviously" a derived work. It really isn't so obvious at all.

In fact, if the design of a driver, and its implementation requires a knowledge of only the driver's kernel interface and the hardware for which the driver is written, it is not derived by any stretch of the imagination. It's like writing code to interface with any API. You only need to understand the published interface and not its underlying principles of operation.

On the other hand, if you were to take an existing driver and modify it to control some new hardware, then it is obviously a derived work. The work was derived from the previous driver.

Anything else is not "obvious", but simply conjecture which may or may not be correct.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips). Warning : 98.36% of all statistics are fiction.
.

****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#2 lore raw
In reply to [email protected]
Quoted 4 lines · On Wednesday 02 November 2005 16:21, [email protected] wrote:

Amongst the various arguments here for declaring a binary kernel module a drived work based on including kernel headers, please take a step back and remember that what's sauce for the goose is sauce for the gander.

I think we've noticed the past few years of foaming looney attacks from SCO, yes. And Microsoft's own attempts to license its header files, and such.

Quoted 4 lines

The basic question is, does the user of the headers require the permission of the author of the headers to distribute the resultant object code? If the answer is "no", then the question of the terms of that permission (the GNU GPL or otherwise) doesn't arise.

Are you creating your source code based on somebody else's source code, or are you creating your source code based on something else (documentation, a defined API, etc).

Whether or not you include the header files is a relatively minor issue, really.

Quoted 2 lines

Suppose EvilCo produces an EvilOS and provides a series of headers for interfacing to EvilOS.

Been there, done that, watched it spawn groklaw.

Quoted 3 lines

Now, if I write a piece of software that runs on EvilOS, or even a device driver to connect some hardware to EvilOS, do I want to need EvilCo's permission to distribute a percompiled version?

Ask Microsoft. They were flirting with this kind of thing years ago. (Trying to make it so that their development tools couldn't be used to create open source.) This effort was about as widely ignored as their shrinkwrap license terms from the 1980's.

Quoted 3 lines

Do I want
them to claim proprietary rights in the source code because it refers to symbols defined in their headers?

Are those symbols documented? Or did they have to deeply study a copyrighted work in that claims rights over derived works in order to find out about those symbols in the first place?

Quoted 3 lines

(There is a bit of that in the game console market, but that's enforced by not giving you the headers until you agree to an NDA with lots of conditions.)

There's a difference between grounds for a lawsuit and a slam-dunk easy case you're confident you can win in a finite amount of time. If you're trying to prevent Foaming Nutballs, Inc. from ever having the slightest trumped up grounds for a suit, you're not going to be doing much.

Quoted 3 lines

In particular, it's a lot harder to argue that such a claim is ridiculous if you're making the same claim yourself. And it's not at all clear to me that the benefit is worth that cost.

I don't think anybody with a brain is arguing that #including the userspace (/usr/include) header files puts your Linux program under the GPL. And there's never been any alternative but to include the GPL linux kernel header files in those...

Quoted 4 lines

Feel free to argue that the cost is worth it; what worried me was that it wasn't clear that people were considering the flip side of the arguments at all. (Of course, there are a lot more mailing list archives than I've read; I may just have missed it.)

I've been considering the flip side of all these arguments for about five years, and considering them especially closely for the last two. :)

Rob

#3 lore raw
Quoted 8 lines · Rob Landley
Quoted 4 lines · On Wednesday 02 November 2005 16:21, [email protected] wrote:

Amongst the various arguments here for declaring a binary kernel module a drived work based on including kernel headers, please take a step back and remember that what's sauce for the goose is sauce for the gander.

I think we've noticed the past few years of foaming looney attacks from SCO, yes. And Microsoft's own attempts to license its header files, and such.

[...]

Quoted 7 lines
Quoted 3 lines

Do I want
them to claim proprietary rights in the source code because it refers to symbols defined in their headers?

Are those symbols documented? Or did they have to deeply study a copyrighted work in that claims rights over derived works in order to find out about those symbols in the first place?

To /study/ a copyrighted work to find out how it works and then write code against what you learned, you are /not/ copying anything. Sure, the original code's license might forbid such activities, but in Linux' case it certainly doesn't.

Signature · 4 lines
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513