Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Quoted 6 lines · On Friday 15 June 2007 21:29:22 Linus Torvalds wrote:
Quoted 3 lines · Rob Landley
Technically what they're holding back is _trademark_ rights, which are a different area of IP law and not addressed by the GPL. (I know you know this, but just for the record...)
No, technically Red Hat really *does* have copyrights of their own.
They do have copyrights. They license them under the GPL, and afterwards they still have them.
Quoted 5 lines
Red Hat owns the "compilation copyright" on their distribution. That means, for example, that even if they have _only_ open source programs on their DVD image, you still are not necessarily able (without their permission) to set up a "cheap-cd's" kind of operation, and sell their CD-ROM/DVD images for a lower price.
I agree that they have this right, but that wasn't the rationale they gave in the cease and desist letters they sent out in 2001. Those said it was ok to redistribute, but you can't use their trademarks to promote it when you did so:
http://www.newsforge.com/article.pl?sid=01/12/10/2014239&mode=thread
[Rummages around for their current policy statement...]
The restriction is embodied in their "trademark guidelines and policies":
http://www.redhat.com/about/companyprofile/trademark/
If you open the PDF:
http://www.redhat.com/f/pdf/corp/RH-3573_284204_TM_Gd.pdf
Page one, the right hand side talks about copyright, second paragraph:
Quoted 7 lines
At the same time, the combined body of work that consitutes Red Hat (R) Enterprise Linux (R) is a collective work which has been organized by Red hat, and Red hat holds the copyright in that collective work. Red hat then permits others to copy, modify and redistribute the collective work. To grant this permission Red hat usually uses the GNU General Public License ("GPL") version 2 and Red Hat's own End User License Agreement. Although software licensed under the GPL is "open source software," Red Hat retains
Quoted 8 lines
ownership of the copyright in its collective work. If someone violates the GPL regarding that collective work, only Red Hat, as the copyright owner and licensor of that collective work, has legal authority to enforce the GPL against the violator. Although Red hat "owns" the collective work, in licenseing it under the GPL, Red Hat grants broad rights in the collective work to others. Neither the GPL nor Red Hat's End User License Agreement grant any right to use Red hat's trademarks in the redistribution of the collective work.
That seems to say that their compilation copyright is also licensed under the GPL, and what they're not giving permission to use is the trademark.
Quoted 3 lines
So yes, they do own the Red Hat trademark too, but they fundamentally do own copyrights over and beyond those of the individual programs they distribute!
I agree they claim compilation copyrights. But they seem to have licensed their compilation copyrights under GPLv2.
If they're including GPLed works in the compilation, this may actually be a requirement. (Lawyers would happily fight over this issue for months:
asserting a copyright over the aggregation takes the "mere" out of it, don't you think? Is a compilation a derived work of the components that were compiled, at least for the purposes of GPLv2? Can it be "mere aggregation" if you're enforcing a copyright on that aggregation? Does it not then become a larger work with GPL components? I dunno.)
You'll notice that back under Bob Young, Red Hat carefully didn't go there, by licensing the compilation GPLv2 and segregating incompatibly licensed content to a separate CD. After the IPO, he retired and different management took over, and introduced Red Hat Enterprise to eat Sun's market[1], and who knows what they're thinking now? I suspect their lawyers still want the GPL-incompatible stuff on a separate CD so they can sleep at night.
(Either that, or they just don't assert a compilation copyright, but why give that up if they don't have to?)
Quoted 3 lines
Now, I think it so happens that the RHEL DVD's contains other programs than just open source, and that you couldn't legally copy them *anyway*, but that's a different issue.
The existence of CentOS seems to argue against this. They say:
Quoted 4 lines
The vast majority of changes made will be made to comply with the upstream vendor's re-distribution policies concerning trademarked names or logos. Any other changes made will be spelled out in the Release Notes for the individual CentOS product.
I haven't noticed any specific non-GPL packages removed from Centos. Buried down in their FAQ they say they're building the same set of packages as are in Red Hat Enterprise AS.
I suspect the reason for a lack of obvious proprietary stuff in the RHEL base distro is that Red Hat's lawyers don't want to give up the option to enforce the compilation copyright on said base distro, but also don't want to raise the spectre of enforcing a copyright on a derived work of GPL code (the compilation, which includes GPL code and if copyrighted probably isn't "mere aggregation") that contains code which can't be licensed under the GPL.
I don't know the answer to this one. This is the sort of thing that gives lawyers ulcers. (And yachts.) But I can believe their lawyers want to keep their options open if they're sufficiently unsure how the hypothetical would play out in court...
Quoted 4 lines
Also, happily, a lot of vendors do not *want* to exercise their copyright in the compilation, so you can go to cheapbytes.com, and you'll find Fedora CD's, OpenSuSE CD's, Ubuntu CD's, etc, and as far as I know, they're all perfectly legal.
Red Hat created the "Fedora" trademark to have a separate and more liberally licensed trademark that people like cheapbytes.com could use without reflecting on Red Hat Enterprise. Unfortunately, trying to find reference for this is non-obvious, because, the Fedora Trademarks page is:
http://fedoraproject.org/wiki/Legal/TrademarkGuidelines
Which contains no actual content, but instead links to a fedora.redhat.com page which is 404. :P
But again, it's trademark not copyright they're restricting.
Quoted 11 lines
Quoted 2 lines
The five main areas of IP law as I understand them are copyright, patent, trademark, contract, and trade secret.
I'd not put contract there, but fair enough. But what I was really trying to point out is that there are many different "levels" of copyright.
So you can own a "copyright in the compilation" - which just means that you own the details of how you set it all together - _without_ actually necessarily owning the copyrights in any of the individual packages (although you obviously have to have a license to _make_ a compilation of them - but the GPLv2 is one such license).
Sure, it's spelled out in some detail by the copyright office right here:
http://www.copyright.gov/circs/circ14.html#compilations
And in less penetrable legalese here [2]:
http://www.copyright.gov/title17/92chap1.html#103
However, mostly I just deal with straightforward derivative works when worrying about GPL enforcement. (When I brought up compilation copyright to the SFLC guys last year in relation to enforcing the busybox copyrights, they didn't think they needed to go there since between Erik and myself they represent copyrights to a significant portion of the entire codebase, including the central plumbing you can't run the thing without).
Intellectual property law has been a hobby of mine ever since I visited the Patent and Trademark office in washington DC with my grandfather back in the 90's, and picked up the big green brochures explaining this stuff. I think I still have the badge in a box somewhere. There's all SORTS of weird corner cases to this stuff. (Did you know the federal government can't create a copyright? Everything created by federal employees is automatically in the public domain. So the way they get around that is they hire contractors, have them create copyrighted materials, and transfer the copyrights to the government...)
Quoted 1 line
Linus
Rob
[1] Large purchasing contracts, especially for government projects, often cap a supplier's profits at a percentage of costs. This means the way for a supplier to get a larger profit off the contract is to user more expensive components. So they'd rather grab $5000/seat OS than a $20/seat OS because the same 10% profit is $500 vs $2. This is a big reason you saw lots of Solaris and AIX and such in Navy bids 10 years ago: it was popular _because_ it was expensive. Then Red Hat figured out "wait, you mean if I can come up with an excuse to charge a couple orders of magnitude more per seat, MORE people will buy it?" And they invented "Red Hat Enterprise" to soak that kind of purchaser for all they were worth, and it was so lucrative they retreated up into that space to attack the soft underbelly of Sun...
[2] The section relating specifically to computer programs is interesting reading too: http://www.copyright.gov/title17/92chap1.html#117
The stuff about "archival copies" is explicitly statutory. When I first heard about it I thought it was just case law...
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 8 lines
Red Hat created the "Fedora" trademark to have a separate and more liberally licensed trademark that people like cheapbytes.com could use without reflecting on Red Hat Enterprise. Unfortunately, trying to find reference for this is non-obvious, because, the Fedora Trademarks page is:
http://fedoraproject.org/wiki/Legal/TrademarkGuidelinesWhich contains no actual content, but instead links to a fedora.redhat.com page which is 404. :P
That would be a bug 8)
Quoted 1 line
But again, it's trademark not copyright they're restricting.
Correct - all the vendors face the problem that there are people out there who want to try and pass crap on using someone elses good name whether its toothpaste, perfume or software (or in the case of RHEL software/services/support bundles)
The Fedora mark is thus used to make sure that if you get a Fedora CD, it actually has -Fedora- on it etc.
Quoted 9 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
I've never had a reason to want to change the way any device like a TiVO works. So I can't comment on this.
Have you never wanted to improve any aspect of the software in your cell phone? In your TV, VCR, DVD player, anything? In the microwave oven, maybe?
This is perhaps the part that's the most interesting. For the very small number of people that _do_ want to change these things (usually at the expense of a voided warranty, in the consumer device case), there's always a way to make these changes, even if you must resort to hardware hacking. Trying to mandate this sort of functionality in the license might make it easier for a few people to get their code loaded, but the vast majority of users have zero interest in anything like this.
I don't see how you can claim that the vendor is infringing on your freedom, _you_ made the decision to go out and buy the product knowing that the vendor wasn't going to go out of their way to help you hack the device. In many cases the vendor doesn't even have the option (802.11b channels and certification come to mind, GSM, etc.) of opening things up to the end user, and making changes to the license isn't going to magically change any of this.
If you don't like what the vendor has done with the product, you have the freedom to not support the vendor, and to try and encourage people to follow suit. As an example, I simply opted not to buy a tivo since I wasn't able to do what I wanted with it out of the box, rather than opting to rant about it (or coin an idiotic buzzword) much to the dismay of every other person on a mailing list. This was neither something I lost a great deal of sleep over, nor did I at any time feel like my freedom was being eroded. True story.
If the vendor's bottom line is measurably impacted, they may even reevaluate their position on supporting device hacking, but it's certainly not going to be through draconian licensing that vendors suddenly decide to play nice.
There were certainly enough vendors that followed the letter of the GPLv2 without following the spirit of the license, with varied benefit (especially with consumer device vendors). Imposing additional constraints under the guise of the FSF's current version of "freedom" isn't going to get these sorts of vendors working any better with the community. You could of course argue that these vendors have nothing to offer the community, and so they shouldn't be tolerated at all, but that assumes that being able to load arbitrary code on their hardware and the usefulness of whatever contributions they have to make to the software are directly coupled some how. This has never been the case, and it only seems to be a mindset that has started circulating when the GPLv3 came about.
One idly wonders who exactly the FSF feels they're speaking for at this point..
Quoted 7 lines · Paul Mundt
This is perhaps the part that's the most interesting. For the very small number of people that _do_ want to change these things (usually at the expense of a voided warranty, in the consumer device case), there's always a way to make these changes, even if you must resort to hardware hacking. Trying to mandate this sort of functionality in the license might make it easier for a few people to get their code loaded, but the vast majority of users have zero interest in anything like this.
I don't feel this is a very conclusive argument.
How many computer users do want to change their OS? I mean not only want to change the OS in the sense of "apply patches released by Microsoft", but on their own? Many typical computer users ask for help to "fix their computer" when turning it off and on again already "fixes it". They would never ever change the source code of their OS even if they technically could do it - they are not programmers.
However, if there is the technical possibility to change the firmware of an appliance, somebody does it, and often mere users upload these changes to their own device (like the OpenWRT stuff).
Let me give one example: My parents own a DVB-T DVR. It was a cheap one, and it was cheap because the software is lackluster. Unfortunately it isn't free. Many users of this device complain to the manufacturer about the stability and quality of the software, but with no avail - there haven't been any updates in the last two years. I suppose I would be able to fix the problem, most other users probably wouldn't (and my parents neither). But if I did fix the problem, and provided them with an updated firmware, they would install it on their device.
That's the "help your neighbour" right in the GNU manifesto. It's as important as the "help yourself" right, maybe even more. It was the original motivation of RMS to make free software - the frustration of not being able to help his neighbours. He had an NDA to help himself.
What people want is software that works. If the firmware of your microwave or DVR works, you don't care so much if it is free or not. You only care if it doesn't work, and you feel the urge to fix it (and turning it off and on again doesn't fix it). That's why people complain loud about ATI drivers not being open, and don't care that much about the Nvidia driver, which is just as closed, but works.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 4 lines · Paul Mundt
I don't see how you can claim that the vendor is infringing on your freedom, _you_ made the decision to go out and buy the product knowing that the vendor wasn't going to go out of their way to help you hack the device.
But I also made this decision fully aware that the software included in the package was published under a license that said I was entitled to modify it. More than once I purchased a device that claimed to have GNU/Linux software on it, only to find out that I couldn't use the freedoms, because the distributor was infringing the license in various ways.
Quoted 3 lines
If you don't like what the vendor has done with the product, you have the freedom to not support the vendor, and to try and encourage people to follow suit.
Sure. But wouldn't it be nice if the copyright holder could also help in this effort? It doesn't mean the copyright holder has to: s/he can always grant an additional permission, or simply refrain from enforcing this provision of the license.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Daniel Hazelton
<somewhat sarcastic>
And the companies that produce devices that come with Linux and/or other GPL'd software installed and place limits such that only people that have purchased that hardware have access to the "modified" source running on the device are following the letter, and the spirit, of the GPL.
WAIT, WAIT, THAT'S... :-)
Quoted 4 lines
Before you start yelling I'm wrong, think about it this way: they make the source available to the people that they've given binary versions to, and there is nothing stopping one of those people from making the source available to the rest of the world.
The *only* in your sentence betrayed you.
If they place the limits such that nobody else can access the sources, they're in violation of the license.
If they merely refrain from distributing the sources to others, but still enable the recipients to do so, this is not a violation of the license.
But then IANAL.
Quoted 2 lines
*AND* the GPL has never been about making the source available to everyone - just to those that get the binaries.
Exactly. Not even to the upstream distributor. That's where Linus' theory of tit-for-tat falls apart.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 7 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
*AND* the GPL has never been about making the source available to everyone - just to those that get the binaries.
Exactly. Not even to the upstream distributor. That's where Linus' theory of tit-for-tat falls apart.
Nope.
case 1: Upstream provides source, tivo modifies and distributes it (to their customers).
case 2: tivo provides source, end user modifies and distributes it (possibly to their customers, maybe to friends, possibly even to upstream).
See? Tit for tat.
Chris
Quoted 11 lines · Chris Friesen
Quoted 7 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
*AND* the GPL has never been about making the source available to everyone - just to those that get the binaries.
Exactly. Not even to the upstream distributor. That's where Linus' theory of tit-for-tat falls apart.
Nope.
Quoted 8 lines
case 1: Upstream provides source, tivo modifies and distributes it (to their customers).
case 2: tivo provides source, end user modifies and distributes it (possibly to their customers, maybe to friends, possibly even to upstream).
See? Tit for tat.
case 2': tivo provides source, end user tries to improve it, realizes the hardware won't let him and gives up
Where's the payback, or the payforward?
And then, tit-for-tat is about equivalent retaliation, an eye for an eye. Where's the retaliation here?
If GPLv2 were tit-for-tat, if someone invents artifices to prevent the user from making the changes the user wants on the software, wouldn't it be "equivalent retaliation" to prevent the perpetrator from making the changes it wants on the software?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 14 lines · On Thursday 14 June 2007 18:45:07 Alexandre Oliva wrote:
Quoted 13 lines · Chris Friesen
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
*AND* the GPL has never been about making the source available to everyone - just to those that get the binaries.
Exactly. Not even to the upstream distributor. That's where Linus' theory of tit-for-tat falls apart.
Nope.
case 1: Upstream provides source, tivo modifies and distributes it (to their customers).
Quoted 8 lines
Quoted 5 lines
case 2: tivo provides source, end user modifies and distributes it (possibly to their customers, maybe to friends, possibly even to upstream).
See? Tit for tat.
case 2': tivo provides source, end user tries to improve it, realizes the hardware won't let him and gives up
Faulty logic. The hardware doesn't *restrict* you from *MODIFYING* any fscking thing.
DRH
Quoted 10 lines
Where's the payback, or the payforward?
And then, tit-for-tat is about equivalent retaliation, an eye for an eye. Where's the retaliation here?
If GPLv2 were tit-for-tat, if someone invents artifices to prevent the user from making the changes the user wants on the software, wouldn't it be "equivalent retaliation" to prevent the perpetrator from making the changes it wants on the software?
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 2 lines · Daniel Hazelton
Faulty logic. The hardware doesn't *restrict* you from *MODIFYING* any fscking thing.
Ok, lemme try again:
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
Quoted 10 lines · On Thursday 14 June 2007 18:45:07 Alexandre Oliva wrote:
Quoted 9 lines
Where's the payback, or the payforward?
And then, tit-for-tat is about equivalent retaliation, an eye for an eye. Where's the retaliation here?
If GPLv2 were tit-for-tat, if someone invents artifices to prevent the user from making the changes the user wants on the software, wouldn't it be "equivalent retaliation" to prevent the perpetrator from making the changes it wants on the software?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
So you're blaming Tivo for the fact that your end user was a lazy bum and wanted to take advantage of somebody elses hard work without permission?
Quite frankly, I know who the bad guy in that scenario is, and it ain't Tivo. It's your lazy bum, that thought he would just take what Tivo did, sign the contract, and then not follow it. And just because the box _contained_ some piece of free software, that lazy bum suddenly has all those rights? Never mind all the *other* effort that went into bringing that box to market?
You do realize that Tivo makes all their money on the service, don't you? The actual hardware they basically give away at cost, exactly to get the service contracts. Not exactly a very unusual strategy in the high-tech world, is it?
You know what? I respect the pro-FSF opinions less and less, the more you guys argue for it. Michael Poole seems to argue that things like fair use shouldn't exist, and even the cryptographic _signatures_ of the programs should be under total control of the copyright owner.
And you seem to argue that it's perfectly fine to ignore the people who design hardware and the services around them, and once you have that piece of hardware in your grubby hands you can do anythign you want to it, and _their_ rights and the contracts you signed don't matter at all.
Guys, you should be ashamed of calling yourself "free software" people.
You sound more like the RIAA/MPAA ("we own all the rights! We _own_ your sorry asses for even listening to our music") and a bunch of whiners that think that just because you have touched a piece of hardware you automatically can do anythign you want to it, and nobody elses rights matter in the least!
Guys, in fighting for "your rights", you should look a bit at *other* peoples rights too. Including the rights of hw manufacturers, and the service providers. Because this is all an eco-system, where in order to actually succeed, you need to make _everybody_ succeed.
Linus
Quoted 7 lines · Linus Torvalds
Quoted 3 lines · Alexandre Oliva
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
So you're blaming Tivo for the fact that your end user was a lazy bum and wanted to take advantage of somebody elses hard work without permission?
-ENONSEQUITUR
Quoted 5 lines
Quite frankly, I know who the bad guy in that scenario is, and it ain't Tivo. It's your lazy bum, that thought he would just take what Tivo did, sign the contract, and then not follow it. And just because the box _contained_ some piece of free software, that lazy bum suddenly has all those rights?
Yes, because the software license that TiVo signed up for says that TiVo must pass on certain rights and not impose any further restrictions.
And all that because TiVo wanted to use kernel and userland that were readily available, and at no cost other than respecting others' freedoms, while at that?
Who's the lazy bum, again?
Quoted 2 lines
And you seem to argue that it's perfectly fine to ignore the people who design hardware and the services around them,
Just like they seem to think it's perfectly fine to ignore a number of people who design and maintain the software they decided to use in their hardware.
Quoted 8 lines
Guys, you should be ashamed of calling yourself "free software" people.
You sound more like the RIAA/MPAA ("we own all the rights! We _own_ your sorry asses for even listening to our music") and a bunch of whiners that think that just because you have touched a piece of hardware you automatically can do anythign you want to it, and nobody elses rights matter in the least!
Quoted 4 lines
Guys, in fighting for "your rights", you should look a bit at *other* peoples rights too. Including the rights of hw manufacturers, and the service providers. Because this is all an eco-system, where in order to actually succeed, you need to make _everybody_ succeed.
Good. How about thinking of the users, the customers of your dear friends too? The ones who might be contributing much more to your project.
Then look how what you said in the paragraph before about RIAA/MPAA applies to what TiVO is doing to the software, and realize that you're accusing us of doing what the party you support does.
I'm not trying to impose anything. I'm not pushing anything. I'm defending the GPLv3 from accusations that it's departing from the GPL spirit, and I'm trying to find out in what way Tivoization promotes the goals you perceive as good for Linux, that make GPLv2 advantageous. So far, you haven't given any single reason about this. You talked about tit-for-tat, you said anti-Tivoization in GPLv3 was bad, but you don't connect the dots. Forgive if I get the impression that you're just fooling yourself, and misguiding a *lot* of people out there in the process.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · Alexandre Oliva
I'm not trying to impose anything. I'm not pushing anything. I'm defending the GPLv3 from accusations that it's departing from the GPL spirit, and I'm trying to find out in what way Tivoization promotes the goals you perceive as good for Linux, that make GPLv2 advantageous. So far, you haven't given any single reason about this. You talked about tit-for-tat, you said anti-Tivoization in GPLv3 was bad, but you don't connect the dots. Forgive if I get the impression that you're just fooling yourself, and misguiding a *lot* of people out there in the process.
Give. Me. A. Break.
Section 6 is inherently broken. It tries to gerrymander the "bad" cases and ends up with a huge mess. Definition of user device is arbitrary and reeks with discrimination against the field of use. Trying to be more explicit about installation instructions walks straight into a minefield:
* is it enough to give some installation methods? If so,
should they be as cheap as the rest? As efficient as the rest in some sense? Representative in some sense? The same as what manufacturer ever uses?
* if all installation methods should be given, where does
one stop? Should one describe unsupported ones? All of them? Is that a violation of license to omit some? How does one prove that omission hadn't been malicious violation in face of complaint?
Trying to be explicit enough to get a rope on the TiVo neck ends up with not just clumsy rules; it opens a can of worms worse than what we have in matching part of v2.
It looks like trying to be tight enough to be sure to catch the cases FSF doesn't like and trying to avoid getting the stuff that really shouldn't be caught. And looks like these requirements conflict.
So in the end you get an ugliness that satisfies neither those who think that TiVo case is not a problem nor those who agree that it is a problem and consider v2 sufficient in that area.
And BTW, you've been told just that about an hour before you've sent that mail. I don't mind repeating that on l-k, but please don't pretend to be unaware of the problems in that area. I've no idea which problems Linus has with that turd, but there's certainly enough in there.
Quoted 11 lines · Al Viro
Quoted 9 lines · Alexandre Oliva
I'm not trying to impose anything. I'm not pushing anything. I'm defending the GPLv3 from accusations that it's departing from the GPL spirit, and I'm trying to find out in what way Tivoization promotes the goals you perceive as good for Linux, that make GPLv2 advantageous. So far, you haven't given any single reason about this. You talked about tit-for-tat, you said anti-Tivoization in GPLv3 was bad, but you don't connect the dots. Forgive if I get the impression that you're just fooling yourself, and misguiding a *lot* of people out there in the process.
Quoted 3 lines
Give. Me. A. Break.
Section 6 is inherently broken.
You mean the bits against Tivoization in it, right.
You point out reasons you dislike the particular wording (good, can you relay them to gplv3.fsf.org, please?), but nowhere do you show where such provisions hamper the tit-for-tat goal that Linus likes about GPLv2 and claims to be the reason he chose v2. In fact, I've shown evidence that anti-Tivoization increases this tit-for-tat. Still, v2 is preferred over v3 under these grounds. How can it be?
Quoted 2 lines
And BTW, you've been told just that about an hour before you've sent that mail.
Yup. I got your opinion. Now I got it twice, and others got it once. How about others' opinions?
And, more importantly, how does that provision conflict with your personal goals WRT Linux?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 6 lines · Alexandre Oliva
You point out reasons you dislike the particular wording (good, can you relay them to gplv3.fsf.org, please?), but nowhere do you show where such provisions hamper the tit-for-tat goal that Linus likes about GPLv2 and claims to be the reason he chose v2. In fact, I've shown evidence that anti-Tivoization increases this tit-for-tat. Still, v2 is preferred over v3 under these grounds. How can it be?
It's not about particular wording. It's about disgust at that kind of games in general. Now bugger off and stop deliberately misparsing what I said.
Oh, and could you please lose the "Free Software Evangelist" bit in your sig when posting on l-k? Unless you want to get the treatment normally reserved for evangelist pests, that is... Your personal kinks are your personal kinks; kindly keep your religion to consenting partners.
Quoted 16 lines · On Friday 15 June 2007 00:14:49 Alexandre Oliva wrote:
Quoted 6 lines · Linus Torvalds
Quoted 2 lines · Alexandre Oliva
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
So you're blaming Tivo for the fact that your end user was a lazy bum and wanted to take advantage of somebody elses hard work without permission?
-ENONSEQUITURQuoted 5 lines
Quite frankly, I know who the bad guy in that scenario is, and it ain't Tivo. It's your lazy bum, that thought he would just take what Tivo did, sign the contract, and then not follow it. And just because the box _contained_ some piece of free software, that lazy bum suddenly has all those rights?
Quoted 3 lines
Yes, because the software license that TiVo signed up for says that TiVo must pass on certain rights and not impose any further restrictions.
They don't add any restrictions that don't already exist. As stated in section 0 of the GPLv2 the scope of the license is "copying, distributing and modification".
Quoted 5 lines
And all that because TiVo wanted to use kernel and userland that were readily available, and at no cost other than respecting others' freedoms, while at that?
Who's the lazy bum, again?
Still the same one that Linus pointed out. No amount of faulty logic can change that.
Quoted 6 lines
Quoted 2 lines
And you seem to argue that it's perfectly fine to ignore the people who design hardware and the services around them,
Just like they seem to think it's perfectly fine to ignore a number of people who design and maintain the software they decided to use in their hardware.
Huh? They have complied with the terms - and, IMHO, the spirit - of the license under which that software was released.
Quoted 8 lines
Quoted 8 lines
Guys, you should be ashamed of calling yourself "free software" people.
You sound more like the RIAA/MPAA ("we own all the rights! We _own_ your sorry asses for even listening to our music") and a bunch of whiners that think that just because you have touched a piece of hardware you automatically can do anythign you want to it, and nobody elses rights matter in the least!
Quoted 8 lines
Quoted 4 lines
Guys, in fighting for "your rights", you should look a bit at *other* peoples rights too. Including the rights of hw manufacturers, and the service providers. Because this is all an eco-system, where in order to actually succeed, you need to make _everybody_ succeed.
Good. How about thinking of the users, the customers of your dear friends too? The ones who might be contributing much more to your project.
If they are *CONTRIBUTING* then they are not just simple users anymore.
Quoted 4 lines
Then look how what you said in the paragraph before about RIAA/MPAA applies to what TiVO is doing to the software, and realize that you're accusing us of doing what the party you support does.
Quoted 9 lines
I'm not trying to impose anything. I'm not pushing anything. I'm defending the GPLv3 from accusations that it's departing from the GPL spirit, and I'm trying to find out in what way Tivoization promotes the goals you perceive as good for Linux, that make GPLv2 advantageous. So far, you haven't given any single reason about this. You talked about tit-for-tat, you said anti-Tivoization in GPLv3 was bad, but you don't connect the dots. Forgive if I get the impression that you're just fooling yourself, and misguiding a *lot* of people out there in the process.
And failing. You say that the intent and spirit of the GPLv2 is clear if you read it. I read it and I feel its pretty clear that the only things that the GPLv2 sought to protect are *EXACTLY* "copying, distribution and modification".
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 7 lines · Daniel Hazelton
Quoted 5 lines · On Friday 15 June 2007 00:14:49 Alexandre Oliva wrote:
Quoted 4 lines · Linus Torvalds
Guys, in fighting for "your rights", you should look a bit at *other* peoples rights too. Including the rights of hw manufacturers, and the service providers. Because this is all an eco-system, where in order to actually succeed, you need to make _everybody_ succeed.
Quoted 5 lines
Quoted 3 lines
Good. How about thinking of the users, the customers of your dear friends too? The ones who might be contributing much more to your project.
If they are *CONTRIBUTING* then they are not just simple users anymore.
Yeah. Isn't that great? Isn't this even more contributions "in kind"?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 6 lines · Linus Torvalds
Quoted 3 lines · Alexandre Oliva
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
Quoted 6 lines
So you're blaming Tivo for the fact that your end user was a lazy bum and wanted to take advantage of somebody elses hard work without permission?
Quite frankly, I know who the bad guy in that scenario is, and it ain't Tivo. It's your lazy bum, that thought he would just take what Tivo did, sign the contract, and then not follow it. And just because the box _contained_ some piece of free software, that lazy bum suddenly has all those rights? Never mind all the *other* effort that went into bringing that box to market?
You do realize that Tivo makes all their money on the service, don't you? The actual hardware they basically give away at cost, exactly to get the service contracts. Not exactly a very unusual strategy in the high-tech world, is it?
Not unusual - but so what.
This strategy may backfire if users find a way
to use the cheap box for something without Tivo's service contract.
That don't make me feel sorry for Tivo - they can then sell their boxes with some profit - or go bankrupt for doing stupid business.
Similiar to how unrealistic cheap printers backed by ink sales fail when third parties undercuts the ridiculously expensive ink. Or give-away cellphones tied to an expensive provider, being unlocked by third parties so a switch to a cheaper provider will work.
Don't get me wrong - I have nothing against Tivo - and nothing for them either. Them making a locked device is just a fun arms race to see who can reprogram the bootloader key
or find some other clever way to load software. . .
Quoted 2 lines
Guys, in fighting for "your rights", you should look a bit at *other* peoples rights too. Including the rights of hw manufacturers, and the service providers. Because this is all an eco-system, where in order to actually succeed, you need to make _everybody_ succeed.
Nothing against a hw manufacturers right - but of course they have no particular right to succeed with give-away hw and expensive service. When that strategy fail due to people operating the hw without buing service then the cure is to charge properly for the hw, not to ask everybody to please stop hacking.
Assuming that nobody can change the box after the sale is their risk, and there is nothing unfair about failure here.
Helge Hafting
Quoted 10 lines · Helge Hafting
Quoted 6 lines · Linus Torvalds
You do realize that Tivo makes all their money on the service, don't you? The actual hardware they basically give away at cost, exactly to get the service contracts. Not exactly a very unusual strategy in the high-tech world, is it?
Not unusual - but so what.
This strategy may backfire if users find a way
to use the cheap box for something without Tivo's service contract.
Yeah, I'm not at all trying to say that Tivo has the "right to make money".
They can fail for all I care.
But they do have the right to make their own choices, and try their own strategies. And people shouldn't complain about that. If somebody doesn't like the Tivo box, and the Tivo service requirements, just don't *buy* the damn thing, and don't sign up for the service.
Whining about Tivo's choices is just stupid.
And anybody who thinks others don't have the "right to choice", and then tries to talk about "freedoms" is a damn hypocritical moron.
Linus
Quoted 9 lines · Linus Torvalds
But they do have the right to make their own choices, and try their own strategies. And people shouldn't complain about that. If somebody doesn't like the Tivo box, and the Tivo service requirements, just don't *buy* the damn thing, and don't sign up for the service.
And anybody who thinks others don't have the "right to choice", and then tries to talk about "freedoms" is a damn hypocritical moron.
One might say the same thing about someone who claims not to have a moral right to force certain choices on others in some circumstances (e.g. when those others have used copyrighted work in a product and ought to understand that for some not insignificant portion of the copyright holders, the terms implicitly included preserving certain "freedoms" for downstream recipients) while reserving a very similar moral right with others (e.g. potential murderers, theives, tresspassers, distributors of proprietary derived works).
As I pointed out in a previous message in the thread, that some people want the copyright holders -- who have economic power over the hardware vendors who use Linux in their products -- to force a desireable outcome for those without that power (i.e. the small number of people who buy TiVOs or Linksys routers who actually care about source availability and who get told "don't buy it" as if that will change anything) is understandable.
I think that there's a legitimate concern about what types of constraints it's valid for a copyright holder to try to enforce w/ a license -- I think it's immoral for an employer to force an employee to toil at a meaningless, soul-crushing job for the vast majority of one's single, short existence if they could make it more enjoyable, but I'd hate to see someone try to enforce that with a license (I'm happy telling a person in that situation to "just quit" just as you tell people "just don't buy it"). To call people who draw the line in a different place than you hypocrites is BS.
Your pragmatic arguments make much more sense than your moralistic ones, IMHO.
Dave
Quoted 8 lines
constraints it's valid for a copyright holder to try to enforce w/ a license -- I think it's immoral for an employer to force an employee to toil at a meaningless, soul-crushing job for the vast majority of one's single, short existence if they could make it more enjoyable, but I'd hate to see someone try to enforce that with a license (I'm happy telling a person in that situation to "just quit" just as you tell people "just don't buy it"). To call people who draw the line in a different place than you hypocrites is BS.
Very poor example. In many parts of the world "Just quit" is "just starve to death".
And guess what - brand owners do use the rights to try and stop that kind of abuse with varying degrees of success. The 'fair trade' logo is controlled this way. Many companies do their best not to license production of goods to sweat shops and child slaves. It's considered morally correct and companies get pounded by the public and lose business when they fail to police these restrictions.
So please DON'T equate the two. Tivo is a minor control argument about a silly little TV recording box. Employee rights is a matter of life, death and slavery for many many people.
Alan
Quoted 9 lines · Alan Cox
Quoted 2 lines
To call people who draw the line in
a different place than you hypocrites is BS.Very poor example. In many parts of the world "Just quit" is "just starve to death".
So please DON'T equate the two. Tivo is a minor control argument about a silly little TV recording box. Employee rights is a matter of life, death and slavery for many many people.
Well, I consider your eloquent counter-argument to have strengthened my point that such "rights to moral coercion" arguments are inherently subjective and highly context-dependent.
Dave
Quoted 4 lines · Dave Neuer
Quoted 3 lines
And anybody who thinks others don't have the "right to choice", and then tries to talk about "freedoms" is a damn hypocritical moron.
Quoted 8 lines
One might say the same thing about someone who claims not to have a moral right to force certain choices on others in some circumstances (e.g. when those others have used copyrighted work in a product and ought to understand that for some not insignificant portion of the copyright holders, the terms implicitly included preserving certain "freedoms" for downstream recipients) while reserving a very similar moral right with others (e.g. potential murderers, theives, tresspassers, distributors of proprietary derived works).
I don't disagree that "morals" are something very personal, and you can thus never really argue on morals *except*for*your*own*behaviour*.
So I claim that for *me* the right choice is GPLv2 (or something similar). I think the GPLv3 is overreaching.
There's a very fundamental, and very basic rule that is often a good guideline. It's "Do unto others".
So the reason I *personally* like the GPLv2 is that it does unto others exactly what I wish they would do unto me.
It allows everybody do make that choice that I consider to be really
important: the choice of how something _you_ designed gets used.
And it does that exactly by *limiting* the license to only that one work. Not trying to extend it past the work.
See?
The GPLv3 can never do that. Quite fundamentally, whenever you extend the "reach" of a license past just the derived work, you will *always* get into a situation where people who designed two different things get into a conflict when they meet. The GPLv2 simply avoids the conflict entirely, and has no problem at all with the "Do unto others as you would have them do unto you".
In a very real sense, the GPLv3 asks people to do things that I personally would refuse to do. I put Linux on my kids computers, and I limit their ability to upgrade it. Do I have that legal right (I sure do, I'm their legal guardian), but the point is that this is not about "legality", this is about "morality". The GPLv3 doesn't match what I think is morally where I want to be. I think it *is* ok to control peoples hardware. I do it myself.
So your arguments about "potential murderes", "thieves", "trespassers" and "distributors of proprietary derived works" is totally missing the point.
It's missing the point that "morals" are about _personal_ choices. You cannot force others to a certain moral standpoint.
Laws (like copyright law) and legal issues, on the other hand, are fundamentally *not* about "personal" things, they are about interactions that are *not* personal. So laws need to be fundamnetally different from morals. A law has to take into account that different people have different moral background, and a law has to be _pragmatic_.
So trying to mix up a moral argument with a legal one is a fundamental mistake. They have two totally different and separate areas.
The GPLv2 is a *legal* license. It's not a "moral license" or a "spiritual guide". Its raison-d'etre is that pragmatic area where different peoples different moral rules meet.
In contrast, a persons *choice* to use the GPLv2 is his private choice. Totally different. My choice of the GPLv2 doesn't say anything about my choice of laws or legal issues.
You don't have to agree with it - but exactly because it's his private choice, it's a place where the persons moral rules matter, in a way that they do *not* matter in legal issues.
So killing, thieving, and distributing proprietary derived works are about *legal* choices. Are they also "immoral"? Who knows. Sometimes killing is moral. Sometimes thievery can me moral. Sometimes distributing derived works can be moral. Morality != legality. They are two totally different things.
Only religious fanatics and totalitarian states equate "morality" with "legality". There's tons of examples of that from human history. The ruler is not just a king, he's a God, so disagreeing with him is immoral, but it's also illegal, and you can get your head cut off.
In fact, a lot of our most well-known heroes are the ones that actually saw the difference between morals and laws.
A German soldier who refused to follow orders was clearly the more "moral" one, wouldn't you say? Never mind law. Gandhi is famous for his peaceful civil disobedience - was that "immoral" or "illegal"?
Or Robin Hood. A romantic tale, but one where the big fundamnetal part of the picture is the _difference_ between morality and legality.
Think about it.
Yes, there is obviously overlap, in that a lot of laws are there to protect things that people also consider "moral". But the fact that there is correlation should *not* cause anybody to think that they are at all about the same thing.
Quoted 2 lines
To call people who draw the line in a different place than you hypocrites is BS.
That was *not* what I did.
I don't think it's hypocritical to prefer the GPLv3. That's a fine choice, it's just not *mine*.
What I called hypocritical was to do so in the name of "freedom", while you're at the same time trying to argue that I don't have the "freedom" to make my own choice.
See? THAT is hypocritical.
Linus
Quoted 91 lines · Linus Torvalds
Quoted 4 lines · Dave Neuer
Quoted 3 lines
And anybody who thinks others don't have the "right to choice", and then tries to talk about "freedoms" is a damn hypocritical moron.
Quoted 8 lines
One might say the same thing about someone who claims not to have a moral right to force certain choices on others in some circumstances (e.g. when those others have used copyrighted work in a product and ought to understand that for some not insignificant portion of the copyright holders, the terms implicitly included preserving certain "freedoms" for downstream recipients) while reserving a very similar moral right with others (e.g. potential murderers, theives, tresspassers, distributors of proprietary derived works).
I don't disagree that "morals" are something very personal, and you can thus never really argue on morals *except*for*your*own*behaviour*.
So I claim that for *me* the right choice is GPLv2 (or something similar). I think the GPLv3 is overreaching.
There's a very fundamental, and very basic rule that is often a good guideline. It's "Do unto others".
So the reason I *personally* like the GPLv2 is that it does unto others exactly what I wish they would do unto me.
It allows everybody do make that choice that I consider to be really
important: the choice of how something _you_ designed gets used.And it does that exactly by *limiting* the license to only that one work. Not trying to extend it past the work.
See?
The GPLv3 can never do that. Quite fundamentally, whenever you extend the "reach" of a license past just the derived work, you will *always* get into a situation where people who designed two different things get into a conflict when they meet. The GPLv2 simply avoids the conflict entirely, and has no problem at all with the "Do unto others as you would have them do unto you".
In a very real sense, the GPLv3 asks people to do things that I personally would refuse to do. I put Linux on my kids computers, and I limit their ability to upgrade it. Do I have that legal right (I sure do, I'm their legal guardian), but the point is that this is not about "legality", this is about "morality". The GPLv3 doesn't match what I think is morally where I want to be. I think it *is* ok to control peoples hardware. I do it myself.
So your arguments about "potential murderes", "thieves", "trespassers" and "distributors of proprietary derived works" is totally missing the point.
It's missing the point that "morals" are about _personal_ choices. You cannot force others to a certain moral standpoint.
Laws (like copyright law) and legal issues, on the other hand, are fundamentally *not* about "personal" things, they are about interactions that are *not* personal. So laws need to be fundamnetally different from morals. A law has to take into account that different people have different moral background, and a law has to be _pragmatic_.
So trying to mix up a moral argument with a legal one is a fundamental mistake. They have two totally different and separate areas.
The GPLv2 is a *legal* license. It's not a "moral license" or a "spiritual guide". Its raison-d'etre is that pragmatic area where different peoples different moral rules meet.
In contrast, a persons *choice* to use the GPLv2 is his private choice. Totally different. My choice of the GPLv2 doesn't say anything about my choice of laws or legal issues.
You don't have to agree with it - but exactly because it's his private choice, it's a place where the persons moral rules matter, in a way that they do *not* matter in legal issues.
So killing, thieving, and distributing proprietary derived works are about *legal* choices. Are they also "immoral"? Who knows. Sometimes killing is moral. Sometimes thievery can me moral. Sometimes distributing derived works can be moral. Morality != legality. They are two totally different things.
Only religious fanatics and totalitarian states equate "morality" with "legality". There's tons of examples of that from human history. The ruler is not just a king, he's a God, so disagreeing with him is immoral, but it's also illegal, and you can get your head cut off.
In fact, a lot of our most well-known heroes are the ones that actually saw the difference between morals and laws.
Quoted 8 lines
A German soldier who refused to follow orders was clearly the more "moral" one, wouldn't you say? Never mind law. Gandhi is famous for his peaceful civil disobedience - was that "immoral" or "illegal"?
Or Robin Hood. A romantic tale, but one where the big fundamnetal part of the picture is the _difference_ between morality and legality.
Think about it.
Oh, I have, professor.
Quoted 5 lines
Yes, there is obviously overlap, in that a lot of laws are there to protect things that people also consider "moral". But the fact that there is correlation should *not* cause anybody to think that they are at all about the same thing.
No, they overlap in cases where the reason for the law is to enforce some moral edict, and when they're not in sync it's often because some person or group of people casuistically draw a moral distinction which is absent in the law (likely because it conflicts with some other group's moral values).
Your example of Robin Hood is instructive. Rich people quite likely don't agree with you that taking from the rich to give to the poor is moral, and they get more say (in a culturally-dependent fashion) when it comes time to codify the morals into laws.
Quoted 5 lines
Quoted 3 lines
To call people who draw the line in a different place than you hypocrites is BS.
That was *not* what I did.
It is.
Quoted 3 lines
I don't think it's hypocritical to prefer the GPLv3. That's a fine choice, it's just not *mine*.
I understand your oft-repeated (in this message alone) preference, which revolves around your personal "bright line" boundary of moral coercion at "I designed it."
Quoted 6 lines
What I called hypocritical was to do so in the name of "freedom", while you're at the same time trying to argue that I don't have the "freedom" to make my own choice.
See? THAT is hypocritical.
It is no more hypocritical than any other instance of restricting one person's freedom to protect some freedom of some other person. The law restricts your freedom to take things from my house in order to preserve my freedom to own things. That you don't disagree with that law indicates that you agree with the majority of people about where to draw the line between one person's freedom and another in that instance, not that you are a hypocrite or that people who steal are hypocrites (they're hypocrites if they complain about people stealing from them).
You have every right to prefer using your copyright to coerce people to provide source but not keys used to make binaries from that source run on hardware with which those binaries are distributed.
But people who prefer the GPLv3 in the name of freedom simply favor making explicit what they felt was always implicit in earlier versions, which is their wish that people who want to use what "they designed" do so in ways which comport with freedoms which are more important to them than the freedom of the hardware developer to design their system unconstrained (like the freedom of the end user to make their TiVO work some other way). They are no more hypocrites than you are for apparently feeling that it's OK for Robin Hood to steal from the rich to feed the poor.
Quoted 3 lines
Linus
Dave
Quoted 5 lines · Linus Torvalds
It allows everybody do make that choice that I consider to be really
important: the choice of how something _you_ designed gets used.And it does that exactly by *limiting* the license to only that one work. Not trying to extend it past the work.
Actually, the two paragraphs above are contradictory, and the second is not true in as much as it gives way to the former.
Consider an independent file contributed to Linux. It is an independent work. But the moment it gets combined with Linux, the only license you can use is GPLv2.
Consider a patch, or any modified version of Linux. It's another work. But the license applies to it as well.
Similarly, the GPL affects patents that somehow cover the work: the distributor can no longer enforce them against downstream users of the software.
See?
Quoted 1 line
The GPLv3 can never do that.
It does it in just the same way that GPLv1 and GPLv2 do: "no further restrictions". That it has to make some of them explicit, such that people understand they apply, or such that this provision can't be trampled on by other laws that by default trample copyright law, is just a legal implementation detail.
Quoted 2 lines
It's missing the point that "morals" are about _personal_ choices. You cannot force others to a certain moral standpoint.
FWIW, I tend to consider morals more of a society issue than an individual issue. Morals encode what the society understands to be the common good, and that's often something evolutionary, even with biological roots.
Laws (as you say) try to reflect the morals of the society, but since it's based on morals, it often lags behind. Which is why some laws become forgotten and no longer applied, even if still applicable in theory. And that's also why (as you alluded to in your message), when laws actively diverge from morals, you observe a lot of civil
disobedience: think DRM, DMCA, non-benevolent dictatorships and other abusive regimes.
I must say that it *is* lovely to watch you talk about morals in ways that I agree so much with, even if I dissent in a some details. This has further increased my admiration for you. Thank you.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 2 lines · Linus Torvalds
And anybody who thinks others don't have the "right to choice", and then tries to talk about "freedoms" is a damn hypocritical moron.
Yeah, it is indeed possible to twist it such that it sounds bad.
The important point is that one's freedom ends where another's starts. Unlimited freedom would be freedom to trample over others' freedoms too, and that's not right. That's why freedom of choice has to be used with care. Even fundamental human rights sometimes clash with each other.
We don't fight for the freedoms as goals in themselves. We fight for them because we understand they're essential for the common good.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · On Thursday 14 June 2007 23:22:48 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton
Faulty logic. The hardware doesn't *restrict* you from *MODIFYING* any fscking thing.
Ok, lemme try again:
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
And there is nothing in the license that says that this has to be done. Claiming that it is a requirement because of the "spirit" of the license or that such was the "intent" of the license does not make it any less legal than it is. And, as I've taken the time to explain to you, lacking any clear statement, written at the exact same time as the license, a statement of intent or spirit cannot have any real legal weight when the text of a license is finally decided upon. The reason, in case you missed the mail in which I gave it, is that the author *cannot*, no matter the belief anyone may have in their honesty or the oaths they may swear, be trusted to have *not* changed his/her mind as to the intent and/or spirit of the license at any time after the license goes into use.
DRH
Quoted 10 lines
Quoted 10 lines · On Thursday 14 June 2007 18:45:07 Alexandre Oliva wrote:
Quoted 9 lines
Where's the payback, or the payforward?
And then, tit-for-tat is about equivalent retaliation, an eye for an eye. Where's the retaliation here?
If GPLv2 were tit-for-tat, if someone invents artifices to prevent the user from making the changes the user wants on the software, wouldn't it be "equivalent retaliation" to prevent the perpetrator from making the changes it wants on the software?
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 10 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
Faulty logic. The hardware doesn't *restrict* you from *MODIFYING* any fscking thing.
Ok, lemme try again:
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
So? The user still has the source and is free to use that in other GPLv2 projects, that's the point. The point is not being able to run it on any specific hardware, the point is having the source with the
same rights to modify it and distribute it. And no, the right to
modify your copy of the source does not also mean you *have to* be able to install it on the hardware it was originally designed for - it only means you have the right to modify it and redistribute it.
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 11 lines · Jesper Juhl
Quoted 7 lines · Alexandre Oliva
Quoted 2 lines · Daniel Hazelton
Faulty logic. The hardware doesn't *restrict* you from *MODIFYING* any fscking thing.
case 2'': tivo provides source, end user tries to improve it, realizes the hardware won't let him use the result of his efforts, and gives up
So? The user still has the source and is free to use that in other GPLv2 projects, that's the point.
This point of yours is a distraction from the argument in this sub-thread.
These cases were Chris Friesen's attempt to show that GPLv2 was tit-for-tat, and case 2'' shows it isn't, at least not in the sense he tried to picture it:
Quoted 14 lines · Chris Friesen
Quoted 1 line · Alexandre Oliva
That's where Linus' theory of tit-for-tat falls apart.
Nope.
case 1: Upstream provides source, tivo modifies and distributes it (to their customers).
case 2: tivo provides source, end user modifies and distributes it (possibly to their customers, maybe to friends, possibly even to upstream).
See? Tit for tat.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 15 lines · On Thursday 14 June 2007 17:27:27 Alexandre Oliva wrote:
Quoted 6 lines · Daniel Hazelton
<somewhat sarcastic>
And the companies that produce devices that come with Linux and/or other GPL'd software installed and place limits such that only people that have purchased that hardware have access to the "modified" source running on the device are following the letter, and the spirit, of the GPL.WAIT, WAIT, THAT'S... :-)
Quoted 4 lines
Before you start yelling I'm wrong, think about it this way: they make the source available to the people that they've given binary versions to, and there is nothing stopping one of those people from making the source available to the rest of the world.
Quoted 4 lines
The *only* in your sentence betrayed you.
If they place the limits such that nobody else can access the sources, they're in violation of the license.
Nope. There is *NO* requirement *ANYWHERE* in the GPL, no matter the version, that says you have to *DISTRIBUTE* the source to *ANYONE* except those that you have given a binary to. Go read the licenses.
Quoted 4 lines
If they merely refrain from distributing the sources to others, but still enable the recipients to do so, this is not a violation of the license.
Exactly what I said. "only the people that have purchased the hardware have access to the modified sources"
That is *EXACTLY* what a number of companies have done - Acer (yes, the laptop company) has done that. They sell laptops running Linux, but unless you have purchased one of them you can't download the sources (or even replacement binaries) for the version of linux they put on their machines. (From Acer, that is)
However, as I also said, there is nothing stopping one of those people from making those "modified sources" available to the rest of the world. (I have yet to find someone that has done that with the Acer specific stuff, but...)
Quoted 7 lines
But then IANAL.
Quoted 2 lines
*AND* the GPL has never been about making the source available to everyone - just to those that get the binaries.
Exactly. Not even to the upstream distributor. That's where Linus' theory of tit-for-tat falls apart.
Yes, it does. However, the practicality is that there is nothing *stopping* the person upstream from getting a copy of the source and incorporating the modifications they contain in a new version.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 16 lines · Daniel Hazelton
Quoted 15 lines · On Thursday 14 June 2007 17:27:27 Alexandre Oliva wrote:
Quoted 6 lines · Daniel Hazelton
<somewhat sarcastic>
And the companies that produce devices that come with Linux and/or other GPL'd software installed and place limits such that only people that have purchased that hardware have access to the "modified" source running on the device are following the letter, and the spirit, of the GPL.WAIT, WAIT, THAT'S... :-)
Quoted 4 lines
Before you start yelling I'm wrong, think about it this way: they make the source available to the people that they've given binary versions to, and there is nothing stopping one of those people from making the source available to the rest of the world.
Quoted 8 lines
Quoted 4 lines
The *only* in your sentence betrayed you.
If they place the limits such that nobody else can access the sources, they're in violation of the license.
Nope. There is *NO* requirement *ANYWHERE* in the GPL, no matter the version, that says you have to *DISTRIBUTE* the source to *ANYONE* except those that you have given a binary to. Go read the licenses.
I agree. I even said so.
But the *only* gave me the impression that you were talking about magic, or any other sufficiently advanced technology ;-), that would enable the recipients to get the source code, but not usefully pass it on.
Quoted 5 lines
That is *EXACTLY* what a number of companies have done - Acer (yes, the laptop company) has done that. They sell laptops running Linux, but unless you have purchased one of them you can't download the sources (or even replacement binaries) for the version of linux they put on their machines. (From Acer, that is)
That's the sort of stuff that breaks the tit-for-tat premise. GPL indeed is not concerned about tit-for-tat. It's concerned about respect for the freedoms.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · Alexandre Oliva
Quoted 4 lines · Paul Mundt
I don't see how you can claim that the vendor is infringing on your freedom, _you_ made the decision to go out and buy the product knowing that the vendor wasn't going to go out of their way to help you hack the device.
But I also made this decision fully aware that the software included in the package was published under a license that said I was entitled to modify it.
And you certainly are free to do so. The vendor ships the product with the binaries, and you get the source as a result. You can in turn modify that source and do whatever you like with it. If the vendor is more proactive, they may have even tried to get all of their changes merged by the time the product hit the market, so they wouldn't be sitting on anything "special" anyways.
This however has nothing to do with your ability to apply those changes to the _hardware_. If the vendor doesn't want to, or is unable to support third-party modifications on their product, they have the basic right to make that decision, as you have the basic right not to buy the product if this is something that's going to be a problem for you.
Quoted 4 lines
More than once I purchased a device that claimed to have GNU/Linux software on it, only to find out that I couldn't use the freedoms, because the distributor was infringing the license in various ways.
In this example, at _no time_ did the vendor infringe on the license. They haven't given you an easy way to change the hardware, but they're completely compliant both in terms of the letter and the spirit (depending on how they work with the community) of the license.
If you're trying to pretend that GPLv2 had _anything_ to say about hardware, you'd be wrong. In such a situation, there'd hardly be a "need" (as you seem to see it) for GPLv3 at all. If you think this bizarre coupling of the hardware/software paradigm is in any way constructive, you're of course welcome to use the GPLv3, but this does not retroactively change the terms of the GPLv2 simply because you saw this as an area that was apparently "lacking".
And on the other hand, you're more than welcome to dual-license all of your kernel changes under v2/v3 if you really feel that that's the best way to go, just as I'm welcome to print out and burn the GPLv3 as a symbolic gesture. Simply because some folks have no intention of ever supporting v3 doesn't stop you from using it on any of your own changes.
Quoted 2 lines · Alexandre Oliva
BTW, what license is Linux licensed under? It's GPLv2 plus userland exception, right? (There's some additional module exception, right?)
Pure GPLv2.
Userland exception? Never heard of.
Module exception? Perhaps you mean "interpretation"?
Signature · 1 line
Krzysztof Halasa
Quoted 5 lines · Daniel Hazelton
Exactly. And I don't see anything about a TiVO (or any device that, like a TiVO, requires binaries that run on it to be digitally signed) that stops you
from exercising the "freedoms" guaranteed by the GPL. As I said before, what it does is stop you from violating the license on the hardware.
BTW: don't they sell their hardware (as well)? I think it should be easy to replace the ROMs (EPROMs? flash ROMs?) using some diagnostic clip and/or JTAG. Unless the CPU itself verifies ROM signatures, they shouldn't matter.
Signature · 1 line
Krzysztof Halasa
Quoted 5 lines · Alexandre Oliva
Quoted 4 lines · Daniel Hazelton
On Wednesday 13 June 2007 19:49:23 Alexandre Oliva wrote:
Exactly. They don't. What TiVO prevents is using that modified version on their hardware. And they have that right, because the Hardware *ISN'T*
^^^^^^^^^^^^^^
BTW as soon as I bought that thing, it is *my* hardware and no longer *theirs* (whoever "theirs" was).
Quoted 3 lines
Quoted 1 line
covered by the GPL.
Indeed, TiVO has this legal right. But then they must not use
Do they? At least in .at, it is usually impossible to (legally) limit the rights of the *owner* a (tangible) thing (and if I bought it, I *am* the owner and no one else) - even if you put it in the sales contract since this is discussion about/within sales law.
One usual example is "you buy a car and neither the car producer nor the (re)seller can restrict the brands of the tires you may use or the brand of the fuel etc.".
And the same holds for pretty much everything. No one can forbid you to open a TV set and fix it (or let it fix by whoever I choose to).
Yes, there are exceptions in several laws for specific things (e.g. for really dangerous ones like airbags in cars) but in general, you are allowed to do almost anything (including the simple destruction of it).
And yes, if you *rent* the thing, you are not the owner and this is a totally different thing.
Quoted 2 lines
software under the GPLv3 in it. And, arguably, they must not use software under the GPLv2 either.
Bernd
Signature · 3 lines
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and ServicesQuoted 11 lines · On Thursday 14 June 2007 04:37:55 Bernd Petrovitsch wrote:
Quoted 6 lines · Alexandre Oliva
Quoted 5 lines · Daniel Hazelton
On Wednesday 13 June 2007 19:49:23 Alexandre Oliva wrote:
Exactly. They don't. What TiVO prevents is using that modified version on their hardware. And they have that right, because the Hardware *ISN'T*
^^^^^^^^^^^^^^BTW as soon as I bought that thing, it is *my* hardware and no longer *theirs* (whoever "theirs" was).
eh. Perhaps I should have said that differently. And TiVO could handle it differently. I'm not going to argue about it anymore. It's pointless.
Quoted 4 lines
Quoted 3 lines
Quoted 1 line
covered by the GPL.
Indeed, TiVO has this legal right. But then they must not use
Quoted 8 lines
Do they? At least in .at, it is usually impossible to (legally) limit the rights of the *owner* a (tangible) thing (and if I bought it, I *am* the owner and no one else) - even if you put it in the sales contract since this is discussion about/within sales law.
One usual example is "you buy a car and neither the car producer nor the (re)seller can restrict the brands of the tires you may use or the brand of the fuel etc.".
No argument there. However, that is not to say that "you bought it, now you're free to do with it whatever you please" is always what the law says (at least in the US)
In the TiVO case there may be restrictions placed on the manufacturer for legal reasons or contractual reasons. Seeing as I'm not privy to the contracts between TiVO and the various production and broadcasting companies I can't comment on what contracts they have. As to the legal side there are restrictions in copyright law.
Quoted 2 lines
And the same holds for pretty much everything. No one can forbid you to open a TV set and fix it (or let it fix by whoever I choose to).
I know of at least one company that will sell you the parts to repair your TV if its out of warranty.
DRH
Quoted 11 lines
Yes, there are exceptions in several laws for specific things (e.g. for really dangerous ones like airbags in cars) but in general, you are allowed to do almost anything (including the simple destruction of it).
And yes, if you *rent* the thing, you are not the owner and this is a totally different thing.
Quoted 2 lines
software under the GPLv3 in it. And, arguably, they must not use software under the GPLv2 either.
Bernd
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 1 line · Daniel Hazelton
On Thursday 14 June 2007 04:37:55 Bernd Petrovitsch wrote:
[...]
Quoted 9 lines
Quoted 9 lines
Quoted 3 lines
Quoted 1 line
covered by the GPL.
Indeed, TiVO has this legal right. But then they must not use
Do they? At least in .at, it is usually impossible to (legally) limit the rights of the *owner* a (tangible) thing (and if I bought it, I *am* the owner and no one else) - even if you put it in the sales contract since this is discussion about/within sales law.
Quoted 7 lines
Quoted 3 lines
One usual example is "you buy a car and neither the car producer nor the (re)seller can restrict the brands of the tires you may use or the brand of the fuel etc.".
No argument there. However, that is not to say that "you bought it, now you're free to do with it whatever you please" is always what the law says (at least in the US)
Of course not (and I neither stated nor implied it) - there are lots of laws which forbid killing other people etc.
But the seller of the car is not in the position to forbid anything (which is not forbidden by the law), e.g. ha cannot forbid to replace the motor or similar thing. I may loose guarantee or have to cope with other consequences (if it is done badly), but that is my problem and decision.
Quoted 2 lines
In the TiVO case there may be restrictions placed on the manufacturer for legal reasons or contractual reasons. Seeing as I'm not privy to the
Frankly, I really don't care that much about legal and contractual reasons of the *manufacturer* (starting from waste disposal regulations up to tax regulations, etc.) and they are irrelevant to me anyways. At most I can have
*) legal restrictions (obviously coming from the law) on the *usage* of
the device or
*) from a contract (obviously with the seller of the device since there
is no other involved - and this contract may contain inapplicable clauses - e.g. sth. like "you are not allowed hear German music with this device").
And I don't have a contract with the manufacturer so there can't be any limitation by the manufacturer.
Quoted 2 lines
contracts between TiVO and the various production and broadcasting companies I can't comment on what contracts they have. As to the legal side there are
And they are pretty irrelevant anyways to everyone else.
Quoted 1 line
restrictions in copyright law.
ACK. But copyright law (at least the equivalent in .at and very probably .de - and IMHO it is probably everywhere else similar simply because copyright/authors rights laws was actually designed and written to deal with music, literature, etc. which are intangible by nature) simply doesn't apply to hardware as such (pun intended;-).
Bernd
Signature · 3 lines
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and ServicesQuoted 9 lines · Bernd Petrovitsch
Quoted 5 lines · Alexandre Oliva
Quoted 4 lines · Daniel Hazelton
On Wednesday 13 June 2007 19:49:23 Alexandre Oliva wrote:
Exactly. They don't. What TiVO prevents is using that modified version on their hardware. And they have that right, because the Hardware *ISN'T*
^^^^^^^^^^^^^^BTW as soon as I bought that thing, it is *my* hardware and no longer *theirs* (whoever "theirs" was).
You bought *their* design. It was your choice.
And yes, you own the hardware, and you can hack it any which way you like (modulo laws and any other contracts you signed when you bought it). But they had the right to design it certain ways, and part of that design may be making it _harder_ for you to hack.
For example, they may have used glue to put the thing together rather than standard phillips screws. Or poured resin over some of the chips. All of which has been done (not necessarily with Linux, but this really is an issue that has nothing to do with Linux per se). Making the firmware or hardware harder to access or modify is their choice.
Your choice is whether you buy it, despite the fact that you know it's not necessarily all that easy to hack.
Quoted 6 lines
Quoted 1 line
Indeed, TiVO has this legal right. But then they must not use
Do they? At least in .at, it is usually impossible to (legally) limit the rights of the *owner* a (tangible) thing (and if I bought it, I *am* the owner and no one else) - even if you put it in the sales contract since this is discussion about/within sales law.
The "when I buy it, I own it" argument is a favourite of the GPLv3 shills, but it's irrelevant. The *design* was done long before you bought it, and yes, Tivo had the right to design and build it, any which way they wanted to.
Quoted 6 lines
One usual example is "you buy a car and neither the car producer nor the (re)seller can restrict the brands of the tires you may use or the brand of the fuel etc.".
And the same holds for pretty much everything. No one can forbid you to open a TV set and fix it (or let it fix by whoever I choose to).
You are missing the picture. Sure, you can do whatever you want to (within any applicable laws) _after_ you bought it. But that doesn't take away the right from the manufacturer to design it his way.
And you're also *wrong*. Tivo doesn't limit the brands of electricity it uses or anything idiotic like that. You can put after-market rubber bumps on the thing to make it look sleeker, and I seriously doubt that Tivo will do aythign at all. It's about going into the innards, and different car manufacturers make that harder too, for various reasons.
If the car manufacturer makes things harder to hack, it's your choice. For example, car hackers *do* actually prefer certain brands. Apparently the Subaru's are popular, and German cars are a pain to try to change. I'm told that even somethign as simple as upgrading the sound system is just _harder_ in a German car, apparently because they make things fit together so tightly, that doing after-market cabling is just much more of a problem.
Same goes for things like electronic engine controls. Look it up. Try chipping a car lately? For some, it's literally buying a chip online, and some fairly simple work. For others, it's almost impossible, and you have to take your car in to somebody who really knows what he's doing. And you know what? Exactly like with a Tivo, the car manufacturer won't have anything to do with the car afterwards. If you broke it by chipping it, you voided your warranty.
See? If you are actually looking for a car to hack on, you'd buy a car with that in mind. Do the exact same thing with your Tivo. Don't buy it if you want to hack it: buy a Neuros OSD device instead! I'm serious: the Neuros people do *not* limit you, and in fact they encourage hacking. Instead of whining about Tivo, do something *positive*, and support Neuros for their better policies!
Linus
On Wed, 2007-06-13 at 20:42 -0400, Daniel Hazelton wrote:
<SNIP>
Quoted 7 lines
Quoted 3 lines
Do you deny that TiVo prevents you (or at least a random customer) from modifying the copy of Linux that they ship in their DVR?
Exactly. They don't. What TiVO prevents is using that modified version on their hardware. And they have that right, because the Hardware *ISN'T* covered by the GPL.
The hardware isn't directly covered by the GPL, correct. But, if they want to use the software on the hardware, they have to comply with the GPL. The software license can then influence hardware IF they want to use it badly enough.
For example, the hardware is perfectly capable of being used to break the terms of the GPL by being used to distribute a modified binary without releasing the source. But the hardware's behavior is restricted by the software for the betterment of all.
This whole argument is about the spirit of the GPL. Linus and others think the spirit is one thing, the FSF guys think its something else. Since the license is clearly owned by the FSF, I think they get the final vote on what they "intended" it to be when they wrote it, no? If they say they intended it to not allow Tivoization then believe them, because they are the only ones that know what they were thinking when they wrote it! The GPLv2 seems to allow it though. If Linus and friends want to allow it, then they can stay with the GPLv2. For those who want to disallow Tivoization, choose v3. No worries guys.
Quoted 1 line
Do you understand that, or do I need to break out the finger-puppets next ?
Guys, we are all friends here. No reason to be so insulting. Its just a difference of opinion. People seem to be talking past each other instead of to one another. This usually happens when people are basing their underlying assumptions on different things and not listening to the other. Please take a step back and think about it.
<SNIP>
Quoted 4 lines · Kevin Fox
The hardware isn't directly covered by the GPL, correct. But, if they want to use the software on the hardware, they have to comply with the GPL.
Only with the GPLv3.
Again, don't confuse the *new* requirements in the GPLv3 with any "GPL requirements". They didn't exist before. The kernel never signed up to them. They are irrelevant for the discussion.
So hardware details have *nothing* to do with compying with the GPLv2.
Could you write *another* license that puts limitations on the hardware or environment that you have to comply with? Sure can. And the GPLv3 does that. But the GPLv2 does not, and that's a fundmanetal *improvement* over the GPLv3 in my opinion.
Do you like licenses that force the licensee to give money back?
So why do you like licenses that force the licensee to give access to hardware back? It's a form of "extra compensation" that the GPLv2 never had. The GPLv2 talks about giving access to the *source* code. The GPLv3 talks about giving access to the *hardware*.
Can people really not see the difference, and why I might think it's a fundamental difference, and why I might choose to say that the GPLv3 is a worse license?
And *why* would I ever downgrade to a worse license? There had better be some really pressing reason to choose the worse version of the GPL. And I just don't find that reason in the GPLv3 itself - although, as mentioned, the reason could become *external* (ie I might accept a worse license it it comes with external code attached to it that I think makes up for the license deficiency).
Linus
Quoted 7 lines · Linus Torvalds
Quoted 4 lines · Kevin Fox
The hardware isn't directly covered by the GPL, correct. But, if they want to use the software on the hardware, they have to comply with the GPL.
Only with the GPLv3.
This is not true. The terms of the GPLv2 that say you can't impose further restrictions on the exercise of the freedoms apply to the software under GPLv2 and GPLv3 just the same way.
Quoted 4 lines
Do you like licenses that force the licensee to give money back?
So why do you like licenses that force the licensee to give access to hardware back?
I don't know where the 'back' in the second question amounts to, but it definitely isn't about GPLv3.
In fact, the GPL isn't about giving anything back. It's about passing on.
So both requirements, as you phrased them, would be equally wrong.
So let's change the question to turn them into forms of passing on:
Do you like licenses that force the licensee to pass money on?
Do you like licenses that force the licensee to pass on access to hardware?
This is still bad. This is still not what the GPLv3 is about. There's no requirement to let the user go wild and do whatever she likes on the hardware.
The only requirement is the one that was always there: to respect the freedoms of the users of the software, i.e., let them modify and share the software, not imposing any further restrictions, by whatever means.
So the second question would be correctly phrased as
Do you like licenses that force the licensee to pass on the right to modify the software in the hardware containing it?
Or, reframing it:
Do you like licenses that permit the licensee to deny others the right to modify the software in the hardware containing it?
Quoted 1 line
It's a form of "extra compensation" that the GPLv2 never had.
No, sir, it's still respect for the freedoms. The same "in kind" contribution as always.
Quoted 1 line
The GPLv2 talks about giving access to the *source* code.
It does. But that's not all. Even GPLv1 went further than that.
Quoted 3 lines
Can people really not see the difference, and why I might think it's a fundamental difference, and why I might choose to say that the GPLv3 is a worse license?
Since someone brought liberal (Original BSD, Modified BSD, MIT, etc) licenses into the picture, and you expressed dislike for them, let me pick that up for a moment.
Quoted 4 lines
The license doesn't encode my fundamental beliefs of "fairness". I think the BSD license encourages a "everybody for himself" mentality, and doesn't encourage people to work together, and to merge.
And then you say what TiVO does is ok, saying:
Quoted 2 lines
Oh, but you want to hack the hardware to accept it? That's a totally different issue. If so, buy a Neuros OSD box.
Sounds a lot like the very "everybody for himself" attitude you dislike.
So can you please explain to me how enabling TiVO to deny others the freedom that it received "in kind", failing to keep with the "in kind" spirit of the GPL, encourage people to work together, and to merge?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
So can you please explain to me how enabling TiVO to deny others the freedom that it received "in kind", failing to keep with the "in kind" spirit of the GPL, encourage people to work together, and to merge?
They're not denying others the freedom that they themselves received. Tivo took GPL'd software, modified it, and distributed it with their own custom hardware. You have the right to take their changes, possibly modify them further, and distribute them (possibly with your own hardware).
The fact that you can't modify the software and load it back onto the tivo is irrelevent. They are not restricting your distribution of the software in any way. Rather, they're restricting the *running* of the software on their proprietary hardware platform.
Chris
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines
Only with the GPLv3.
This is not true. The terms of the GPLv2 that say you can't impose further restrictions on the exercise of the freedoms apply to the software under GPLv2 and GPLv3 just the same way.
The GPLv2 talks *only* about the software. You're making everything else up, and when I point out that your reading of the GPLv2 is insane, you just ignore my proofs of your internal inconsistency.
Quoted 3 lines
So can you please explain to me how enabling TiVO to deny others the freedom that it received "in kind", failing to keep with the "in kind" spirit of the GPL, encourage people to work together, and to merge?
Because Tivo *IS NOT DENYING* those freedoms.
Tivo *respected* the freedoms, and gave source back, and gave you all the same rights you had to Linux originally, and to their modifications.
How stupid are you to not acknowledge that?
Tivo limited their *hardware*, not the software.
Linus
Quoted 6 lines · Linus Torvalds
Tivo *respected* the freedoms, and gave source back, and gave you all the same rights you had to Linux originally, and to their modifications.
How stupid are you to not acknowledge that?
Tivo limited their *hardware*, not the software.
Have you ever wondered *why* it limited the hardware?
Is it per chance such that I cannot modify the software that runs on the hardware?
How is that respecting the freedoms? How is this not imposing further restrictions?
And, more importantly, how is it that permitting this makes for *better* compliance with your tit-for-tat conceptions about the GPL?
I.e., if Tivoization is the only issue that you think makes GPLv3 a worse license than GPLv2, and you like GPLv2 because of this tit-for-tat, surely you should be able to explain why Tivoization promotes this tit-for-tat notion better than GPLv3, right?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 5 lines · Alexandre Oliva
Quoted 2 lines · Linus Torvalds
Tivo *respected* the freedoms, and gave source back, and gave you all the same rights you had to Linux originally, and to their modifications.
Quoted 8 lines
Quoted 3 lines
How stupid are you to not acknowledge that?
Tivo limited their *hardware*, not the software.
Have you ever wondered *why* it limited the hardware?
Is it per chance such that I cannot modify the software that runs on the hardware?
if you cannot modify the software that runs on your Tivo hardware you haven't tried very hard.
true, they don't go out of their way to make it easy, but even if they didn't do the integrity checking of the system it still wouldn't be easy to load your own software on the tivo, there's no path to load the software without disassembling the hardware.
Quoted 2 lines
How is that respecting the freedoms? How is this not imposing further restrictions?
I think the software is all available at www.tivo.com/linux that provides you all the freedom that they got.
David Lang
Quoted 10 lines
And, more importantly, how is it that permitting this makes for *better* compliance with your tit-for-tat conceptions about the GPL?
I.e., if Tivoization is the only issue that you think makes GPLv3 a worse license than GPLv2, and you like GPLv2 because of this tit-for-tat, surely you should be able to explain why Tivoization promotes this tit-for-tat notion better than GPLv3, right?
Quoted 2 lines · On Friday 15 June 2007 01:46, [email protected] wrote:
if you cannot modify the software that runs on your Tivo hardware you haven't tried very hard.
Yes, but the GPLv2 clearly says that you don't have to try very hard. The preferred form of modification has to be distributed. I can run a decompiler or disassembler on a program, and I can even modify it in place with a hex editor (I have even modified programs in embedded ROMs by using focussed ion beam, so I know you can modify every program if you try hard enough). It's certainly possible to crack Tivo's firmware to accept my own signature, but it's *not* the preferred form of modification, the source code and Tivo's key for the signature.
Since Tivo's firmware only accepts a signed kernel, the combination of kernel+signature is the binary they ship. The kernel itself is useless, the signature as well. Therefore, you can imply that Tivo's key is part of the "other stuff" the GPLv2 mentions, because you need it to recreate the same code as Tivo did and shipped (compilers insert timestamps and such), and to modify that code. The source code is just a mean, the thing they shipped is the end (the binary), and they have to comply with the GPL for that binary - which by all means of practical understanding includes the signature.
"You can imply" means: It depends on court and legal system. I'm quite confident that in Germany, the legal system might favor the "GPLv2 does not allow tivoization" point of view, and in the USA, the legal sysem might do the opposite.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 4 lines · On Friday 15 June 2007 05:30:09 Bernd Paysan wrote:
Quoted 2 lines · On Friday 15 June 2007 01:46, [email protected] wrote:
if you cannot modify the software that runs on your Tivo hardware you haven't tried very hard.
Quoted 8 lines
Yes, but the GPLv2 clearly says that you don't have to try very hard. The preferred form of modification has to be distributed. I can run a decompiler or disassembler on a program, and I can even modify it in place with a hex editor (I have even modified programs in embedded ROMs by using focussed ion beam, so I know you can modify every program if you try hard enough). It's certainly possible to crack Tivo's firmware to accept my own signature, but it's *not* the preferred form of modification, the source code and Tivo's key for the signature.
How is a signing key part of the "preferred form for modification"? It isn't a requirement to *modify* anything, just to *replace* something. (And I am *NOT* going to explain why "replace != modify" again)
Quoted 9 lines
Since Tivo's firmware only accepts a signed kernel, the combination of kernel+signature is the binary they ship. The kernel itself is useless, the signature as well. Therefore, you can imply that Tivo's key is part of the "other stuff" the GPLv2 mentions, because you need it to recreate the same code as Tivo did and shipped (compilers insert timestamps and such), and to modify that code. The source code is just a mean, the thing they shipped is the end (the binary), and they have to comply with the GPL for that binary - which by all means of practical understanding includes the signature.
I can find no such requirement in the GPLv2. In fact, it actually says that you don't even have to be able to *USE* the program. See section 12 of the GPL if you don't believe me.
Quoted 4 lines
"You can imply" means: It depends on court and legal system. I'm quite confident that in Germany, the legal system might favor the "GPLv2 does not allow tivoization" point of view, and in the USA, the legal sysem might do the opposite.
In light of the d-link case, I'm pretty certain that the German Courts interpretation of the GPLv2 makes "Tivoization" a violation. In the US I can say that the result would be "GPLv2 does not disallow tivoization". As I've pointed out in other posts, the GPLv2 actually *limits* itself to three specific "activities". Whether it was intended to "incidentally" cover other things or not, it does *clearly* state what it's scope is. If that scope *IS* *NOT* the intent of the person and/or person who authored the license, that text *SHOULD* *NOT* exist.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 14 lines · Daniel Hazelton
Quoted 4 lines · On Friday 15 June 2007 05:30:09 Bernd Paysan wrote:
Quoted 2 lines · On Friday 15 June 2007 01:46, [email protected] wrote:
if you cannot modify the software that runs on your Tivo hardware you haven't tried very hard.
Quoted 8 lines
Yes, but the GPLv2 clearly says that you don't have to try very hard. The preferred form of modification has to be distributed. I can run a decompiler or disassembler on a program, and I can even modify it in place with a hex editor (I have even modified programs in embedded ROMs by using focussed ion beam, so I know you can modify every program if you try hard enough). It's certainly possible to crack Tivo's firmware to accept my own signature, but it's *not* the preferred form of modification, the source code and Tivo's key for the signature.
Quoted 3 lines
How is a signing key part of the "preferred form for modification"? It isn't a requirement to *modify* anything, just to *replace* something. (And I am *NOT* going to explain why "replace != modify" again)
The signing key determines a critical portion of the binary form that was distributed. You cannot produce that portion of the binary form without the signing key. Without that portion, the binary form does not perform the function for which it is distributed. If you think such an input is not part of "the preferred form for modification", I have a bridge to sell you.
The work that the GPL protects a recipient's right to modify and redistribute is not the source code -- it is each form the user receives.
Quoted 10 lines
Quoted 9 lines
Since Tivo's firmware only accepts a signed kernel, the combination of kernel+signature is the binary they ship. The kernel itself is useless, the signature as well. Therefore, you can imply that Tivo's key is part of the "other stuff" the GPLv2 mentions, because you need it to recreate the same code as Tivo did and shipped (compilers insert timestamps and such), and to modify that code. The source code is just a mean, the thing they shipped is the end (the binary), and they have to comply with the GPL for that binary - which by all means of practical understanding includes the signature.
Quoted 3 lines
I can find no such requirement in the GPLv2. In fact, it actually says that you don't even have to be able to *USE* the program. See section 12 of the GPL if you don't believe me.
Section 12 of the GPL(v2) is a warranty and liability disclaimer. It is not an absolution of license obligations. It limits the liability of a distributor to the end user, not to copyright owners.
Michael Poole
Quoted 2 lines · Kevin Fox
This whole argument is about the spirit of the GPL. Linus and others think the spirit is one thing, the FSF guys think its something else.
What the fsck it is, linux-kernel or bleeding Council of Nikea?
Quoted 6 lines · On Thursday 14 June 2007 12:06:31 Kevin Fox wrote:
On Wed, 2007-06-13 at 20:42 -0400, Daniel Hazelton wrote:
<SNIP>Quoted 3 lines
Quoted 2 lines
Do you deny that TiVo prevents you (or at least a random customer) from modifying the copy of Linux that they ship in their DVR?
Quoted 8 lines
Quoted 3 lines
Exactly. They don't. What TiVO prevents is using that modified version on their hardware. And they have that right, because the Hardware *ISN'T* covered by the GPL.
The hardware isn't directly covered by the GPL, correct. But, if they want to use the software on the hardware, they have to comply with the GPL. The software license can then influence hardware IF they want to use it badly enough.
Until GPLv3 there was no requirement that the modified code be able to operate on any given device - even the one its designed for. Claiming otherwise seems stupid to me, almost ridiculous.
Quoted 4 lines
For example, the hardware is perfectly capable of being used to break the terms of the GPL by being used to distribute a modified binary without releasing the source. But the hardware's behavior is restricted by the software for the betterment of all.
But this can be done *NOW* - has been done by at least one company, IIRC. (and, IIRC again, they didn't so much as "not release the modified version" as "not release all tools/scripts/installation/build instructions")
Quoted 10 lines
This whole argument is about the spirit of the GPL. Linus and others think the spirit is one thing, the FSF guys think its something else. Since the license is clearly owned by the FSF, I think they get the final vote on what they "intended" it to be when they wrote it, no? If they say they intended it to not allow Tivoization then believe them, because they are the only ones that know what they were thinking when they wrote it! The GPLv2 seems to allow it though. If Linus and friends want to allow it, then they can stay with the GPLv2. For those who want to disallow Tivoization, choose v3. No worries guys.
Quoted 8 lines
Quoted 2 lines
Do you understand that, or do I need to break out the finger-puppets next ?
Guys, we are all friends here. No reason to be so insulting. Its just a difference of opinion. People seem to be talking past each other instead of to one another. This usually happens when people are basing their underlying assumptions on different things and not listening to the other. Please take a step back and think about it.
I noticed that ten or twenty messages after I made that comment. In truth, the reason I made it was, and is, because I am tired of explaining the fact that there is no "one" interpretation of the GPLv2 - or any license - *UNLESS* it has been ruled on by a court. And even then, the courts ruling only applies to the parts of the license that were in contention before it.
DRH
Quoted 1 line
<SNIP>
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 8 lines · Alexandre Oliva
if you distribute copies of such a program, [...] you must give the recipients all the rights that you have
So, TiVo includes a copy of Linux in its DVR.
TiVo retains the right to modify that copy of Linux as it sees fit.
It doesn't give the recipients the same right.
Sure it does; you received a program (the kernel) and you can modify it. You also received hardware; they don't support modification of that. Nowhere in the license does it say they have to, because the license only covers the program.
Or are you claiming that putting software on hardware makes the result a derivative work? I think it falls under the "mere aggregation" clause.
What if TiVo had put the kernel in a burned-in ROM (not flash, or on a flash ROM with no provision for reprogramming it)? Would that also violate the "spirit" of the GPL? Must any device that wishes to include GPL code include additional hardware to support replacing that code (even if that hardware is otherwise superfluous)?
Quoted 5 lines
What if TiVo had put the kernel in a burned-in ROM (not flash, or on a flash ROM with no provision for reprogramming it)? Would that also violate the "spirit" of the GPL? Must any device that wishes to include GPL code include additional hardware to support replacing that code (even if that hardware is otherwise superfluous)?
This is an area the GPLv3 tries to clarify and for good reason.
Of course these days in the US someone would probably sue arguing that a ROM is protection scheme ;)
Alan
Quoted 5 lines
What if TiVo had put the kernel in a burned-in ROM (not flash, or on a flash ROM with no provision for reprogramming it)? Would that also violate the "spirit" of the GPL? Must any device that wishes to include GPL code include additional hardware to support replacing that code (even if that hardware is otherwise superfluous)?
As a PS to the GPL3 comment here is the basic difference
ROM - I can't modify the code on the device
The creator can't modify the code further on the device
Tivo - I can't modify the code on the device
The owner can modify the code
One is an implicit limitation of the hardware (just like I can't run openoffice on a 4MB PC even though the license gives me the right to try), the other is an artificial restriction.
One case is witholding freedom in the GPL sense by one party while keeping it themselves, the other is a limitation of the system inevitably imposed on everyone.
Quoted 9 lines · Alan Cox
As a PS to the GPL3 comment here is the basic difference
ROM - I can't modify the code on the device
The creator can't modify the code further on the deviceTivo - I can't modify the code on the device
The owner can modify the code
Quoted 7 lines
One is an implicit limitation of the hardware (just like I can't run openoffice on a 4MB PC even though the license gives me the right to try), the other is an artificial restriction.
One case is witholding freedom in the GPL sense by one party while keeping it themselves, the other is a limitation of the system inevitably imposed on everyone.
I've been following this discussion and I find this interesting. Consider these two cases:
1.) I ship the device back to the manufacturer, they replace the ROM,
and ship it back to me.
2.) I ship the device back to the manufacturer, they load new code
into it, and ship it back to me.
How do these two differ? Or is it now just a question of the ROM being in a socket? I can't see how the technicalities of how the hardware is constructed can change the legality of the software.
Signature · 1 line
Dan
Quoted 9 lines · Daniel Forrest
1.) I ship the device back to the manufacturer, they replace the ROM,
and ship it back to me.2.) I ship the device back to the manufacturer, they load new code
into it, and ship it back to me.How do these two differ? Or is it now just a question of the ROM being in a socket? I can't see how the technicalities of how the hardware is constructed can change the legality of the software.
I don't see that they differ. If the software can be replaced, the manufacturer ought to tell you how to do it. It doesn't have to do it for you, it doesn't have to give you the hardware tools needed to do it, but if you're not able to start from the source code and the information provided by the manufacturer and get to a modified version of the software on the device, while the manufacturer could do it, then the manufacturer is locking you in, and therefore you're not free. This is a clear violation of the spirit of the license, even if the legalese might make room for some such misbehavior.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 22 lines
Quoted 8 lines
As a PS to the GPL3 comment here is the basic difference
ROM - I can't modify the code on the device
The creator can't modify the code further on the deviceTivo - I can't modify the code on the device
The owner can modify the codeQuoted 7 lines
One is an implicit limitation of the hardware (just like I can't run openoffice on a 4MB PC even though the license gives me the right to try), the other is an artificial restriction.
One case is witholding freedom in the GPL sense by one party while keeping it themselves, the other is a limitation of the system inevitably imposed on everyone.
I've been following this discussion and I find this interesting. Consider these two cases:
1.) I ship the device back to the manufacturer, they replace the ROM,
and ship it back to me.
Quoted 6 lines
2.) I ship the device back to the manufacturer, they load new code
into it, and ship it back to me.How do these two differ? Or is it now just a question of the ROM being in a socket? I can't see how the technicalities of how the hardware is constructed can change the legality of the software.
At first glance I think a construct where the manufacturer is obliged to load _MY_ modified software in a timely fashion and at a reasonable price into the device would fit my understanding of the GPL's spirit though this leaves room for the definition of timely...
Best,
Michael
Signature · 5 lines
Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar Sitz Hamburg; HRB 89145 Amtsgericht Hamburg Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: [email protected] GPG-keys available on request or at public keyserver
Quoted 10 lines
I've been following this discussion and I find this interesting. Consider these two cases:
1.) I ship the device back to the manufacturer, they replace the ROM,
and ship it back to me.2.) I ship the device back to the manufacturer, they load new code
into it, and ship it back to me.How do these two differ? Or is it now just a question of the ROM
Thats one thing I don't like about the GPL3 special casing.
Quoted 2 lines
being in a socket? I can't see how the technicalities of how the hardware is constructed can change the legality of the software.
In the replace/reflash the ROM case its about access to the righ tools - I could do it myself, send it to another company to load my code etc.
In the Tivo case its about one company having the ability to make such mods and blocking others from doing so.
Quoted 6 lines · Alan Cox
Quoted 5 lines
What if TiVo had put the kernel in a burned-in ROM (not flash, or on a flash ROM with no provision for reprogramming it)? Would that also violate the "spirit" of the GPL? Must any device that wishes to include GPL code include additional hardware to support replacing that code (even if that hardware is otherwise superfluous)?
Quoted 7 lines
As a PS to the GPL3 comment here is the basic difference
ROM - I can't modify the code on the device
The creator can't modify the code further on the deviceTivo - I can't modify the code on the device
The owner can modify the code
Tivo gets sick of the endless flamewars on lkml, signs a copy of QNX, pushes it out to the hardware. No more Linux on Tivo.
You also can't replace that but Tivo can. As I see it the two are completely orthagonal:
a) Can anyone but the manufacturer upload new software into a a device without taking extreme measures (soldering a new public-key-containing-chip onto the board)
b) Is the software currently installed on a device licenced under a rule which requires the distributor to also distribute source code upon request.
Now I think it would reasonable to ask that the source code be able to be built by [same compiler, same flags, same ...] to produce an identical binary to the one running on the device so you can confirm that it's exactly the same code. That's separate from being able to upload a changed binary.
Bron.
Quoted 2 lines · Bron Gondwana
Tivo gets sick of the endless flamewars on lkml, signs a copy of QNX, pushes it out to the hardware. No more Linux on Tivo.
What do we lose?
Do we actually get any benefit whatsoever from TiVO's choice of Linux as the kernel for its device?
Do TiVO customers lose anything from the change from one non-Free software to another? (the Linux binary, as shipped in the TiVO, has become non-Free)
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · Alexandre Oliva
Quoted 2 lines · Bron Gondwana
Tivo gets sick of the endless flamewars on lkml, signs a copy of QNX, pushes it out to the hardware. No more Linux on Tivo.
What do we lose?
Do we actually get any benefit whatsoever from TiVO's choice of Linux as the kernel for its device?
Sure, if they make any changes or fixes to Linux. Other than that, only the same benefit that Microsoft get from Windows piracy - TiVo employees become familiar with Linux and are more likely to use it and maybe contribute more in another job later.
What we don't get is TiVo having a better kernel than everyone else because they've put some work into extending it without giving that work back.
I see stuff in arch/powerpc/kernel/ which is Copyright "TiVo, Inc" and more recent stuff in usb/net/asix.c and usb/net/mcs7830.c which is more than I've ever contributed to the kernel, despite making extensive use and even selling services where I ran servers with Linux on them but didn't allow my customers to change the kernel on the servers if there was some feature they wanted to play with.
Quoted 3 lines
Do TiVO customers lose anything from the change from one non-Free software to another? (the Linux binary, as shipped in the TiVO, has become non-Free)
Not particularly, no. Other than maybe some nice features that TiVo gains from being able to use Linux.
Bron.
Quoted 9 lines · Bron Gondwana
Quoted 2 lines · Alexandre Oliva
Do we actually get any benefit whatsoever from TiVO's choice of Linux as the kernel for its device?
Sure, if they make any changes or fixes to Linux. Other than that, only the same benefit that Microsoft get from Windows piracy - TiVo employees become familiar with Linux and are more likely to use it and maybe contribute more in another job later.
Now, what if TiVO actually permitted all of its customers to make changes or fixes to Linux, and become familiar with it and become more likely to use it and maybe contribute more later?
Would we lose more or gain more?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 4 lines
Sure, if they make any changes or fixes to Linux. Other than that, only the same benefit that Microsoft get from Windows piracy - TiVo employees become familiar with Linux and are more likely to use it and maybe contribute more in another job later.
Now, what if TiVO actually permitted all of its customers to make changes or fixes to Linux, and become familiar with it and become more likely to use it and maybe contribute more later?
a) there's nothing that prevents a Tivo user from changing or fixing Linux completely outside of the Tivo
b) the 'interesting' bits that someone would modify the Tivo to change *aren't actually the bits that everyone is kvetching about here*
Bill
Quoted 6 lines · Bill Nottingham
Quoted 5 lines · Alexandre Oliva
Quoted 4 lines
Sure, if they make any changes or fixes to Linux. Other than that, only the same benefit that Microsoft get from Windows piracy - TiVo employees become familiar with Linux and are more likely to use it and maybe contribute more in another job later.
Quoted 6 lines
Quoted 3 lines
Now, what if TiVO actually permitted all of its customers to make changes or fixes to Linux, and become familiar with it and become more likely to use it and maybe contribute more later?
a) there's nothing that prevents a Tivo user from changing or fixing Linux completely outside of the Tivo
But how about inside the TiVO, so as to use Linux and the rest of the GNU/Linux distro put in there for an even better DVR experience?
Sure, this might still be accomplished on another hardware platform. But the TiVO already has all the hardware there, and you already have all the software ready to work on it. Except that you can't change it. You'd have to waste time and money just to get to the same status on another hardware platform.
What do we gain?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 10 lines · Alexandre Oliva
But how about inside the TiVO, so as to use Linux and the rest of the GNU/Linux distro put in there for an even better DVR experience?
Sure, this might still be accomplished on another hardware platform. But the TiVO already has all the hardware there, and you already have all the software ready to work on it. Except that you can't change it. You'd have to waste time and money just to get to the same status on another hardware platform.
What do we gain?
Nothing. But that's not the terms it was licensed under, and no matter what someone may claim about the *spirit* of the license, adding clauses that restrict how you can deploy GPL software for use is a fundamental enough change to the practical aspect of the license that it's no wonder that people will choose not to use it.
If the designers of the license are more interested in vendettas against those using the software in a way they didn't see beforehand (come on, explicitly trying to define 'consumer product'?) in order to accomplish pyrrhic victories (people moving to other platforms instead of using your newly licensed code), that's fine, it's their choice. But not everyone will want to follow that choice.
Bill
Quoted 9 lines · Alexandre Oliva
Quoted 2 lines · Bron Gondwana
Tivo gets sick of the endless flamewars on lkml, signs a copy of QNX, pushes it out to the hardware. No more Linux on Tivo.
What do we lose?
Do we actually get any benefit whatsoever from TiVO's choice of Linux as the kernel for its device?
Do they contribute back any code that makes Linux better?
If Tivo doesn't, what about other vendors who may be in a similar situation?
Bernd
Quoted 11 lines · Chris Adams
Quoted 8 lines · Alexandre Oliva
if you distribute copies of such a program, [...] you must give the recipients all the rights that you have
So, TiVo includes a copy of Linux in its DVR.
TiVo retains the right to modify that copy of Linux as it sees fit.
It doesn't give the recipients the same right.
Sure it does; you received a program (the kernel) and you can modify it.
If I take the software I received, build it and install it on the same hardware, it won't run. Something is missing in the source code I received, I guess..
If I make changes to the source code, build it, and install it on that same computer, it won't run. How is that being able to modify *that* copy of the program?
If TiVo makes the same changes, builds tehm, and installs it on my computer, it will run just fine. How are they passing on the right they had to me?
Quoted 1 line
You also received hardware; they don't support modification of that.
They don't have to support them. They don't have to help me if it breaks. But if they can do it and I can't, they're failing to comply with the spirit of the GPL.
Quoted 2 lines
Nowhere in the license does it say they have to, because the license only covers the program.
They can't distribute the program while imposing restrictions on modification not present in the software license itself.
Quoted 2 lines
Or are you claiming that putting software on hardware makes the result a derivative work? I think it falls under the "mere aggregation" clause.
I tend to agree, in this particular case, but IANAL. I don't rule out derivative works in future attempts to find loopholes in the GPL.
Quoted 1 line
What if TiVo had put the kernel in a burned-in ROM
Then they wouldn't have the ability to change it any more, so there wouldn't be such a right to pass on to the users.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 2 lines · Alexandre Oliva
So, TiVo includes a copy of Linux in its DVR.
Stop right there.
You seem to make the mistake to think that software is something physical.
Quoted 1 line
TiVo retains the right to modify that copy of Linux as it sees fit.
No. If you were logical (which you are not), you would admit that
(a) physical property is very different from intellectual property (the FSF seems to admit that when it suits their needs, not otherwise)
(b) They never modified "a copy" of Linux - they simply replaced it with "another copy" of Linux. The only thing that actually got *modified* was their hardware!
The first copy didn't "morph" into a second copy. There was no "physical" software that was molded. They do need to follow the GPLv2, since clearly they _do_ distribute Linux, but you have all the same rights as they do with regard to the *software*.
The fact that they maintained some control of the *hardware* (and some software they wrote too) they designed is _their_ choice.
What Tivo did and do, is to distribute hardware that can *contain* a copy of Linux (or just about anything else, for that matter - again, there's a difference between physical and intellectual property).
And their hardware (and firmware) will run some integrity checks on *whatever* copies of software they have. This is all totally outside Linux itself.
Btw, according to your _insane_ notion of "a copy" of software, you can never distribute GPL'd software on a CD-ROM, since you've taken away the right of people to modify that CD-ROM by burning and fixating it. So according to your (obvously incorrect) reading of the GPLv2, every time Red Hat sends anybody a CD-ROM, they have restricted peoples right to modify the software on that CD-ROM bymaking it write-only.
See? Your reading of the license doesn't _work_. Mine does. What I say is that when you distribute software, you don't distribute "a copy" of software, you distribute the _information_ about the software, so that others can take it and modify it. And notice? My reading of the license must be the correct one, since my reading actually makes sense, unlike yours.
And yes, when Tivo distributes Linux, they give everybody else all the same rights they have - with respect to Linux! No, not with respect to their hardware, but that's a totally different thing, and if you cannot wrap your mind around the difference between "the software that is on a CD" and the "piece of plastic that is the CD", and see that when you replace "CD" with any other medium, the equation doesn't change, I don't know what to say.
Quoted 5 lines
It doesn't give the recipients the same right.
Oops.
Sounds like a violation of the spirit to me.
Only if you extend the license to the *hardware*. Oops. Which it never did before.
In other words, you basically try to change the rules. The GPLv2 clearly states that it's about software, not hardware. All the language you quoted talks about software.
In other words, the only way to argue that I'm wrong is to try to twist the meanings of the words, and say that words only mean one specific thing that _you_ claim are their meaning.
And I'm saying you act like Humpty Dumpty when you do. You can argue that way all you like, but your argument is nonsensical. It's akin to the argument that "God is perfect. Perfect implies existence. Therefore God exists".
That kind of argument only works if you *define* the words to suit your argument. But it's a logical fallacy.
And I'm saying that the GPLv2 can mroe straightforwardly be read the way I read it - to talk about software, and to realize that software is not "a copy", it's a more abstract thing. You get Linux when you buy a Tivo (or preferably - don't buy it, since you don't like it), and that means that they have to give you access to and control over the SOFTWARE. But nowhere in the GPL (in the preamble or anywhere else) does it talk about giving you control over the HARDWARE, and the only way you can twist the GPLv2 to say that is by trying to re-define what the words mean.
And then you call *me* confused? After you yourself admitted that the FSF actually agrees with me, and that what Tivo did was not a license violation?
Trust me, I'm not the confused person here.
I'm perfectly fine with other people wanting to extend the license to cover the hardware, but I am *not* perfectly fine with people then trying to claim I'm confused just because I don't agree with them.
Face it: the GPLv3 is a _new_ license. Making funamentally _different_ and _new_ restrictions that do not exist in the GPLv2, and do not exist in the preamble. Any language attempts to make it appear otherwise are just sophistry.
And btw, just to make it clear: as far as I'm concerned, you can read the preamble and the word "freedom" and "rigths" _your_ way. I'm not objecting to that at all. If you read it so that you think it's wrong to distribute GPL'd software on a CD-ROM, that's really not my problem. You do whatever you want to, and think the license means whatever you want to.
What I'm objecting to is how you claim that anybody that doesn't follow your interpretation is "confused". When clearly even the FSF lawyers agree that my interpretation was _correct_, and I don't think your interpretation even makes sense!
Linus
Quoted 7 lines · Linus Torvalds
Quoted 2 lines · Alexandre Oliva
So, TiVo includes a copy of Linux in its DVR.
Stop right there.
You seem to make the mistake to think that software is something physical.
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
Quoted 5 lines
Quoted 1 line
TiVo retains the right to modify that copy of Linux as it sees fit.
(b) They never modified "a copy" of Linux - they simply replaced it with "another copy" of Linux. The only thing that actually got *modified* was their hardware!
Per this reasoning, nobody never modifies software. When you open a source file in your editor, you make changes to it, then save it, you're not modifying it, you're replacing it with another copy, and the only thing that actually got modified was the hardware.
Maybe look what "modify" means in legal context?
Then refer to the GPL:
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program,
Quoted 3 lines
And their hardware (and firmware) will run some integrity checks on *whatever* copies of software they have. This is all totally outside Linux itself.
Agreed. But as it turns out they use these checks to stop people from modifying the copy of Linux they ship in the device, and this restriction is a GPL violation because they don't provide information you need to build a functioning modified version.
Quoted 3 lines
Btw, according to your _insane_ notion of "a copy" of software, you can never distribute GPL'd software on a CD-ROM, since you've taken away the right of people to modify that CD-ROM by burning and fixating it.
You don't retain that right yourself. When you pass that copy on, you pass it on with all the rights that you have. No problem here. This is no different from the software on ROM.
Quoted 3 lines
And I'm saying that the GPLv2 can mroe straightforwardly be read the way I read it - to talk about software, and to realize that software is not "a copy", it's a more abstract thing.
If you choose to disregard the legal meaning of the legal terms used in the GPLv2, you may have a point.
Quoted 2 lines
that means that they have to give you access to and control over the SOFTWARE.
Yes. That's all I'm saying. You just can't use the hardware to take that control away. That would be a violation of the license.
Quoted 2 lines
Face it: the GPLv3 is a _new_ license. Making funamentally _different_ and _new_ restrictions that do not exist in the GPLv2,
This is true.
Quoted 1 line
and do not exist in the preamble.
This is not true.
The spirit remains the same: let people modify and share the software.
If the binary you got can't be created out of the corresponding sources, something is missing. If it won't run without this missing bit, you're missing functional portions of the source code. This all means the hardware is being used to impose a restriction on modification of the software, which is against the spirit of the GPL, and quite likely against its letter as well.
If you don't want it to be so, you can always add an additional permission that clarifies this bit, such that TiVO and you will be happy.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 13 lines · Alexandre Oliva
Quoted 8 lines · Linus Torvalds
Quoted 2 lines · Alexandre Oliva
So, TiVo includes a copy of Linux in its DVR.
Stop right there.
Quoted 8 lines
Quoted 2 lines
You seem to make the mistake to think that software is something physical.
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
I'm now intrigued, where are these (Brazilian and US) definitions stipulated, and under what authority?
Matt
Quoted 9 lines · Matt Keenan
Quoted 6 lines · Alexandre Oliva
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
I'm now intrigued, where are these (Brazilian and US) definitions stipulated, and under what authority?
In the US, 17 USC 101 (the "Definitions" section of the title dealing with Copyright) makes this definition:
A "computer program" is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.
As its purpose is to outline the scope of copyright law, this definition is made under the authority granted to Congress by Article I, Section 8 of the United States Constitution.
Michael Poole
Quoted 18 lines · Michael Poole
Quoted 11 lines · Matt Keenan
Quoted 6 lines · Alexandre Oliva
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
I'm now intrigued, where are these (Brazilian and US) definitions stipulated, and under what authority?
In the US, 17 USC 101 (the "Definitions" section of the title dealing with Copyright) makes this definition:
Quoted 9 lines
A "computer program" is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.
As its purpose is to outline the scope of copyright law, this definition is made under the authority granted to Congress by Article I, Section 8 of the United States Constitution.
But where is the part that says it "requires some physical support"? It says what it is; "a set of statements or instructions", how it should be used; "to be used directly or indirectly in a computer", and what purpose it serves; "in order to bring about a certain result", but it doesn't seem to indicate that it "requires physical support" aka needing some physical representation. I suspect this argument boils down to the philosophical debate of whether ideas (in this case software) can be truely devoid of the physical.
Matt
Quoted 28 lines · Matt Keenan
Quoted 18 lines · Michael Poole
Quoted 11 lines · Matt Keenan
Quoted 6 lines · Alexandre Oliva
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
I'm now intrigued, where are these (Brazilian and US) definitions stipulated, and under what authority?
In the US, 17 USC 101 (the "Definitions" section of the title dealing with Copyright) makes this definition:
Quoted 9 lines
A "computer program" is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.
As its purpose is to outline the scope of copyright law, this definition is made under the authority granted to Congress by Article I, Section 8 of the United States Constitution.
Quoted 8 lines
But where is the part that says it "requires some physical support"? It says what it is; "a set of statements or instructions", how it should be used; "to be used directly or indirectly in a computer", and what purpose it serves; "in order to bring about a certain result", but it doesn't seem to indicate that it "requires physical support" aka needing some physical representation. I suspect this argument boils down to the philosophical debate of whether ideas (in this case software) can be truely devoid of the physical.
Sets of statements or instructions that cannot "be used directly or indirectly in a computer in order to bring about a certain result" are, for the purposes of copyright law, not software. "A computer" is a physical device. It always has been a physical device, except when "computer" referred to a person who performed computations -- and that meaning fell out of common use 40 years ago. Any suggestion that the requirement to be usable on a physical device is significantly different from "require[s] some physical support" is laughably stupid.
17 USC 102 requires that copyright protection only subsists in works that are "fixed in any tangible medium of expression" -- which obviously includes paper and hard drives, and has been ruled to include volatile program memory (the 9th Circuit's holding to this effect in MAI Systems Corp. v. Peak Computer, Inc. is what inspired the addition of 17 USC 117(c)). If the set of instructions exist only in transmission or in someone's head, they are not protected by copyright law.
Michael Poole
Quoted 8 lines · Matt Keenan
Quoted 3 lines · Alexandre Oliva
Err, no. Software, per legal definitions in Brazil, US and elsewhere, require some physical support. That's the hard disk in the TiVO DVR, in this case. I don't see how this matters, though.
I'm now intrigued, where are these (Brazilian and US) definitions stipulated, and under what authority?
http://www.planalto.gov.br/ccIVIL_03/LEIS/L9609.htm
LEI Nº 9.609 , DE 19 DE FEVEREIRO DE 1998.
Art. 1º Programa de computador é a expressão de um conjunto organizado de instruções em linguagem natural ou codificada, contida em suporte
^^^^^^^^^^^^^^^^^^
físico de qualquer natureza, de emprego necessário em máquinas ^^^^^^^^^^^^^^^^^^^^^^^^^^^
automáticas de tratamento da informação, dispositivos, instrumentos ou equipamentos periféricos, baseados em técnica digital ou análoga, para fazê-los funcionar de modo e para fins determinados.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · Alexandre Oliva
Oh, good, let's take this one.
if you distribute copies of such a program, [...] you must give the recipients all the rights that you have
So, TiVo includes a copy of Linux in its DVR.
TiVo retains the right to modify that copy of Linux as it sees fit.
Quoted 7 lines
It doesn't give the recipients the same right.
Oops.
Sounds like a violation of the spirit to me.
Sounds like plugging this hole would retain the same spirit.
Note that Harald Welte has already managed to force Siemens to unlock a "tivoized" Linux router with the GPLv2 in Germany. German contract law values intention when the contract has no specific clause that deals with the issue, and in German law, an accepted license is a contract.
So the fact that tivoizing Linux is against the spirit of the GPLv2 is a court-proof fact, not just some speculation.
What about if your GPL program ends up in a piece of hardware (e.g. a ROM, or an embedded ROM, or if it's some GPL code from OpenCores, as gate netlist in silicon)? My interpretation is that you need a permission from the author for doing that, unless there's an easy way to replace it with a modified copy (e.g. if you put the OpenCores stuff into an FPGA, replacing the configuration PROM would do it).
Some people have difficulties with intentions of contracts rather than direct rules. That may be due to different rules in different countries. In continental Europe, contract law usually bases on Code Napoleon, and there, "good faith" is an important principle (and "good faith" means that the intention is more important than the actual coded practices). In the roman law that was used before and has survived in countries who didn't let Napoleon in (like the UK and the USA), it's slightly different. But a contract or a license still is not a program where anything that isn't said explicitely isn't said at all.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 10 lines
What about if your GPL program ends up in a piece of hardware (e.g. a ROM,
or an embedded ROM, or if it's some GPL code from OpenCores, as gate netlist in silicon)? My interpretation is that you need a permission from the author for doing that, unless there's an easy way to replace it with a
modified copy (e.g. if you put the OpenCores stuff into an FPGA, replacing
the configuration PROM would do it).
The GPL does not require it to be easy in fact to modify the piece of software. It just requires that you have the right to modify it, that is, that there be no legal obstacles in your way. You are entitled to the source code in modifiable, understandable form. There are no legal restrictions, other than those in the GPL and in the law, on what you can do with it.
What you are actually *able* to do, however, depends upon a wide variety of factors way outside the scope of the GPL.
By the way, I have a lot of sympathy for the argument that *if* you provide me a binary made from GPL'd code that required a key to produce that binary, I am entitled to that key. The key is precisely analogous to any other piece of source code -- it is mathematically 'combined' and 'processed' by tools to produce the final, distributed executable. If there's some rational basis for a legal difference between a signing key and a header file, I don't know what it is.
DS
Quoted 2 lines · David Schwartz
The GPL does not require it to be easy in fact to modify the piece of software.
Yes it does, section 3: "The source code for a work means the preferred form of the work for making modifications to it." It then even lists that you need to provide all the scripts and stuff you use to make it easy for you.
Come on, *READ* the GPL, before you argue.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 6 lines · David Schwartz
Quoted 3 lines
The GPL does not require it to be easy in fact to modify the piece of software.
Quoted 6 lines
Yes it does, section 3: "The source code for a work means the preferred form
of the work for making modifications to it." It then even lists that you need to provide all the scripts and stuff you use to make it easy for you.Come on, *READ* the GPL, before you argue.
Nice job quoting me out of context. For the record, here is the context, and it addresses your criticism already:
"The GPL does not require it to be easy in fact to modify the piece of software. It just requires that you have the right to modify it, that is, that there be no legal obstacles in your way. You are entitled to the source code in modifiable, understandable form. There are no legal restrictions, other than those in the GPL and in the law, on what you can do with it."
DS
Quoted 20 lines · Alexandre Oliva
So let's go back to the preamble, that provides motivations and some guidance as to the interpretation of the legal text (i.e., the spirit of the license):
[...] the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. [...]
[...] Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
Quoted 6 lines
[...] if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have
Can anyone show me how any of the provisions of GPLv3 fails to meet this spirit?
Well much as I don't like what Tivo did with only allowing signed kernels to run, I don't see anything in the above that says they can't do that. They let you have the code and make changes to it, they just don't let you put that changed stuff on the device they build. The software is free, even though the hardware is locked down. The GPL v3 really seems to change the spirit to try and cover usage and hardware behaviour, while the spirit of the GPL v2 seemed to me at least to simply be to allow people to copy and change and use the code, and pass that on to people. It didn't have anything to do with what they did with it on hardware. Nothing prevents you from taking tivos kernel changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled. It covers freedom of the source code and resulting binaries, not of the platform you run it on. The GPL v3 has a much broader coverage of what it wants to control, which to me means the spirit is different.
I don't have a tivo, I use mythtv on my own PC. Tivo doesn't force you to buy their hardware after all.
--
Len Sorensen
Quoted 1 line · On Jun 14, 2007, [email protected] (Lennart Sorensen) wrote:
They let you have the code and make changes to it,
Not to the software installed in the device.
What they do is like an author A who distributes a program to user B under a non-Free Software license, and to user C under a Free Software license.
C passes the program on to B under the same license. Now B has two copies of the program. One is free, the other is not.
Except that TiVO had no right to distribute the program under non-Free terms in the first place, because it was not the author, and the license it had explicitly said it couldn't impose further restrictions.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 4 lines · On Thursday 14 June 2007 21:32:08 Alexandre Oliva wrote:
Quoted 1 line · On Jun 14, 2007, [email protected] (Lennart Sorensen) wrote:
They let you have the code and make changes to it,
Not to the software installed in the device.
So now you want access to all the software that is installed in their device? Could you explain that please? You do have access to the GPL code that they used. If you buy one of Google's Search Appliance, are you expecting to allow you to make changes to the software that is installed on that device?
Quoted 5 lines
What they do is like an author A who distributes a program to user B under a non-Free Software license, and to user C under a Free Software license.
Quoted 7 lines
C passes the program on to B under the same license. Now B has two copies of the program. One is free, the other is not.
Except that TiVO had no right to distribute the program under non-Free terms in the first place, because it was not the author, and the license it had explicitly said it couldn't impose further restrictions.
Reread what you wrote here and see the complete lack of logic in your argument.
Author A are Linux developers who distribute their software under GPL 2, TiVO gets the software under the same license and distributes it to their end users. They then make the all the changes to the Linux Kernel available to their end users under the same terms that they got from the Linux kernel developers.
What freedom did they take away?
Quoted 8 lines · Bongani Hlope
Quoted 4 lines · On Thursday 14 June 2007 21:32:08 Alexandre Oliva wrote:
Quoted 1 line · On Jun 14, 2007, [email protected] (Lennart Sorensen) wrote:
They let you have the code and make changes to it,
Not to the software installed in the device.
So now you want access to all the software that is installed in their device?
What's under the GPL.
Quoted 3 lines
If you buy one of Google's Search Appliance, are you expecting to allow you to make changes to the software that is installed on that device?
Arguably, if I purchased the device, I ought to be entitled to make changes to it, yes. But that's a distraction I'd rather not get into ATM.
Quoted 5 lines
They then make the all the changes to the Linux Kernel available to their end users under the same terms that they got from the Linux kernel developers.
What freedom did they take away?
They prevent the user from installing and running modified versions of the program on the box, while they can still do it themselves on the same box.
I guess I must have repeated this at least a dozen times in this thread, so I'll just refrain from repeating this point from now on.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Lennart Sorensen
Nothing prevents you from taking tivos kernel
changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled.
Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
This argument seems totally disingenuous to me. The GPLv<3 was written in a time when the majority of sotware to which the license was applied was written for general purpose computers. The "user" was the owner of the computer, and Freedom 0 was about letting that user RUN modified copies of the software.
Things have changed a lot; we're surrounded by embedded computers, and Freedom 0 seems to strongly imply I should have the right to run modified versions of the Free Software I own on the hardware I OWN. Or is the future of Open Source that you'll be able to hack on free software as long as you work for Intel, Red Hat, TiVO, Google or OSDL? Or own many-thousand-$$ fab printer?
Look, I totally respect Linus' and others' position that the license is an inappropriate way to enforce what they feel are hardware design decisions, but can we dispense w/ the silly argument that the intent of the GPL is fullfilled as long as the user is allowed to modify the software where modify means "imagine a world where they'd be able to run" it?
Dave
Quoted 7 lines
Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
Quoted 5 lines
This argument seems totally disingenuous to me. The GPLv<3 was written in a time when the majority of sotware to which the license was applied was written for general purpose computers. The "user" was the owner of the computer, and Freedom 0 was about letting that user RUN modified copies of the software.
And what about people who can't modify the Linux kernel? They don't know C. They don't know how to use a shell. They're not familiar with UNIX operating systems at all. Maybe they aren't smart enough to modify kernel code.
The GPL is about having the legal right to modify the software and being able to put other people's distributed improvements back into the original code base. It does not guarantee that you will actually be able to modify the software and get it to work on some particular hardware.
I certainly understood the GPL as ensuring the right to get the source code so that you could do something else with it. I never understood the GPL to be about getting hardware to do something else just because it ran GPL'd software.
DS
Quoted 4 lines · David Schwartz
And what about people who can't modify the Linux kernel? They don't know C. They don't know how to use a shell. They're not familiar with UNIX operating systems at all. Maybe they aren't smart enough to modify kernel code.
I learned C in part by modifying the Linux kernel and running the modified kernel on hardware I own, and enabling precisely that kind of tinkering is what the "spirit" of the GPL is about, as is quite plain (to me) from the preamble.
Quoted 4 lines
The GPL is about having the legal right to modify the software and being able to put other people's distributed improvements back into the original code base.
I agree that is what the letter of the GPLv<3 is about.
Quoted 2 lines
It does not guarantee that you will actually be able to modify the software and get it to work on some particular hardware.
Please don't conflate my endorsement of the "spirit" of the GPL with Alexandre's assertion that the GPLv2 forbids TiVOisation. I don't agree with him. My point is that people arguing that the spirit of the GPL doesn't revolve around the freedom of the end user to modify the software *and* run modified copies seem to be missing the point. Linus gets that, as he said in a previous message, he just doesn't personally care about freedom defined that way.
Dave
Quoted 5 lines · Dave Neuer
Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
Yes I am serious. I wouldn't want to buy any such locked down hardware, but that still doesn't mean that I don't think it fits within the spirit of the GPLv2.
Quoted 6 lines
This argument seems totally disingenuous to me. The GPLv<3 was written in a time when the majority of sotware to which the license was applied was written for general purpose computers. The "user" was the owner of the computer, and Freedom 0 was about letting that user RUN modified copies of the software.
Quoted 6 lines
Things have changed a lot; we're surrounded by embedded computers, and Freedom 0 seems to strongly imply I should have the right to run modified versions of the Free Software I own on the hardware I OWN. Or is the future of Open Source that you'll be able to hack on free software as long as you work for Intel, Red Hat, TiVO, Google or OSDL? Or own many-thousand-$$ fab printer?
I think it depends on the type of hardware. Certainly I agree some types of hardware really should not allow you to change the code on them due to the potential risks from doing so. Hence if a license starts to get into the grey area that covers such things, it is getting onto some thin ice that is probably should stay off. You risk excluding things you didn't intend to exclude while almost certainly still missing things you would like to have excluded. I agree that for many devices I could buy, being able to change the code on it would be great, and that there generally is no good reason to deny me from doing it, but I don't think it is worth the risk to put such a requirement into the license, and I certainly never read the GPLv2 to in any way imply such a thing. Apparently from what I can see, Linus never read any such thing in it either when he chose to use it. In fact I think you have to already have a very narrow preset view in order to read the GPLv2 in such as way as to think it intended to prevent such things.
Quoted 6 lines
Look, I totally respect Linus' and others' position that the license is an inappropriate way to enforce what they feel are hardware design decisions, but can we dispense w/ the silly argument that the intent of the GPL is fullfilled as long as the user is allowed to modify the software where modify means "imagine a world where they'd be able to run" it?
It seems many people really do feel that it is fulfilled. They may think it is a stupid hardware design and they may also chose not to buy such hardware, but at the same time they can be perfectly willing to say that as long as the modified sources are provided, that is good enough since further development of the source can be done, never mind what you can do with that particular locked down door stop the code was modified to support. Not everyone views the world through the eyes of RMS.
--
Len Sorensen
Quoted 11 lines · Dave Neuer
Quoted 3 lines · Lennart Sorensen
Nothing prevents you from taking tivos kernel
changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled.Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
So your objection here is that one needs additional resources to do excersise their rights. Well, what about spending time and money to get education to be able to do programming work? Being able to understand C and hardware, etc is also an additional restriction imposed on an average person. Do you advocate that every copy of GPL program should be accompanied with an engineer who would explain how it all works?
Signature · 1 line
Dmitry
Quoted 13 lines · Dmitry Torokhov
Quoted 11 lines · Dave Neuer
Quoted 3 lines · Lennart Sorensen
Nothing prevents you from taking tivos kernel
changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled.Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
Quoted 3 lines
So your objection here is that one needs additional resources to do excersise their rights. Well, what about spending time and money to get education to be able to do programming work?
Come on, again w/ the bullshit. TiVO does not try to prevent me from getting a CS degree, or buying a C reference. They _do_ prevent me from running modified code on my TiVO box.
Quoted 3 lines
Being able to
understand C and hardware, etc is also an additional restriction imposed on an average person.
Not imposed by TiVO.
Quoted 3 lines
Do you advocate that every copy of GPL
program should be accompanied with an engineer who would explain how it all works?
No, just that hardware vendors not lock me out of _my_ hardware if they've benefitted from code which was intended to be modifiable by end users.
Dave
Quoted 13 lines · Dmitry Torokhov
Quoted 11 lines · Dave Neuer
Quoted 3 lines · Lennart Sorensen
Nothing prevents you from taking tivos kernel
changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled.Oh, come on: you're not serious, right? Something indeed prevents me -- the fact that I'm not a hardware manufacturer, I don't have fabs, outsource vendors to provide me w/ designs, ASICs, etc. Nor to I have the money to pay one-off prices for various components if they're even available in batches that small.
Quoted 7 lines
So your objection here is that one needs additional resources to do excersise their rights. Well, what about spending time and money to get education to be able to do programming work? Being able to understand C and hardware, etc is also an additional restriction imposed on an average person. Do you advocate that every copy of GPL program should be accompanied with an engineer who would explain how it all works?
Yes please. Can she be spunky as well? ta.
Quoted 2 lines · Lennart Sorensen
Well much as I don't like what Tivo did with only allowing signed kernels to run, I don't see anything in the above that says they can't
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
Quoted 14 lines
do that. They let you have the code and make changes to it, they just don't let you put that changed stuff on the device they build. The software is free, even though the hardware is locked down. The GPL v3 really seems to change the spirit to try and cover usage and hardware behaviour, while the spirit of the GPL v2 seemed to me at least to simply be to allow people to copy and change and use the code, and pass that on to people. It didn't have anything to do with what they did with it on hardware. Nothing prevents you from taking tivos kernel changes and building your own hardware to run that code on, and as such the spirit of the GPL v2 seems fulfilled. It covers freedom of the source code and resulting binaries, not of the platform you run it on. The GPL v3 has a much broader coverage of what it wants to control, which to me means the spirit is different.
Quoted 2 lines
I don't have a tivo, I use mythtv on my own PC. Tivo doesn't force you to buy their hardware after all.
Well, it is not Tivo alone, a large chunk of the vendors do that. The vendors who actually do it the clean way are just few and can be counted very easily.
Quoted 3 lines
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
GPLv2 deals with that case, and they can (and should) be sued for it [except that US copyright law is designed for large music companies not people]
Quoted 7 lines · Alan Cox
Quoted 3 lines
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
GPLv2 deals with that case, and they can (and should) be sued for it [except that US copyright law is designed for large music companies not people]
Their argument was that the mentioned sources contain propreitary closed stuff from IBM/AMCC for the PPC 405/440 and or for the NXP (MIPS based) chips. Even if the GPLv2 deals with it, well haven't reached anywhere with it, inspite of talks with them. So most of the users just probably stopped talking sense with them, just like me.
Have some of those Amino STB's, the software on it being buggy, including myself many others wanted to fix those bugs, but then people had to pay for their annual support to get the fixes. People who were able to fix also were denied the same since there is no source available. But if you wanted the sources, then you pay for the sources. If you don't pay for their sources, then pay for their Bronze/Silver/Gold Support schemes, where people pay through their nose.
For a specific case with which i wanted to attach a USB based device to the box, they stated: we can port in a driver that which exists in the vanilla kernel, to their device but just that they need to be paid for that to be done, eventhough if someone else was willing to do that job, but that wasn't possible because of no sources.
In either way, if you buy their devices, it is just that, you keep paying us, if you want your device your work as expected.
Quoted 5 lines · Manu Abraham
Quoted 4 lines · Alan Cox
Quoted 3 lines
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
Quoted 7 lines
Quoted 3 lines
GPLv2 deals with that case, and they can (and should) be sued for it [except that US copyright law is designed for large music companies not people]
Their argument was that the mentioned sources contain propreitary closed stuff from IBM/AMCC for the PPC 405/440 and or for the NXP (MIPS based) chips.
As you probably know, this is not a valid excuse to distribute the software under conditions that disrespect its license.
It doesn't mean you can force them to give you the source code, it only means the copyright holder can stop them from distributing the software this way.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Manu Abraham
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
Hmm, set top boxes are often rented from the cable company rather than sold. Stupid grey area for sure. At least tivo does give you the sources, without demanding more money. Rather big difference.
Quoted 3 lines
Well, it is not Tivo alone, a large chunk of the vendors do that. The vendors who actually do it the clean way are just few and can be counted very easily.
Well at least where I work we don't try to lock down the hardware, we do contribute our changes and bug fixes to upstream when it makes sense (and where our changes wouldn't make sense for upstream, they are still clearly included with the sources we have.) If a customer wants a copy of the sources, they will get a nice DVD, although strangely none have asked for one yet.
--
Len Sorensen
Quoted 8 lines · Lennart Sorensen
Quoted 3 lines · Manu Abraham
Well, it is not Tivo alone -- look at http://aminocom.com/ for an example. If you want the kernel sources pay USD 50k and we will provide the kernel sources, was their attitude.
Hmm, set top boxes are often rented from the cable company rather than sold. Stupid grey area for sure. At least tivo does give you the sources, without demanding more money. Rather big difference.
I am not talking about the rented aspect, since these STB's are usually sold rather than rented.
Quoted 10 lines
Quoted 3 lines
Well, it is not Tivo alone, a large chunk of the vendors do that. The vendors who actually do it the clean way are just few and can be counted very easily.
Well at least where I work we don't try to lock down the hardware, we do contribute our changes and bug fixes to upstream when it makes sense (and where our changes wouldn't make sense for upstream, they are still clearly included with the sources we have.) If a customer wants a copy of the sources, they will get a nice DVD, although strangely none have asked for one yet.
Providing the changes back itself is a great thing altogether.
Quoted 1 line · Manu Abraham
Providing the changes back itself is a great thing altogether.
It also makes sense. If the changes are accepted back, the community at large will keep the changes maintained. Less work for me to do when going to newer code versions later. And even better, it may help someone else out too.
A company is likely to like the reduced maintenance burden part, but I think the other part is even better. After all we saved time not having to write everything our selves, so helping others save time seems only fair. The GPL may only require giving the sources to the people who buys the product, but there isn't really any benefit to us in doing only that.
--
Len Sorensen
Quoted 5 lines · Alexandre Oliva
Look, there was room for misunderstandings in earlier drafts of the license. Based on the public comments, the wording was improved. I'd like to think the issues that arose from misunderstandings of the earlier drafts are no longer an issue. Is it not so?
No. The anti-DRM language is still there, and no, it was never a misunderstanding. Now it's been limited to "consumer devices" (after I pointed out some of the _obvious_ problems with the original language), and the only people who called anything a "misunderstanding" were the ones that tried to point to *other* points in the license altogether (ie there was also a "drm section", which didn't really seem to say anything much at all).
Rms calls it "tivoization", but that's a word he has made up, and a term I find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact that they do their hardware and have some DRM issues with the content producers and thus want to protect the integrity of that hardware.
The kernel license covers the *kernel*. It does not cover boot loaders and hardware, and as far as I'm concerned, people who make their own hardware can design them any which way they want. Whether that means "booting only a specific kernel" or "sharks with lasers", I don't care.
Quoted 4 lines
Keeping on making false claims about the license drafts can be one of two things: misunderstandings, out of ambiguity in the text or preconceptions, or ill intentions. I'd rather believe it's the former.
No, it was not the former. And I think the whole "the kernel developers misunderstand the license" crap that the FSF was saying (several times) was very trying to confuse the issue: the FSF knew damn well which part of the license was obnoxious, they just tried to confuse the issue by pointing to *another* part of the license.
And you're just parrotting their idiotic line.
Quoted 3 lines
Now, of course you can look at the licenses and decide that you never agreed with the spirit of the GPL in the first place, and that GPLv2 models better your intentions than GPLv3.
And this is again the same *disease*. You claim that I "misunderstood" the "spirit of the GPL".
Dammit, the GPL is a license. I understand it quite well. Probably better than most. The fact that the FSF then noticed that there were *other* things that they wanted to do, and that were *not* covered by the GPLv2, does *not* mean that they can claim that others "misunderstood" the license.
I understood it perfectly fine, and it fit my needs. So tell me: who is the more confused one: the one who chose the license fifteen years ago, and realized what it means legally, and still stands behind it? I don't think so.
Quoted 7 lines
Your assessment about sharing of code between Linux and OpenSolaris very much makes it seem like that the spirit of sharing, of letting others run, study, modify and share the code as long as they respect others' freedoms, has never been what moved you. Rather, you seem to perceive the GPL as demanding some form of payback, of contribution, rather than the respect for others' freedoms that it requires. In fact, you said something along these lines yourself many months ago.
I have said *exactly* that many many times.
The beauty of the GPLv2 is exactly that it's a "tit-for-tat" license, and you can use it without having to drink the kool-aid.
I've said that over and over again. It's the "spirit of the GPLv2". It's what has made it such a great license, that lots of people (and companies) can use, is very fundamentally that it's fair.
The fact that the FSF sees *another* spirit to it is absolutely not a reason to say that I'm "confused". Quite frankly, apparently I'm _less_ confused than they are, since I saw the GPLv2 for what it was, and they did not - and as a result they felt they needed to extend upon it, because the license didn't actually match what they thought it would do.
Quoted 2 lines
In fact, the spirit has always been described in its preamble, and it didn't change at all: it's all about respecting others' freedoms.
That's a lot of bullshit. You are apparently the grand poobah, and can decide _which_ freedoms and for _what_ others' that matter.
I respect peoples freedoms too. I just disagree with the FSF on what that slippery word means.
The fact that you are unable to even apparently fathom this fundamental issue, and that the FSF thinks that they own the definition of "freedom" is _your_ problem.
You're acting like some Alice-in-Wonderland character, saying that your definition of words is the only one that matter. And that others are "confused". Read up on your humpty-dumpty some day.
I'm damn fed up with the FSF being the "protector of freedoms", and also feeling that they can define what those freedoms mean.
The GPLv2 is a *legal*license*. And no, the FSF doesn't get to define what the words mean to suit their agenda.
Linus
Quoted 2 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 2 lines
The GPLv2 is a *legal*license*. And no, the FSF doesn't get to define what the words mean to suit their agenda.
Agreed - everyone contributed to the kernel based upon the GPLv2. Lots of different reasons, lots of different viewpoints about GPL2 v GPL3, DRM , Treacherous Computing, etc. The commonality is not political, not a grand plan, not a grand unified social agenda but a bunch of people for whom the GPLv2 was an acceptable license for furthering their intentions whether that is education for all, a shared commons or just making a quick buck
Alan
Quoted 6 lines · Alan Cox
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Well, even the FSF lawyers did, but one of the reasons I never wanted to do the copyright assignments(*) is exactly because I think people need to make their own judgments on what the GPLv2 means. In the end, the only thing that really matters is what a judge says (after appeals etc), and the fact is, any license will always have gray areas where people disagree about interpretation.
And I actually am of the very firm opinion that a world with gray areas (and purple, and pink, and green) is a hell of a lot better than one where everything is black-and-white. Only lawyers want a black-and-white world.
So I would actually *encourage* other people to sue over their GPLv2 interpretations, as they have done in Germany (and as IBM has done in the US). I'd sue based on _my_ reading of it, but hey, while my opinion is obviously always correct, I recognize that I live in a world where not everybody else always sees that.
[ (*) Obviously, the *biggest* reason not to do copyright assignments is
that they are just a total pain in the ass to do, and cause tons of totally pointless paperwork. So "Linus is lazy and not interested in being a lawyer" is obviously the primary reason for the lack of assignments. I'm just much happier with people owning their own code outright. ]
Of course, I also realize that suing people over license violations is a big pain in the ass, and in that sense while I "encourage" people to assert their own copyrights, I would obviously also say that it's almost certainly not worth doing if it's in a "gray" area. But that, in the end, has to be the copyright owners own decision!
Quoted 10 lines
Quoted 2 lines
The GPLv2 is a *legal*license*. And no, the FSF doesn't get to define what the words mean to suit their agenda.
Agreed - everyone contributed to the kernel based upon the GPLv2. Lots of different reasons, lots of different viewpoints about GPL2 v GPL3, DRM , Treacherous Computing, etc. The commonality is not political, not a grand plan, not a grand unified social agenda but a bunch of people for whom the GPLv2 was an acceptable license for furthering their intentions whether that is education for all, a shared commons or just making a quick buck
Indeed. And it's _fine_ to even be in it "just to make a quick buck". We do want all kinds of input. I think the community is much healthier having lots of different reasons for people wanting to be involved, rather than concentrating on just some specific reason.
For some it's the technology. For some it's the license. For some it's just a thing to pass boredom. Others like to learn. Whatever. It's all good!
Linus
Quoted 9 lines · Linus Torvalds
Quoted 5 lines · Alan Cox
Quoted 2 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
Quoted 8 lines · Linus Torvalds
Quoted 6 lines · Alan Cox
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license. TiVO never stopped people from copying, modifying or distributing the code - what they did was say "The code is GPL'd, the hardware is restricted" -
ie: "You can do what you want with the code, but you can only run compiled version of it that we provide on our hardware". Why is that legal? Because TiVO produces the hardware and sells it to you with a certain *LICENSE* - because it does contain hardware covered under any number of patents. That license grants you the right to use the patents - in this case algorithms - provided you comply with the terms of the license. (Just like the GPL gives you the right to copy, modify and distribute GPL'd code as long as you comply with its terms)
If you believe otherwise then you are sadly mistaken. Now stop parroting the FSF's worn and tired tripe.
DRH
PS: Looking at your .sig I guess maybe you can't do that without getting kicked out of the FSF-LA
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 17 lines · Daniel Hazelton
Quoted 9 lines · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
Quoted 8 lines · Linus Torvalds
Quoted 6 lines · Alan Cox
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license.
...
The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
AFAIK there haven't been any court rulings on this issue, and it could even be that courts in different countries will decide differently.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 35 lines · On Wednesday 13 June 2007 20:44:19 Adrian Bunk wrote:
Quoted 17 lines · Daniel Hazelton
Quoted 9 lines · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
Quoted 8 lines · Linus Torvalds
Quoted 6 lines · Alan Cox
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license. ...
The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
Quoted 6 lines
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
If the hardware was designed for the end-user to change the software running on it - including running software that it was never meant to run (ie: a complete webserver on cell phone) - then yes, the signing keys are a part of the source, as the software running on the device is designed to be updated by the user using the provided system.
If, on the other hand, the only "software updates" the user is expected to perform are the installation of newer versions of the existing code for "Security" or "Bug Fix" reasons then the signing keys aren't part of the source.
I haven't looked into what Harald Welte did, but I'd be surprised if someone tried following suit in America and had as much success.
Quoted 3 lines
AFAIK there haven't been any court rulings on this issue, and it could even be that courts in different countries will decide differently.
Agreed.
DRH
Quoted 3 lines
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 49 lines · Daniel Hazelton
Quoted 35 lines · On Wednesday 13 June 2007 20:44:19 Adrian Bunk wrote:
Quoted 17 lines · Daniel Hazelton
Quoted 9 lines · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
Quoted 8 lines · Linus Torvalds
Quoted 6 lines · Alan Cox
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license. ...
The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
Quoted 6 lines
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
If the hardware was designed for the end-user to change the software running on it - including running software that it was never meant to run (ie: a complete webserver on cell phone) - then yes, the signing keys are a part of the source, as the software running on the device is designed to be updated by the user using the provided system.
Quoted 4 lines
If, on the other hand, the only "software updates" the user is expected to perform are the installation of newer versions of the existing code for "Security" or "Bug Fix" reasons then the signing keys aren't part of the source.
Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs?
The GPL doesn't give someone distributing the software the choice of how much to limit the freedom of the user.
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
Quoted 3 lines
I haven't looked into what Harald Welte did, but I'd be surprised if someone tried following suit in America and had as much success.
...
Harald is in Germany, and he therefore takes legal action against people distributing products violating his copyright on the Linux kernel in Germany at German courts based on German laws.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines · On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
Quoted 4 lines · Daniel Hazelton
Quoted 3 lines · On Wednesday 13 June 2007 20:44:19 Adrian Bunk wrote:
Quoted 2 lines · Daniel Hazelton
Quoted 1 line · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
On Jun 13, 2007, Linus Torvalds <[email protected]>
Quoted 45 lines · wrote:
Quoted 45 lines
Quoted 32 lines
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines · Alan Cox
Quoted 6 lines
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license. ...
The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
Quoted 6 lines
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
If the hardware was designed for the end-user to change the software running on it - including running software that it was never meant to run (ie: a complete webserver on cell phone) - then yes, the signing keys are a part of the source, as the software running on the device is designed to be updated by the user using the provided system.
Quoted 7 lines
Quoted 4 lines
If, on the other hand, the only "software updates" the user is expected to perform are the installation of newer versions of the existing code for "Security" or "Bug Fix" reasons then the signing keys aren't part of the source.
Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs?
Nope. Merely stating a distinction. Either a device is distributed, like the common PC, that is designed for the user to change and update the software on, or, like the PS2 it isn't designed for that. If I find a way to update my PS2 to run Linux and find that it doesn't want to start the "Linux Firmware" because I'm lacking a signing key...
In the case of a device that internally runs Linux (or any other GPL'd software) and wasn't designed for the end-user to change the software running on it then the signing keys aren't part of the source. OTOH, if I sell a PC running Linux that requires the kernel be signed then the signing keys *are* part of the source, since a PC is designed for the end-user to change the software running on it.
BTW, nice use of irony with that line. Makes me regret letting my fingers get ahead of my brain.
Quoted 2 lines
The GPL doesn't give someone distributing the software the choice of how much to limit the freedom of the user.
Never claimed it did. I just wasn't as specific as I should have been when giving my examples.
Quoted 3 lines
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
No. It all depends on the use-case. If the hardware is designed for the user to install their own, custom versions of the code on then the signing keys are part of the source as defined by the GPLv2.
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware. If the manufacturer provided the signing keys they'd be facilitating the commission of a crime. (call it "Breach of Contract")
Quoted 7 lines
Quoted 3 lines
I haven't looked into what Harald Welte did, but I'd be surprised if someone tried following suit in America and had as much success.
...Harald is in Germany, and he therefore takes legal action against people distributing products violating his copyright on the Linux kernel in Germany at German courts based on German laws.
I know this. As I said, I doubt that anyone who tried this in America would have the success he has had.
DRH
Quoted 2 lines
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 90 lines · Daniel Hazelton
Quoted 5 lines · On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
Quoted 4 lines · Daniel Hazelton
Quoted 3 lines · On Wednesday 13 June 2007 20:44:19 Adrian Bunk wrote:
Quoted 2 lines · Daniel Hazelton
Quoted 1 line · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
On Jun 13, 2007, Linus Torvalds <[email protected]>
Quoted 45 lines · wrote:
Quoted 45 lines
Quoted 32 lines
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines · Alan Cox
Quoted 6 lines
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL - regardless of version - is a *SOFTWARE* license. ...
The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
Quoted 6 lines
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
If the hardware was designed for the end-user to change the software running on it - including running software that it was never meant to run (ie: a complete webserver on cell phone) - then yes, the signing keys are a part of the source, as the software running on the device is designed to be updated by the user using the provided system.
Quoted 7 lines
Quoted 4 lines
If, on the other hand, the only "software updates" the user is expected to perform are the installation of newer versions of the existing code for "Security" or "Bug Fix" reasons then the signing keys aren't part of the source.
Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs?
Nope. Merely stating a distinction. Either a device is distributed, like the common PC, that is designed for the user to change and update the software on, or, like the PS2 it isn't designed for that. If I find a way to update my PS2 to run Linux and find that it doesn't want to start the "Linux Firmware" because I'm lacking a signing key...
In the case of a device that internally runs Linux (or any other GPL'd software) and wasn't designed for the end-user to change the software running on it then the signing keys aren't part of the source. OTOH, if I sell a PC running Linux that requires the kernel be signed then the signing keys *are* part of the source, since a PC is designed for the end-user to change the software running on it.
BTW, nice use of irony with that line. Makes me regret letting my fingers get ahead of my brain.
Quoted 2 lines
The GPL doesn't give someone distributing the software the choice of how much to limit the freedom of the user.
Never claimed it did. I just wasn't as specific as I should have been when giving my examples.
Quoted 3 lines
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
No. It all depends on the use-case. If the hardware is designed for the user to install their own, custom versions of the code on then the signing keys are part of the source as defined by the GPLv2.
Quoted 8 lines
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware. If the manufacturer provided the signing keys they'd be facilitating the commission of a crime. (call it "Breach of Contract")
...
Repetition doesn't let wrong things become true.
Where does the GPLv2 talk about the distinction you are trying to make based on distributor intentions?
We are talking about the GPLv2 licence text, not about what you would personally prefer.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 101 lines · On Wednesday 13 June 2007 22:08:27 Adrian Bunk wrote:
Quoted 91 lines · Daniel Hazelton
Quoted 5 lines · On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
Quoted 4 lines · Daniel Hazelton
Quoted 3 lines · On Wednesday 13 June 2007 20:44:19 Adrian Bunk wrote:
Quoted 2 lines · Daniel Hazelton
Quoted 1 line · On Wednesday 13 June 2007 19:15:42 Alexandre Oliva wrote:
On Jun 13, 2007, Linus Torvalds <[email protected]>
Quoted 45 lines · wrote:
Quoted 45 lines
Quoted 32 lines
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines · Alan Cox
Quoted 6 lines
Quoted 3 lines
find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact
Not all of us agree with this for the benefit of future legal interpretation.
Quoted 6 lines
Quoted 1 line
Well, even the FSF lawyers did,
Or rather they didn't think an attempt to enforce that in the US would prevail (or so I'm told). That's not saying what TiVo did was right, and that's not saying that what TiVo did was permitted by the license. Only courts of law can do that.
Quoted 6 lines
Wrong! Anyone with half a brain can make the distinction. What TiVO did is entirely legal - they fully complied with the GPLv2. Note that what they *DON'T* allow people to do is run whatever version of whatever software they want on their hardware. They have that right - its the "Free Software Foundation" and the GPL
- regardless of version - is a *SOFTWARE* license. ...The GPLv2 says:
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys. Different people have different opinions regarding this issue.
Quoted 6 lines
If "the complete source code" includes private keys, the GPLv2 requires them to give any costumer the private keys.
Fact is that Harald Welte did in several cases successfully convince vendors that private keys are part of the source code if they are required for running the compiled binary on some hardware.
If the hardware was designed for the end-user to change the software running on it - including running software that it was never meant to run (ie: a complete webserver on cell phone) - then yes, the signing keys are a part of the source, as the software running on the device is designed to be updated by the user using the provided system.
Quoted 7 lines
Quoted 4 lines
If, on the other hand, the only "software updates" the user is expected to perform are the installation of newer versions of the existing code for "Security" or "Bug Fix" reasons then the signing keys aren't part of the source.
Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs?
Nope. Merely stating a distinction. Either a device is distributed, like the common PC, that is designed for the user to change and update the software on, or, like the PS2 it isn't designed for that. If I find a way to update my PS2 to run Linux and find that it doesn't want to start the "Linux Firmware" because I'm lacking a signing key...
In the case of a device that internally runs Linux (or any other GPL'd software) and wasn't designed for the end-user to change the software running on it then the signing keys aren't part of the source. OTOH, if I sell a PC running Linux that requires the kernel be signed then the signing keys *are* part of the source, since a PC is designed for the end-user to change the software running on it.
BTW, nice use of irony with that line. Makes me regret letting my fingers get ahead of my brain.
Quoted 2 lines
The GPL doesn't give someone distributing the software the choice of how much to limit the freedom of the user.
Never claimed it did. I just wasn't as specific as I should have been when giving my examples.
Quoted 3 lines
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
No. It all depends on the use-case. If the hardware is designed for the user to install their own, custom versions of the code on then the signing keys are part of the source as defined by the GPLv2.
Quoted 8 lines
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware. If the manufacturer provided the signing keys they'd be facilitating the commission of a crime. (call it "Breach of Contract")
...
Quoted 7 lines
Repetition doesn't let wrong things become true.
Where does the GPLv2 talk about the distinction you are trying to make based on distributor intentions?
We are talking about the GPLv2 licence text, not about what you would personally prefer.
The GPLv2 doesn't have to cover this distinction to make it a reality. This distinction is *EXACTLY* the type of distinction a lawyer will make when arguing the point.
Yes, it's artificial. Yes, it does appear to violate the GPLv2 - *IF* you read the text of such in a specific manner.
However, the GPL, until version 3, *NEVER* guaranteed the right to run a given piece of software on *ANY* hardware - not the hardware it *COMES* on.
And please, I repeated myself only because your reply seemed to imply that you didn't understand the statement I had made. Since you have now informed me, in a backhanded way, informed me that my interpretation of your response was wrong, I will not repeat myself again.
Also note that I have re-examined the facts, in light of new information presented in this discussion, and have come to the conclusion that devices like the TiVO, in keeping the signing keys private (because of the "Facilitation of a Crime" thing I noted earlier), is violating the GPL, but not in the manner almost everyone is arguing. The violation is, rather, with the clause about the license being null and void in event of laws impacting the delivery of the source. (Because, as I also stated earlier, the signing keys are part of the source. Since, in some cases, the license on the hardware prevents running modified binaries (a reason for the digital signing) companies will keep said keys private - doing otherwise can (and I can assure you that some lawyer will do this) be construed as "Facilitating the Commission of a crime". In this case, it'd be "Breach of Contract" - IANAL, but IIRC, licenses fall under contract law))
DRH
Quoted 3 lines
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 26 lines · Daniel Hazelton
Quoted 2 lines · On Wednesday 13 June 2007 22:08:27 Adrian Bunk wrote:
Quoted 1 line · Daniel Hazelton
On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
...
Quoted 22 lines
Quoted 8 lines
Quoted 3 lines
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
No. It all depends on the use-case. If the hardware is designed for the user to install their own, custom versions of the code on then the signing keys are part of the source as defined by the GPLv2.
Quoted 8 lines
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware. If the manufacturer provided the signing keys they'd be facilitating the commission of a crime. (call it "Breach of Contract")
...Repetition doesn't let wrong things become true.
Where does the GPLv2 talk about the distinction you are trying to make based on distributor intentions?
Quoted 7 lines
Quoted 2 lines
We are talking about the GPLv2 licence text, not about what you would personally prefer.
The GPLv2 doesn't have to cover this distinction to make it a reality. This distinction is *EXACTLY* the type of distinction a lawyer will make when arguing the point.
...
Reality check:
Harald convinced companies that they have to provide the private keys required to run the Linux kernel they ship on their hardware.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 37 lines · On Wednesday 13 June 2007 22:56:40 Adrian Bunk wrote:
Quoted 28 lines · Daniel Hazelton
Quoted 2 lines · On Wednesday 13 June 2007 22:08:27 Adrian Bunk wrote:
Quoted 1 line · Daniel Hazelton
On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
...
Quoted 22 lines
Quoted 8 lines
Quoted 3 lines
Either private keys required to run the kernel on the hardware are always considered part of "the complete source code" or they are never part of it.
No. It all depends on the use-case. If the hardware is designed for the user to install their own, custom versions of the code on then the signing keys are part of the source as defined by the GPLv2.
Quoted 8 lines
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware. If the manufacturer provided the signing keys they'd be facilitating the commission of a crime. (call it "Breach of Contract")
...Repetition doesn't let wrong things become true.
Where does the GPLv2 talk about the distinction you are trying to make based on distributor intentions?
Quoted 7 lines
Quoted 2 lines
We are talking about the GPLv2 licence text, not about what you would personally prefer.
The GPLv2 doesn't have to cover this distinction to make it a reality. This distinction is *EXACTLY* the type of distinction a lawyer will make when arguing the point.
...
Quoted 4 lines
Reality check:
Harald convinced companies that they have to provide the private keys required to run the Linux kernel they ship on their hardware.
In Germany, not America. I should have qualified my statement to make it clear I mean "In America". Sorry about the confusion.
DRH
Quoted 3 lines
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 2 lines
In Germany, not America. I should have qualified my statement to make it clear I mean "In America". Sorry about the confusion.
You shouldn't say "America" when you mean the "US".
Best wishes,
Michael
Signature · 5 lines
Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar Sitz Hamburg; HRB 89145 Amtsgericht Hamburg Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: [email protected] GPG-keys available on request or at public keyserver
Quoted 4 lines · On Thursday 14 June 2007 01:39:13 Michael Gerdau wrote:
Quoted 2 lines
In Germany, not America. I should have qualified my statement to make it clear I mean "In America". Sorry about the confusion.
You shouldn't say "America" when you mean the "US".
Sorry, I slipped. I'm still trying to rid myself of the uniquely "US" belief that "America" == "USA". Thanks for the reminder.
DRH
Quoted 3 lines
Best wishes,
Michael
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 4 lines · Adrian Bunk
Reality check:
Harald convinced companies that they have to provide the private keys required to run the Linux kernel they ship on their hardware.
No, the *real* reality check:
The operative words here are "convinced companies" - as opposed to "convinced a judge to rule that private keys are required to be disclosed". (I just checked around on gpl-violations.org, and I don't see any news items that say they actually generated citable case law on the topic of keys...)
Harald convinced companies that it was easier/cheaper/faster to provide the private keys than to continue in a long legal battle with an uncertain outcome. If the company estimates the total loss due to keys being released is US$100K, but the costs of taking it to court are estimated at US$200K, it's obviously a win (lesser loss, actually) for the company to just fold.
Incidentally, this same logic is what drives the average successful patent troll lawsuit - the sued company will buy a license for $25K, just because they know that fighting the lawsuit will cost $100K and up.
Quoted 3 lines · On Thu, Jun 14, 2007 at 12:00:17AM -0400, [email protected] wrote:
Incidentally, this same logic is what drives the average successful patent troll lawsuit - the sued company will buy a license for $25K, just because they know that fighting the lawsuit will cost $100K and up.
You're off by a factor of 10-50. The usual estimates I've heard from people who ought to know is the minimum ante for fighting a patent lawsuit is $1 million to $5 million. Lawyer time and expert witness time to give the judge a granduate education in the technologies involved is *expensive* (since the judge may be really smart, but most judges have no engineering background to speak of, so you have to explain the technologies involved in terms that make sense to someone with an honors education with a Bachelor of Arts degree).
Basically, in the US, you get the best justice money can buy. :-)
- Ted
Quoted 1 line · Theodore Tso
Basically, in the US, you get the best justice money can buy. :-)
that has to be one of the best one-liners ever! :)
Quoted 2 lines
- Ted
-jb
Signature · 1 line
Tact is the art of making a point without making an enemy.
Quoted 14 lines · On Thu, Jun 14, 2007 at 12:00:17AM -0400, [email protected] wrote:
Quoted 4 lines · Adrian Bunk
Reality check:
Harald convinced companies that they have to provide the private keys required to run the Linux kernel they ship on their hardware.
No, the *real* reality check:
The operative words here are "convinced companies" - as opposed to "convinced a judge to rule that private keys are required to be disclosed". (I just checked around on gpl-violations.org, and I don't see any news items that say they actually generated citable case law on the topic of keys...)
Quoted 6 lines
Harald convinced companies that it was easier/cheaper/faster to provide the private keys than to continue in a long legal battle with an uncertain outcome. If the company estimates the total loss due to keys being released is US$100K, but the costs of taking it to court are estimated at US$200K, it's obviously a win (lesser loss, actually) for the company to just fold.
...
Here in Germany, the rules at court are roughly "the loser pays everything including the costs of the winner", so if a big company is sure they will win at court there's no reason not to go there.
And if they did the effort of using private keys to only allow running an official firmware, they must have seen an advantage from doing so.
I'm not saying it legally clear the other way round, my statement was an answer to Daniel's emails claiming it was clear what such companies do was legal.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 4 lines · Adrian Bunk
Here in Germany, the rules at court are roughly "the loser pays everything including the costs of the winner", so if a big company is sure they will win at court there's no reason not to go there.
Well, the thing is (and I've said this before), a lawsuit is (and _should_ be) very much a last resort.
I think that the Open Source community (and the FSF too) is much better off *not* concentrating so much on "legal rules" of what can and cannot be done, and instead spend much more effort on showing people why the whole "Open Source" thing actually works.
And in fact, I think that's _exactly_ what Linux has been doing for the last decade!
A lot of companies are actually doing the Right Thing (tm).
Not because of anybody "forcing" them, but because they have literally bought into the whole "Open Source can do things better" mentality.
In fact, the whole "coercive" approach is counter-productive. It makes people dislike you. It makes companies _resist_ open source, rather than see it as a potential ally.
And no, I'm not speaking out of my *ss. Anybody who goes back fifteen years and looks at how the FSF was acting wrt the GPL (v2, back then), and how many friends - and enemies - they were making, should see that as a big clue. Linux really *did* change the landscape - for the better (*). By being much less contrary.
So look at Intel in the open source space. They're doing well. Look at Sun. They aren't _forced_ to open-source, they see others open-sourcing, and they see that it works damn well.
In the "Tivo space", look at Neuros.
In other words, we're just *much* better off with a friendly license and not trying to force people to choose sides, than with the rabid idealism that was - and still is - the FSF. The FSF always makes for this horrible "you're with us, or you're against us" black-and-white mentality, where there are "evil" companies (Tivo) and "good" companies (although I dunno if the FSF really sees anybody as truly "good").
I'd much rather just see "individuals" and "companies". They're not evil or good, they are all in it for their own reasons (and their reasons are *NOT* the same reasons they are for me, you, or anybody else), and we should show them that the whole "Open Source" approach really does work for them.
It's totally pointless to try to "force" people to be good. That's like "curing" gay people. Not going to happen.
Linus
(*) Not just Linux, of course, but I do claim that this is actually an area where Linux was a big influence. Not the only one, but a major player.
Quoted 6 lines · On Thu, 14 Jun 2007 09:01:32 -0700 (PDT) Linus Torvalds…
In other words, we're just *much* better off with a friendly license and not trying to force people to choose sides, than with the rabid idealism that was - and still is - the FSF. The FSF always makes for this horrible "you're with us, or you're against us" black-and-white mentality, where there are "evil" companies (Tivo) and "good" companies (although I dunno if the FSF really sees anybody as truly "good").
Linus,
If you really believe that then why didn't you choose a BSD license for Linux? You didn't say "completely free, no restrictions attached, people will follow because they'll see it's best, we just won't buy products that use Linux in a way with which we disagree".
Instead you chose a license which enforced the so called tit-for-tat policy you think is fair. But people who prefer the BSD license may think you're a moron for forcing your political agenda (ie. tit-for-tat) on users of your code. The point of all that being, you _do_ believe in enforcing restrictions or you wouldn't like the GPL v2.
So you draw the line of "fairness" and belief that people will do-the-right-thing somewhere short of the BSD license. Why is it so hard then to accept that the FSF draws the line short of the GPLv2 after having gained practical experience with it since its release?
You can argue till the cows come home the belief that _your_ restrictions are more fair, moral and reasonable than theirs. But at the end of the day it's all just a matter of opinion about what constitutes fair and reasonable. You think its a fair trade that you get code back, the FSF think its fair that people can hack and run the code anywhere its used.. It all comes down to the author of the code getting to attach whatever restrictions they choose.
Sean
Quoted 3 lines · Sean
If you really believe that then why didn't you choose a BSD license for Linux?
Because I think the GPLv2 is a great license.
And I don't like the FSF's radical world-view, but I am able to separate the license (the GPLv2) from the author and source of the license (rms and the FSF).
Why do people always confuse the two? The GPLv2 stands on its own. The fact that I disagree with the FSF on how to act has _zero_ relevance for my choice of license.
The BSD license, as far as I'm concerned, is _horrible_ for any project I would use. I have actually released code under it, but never a "project". I've given some code of mine that I don't care about that much to the BSD projects, just because I didn't think that code really mattered, and I thought it would be stupid and small-minded not to let the BSD's use it.
But for a project I actually care about, I would never choose the BSD license. The license doesn't encode my fundamental beliefs of "fairness". I think the BSD license encourages a "everybody for himself" mentality, and doesn't encourage people to work together, and to merge.
Let me put this in source management terms, since I've also been working on a source control management project for the last few years: the BSD license encourages "branching", but the fact is, branching is not really all that interesting. What's interesting is "merging": the branching is just a largely irrelevant prerequisite to be able to merge.
The GPLv2 encourages *merging*. Again, the right to "branch" needs to be there in order for merges to be possible, but the right to branch is actually much less important than the right to "merge".
See?
So I'm a *big* believer in the GPLv2. I think the GPLv2 is an almost perfect license. That doesn't mean that I have to agree with the FSF on everything else.
Quoted 4 lines
Instead you chose a license which enforced the so called tit-for-tat policy you think is fair. But people who prefer the BSD license may think you're a moron for forcing your political agenda (ie. tit-for-tat) on users of your code.
Oh, and some people did and do.
And you know what? That's PERFECTLY OK!
I think that the BSD license is wrong for me. Does that mean that people who choose the BSD license are wrong to do so? No. For *them* the choices that the BSD license makes may be the right ones!
Quoted 2 lines
The point of all that being, you _do_ believe in enforcing restrictions or you wouldn't like the GPL v2.
.. but I think that the software license I choose should be about the software, and about giving back in kind.
And the GPLv2 is _perfect_ for that.
And the GPLv3 is horrible.
And you know what? YOU can choose the GPLv3 for your projects. I'm not saying anything else. I'm saying that no, I was _not_ confused when I chose the GPLv2. I thought it was a good license 15 years ago. I thought it was a good license 10 years ago. I thought it was a good license five years ago. And I think it's a good license today.
Because it fundamnetally does what I think is fair.
In a way that the GPLv3 DOES NOT.
Linus
Quoted 6 lines · Linus Torvalds
.. but I think that the software license I choose should be about the software, and about giving back in kind.
And the GPLv2 is _perfect_ for that.
And the GPLv3 is horrible.
Is there anything other than TiVOization to justify these statements?
Also, can you elaborate on what you mean about 'giving back in kind'? (I suspect this is related with the tit-for-tat reasoning, that you've failed to elaborate on before)
The only thing the GPL demands is respect for others' freedoms, as in, "I, the author, respect your freedoms, so you, the licensee, must respect others' freedoms as well". Is this the "in kind" you're talking about? Or are you mistaken about the actual meaning of even GPLv2?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 2 lines · Alexandre Oliva
Is there anything other than TiVOization to justify these statements?
Do you need anything else?
But if by the question you mean "would you think the GPLv3 is fine without the new language in section 6 about the 'consumer devices'", then the answer is that yes, I think that the current GPLv3 draft looks fine apart from that.
Quoted 3 lines
Also, can you elaborate on what you mean about 'giving back in kind'? (I suspect this is related with the tit-for-tat reasoning, that you've failed to elaborate on before)
I've *not* failed to elaborate on that before. Not at all.
Just google for
torvalds tit-for-tat
and you'll see a lot of my previous postings. Trying to claim that this is somehow "new" is ludicrous. In fact, some of the google hits you find are from 2004, *loong* before the current GPLv3 discussion.
So your "failed to elaborate" is not a failure on my side.
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
I don't ask for money. I don't ask for sexual favors. I don't ask for access to the hardware you design and sell. I just ask for the thing I gave you: source code that I can use myself.
I really don't think my "tit-for-tat" or "give back in kind" is that hard to understand, is it?
And no, it's not a new concept. Neither is the fact that I've never agreed with the FSF's agenda about "freedom" (as defined by _them_ - I have a notion of "freedom" myself, and the FSF doesn't get to define it for me).
I don't call Linux "Free Software". I haven't called it that for close to ten years! Because I think the term "Open Source" is a lot better.
Quoted 5 lines
The only thing the GPL demands is respect for others' freedoms, as in, "I, the author, respect your freedoms, so you, the licensee, must respect others' freedoms as well". Is this the "in kind" you're talking about? Or are you mistaken about the actual meaning of even GPLv2?
I respect your freedom to design products around Linux. You can do whatever you damn well please - I just ask that you give the software back in a usable form. That's all I ask for.
And that's all the GPLv2 asks for.
Which is why I selected the GPLv2 in the first place, and why I *still* think the GPLv2 is a wonderful license!
So I claim that the "freedoms" that the GPLv2 embodies are *greater* than the "freedoms" embodied in the GPLv3.
Linus
Quoted 5 lines · Linus Torvalds
Quoted 2 lines · Alexandre Oliva
Is there anything other than TiVOization to justify these statements?
Do you need anything else?
No, I'm quite happy that this is all.
Quoted 4 lines
But if by the question you mean "would you think the GPLv3 is fine without the new language in section 6 about the 'consumer devices'", then the answer is that yes, I think that the current GPLv3 draft looks fine apart from that.
Then would you consider relicensing Linux under GPLv3 + additional permission for Tivoization?
Quoted 4 lines
Quoted 3 lines
Also, can you elaborate on what you mean about 'giving back in kind'? (I suspect this is related with the tit-for-tat reasoning, that you've failed to elaborate on before)
Quoted 8 lines
I've *not* failed to elaborate on that before. Not at all.
Just google for
torvalds tit-for-tat
and you'll see a lot of my previous postings. Trying to claim that this is somehow "new" is ludicrous.
I didn't. But I've provided evidence that your prior musings on this topic were wrong. I wanted to give you an opportunity to review your position under this new light. I see you haven't changed it at all.
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
Where do you think the GPL say that you get the source code back?
Quoted 3 lines
I don't ask for money. I don't ask for sexual favors. I don't ask for access to the hardware you design and sell. I just ask for the thing I gave you: source code that I can use myself.
See, that's not what the license says.
The license says what you ask for is respect for other users' freedoms. Nothing whatsoever for you. Only for users.
Freedom is in "in kind" payment, and it's not even a retribution, a
payback: it's payforward, or paysideways.
Do you understand why I find your reasoning hard to accept?
Quoted 3 lines
And no, it's not a new concept. Neither is the fact that I've never agreed with the FSF's agenda about "freedom" (as defined by _them_ - I have a notion of "freedom" myself, and the FSF doesn't get to define it for me).
We don't have to agree on our individual definitions of freedom. But we're talking about a specific license that assigns a specific meaning to the term "freedoms", and that's all this is about.
Quoted 2 lines
I don't call Linux "Free Software". I haven't called it that for close to ten years! Because I think the term "Open Source" is a lot better.
I can appreciate that you think it's better, but unfortunately it appears to be playing a significant role in confusing your interpretation of the GPL. The GPL is not just about making the source code visible, or even modifyable by others. It's about respecting others' freedoms. No matter how badly you prefer Open Source over Free Software, how badly you'd rather disregard the freedoms in the spirit and in the legal terms of the GPL, you chose a license designed to protect those freedoms, not only the ability to see and modify source code.
Quoted 8 lines
Quoted 5 lines
The only thing the GPL demands is respect for others' freedoms, as in, "I, the author, respect your freedoms, so you, the licensee, must respect others' freedoms as well". Is this the "in kind" you're talking about? Or are you mistaken about the actual meaning of even GPLv2?
I just ask that you give the software back in a usable form. That's all I ask for.
I'm afraid that's not what the GPLv2 says. There's no provision whatsoever about giving anything back. Not in the spirit, not in the legal terms.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
What part of the word "expect" did you not understand? And whats your point here anyway?
Sam
Quoted 11 lines · Sam Ravnborg
Quoted 8 lines · Alexandre Oliva
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
What part of the word "expect" did you not understand?
http://lkml.org/lkml/2006/9/24/246
It asks everybody - regardless of circumstance - for the same thing. It asks for the effort that was put into improving the software to be given back to the common good. You can use the end result any way you want (and if you want to use it for "bad" things, be my guest), but we ask the same exact thing of everybody - give your modifications back.
Quoted 1 line
And whats your point here anyway?
The the GPL doesn't do that. It encourages that. But what it asks for is respect for the freedoms it defends WRT the software licensed under it.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 23 lines · Alexandre Oliva
Quoted 11 lines · Sam Ravnborg
Quoted 8 lines · Alexandre Oliva
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
What part of the word "expect" did you not understand?
http://lkml.org/lkml/2006/9/24/246
It asks everybody - regardless of circumstance - for the same thing. It asks for the effort that was put into improving the software to be given back to the common good. You can use the end result any way you want (and if you want to use it for "bad" things, be my guest), but we ask the same exact thing of everybody - give your modifications back.
Quoted 5 lines
Quoted 1 line
And whats your point here anyway?
The the GPL doesn't do that. It encourages that. But what it asks for is respect for the freedoms it defends WRT the software licensed under it.
Reading the above you are writing exact the same as Linus here but refusing to accept it and without usign the same words.
In the end of the day both things says: "please give back" And the rest is just worthless nitpicking - in my local language is it "flueknepperi".
Sam
Quoted 23 lines · On Thursday 14 June 2007 16:42:44 Alexandre Oliva wrote:
Quoted 6 lines · Sam Ravnborg
Quoted 5 lines · Alexandre Oliva
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
What part of the word "expect" did you not understand?
http://lkml.org/lkml/2006/9/24/246
It asks everybody - regardless of circumstance - for the same thing. It asks for the effort that was put into improving the software to be given back to the common good. You can use the end result any way you want (and if you want to use it for "bad" things, be my guest), but we ask the same exact thing of everybody - give your modifications back.
Quoted 5 lines
Quoted 1 line
And whats your point here anyway?
The the GPL doesn't do that. It encourages that. But what it asks for is respect for the freedoms it defends WRT the software licensed under it.
Logical fallacy. The two statements are semantically equivalent, and the draw and allure of "Open Source" is that the software continually gets better at doing its job, grows more features, etc... *ALL* because the modifications *DO* get "given back".
Because it is *VERY* hard to keep a modification *PRIVATE* and avoid the "distribution" clauses of the GPL the belief that it "doesn't require giving changes back" is technically and literally true, but is false in practice.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 3 lines · Alexandre Oliva
Then would you consider relicensing Linux under GPLv3 + additional permission for Tivoization?
No. I'm not stupid.
The GPLv3 explicitly allows removing additional permissions.
So anybody who does "GPLv3 + additional permissions" is basically setting himself up for people taking those permissions away.
Since the Tivo kind of permission is in my opinion a *fundamental right* (or call if "freedom" if you want), then "GPLv3 + additional permissions" simply is not a viable alternative, since anybody could just decide to make improvements and strip those permissions.
The whole notion of "additional permissions" in the GPLv3 is totally pointless, since it's legally *exactly* the same as allowing dual licensing (which a license doesn't even have to spell out: you can dual-license *regardless* of the license!).
The reason for the "additional permissions" is just to make the LGPL go away, and become a sub-clause of the GPLv3.
If you really thought anything else, you're just uninformed and stupid, and didn't think things through.
Linus
Quoted 8 lines · Linus Torvalds
Quoted 3 lines · Alexandre Oliva
Then would you consider relicensing Linux under GPLv3 + additional permission for Tivoization?
No. I'm not stupid.
The GPLv3 explicitly allows removing additional permissions.
So what? You just refrain from accepting contributions that attempt to remove them, and you'll keep TiVO happy.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 4 lines · Linus Torvalds
No. I'm not stupid.
The GPLv3 explicitly allows removing additional permissions.
So what? You just refrain from accepting contributions that attempt to remove them, and you'll keep TiVO happy.
You really aren't thinking, are you?
It's not about keeping Tivo happy. It's about keeping *me* happy. That's my primary (only) motivation for a license.
And let's go back to why I selected the GPLv2 in the first place, shall we?
I want to be able to use other peoples improvements. If they release improved versions of the software I started, I want to be able to merge those improvements if I want to.
Your *IDIOTIC* suggestion is explicitly against the whole POINT! By saying that I shouldn't accept contributions like that, you just INVALIDATED the whole point of the license in the first place!
Can you really not see that?
Linus
Quoted 3 lines · Linus Torvalds
I want to be able to use other peoples improvements. If they release improved versions of the software I started, I want to be able to merge those improvements if I want to.
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
Quoted 3 lines
Your *IDIOTIC* suggestion is explicitly against the whole POINT! By saying that I shouldn't accept contributions like that, you just INVALIDATED the whole point of the license in the first place!
I understand. I assumed you had some trust that people would abide by your wish to permit TiVOization, and that authors of modifications were entitled to make "whatever restrictions they wanted" on their code.
Pardon me if I think your position is at least somewhat incoherent. Can you help me make sense of it?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 5 lines · Alexandre Oliva
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
You *cannot* make GPLv3-only contributions to the kernel.
I'm sorry, but that's how it is. You can take some of the code that is GPLv2+ in the kernel, and MOVE IT TO ANOTHER PROJECT, and use them there. But not within the confines of the Linux kernel. Within the Linux kernel, the GPLv2 rules - and "GPLv2+" becomes just "GPLv2", since the GPLv3 is not compatible with v2.
This is no different from the fact that we have some drivers that are GPLv2/BSD licensed. Within the kernel, they are GPLv2. But on their own, you can choose to use them under the BSD license, make your changes to them, and release them commercially.
And correct - I cannot (and neither can anybody else) then accept those *non*GPLv2 changes back.
Quoted 4 lines
I understand. I assumed you had some trust that people would abide by your wish to permit TiVOization, and that authors of modifications were entitled to make "whatever restrictions they wanted" on their code.
Actually, normally I *do* have such a trust. It's why I have no problem with drivers that are dual-GPL/BSD, and in fact, I've told people that I don't want them to turn them into GPL-only, because that is simply not polite.
But I hold *myself* to higher standards than I hold others. And in particular, when it comes to people with a religious agenda, I don't expect them to be polite or take my feelings into account. I expect (from good history) that people with a license agenda will consider the license agenda more important than any hurt feelings, or any wishes of mine.
Quoted 2 lines
Pardon me if I think your position is at least somewhat incoherent. Can you help me make sense of it?
I'm giving up. I'm moving you to my "flamers" list, so that your emails go to a separate mailbox that I read weekly. I've wasted too much time with you, your arguments don't make sense, and you seem to refuse to even _try_ to understand my position, or respect the fact that my choice of license is MY choice, and that I actually have a brain of my own.
Linus
Quoted 8 lines · Linus Torvalds
Quoted 5 lines · Alexandre Oliva
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
You *cannot* make GPLv3-only contributions to the kernel.
I can make improvements to GPLv2+ files under GPLv3 (or rather will,
Quoted 3 lines · after GPLv3 is published). And you wrote:
I want to be able to use other peoples improvements. If they release improved versions of the software I started, I want to be able to merge those improvements if I want to.
So which is it? Do you want to be able to use other people's improvements, respecting the conditions you said they are legitimately entitled to make, or is this not quite the whole story?
Quoted 3 lines
But not within the confines of the Linux kernel. Within the Linux kernel, the GPLv2 rules - and "GPLv2+" becomes just "GPLv2", since the GPLv3 is not compatible with v2.
I understand this very well. You'd have to get the kernel upgraded to GPLv3 in order to accept the contribution.
Likewise for any other contribution under any other GPLv2-incompatible license.
So, you see, your statement above, about wanting to be able to use other people's improvements, cannot be taken without qualification.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 6 lines · Linus Torvalds
Quoted 5 lines · Alexandre Oliva
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
Quoted 4 lines
Quoted 1 line
You *cannot* make GPLv3-only contributions to the kernel.
I can make improvements to GPLv2+ files under GPLv3 (or rather will, after GPLv3 is published).
You can do that, but you won't be able to distribute those changes along with the rest of the kernel.
Signature · 1 line
Jeremy Maitin-Shepard
Quoted 9 lines · Jeremy Maitin-Shepard
Quoted 7 lines · Alexandre Oliva
Quoted 6 lines · Linus Torvalds
Quoted 5 lines · Alexandre Oliva
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
You *cannot* make GPLv3-only contributions to the kernel.
I can make improvements to GPLv2+ files under GPLv3 (or rather will, after GPLv3 is published).
You can do that, but you won't be able to distribute those changes along with the rest of the kernel.
I know. Neither will Linus. But he says he chose GPLv2 such that he could, and the v2 is better than v3 in this regard. What's wrong with this picture?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
I know. Neither will Linus. But he says he chose GPLv2 such that he could, and the v2 is better than v3 in this regard. What's wrong with this picture?
I'm sure it's a rethorical question - but what is wrong is that imho the clause that normally is added to any file under the GPL ("... version 2 or higher") is builtin in as a safeguard: If, for whatever reason, in the future it is discovered that the GPL version X has a flaw that was not forseen - then it can be 'patched' by writing a successor, having that released by the FSF and allow anyone to "upgrade" all GPL-ed software to the new license, as such having avoided the problems of the said (fictious) flaw.
Therefore, it seems pretty weird to me that LONG before version 3 was written and released, someone purposely would choose to freeze their software at version 2. Why make it "impossible" to use this safe-guard? ["impossible" because if you get a signature from every author where they transfer the authorship rights to you, you can re-release everything under a different license anyway. However, the kernel has so many authors who never signed anything(?) that this is not possible anymore].
I never knew it was possible to change the "version 2 or higher" into "only version 2", but I am not a laywer and not into licenses at all, and I am sure Linus had laywers look into this, so we can take this as a fact.
The result is simple:
1) A lot of files in the kernel are fixed at version 2.
2) Version 3 is incompatible with version 2 (which I also take for granted, having read that in this thread).
Many (or at least important) authors of version-2 files do not wish to change the license to one that allows it to be transformed to GPL v3 (ie, add the clause "version 2 or higher". Therefore, this will not happen.
The result is that it is impossible to accept/add patches that can not be converted to GPL v2 (ie, which are explicitely version 2 or have the phrase "version 2 or higher").
I think this whole thread has only one purpose:
To "test" if the kernel source is indeed - by LAW - immutable and fixed to version 2.
Of course, as an unwritten rule, everyone here will respect Linus' wishes: he is our leader for things like this. But that is irrelevant when it is about important things like this:
One day he will be gone - and if this license "upgrade" is only stopped because people see him as a leader, then the discussion will happen again and again and again - until the software IS upgraded. This being a one-way lane (once upgraded, you can't go back) I think it is LOGICAL to do this: 1) Don't upgrade for as long as possible (possibly forever), 2) Have discussions like this while Linus is still alive until it is cristal clear that the kernel can or can not be "upgraded" to version 3 as a result of the law. And, imho, as I pointed out above - this is already clear to me (so this thread can end now as far as me is concerned).
Finally - I realize that most people who seem to oppose Linus - ie Alexandre, and me included, are NOT (perse) in favour of version 3 (I know I am not). The most important purpose of the discussion is to TEST if someone could force this "upgrade" in the future when leadership is less clear. So, I think it's good that some people are willing to take the side of version 3 and try to go all the way to prove that it's better and/or possible to "upgrade" etc - as if they REALLY want that.
Signature · 1 line
Carlo Wood <[email protected]>
Quoted 5 lines · Carlo Wood
Therefore, it seems pretty weird to me that LONG before version 3 was written and released, someone purposely would choose to freeze their software at version 2. Why make it "impossible" to use this safe-guard?
Because what you call "safe-guard" is just call "idiotic".
The fact is, anybody who cares about the copyright license he uses on software (and I sure do care!) should *never* give a blank check to somebody else that they don't trust to change that license for them.
In other words, the whole "v2 or later" language *only* makes sense if:
- You are the FSF, and you *decide* what "or later" actually means
In this case, you obviously don't have to trust "somebody else". You just trust yourself.
- You don't care about your choice of license.
In this case, you might as well let somebody else make that decision for you, although quite frankly, you might as well use something like the BSD license and let many *more* people make that decision to relicense for you.
- ..or you trust the FSF implicitly.
In this case, you're not an independent entity, you're just a lackey of the FSF when it comes to the license.
If none of those conditions are true, you'd be *incompetent* to leave the "v2 or later".
And I'm not incompetent. None of the above conditions holds true for me, so the "v2 or later" would be totally idiotic. Which is why Linux has *never* had that statement for *any* code I have ever written!
So the fact that *you* (and the FSF) call it a "safe-guard" by no means makes it so.
Quoted 4 lines
I never knew it was possible to change the "version 2 or higher" into "only version 2", but I am not a laywer and not into licenses at all, and I am sure Linus had laywers look into this, so we can take this as a fact.
What you state above is that you didn't even *READ* the GPL, yet you make some arguments about it as if you had!
So let me educate you. You may not want to be educated, but I'll try anyway:
- Please *read* the license that you discuss. If you don't read it, there's no point in you making any arguments about it.
And by reading it, I don't mean just mechanical "reading" in a technical sense. I mean "read and think about it"
- Once you have actually read it, you'll notice that there *is* no "either version 2 of the License, or (at your option) any later version" in the GPL v2 license AT ALL.
Really. That phrase DOES NOT EXIST in the GPLv2.
- That phrase exists *outside* the license, in the *suggestion* of how you migth want to use it! Notice how that license comes *after* the "END OF TERMS AND CONDITIONS" thing, and in the section that describes how you might *use* the license.
In other words, you are a perfect example of somebody who argues about the GPLv2 without ever having read or understood it!
I'm really tired of people claiming that the kernel license is a "modified" GPLv2 to remove the "v2 or later" language. It's *not* modified at all: that language simply DOES NOT EXIST in the GPLv2. It exists outside the license, in a suggestion on how you _might_ use it, and it's a suggestion that my code has *never* *ever* actually followed.
Quoted 1 line
From the very first version of Linux that used the GPLv2 (that would be
Linux-0.95, iirc), Linux has *always* been under a unmodified GPLv2. Not "any later". Not "modified". It has *always* stated the version explicitly (by *including* it verbatim - there was certainly never any ambiguity about versions), and it has *never* stated "v2 or later" in any source code I wrote!
Yes, afterwards, I have added clarifications, because it turns out that lawyers (and non-lawyers, for that matter) actually prefer having certain things clarified and written out, so that nobody can later claim that they misunderstood certain things.
But even those clarifications NEVER MODIFIED THE ACTUAL LICENSE. They are literally just clarifications. The license didn't change.
The clarifications are
- the obvious *fact* that user-mode code using standard system calls is not a derived work of the kernel.
This is so obvious to anybody with any knowledge of what "derived work" means that there is absolutely no legal question about this being a fact, but the FSF had made such a name for the GPL being "viral" that some people were still worried that I was crazy and would sue. They probably weren't actually worried that they'd lose, but a lawsuit is potentially quite damaging (to PR and in just legal expenses) even if you do end winning, so to make it clear that I wasn't crazy, I added a clarification about this very early on.
Side note: while it's just a clarification, and as such doesn't actually alter the license in *any* way, it's *also* a "public statement of intent", and as such has legal meaning: it means that if I were to stop taking my meds and go crazy, I *still* couldn't sue, because of the so-called "doctrine of lathes" (and probably other legal issues), since I have made it clear that you cannot be *expected* to be sued over it.
So please do realize that while a clarification does not change the license in any way, shape, or form, it does actually have some real legal implications as to whether you can effectively sue somebody. You cannot first claim that certain uses are ok, and then suddenly change your mind when people have made decisions based on your claim.
- the above *fact* that the source code never followed the FSF suggestion of "v2 or later" was clarified and made explicit.
Again, this in no way changed the license itself (that "v2 or later" language simply _does_not_exist_ in the GPLv2), but it *also* didn't actually change the licensing of the code itself. Because the whole "v2 or later" language (in the "how to use") only takes effect *if*it*exists* in the source code, and the whole "any version of your choice" language (which *does* exist in the GPLv2) only takes effect if there wasn't some explicit license version that was obvious (and dammit, it doesn't get much more obvious than a COPYING file that includes the whole license *verbatim*)
So I am 100% sure that the whole Linux kernel is "v2 only". It has *always* been "v2 only" since very early in 1992, and before that, it wasn't GPL'd at all.
Certain individual *parts* of the kernel can be used under other licenses (BSD, Mozilla, and yes, GPLv3+), but that is very much a localized issue, and does not in any way change the fact that the Linux kernel itself in its entirety is GPL version *2*. And nothing else.
And I'm also 100% sure that anybody who claims otherwise is totally ignorant of either copyright law, the GPLv2, or *both*.
Linus
Quoted 3 lines
Quoted 1 line
"version 2 or higher"
That phrase exists outside the license
That's true. But sec. 9 of the GPLv2 says:
If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
So, by making the COPYING contain the v2 text, is the author specifying a particular version? If yes, then the sec. 9 provision would be meaningless, since there would be no way to not specify a version number.
My understanding is that courts would presume that a license term has a meaning, if it has a plausible reading. And there such a reading:
that to specify a version, there needs to be (e.g. in the source files) a statement like, "This file [or work] is licensed under the GNU GPLv2."
Corrections, flames, etc. are welcome.
-Sanjoy
Quoted 4 lines · Sanjoy Mahajan
So, by making the COPYING contain the v2 text, is the author specifying a particular version? If yes, then the sec. 9 provision would be meaningless, since there would be no way to not specify a version number.
Of course the "published under terms of GPL." would do.
Signature · 1 line
Krzysztof Halasa
Quoted 6 lines · Krzysztof Halasa
Quoted 4 lines
So, by making the COPYING contain the v2 text, is the author specifying a particular version? If yes, then the sec. 9 provision would be meaningless, since there would be no way to not specify a version number.
Of course the "published under terms of GPL." would do.
It would do, if you could stop there and say no more. But:
You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you...give any other recipients of the Program a copy of this License along with the Program. [GPLv2, section 1]
So you have to give recipients the license text from a particular version of the GPL. To make that the only version unde which the work is licensed, you have to add something like "Licensed under the GPLv2". Otherwise sec. 9 says that you offer the work under any version of the GPL, and the licensee can take his or her pick -- even using v1 (!).
-Sanjoy
Quoted 6 lines · Sanjoy Mahajan
So you have to give recipients the license text from a particular version of the GPL. To make that the only version unde which the work is licensed, you have to add something like "Licensed under the GPLv2". Otherwise sec. 9 says that you offer the work under any version of the GPL, and the licensee can take his or her pick -- even using v1 (!).
That's exactly what I meant by "not specifying the version".
Signature · 1 line
Krzysztof Halasa
Quoted 6 lines · On Thursday 14 June 2007 19:20:19 Alexandre Oliva wrote:
Quoted 3 lines
But not within the confines of the Linux kernel. Within the Linux kernel, the GPLv2 rules - and "GPLv2+" becomes just "GPLv2", since the GPLv3 is not compatible with v2.
I understand this very well. You'd have to get the kernel upgraded to GPLv3 in order to accept the contribution.
Why do you keep saying "upgraded" to GPLv3? How is it an improvement to move from a small, simple, elegant, and tested implementation to something that's more complicated, less elegant, less coherent, totally untested, and full of numerous special cases?
Bumping a version number is not in indicator of quality, and spending over twice as much text to express the same legal principles is not an improvement. So far, you haven't brought up a single reason to use v3 except for a higher version number. (Not that I'm asking you to.) You've just tried to argue that it isn't WORSE than the existing license.
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 4 lines · Rob Landley
Why do you keep saying "upgraded" to GPLv3? How is it an improvement to move from a small, simple, elegant, and tested implementation to something that's more complicated, less elegant, less coherent, totally untested, and full of numerous special cases?
Ahhh, but so much more entreprisy. I never had realized before that the DailyWTF applied to licenses too.
OG.
Quoted 6 lines · Rob Landley
Quoted 2 lines · On Thursday 14 June 2007 19:20:19 Alexandre Oliva wrote:
I understand this very well. You'd have to get the kernel upgraded to GPLv3 in order to accept the contribution.
Why do you keep saying "upgraded" to GPLv3?
Just because it has a higher version number. Honest, no other reason was implied.
I'm seriously not trying to push v3 here. I got into this to try to dispell myths and get a better grasp of the situation.
Quoted 1 line
Bumping a version number is not in indicator of quality,
Agreed. Still, some people talk about upgrading from XP to Vista (ok, no numbers here, but you get the idea), just like they talk about upgrading from linux 2.4 to 2.6.
Quoted 1 line
So far, you haven't brought up a single reason to use v3
Sure, that was not my goal. I wasn't even trying.
Would you like me to?
Quoted 2 lines
You've just tried to argue that it isn't WORSE than the existing license.
Good, it's nice when people get the idea of what I'm trying to accomplish. I feared this had been lost in the noise.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
So, you see, your statement above, about wanting to be able to use other people's improvements, cannot be taken without qualification.
No. Linus and other Linux kernels might *want* to take other people's improvements, but thanks to Richard Stallman's choices for GPLv3, they can *not* legally take other people's improvements without violating the GPLv3 license. That's not their fault, it's the fault of people who wrote the GPLv3 license, promulgated the GPLv3 license, and who is attempting to convince everyone that the GPLv3 license is the only valid license for Right Thinking FSF automatons to use.
There are plenty of things that I might *want* to do, that I am legally prohibited from doing. that doesn't change the fact that I might want to do it. The fact that GPLv3 is incompatible with GPLv2 is a tragedy, in the Greek sense.
- Ted
Quoted 8 lines · On Fri, 15 Jun 2007 01:24:32 -0400 Theodore Tso <[email protected]> wrote:
No. Linus and other Linux kernels might *want* to take other people's improvements, but thanks to Richard Stallman's choices for GPLv3, they can *not* legally take other people's improvements without violating the GPLv3 license. That's not their fault, it's the fault of people who wrote the GPLv3 license, promulgated the GPLv3 license, and who is attempting to convince everyone that the GPLv3 license is the only valid license for Right Thinking FSF automatons to use.
Quoted 4 lines
There are plenty of things that I might *want* to do, that I am legally prohibited from doing. that doesn't change the fact that I might want to do it. The fact that GPLv3 is incompatible with GPLv2 is a tragedy, in the Greek sense.
The _exact_ same arguments are made against the GPLv2 by the BSD folks.
Given that many people here defend the GPLv2 over BSD, it's ironic the tone and level of vitriol shown against the v3 and such a willingness to use the same arguments the BSD folks use against v2.
Both v2 and v3 enforce some restrictions that people who want to participate must obey. And _yes_ I acknowledge that v3 has _more_ restrictions. But then, v2 has more restrictions than BSD and we're more or less happy with that, aren't we? In fact, many of us believe it's a virtue that Linux has a more restrictive license than that of the BSD's.
While this isn't an argument that we should happily accept more restrictions, hopefully it will put things in a cheerier perspective. We're not talking about a fundamental disagreement (ie. no restrictions versus any restrictions); we're simply talking about _degree_ of restriction.
There's no problem with people voicing honest disagreement with the v3, but please lighten up a bit on FSF bashing and the Greek tragedy talk.
Sean.
Quoted 2 lines · Sean
There's no problem with people voicing honest disagreement with the v3, but please lighten up a bit on FSF bashing and the Greek tragedy talk.
<wry> Would you prefer a reference to Resistible Rise of Arturo Ui? </wry>
Quoted 11 lines · Theodore Tso
Quoted 2 lines · Alexandre Oliva
So, you see, your statement above, about wanting to be able to use other people's improvements, cannot be taken without qualification.
No. Linus and other Linux kernels might *want* to take other people's improvements, but thanks to Richard Stallman's choices for GPLv3, they can *not* legally take other people's improvements without violating the GPLv3 license. That's not their fault, it's the fault of people who wrote the GPLv3 license, promulgated the GPLv3 license, and who is attempting to convince everyone that the GPLv3 license is the only valid license for Right Thinking FSF automatons to use.
Ah no, it's their fault. The GPLv2 always was clear that there will be some future releases of the GPL, and that you should keep "upgrading" possible.
Quoted 4 lines
There are plenty of things that I might *want* to do, that I am legally prohibited from doing. that doesn't change the fact that I might want to do it. The fact that GPLv3 is incompatible with GPLv2 is a tragedy, in the Greek sense.
The GPLv2 tries hard to be compatible with any further versions of the GPL as possible, by allowing people to choose which license you take, and by making sure that no man in the middle can restrict this choice. If people deliberately select to use "GPLv2 only", who's to blame? RMS? Come on, that's bullshit. It's *Linus Torvalds* who made Linux incompatible with GPLv3, nobody else - ok, Al Viro with his tagged GPLv2 files (and honestly, I think this is just another Linus misinterpretation about the GPL, and he really didn't do it, because he couldn't).
This thread was fun, but I think all arguments have been repeated often enough. I try to give up. I suggest everyone who has some assertions about what the GPLv2 does read it through and find the place where it says so. Unfortunately, I haven't seen GPL citations from the Linus-fanboy curve, only suggestions that the GPL "does not say something" which it clearly does.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 13 lines · On Friday 15 June 2007 06:02:11 Bernd Paysan wrote:
Quoted 11 lines · Theodore Tso
Quoted 2 lines · Alexandre Oliva
So, you see, your statement above, about wanting to be able to use other people's improvements, cannot be taken without qualification.
No. Linus and other Linux kernels might *want* to take other people's improvements, but thanks to Richard Stallman's choices for GPLv3, they can *not* legally take other people's improvements without violating the GPLv3 license. That's not their fault, it's the fault of people who wrote the GPLv3 license, promulgated the GPLv3 license, and who is attempting to convince everyone that the GPLv3 license is the only valid license for Right Thinking FSF automatons to use.
Quoted 2 lines
Ah no, it's their fault. The GPLv2 always was clear that there will be some future releases of the GPL, and that you should keep "upgrading" possible.
Not true at all. The GPLv2 leaves it up to the person placing their work under the GPLv2 license that its up to them whether they want the license on their "covered work" to be able to be changed. That the boilerplate includes this clause is pretty pointless - anyone can easily remove the "or, at your option, any later version" clause and render section 9 meaningless as applies to their work.
Quoted 5 lines
Quoted 4 lines
There are plenty of things that I might *want* to do, that I am legally prohibited from doing. that doesn't change the fact that I might want to do it. The fact that GPLv3 is incompatible with GPLv2 is a tragedy, in the Greek sense.
Quoted 8 lines
The GPLv2 tries hard to be compatible with any further versions of the GPL as possible, by allowing people to choose which license you take, and by making sure that no man in the middle can restrict this choice. If people deliberately select to use "GPLv2 only", who's to blame? RMS? Come on, that's bullshit. It's *Linus Torvalds* who made Linux incompatible with GPLv3, nobody else - ok, Al Viro with his tagged GPLv2 files (and honestly, I think this is just another Linus misinterpretation about the GPL, and he really didn't do it, because he couldn't).
Incorrect. Read section 9 of the GPLv2. It's pretty clear that the "any later version" clause is optional. Whats more is that since the modern linux kernel *IS* a "composite work" composed of Linus' original code with changes contributed by other people - Linus retains copyright to the work as a whole. This means that he can license it in any manner he chooses, as long as it doesn't affect the copyrights (or licensing) of the people that have contributed changes. I don't have to go to the US copyright law for this - Linus released Linux under the GPL, others made changes and sent them back saying "You let me have access to your code under the GPL, I've made some changes that make it better. You can have my changes under the GPL." QED:
Linus still holds copyright to Linux and can license it in any way he chooses. This is limited because of the license he accepted when adding the changes back to his code. He may have locked the kernel, as a whole, to version 2 of the GPL - but that is his right. There is nothing he has done that has stopped people from having their code included that is still "v2 or later".
Quoted 6 lines
This thread was fun, but I think all arguments have been repeated often enough. I try to give up. I suggest everyone who has some assertions about what the GPLv2 does read it through and find the place where it says so. Unfortunately, I haven't seen GPL citations from the Linus-fanboy curve, only suggestions that the GPL "does not say something" which it clearly does.
Because there has been no need to quote the GPLv2 until it became clear that people were going to keep claiming it stated things it did not. Since then I've started quoting the relevant sections of it.
But I agree with you - the thread was fun. And then I realized that the discussion was going nowhere at all. So I'm going to answer the last few messages in my inbox and then start filtering messages with this topic off without reading them.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 4 lines · Daniel Hazelton
Incorrect. Read section 9 of the GPLv2. It's pretty clear that the "any later version" clause is optional. Whats more is that since the modern linux kernel *IS* a "composite work" composed of Linus' original code with changes contributed by other people - Linus retains copyright to the work as a whole.
Huh - surely not to files added to the kernel that were written by others from scratch!
Quoted 8 lines
This means that he can license it in any manner he chooses, as long as it doesn't affect the copyrights (or licensing) of the people that have contributed changes. I don't have to go to the US copyright law for this - Linus released Linux under the GPL, others made changes and sent them back saying "You let me have access to your code under the GPL, I've made some changes that make it better. You can have my changes under the GPL." QED:
Linus still holds copyright to Linux and can license it in any way he chooses.
This is totally new to me - if this is true - I'd really like to be sure! I always thought that it would be necessary to get signatures of each and every contributor before you can change a license of a file. Why do you think that the FSF demands written copyright-transfers with signatures before you are allowed to submit a patch to any of their largers projects? If they - as original copyright holder - could do what you claim - they wouldn't need those signatures.
Having signed a copyright transfer for 'future' changes for gprof, libiberty, readline, zlib, gcc, gdb, libstdc++, bfd, dejagnu, gas, and binutils,
Carlo Wood <[email protected]>
Quoted 8 lines · Carlo Wood
Quoted 4 lines · Daniel Hazelton
Incorrect. Read section 9 of the GPLv2. It's pretty clear that the "any later version" clause is optional. Whats more is that since the modern linux kernel *IS* a "composite work" composed of Linus' original code with changes contributed by other people - Linus retains copyright to the work as a whole.
Huh - surely not to files added to the kernel that were written by others from scratch!
Actually, yes. Even to those - when they are part of "the whole".
I'm sorry, but I've learnt more about copyright law, and talked to more lawyers about licensing that probably most of the rest of the people involved in this discussion have *combined*.
And yes, at least under US copyright law, and at least if you see Linux as a "collective work" (which is arguably the most straightforward reading og copyright law, but perhaps not the only one) I am actually the sole owner of copyright in the *collective* work of the Linux kernel.
The way "collective works" work, there are two separate copyrights: there is the copyright in the "separate contribution", which is vests ininitally in the author of that contribution (unless he signs over his copyrights, often by virtue of working for somebody else).
And then there is the copyright in the "collective work", which would be me.
Of course, owning coyright in the "collective work" doesn't actually give me complete control anyway. I cannot relicense things in ways that go against the rules of the individual works. But in a very real sense, yes, I actually do own a certain (*limited*) copyright over even the parts that have not been explicitly signed over to me.
And yes, there are other potential ways to describe Linux, and in the end, it doesn't really matter. Because the way the GPLv2 works, it makes it clear that as long as a piece is a part of the whole, it has to be licensed under the GPLv2 and nothing else.
And btw, just to make you feel safe - I cannot do anything about that, even if I *do* own the copyright in the collective, because of the limitations on what that colletive work copyright implies (it says that I have the right to reproduce and distribute, but I don't have the right to *modify* except as given to me by the original author!)
So don't worry. I *technically* have certain special rights, but I practically speaking gave up most all of those rights by accepting code from others under the GPLv2 - since in order to do that, I had to agree to be bound by the GPLv2 license myself.
Quoted 1 line
This is totally new to me - if this is true - I'd really like to be sure!
It would be generally held to be true at least in the US, but it doesn't really matter.
Quoted 2 lines
I always thought that it would be necessary to get signatures of each and every contributor before you can change a license of a file.
You are mostly correct. The "mostly" comes because I would not say "every contributor", but would clarify it by saying "every copyright holder". The difference? Not all contributions are necessarily copyrightable. If you send in trivial one-liners, we will credit you for them, but that does not automatically mean that you necessarily own copyright in something.
But yes, somebody who wrote an original file (that has some artistic expression, and isn't just a list of PCI ID's, for example) will be the copyright owner in that file. Some *very* few people have actually sent me paperwork to transfer the ownership of copyrights, but they seem to have done that because they were just used to doing it with the FSF, and I actually don't care.
Linus
Quoted 15 lines · Linus Torvalds
Quoted 8 lines · Carlo Wood
Quoted 4 lines · Daniel Hazelton
Incorrect. Read section 9 of the GPLv2. It's pretty clear that the "any later version" clause is optional. Whats more is that since the modern linux kernel *IS* a "composite work" composed of Linus' original code with changes contributed by other people - Linus retains copyright to the work as a whole.
Huh - surely not to files added to the kernel that were written by others from scratch!
Actually, yes. Even to those - when they are part of "the whole".
Quoted 8 lines
I'm sorry, but I've learnt more about copyright law, and talked to more lawyers about licensing that probably most of the rest of the people involved in this discussion have *combined*.
And yes, at least under US copyright law, and at least if you see Linux as a "collective work" (which is arguably the most straightforward reading og copyright law, but perhaps not the only one) I am actually the sole owner of copyright in the *collective* work of the Linux kernel.
US law is only relevant for < 5% of all people.
How valid would any action based on US copyright law be in other parts of the world?
Quoted 8 lines
The way "collective works" work, there are two separate copyrights: there is the copyright in the "separate contribution", which is vests ininitally in the author of that contribution (unless he signs over his copyrights, often by virtue of working for somebody else).
And then there is the copyright in the "collective work", which would be me.
Quoted 6 lines
Of course, owning coyright in the "collective work" doesn't actually give me complete control anyway. I cannot relicense things in ways that go against the rules of the individual works. But in a very real sense, yes, I actually do own a certain (*limited*) copyright over even the parts that have not been explicitly signed over to me.
...
Does this include GPLv2'ed code not intended to be used in the Linux kernel submitted by people other than the copyright holder for inclusion in the Linux kernel?
If yes, the FSF has exactly the same rights if taking a GPLv2 driver from the Linux kernel and including it in GNU Hurd.
Quoted 1 line
Linus
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines · Adrian Bunk
US law is only relevant for < 5% of all people.
How valid would any action based on US copyright law be in other parts of the world?
I tried to explain that in the case of the Linux kernel, we really don't care, since in the end, what matters is the GPLv2, and I have bound myself to the terms of that license *regardless* of any US law.
So yes, US law is only relevant for < 5% of all people, but in the specific case of the kernel, even that US law isn't _really_ all thgat relevant at all, not *even* to those 5% ;)
So I *really* hope you took my explanation of why I actually have more rights than others as a nitpicking "legal detail", not as a "I own your very SOUL, bow down before me!" kind of thing.
But to answer your question by _another_ nitpicking answer, as the original author, I probably do have some special legal status even in Europe, and probably in other places too. The fact that others *extended* on my original work doesn't take away the special place of original authorship, even if the extended version has a totally different form (ie, a movie based on a book ends up still havign the original author of the book holding special rights - and in fact those rights are in some cases much *stronger* in Europe than they are in the US).
For example, Europe recognizes "moral rights" in original authorship, in ways that it is much harder to enforce (if at all) in the US.
But as mentioned, since I myself has bound myself to the GPLv2, that really is a pretty damn theoretical argument. When it comes to the kernel, I'm "Primus inter pares", if you wish.
("First among equals", for the non-latin-speaking world ;)
Quoted 3 lines
Does this include GPLv2'ed code not intended to be used in the Linux kernel submitted by people other than the copyright holder for inclusion in the Linux kernel?
In the US sense of "within the compilation", probably yes. Ie that right is tied to *linux* as a compilation. In the European sense of "moral rights", no - that right is very much tied to original authorship (so I, as original author of Linux, have some rights with respect to Linux, but on the other hand, they, as the original authors of some specific code, have some specific rights wrt that code!)
Quoted 2 lines
If yes, the FSF has exactly the same rights if taking a GPLv2 driver from the Linux kernel and including it in GNU Hurd.
The FSF does indeed have special rights wrt Hurd, regardless of where the code in question has come from (as long as it came there *legally*, of course!). So when it comes to Hurd, they have the copyright in the compilation of that (and Red Hat as their copyright in their RHEL distribution - of which the kernel is just a small part!).
It's a confusing set of nesting dolls of different levels of copyrights, and the GPLv2 makes it all pretty much irrelevant, by being the thing that cuts through all the other licensing issues!
Linus
Quoted 2 lines · On Friday 15 June 2007 12:22:16 Adrian Bunk wrote:
Quoted 1 line · Linus Torvalds
On Fri, 15 Jun 2007, Carlo Wood wrote:
<snip>
Quoted 15 lines
Quoted 8 lines
The way "collective works" work, there are two separate copyrights: there is the copyright in the "separate contribution", which is vests ininitally in the author of that contribution (unless he signs over his copyrights, often by virtue of working for somebody else).
And then there is the copyright in the "collective work", which would be me.
Quoted 6 lines
Of course, owning coyright in the "collective work" doesn't actually give me complete control anyway. I cannot relicense things in ways that go against the rules of the individual works. But in a very real sense, yes, I actually do own a certain (*limited*) copyright over even the parts that have not been explicitly signed over to me.
...
Quoted 6 lines
Does this include GPLv2'ed code not intended to be used in the Linux kernel submitted by people other than the copyright holder for inclusion in the Linux kernel?
If yes, the FSF has exactly the same rights if taking a GPLv2 driver from the Linux kernel and including it in GNU Hurd.
Of course they do. That is defined by the license. They can include it with HURD, but that doesn't give them copyright to it, just the right to exercise the rights granted by the license.
DRH
Quoted 5 lines
Quoted 2 lines
Linus
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 3 lines · Linus Torvalds
I'm sorry, but I've learnt more about copyright law, and talked to more lawyers about licensing that probably most of the rest of the people involved in this discussion have *combined*.
Which is why I have taken everything you said so far for granted as being a fact -- no need to try to convince me of something ;) In my case it suffices if you say that you are sure (and before anyone says: you're nuts - what I REALLY mean is 'for the purpose of this discussion'. For me, it makes no sense to waste more time on discussing such an issue; I won't bet all my money it, of course).
[..snip..]
Quoted 8 lines
Quoted 2 lines
I always thought that it would be necessary to get signatures of each and every contributor before you can change a license of a file.
You are mostly correct. The "mostly" comes because I would not say "every contributor", but would clarify it by saying "every copyright holder". The difference? Not all contributions are necessarily copyrightable. If you send in trivial one-liners, we will credit you for them, but that does not automatically mean that you necessarily own copyright in something.
I knew that.
Quoted 8 lines
But yes, somebody who wrote an original file (that has some artistic expression, and isn't just a list of PCI ID's, for example) will be the copyright owner in that file. Some *very* few people have actually sent me paperwork to transfer the ownership of copyrights, but they seem to have done that because they were just used to doing it with the FSF, and I actually don't care.
Linus
The point is: can you, or can't you (legally) relicense the whole kernel tree under the GPLv3 (or GPLv2+GPLv3)?
At first I thought that you cannot, because too many (significant) contributors have been involved (and you will never get signatures from them all). Then someone surprised me by claiming that the original author had copyright for everything - even files added by others. To me, this seemed to say: even if those contributors don't like it, the original author can still sell the whole to some company under a proprietary license (also still having the original under the GPL on the net, of course), as he could do when he was the sole author.
Then you reply with:
Quoted 3 lines
Carlo> Huh - surely not to files added to the kernel that were written by Carlo> others from scratch!
Linus> Actually, yes. Even to those - when they are part of "the whole".
But the rest of your reply made it a bit unclear again.
Assume you stopped taking your meds and next week you think that GPLv3 is THE thing for the kernel. Then could you legally, or can't you, go ahead and change the license of the whole kernel to GPLv3? And if you can't, then roughly how many files / authors are stopping you from doing so?
If the answer is: I can't. Then I think you're a lucky bastard, and have escaped years and years of discussions with people trying to convince you that the GPLv3 is better ;)
I think that the question: can OTHERS "upgrade" the kernel to GPLv3 has been answered clearly now: No they can't. But if you can, you're probably not done with dealing with people who want that to happen.
Signature · 1 line
Carlo Wood <[email protected]>
Quoted 3 lines · Carlo Wood
The point is: can you, or can't you (legally) relicense the whole kernel tree under the GPLv3 (or GPLv2+GPLv3)?
No. My special rights do not actually give me those kinds of powers, exactly because I'm bound by my _other_ agreement (namely the GPLv2) to follow the license of the code that other people have sent me.
Quoted 4 lines
At first I thought that you cannot, because too many (significant) contributors have been involved (and you will never get signatures from them all). Then someone surprised me by claiming that the original author had copyright for everything - even files added by others.
Both are true facts, but the "copyright for everything" is a *separate* kind of copyright, which does not include the right to relicense. It's literally the "copyright in the collective".
For examples of the US rules, see USC 17.2.201(c) ("Ownership of copyright" and " Contributions to Collective Works"), which spells out some limited special rights that I have (namely the right to reproduce and distribute).
Of course, US law being what it is, the USC is just part of the picture. US law is the strange kind of British law, where "case law" is in many ways more important than the written-down rules like the USC. So caveat emptor!
So I have limited special rights in the collective, but those rights are actually in almost every way *more* limited than the rights that the GPLv2 gives to me (the "almost every way" is because quite frankly, I'm not entirely sure about certain special cases. In particular, if somebody tried to _revoke_ the rights to their code under the GPLv2, I suspect that my rights in the collective would protect me from that and allow me to still distribute the code in question, since _those_ rights cannot be revoked, and they are _mine_).
And btw: the above paragraph is *way* more legalistic detail than I am at all ready to state as "fact". It depends on too many things, and is largely speculative in nature.
But one thing is pretty clear and nonspeculative: *nobody* has the right to upgrade the kernel to GPLv3. Not me, not you, not anybody. Not without clearing it with every single person whose copyright is involved and who didn't already give that permission.
So only in the case of some really obscure and unclear situations, I _may_ have more rights than some other people, but trust me, but that is damn murky, and you'd better have a good lawyer state it, not just a programmer who has talked to too many lawyers..
Linus
Quoted 13 lines · On Friday 15 June 2007 14:15:58 Linus Torvalds wrote:
Quoted 2 lines · Carlo Wood
The point is: can you, or can't you (legally) relicense the whole kernel tree under the GPLv3 (or GPLv2+GPLv3)?
No. My special rights do not actually give me those kinds of powers, exactly because I'm bound by my _other_ agreement (namely the GPLv2) to follow the license of the code that other people have sent me.
Quoted 4 lines
At first I thought that you cannot, because too many (significant) contributors have been involved (and you will never get signatures from them all). Then someone surprised me by claiming that the original author had copyright for everything - even files added by others.
Quoted 8 lines
Both are true facts, but the "copyright for everything" is a *separate* kind of copyright, which does not include the right to relicense. It's literally the "copyright in the collective".
For examples of the US rules, see USC 17.2.201(c) ("Ownership of copyright" and " Contributions to Collective Works"), which spells out some limited special rights that I have (namely the right to reproduce and distribute).
http://www.copyright.gov/title17/92chap2.html#201
There are some really interesting bits in Chapter 1 too...
http://www.copyright.gov/title17
Quoted 2 lines
entirely sure about certain special cases. In particular, if somebody tried to _revoke_ the rights to their code under the GPLv2,
There's no revocation clause in the license. They can't. (SCO would have tried to revoke Caldera's license to its contributions it if it were at all possible.)
Quoted 4 lines
I suspect that
my rights in the collective would protect me from that and allow me to still distribute the code in question, since _those_ rights cannot be revoked, and they are _mine_).
Title 17 chapter 1 section 103(a) seems to lean against this. I think it says that having rights to the collective is conditional on having had the rights to the components of that collective.
Quoted 4 lines
So only in the case of some really obscure and unclear situations, I _may_ have more rights than some other people, but trust me, but that is damn murky, and you'd better have a good lawyer state it, not just a programmer who has talked to too many lawyers..
Entirely agreed. :)
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 9 lines · On Friday 15 June 2007 09:02:54 Carlo Wood wrote:
Quoted 5 lines · Daniel Hazelton
Incorrect. Read section 9 of the GPLv2. It's pretty clear that the "any later version" clause is optional. Whats more is that since the modern linux kernel *IS* a "composite work" composed of Linus' original code with changes contributed by other people - Linus retains copyright to the work as a whole.
Huh - surely not to files added to the kernel that were written by others from scratch!
Even those.
Quoted 9 lines
Quoted 8 lines
This means that he can license it in any manner he chooses, as long as it doesn't affect the copyrights (or licensing) of the people that have contributed changes. I don't have to go to the US copyright law for this
- Linus released Linux under the GPL, others made changes and sent them back saying "You let me have access to your code under the GPL, I've made some changes that make it better. You can have my changes under the GPL."
QED: Linus still holds copyright to Linux and can license it in any way he chooses.
Quoted 7 lines
This is totally new to me - if this is true - I'd really like to be sure! I always thought that it would be necessary to get signatures of each and every contributor before you can change a license of a file. Why do you think that the FSF demands written copyright-transfers with signatures before you are allowed to submit a patch to any of their largers projects? If they - as original copyright holder - could do what you claim - they wouldn't need those signatures.
They don't. They demand the signature so that some contributor can't change their mind at a later date or even be able to give a proprietary software vendor the ability to use the GPL'd code in a non-GPL project.
Quoted 4 lines
Having signed a copyright transfer for 'future' changes for gprof, libiberty, readline, zlib, gcc, gdb, libstdc++, bfd, dejagnu, gas, and binutils,
Carlo Wood <[email protected]>
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 3 lines · Bernd Paysan
Ah no, it's their fault. The GPLv2 always was clear that there will be some future releases of the GPL, and that you should keep "upgrading" possible.
No. It is clear that you have the *option* of keep upgrading, but it is also equally clear that Linux has always decided *not* to exercise that option, exactly because I liked the GPLv2, not some "future upgrade".
I decided that long before I saw the GPLv3.
And I'm surprised by people who wonder why I did that.
I'm _intelligent_, dammit. That means that I can foresee the future to some degree, at least in the limited sense of what is a likely outcome of my actions.
Why are people surprised by the fact that I have foresight? I may be known for being an impolite bastard, but quite frankly, anybody who thinks I'm a _stupid_ impolite bastard must be missing a page.
You can disagree with my opinions. You can call me obstinate, impolite, and opinionated. But quite frankly, very few people have ever found me *stupid*.
So give me that - I'm not stupid. That means that I actually *can* predict the future to some fuzzy degree, and that people really should *not* be surprised by the fact that I never let the FSF control my choice of license.
Quoted 4 lines
The GPLv2 tries hard to be compatible with any further versions of the GPL as possible, by allowing people to choose which license you take, and by making sure that no man in the middle can restrict this choice. If people deliberately select to use "GPLv2 only", who's to blame?
There's no "blame". There's only credit.
Besides, you are wrong. The *default* for the GPLv2 in the presense of license information is *not* "v2 or later"
In order to get "GPLv2 or later", you actually have to explicitly specify it.
I just find it sad that so many people did that, often apparently just because they didn't actually read or understand the license.
Linus
Quoted 7 lines · Bernd Paysan
Quoted 4 lines
the GPLv3 license. That's not their fault, it's the fault of people who wrote the GPLv3 license, promulgated the GPLv3 license, and who is attempting to convince everyone that the GPLv3 license is the only valid license for Right Thinking FSF automatons to use.
Ah no, it's their fault. The GPLv2 always was clear that there will be some future releases of the GPL, and that you should keep "upgrading" possible.
...
Quoted 2 lines
enough. I try to give up. I suggest everyone who has some assertions about what the GPLv2 does read it through and find the place where it says so.
Ok, open your local copy of the GPL (you should have a copy in /usr/share/common-licences/GPL if you use Debian).
Now read along with me...
| GNU GENERAL PUBLIC LICENSE
| Version 2, June 1991
Ok, we have that settled, this license describes GPL version 2, specifically, no if's or later's. Bunch of legal mumbo jumbo follows until we reach...
| END OF TERMS AND CONDITIONS
And we've reached the end of the license. Now it it followed up by some helpful text for the reader...
| How to Apply These Terms to Your New Programs
...
| To do so, attach the following notices to the program. It is safest | to attach them to the start of each source file to most effectively | convey the exclusion of warranty; and each file should have at least | the "copyright" line and a pointer to where the full notice is found. | | <one line to give the program's name and a brief idea of what it does.> | Copyright (C) <year> <name of author> | | This program is free software; you can redistribute it and/or modify | it under the terms of the GNU General Public License as published by | the Free Software Foundation; either version 2 of the License, or | (at your option) any later version.
Look, some example boiler plate that is suggested to be placed in the source code _to most effectively convey_ that the code is GPL licensed. So clearly there must be less effective ways, one of which may just be to include a COPYING or LICENSE file along with the distributed source.
And the author of this example boiler place is clearly 'talking' to the the copyright owner/licensor (i.e. not the licencee), giving suggestions about adding contact information and even possible commands that could be added to interactive programs. So that '(at your option)' may just be a suggestion to the licensor, or maybe not. But that isn't really here not there.
Files that don't have such boiler plate do not convey the terms of the license as effectively, but they are still covered by the license that was included with the kernel, which is clearly version 2.
Now ofcourse we were looking at the official GPLv2, so I ran a diff against the COPYING file in the kernel tree. The only differences I can see are the included clarification by Linus at the top, some formatting differences and the fact that the FSF version seems to refer to the 'GNU Lesser General Public License', while Linus's version has, 'GNU Library General Public License'.
Quoted 3 lines
Unfortunately, I haven't seen GPL citations from the Linus-fanboy curve, only suggestions that the GPL "does not say something" which it clearly does.
I hope this helps.
Jan
Quoted 9 lines · Theodore Tso
Quoted 3 lines · Alexandre Oliva
So, you see, your statement above, about wanting to be able to use other people's improvements, cannot be taken without qualification.
No. Linus and other Linux kernels might *want* to take other people's improvements, but thanks to Richard Stallman's choices for GPLv3, they can *not* legally take other people's improvements without violating the GPLv3 license.
This argument is backwards. It's because of Linus' choice for GPLv2 that he can't take improvements under the GPLv3.
Had he chosen any other GPLv3-compatible license, he could.
And the same applies to any other incompatible pair of licenses.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 9 lines · On Thursday 14 June 2007 18:35:01 Alexandre Oliva wrote:
Quoted 3 lines · Linus Torvalds
I want to be able to use other peoples improvements. If they release improved versions of the software I started, I want to be able to merge those improvements if I want to.
Hmm... So, if someone takes one of the many GPLv2+ contributions and makes improvements under GPLv3+, you're going to make an effort to accept them, rather than rejecting them because they're under the GPLv3?
Doesn't matter at all. GPLv3 requires that any project incorporating GPLv3 code be licensed under the GPLv3. Linus is, as he has shown, intelligent enough to know this. The *second* he actually accepted GPLv3 code into the kernel it would either be "change the license or start getting lawsuits for breach of the terms of the GPLv3".
Quoted 11 lines
Quoted 3 lines
Your *IDIOTIC* suggestion is explicitly against the whole POINT! By saying that I shouldn't accept contributions like that, you just INVALIDATED the whole point of the license in the first place!
I understand. I assumed you had some trust that people would abide by your wish to permit TiVOization, and that authors of modifications were entitled to make "whatever restrictions they wanted" on their code.
Pardon me if I think your position is at least somewhat incoherent. Can you help me make sense of it?
You are making a distinction between "part" and "whole". When separate from the kernel the code can have whatever restrictions the creator pleases. If he has said "I want this in the "official" Linux Kernel" (ie: I want this in Linus' Linux Kernel source tree) then the creator of the code has stated a willingness to abide by Linus' decision about the whole work.
It's a moot point, though. The Linux Kernel is licensed under GPLv2, which means that *all* code in it has to be under the same license *and* that no code in it can have any restrictions *NOT* in the GPLv2.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 7 lines · On Thursday 14 June 2007 15:46:36 Alexandre Oliva wrote:
Quoted 4 lines · Linus Torvalds
Quoted 1 line · Alexandre Oliva
Is there anything other than TiVOization to justify these statements?
Do you need anything else?
No, I'm quite happy that this is all.
So am I, actually :)
Quoted 8 lines
Quoted 5 lines
But if by the question you mean "would you think the GPLv3 is fine without the new language in section 6 about the 'consumer devices'", then the answer is that yes, I think that the current GPLv3 draft looks fine apart from that.
Then would you consider relicensing Linux under GPLv3 + additional permission for Tivoization?
With Al Viro, at least, specifying that his code has been released *strictly* under GPLv2, this is impossible.
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
Also, can you elaborate on what you mean about 'giving back in kind'? (I suspect this is related with the tit-for-tat reasoning, that you've failed to elaborate on before)
I've *not* failed to elaborate on that before. Not at all.
Just google for
Quoted 8 lines
Quoted 4 lines
torvalds tit-for-tat
and you'll see a lot of my previous postings. Trying to claim that this is somehow "new" is ludicrous.
I didn't. But I've provided evidence that your prior musings on this topic were wrong. I wanted to give you an opportunity to review your position under this new light. I see you haven't changed it at all.
It is wrong when you look at the text of the GPLv2 only. When you look at how the "Open Source" community works it is clear that the "tit-for-tat" nature is a reality. No, it isn't mandated by GPLv2, but that is the "spirit" of the GPLv2 that most people who work on Open Source projects follow.
If you want a *REAL* and *CONTINUING* violation of the GPL just look at Herr Schillings "cdrecord", in which he places additional restrictions on peoples ability to modify the code with statements in the same such as "You must leave this check in place" or "You have to leave this comment in place" - even when the comment isn't part of the "licensing statement" mandated by the GPLv2. (if you want specifics I'll go download the source and pull them out)
Quoted 10 lines
Quoted 5 lines
Giving back "in kind" is obvious. I give you source code to do with as you see fit. I just expect you to give back in kind: source code for me to do with as I see fit, under the same license I gave you source code.
How hard is that to accept?
Forgive me if I find this a bit hard, because that's *not* what the GPL says.
Where do you think the GPL say that you get the source code back?
It doesn't. But that it doesn't *MAKES* *NO* *DIFFERENCE* because, in practice, that is *EXACTLY* what happens anyway.
<snip>
Quoted 12 lines
Quoted 2 lines
I don't call Linux "Free Software". I haven't called it that for close to ten years! Because I think the term "Open Source" is a lot better.
I can appreciate that you think it's better, but unfortunately it appears to be playing a significant role in confusing your interpretation of the GPL. The GPL is not just about making the source code visible, or even modifyable by others. It's about respecting others' freedoms. No matter how badly you prefer Open Source over Free Software, how badly you'd rather disregard the freedoms in the spirit and in the legal terms of the GPL, you chose a license designed to protect those freedoms, not only the ability to see and modify source code.
Which is not in question here. The objections Linus (and others) have to the GPLv3 may share some specifics with my own objections, but my own are that GPLv2 respects my freedoms in their entirety. GPLv3 restricts my freedoms because one (or more) of the people behind it have a political agenda. (No, that term isn't entirely accurate, but its the best one I have found for the situation. Explanation: We don't like the way the law of one or more munincipalities/political divisions/countries is written and rather than trying to get it changed through other channels, we are going to enforce the way we think it should be by using a related set of laws and the text of a license)
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
The only thing the GPL demands is respect for others' freedoms, as in, "I, the author, respect your freedoms, so you, the licensee, must respect others' freedoms as well". Is this the "in kind" you're talking about? Or are you mistaken about the actual meaning of even GPLv2?
Quoted 6 lines
Quoted 2 lines
I just ask that you give the software back in a usable form. That's all I ask for.
I'm afraid that's not what the GPLv2 says. There's no provision whatsoever about giving anything back. Not in the spirit, not in the legal terms.
But it does. If you are going to distribute your own, modified version - in any way - you have to make the source available as well.
No, it doesn't require that you give back a version if you aren't distributing it, but in that case it hardly matters.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 10 lines · On Thursday 14 June 2007 13:14:09 Sean wrote:
On Thu, 14 Jun 2007 09:01:32 -0700 (PDT)
Quoted 6 lines · Linus Torvalds
In other words, we're just *much* better off with a friendly license and not trying to force people to choose sides, than with the rabid idealism that was - and still is - the FSF. The FSF always makes for this horrible "you're with us, or you're against us" black-and-white mentality, where there are "evil" companies (Tivo) and "good" companies (although I dunno if the FSF really sees anybody as truly "good").
Quoted 4 lines
Linus,
If you really believe that then why didn't you choose a BSD license for Linux?
BSD licenses encourage forking. Specifically, if a BSD-licensed project becomes significantly commercially valuable, there's an incentive for companies to hire your developers away to work on a proprietary fork.
When Sun Microsystems started up in 1982, they hired away Bill Joy to work on a closed version of BSD (SunOS). When Berkeley shut down the CSRG, BSDi hired those developers to work on another closed source BSD variant. More recently, Apple hired people like Jordan Hubbard away from FreeBSD to do yet another fork: MacOS X. The loss of people hurts the original project.
With BSD licensed code, companies can say "work on the codebase you love as a day job, and you can still work on the open version at night". Then work them 90 hours/week. Or even "we'll release this code open source after we can't sell it anymore, a year or two from now". And then the deadline never comes, or the codebase is irrelevant by then, or too far diverged to merge. You won't get all the developers, but you'll get enough to cost the open project momentum. BSD is 30 years old and the free version is still a pale shadow of its proprietary forks like MacOS X or the bits of it Windows incorporated.
Now think about trying to do that to a GPL project. If you hire the developers away, they have to work on a _different_ codebase. Much less compelling, both for the hirer and the hiree. If you think Linux is compelling enough to commercialize, you MUST do so within the terms of the GPL or not do it at all. You can't do a closed fork and distribute the result. Maybe this means companies aren't as quick to jump on the bandwagon trying to commercialize it, but the project can then grow larger without interference until commercial participation _is_ compelling, on its own merits, despite being unable to corner the market on it.
Quoted 4 lines
Instead you chose a license which enforced the so called tit-for-tat policy you think is fair. But people who prefer the BSD license may think you're a moron for forcing your political agenda (ie. tit-for-tat) on users of your code.
It's not political, it's pragmatic. GPLv2 has tangible benefits for project maintainers.
Quoted 8 lines
The point of all that being, you _do_ believe
in enforcing restrictions or you wouldn't like the GPL v2.So you draw the line of "fairness" and belief that people will do-the-right-thing somewhere short of the BSD license. Why is it so hard then to accept that the FSF draws the line short of the GPLv2 after having gained practical experience with it since its release?
Nobody objects to the FSF putting out new licenses if it changes its mind about what it wants to do. They object to it pestering those of us continuing to use the old license because we prefer it to the new one.
The FSF _does_ draw the line in a different place than the Linux developers. Hence the Linux developers don't want to use the new license, they prefer the old one from back before Stallman went insane. They have that right, and Stallman trying to deny them that right in the name of "freedom" is deeply ironic.
Quoted 2 lines
You can argue till the cows come home the belief that _your_ restrictions are more fair, moral and reasonable than theirs.
It's not the FSF's code being licensed. It's the Linux developers' code being licensed. The people who write the code get to choose the license.
Quoted 2 lines
But at the end of the day it's all just a matter of opinion about what constitutes fair and reasonable.
Why is Linus's opinion less valuable than Stallman's when it comes to the license under which the project Linus founded, and which Linus still maintains, is distributed?
Quoted 5 lines
You think its a fair trade
that you get code back, the FSF think its fair that people can hack and run the code anywhere its used.. It all comes down to the author of the code getting to attach whatever restrictions they choose.
Exactly. And Linus likes GPLv2. As do I.
Quoted 1 line
Sean
Rob
Quoted 6 lines · Linus Torvalds
Quoted 4 lines · Adrian Bunk
Here in Germany, the rules at court are roughly "the loser pays everything including the costs of the winner", so if a big company is sure they will win at court there's no reason not to go there.
Quoted 7 lines
Well, the thing is (and I've said this before), a lawsuit is (and _should_ be) very much a last resort.
I think that the Open Source community (and the FSF too) is much better off *not* concentrating so much on "legal rules" of what can and cannot be done, and instead spend much more effort on showing people why the whole "Open Source" thing actually works.
I'm wondering more and more why you choose the GPL and not the BSD licence for the Linux kernel...
Companies are violating the GPL and this only works as long as noone starts taking legal actions against them.
And taking legal actions easily takes all of your fortune at risk.
Quoted 7 lines
And in fact, I think that's _exactly_ what Linux has been doing for the last decade!
A lot of companies are actually doing the Right Thing (tm).
Not because of anybody "forcing" them, but because they have literally bought into the whole "Open Source can do things better" mentality.
And there are some companies for whom it's better if they can take the open source code and turn it into some closed thing. There's a reason why TiVo warned it's investors that the GPLv3 might hurt their business.
Quoted 3 lines
In fact, the whole "coercive" approach is counter-productive. It makes people dislike you. It makes companies _resist_ open source, rather than see it as a potential ally.
And what are the risk of your allies actions?
Consider e.g. that your ally AMD offers legally questionable non-GPL modules and Debian shipping binaries.
If one of the many copyright holders of the kernel wants to take legal actions against this suing AMD might simply be out of reach due to financial reasons.
But legal actions against the maintainers of ftp.<your_country>.debian.org distributing binaries of these legally questionable modules have a good chance of success.
The legal risks might not be a problem for a big company like AMD, but anyone seeking an easy legal win will _naturally_ attack mirrors.
And considering the lucratice "cease and desist letter" business in Germany, it really seems to be only a matter of time until mirrors will have to pay (the lawyer costs of the ones sending the cease and desist letters) for the actions of your "allies".
Quoted 9 lines
And no, I'm not speaking out of my *ss. Anybody who goes back fifteen years and looks at how the FSF was acting wrt the GPL (v2, back then), and how many friends - and enemies - they were making, should see that as a big clue. Linux really *did* change the landscape - for the better (*). By being much less contrary.
So look at Intel in the open source space. They're doing well. Look at Sun. They aren't _forced_ to open-source, they see others open-sourcing, and they see that it works damn well.
Look at AMD.
Look at NVIDIA.
Will they ever switch from providing illegal modules to open source?
Quoted 9 lines
In the "Tivo space", look at Neuros.
In other words, we're just *much* better off with a friendly license and not trying to force people to choose sides, than with the rabid idealism that was - and still is - the FSF. The FSF always makes for this horrible "you're with us, or you're against us" black-and-white mentality, where there are "evil" companies (Tivo) and "good" companies (although I dunno if the FSF really sees anybody as truly "good").
Quoted 6 lines
I'd much rather just see "individuals" and "companies". They're not evil or good, they are all in it for their own reasons (and their reasons are *NOT* the same reasons they are for me, you, or anybody else), and we should show them that the whole "Open Source" approach really does work for them.
...
Until someone starts to attack ftp mirrors and other people distributing the questionable code.
There are so many copyright holders of the Linux kernel (including e.g. the former Caldera), and if someone wants to spread fear among Linux users legal actions against people maintaining ftp mirrors or selling their old Linux distribution at ebay will be the cheap and effective way to achieve this goal.
Quoted 2 lines
Linus
...
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 3 lines · Adrian Bunk
I'm wondering more and more why you choose the GPL and not the BSD licence for the Linux kernel...
Why do people confuse "anti-GPLv3" with "pro-BSD"?
What's the logic?
The BSD license is not doing tit-for-tat. It doesn't give me anything back. I don't believe in that kind of model. So I'd not use it for my projects.
The GPLv2 has a good balance. It encourages tit-for-tat, and it makes sure that the software is kept free. And it doesn't try to force anything else, or play politics. The only thing you have to believe in is "tit-for-tat".
The GPLv3 goes too far. It's no longer "tit-for-tat", it's "our software is worth _soo_ much, that we want to force you to behave well, or you cannot use it".
I think one of the above licenses are good. The fact that I reject the GPLv3 in _no_ way implies that I should like the BSD license. Both the BSD license and the GPLv3 are flawed - they are just flawed in fundamentally different ways.
So the whole question of "why don't you use he BSD license then" is just fundamentally bogus. A license is about a *balance* of things. "Fairness" is not about laissez-faire (BSD) or about total-control (GPLv3). To me, It's about something in the middle, where people give back in kind.
And btw, that "to me" is important.
Different people have different opinions. That's _fine_. Use the GPLv3 for your projects. Go wild. Use the BSD license. It's your choice.
But by the same token, it was _my_ choice (and it was an informed choice) to use the GPLv2.
And to then come in fifteen years later and call me "confused" about a license I've chosen is a damn affront to me. I'm not confused. Somebody else may be, but it's not me.
Linus
Quoted 1 line · Linus Torvalds
In fact, the whole "coercive" approach is counter-productive.
Let me see if I got your position right: when TiVO imposes restrictions, that's ok, but when others want to find ways to stop it, then it's not. *Now* I'm confused ;-)
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
Let me see if I got your position right: when TiVO imposes restrictions, that's ok
Sure. I think it's ok that Microsoft imposes restrictions too on the software they create. It's *their* choice.
And I think it's ok for you to impose any restrictions (including the ones in GPLv3) on the software *you* produce. It's your choice.
Quoted 2 lines
but when others want to find ways to stop it, then it's not. *Now* I'm confused ;-)
You are indeed totally confused.
It's *ok* to impose restrictions on the stuff you create. Everybody has a different world-view, and for some it's about making money, for some it's about something else, and some don't want any restrictions at all.
For me, the GPLv2 was the license I liked. I didn't like the BSD license, so I didn't choose it. I don't like a license that restricts hardware, so I didn't choose that.
And I *still* don't choose that.
See? I think the GPLv3 is a *much* inferior license to the GPLv2. It's better than its drafts were, but it's still doing things I disagree with.
So tell me, why do you think I'm confused about the GPLv3? Why do you think I should have said "GPLv2 or anything else the FSF comes up with"?
So the only thing I want you to say is:
(a) Linus knows what he is doing, and isn't actually confused.
and
(b) It was my right to use the license of my choice for a project that I started.
and
(c) I have the right to see the difference between the GPLv2 and v3, and think that the GPLv3 is the inferior license.
Comprende? MY CHOICE. Not the FSF's. Not yours. Not anybody elses.
Linus
Quoted 7 lines · Linus Torvalds
Quoted 3 lines · Alexandre Oliva
Let me see if I got your position right: when TiVO imposes restrictions, that's ok
Sure. I think it's ok that Microsoft imposes restrictions too on the software they create. It's *their* choice.
Last I looked, TiVO was not the author of Linux. Did you sell out or something? ;-P :-D
Quoted 1 line
So tell me, why do you think I'm confused about the GPLv3?
I think you're confused about the spirit of the GPL, that applies equally to v1, v2 and v3.
I think you're confused because you claim the GPL is tit-for-tat, that it encourages/requires (you haven't been consistent) contributions in kind, but the only contribution in kind is respect for the freedoms of others. But then, when measures are introduced to ensure compliance with this twisted tit-for-tat notion, you claim they're wrong, that they escape the spirit of the license.
This is why I think you're confused.
That said, it is possible that you disregarded the spirit of the GPL entirely, focused on some of the legal terms and decided that was something you wanted for your project. And that it models what you want for your project better than GPLv3 does, because GPLv3 takes the spirit that you disregarded even more seriously than GPLv2.
I still fail to see why what it is in GPLv2 that makes it better to satisfy your intentions WRT Linux than GPLv3. I must assume that, when you say "tit-for-tat", you mean something else, and not respect for others' freedoms. If you take the time to explain what it is, then perhaps it will become clear why you consider the GPLv2 a better license to achieve your goals, or perhaps it will show that you're indeed confused about what GPLv2 and GPLv3 mean.
Quoted 1 line
(a) Linus knows what he is doing, and isn't actually confused.
I can't say that yet. Maybe after the points above are sufficiently explored I will be able to say that.
Quoted 2 lines
(b) It was my right to use the license of my choice for a project that I started.
No doubt about it.
Quoted 2 lines
(c) I have the right to see the difference between the GPLv2 and v3, and think that the GPLv3 is the inferior license.
You sure do have that right.
Quoted 1 line
Comprende? MY CHOICE. Not the FSF's. Not yours. Not anybody elses.
Until you started accepting contributions from others, yes.
BTW, in Portuguese the correct spelling would be "compreende", with a double 'e'. "Comprende" is Spanish, and in Brazil, where I live, we speak Portuguese. But thanks for trying, that's appreciated ;-)
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
Last I looked, TiVO was not the author of Linux. Did you sell out or something? ;-P :-D
You're a moron.
I'm the original author, and I selected the GPLv2 for Linux.
Tivo accepted that, and followed the GPLv2. Even the FSF lawyers agreed that they followed it.
But Tivo *is* the "author" of their own proprietary applications, and it *is* the designer of their hardware.
And exactly like I had the right to the choice of license when it comes to Linux, they have the right of choice to license and behaviour when it comes to *their* software and hardware (that is not a derived work of Linux).
But you cannot follow a coherent argument, because you dont' *want* to follow it. Because following the logical argument would take you to a place where you don't want to be.
I'm not going to bother discussing this any more. You don't seem to respect my right to choose the license for my own code.
So one final time:
- I chose the GPLv2, fully understanding that the Tivo kind of situation is ok.
- the FSF lawyers too have acknowledged that what Tivo did was not a license violation, so I obviously am not confused about the issue: YOU are.
- I think that what Tivo did was not only "technically valid" by the license, it was what I *intended* by my choice of license!
And you are apparently totally unable to understand - or respect - that I actually made an informed decision that happens to be different from what you *wish* it were.
Linus
Quoted 2 lines · Linus Torvalds
- I chose the GPLv2, fully understanding that the Tivo kind of situation is ok.
Wow, do you remember the date when you first thought of this business model?
Quoted 3 lines
And you are apparently totally unable to understand - or respect - that I actually made an informed decision that happens to be different from what you *wish* it were.
While you insist in the nonsensical tit-for-tat argument and "in kind" retributions, I don't think I have much of a choice, because this is not what the GPL is about, this is not what it requires of licensees.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 2 lines · Linus Torvalds
- I chose the GPLv2, fully understanding that the Tivo kind of situation is ok.
Wow, do you remember the date when you first thought of this business model?
You know what? I'm intelligent. That's what you call people who see th consequences of their actions. I didn't see the *details* of what all the GPLv2 could result in, but yes, I claim that I knew what I was setting myself up for (in a license way) pretty much from the beginning.
Did it take me by surprise how people actually ended up using Linux? It sure did. But has the GPLv2 itself ever surprised me? Not really. I read it back then, and yes, I understood what it meant.
Quoted 1 line
From the very beginning of Linux, even before I chose the GPLv2 as the
license, the thing I cared about was that source code be freely available. That was the first license, but more importantly, it was why I started Linux in the first place - my frustrations with Minix, and my memories of how painful it was to find an OS that I wanted to use and work with.
(That, btw, was not Minix-only: I actually originally was thinking about literally buying a commercial Unix for my PC too. The price factor kept me away from the commercial unixes, and in retrospect I'm obviously very happy).
So my first goal was "source must be available and it must be free (as in beer)". Which my first copyright license reflects very directly.
What happened a few months into the thing was that some people actually wanted to make floppy images of Linux available to Linux users groups, but they didn't want to have to actually *fund* the floppies and their work themselves, so they wanted to sell them at cost (which the first license actually didn't allow!).
And I realized that the money angle really wasn't what I ever really cared about. I cared about availability, but people sure could get paid for their effort in distributing the thing, as long as the source code remained open. I didn't want money, I didn't want hardware, I just wanted the improvements back.
So given that background, which license do you _think_ I should have chosen?
And given that background, do you see why the GPLv2 is _still_ better than the GPLv3? I don't care about the hardware. I'll use it, but it's not what Linux is all about. Linux is about something much bigger than any individual device.
And yeah, maybe I'm just better at abstracting things. Maybe I prefer seeing the big picture, and that the individual devices don't matter. What matters is the improvement in the *software*, because while each physical device is a one-off thing, in the long term, it's the *development* that matters.
And the GPLv2 protects that.
It's a bit like evolution: individual organisms matter to *themselves* and to their immediate neighborhood, but in the end, the individuals will be gone and forgotten, and what remains is the development.
In those terms, I care about the DNA, and the *process* or recombination and the bigger picture. Any individual organism? Not so much. It's all part of a much bigger tapestry, and closed hardware is more like an eunuch (or a worker bee): it won't pass on its legacy, but it might help the people who do.
So instead of thinking of Tivo as something "evil", I think of Tivo as the working bee who will never pass on its genes, but it actually ended up helping the people who *do* pass on their genes: the kernel (to a small degree - not so much because of the patches themselves, as the *mindshare* in the PVR space) and projects like MythTV (again, not so much because of any patches, but because it helped grow peoples understanding of the problem space!).
Let's take another example: BitKeeper. The FSF follower people seem to view BitKeeper as something "evil". To me, BitKeeper was not just a great tool, but it also ended up being something that showed others how things *could* be done. And the world - including the open source world - is a better place for it!
See? In the big picture, individual devices and even projects won't matter. In a hundred years, I'll be long dead, and nobody will care. But in a hundred years, I hope that the "live and let live" open source mentality will still flourish, and maybe "Linux" itself won't live on, but some of the memories and impact may. And *that* is what matters.
A Tivo? It's just a toy. Who cares? It's not important. But source code that evolves? THAT can change the world!
Linus
Quoted 2 lines · Linus Torvalds
From the very beginning of Linux, even before I chose the GPLv2 as the license, the thing I cared about was that source code be freely available.
Ok, the MIT license could get you that. Even public domain could.
Quoted 2 lines
I didn't want money, I didn't want hardware, I just wanted the improvements back.
GPL won't get you that. You want a non-Free Software license.
It will only as long as people play along nicely and perceive the benefits of cooperation. But some players don't.
Quoted 2 lines
So given that background, which license do you _think_ I should have chosen?
I can't morally recommend a non-Free Software license.
Quoted 2 lines
And given that background, do you see why the GPLv2 is _still_ better than the GPLv3?
No. Honestly, I really don't. Even when I try and look at it from your perspective, that you described very beautifully in the rest of the message that I snipped, it's still a mistery to me why you think permitting Tivoization could possibly be advantageous to your project.
What is it in the anti-Tivoization provision that gets you any less improvements back?
If anything, I'd think that, by not permitting TiVO to prohibit users from running modified versions of your code that they don't authorize themselves, these users would do *more* than TiVO alone ever could, and if a fraction of them contributes something back, you're way better off.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 1 line · Alexandre Oliva
Ok, the MIT license could get you that. Even public domain could.
Those would not ensure that the source code stays free.
Quoted 7 lines
Quoted 2 lines
I didn't want money, I didn't want hardware, I just wanted the improvements back.
GPL won't get you that. You want a non-Free Software license.
It will only as long as people play along nicely and perceive the benefits of cooperation. But some players don't.
It seems to work very well in practice though.
Quoted 4 lines
No. Honestly, I really don't. Even when I try and look at it from your perspective, that you described very beautifully in the rest of the message that I snipped, it's still a mistery to me why you think permitting Tivoization could possibly be advantageous to your project.
Perhaps there is no benefit in permitting "Tivoization". But at the same time, perhaps there are benefits in not preventing "Tivoization" in ways that may or may not be foreseen at this time.
Quoted 2 lines
What is it in the anti-Tivoization provision that gets you any less improvements back?
Tivo has provided some code changes and improvements to Linux. If they had been totally unable to use Linux due to the license, they would probably have used vxworks or BSD or something else, and Linux would have gotten nothing back. So the Linux source code improved and other systems using the linux code base got better as a result.
Quoted 5 lines
If anything, I'd think that, by not permitting TiVO to prohibit users from running modified versions of your code that they don't authorize themselves, these users would do *more* than TiVO alone ever could, and if a fraction of them contributes something back, you're way better off.
Users of the Tivo hardware would be able to do more, sure, but then again, actualyl, maybe not. After all if it ran vxworks or bsd, the user still wouldn't be able to do anything about it. The end result is the same. The answer is also still the same: Don't buy a tivo if you want to change what it does, because it doesn't let you do that.
--
Len Sorensen
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines · Linus Torvalds
From the very beginning of Linux, even before I chose the GPLv2 as the license, the thing I cared about was that source code be freely available.
Ok, the MIT license could get you that. Even public domain could.
Why do you bother sending out emails that just show that you cannot read or understand?
I want not just the code *I* write to be freely available. I want the modifications that others release that are based on my code to be freely available too!
That's what the whole "tit-for-tat" thing was all about!
Doyou even understand what "tit-for-tat" means?
Should I use another phrase? Do you understand the phrase "Quid pro quo"? Which is another phrase I've used to explain this over the years.
Quoted 7 lines
Quoted 2 lines
I didn't want money, I didn't want hardware, I just wanted the improvements back.
GPL won't get you that. You want a non-Free Software license.
It will only as long as people play along nicely and perceive the benefits of cooperation. But some players don't.
You are living in some alternate world. The GPLv2 gives me exactly what I looked for.
Yes, people can do improvements in private, and by keeping them private they'll never need to release them to anybody else. Big deal. I don't care. By keeping them private, I never see the end result anyway, so they "don't exist" as far as I'm concerned.
Quoted 4 lines
Quoted 2 lines
And given that background, do you see why the GPLv2 is _still_ better than the GPLv3?
No. Honestly, I really don't.
Yeah. So stop bothering me then. Go cry on somebody elses shoulder. Just accept the fact that I'm a grown person, in full control of my faculties, and that I'm perfectly able to make my own judgements, and that I don't need to follow the FSF blindly.
And it doesn't even matter if you don't understand me. That is, as I've said, _your_ problem. I've done my best to explain to you, but if you are so limited that you cannot understand that other people have other opinions than yours, there really is only so much I can do for you.
Go away.
Linus
Quoted 11 lines · Linus Torvalds
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines · Linus Torvalds
From the very beginning of Linux, even before I chose the GPLv2 as the license, the thing I cared about was that source code be freely available.
Ok, the MIT license could get you that. Even public domain could.
Why do you bother sending out emails that just show that you cannot read or understand?
Because I can't divine what's in your mind, and if you don't make the points you want to make clear, I may very well fail to understand.
Quoted 3 lines
I want not just the code *I* write to be freely available. I want the modifications that others release that are based on my code to be freely available too!
With the exception of those who choose not to distribute their changes. Or who choose to distribute their changes to people who are not willing to share them with you. Fair enough.
Quoted 3 lines
That's what the whole "tit-for-tat" thing was all about!
Doyou even understand what "tit-for-tat" means?
Yes. I even wrote an article about that.
http://fsfla.org/svnwiki/blogs/lxo/draft/gplv3-snowwhite
Quoted 1 line
Should I use another phrase? Do you understand the phrase "Quid pro quo"?
Yes. It's there in the article as well. The difference is basically in attitude. Tit-for-tat is adversarial (equivalent retaliation), whereas Quid pro quo is cooperative (a favor for a favor).
Quoted 1 line
Which is another phrase I've used to explain this over the years.
Yup, I remember that.
Quoted 10 lines
Quoted 7 lines
Quoted 2 lines
I didn't want money, I didn't want hardware, I just wanted the improvements back.
GPL won't get you that. You want a non-Free Software license.
It will only as long as people play along nicely and perceive the benefits of cooperation. But some players don't.
You are living in some alternate world. The GPLv2 gives me exactly what I looked for.
And in what sense the GPLv3 anti-Tivoization clause doesn't?
In what sense does it give you *less* of what you want?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 2 lines
Do you even understand what "tit-for-tat" means?
I don't. Could someone please explain it. Specifically:
1) What is "tat"?
2) How can I get some?
3) Where do I go to trade it in?
DS
Quoted 5 lines
1) What is "tat"?
2) How can I get some?
3) Where do I go to trade it in?
4) is it legal to consume it in my country?
5) should I have a designed driver when I do?
Signature · 3 lines
|_|0|_| |_|_|0| |0|0|0|
Quoted 9 lines · Tomas Neme
Quoted 5 lines
1) What is "tat"?
2) How can I get some?
3) Where do I go to trade it in?
4) is it legal to consume it in my country?
5) should I have a designed driver when I do?
6) Is that allowed to be a binary-only driver or
does it have to come with source code?
Quoted 1 line · Linus Torvalds
I'm the original author, and I selected the GPLv2 for Linux.
[...]
Quoted 2 lines
I'm not going to bother discussing this any more. You don't seem to respect my right to choose the license for my own code.
This is the main reason I dislike GPLwhatever: there is no notion of "orginal author". You might have written 99% of the code, that doesn't matter. You have no rights whatsoever once you release something under the GPL (no more than ANYOne else).
The GPL is nice for the community, and for the users - but very, very bad towards it's authors (taking all and every right you might have). If John Doe wants to re-release the whole kernel under GPLv3, then all he needs is a website and some bandwidth.
Signature · 1 line
Carlo Wood <[email protected]>
Quoted 2 lines
This is the main reason I dislike GPLwhatever: there is no notion of "orginal author". You might have written 99% of the code, that
Every literary work (including thus software) has an author, and that author has certain rights which are implicit in them being author.
Quoted 2 lines
doesn't matter. You have no rights whatsoever once you release something under the GPL (no more than ANYOne else).
Wrong. The author has a collection of rights which vary by jurisdiction but which are primarily governed by the Berne Convention and its sequels notably TRIPS.
Quoted 3 lines
The GPL is nice for the community, and for the users - but very, very bad towards it's authors (taking all and every right you might have). If John Doe wants to re-release the whole kernel under
You must be using a different GPL to the rest of us.
Quoted 1 line
GPLv3, then all he needs is a website and some bandwidth.
And a very good lawyer (oh and a GPL3 as there isn't one yet...)
Alan
Quoted 5 lines · Alan Cox
Quoted 2 lines
This is the main reason I dislike GPLwhatever: there is no notion of "orginal author". You might have written 99% of the code, that
Every literary work (including thus software) has an author, and that author has certain rights which are implicit in them being author.
Like, they can release/sell the whole thing under some arbitrary other license at their choice. But once you license it with the GPLv2, then you can't stop anyone else (who got it under that license) from using the code under that license anymore, as such it doesn't matter that you are the original author.
Quoted 7 lines
Quoted 2 lines
doesn't matter. You have no rights whatsoever once you release something under the GPL (no more than ANYOne else).
Wrong. The author has a collection of rights which vary by jurisdiction but which are primarily governed by the Berne Convention and its sequels notably TRIPS.
Quoted 5 lines
Quoted 3 lines
The GPL is nice for the community, and for the users - but very, very bad towards it's authors (taking all and every right you might have). If John Doe wants to re-release the whole kernel under
You must be using a different GPL to the rest of us.
You actually had me check the license of the linux kernel :p But really - it has this paragraph that I was refering to in most of it's source files:
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
I might be wrong, but I always thought that that meant that John Doe is free to redistribute the software under version 3 of the License, as published by the FSF.
There are source files in the kernel without this phrase, ie - they just say: * This file is released under the GPL.
But then the paragraph from COPYING kicks in, reading:
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
Any, 'any version' probably includes version 3 as well.
Finally, there are file that don't mention the GPL at all, for example kernel/sys.c just says:
* Copyright (C) 1991, 1992 Linus Torvalds
But - if it weren't GPL-ed then that would be a violation of the GPL-ed of the rest (Nevertheless, I think the license header should be added to those files).
Quoted 3 lines
Quoted 1 line
GPLv3, then all he needs is a website and some bandwidth.
And a very good lawyer (oh and a GPL3 as there isn't one yet...)
I really don't like license discussions - and after reading in the mailinglist FAQ that license posts are taboo here - I was partly annoyed, partly amazed to see this HUGE flood of mails with as subject line "Dual-Licensing Linux Kernel with GPL V2 and GPL V3"
I am sorry that I drew the apparently wrong conclusion that GPL V3 is a pressing reality.
Quoted 1 line
Alan
Signature · 1 line
Carlo Wood <[email protected]>
Quoted 5 lines
Like, they can release/sell the whole thing under some arbitrary other license at their choice. But once you license it with the GPLv2, then you can't stop anyone else (who got it under that license) from using the code under that license anymore, as such it doesn't matter that you are the original author.
This is true of most licences. Ask musicians about trying to get their music back from a record company.
Quoted 8 lines
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.I might be wrong, but I always thought that that meant that John Doe is free to redistribute the software under version 3 of the License, as published by the FSF.
For those marked parts yes - thats the authors choice. Some of the kernel is dual licensed BSD even so you can use that bit for all sorts of stuff. Again authors choice, some authors wanted to share code between Linux and other projects. I believe you can buy proprietary licenses to reiserfs too.
Some authors like GPLv2 or later, some don't trust the FSF, some will decide once GPLv3 is out, some couldn't care etc.. as the kernel doesn't do copyright assignment all these wishes are respected and that is how it should be.
Alan
Quoted 2 lines · Carlo Wood
But then the paragraph from COPYING kicks in, reading:
Read the COPYING file more closely, and realize that "the Program" has always specified a version number of this license.
It used to include it just by virtue of having the COPYING file *itself* be included (and that's v2), but since some people felt that was unclear, the COPYING file has this language pretty visibly at the top:
Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.
Quoted 1 line
Any, 'any version' probably includes version 3 as well.
Not for the kernel. Exactly because the kernel _does_ specify the version. So the sequence you quoted is a non-issue.
In other words: any file that does not *explicitly* say that it's "v2 or later" is v2 only.
Linus
Quoted 10 lines · Carlo Wood
Quoted 1 line · Linus Torvalds
I'm the original author, and I selected the GPLv2 for Linux.
[...]
Quoted 2 lines
I'm not going to bother discussing this any more. You don't seem to respect my right to choose the license for my own code.
This is the main reason I dislike GPLwhatever: there is no notion of "orginal author". You might have written 99% of the code, that doesn't matter. You have no rights whatsoever once you release something under the GPL (no more than ANYOne else).
You retain the copyright, and in particular the right to relicense. Only if you make the mistake of including the "or any later version" phrase do you allow others to redistribute the work under a different version of the GPL. Although this provision may seem slightly convenient to authors, its effect is to grant a very large amount of relicensing permission to the FSF. It almost certainly doesn't make sense to place that much trust in a single organization.
Quoted 4 lines
The GPL is nice for the community, and for the users - but very, very bad towards it's authors (taking all and every right you might have). If John Doe wants to re-release the whole kernel under GPLv3, then all he needs is a website and some bandwidth.
Well, he also needs one tiny little extra thing: the permission of every copyright holder in Linux.
Signature · 1 line
Jeremy Maitin-Shepard
Quoted 5 lines · On Thursday 14 June 2007 19:18:12 Carlo Wood wrote:
Quoted 1 line · Linus Torvalds
I'm the original author, and I selected the GPLv2 for Linux.
[...]
Quoted 7 lines
Quoted 2 lines
I'm not going to bother discussing this any more. You don't seem to respect my right to choose the license for my own code.
This is the main reason I dislike GPLwhatever: there is no notion of "orginal author". You might have written 99% of the code, that doesn't matter. You have no rights whatsoever once you release something under the GPL (no more than ANYOne else).
You mean if the original author gets hit by a bus and their estate gets sold to SCO they can't revoke our rights to the code? How is this a down side?
And you do have more rights than anyone else: as the copyright holder you can issue other licenses, and you have standing to sue to enforce the code. (If nobody else has a copyright on the code, they don't have standing to sue to enforce the license terms.)
(Right now, nobody EXCEPT the FSF has the right to sue somebody to enforce the license terms on something like gcc. Do you find that a comforting thought?)
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 3 lines · Rob Landley
(Right now, nobody EXCEPT the FSF has the right to sue somebody to enforce the license terms on something like gcc. Do you find that a comforting thought?)
Have you ever signed a copyright transfer agreement to the FSF? Obviously not, because then you wouldn't utter such nonsense. The agreement reads that you transfer a non-exclusive right to the FSF to distribute the code under GPL (versions of your choice, they have this right anyway, but making it explicit is always good), and the right to enforce the license. You still have the right to relicense the work as you like. You also have the right to enforce the license yourself, or to transfer that right to somebody else like gpl-violations.org. The FSF even doesn't require to transfer copyright if you make a GNU project, but if you don't, the FSF won't help you (because they can't).
They make very obvious promises about what they care ("four freedoms"), and that they will be very consistent in doing so. So far, all track records have proven that they indeed are very consistent in doing so - the main controversy here is not whether the FSF protects the "four freedoms", but whether these four freedoms are the right goal, and if they really should try so hard to protect these four freedoms. This part of the discussion is fully acceptable, what's not acceptable is that the Linus-fancurve claims things the GPL sais which it doesn't (like "tit-for-tat") or doesn't say which it does (like section 6 - direct license from the licensor, and in cases like Linux where no copyright transfer agreements whatsoever exist, these are the individual contributors). Or that Linux 0.something was already under GPLv2 only, when GPLv2 clearly says that there may be updates, and when you as author don't say something, you are allowing users to update if they like.
The last point IMHO makes clear that my interpretation of the comment is
valid: This is a commend made by Linus Torvalds, as how he understands or misunderstands the license text. It's not even something you can take as legal advice, because Linus is not a lawyer (fortunately - think how the kernel would look like if it was programmed by a lawyer ;-).
Sure, if you as outsider strip the kernel of obvious GPLv2-only code to relicense it as a whole under GPLv3, you need a good asbestos suite, a good lawyer, and good arguments. But let's assume Microsoft really succeeds with its patent FUD against Linux, and the only way out is GPLv3, when will opinions here change?
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 6 lines · On Friday 15 June 2007 07:57:10 Bernd Paysan wrote:
Quoted 3 lines · Rob Landley
(Right now, nobody EXCEPT the FSF has the right to sue somebody to enforce the license terms on something like gcc. Do you find that a comforting thought?)
Have you ever signed a copyright transfer agreement to the FSF?
Nope, and I probably never will, but I'm glad to be wrong about this one.
Quoted 3 lines
But let's assume Microsoft really succeeds with
its patent FUD against Linux, and the only way out is GPLv3, when will opinions here change?
Ever heard of the Open Invention Network or the Software Freedom Law Center?
And since when did the FSF become an ally of Microsoft? The rest of us seem to think the Novell deal's a minefield under GPLv2, and would just LOVE Microsoft to reopen the antitrust can of worms by suing somebody over Linux (they're still a convicted predatory monopolist, only the sentence part was defused)...
And yet GPLv3 was DOA until the Novell deal happened and suddenly the FSF had this huge thing. Reminds me of everybody rallying behind Bush after
September 11 to support abominations like the Patriot Act. It's sad how
fear makes people stop thinking.
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 11 lines · Bernd Paysan
Have you ever signed a copyright transfer agreement to the FSF? Obviously not, because then you wouldn't utter such nonsense. The agreement reads that you transfer a non-exclusive right to the FSF to distribute the code under GPL (versions of your choice, they have this right anyway, but making it explicit is always good), and the right to enforce the license. You still have the right to relicense the work as you like. You also have the right to enforce the license yourself, or to transfer that right to somebody else like gpl-violations.org. The FSF even doesn't require to transfer copyright if you make a GNU project, but if you don't, the FSF won't help you (because they can't).
Quoted 14 lines
They make very obvious promises about what they care ("four freedoms"), and that they will be very consistent in doing so. So far, all track records have proven that they indeed are very consistent in doing so - the main controversy here is not whether the FSF protects the "four freedoms", but whether these four freedoms are the right goal, and if they really should try so hard to protect these four freedoms. This part of the discussion is fully acceptable, what's not acceptable is that the Linus-fancurve claims things the GPL sais which it doesn't (like "tit-for-tat") or doesn't say which it does (like section 6 - direct license from the licensor, and in cases like Linux where no copyright transfer agreements whatsoever exist, these are the individual contributors). Or that Linux 0.something was already under GPLv2 only, when GPLv2 clearly says that there may be updates, and when you as author don't say something, you are allowing users to update if they like.
So if Linus wasn't entirely clear to begin with that he wanted GPLv2 only, then that is just too bad? Well why not then say that if the GPLv2 didn't say that what Tivo did was bad, then too bad, you can't change your mind later. The FSF can't have it both ways.
Quoted 11 lines
The last point IMHO makes clear that my interpretation of the comment is
valid: This is a commend made by Linus Torvalds, as how he understands or misunderstands the license text. It's not even something you can take as legal advice, because Linus is not a lawyer (fortunately - think how the kernel would look like if it was programmed by a lawyer ;-).Sure, if you as outsider strip the kernel of obvious GPLv2-only code to relicense it as a whole under GPLv3, you need a good asbestos suite, a good lawyer, and good arguments. But let's assume Microsoft really succeeds with its patent FUD against Linux, and the only way out is GPLv3, when will opinions here change?
No the GPLv3 is not the only solution. Perhaps a GPLv2.1 that is actually in the spirit of the VPLv2 with just enough changes to fix the real problems, that may in fact be a solution. The GPLv3 is very much not the only solution. A totally different kernel specific license may even be an option. There are many options, most of them just happen to be pretty hard.
--
Len Sorensen
Quoted 4 lines · Lennart Sorensen
So if Linus wasn't entirely clear to begin with that he wanted GPLv2 only, then that is just too bad? Well why not then say that if the GPLv2 didn't say that what Tivo did was bad, then too bad, you can't change your mind later. The FSF can't have it both ways.
Of course they can - as any politician. What, do you really think that Bernd wakes up, looks in a mirror and spits in disgust? I very much doubt that.
Here's how that kind of stuff works: to be a successful politician one needs to have ideals. The more, the better. Then there always will be an ideal advanced by action one wants to take. Experienced politician is one that will be able to pick those automatically. And feel damn righteous at that.
Of course they can have it both ways - just say something like "we work for the greater good of users", "what advances our goals helps the interests of users", "we'll read both cases in a way that helps the interests of users", "we are consistent in helping the interests of users". And at that point any talk of inconsistencies will be deflected by the highly moral considerations. End of story. Sprinkle with generic constructs making the critics easier to ignore ("they do it because they are Bad"/"they do it because they had been seduced by Evil"/ "they just parrot somebody"/"they do it because of <random psychobubble>"/ "they do it because of wrong ideology"/"they do it because of ego") and enjoy.
Quoted 3 lines · Alexandre Oliva
Let me see if I got your position right: when TiVO imposes restrictions, that's ok, but when others want to find ways to stop it, then it's not. *Now* I'm confused ;-)
Me, I agree that hardware shouldn't lock users. And since I'm one of those evil european socialdemocrats, I may go as far as to think that there should be laws that *forbid* selling such hardware.
But I think that all this iss a *hardware* issue. It seems to me that lot of people at the FSF wants to regulate the hardware industry using the influence of free/open software in the computing industry and the "V2 or later" phrase from the GPL.
But the fact is that free/open source runs on _top_ of hardware. You don't control hardware, you only control the things that are built on top of your software, not the parts you use to build your software.
And the FSF is trying to control the design and licensing of hardware throught the influence of their software. And I think it's wrong. I'm all to forbid hardware that imposes restrictions on hardware, but software licenses are NOT the way to make it. That's a task for a "Free Hardware Foundation", not the FSF.
What the FSF is trying to do is EVIL. It's not about free software, it's not about freedom, it's about the FSF trying to have to much control over things that they shouldn't even try to control. I think that the FSF can do a terrible damage to free/open source with such stupid ideas. I wouldn't even be surprised that some jugde rules that a software license that tries to 'control' hardware is invalid
Quoted 5 lines · Diego Calleja
And the FSF is trying to control the design and licensing of hardware throught the influence of their software. And I think it's wrong. I'm all to forbid hardware that imposes restrictions on hardware, but software licenses are NOT the way to make it. That's a task for a "Free Hardware Foundation", not the FSF.
Amen. And btw, opencores.org does actually exist.
I don't even think open hardware is a big issue: the worry-warts about hardware are likely wrong, and hardware today is a lot more open than it used to be even just a decade ago. You can much more easily design your own (FPGA's are cheap and powerful), and yes, it's more complex today, but that's actually an argument _for_ openness rather than against it (open processes work better in complex environments!).
The real issue is "open content", and we do actually have various organizations that support that in particular. I would heartily encourage people to get involved with the Creative Commons, and the EFF, and I think Larry Lessig is a really smart and articulate person, who you should listen to.
Quoted 1 line
What the FSF is trying to do is EVIL.
I wouldn't go that far (although, in the heat of the moment I probably _have_ gone that far. Oops ;).
I don't think the FSF is evil. They're just too single-minded, and look too much at one issue, and only care about the one thing they care about, and in the process, they tend to have a really hard time seeing the other side of the coin.
They define "freedom" one way, and by defining it in a very particular way, they miss the fact that what is "freedom" to them is not "freedom" to somebody else.
They have a very particular agenda, and in having that agenda and a very strict view of how the world should look (according to the FSF), they dismiss the fact that other people have _other_ agenda's, and see the same world totally differently.
And I think that kind of single-mindedness is silly and counter-productive.
I literally think that the GPLv2 has worked so well exactly because you can strip it of its high-falutin' morality and the FSF Kool-Aid, and just see it as a "tit-for-tat" license. It allows everybody to see that the work they put in (into the _software_) is protected, and people cannot make improved versions of that software and distribute those improved versions without giving you the right back to use those improvements (to the _software_).
So the GPLv2 may have come out of a very single-minded endeavor, but I think it ended up being capable of so much more than rms really even envisioned, exactly because you don't have to _view_ it in that manner.
Linus
Quoted 4 lines · Linus Torvalds
Quoted 2 lines · Diego Calleja
And the FSF is trying to control the design and licensing of hardware throught the influence of their software.
It's not. It's only working to ensure recipients of the Free Software can modify and share the software.
Quoted 4 lines
Quoted 1 line
What the FSF is trying to do is EVIL.
I wouldn't go that far (although, in the heat of the moment I probably _have_ gone that far. Oops ;).
:-)
Quoted 7 lines
I literally think that the GPLv2 has worked so well exactly because you can strip it of its high-falutin' morality and the FSF Kool-Aid, and just see it as a "tit-for-tat" license. It allows everybody to see that the work they put in (into the _software_) is protected, and people cannot make improved versions of that software and distribute those improved versions without giving you the right back to use those improvements (to the _software_).
Can you explain to me how it is that the Tivoization provisions (the only objection you have to GPLv3) conflict with this?
(nevermind our disagreement as to whether "tit-for-tat" applies to
either GPLv2 or GPLv3)
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines
Can you explain to me how it is that the Tivoization provisions (the only objection you have to GPLv3) conflict with this?
Is it really that hard to understand? GPLv2 applied only to works people chose to place under that license or to works that contain so much code that someone chose to place under that license that they are legally considered a derivative work. GPLv3, on the other hand, attempts to extend control over works that don't contain any code that anyone ever chose to place under the GPL.
This is a night and day difference.
The GPLv2 stands within the legal scope of copyright. If I create a work, I have some rights to control that work. If you create a work *based* *on* *my* *work* I can retain some rights over how this new work is used because it actually *contains* parts of my work in it.
The GPLv2 makes no attempt to exercise any control over anything else. The GPLv3, however, attempts to leverage copyright control to restrict what can be done with things completely outside the covered works.
DS
Quoted 7 lines · On Thursday 14 June 2007 21:55:09 Alexandre Oliva wrote:
Quoted 3 lines · Linus Torvalds
Quoted 2 lines · Diego Calleja
And the FSF is trying to control the design and licensing of hardware throught the influence of their software.
It's not. It's only working to ensure recipients of the Free Software can modify and share the software.
^^^^^
Exactly what has been said to you the whole time, but you still refuse to accept that. If Linus develops and runs his code on a PowerPC and I struggle to install the code that he has released for me to modify and share on a PowerPC (maybe because I'm an idiot). Should I create a license with a Linusation term, because he is evil he runs his code on a PowerPC and I can't?
Quoted 8 lines · Bongani Hlope
Quoted 7 lines · On Thursday 14 June 2007 21:55:09 Alexandre Oliva wrote:
Quoted 3 lines · Linus Torvalds
Quoted 2 lines · Diego Calleja
And the FSF is trying to control the design and licensing of hardware throught the influence of their software.
It's not. It's only working to ensure recipients of the Free Software can modify and share the software.
Quoted 7 lines
^^^^^Exactly what has been said to you the whole time, but you still refuse to accept that. If Linus develops and runs his code on a PowerPC and I struggle to install the code that he has released for me to modify and share on a PowerPC (maybe because I'm an idiot). Should I create a license with a Linusation term, because he is evil he runs his code on a PowerPC and I can't?
Depends. In this hypothetical scenario, what did he do to stop you from installing and running the modified version (or even the pristine version, merely recompiled) in your PowerPC? And why did he do it?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 7 lines · Alexandre Oliva
Quoted 4 lines · Diego Calleja
Quoted 3 lines
And the FSF is trying to control the design and licensing of hardware throught the influence of their software.
It's not. It's only working to ensure recipients of the Free Software can modify and share the software.
Those may be the intentions, but I claim that your statement is false. The anti-tivoisation FSF movement is not "working to ensure recipients of the Free Software can modify and share the software".
They can't, because the fact is that hardware vendors can NOT stop you from "modifing and sharing the software". They only can stop you from running your modifications, which is very different. So this is a _hardware_ limitation. It's pointless to try to address this problem with software licenses.
What the anti-tivoisation movement is trying to do: "If you are a vendor of tivoized hardware you must give your users whatever information is needed to run modifications of their software"
How it works in the real world: "You can't run this software in hardware that doesn't allow to run code modifications of this software"
So while the anti-tivoisation movement is trying to limit hardware design/licensing, the fact is that what you are restricting is not the hardware, but the _software_, in a way very different from the 'restrictions' that the GPL has when compared with the BSD ie: in a way that doesn't benefit freedom or contribution of code. Because your users already can modify and share their code regardless of what hardware they're using (even if they can't run their modifications), you're just adding pointless prohibitions.
Quoted 1 line · Linus Torvalds
It's totally pointless to try to "force" people to be good. That's like "curing" gay people. Not going to happen.
Tangent, but that could in fact quite easily be construed as saying that gay people aren't good which I hope is not the point you are making :-/
Rene.
Quoted 7 lines · Rene Herman
Quoted 2 lines · Linus Torvalds
It's totally pointless to try to "force" people to be good. That's like "curing" gay people. Not going to happen.
Tangent, but that could in fact quite easily be construed as saying that gay people aren't good which I hope is not the point you are making :-/
I certainly read that as 'trying to force people to be good is just as crazy as trying to force people to not be gay'. Some people are good, and some aren't (no idea why), and similarly some people are gay and some aren't (again, no idea why). Neither can be changed by declaring that it must be changed.
I always love Linus' analogies. :)
--
Len Sorensen
Quoted 9 lines · Lennart Sorensen
Quoted 7 lines · Rene Herman
Quoted 1 line · Linus Torvalds
It's totally pointless to try to "force" people to be good. That's like "curing" gay people. Not going to happen.
Tangent, but that could in fact quite easily be construed as saying that gay people aren't good which I hope is not the point you are making :-/
Quoted 5 lines
I certainly read that as 'trying to force people to be good is just as crazy as trying to force people to not be gay'. Some people are good, and some aren't (no idea why), and similarly some people are gay and some aren't (again, no idea why). Neither can be changed by declaring that it must be changed.
Yes, just my sense of humour, I'm afraid... ;-)
Rene.
Quoted 27 lines · On Thursday 14 June 2007 11:20:34 Adrian Bunk wrote:
Quoted 14 lines · On Thu, Jun 14, 2007 at 12:00:17AM -0400, [email protected] wrote:
Quoted 4 lines · Adrian Bunk
Reality check:
Harald convinced companies that they have to provide the private keys required to run the Linux kernel they ship on their hardware.
No, the *real* reality check:
The operative words here are "convinced companies" - as opposed to "convinced a judge to rule that private keys are required to be disclosed". (I just checked around on gpl-violations.org, and I don't see any news items that say they actually generated citable case law on the topic of keys...)
Quoted 7 lines
Harald convinced companies that it was easier/cheaper/faster to provide the private keys than to continue in a long legal battle with an uncertain outcome. If the company estimates the total loss due to keys being released is US$100K, but the costs of taking it to court are estimated at US$200K, it's obviously a win (lesser loss, actually) for the company to just fold.
...Here in Germany, the rules at court are roughly "the loser pays everything including the costs of the winner", so if a big company is sure they will win at court there's no reason not to go there.
Quoted 6 lines
And if they did the effort of using private keys to only allow running an official firmware, they must have seen an advantage from doing so.
I'm not saying it legally clear the other way round, my statement was an answer to Daniel's emails claiming it was clear what such companies do was legal.
I'm sorry if I gave anyone that impression. My point was that it would be pointless to argue the case in the US because here it really is, usually , "buy the best justice for the money".
DRH
Quoted 2 lines
cu
Adrian
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 7 lines · On Thursday 14 June 2007 15:49:13 Daniel Hazelton wrote:
Quoted 3 lines
I'm not saying it legally clear the other way round, my statement was an answer to Daniel's emails claiming it was clear what such companies do was legal.
I'm sorry if I gave anyone that impression. My point was that it would be pointless to argue the case in the US because here it really is, usually , "buy the best justice for the money".
Or do what BusyBox and uClibc did (on the advice of Pamela Jones of Groklaw) and sign up with the the Software Freedom Law Center so they can enforce your copyrights for you.
Didn't cost us a dime, and they were ok with GPLv2 without the "or later" clause...
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 3 lines · Daniel Hazelton
Either a device is distributed, like the common PC, that is designed for the user to change and update the software on, or, like the PS2 it isn't designed for that.
Have you ever installed GNU/Linux on a PC "Designed for Microsoft Windows"?
How dare you? ;-)
Quoted 5 lines
If, OTOH, the hardware was never meant for the end-user to install custom versions of the software on, then while the signing keys are still *technically* part of the source, in practice they are not. Why? Because in most of those cases the end-user isn't granted the right to install and run custom binaries on the hardware.
And distributing the GPLed software under this restriction is quite likely copyright infringement.
Quoted 2 lines
I know this. As I said, I doubt that anyone who tried this in America would have the success he has had.
Quoted 2 lines · On Wednesday 13 June 2007 21:24:01 Adrian Bunk wrote:
Quoted 2 lines
Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs?
;-) :-P :-D
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 6 lines · Daniel Hazelton
Nope. Merely stating a distinction. Either a device is distributed, like the common PC, that is designed for the user to change and update the software on, or, like the PS2 it isn't designed for that. If I find a way to update my PS2 to run Linux and find that it doesn't want to start the "Linux Firmware" because I'm lacking a signing key...
Quoted 6 lines
In the case of a device that internally runs Linux (or any other GPL'd software) and wasn't designed for the end-user to change the software running on it then the signing keys aren't part of the source. OTOH, if I sell a PC running Linux that requires the kernel be signed then the signing keys *are* part of the source, since a PC is designed for the end-user to change the software running on it.
Come on, GPL is software licence, the hardware isn't part of the equation. One can argue that keys are or aren't part of the source (= that digital signature is or isn't part of the executable) but it's totally independent of any hardware and its purpose.
For example, it doesn't matter if the signature is merely for checking file integrity (and any signature would do) or if it's for restricting users from running something.
Signature · 1 line
Krzysztof Halasa
Quoted 3 lines · Adrian Bunk
Harald is in Germany, and he therefore takes legal action against people distributing products violating his copyright on the Linux kernel in Germany at German courts based on German laws.
And if Tivo did sell their crap in Germany, I bet, Harald had brought them down years ago (as he did in the "tivoized" Siemens router case). But Tivo doesn't (they started in the UK, and stopped doing so right after Harald unlocked that Siemens router ;-), and in the US, courts may think different. Or they rely that there simply is no Harald Welte in the US, who goes after the violators.
Signature · 3 lines
Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Quoted 11 lines · On Thursday 14 June 2007 05:32:47 Bernd Paysan wrote:
Quoted 3 lines · Adrian Bunk
Harald is in Germany, and he therefore takes legal action against people distributing products violating his copyright on the Linux kernel in Germany at German courts based on German laws.
And if Tivo did sell their crap in Germany, I bet, Harald had brought them down years ago (as he did in the "tivoized" Siemens router case). But Tivo doesn't (they started in the UK, and stopped doing so right after Harald unlocked that Siemens router ;-), and in the US, courts may think different. Or they rely that there simply is no Harald Welte in the US, who goes after the violators.
On http://www.busybox.net the March 26, 2006 entry reads:
Quoted 9 lines
27 March 2006 -- Software Freedom Law Center representing BusyBox and uClibc One issue Erik Andersen wanted to resolve when handing off BusyBox maintainership to Rob Landley was license enforcement. BusyBox and uClibc's existing license enforcement efforts (pro-bono representation by Erik's father's law firm, and the Hall of Shame), haven't scaled to match the popularity of the projects. So we put our heads together and did the obvious thing: ask Pamela Jones of Groklaw for suggestions. She referred us to the fine folks at softwarefreedom.org.
Quoted 5 lines
As a result, we're pleased to
announce that the Software Freedom Law Center has agreed to represent BusyBox and uClibc. We join a number of other free and open source software projects (such as X.org, Wine, and Plone in being represented by a fairly cool bunch of lawyers, which is not a phrase you get to use every day.
See also the September 29, 2006 entry where we set up an email address to forward license violation reports directly to them so we wouldn't have to deal with any of it.
I'd say this "hasn't cost me a dime", but I believe I'm on my third stamp.
(I also note that I'm not busybox maintainer anymore and Erik isn't uclibc maintainer anymore either, but since it's our copyrights they're basing the enforcement actions on, they still bounce an email off us every few months.)
Rob
Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Quoted 2 lines
I haven't looked into what Harald Welte did, but I'd be surprised if someone tried following suit in America and had as much success.
One of the distinct advantages of German law over the US system (and to a large extent the UK system its based upon) is that German law favours justice over money.
Quoted 4 lines
Quoted 2 lines
AFAIK there haven't been any court rulings on this issue, and it could even be that courts in different countries will decide differently.
Agreed.
That in theory shouldn't happen as the conventions on copyright are supposed to stop that mess occuring.
Quoted 8 lines · Alan Cox
...
Quoted 4 lines
Quoted 2 lines
AFAIK there haven't been any court rulings on this issue, and it could even be that courts in different countries will decide differently.
Agreed.
That in theory shouldn't happen as the conventions on copyright are supposed to stop that mess occuring.
Is there any way how this would be resolved?
I can easily imagine that two courts, no matter whether they are in the same or different countries, would decide differently in grey areas like non-GPL modules or the GPLv2 and private keys.
If the two courts are in the same country there's usually a higher court above both that can resolve this. But what if let's say the highest court in the USA and the highest court in Germany would disagree on such a matter?
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 4 lines · Adrian Bunk
If the two courts are in the same country there's usually a higher court above both that can resolve this. But what if let's say the highest court in the USA and the highest court in Germany would disagree on such a matter?
Upgrade the license so as to provide guidance as to the intent of the authors, such that the disagreement doesn't happen again.
If there's room in each country's laws to fix the problem, that is.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 11 lines · Alexandre Oliva
Quoted 4 lines · Adrian Bunk
If the two courts are in the same country there's usually a higher court above both that can resolve this. But what if let's say the highest court in the USA and the highest court in Germany would disagree on such a matter?
Upgrade the license so as to provide guidance as to the intent of the authors, such that the disagreement doesn't happen again.
If there's room in each country's laws to fix the problem, that is.
I don't think that's an option.
Consider the question of whether non-GPL kernel modules are legal at all and the number and different opinions of Linux kernel authors.
Plus the general question whether any "upgrade the license" would be valid in all jurisdictions ("GPL version 2 or any later version" as licence might make it possible, but in all other cases I'd have serious doubts).
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 4 lines
If the two courts are in the same country there's usually a higher court above both that can resolve this. But what if let's say the highest court in the USA and the highest court in Germany would disagree on such a matter?
It would be very unusual for both cases to proceed in parallel. The one court will then strongly consider the decision of the other.
Quoted 7 lines · Adrian Bunk
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys.
No. That's the question as the FSF would like to frame it.
But the real fact is that it *not* the right question.
You can install Linux on a Tivo all you like. Take out the harddisk, install your own version of Linux on it, and put it back in. That's pretty much how Tivo installs Linux on the things too, afaik, although they don't need to take the disk out (since they just assemble it).
No magic needed. In fact, no keys needed.
Now, maybe the hardware/firmware knows to expect a certain SHA1 on that disk, that's a different issue. Tivo could even tell you exactly what the SHA1 they are checking is. Maybe they have a list of SHA1's, and maybe they have a way to upgrade THEIR OWN FIRMWARE with new SHA1's, and they could still tell you all of them, and be very open.
And you could actually replace their copy of Linux with another one. It would have to have the same SHA1 to actually start _running_, but that's the hardware's choice.
See? No private keys needed. No magic install scripts. It really _is_ that easy.
Of course, using private keys, and signing the image with them is possibly a technically more flexible/easier/more obvious way to do it, but in the end, do you really want to argue technical details?
But I think the whole thing is totally misguided, because the fact is, the GPLv2 doesn't talk about "in place" or "on the same hardware".
So take another example: I obviously distribute code that is copyrighted by others under the GPLv2. Do I follow the GPLv2? I sure as hell do! But do I give you the same rights as I have to modify the copy on master.kernel.org as I have? I sure as hell DO NOT!
So by the idiotic logic of "modifying in place", I'm violating the GPLv2 every time I'm makign a release - because I make Linux available, but I don't actually give people the "same rights" to that particular copy that I have! Oh horrors of horrors! You need to make a _copy_ of the thing I distribute, and then you have the same rights I have to that _copy_, but you never had the same rights to the thing I actually distributed!
And here's a big clue for people: anybody who thinks that I'm violating the GPLv2 by not giving out my private SSH key to master.kernel.org is a f*cking moron! You have the right to modify *copies* of the kernel I distribute, but you cannot actually modify the _actual_ entity that I made available!
See any parallels here? Any parallel to a CD-ROM distribution, or a Tivo distribution? The rights that the GPLv2 gives to "the software", is to something much bigger than "the particular copy of the software".
Can people really not see the difference between "the software" and "a particular encoded copy of the software"?
I'm sorry, but people who cannot see that difference are just stupid.
Linus
Quoted 10 lines · Linus Torvalds
Quoted 7 lines · Adrian Bunk
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys.
No. That's the question as the FSF would like to frame it.
No. The FSF actually does *not* want to take this position. That's why it chose the formulation of Installation Instructions. It doesn't share my view that the keys needed to sign a binary in order for it to work are part of the source code.
Quoted 3 lines
And you could actually replace their copy of Linux with another one. It would have to have the same SHA1 to actually start _running_, but that's the hardware's choice.
That's the hardware imposing a restriction on modification of the software. It doesn't matter how elaborate the excuse is to justify denying users' freedoms: it's against the spirit of the GPL, and the GPL will be amended as needed to plug such holes.
Quoted 4 lines
So take another example: I obviously distribute code that is copyrighted by others under the GPLv2. Do I follow the GPLv2? I sure as hell do! But do I give you the same rights as I have to modify the copy on master.kernel.org as I have? I sure as hell DO NOT!
That's an interesting argument.
People don't get your copy, so they're not entitled to anything about it.
When they download the software, they get another copy, and they have a right to modify that copy.
Quoted 3 lines
And here's a big clue for people: anybody who thinks that I'm violating the GPLv2 by not giving out my private SSH key to master.kernel.org is a f*cking moron!
Agreed, except I'd probably use a lighter term.
Quoted 2 lines
See any parallels here? Any parallel to a CD-ROM distribution, or a Tivo distribution?
Yes. You see how TiVO is different? It is modifyable, and I actually receive the copy that TiVO can still modify, but I can't.
Quoted 2 lines
The rights that the GPLv2 gives to "the software", is to something much bigger than "the particular copy of the software".
Indeed, it's something bigger. But this doesn't exclude the smaller things, does it?
Quoted 2 lines
Can people really not see the difference between "the software" and "a particular encoded copy of the software"?
There is a difference. But the GPL doesn't limit itself to the former. It explicitly talks about "copies".
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 16 lines · On Thursday 14 June 2007 02:36:12 Alexandre Oliva wrote:
Quoted 9 lines · Linus Torvalds
Quoted 6 lines · Adrian Bunk
"For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable."
The question is whether this includes private keys.
No. That's the question as the FSF would like to frame it.
No. The FSF actually does *not* want to take this position. That's why it chose the formulation of Installation Instructions. It doesn't share my view that the keys needed to sign a binary in order for it to work are part of the source code.
Quoted 8 lines
Quoted 3 lines
And you could actually replace their copy of Linux with another one. It would have to have the same SHA1 to actually start _running_, but that's the hardware's choice.
That's the hardware imposing a restriction on modification of the software. It doesn't matter how elaborate the excuse is to justify denying users' freedoms: it's against the spirit of the GPL, and the GPL will be amended as needed to plug such holes.
And? There is *absolutely* *nothing* in any version of the GPL *prior* to 3 that says that hardware cannot impose restrictions. What the GPL *does* say is that you can't "add additional restrictions to the license" - (IMHO) a piece of hardware having a restriction isn't an "additional restriction added to the license". As well, as Linus stated, there is nothing *anywhere* - AFAICT, not even in GPLv3 - that says that you have to be able to run the software "in place" or "on the same hardware".
If a hardware manufacturer - like TiVO - uses GPL'd code in their product - and complies with the terms of the license - they aren't required to allow you to run modified code on that hardware. Without it mentioned anywhere in the GPL *OR* the assorted writings of RMS (who founded the FSF and wrote the original GPL) that "modified software must be able to run on the same hardware" then it cannot be in the "spirit" of the license to allow this.
Quoted 5 lines
Quoted 4 lines
So take another example: I obviously distribute code that is copyrighted by others under the GPLv2. Do I follow the GPLv2? I sure as hell do! But do I give you the same rights as I have to modify the copy on master.kernel.org as I have? I sure as hell DO NOT!
Quoted 7 lines
That's an interesting argument.
People don't get your copy, so they're not entitled to anything about it.
When they download the software, they get another copy, and they have a right to modify that copy.
But you get the TiVO corporations copy of the software? I smell a logical fallacy here, but can't remember the name for it.
Quoted 11 lines
Quoted 3 lines
And here's a big clue for people: anybody who thinks that I'm violating the GPLv2 by not giving out my private SSH key to master.kernel.org is a f*cking moron!
Agreed, except I'd probably use a lighter term.
Quoted 2 lines
See any parallels here? Any parallel to a CD-ROM distribution, or a Tivo distribution?
Yes. You see how TiVO is different? It is modifyable, and I actually receive the copy that TiVO can still modify, but I can't.
I don't. You don't get the TiVO corporations copy of the software. You get your own copy, with all the rights that TiVO had when receiving the software. The right to install and run the kernel in the TiVO device is independent of the rights to copy, modify, distribute and run the software. (because the GPL never guarantees you the right to run the software on a particular piece of hardware.)
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 2 lines · Daniel Hazelton
And? There is *absolutely* *nothing* in any version of the GPL *prior* to 3 that says that hardware cannot impose restrictions.
It's not that the hardware is deciding to impose restrictions on its own. It's the hardware distributor that is deciding to use the hardware to impose restrictions on the user. Seems like a violation of section 6 of GPLv2 to me.
Quoted 2 lines
What the GPL *does* say is that you can't "add additional restrictions to the license"
Not quite. It's more general than that:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
So take another example: I obviously distribute code that is copyrighted by others under the GPLv2. Do I follow the GPLv2? I sure as hell do! But do I give you the same rights as I have to modify the copy on master.kernel.org as I have? I sure as hell DO NOT!
That's an interesting argument.
Quoted 7 lines
Quoted 5 lines
People don't get your copy, so they're not entitled to anything about it.
When they download the software, they get another copy, and they have a right to modify that copy.
But you get the TiVO corporations copy of the software?
Yes. The customer gets the copy that TiVO stored in the hard disk in the device it sells. And it's that copy that the customer is entitled to modify because TiVO is still able to modify it.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 5 lines · Alexandre Oliva
It's not that the hardware is deciding to impose restrictions on its own. It's the hardware distributor that is deciding to use the hardware to impose restrictions on the user. Seems like a violation of section 6 of GPLv2 to me.
You *still* haven't figured out the difference between "the software" and "a particular copy of the software", have you?
What's your problem?
I doubt you're really stupid, so I think your problem is that if you admit that "the software" is something *different* from "a particular copy of the software", you realize (perhaps subconsciously) that your arguments do not make any sense. So you do not allow yourself to think clearly about the matter.
So let's look at that "section 6" that you talk about, and quote the relevant parts, will we:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
and then let's look at Red Hat sending me a CD-ROM or a DVD.
Now, Red Hat clearly *did* "further restrict" my rights as it pertains TO THAT COPY ON THE CD-ROM! I cannot change it! Waa waa waa! I'll sue your sorry ass off!
See the issue? You are continually making the mistake of thinking that the GPLv2 talks about individual copies of software. And I'm continually having to point out that that is a MISTAKE.
And it's OBVIOUSLY a mistake, because your reading is nonsensical. If you think that Tivo does somethign bad, then hat Red Hat does is the same badness, thousads times over! I strongly suspect Red Hat has shipped a lot more CD-ROM's than Tivo has shipped boxes!
So let me iterate AGAIN:
- the rights that the GPLv2 gives *cannot* be about "the particular copy" that you send, since that would be INSANE. Red Hat sends lots of copies of software that are NOT MODIFIABLE!
- ergo, the rights about "the software" in the GPLv2 must be about something else.
See? Your argument about "individual copies" simply DOES NOT MAKE SENSE!
Just admit it.
Quoted 7 lines
Quoted 2 lines
What the GPL *does* say is that you can't "add additional restrictions to the license"
Not quite. It's more general than that:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
And your point is? Nothing.
The rights granted are the rights to "distribute and modify the software". But by "the software", the license is not talking about a particular *copy* of the software, it's talking about the software IN THE ABSTRACT.
In other words, the reason that Red Hat is not violating the GPLv2 is that no, I cannot change the copy on the software on the particular CD-ROM or DVD, but I can get a copy of the sources other ways, and make my own modifications *SOMEWHERE*ELSE*!
The fact that Red Hat made a "restricted copy" is totally irrelevant.
In fact, it's exactly as irrelevant as the fact that Tivo makes a "restricted copy". The *software* is still free!
Linus
Quoted 9 lines · Linus Torvalds
Quoted 5 lines · Alexandre Oliva
It's not that the hardware is deciding to impose restrictions on its own. It's the hardware distributor that is deciding to use the hardware to impose restrictions on the user. Seems like a violation of section 6 of GPLv2 to me.
You *still* haven't figured out the difference between "the software" and "a particular copy of the software", have you?
I have. And so has GPLv2, look:
2. You may modify your copy or copies of the Program or any portion
^^^^
Quoted 1 line
What's your problem?
Trying to get you to see what is so obvious to me.
Quoted 11 lines
So let's look at that "section 6" that you talk about, and quote the relevant parts, will we:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
and then let's look at Red Hat sending me a CD-ROM or a DVD.
Now, Red Hat clearly *did* "further restrict" my rights as it pertains TO THAT COPY ON THE CD-ROM! I cannot change it! Waa waa waa! I'll sue your sorry ass off!
Red Hat is not stopping you from making changes. The media is, and that's not something Red Hat can control.
Compare this with the TiVO. TiVO *designs* the thing such that it can still make changes, but customers can't.
That's the difference.
TiVO is using hardware to "impose further restrictions on the recipients' exercise of the rights granted herein", and this violates section 6 of GPLv2.
Quoted 2 lines
See the issue? You are continually making the mistake of thinking that the GPLv2 talks about individual copies of software.
It does. You're making the mistake of thinking that it doens't. And even in the legal terms that you claimed to have understood so thoroughly.
Quoted 1 line
The rights granted are the rights to "distribute and modify the software".
More specifically, some of the rights are:
copy and distribute verbatim copies of the Program's source code as you receive it
modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work
Quoted 2 lines
But by "the software", the license is not talking about a particular *copy* of the software, it's talking about the software IN THE ABSTRACT.
Please read it again.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}On Thursday 14 June 2007 14:35:29 Alexandre Oliva wrote:
<snip>
Quoted 6 lines
Quoted 6 lines
So let's look at that "section 6" that you talk about, and quote the relevant parts, will we:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
Quoted 8 lines
Quoted 5 lines
and then let's look at Red Hat sending me a CD-ROM or a DVD.
Now, Red Hat clearly *did* "further restrict" my rights as it pertains TO THAT COPY ON THE CD-ROM! I cannot change it! Waa waa waa! I'll sue your sorry ass off!
Red Hat is not stopping you from making changes. The media is, and that's not something Red Hat can control.
TiVO isn't stopping you from making changes - the *media* is. (in this case the "Media" isn't even doing as much as a CD-ROM does. The only thing a TiVO box restricts is which binaries it will execute as the operating system)
Quoted 5 lines
Compare this with the TiVO. TiVO *designs* the thing such that it can still make changes, but customers can't.
That's the difference.
No, it isn't. Look at any motherboard. The Bios on the last three or four motherboards I've purchased check for a digital signature on the Bios updates. The motherboard manufacturer can make changes, but the customer can't. Is there any difference? Nope.
Quoted 3 lines
TiVO is using hardware to "impose further restrictions on the recipients' exercise of the rights granted herein", and this violates section 6 of GPLv2.
No, they don't. The GPLv2 makes no provisions for you being able to execute a modified copy of the code on the same media or hardware that you received it on. The fact is that claiming it was "the spirit" doesn't matter at all - this isn't philosophy you're arguing, its *LAW*, and in law, if it isn't clearly spelled out, it doesn't exist.
Quoted 10 lines
Quoted 2 lines
See the issue? You are continually making the mistake of thinking that the GPLv2 talks about individual copies of software.
It does. You're making the mistake of thinking that it doens't. And even in the legal terms that you claimed to have understood so thoroughly.
Quoted 2 lines
The rights granted are the rights to "distribute and modify the software".
Quoted 8 lines
More specifically, some of the rights are:
copy and distribute verbatim copies of the Program's source code as you receive it
modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work
And where does it say that you even have the right to run the "work based on the Program", or even a self-compiled copy of the "verbatim copy of the code" on any given piece of hardware?
Quoted 4 lines
Quoted 2 lines
But by "the software", the license is not talking about a particular *copy* of the software, it's talking about the software IN THE ABSTRACT.
Please read it again.
Done. Section 3 of GPLv2 covers the right to distribute "object code" forms of a licensed work. At no point does it even *mention* that, if the object code form comes on a device capable of executing it, you have to give the right to execute a modified form of the work on the same platform. If this has been the "intent and spirit" of the license from the beginning, it should be there somewhere.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 10 lines · Daniel Hazelton
On Thursday 14 June 2007 14:35:29 Alexandre Oliva wrote:
<snip>Quoted 8 lines
Quoted 8 lines
So let's look at that "section 6" that you talk about, and quote the relevant parts, will we:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
and then let's look at Red Hat sending me a CD-ROM or a DVD.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Now, Red Hat clearly *did* "further restrict" my rights as it pertains TO THAT COPY ON THE CD-ROM! I cannot change it! Waa waa waa! I'll sue your sorry ass off!
Red Hat is not stopping you from making changes. The media is, and that's not something Red Hat can control.
TiVO isn't stopping you from making changes - the *media* is.
TiVO made it so, that's the difference.
I'll give you that it's not so much about making changes per se, or even installing them, as it is about running the modified versions for any purpose.
Quoted 9 lines
Quoted 4 lines
Compare this with the TiVO. TiVO *designs* the thing such that it can still make changes, but customers can't.
That's the difference.
No, it isn't. Look at any motherboard. The Bios on the last three or four motherboards I've purchased check for a digital signature on the Bios updates. The motherboard manufacturer can make changes, but the customer can't. Is there any difference? Nope.
Is the BIOS code under the GPL?
Quoted 3 lines
The fact is that claiming it was "the spirit" doesn't matter at all
- this isn't philosophy you're arguing, its *LAW*, and in law, if it isn't clearly spelled out, it doesn't exist.
That's exactly what makes for the difference between the spirit and the precise legal terms, and why GPLv3 is fixing these divergences.
Quoted 3 lines
And where does it say that you even have the right to run the "work based on the Program", or even a self-compiled copy of the "verbatim copy of the code" on any given piece of hardware?
It doesn't. The license can't demand the software, or modified versions thereof, to run. The only thing it can demand is that licensees don't impose restrictions on others' abilities to do so.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
But by "the software", the license is not talking about a particular *copy* of the software, it's talking about the software IN THE ABSTRACT.
Please read it again.
Done.
2. You may modify your copy or copies of the Program or any portion
of it ^^^^
Quoted 2 lines
If this has been the "intent and spirit" of the license from the beginning, it should be there somewhere.
I think you're missing what 'spirit' means. It's guidance, it's not the legal terms. And it's precisely because the implementation (the legal terms) failed to meet that design (the spirit, encoded in the preamble) that the license needs patching.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 19 lines · On Thursday 14 June 2007 21:43:07 Alexandre Oliva wrote:
Quoted 18 lines · Daniel Hazelton
On Thursday 14 June 2007 14:35:29 Alexandre Oliva wrote:
<snip>Quoted 14 lines
Quoted 11 lines
So let's look at that "section 6" that you talk about, and quote the relevant parts, will we:
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
and then let's look at Red Hat sending me a CD-ROM or a DVD.
Now, Red Hat clearly *did* "further restrict" my rights as it pertains TO THAT COPY ON THE CD-ROM! I cannot change it! Waa waa waa! I'll sue your sorry ass off!
Red Hat is not stopping you from making changes. The media is, and that's not something Red Hat can control.
Quoted 7 lines
Quoted 1 line
TiVO isn't stopping you from making changes - the *media* is.
TiVO made it so, that's the difference.
I'll give you that it's not so much about making changes per se, or even installing them, as it is about running the modified versions for any purpose.
Artificial distinction on your part.
Quoted 11 lines
Quoted 9 lines
Quoted 4 lines
Compare this with the TiVO. TiVO *designs* the thing such that it can still make changes, but customers can't.
That's the difference.
No, it isn't. Look at any motherboard. The Bios on the last three or four motherboards I've purchased check for a digital signature on the Bios updates. The motherboard manufacturer can make changes, but the customer can't. Is there any difference? Nope.
Is the BIOS code under the GPL?
By your reasoning it doesn't even matter. I own the hardware, I should be able to change the BIOS to *any* chunk of code I want.
Do you see the fallacy here? You're making an artificial distinction based on whether the *SOFTWARE* has a certain license or not.
Quoted 6 lines
Quoted 3 lines
The fact is that claiming it was "the spirit" doesn't matter at all
- this isn't philosophy you're arguing, its *LAW*, and in law, if it isn't clearly spelled out, it doesn't exist.That's exactly what makes for the difference between the spirit and the precise legal terms, and why GPLv3 is fixing these divergences.
And the reason behind this is all "ethics and morals". In other words, you are forcing those "ethics and morals" on others and hiding it by giving it a different name.
Wasn't it Shakespear who said: "What is in a name? A Rose by any other name would smell as sweet"
Quoted 7 lines
Quoted 3 lines
And where does it say that you even have the right to run the "work based on the Program", or even a self-compiled copy of the "verbatim copy of the code" on any given piece of hardware?
It doesn't. The license can't demand the software, or modified versions thereof, to run. The only thing it can demand is that licensees don't impose restrictions on others' abilities to do so.
No, it doesn't. There is no requirement in the license in question that makes a persons ability to run the program on any given piece of hardware. What it does say is you can't stop someone from *TRYING* to do that.
Quoted 11 lines
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
But by "the software", the license is not talking about a particular *copy* of the software, it's talking about the software IN THE ABSTRACT.
Please read it again.
Done.
2. You may modify your copy or copies of the Program or any portion
of it ^^^^
Quoted 7 lines
Quoted 2 lines
If this has been the "intent and spirit" of the license from the beginning, it should be there somewhere.
I think you're missing what 'spirit' means. It's guidance, it's not the legal terms. And it's precisely because the implementation (the legal terms) failed to meet that design (the spirit, encoded in the preamble) that the license needs patching.
If the intent of a law (or license) is to do A but it doesn't say that, then how is the intent to be known? Your answer: Ask the author. Question: how can we be absolutely certain that the authors intent *hasn't* changed since the law (or license) was written? *ONLY* answer: It is impossible. Conclusion:
Unless the intent is clearly spelled out at the time the law (or license) is written, or is available in other writings by the author of the law/license from the same time period as the law/license then it is impossible.
Question: How do you know what the "spirit" of a license is? Your Answer: Ask the author.
Question: How do we know that the Author hasn't changed their mind about the "spirit" of the license since it was written?
*ONLY* Answer: See the answer to the parallel question about "intent".
Now that I've knocked down your "Intent" and "Spirit" straw-men you have no way to argue that the GPLv3 is written with the same "spirit" as the GPLv2.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 2 lines · Daniel Hazelton
You're making an artificial distinction based on whether the *SOFTWARE* has a certain license or not.
What matters to me is that, when the GPL says you can't impose further restrictions, then you can't, no matter how convoluted your argument is
Quoted 4 lines
Quoted 2 lines
That's exactly what makes for the difference between the spirit and the precise legal terms, and why GPLv3 is fixing these divergences.
And the reason behind this is all "ethics and morals".
There was never any attempt to hide that this was what the Free Software movement was about, and that the GPL was about defending these freedoms.
Sure, it has other advantages. But the goal has always been the same, and it's not going to change.
Quoted 3 lines
If the intent of a law (or license) is to do A but it doesn't say that, then how is the intent to be known? Your answer: Ask the author.
No, you interpret based on what the author wrote then.
You read the preamble, and any other rationales associated with the license or law. I don't know how it's elsewhere, but in Brazil every law has a rationale, and that's often used to guide its interpretation in courts, even though the rationale is not part of the law.
If the author realizes what he wrote was not enough, or it got misinterpreted, author his text, and then whoever feels like it and is entitled to adopts the revised version.
In the GPLv2=>v3 case, all that needed revision was the legalese. The preamble has barely changed. This is a strong indication that the spirit remains the same, is it not?
Quoted 4 lines
Unless the intent is clearly spelled out at the time the law (or license) is written, or is available in other writings by the author of the law/license from the same time period as the law/license then it is impossible.
Is there anything not clear about freedom #0, in the free software definition, alluded to by the preamble that talks about free software in very similar terms?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 7 lines · On Thursday 14 June 2007 23:39:50 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton
You're making an artificial distinction based on whether the *SOFTWARE* has a certain license or not.
What matters to me is that, when the GPL says you can't impose further restrictions, then you can't, no matter how convoluted your argument is
Convoluted? Not in the least. Every example I have given has been an example of the application of your logic. If my examples are convoluted, then, QED, so is your logic.
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines
That's exactly what makes for the difference between the spirit and the precise legal terms, and why GPLv3 is fixing these divergences.
And the reason behind this is all "ethics and morals".
There was never any attempt to hide that this was what the Free Software movement was about, and that the GPL was about defending these freedoms.
Sure, it has other advantages. But the goal has always been the same, and it's not going to change.
I'm not trying to change that. My point in making that statement is to prove that the FSF is doing exactly what the Spanish Inquisition did, what every "Communist Revolution" has done and what Hitler did. Saying "My ethics and morals are better than everyone else, so I'm going to force everyone else to have my morals and ethics". That the FSF isn't doing this through force of arms or threat of violence just shows how sophisticated people have really become in the sixty years that have passed since Hitler - they now use threat of legal action.
Quoted 5 lines
Quoted 3 lines
If the intent of a law (or license) is to do A but it doesn't say that, then how is the intent to be known? Your answer: Ask the author.
No, you interpret based on what the author wrote then.
Really? Well I must say I'm surprised at the sudden change of heart. I have several mails here in which you have either said "You ask the author" or that line has been quoted.
Quoted 4 lines
You read the preamble, and any other rationales associated with the license or law. I don't know how it's elsewhere, but in Brazil every law has a rationale, and that's often used to guide its interpretation in courts, even though the rationale is not part of the law.
Show me where in the preamble that this issue of "it must run on any given piece of hardware" or even less generally, "it must run on the hardware it came on" is even *hinted* at. You wont find it. Nor will you find any mention of anything of the sort in the publicly available writings of RMS.
But let me go re-read the GPLv2 preamble again and see if it even hints at this issue... oh, wait, I read it earlier and didn't see anything that hinted at this. So I can safely conclude that no lawyer or judge would find it when interpreting the license. QED: The Tivo clause of GPLv3 causes it to break spirit with the GPLv2.
(And, by the way, if the FSF decided to release a GPLv4 that had an active section that said "You must turn over all copyright rights to a work released under this license to the FSF" it wouldn't "break spirit" with the GPL (v2 or v3). Why? Because *both* contain the following paragraph:
"We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
By your logic it is the *intent* of the FSF to hold copyright on all software released under the GPL *and* only give the rights detailed in the license to other people - including the person who has placed the work under the GPL.
Can you see the problem with your logic ?
Quoted 9 lines
If the author realizes what he wrote was not enough, or it got misinterpreted, author his text, and then whoever feels like it and is entitled to adopts the revised version.
In the GPLv2=>v3 case, all that needed revision was the legalese. The preamble has barely changed. This is a strong indication that the spirit remains the same, is it not?
If "tivoization" was against the spirit, then all that would have been needed was one extra clause clearly explaining that. Instead there are more than 6 extra sections in the GPLv3.
If "DRM" was against the license then an extra section clearly explaining that could have been added. (in the DRM case I actually understand the reasoning and agree with it.)
Quoted 8 lines
Quoted 4 lines
Unless the intent is clearly spelled out at the time the law (or license) is written, or is available in other writings by the author of the law/license from the same time period as the law/license then it is impossible.
Is there anything not clear about freedom #0, in the free software definition, alluded to by the preamble that talks about free software in very similar terms?
0. ... 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, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
Note that it says, in very clear and simple English, that the scope of the license is *ONLY* the activities of "copying, distribution and modification". I must be an idiot, because I completely fail to see how an activity besides one of the three that are mentioned as being the only ones in the scope of the license is in the "spirit" of the license.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 10 lines · Daniel Hazelton
Quoted 7 lines · On Thursday 14 June 2007 23:39:50 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton
You're making an artificial distinction based on whether the *SOFTWARE* has a certain license or not.
What matters to me is that, when the GPL says you can't impose further restrictions, then you can't, no matter how convoluted your argument is
Convoluted? Not in the least.
I didn't say your arguments were convoluted, and I know I didn't mean to say that. But I've heard enough arguments about excuses to escape the obligations of the GPL (and other licenses and obligations, FWIW) to know that such arguments can get very convoluted.
That said, I was actually trying to quote Eben Moglen, who once spoke about this, but the word he used was "elaborate", not "convoluted". Unfortunately, the right word escaped me ATM.
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
If the intent of a law (or license) is to do A but it doesn't say that, then how is the intent to be known? Your answer: Ask the author.
No, you interpret based on what the author wrote then.
Really? Well I must say I'm surprised at the sudden change of heart. I have several mails here in which you have either said "You ask the author" or that line has been quoted.
It's no change. You interpret what's there. If it's clear, good. If there's a dispute, you have to ask the author, only s/he knows what s/he meant. It's really that simple.
Quoted 2 lines
Show me where in the preamble that this issue of "it must run on any given piece of hardware"
Why is the burden of the proof on me?
You show me where it says "one may impose restrictions on what particupar pieces of hardware the program can run", to override the general spirit of "passing on all the rights one has".
Quoted 4 lines
(And, by the way, if the FSF decided to release a GPLv4 that had an active section that said "You must turn over all copyright rights to a work released under this license to the FSF" it wouldn't "break spirit" with the GPL (v2 or v3).
Can't. These terms wouldn't apply to the copyright holder (the only person who could make the transfer), only to licensees.
Quoted 3 lines
If "tivoization" was against the spirit, then all that would have been needed was one extra clause clearly explaining that. Instead there are more than 6 extra sections in the GPLv3.
Erhm... How did you get the (completely flawed, BTW) impression that tivoization was all GPLv3 was about?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 12 lines · On Friday 15 June 2007 16:04:15 Alexandre Oliva wrote:
Quoted 10 lines · Daniel Hazelton
Quoted 7 lines · On Thursday 14 June 2007 23:39:50 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton
You're making an artificial distinction based on whether the *SOFTWARE* has a certain license or not.
What matters to me is that, when the GPL says you can't impose further restrictions, then you can't, no matter how convoluted your argument is
Convoluted? Not in the least.
Quoted 8 lines
I didn't say your arguments were convoluted, and I know I didn't mean to say that. But I've heard enough arguments about excuses to escape the obligations of the GPL (and other licenses and obligations, FWIW) to know that such arguments can get very convoluted.
That said, I was actually trying to quote Eben Moglen, who once spoke about this, but the word he used was "elaborate", not "convoluted". Unfortunately, the right word escaped me ATM.
Thanks for the clarification.
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 3 lines
If the intent of a law (or license) is to do A but it doesn't say that, then how is the intent to be known? Your answer: Ask the author.
No, you interpret based on what the author wrote then.
Quoted 7 lines
Quoted 3 lines
Really? Well I must say I'm surprised at the sudden change of heart. I have several mails here in which you have either said "You ask the author" or that line has been quoted.
It's no change. You interpret what's there. If it's clear, good. If there's a dispute, you have to ask the author, only s/he knows what s/he meant. It's really that simple.
And as I have hopefully given good proof for, asking the author is not a good solution. The author can change their mind about their intent at any point in time - even during the process of writing the license.
Quoted 8 lines
Quoted 2 lines
Show me where in the preamble that this issue of "it must run on any given piece of hardware"
Why is the burden of the proof on me?
You show me where it says "one may impose restrictions on what particupar pieces of hardware the program can run", to override the general spirit of "passing on all the rights one has".
It's "pass on all rights granted under this license". If I had to pass on "all rights I have" I'd have to pass on my right to change the license on my code. Since that isn't a right I'm obligated to pass on - and you could never convice me it is - I'm not "passing on all the rights I have" at *all*.
Quoted 7 lines
Quoted 4 lines
(And, by the way, if the FSF decided to release a GPLv4 that had an active section that said "You must turn over all copyright rights to a work released under this license to the FSF" it wouldn't "break spirit" with the GPL (v2 or v3).
Can't. These terms wouldn't apply to the copyright holder (the only person who could make the transfer), only to licensees.
It's part of the preamble, in which the "We" refers to the FSF. If the preamble determines the "intent" and "spirit" of the license, then part of the "intent" and "spirit" of the license is collective aggregation of all copyright rights to all software released under the GPL by the FSF.
Quoted 6 lines
Quoted 3 lines
If "tivoization" was against the spirit, then all that would have been needed was one extra clause clearly explaining that. Instead there are more than 6 extra sections in the GPLv3.
Erhm... How did you get the (completely flawed, BTW) impression that tivoization was all GPLv3 was about?
I've looked through the GPLv3 and "tivoization" and DRM are the only things that are functionally different. In reading the GPLv3 *again* today I got the impression that there are more restrictions than grants of rights.
DRH
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 3 lines · Daniel Hazelton
I've looked through the GPLv3 and "tivoization" and DRM are the only things that are functionally different. In reading the GPLv3 *again* today I got the impression that there are more restrictions than grants of rights.
http://fsfla.org/svnwiki/blogs/lxo/draft/gplv3-snowwhite discusses each one of the significant changes (and some of the insignificant ones) and shows why each one of them is more "tit-for-tat" than v2.
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 5 lines · Alexandre Oliva
Quoted 3 lines · Daniel Hazelton
Quoted 3 lines
When they download the software, they get another copy, and they have a right to modify that copy.
Quoted 7 lines
Quoted 2 lines
But you get the TiVO corporations copy of the software?
Yes. The customer gets the copy that TiVO stored in the hard disk in the device it sells. And it's that copy that the customer is entitled to modify because TiVO is still able to modify it.
No, by this twisted logic Tivo *cannot* modify that particular copy any more than you can. They can modify *another* copy (just like you) and they can *replace* the copy in your device with the new version (unlike you).
So your entire logical construct does not stand because this is not (cannot be) about modifying a particular copy (how would you do that anyway? hexedit the binary blob in place?) but about the ability to deploy the software on a particular platform.
---
fm
Quoted 8 lines · Florin Malita
Quoted 6 lines · Alexandre Oliva
Quoted 4 lines · Daniel Hazelton
Quoted 2 lines
When they download the software, they get another copy, and they have a right to modify that copy.
But you get the TiVO corporations copy of the software?
Quoted 8 lines
Quoted 3 lines
Yes. The customer gets the copy that TiVO stored in the hard disk in the device it sells. And it's that copy that the customer is entitled to modify because TiVO is still able to modify it.
No, by this twisted logic Tivo *cannot* modify that particular copy any more than you can. They can modify *another* copy (just like you) and they can *replace* the copy in your device with the new version (unlike you).
Again, replacing is one form of modification.
What do you think you do when you save a modified source file in your editor?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 8 lines · Alexandre Oliva
Quoted 5 lines
No, by this twisted logic Tivo *cannot* modify that particular copy any more than you can. They can modify *another* copy (just like you) and they can *replace* the copy in your device with the new version (unlike you).
Again, replacing is one form of modification.
No, it's not: replacing does not create derivative work. Modification does.
You've chosen to attach a physical dimension to "program copy" and I'm arguing that even under this distorted line of reasoning you can't support your position:
Quoted 3 lines
The customer gets the copy that TiVO stored in the hard disk in the device it sells. And it's that copy that the customer is entitled to modify because TiVO is still able to modify it.
* Tivo takes public sources, modifies them and builds a brand new blob
* Tivo installs this new copy on the device, most likely side-by-side with the old one - notice how the new copy is derived from public sources and has absolutely nothing to do with the old version (heck, it can be a totally different kernel for what it's worth)
* Tivo deletes the old copy from the device
It seems pretty obvious that the only right Tivo is withholding is the right to install new versions on the device - they never do (and really never could) "modify" the physical copy on your device (which is your main argument).
Quoted 2 lines
What do you think you do when you save a modified source file in your editor?
Don't skip the part where the in-memory version started as an exact copy of the original being replaced. Notice the difference? ;)
---
fm
Quoted 10 lines · Florin Malita
Quoted 6 lines · Alexandre Oliva
Quoted 4 lines
No, by this twisted logic Tivo *cannot* modify that particular copy any more than you can. They can modify *another* copy (just like you) and they can *replace* the copy in your device with the new version (unlike you).
Again, replacing is one form of modification.
No, it's not: replacing does not create derivative work. Modification does.
Thanks. Good point. This convinces me that this doesn't work as a legal argument under copyright.
I still stand by my understanding that this restriction violates the spirit of the license.
And since the specific implementation involves creating a derived work of the GPLed kernel (the signature, or the signed image, or what have you) and refraining from providing the corresponding sources to that derived work (the key and the signature "build scripts"), I still think this specific case is a violation of the letter of the GPLv2, even if the FSF doesn't take this position.
Quoted 2 lines
It seems pretty obvious that the only right Tivo is withholding is the right to install new versions on the device
Actually, no. They withhold the right to run versions that they don't authorize themselves.
Back when GPLv2 was written, the right to run was never considered an issue. It was taken for granted, because copyright didn't control that in the US (it does in Brazil), and nobody had thought of technical measures to stop people from running modified copies of software. At least nobody involved in GPLv2, AFAIK.
The landscape has changed, and GPLv3 is meant to defend this freedom that was taken for granted.
Quoted 2 lines
they never do (and really never could) "modify" the physical copy on your device (which is your main argument).
Qualifying it as the main argument is a bit of an exaggeration. I have a number of different arguments. The one about incomplete sources is the most solid IMHO.
Quoted 5 lines
Quoted 2 lines
What do you think you do when you save a modified source file in your editor?
Don't skip the part where the in-memory version started as an exact copy of the original being replaced. Notice the difference? ;)
Sorry, I really don't follow. Both versions of the kernel binary also started from a common source ancestor. Were you trying to make a distinction on these grounds?
Signature · 4 lines
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
And since the specific implementation involves creating a derived work of the GPLed kernel (the signature, or the signed image, or what have you)
Wait, a signed filesystem image that happens to contain GPL code is now a derived work? Under what sort of interpretation does *that* occur?
(This pretty much throws the 'aggregation' premise in GPLv2 completely out.)
Bill