Driver Model
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
On Wed, 03 Sep 2003 20:00:24 +0200, you wrote in linux.kernel:
Quoted 3 lines
The fact that
GPL_ONLYhorse sh*t exists means there is a restriction on usage. So "GPL_ONLY" has in effect violated GPL, by imposing restrictions of usage.
Where is the restriction? You get the source code, you can roll your own and remove the GPL_ONLY stuff. Apart from that I do not recall to have seen anything about restrictions of usage in the GPL... the only thing it tries to prevent is the source code becoming proprietary.
Signature · 2 lines
Ciao, Pascal
Quoted 10 lines · Pascal Schmidt
On Wed, 03 Sep 2003 20:00:24 +0200, you wrote in linux.kernel:
Quoted 3 lines
The fact that
GPL_ONLYhorse sh*t exists means there is a restriction on usage. So "GPL_ONLY" has in effect violated GPL, by imposing restrictions of usage.Where is the restriction? You get the source code, you can roll your own and remove the
GPL_ONLYstuff. Apart from that I do not recall to have seen anything about restrictions of usage in the GPL... the only thing it tries to prevent is the source code becoming proprietary.
Pascal,
I agree with you and you make the point clear!
There are people who have issued letters to big linux distributors in the US about changing a symbol types. That is a restriction for usage, in my opinion.
Cheers,
Andre
Quoted 9 lines
On Wed, 03 Sep 2003 20:00:24 +0200, you wrote in linux.kernel:
Quoted 4 lines
The fact that
GPL_ONLYhorse sh*t exists means there is a restriction on usage. So "GPL_ONLY" has in effect violated GPL, by imposing restrictions
of usage.
Quoted 4 lines
Where is the restriction? You get the source code, you can roll your own and remove the
GPL_ONLYstuff. Apart from that I do not recall to have seen anything about restrictions of usage in the GPL... the only thing it tries to prevent is the source code becoming proprietary.
If the GPL_ONLY stuff is a license enforcement scheme, the DMCA prohibits
you from removing it. If the GPL_ONLY stuff is not a license enforcement scheme, nothing prohibits you from stamping your module GPL when it's not.
However, the GPL (section 2b) prohibits you from imposing any restrictions
other than those in the GPL itself. The GPL contains no restrictions that apply to mere use and the GPL_ONLY stuff affects use, so it can't be a license restriction, hence there is no restriction to enforce.
I don't see anything preventing a GPL'd work from containing code that
imposes restrictions actually contained in the GPL and using the DMCA to enforce them. But it would have to be a restriction contained in the GPL itself, and there is no restriction about what code you can use with a GPL'd work.
DS
Quoted 2 lines · David Schwartz
If the
GPL_ONLYstuff is a license enforcement scheme, the DMCA prohibits you from removing it.
-ENOTUSCITIZEN
Quoted 2 lines
If the
GPL_ONLYstuff is not a license enforcement scheme, nothing prohibits you from stamping your module GPL when it's not.
I'd say its up to the lawyers and judges to find out whether having MODULE_LICENSE("GPL") in a module means anything legally. It might mean "I promise this module is made from GPL source", but it might also mean nothing.
Quoted 2 lines
However, the GPL (section 2b) prohibits you from imposing any restrictions other than those in the GPL itself.
Section 2b) in the file COPYING in the root dir of the kernel source does not talk about restrictions. Are we talking about the same version of the GPL?
Quoted 3 lines
The GPL contains no restrictions that
apply to mere use and theGPL_ONLYstuff affects use, so it can't be a license restriction, hence there is no restriction to enforce.
The GPL doesn't even cover use of the "product". It covers modification and redistribution.
Well, it is still an open question whether kernel modules are derived works or not, especially since we don't have a stable kernel ABI and therefore modules have to use part of the kernel source (headers) and module writers have to study kernel code to write their modules (since there is no official complete documentation about functions in the kernel).
If modules are derived works, then legally, following the GPL, they must be GPL too and GPL_ONLY is no problem but pointless.
Seems to me you could say GPL_ONLY is a way of the developer saying "I consider your stuff to be a derived work if you use this symbol". Ask a lawyer whether that's their decision to make. ;)
Apart from that, I fail to see how it is an addition restriction when you still have the right to remove all the GPL_ONLY stuff. After all, the kernel is GPLed work, so you have the right to remove things and distribute the result. How is it a real restriction when the license allows you to remove it?
Signature · 2 lines
Ciao, Pascal
Quoted 7 lines · David Schwartz
Quoted 3 lines
If the
GPL_ONLYstuff is a license enforcement scheme, the DMCA prohibits you from removing it.
-ENOTUSCITIZEN
In that case, there is more than likely nothing that prevents you from
doing whatever you want.
Quoted 7 lines
Quoted 2 lines
If the
GPL_ONLYstuff is not a license enforcement scheme, nothing prohibits you from stamping your module GPL when it's not.I'd say its up to the lawyers and judges to find out whether having
MODULE_LICENSE("GPL")in a module means anything legally. It might mean "I promise this module is made from GPL source", but it might also mean nothing.
Probably so.
Quoted 6 lines
Quoted 2 lines
However, the GPL (section 2b) prohibits you from imposing any restrictions other than those in the GPL itself.
Section 2b) in the file COPYING in the root dir of the kernel source does not talk about restrictions. Are we talking about the same version of the GPL?
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
In other words, if you want to distribute the Linux kernel, you must
license it under the terms of the GPL. You may not impose additional restrictions because if you do, you're not causing it to be distribute under the terms of "this License".
So if I download the Linux kernel from somewhere, someone distributed it to
me. Hence, if they complied with the GPL, I am under only the obligations imposed by the GPL.
Quoted 6 lines
Quoted 3 lines
The GPL contains no restrictions that
apply to mere use and theGPL_ONLYstuff affects use, so it can't be a license restriction, hence there is no restriction to enforce.The GPL doesn't even cover use of the "product". It covers modification and redistribution.
It does cover use. Specifically, it permits unrestriced use. If you
received GPL'd code, you have the unrestricted right to use it. That's what section 2b says.
Quoted 6 lines
Well, it is still an open question whether kernel modules are derived works or not, especially since we don't have a stable kernel ABI and therefore modules have to use part of the kernel source (headers) and module writers have to study kernel code to write their modules (since there is no official complete documentation about functions in the kernel).
Non-issue. I'm talking about your rights to *use* the kernel.
Quoted 2 lines
If modules are derived works, then legally, following the GPL, they must be GPL too and
GPL_ONLYis no problem but pointless.
You must not be reading the same GPL I am. Can you please cite to me the
section that requires derived works to be placed under the GPL. I can't find it.
Quoted 3 lines
Seems to me you could say
GPL_ONLYis a way of the developer saying "I consider your stuff to be a derived work if you use this symbol". Ask a lawyer whether that's their decision to make. ;)
But that's not what it does. It prevents you from using the kernel in
certain ways. The GPL does not permit such usage restrictions. It also restricts your ability to create and use derived works. The GPL similarly does not permit such restrictions. The only restrictions the GPL allows a distributed derived work to contain are those specifically imposed by the GPL, and those restrictions only kick in at distribution.
If there were distribution restrictions, you'd have an argument. But we are
talking about use restrictions.
Quoted 2 lines
Apart from that, I fail to see how it is an addition restriction when you still have the right to remove all the
GPL_ONLYstuff.
You only have that right (in the United States) if the GPL_ONLY stuff is
*not* a copyright enforcement scheme.
Quoted 4 lines
After
all, the kernel is GPLed work, so you have the right to remove things and distribute the result. How is it a real restriction when the license allows you to remove it?
Fine, so long as we all agree that the GPL_ONLY stuff is not a copyright or
license enforcement scheme and that evading or modifying it is not evading a copyright/license enforcement scheme. In this case, you cannot argue that the DMCA prohibits claiming a GPL license for purposes of compatability.
DS
Quoted 4 lines · David Schwartz
In other words, if you want to distribute the Linux kernel, you must license it under the terms of the GPL. You may not impose additional restrictions because if you do, you're not causing it to be distribute under the terms of "this License".
Correct.
Quoted 1 line
It does cover use.
In section 0:
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
Quoted 3 lines
Specifically, it permits unrestriced use. If you
received GPL'd code, you have the unrestricted right to use it. That's what section 2b says.
No, section 2b gives you the the right to copy, distribute, and modify the code (as the license only covers those rights, as per section 0) and no restrictions may be placed on those specific rights.
Quoted 1 line
Non-issue. I'm talking about your rights to *use* the kernel.
Well, I'm not buying the argument that the GPL has anything to say about usage.
Quoted 3 lines
You must not be reading the same GPL I am. Can you please cite to me the section that requires derived works to be placed under the GPL. I can't find it.
You quoted it yourself. 2b)
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
"work that ... is derived from the Program or any part thereof"
Quoted 2 lines
But that's not what it does. It prevents you from using the kernel in certain ways. The GPL does not permit such usage restrictions.
Lots of GPL'ed programs refuse to be used in certain ways. For example, fetchmail will refuse to run with a world-readable .fetchmailrc file.
Quoted 2 lines
It also restricts your ability to create and use derived works. The GPL similarly does not permit such restrictions.
That it does not, and such a restriction would violate the GPL, I'd agree to that.
Quoted 2 lines
You only have that right (in the United States) if the
GPL_ONLYstuff is *not* a copyright enforcement scheme.
How can it be that? It does not restrict copying nor distribution nor modification.
People here are saying that it's more of a hint to people that they better think hard and ask a lawyer before implementing non-GPL'ed kernel modules.
I think you bringing the DMCA into this shows an interesting aspect of that law: who gets to say what is a copyright enforcement scheme and what is not?
Signature · 2 lines
Ciao, Pascal
Quoted 8 lines · David Schwartz
Quoted 5 lines
In other words, if you want to distribute the Linux kernel, you must license it under the terms of the GPL. You may not impose additional restrictions because if you do, you're not causing it to be distribute under the terms of "this License".
Quoted 8 lines
Correct.
Quoted 1 line
It does cover use.
In section 0:
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
So are you arguing that I can distribute a derived work from the Linux
kernel and attach a 'you may not use this unless you pay me $100' clause and it would be enforceable?
Quoted 7 lines
Quoted 3 lines
Specifically, it permits unrestriced use. If you
received GPL'd code, you have the unrestricted right to use it. That's what section 2b says.No, section 2b gives you the the right to copy, distribute, and modify the code (as the license only covers those rights, as per section 0) and no restrictions may be placed on those specific rights.
If you are right, you've discovered a serious fundamental flaw in the GPL.
I can distribute code under the GPL and prohibit anyone from using derived works, hence effectively removing their freedom to modify.
Quoted 4 lines
Quoted 1 line
Non-issue. I'm talking about your rights to *use* the kernel.
Well, I'm not buying the argument that the GPL has anything to say about usage.
Then you have no right to usage. The preamble contradicts this, but I doubt
it's binding.
Quoted 4 lines
Quoted 3 lines
You must not be reading the same GPL I am. Can you please cite to me the section that requires derived works to be placed under the GPL. I can't find it.
Quoted 8 lines
You quoted it yourself. 2b)
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
"work that ... is derived from the Program or any part thereof"
This is only about works that you distribute or publish. We're talking
about using modules.
Quoted 5 lines
Quoted 2 lines
But that's not what it does. It prevents you from using the kernel in certain ways. The GPL does not permit such usage restrictions.
Lots of GPL'ed programs refuse to be used in certain ways. For example, fetchmail will refuse to run with a world-readable .fetchmailrc file.
Yes, but nobody's arguing that these are license enforcement schemes or
that this is a license restriction. Nobody would complain if you removed those restrictions. The question here is whether the GPL_ONLY stuff is a copyright enforcement mechanism or license restriction. If we agree it's not and anyone is free to circumvent or remove it, then there's nothing to dispute.
Quoted 5 lines
Quoted 2 lines
It also restricts your ability to create and use derived works. The GPL similarly does not permit such restrictions.
That it does not, and such a restriction would violate the GPL, I'd agree to that.
Okay.
Quoted 5 lines
Quoted 2 lines
You only have that right (in the United States) if the
GPL_ONLYstuff is *not* a copyright enforcement scheme.How can it be that? It does not restrict copying nor distribution nor modification.
Copyright enforcement schemes can also restrict usage. Access cards for
satellite TV are purely usage restriction devices.
Quoted 3 lines
People here are saying that it's more of a hint to people that they better think hard and ask a lawyer before implementing non-GPL'ed kernel modules.
I'd agree with that.
Quoted 3 lines
I think you bringing the DMCA into this shows an interesting aspect of that law: who gets to say what is a copyright enforcement scheme and what is not?
The law has a somewhat incomprehensible definition of what consitutes such
a scheme. I don't think anybody really knows what things would be considered copyright enforcement schemes and what would not.
Your argument that the GPL does not grant usage rights is troubling. If
it's correct, then I have no right to use the Linux kernel, since the copyright holders never granted it to me!
DS
Quoted 3 lines · David Schwartz
So are you arguing that I can distribute a derived work from the Linux kernel and attach a 'you may not use this unless you pay me $100' clause and it would be enforceable?
Well, the GPL does not allow you to impose retrictions on copying and redistribution, so you cannot disallow others redistributing your work without your usage clause attached, and it would be legal for them to do that under the GPL.
Your restriction could only effect the part of the kernel you actually modified, because that would be the only part you have copyright on. How are you going to prove people used that part? They have the right to modify the copy, unrestricted, so they could've taken your piece of the code out before using the kernel.
Quoted 3 lines
If you are right, you've discovered a serious fundamental flaw in the GPL. I can distribute code under the GPL and prohibit anyone from using derived works, hence effectively removing their freedom to modify.
No, I don't see how you have influence over derived works. Nothing in the GPL allows you to bind redistributors to your usage clause, since copying and redistribution is covered by the GPL.
Quoted 2 lines
Then you have no right to usage. The preamble contradicts this, but I doubt it's binding.
Well, under German law, if I have the right to legally obtain something, I automatically have the right to usage. Law only comes into play again if I redistribute it or use it in public in some illegal way.
Under German law, you need a real contract in place for usage restrictions to be effective or you need to make certain kinds of usage technically impossible (because if you don't, courts will say you did not even attempt to protect your interests). And no, MS-type "open this bag and you're bound to our license" is not a legal contract over here. Violation of the usage restriction would then fall under contract law, not copyright law.
I don't see how GPL'ed code can have technical restrictions since I can easily compile and change it and I don't have to sign a contract to get it since the license grants unrestricted redistribution right.
This may all be different in the US, of course.
Quoted 2 lines
This is only about works that you distribute or publish. We're talking about using modules.
Well, somebody must have distributed the module, and if that act was illegal because of a GPL violation, I don't know whether you have any right to usage anyway.
Quoted 2 lines
Copyright enforcement schemes can also restrict usage. Access cards for satellite TV are purely usage restriction devices.
These come with a contract here in Germany, and once you have a contract, you can of course, within some limits, put usage restrictions in it as much as you like. You just have to make sure you only give the card to someone who has indeed signed the contract.
Signature · 2 lines
Ciao, Pascal
People, not GPL [was: Re: Driver Model]
In reply to David SchwartzI'm still 1600 messages behind in reading the list, but I have spent enough time reading the discussion about GPL and drivers that I feel compelled to comment. I don't intend to comment further because I don't want to contribute to a flamewar any more than this already will. But I feel the need to defend those who contribute to Free Software against those who don't.
The argument I have been reading has been centered around the idea of working around the GPL to support binary-only driver and various other things which are counter to the spirit of the GPL and Linux. But someone who is trying to find a legal GPL loophole is not considering the root of the situation and that the GPL is an effect, not a cause.
A point someone else made that I feel compelled to reiterate is that it is the nature of the Linux development model and the attitude of the developers which has made Linux what it is and has made you want to use it.
But I have another point. You are not dealing with a license here. The license is there to satisfy lawyers and make clear the INTENT of the authors. The keyword here is INTENT in that someone who has developed something is telling you how they feel about the use of their work which, under many circumstances, they could have chosen not to share with you. What you are dealing with is real people who have put an incredible amount of time and effort into developing Linux. Those people, to whom you owe much respect for sharing their contributions, have decided that their software should be used with certain restrictions, that being the GPL. If you abuse Linux, it is not the GPL that you are insulting, but the people who developed Linux.
The GPL_ONLY restriction for driver modules may seem unfair, but it is far from it. There are both valid technical and philosophical reasons for working that way. No one forces you to use Linux, and when you made the choice to use it, you are entering into a community with a specific philosophy. You know that philosophy in advance, so when you discover that you have a restruction you don't like, you have no room to complain.
As someone said, if you want to write drivers for a UNIX which does not have these restrictions, there are plenty of commercial UNIXes out there that you have to choose from. The fact that they are perhaps less popular is one reason why Linux developers do not want to imitate them.
So, the discussions about finding ways to make a non-GPL driver look like a GPL driver and get away with it legally are all moot. The reason you should not violate this is because the architects of Linux do not want you to. If you choose to violate that, you are being unethical, pure and simple. Or more to the point, you're being an asshole to a lot of hard-working people who have chosen to freely share their work with you. Since they are the authors and you are not, their feelings about their softare are more important than yours. You may be able to screw them over and get away with it -- people do that sort of thing all the time -- but the fact that you may find a legal loophole doesn't make you any less of an abject asshole.
In short: Be honorable.
RE: People, not GPL [was: Re: Driver Model]
Quoted 12 lines
But I have another point. You are not dealing with a license here. The license is there to satisfy lawyers and make clear the INTENT of the authors. The keyword here is INTENT in that someone who has developed something is telling you how they feel about the use of their work which, under many circumstances, they could have chosen not to share with you. What you are dealing with is real people who have put an incredible amount of time and effort into developing Linux. Those people, to whom you owe much respect for sharing their contributions, have decided that their software should be used with certain restrictions, that being the GPL. If you abuse Linux, it is not the GPL that you are insulting, but the people who developed Linux.
In other words, information does not want to be free. You shouldn't use
code the way you want to use it but the way the authors want you to use it. After all, they didn't have to give it to you if they didn't want to.
However, Richard Stallman does not agree with this view. It's his view that
if the authors chose to give you the code, you can use it any way you want to, regardless of how the authors feel about that type of usage. This is why he created the GPL.
Quoted 4 lines
So, the discussions about finding ways to make a non-GPL driver look like a GPL driver and get away with it legally are all moot. The reason you should not violate this is because the architects of Linux do not want you to.
If you really believe that the Linux authors wished to continue to control
how their code was used, you have to think that they were stupid to release the code under the GPL. After all, the whole point of the GPL is to prohibit such restrictions. The reason Linux is under the GPL is so that developers *can't* put restrictions on how the package can be used. That's the "open" in open source.
Quoted 4 lines
If you choose to violate that, you are being unethical,
pure and simple. Or more to the point, you're being an asshole to a lot of hard-working people who have chosen to freely share their work with you.
The person who tries to put other people's GPL'd works under his license
restrictions is the asshole. I have contributed code to the Linux kernel under the GPL license (bonus points to anyone who can find my 25 lines of code or so). It is nobody else's right to add code to my code and add usage restrictions to it. The GPL expressly forbids this.
Quoted 2 lines
Since they are the authors and you are not, their feelings about their softare are more important than yours.
I'm just baffled. You don't seem to understand at all why the Linux kernel
is organized under the GPL. It's precisely so that some developers can't hijack the project and encumber the growing source base with usage and distribution restrictions.
Quoted 4 lines
You may be able to screw
them over and get away with it -- people do that sort of thing all the time -- but the fact that you may find a legal loophole doesn't make you any less of an abject asshole.
The asshole is the person who thinks that they have the right to change the
express wishes of all the other contributors to the kernel who chose to contribute to a project that operates under the GPL license. The GPL license is about there being no restrictions on usage.
Quoted 1 line
In short: Be honorable.
I am. The hijackers are not.
DS
Re: People, not GPL [was: Re: Driver Model]
Quoted 13 lines · David Schwartz
Quoted 11 lines
But I have another point. You are not dealing with a license here. The license is there to satisfy lawyers and make clear the INTENT of the authors. The keyword here is INTENT in that someone who has developed something is telling you how they feel about the use of their work which, under many circumstances, they could have chosen not to share with you. What you are dealing with is real people who have put an incredible amount of time and effort into developing Linux. Those people, to whom you owe much respect for sharing their contributions, have decided that their software should be used with certain restrictions, that being the GPL. If you abuse Linux, it is not the GPL that you are insulting, but the people who developed Linux.
Quoted 3 lines
In other words, information does not want to be free. You shouldn't use
code the way you want to use it but the way the authors want you to use it. After all, they didn't have to give it to you if they didn't want to.
EXACTLY. Fortunately in this case, the authors place few restrictions on your usage. Indeed, the "restrictions" are more a matter of being nice to the people who made the stuff you're using.
You're stuck thinking about "law" and "rules". I'm thinking instead about "honor".
One of the (unresolved) discussions I had with RMS involved the role of the author. He believes that the user is more important than the author. I believe the author is more important, because had the author not written what the user has, then the user would not have it! Actually, he partially agrees with me but does not feel that the author should be able to apply restrictions (IF the work is PUBLISHED).
Quoted 4 lines
However, Richard Stallman does not agree with this view. It's his view that
if the authors chose to give you the code, you can use it any way you want to, regardless of how the authors feel about that type of usage. This is why he created the GPL.
But it seems clear to me that the GPL places some very strong restrictions on your usage. Those restrictions are that although your specific usage of the code doesn't matter, anything (published) that you derive from GPL work MUST also be published under GPL.
So my point is that when someone publishes something under GPL that you find useful, give respect to the person who wrote it by obeying the spirit of the license. But it is not the license that is important as that the author chose to release his work under those terms. People, not rules; honor, not law.
There are other licenses besides the GPL. When authors release under those terms, you should respect those terms as well. The thing that sets the GPL apart from, say, closed-source licensing is that the GPL is based on a system of honor, while proprietary systems can (and often do) become unfairly restrictive to the users.
Quoted 8 lines
Quoted 6 lines
So, the discussions about finding ways to make a non-GPL driver look like a GPL driver and get away with it legally are all moot. The reason you should not violate this is because the architects of Linux do not want you to.
Quoted 6 lines
If you really believe that the Linux authors wished to continue to control
how their code was used, you have to think that they were stupid to release the code under the GPL. After all, the whole point of the GPL is to prohibit such restrictions. The reason Linux is under the GPL is so that developers *can't* put restrictions on how the package can be used. That's the "open" in open source.
The restrictions they are applying are the only ones in the GPL. It was smart for them to use the GPL because it is compatible with their wishes. Follow the GPL not because the GPL is a copyright license, but because you are grateful for the efforts of those who published under GPL.
Furthermore, if someone publishes under GPL, and your insult them, they may become less willing to release under GPL, thereby limiting your ability to rip them off.
Also, just to be pedantic, because you mentioned RMS, "open source" and "free software" are not the same thing.
Quoted 7 lines
Quoted 5 lines
If you choose to violate that, you are being unethical,
pure and simple. Or more to the point, you're being an asshole to a lot of hard-working people who have chosen to freely share their work with you.
Quoted 5 lines
The person who tries to put other people's GPL'd works under his license
restrictions is the asshole. I have contributed code to the Linux kernel under the GPL license (bonus points to anyone who can find my 25 lines of code or so). It is nobody else's right to add code to my code and add usage restrictions to it. The GPL expressly forbids this.
And I completely agree with all of this. I'm getting the feeling that you and I don't actually disagree on any of this. :)
The point of divergence is with regard to modules and the symbol restrictions for non-GPL drivers. Here is a gray area where the GPL may not apply really. These gray areas are where ethics and honor must come into play.
Quoted 9 lines
Quoted 3 lines
Since they are the authors and you are not, their feelings about their softare are more important than yours.
I'm just baffled. You don't seem to understand at all why the Linux kernel
is organized under the GPL. It's precisely so that some developers can't hijack the project and encumber the growing source base with usage and distribution restrictions.
Which is precisely why those authors placed Linux under the GPL. If they didn't like that, they would be working on proprietary OS's. I'm saying that people should respect the authors by honoring the GPL.
Quoted 11 lines
Quoted 5 lines
You may be able to screw
them over and get away with it -- people do that sort of thing all the time -- but the fact that you may find a legal loophole doesn't make you any less of an abject asshole.The asshole is the person who thinks that they have the right to change the
express wishes of all the other contributors to the kernel who chose to contribute to a project that operates under the GPL license. The GPL license is about there being no restrictions on usage.
Well, aside from the "it must remain free clause" (which I interpret as an important restriction), I agree with you. That is to say, the "contributor" who hijacks the work of other contributors is being dishonorable, because he is not respecting the other contributors.
Quoted 5 lines
Quoted 2 lines
In short: Be honorable.
I am. The hijackers are not.
Agreed.
Re: People, not GPL [was: Re: Driver Model]
Quoted 3 lines · Timothy Miller
David Schwartz wrote:
You're stuck thinking about "law" and "rules". I'm thinking instead about "honor".
Indeed. The GPL may not be perfect, but IMHO the GPL is the only way to make sure everyone plays the game according to the rules. I.e. I give you something, you can use it, but please play according to the rules of fair play.
BSD may look OK, but it doesn't protect against people who don't (want to) play according to the rules.
Quoted 4 lines
The point of divergence is with regard to modules and the symbol restrictions for non-GPL drivers. Here is a gray area where the GPL may not apply really. These gray areas are where ethics and honor must come into play.
I consider binary-only modules some kind of loophole to avoid playing according to the rules of fair play.
Unfortunately it seems to be almost impossible to design a license that forces you to play according to the rules of fair play, and doesn't have any loopholes or grey areas.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: People, not GPL [was: Re: Driver Model]
Quoted 3 lines · Geert Uytterhoeven
Unfortunately it seems to be almost impossible to design a license that forces you to play according to the rules of fair play, and doesn't have any loopholes or grey areas.
Fair play is awfully hard to define. Fair use likewise. Currently almost all countries legal systems have a clear notion of "derived work", and copyright (unlike patents) extends no further. That limits how far the GPL can extend, but its the same line in the sand (well fuzzy patch in the sand in truth) that stops a lot of other things you wouldnt like. Which and what modules count as derivative works is a lawyer question and not it seems a trivial one.
Patents do extend beyond just the derived work and since Linux contains patented material with rights granted for GPL use as per the GPL(but not for non GPL use) there is a murky area around modules and patents - one example of the issues that raises being RTLinux.
Folks using binary modules may also find third party software licenses invalid (eg the OpenMotif one)
Re: People, not GPL [was: Re: Driver Model]
In reply to Timothy MillerIn many ways the original intention of the debate was lost in the battle. There are a lot of zealots on both sides of the GPL debate - personally, my undertanding is that the GPL forbids usage restrictions, thus once you release code under the GPL you cannot control it. This seems especially important in a project, such as Linux, that has been collaboratively developmed by a whole community.
The original question was would a binary driver interface allow easier usage by 'normal' users with any compatible kernel (rather than specific versions) and perhaps simplify module development cycle?
Would the performance hit involved be worth the potential compatibility/simplicity?
A lot of people have, assumed that this is a call to arms for binary-only modules. This is not true although this type of change would make such things more common.
James
Quoted 60 lines · Timothy Miller
I'm still 1600 messages behind in reading the list, but I have spent enough time reading the discussion about GPL and drivers that I feel compelled to comment. I don't intend to comment further because I don't want to contribute to a flamewar any more than this already will. But I feel the need to defend those who contribute to Free Software against those who don't.
The argument I have been reading has been centered around the idea of working around the GPL to support binary-only driver and various other things which are counter to the spirit of the GPL and Linux. But someone who is trying to find a legal GPL loophole is not considering the root of the situation and that the GPL is an effect, not a cause.
A point someone else made that I feel compelled to reiterate is that it is the nature of the Linux development model and the attitude of the developers which has made Linux what it is and has made you want to use it.
But I have another point. You are not dealing with a license here. The license is there to satisfy lawyers and make clear the INTENT of the authors. The keyword here is INTENT in that someone who has developed something is telling you how they feel about the use of their work which, under many circumstances, they could have chosen not to share with you. What you are dealing with is real people who have put an incredible amount of time and effort into developing Linux. Those people, to whom you owe much respect for sharing their contributions, have decided that their software should be used with certain restrictions, that being the GPL. If you abuse Linux, it is not the GPL that you are insulting, but the people who developed Linux.
The
GPL_ONLYrestriction for driver modules may seem unfair, but it is far from it. There are both valid technical and philosophical reasons for working that way. No one forces you to use Linux, and when you made the choice to use it, you are entering into a community with a specific philosophy. You know that philosophy in advance, so when you discover that you have a restruction you don't like, you have no room to complain.As someone said, if you want to write drivers for a UNIX which does not have these restrictions, there are plenty of commercial UNIXes out there that you have to choose from. The fact that they are perhaps less popular is one reason why Linux developers do not want to imitate them.
So, the discussions about finding ways to make a non-GPL driver look like a GPL driver and get away with it legally are all moot. The reason you should not violate this is because the architects of Linux do not want you to. If you choose to violate that, you are being unethical, pure and simple. Or more to the point, you're being an asshole to a lot of hard-working people who have chosen to freely share their work with you. Since they are the authors and you are not, their feelings about their softare are more important than yours. You may be able to screw them over and get away with it -- people do that sort of thing all the time -- but the fact that you may find a legal loophole doesn't make you any less of an abject asshole.
In short: Be honorable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Pascal,
SUPER HIGH FIVE!
You have made the obvious clear, and most will not even follow or listen.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
Quoted 59 lines · Pascal Schmidt
Quoted 2 lines · David Schwartz
If the
GPL_ONLYstuff is a license enforcement scheme, the DMCA prohibits you from removing it.
-ENOTUSCITIZENQuoted 2 lines
If the
GPL_ONLYstuff is not a license enforcement scheme, nothing prohibits you from stamping your module GPL when it's not.I'd say its up to the lawyers and judges to find out whether having
MODULE_LICENSE("GPL")in a module means anything legally. It might mean "I promise this module is made from GPL source", but it might also mean nothing.Quoted 2 lines
However, the GPL (section 2b) prohibits you from imposing any restrictions other than those in the GPL itself.
Section 2b) in the file COPYING in the root dir of the kernel source does not talk about restrictions. Are we talking about the same version of the GPL?
Quoted 3 lines
The GPL contains no restrictions that
apply to mere use and theGPL_ONLYstuff affects use, so it can't be a license restriction, hence there is no restriction to enforce.The GPL doesn't even cover use of the "product". It covers modification and redistribution.
Well, it is still an open question whether kernel modules are derived works or not, especially since we don't have a stable kernel ABI and therefore modules have to use part of the kernel source (headers) and module writers have to study kernel code to write their modules (since there is no official complete documentation about functions in the kernel).
If modules are derived works, then legally, following the GPL, they must be GPL too and
GPL_ONLYis no problem but pointless.Seems to me you could say
GPL_ONLYis a way of the developer saying "I consider your stuff to be a derived work if you use this symbol". Ask a lawyer whether that's their decision to make. ;)Apart from that, I fail to see how it is an addition restriction when you still have the right to remove all the
GPL_ONLYstuff. After all, the kernel is GPLed work, so you have the right to remove things and distribute the result. How is it a real restriction when the license allows you to remove it?Signature · 8 lines
Ciao, Pascal - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/