Skip to contentSkip to conversation

Dual-Licensing Linux Kernel with GPL V2 and GPL V3

DISCUSSION Tarkan Erimer 88 participants 991 messages Jun 9, 2007 – Jun 22, 2007 20 messages not in the archive Page 1 of 5

lore
Share & tools
lore
#0 lore raw

Hi,

As we know the forthcoming GPL V3 will be not compatible with the GPL V2 and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others, that if it is decided to upgrade the Linux Kernel's License to GPL V3, it is needed the permission of all the maintainers permission who contributed to the Linux Kernel and there are a lot of lost or dead maintainers. Which makes it impossible to get all the maintainers' permission. But; if the Linux kernel should Dual-Licensed (GPL V2 and GPL V3), it will allow us the both worlds' fruits like code exchanging from other Open Source Projects (OpenSolaris etc.) that is compatible with GPL V3 and not with GPL V2 and of course the opposite is applicable,too.

So;at this situation, what is possibility to make the Linux Kernel Dual-Licensed as I mentioned above and what is your opinions and suggestions about this idea ?

Regards,

Tarkan Erimer

#1 lore raw
Quoted 10 lines · On Saturday June 9, [email protected] wrote:

Hi,

As we know the forthcoming GPL V3 will be not compatible with the GPL V2 and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others, that if it is decided to upgrade the Linux Kernel's License to GPL V3, it is needed the permission of all the maintainers permission who contributed to the Linux Kernel and there are a lot of lost or dead maintainers. Which makes it impossible to get all the maintainers' permission.

You don't need the permission of maintainers. You need the permission of copyright owners. The two groups overlap, but are not the same. Dead people cannot own anything, even copyright. Their estate probably can. I don't think it is theoretically impossible to get everyone's permission, though it may be quite close to practically impossible.

Quoted 8 lines

But; if the Linux kernel should Dual-Licensed (GPL V2 and GPL V3), it will allow us the both worlds' fruits like code exchanging from other Open Source Projects (OpenSolaris etc.) that is compatible with GPL V3 and not with GPL V2 and of course the opposite is applicable,too.

So;at this situation, what is possibility to make the Linux Kernel Dual-Licensed as I mentioned above and what is your opinions and suggestions about this idea ?

Dual licensing is no easier. It means it is licensed to be used under either license. You already have permission to use it under GPLv2. So to get a dual license, you precisely need to get access under GPLv3 i.e. to convince copyright owners to make that license grant. A thing that we have already agreed is at least "hard".

NeilBrown

#2 lore raw
Quoted 10 lines · Neil Brown
Quoted 8 lines · On Saturday June 9, [email protected] wrote:

As we know the forthcoming GPL V3 will be not compatible with the GPL V2 and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others, that if it is decided to upgrade the Linux Kernel's License to GPL V3, it is needed the permission of all the maintainers permission who contributed to the Linux Kernel and there are a lot of lost or dead maintainers. Which makes it impossible to get all the maintainers' permission.

Quoted 6 lines

You don't need the permission of maintainers. You need the permission of copyright owners. The two groups overlap, but are not the same. Dead people cannot own anything, even copyright. Their estate probably can. I don't think it is theoretically impossible to get everyone's permission, though it may be quite close to practically impossible.

And the next question is: How much copyright does a copyright owner own? For example, think of drivers written by one person, but a small number of lines changed here and there by others to adopt the code to new APIs. Ask them all, I think?

MfG, JBG

Signature · 3 lines
      Jan-Benedict Glaw      [email protected]              +49-172-7608481
Signature of:             God put me on earth to accomplish a certain number of
the second  :            things. Right now I am so far behind I will never die.
#3 lore raw
Quoted 15 lines · Jan-Benedict Glaw
Quoted 5 lines · Neil Brown
Quoted 3 lines · On Saturday June 9, [email protected] wrote:

As we know the forthcoming GPL V3 will be not compatible with the GPL V2 and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others, that if it is decided to upgrade the Linux Kernel's License to GPL V3, it is needed the permission of all the maintainers permission who contributed to the Linux Kernel and there are a lot of lost or dead maintainers. Which makes it impossible to get all the maintainers' permission.

Quoted 7 lines

You don't need the permission of maintainers. You need the permission of copyright owners. The two groups overlap, but are not the same. Dead people cannot own anything, even copyright. Their estate probably can. I don't think it is theoretically impossible to get everyone's permission, though it may be quite close to practically impossible.

Quoted 8 lines

And the next question is: How much copyright does a copyright owner own? For example, think of drivers written by one person, but a small number of lines changed here and there by others to adopt the code to new APIs. Ask them all, I think?

MfG, JBG

And maybe another questions should be : How long a copyright owner can hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders at this point for copyright holding ?

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 31 lines · [email protected] wrote:
Quoted 29 lines · Tarkan Erimer

Date: Sun, 10 Jun 2007 11:43:28 +0300
From: Tarkan Erimer <[email protected]>
To: [email protected]
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

Quoted 22 lines · Jan-Benedict Glaw
Quoted 2 lines · Neil Brown
Quoted 1 line · On Saturday June 9, [email protected] wrote:
Quoted 1 line

As we know the forthcoming GPL V3 will be not compatible with

the GPL > > V2 and Linux Kernel is GPL V2 only.

Quoted 1 line
Quoted 1 line

So, another point is, which is previously mentioned by Linus

and > > others, that if it is decided to upgrade the Linux Kernel's License to > > GPL V3, it is needed the permission of all the maintainers permission > > who contributed to the Linux Kernel and there are a lot of lost or > > dead maintainers. Which makes it impossible to get all the > > maintainers' permission.

Quoted 1 line
Quoted 1 line
Quoted 1 line

You don't need the permission of maintainers. You need the

permission

Quoted 5 lines

of copyright owners. The two groups overlap, but are not the same. Dead people cannot own anything, even copyright. Their estate probably can. I don't think it is theoretically impossible to get everyone's permission, though it may be quite close to practically impossible. >

And the next question is: How much copyright does a copyright owner own? For example, think of drivers written by one person, but a small number of lines changed here and there by others to adopt the code to new APIs. Ask them all, I think?

MfG, JBG

Quoted 5 lines
Quoted 1 line

And maybe another questions should be : How long a copyright owner can hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders at this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better idea to replace the code of this person as said before instead of waiting such 90+ years!

#6 lore raw
Quoted 9 lines · Tarkan Erimer
Quoted 8 lines
Quoted 4 lines

And maybe another questions should be : How long a copyright owner can hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders at this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better idea to replace the code of this person as said before instead of waiting such 90+ years!

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it really doesn't matter how hard it is to deal with the people who you can't contact.

David Lang

#7 lore raw
Quoted 9 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 7 lines · Tarkan Erimer
Quoted 7 lines
Quoted 4 lines

And maybe another questions should be : How long a copyright owner can hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders at this point for copyright holding ?

I believe that in the US it's life + 90 years.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

David Lang

Hmm... Really,it is damn too much time to wait! It's really better idea to replace the code of this person as said before instead of waiting such 90+ years!

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

#8 lore raw
Quoted 19 lines · debian developer
Quoted 18 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright

owner can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law

orders at

Quoted 6 lines
Quoted 5 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better

idea to

Quoted 1 line

replace the code of this person as said before instead of waiting

such 90+

Quoted 1 line

years!

Quoted 8 lines
Quoted 3 lines

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

Yep, the GPLv3 probably will release around July time. So;luckily, we had very little time to see the final decision about it :-) I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). So,we should have more fruits (like ZFS,DTrace etc.) ;-)

#9 lore raw
Quoted 2 lines · Tarkan Erimer

I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.).

The OpenSolaris community has already stated that they do not want to accept GPLv3, why not discuss this with them if you want to try to change their minds?

Quoted 1 line

So,we should have more fruits (like ZFS,DTrace etc.) ;-)

I think the transfer would be more the other way, we have a zillion more things that they do not than the other way around.

thanks,

greg k-h

#10 lore raw
Quoted 10 lines · Greg KH
Quoted 3 lines · Tarkan Erimer

I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.).

The OpenSolaris community has already stated that they do not want to accept GPLv3, why not discuss this with them if you want to try to change their minds?

It was just an example came to my mind at first when thinking about "Dual Licensing" or upgrading Linux Kernel to the GPLv3. Yeah maybe,the "OpenSolaris Community" do not want GPLv3. But; IMHO, it is in the hands of "Sun" not the "OpenSolaris Community".

Regards,

Tarkan

#11 lore raw
Quoted 7 lines · Tarkan Erimer
Quoted 6 lines · Greg KH
Quoted 3 lines · Tarkan Erimer

I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.).

Quoted 8 lines
Quoted 4 lines

The OpenSolaris community has already stated that they do not want to accept GPLv3, why not discuss this with them if you want to try to change their minds?

It was just an example came to my mind at first when thinking about "Dual Licensing" or upgrading Linux Kernel to the GPLv3. Yeah maybe,the "OpenSolaris Community" do not want GPLv3. But; IMHO, it is in the hands of "Sun" not the "OpenSolaris Community".

Perhaps. However, since the only thing in hands of your kind of advocates is best not mentioned on a family-friendly maillist, may I suggest taking that exciting thread to more appropriate place?

#12 lore raw
Quoted 4 lines · Al Viro

Perhaps. However, since the only thing in hands of your kind of advocates is best not mentioned on a family-friendly maillist, may I suggest taking that exciting thread to more appropriate place?

I don't think that this thread is going unfriendly or harmfully. However, what is your suggestion ?

#13 lore raw
Quoted 13 lines · Tarkan Erimer
Quoted 13 lines
Quoted 12 lines
Quoted 7 lines
Quoted 3 lines

I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.).

The OpenSolaris community has already stated that they do not want to accept GPLv3, why not discuss this with them if you want to try to change their minds?

It was just an example came to my mind at first when thinking about "Dual Licensing" or upgrading Linux Kernel to the GPLv3. Yeah maybe,the "OpenSolaris Community" do not want GPLv3. But; IMHO, it is in the hands of "Sun" not the "OpenSolaris Community".

Quoted 6 lines
Quoted 3 lines

Perhaps. However, since the only thing in hands of your kind of advocates is best not mentioned on a family-friendly maillist, may I suggest taking that exciting thread to more appropriate place?

I don't think that this thread is going unfriendly or harmfully. However, what is your suggestion ?

if you want to change the minds of the OpenSolaris community, i'd proffer that it's perhaps more efficient to talk to them, not to the linux-kernel mailing list. Thanks,

Ingo

#14 lore raw
Quoted 4 lines · Ingo Molnar

if you want to change the minds of the OpenSolaris community, i'd proffer that it's perhaps more efficient to talk to them, not to the linux-kernel mailing list. Thanks,

Ingo

I do not want to and try to change anyone's mind: nor the Open Solaris Community nor the Linux Community. Just, I asked simple question and included a simple example in it. Son, including an example related to OpenSolaris does not mean that I want to push OpenSolaris things. That's all.

Regards,

Tarkan

#15 lore raw
Quoted 2 lines · Tarkan Erimer

[...] Just, I asked simple question and included a simple example in it. [...]

actually, what you said was this:

" I hope we should upgrade to GPLv3 and Sun should "Dual License"
the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). "

and to that the answer was:

" The OpenSolaris community has already stated that they do not want to
accept GPLv3 [...] "

in other words: your hypothetical is false today. You called us to do a specific action, but why did you then include a factually false 'example' to underline that point of yours? Or if you simply did not know about the OpenSolaris community's position beforehand, why dont you just admit that and withdraw from that line of argument gracefully?

Ingo

#16 lore raw
Quoted 12 lines · Ingo Molnar
Quoted 2 lines · Tarkan Erimer

[...] Just, I asked simple question and included a simple example in it. [...]

actually, what you said was this:

" I hope we should upgrade to GPLv3 and Sun should "Dual License"
the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). "

Why don't you include the last sentence I wrote: "So,we should have more fruits (like ZFS,DTrace etc.) ;-) " So, that's why I said it. Because, as all the time, we did it: Importing and exporting codes to/from different open source projects.

Quoted 9 lines

and to that the answer was:

" The OpenSolaris community has already stated that they do not want to
accept GPLv3 [...] "

in other words: your hypothetical is false today. You called us to do a specific action, but why did you then include a factually false 'example' to underline that point of yours? Or if you simply did not know about the OpenSolaris community's position beforehand, why dont you just admit that and withdraw from that line of argument gracefully?

Ingo

As I mentioned in my previous posts: This is **not** in the hands of the "OpenSolaris Community" to make and apply such decision. Sun itself **will decide** it. Also, there are strong indications that Sun is very interested to make "OpenSolaris" at least "Dual-Licensed" with GPLv3.

Regards,

Tarkan

#17 lore raw
Quoted 8 lines · Tarkan Erimer
Quoted 7 lines · Ingo Molnar
Quoted 3 lines · Tarkan Erimer

[...] Just, I asked simple question and included a simple example in it. [...]

Quoted 8 lines
Quoted 6 lines

actually, what you said was this:

" I hope we should upgrade to GPLv3 and Sun should "Dual License"
the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). "

Why don't you include the last sentence I wrote: "So,we should have more fruits (like ZFS,DTrace etc.) ;-) "

You might as well have said "the moon is made out of cheese" and i'd not have quoted it either. Why? Because it's irrelevant to the fundamental point that was raised and which you keep ignoring: that the only "example" you cited is a hypothetical that is currently false. In any case, speculation about what Sun might or might not do, up until the point it actually does it, is not something i feel compelled to do anything over, so please stop wasting my time by Cc:-ing me. Thanks,

Ingo

#18 lore raw
Quoted 4 lines · Ingo Molnar

You might as well have said "the moon is made out of cheese" and i'd not have quoted it either. Why? Because it's irrelevant to the fundamental point that was raised and which you keep ignoring: that the only "example" you cited is a hypothetical that is currently false. In any case, speculation about what Sun might or might not do, up until the point it actually does it, is not something i feel compelled to do anything over, so please stop wasting my time by Cc:-ing me. Thanks,

Ingo

I think, you do not want to understand what I really mean. OK,I stopping here. Because, you already wasted a lot of my time via always not understanding what I really mean.

Regards,

Tarkan

#19 lore raw
In reply to Tarkan Erimer
Quoted 3 lines · Tarkan Erimer
Quoted 3 lines

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3.

I was impressed in the sense that it was a hell of a lot better than the disaster that were the earlier drafts.

I still think GPLv2 is simply the better license.

I consider dual-licensing unlikely (and technically quite hard), but at least _possible_ in theory. I have yet to see any actual *reasons* for licensing under the GPLv3, though. All I've heard are shrill voices about "tivoization" (which I expressly think is ok) and panicked worries about Novell-MS (which seems way overblown, and quite frankly, the argument seems to not so much be about the Novell deal, as about an excuse to push the GPLv3).

Linus

#20 lore raw
Quoted 3 lines · Linus Torvalds

I have yet to see any actual *reasons* for licensing under the GPLv3, though.

Btw, if Sun really _is_ going to release OpenSolaris under GPLv3, that _may_ be a good reason. I don't think the GPLv3 is as good a license as v2, but on the other hand, I'm pragmatic, and if we can avoid having two kernels with two different licenses and the friction that causes, I at least see the _reason_ for GPLv3. As it is, I don't really see a reason at all.

I personally doubt it will happen, but hey, I didn't really expect them to open-source Java either(*), so it's not like I'm infallible in my predictions.

Linus

(*) And I've been pushing for that since before they even released it - I walked out on Bill Joy at a private event where they discussed their horrible previous Java license.

#21 lore raw
Quoted 5 lines · Linus Torvalds
Quoted 2 lines · Linus Torvalds

I have yet to see any actual *reasons* for licensing under the GPLv3, though.

Quoted 8 lines

Btw, if Sun really _is_ going to release OpenSolaris under GPLv3, that _may_ be a good reason. I don't think the GPLv3 is as good a license as v2, but on the other hand, I'm pragmatic, and if we can avoid having two kernels with two different licenses and the friction that causes, I at least see the _reason_ for GPLv3. As it is, I don't really see a reason at all.

I personally doubt it will happen, but hey, I didn't really expect them to open-source Java either(*), so it's not like I'm infallible in my predictions.

Linus

(*) And I've been pushing for that since before they even released it - I walked out on Bill Joy at a private event where they discussed their horrible previous Java license.

Thanks for making things more clear :-) Some really strong indications that Sun is very willing to,at least, "Dual-License" the OpenSolaris with GPLv3. I think; in a very short time; we will see when the GPLv3 finalized and released.

Regards,

Tarkan

#22 lore raw
Quoted 8 lines · Tarkan Erimer
Quoted 3 lines

(*) And I've been pushing for that since before they even released it - I walked out on Bill Joy at a private event where they discussed their horrible previous Java license.

Thanks for making things more clear :-) Some really strong indications that Sun is very willing to,at least, "Dual-License" the OpenSolaris with GPLv3. I think; in a very short time; we will see when the GPLv3 finalized and released.

that would certainly be a good and productive move from them. Note the issue that others have pointed out to you: OpenSolaris is probably more interested in picking up code from Linux than the other way around! :-) You mentioned "dtrace" and "ZFS". Firstly, Linux already has a "dtrace" equivalent. Secondly, ZFS might be interesting in theory, although our prior experience of having compatibly-licensed filesystems ported over to Linux has been pretty negative: XFS ended up being an integration nightmare - and that doesnt have to do anything with the qualities of XFS (it's one of the cleanest Linux filesystems, if not the cleanest), the problem is that components within a kernel are very tightly integrated and rarely does it make sense to port over more than just drivers or maybe libraries. And that's i guess what OpenSolaris lacks and which i suspect it is mostly interested in: lots of nice Linux drivers ;-) XFS, the largest Linux filesystem is 100K lines of code - and ZFS (i've never seen it) is very likely smaller than that. Linux drivers on the other hand, as of today, are _3.7 million_ lines of code and enable Linux to run on 99% of the hardware that is produced today. Guess which one has the larger strategic significance? ;-)

Ingo

#23 lore raw
Quoted 12 lines · Ingo Molnar
Quoted 8 lines · Tarkan Erimer
Quoted 3 lines

(*) And I've been pushing for that since before they even released it - I walked out on Bill Joy at a private event where they discussed their horrible previous Java license.

Thanks for making things more clear :-) Some really strong indications that Sun is very willing to,at least, "Dual-License" the OpenSolaris with GPLv3. I think; in a very short time; we will see when the GPLv3 finalized and released.

Quoted 5 lines

that would certainly be a good and productive move from them. Note the issue that others have pointed out to you: OpenSolaris is probably more interested in picking up code from Linux than the other way around! :-) You mentioned "dtrace" and "ZFS". Firstly, Linux already has a "dtrace" equivalent. Secondly, ZFS might be interesting in theory

                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Having just got my first Sun box (one of those 48 disk Thumper machines) I can say it's very interesting in practice too. The admin tools for zfs are a dream to use (unlike just about everything else on Solaris which is a bugwards compatible nightmare to use) and the attitude of checksumming everything on to disk and checking that those checksums match on the way back out presses my "do your own safety checking and don't trust the hardware" buttons very much the right way - especially with that much hardware in there.

I would love to see Sun GPL3 OpenSolaris, not so much for the code itself (maybe not portable into Linux) but for the clarity it would give to the patent position. The patent peace would be portable back to GPL2.

Bron.

#24 lore raw
In reply to Ingo Molnar
Quoted 10 lines · Ingo Molnar
Quoted 4 lines · Tarkan Erimer
Quoted 2 lines

(*) And I've been pushing for that since before they even released it - I walked out on Bill Joy at a private event where they discussed their horrible previous Java license.

Thanks for making things more clear :-) Some really strong indications that Sun is very willing to,at least, "Dual-License" the OpenSolaris with GPLv3. I think; in a very short time; we will see when the GPLv3 finalized and released.

that would certainly be a good and productive move from them. Note the issue that others have pointed out to you: OpenSolaris is probably more interested in picking up code from Linux than the other way around! :-)

Totally agreed :-)

Quoted 4 lines

You mentioned "dtrace" and "ZFS". Firstly, Linux already has a "dtrace" equivalent. Secondly, ZFS might be interesting in theory, although our prior experience of having compatibly-licensed filesystems ported over to Linux has been pretty negative: XFS ended up being an integration nightmare - and that doesnt have to do anything with the qualities of XFS (it's one of the cleanest Linux filesystems, if not the cleanest), the problem is that components within a kernel are very tightly integrated and rarely does it make sense to port over more than just drivers or maybe libraries. And that's i guess what OpenSolaris lacks and which i suspect it is mostly interested in: lots of nice Linux drivers ;-) XFS, the largest Linux filesystem is 100K lines of code - and ZFS (i've never seen it) is very likely smaller than that. Linux drivers on the other hand, as of today, are _3.7 million_ lines of code and enable Linux to run on 99% of the hardware that is produced today. Guess which one has the larger strategic significance? ;-)

Ingo

Yep, it is clear that sun needs more things like drivers etc. to make OpenSolaris more usable and user friendly. Here is an article about this subject and some thoughts of Ian (Murdock) about it ;-)

http://www.zdnet.com.au/news/software/soa/Sun-hopes-for-Linux-like-Solaris/0,130061733,339276057,00.htm

#25 lore raw
In reply to Ingo Molnar
Quoted 7 lines · Ingo Molnar

And that's i guess what OpenSolaris lacks and which i suspect it is mostly interested in: lots of nice Linux drivers ;-) XFS, the largest Linux filesystem is 100K lines of code - and ZFS (i've never seen it) is very likely smaller than that. Linux drivers on the other hand, as of today, are _3.7 million_ lines of code and enable Linux to run on 99% of the hardware that is produced today. Guess which one has the larger strategic significance? ;-)

Per this reasoning, Sun wouldn't be waiting for GPLv3, and it would have already released the OpenSolaris kernel under GPLv2, would it not? ;-)

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}
#26 lore raw
Quoted 4 lines · Alexandre Oliva

Per this reasoning, Sun wouldn't be waiting for GPLv3, and it would have already released the OpenSolaris kernel under GPLv2, would it not? ;-)

Umm. You are making the fundamental mistake of thinking that Sun is in this to actually further some open-source agenda.

Here's a cynical prediction (but backed up by past behaviour of Sun):

- first off: they may be talking a lot more than they are or ever will be doing. How many announcements about Sun and Linux have you seen over the years? And how much of that has actually happened?

- They may like open source, but Linux _has_ hurt them in the marketplace. A lot.

They almost used to own the chip design market, and it took quite a long time before the big EDA vendors ported to Linux (and x86-64 in particular). But when they did, their chip design market just basically
disappeared: sparc performance is so horribly bad (especially on a workstation kind of setup), that to do chip design on them is just idiotic. Which is not to say that there aren't holdouts, but let's face it, for a lot of things, Solaris is simply the wrong choice these days.

Ergo: they sure as hell don't want to help Linux. Which is fine. Competition is good.

- So they want to use Linux resources (_especially_ drivers), but they do *not* want to give anything back (especially ZFS, which seems to be one of their very very few bright spots).

- Ergo: they'll not be releasing ZFS and the other things that people are drooling about in a way that lets Linux use them on an equal footing. I can pretty much guarantee that. They don't like competition on that level. They'd *much* rather take our drivers and _not_ give anythign back, or give back the stuff that doesn't matter (like core Solaris:
who are you kidding - Linux code is _better_).

End result:

- they'll talk about it. They not only drool after our drivers, they drool after all the _people_ who write drivers. They'd love to get kernel developers from Linux, they see that we have a huge amount of really talented people. So they want to talk things up, and the more "open source" they can position themselves, the better.

- They may release the uninteresting parts under some fine license. See the OpenSolaris stuff - instead of being blinded by the code they _did_ release under an open source license, ask yourself what they did *not* end up releasing. Ask yourself why the open source parts are not ready to bootstrap a competitive system, or why they are released under licenses that Sun can make sure they control.

So the _last_ thing they want to do is to release the interesting stuff under GPLv2 (quite frankly, I think the only really interesting thing they have is ZFS, and even there, I suspect we'd be better off talking to NetApp, and seeing if they are interested in releasing WAFL for Linux).

Yes, they finally released Java under GPLv2, and they should be commended for that. But you should also ask yourself why, and why it took so long. Maybe it had something to do with the fact that other Java implementations started being more and more relevant?

Am I cynical? Yes. Do I expect people to act in their own interests? Hell yes! That's how things are _supposed_ to happen. I'm not at all berating Sun, what I'm trying to do here is to wake people up who seem to be living in some dream-world where Sun wants to help people.

So to Sun, a GPLv3-only release would actually let them look good, and still keep Linux from taking their interesting parts, and would allow them to take at least parts of Linux without giving anything back (ahh, the joys of license fragmentation).

Of course, they know that. And yes, maybe ZFS is worthwhile enough that I'm willing to go to the effort of trying to relicense the kernel. But quite frankly, I can almost guarantee that Sun won't release ZFS under the GPLv3 even if they release other parts. Because if they did, they'd lose the patent protection.

And yes, I'm cynical, and yes, I hope I'm wrong. And if I'm wrong, I'll very happily retract anything cynical I said about Sun. They _have_ done great things, and maybe I'm just too pessimistic about all the history I've seen of Sun with open source.

The _good_ news is that Jonathan Schwartz actually does seem to have made a difference, and I hope to God he is really as serious about open-sourcing things as he says he is. And don't get me wrong: I think a truly open-source GPLv3 Solaris would be a really really _good_ thing, even if it does end up being a one-way street as far as code is concerned!

Linus

#27 lore raw
Quoted 8 lines · Linus Torvalds
Quoted 4 lines · Alexandre Oliva

Per this reasoning, Sun wouldn't be waiting for GPLv3, and it would have already released the OpenSolaris kernel under GPLv2, would it not? ;-)

Umm. You are making the fundamental mistake of thinking that Sun is in this to actually further some open-source agenda.

Err, no. I was merely questioning Ingo's reasoning that Sun wanted Linux's drivers as badly as he made it seem. All the fuss about waiting for and going to GPLv3 wouldn't get them that. Moving to GPLv2 would, and still, they aren't doing it. That was my point.

FWIW, I share most of your assessment and wait-and-see attitude about Sun's situation.

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}
#28 lore raw
In reply to Linus Torvalds

El Tue, Jun 12, 2007 at 08:45:46AM -0700 Linus Torvalds ha dit:

Quoted 28 lines · Alexandre Oliva
Quoted 4 lines

Per this reasoning, Sun wouldn't be waiting for GPLv3, and it would have already released the OpenSolaris kernel under GPLv2, would it not? ;-)

Umm. You are making the fundamental mistake of thinking that Sun is in this to actually further some open-source agenda.

Here's a cynical prediction (but backed up by past behaviour of Sun):

- first off: they may be talking a lot more than they are or ever will be doing. How many announcements about Sun and Linux have you seen over the years? And how much of that has actually happened?

- They may like open source, but Linux _has_ hurt them in the marketplace. A lot.

They almost used to own the chip design market, and it took quite a long time before the big EDA vendors ported to Linux (and x86-64 in particular). But when they did, their chip design market just basically
disappeared: sparc performance is so horribly bad (especially on a workstation kind of setup), that to do chip design on them is just idiotic. Which is not to say that there aren't holdouts, but let's face it, for a lot of things, Solaris is simply the wrong choice these days.

Quoted 1 line

Ergo: they sure as hell don't want to help Linux. Which is fine.

> Competition is good.

Quoted 58 lines

- So they want to use Linux resources (_especially_ drivers), but they do *not* want to give anything back (especially ZFS, which seems to be one of their very very few bright spots).

- Ergo: they'll not be releasing ZFS and the other things that people are drooling about in a way that lets Linux use them on an equal footing. I can pretty much guarantee that. They don't like competition on that level. They'd *much* rather take our drivers and _not_ give anythign back, or give back the stuff that doesn't matter (like core Solaris:
who are you kidding - Linux code is _better_).

End result:

- they'll talk about it. They not only drool after our drivers, they drool after all the _people_ who write drivers. They'd love to get kernel developers from Linux, they see that we have a huge amount of really talented people. So they want to talk things up, and the more "open source" they can position themselves, the better.

- They may release the uninteresting parts under some fine license. See the OpenSolaris stuff - instead of being blinded by the code they _did_ release under an open source license, ask yourself what they did *not* end up releasing. Ask yourself why the open source parts are not ready to bootstrap a competitive system, or why they are released under licenses that Sun can make sure they control.

So the _last_ thing they want to do is to release the interesting stuff under GPLv2 (quite frankly, I think the only really interesting thing they have is ZFS, and even there, I suspect we'd be better off talking to NetApp, and seeing if they are interested in releasing WAFL for Linux).

Yes, they finally released Java under GPLv2, and they should be commended for that. But you should also ask yourself why, and why it took so long. Maybe it had something to do with the fact that other Java implementations started being more and more relevant?

Am I cynical? Yes. Do I expect people to act in their own interests? Hell yes! That's how things are _supposed_ to happen. I'm not at all berating Sun, what I'm trying to do here is to wake people up who seem to be living in some dream-world where Sun wants to help people.

So to Sun, a GPLv3-only release would actually let them look good, and still keep Linux from taking their interesting parts, and would allow them to take at least parts of Linux without giving anything back (ahh, the joys of license fragmentation).

Of course, they know that. And yes, maybe ZFS is worthwhile enough that I'm willing to go to the effort of trying to relicense the kernel. But quite frankly, I can almost guarantee that Sun won't release ZFS under the GPLv3 even if they release other parts. Because if they did, they'd lose the patent protection.

And yes, I'm cynical, and yes, I hope I'm wrong. And if I'm wrong, I'll very happily retract anything cynical I said about Sun. They _have_ done great things, and maybe I'm just too pessimistic about all the history I've seen of Sun with open source.

Quoted 6 lines

The _good_ news is that Jonathan Schwartz actually does seem to have made a difference, and I hope to God he is really as serious about open-sourcing things as he says he is. And don't get me wrong: I think a truly open-source GPLv3 Solaris would be a really really _good_ thing, even if it does end up being a one-way street as far as code is concerned!

FYI, Jonathan Schwartz' response:

Linus,

First, I'm glad you give credit to Sun for the contributions we've made to the open source world, and Linux specifically - we take the commitment seriously. It's why we freed OpenOffice, elements of Gnome, Mozilla, delivered Java, and a long list of other contributions that show up in almost every distro. Individuals will always define communities, but Sun as a company has done its part to grow the market
- for others as much as ourselves.

But I disagree with a few of your points. Did the Linux community hurt Sun? No, not a bit. It was the companies that leveraged their work. I draw a very sharp distinction - even if our competition is conveniently reckless. They like to paint the battle as Sun vs. the community, and it's not. Companies compete, communities simply fracture.

And OpenSolaris has come a very long way since you last looked. It and its community are growing, as a result of more than ZFS (although we seem to be generating a lot of interest there, not all intentional) - OpenSolaris scales on any hardware, has built in virtualization, great web service infrastucture, fault management, diagnosability, and tons more. Feel free to try for yourself (and yes, we're fixing installability, no fair knocking us for that.)

Now despite what you suggest, we love where the FSF's GPL3 is headed. For a variety of mechanical reasons, GPL2 is harder for us with OpenSolaris - but not impossible, or even out of the question. This has nothing to do with being afraid of the community (if it was, we wouldn't be so interested in seeing ZFS everywhere, including Linux, with full patent indemnity). Why does open sourcing take so long? Because we're starting from products that exist, in which a diversity of contributors and licensors/licensees have rights we have to negotiate. Indulge me when I say It's different than starting from scratch. I would love to go faster, and we are all doing everything under our control to accelerate progress. (Remember, we can't even pick GPL3 yet - it doesn't officially exist.) It's also a delicate dance to manage this transition while growing a corporation.

But most of all, from where I sit, we should put the swords down - you're not the enemy for us, we're not the enemy for you. Most of the world doesn't have access to the internet - that's the enemy to slay, the divide that separates us. By joining our communities, we can bring transparency and opportunity to the whole planet. Are we after your drivers? No more than you're after ZFS or Crossbow or dtrace - it's not predation, it's prudence. Let's stop wasting time recreating wheels we both need to roll forward.

I wanted you to hear this from me directly. We want to work together, we want to join hands and communities - we have no intention of holding anything back, or pulling patent nonsense. And to prove the sincerity of the offer, I invite you to my house for dinner. I'll cook, you bring the wine. A mashup in the truest sense.

Best,
Jonathan

President, Chief Executive Officer,
Sun Microsystems, Inc.

http://blogs.sun.com/jonathan/entry/one_plus_one_is_fifty

Signature · 11 lines
Matthias Kaehlcke
Linux Application Developer
Barcelona

    Yo soy como soy y tú eres como eres, construyamos un mundo donde yo
    pueda ser sin dejar de ser yo, donde tú puedas ser sin dejar de ser
    tú, y donde ni yo ni tú obliguemos al otro a ser como yo o como tú
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
#29 lore raw
Quoted 8 lines · Matthias Kaehlcke

FYI, Jonathan Schwartz' response:

I wanted you to hear this from me directly. We want to work together, we want to join hands and communities - we have no intention of holding anything back, or pulling patent nonsense. And to prove the sincerity of the offer, I invite you to my house for dinner. I'll cook, you bring the wine. A mashup in the truest sense.

Quoted 9 lines

Best,
Jonathan

President, Chief Executive Officer,
Sun Microsystems, Inc.

http://blogs.sun.com/jonathan/entry/one_plus_one_is_fifty

Really very very interesting! This words reminded me the same dialogues and affair, between "Linus" and "Steve Jobs", that have been happened several years ago :-)

Regards,

Tarkan

#30 lore raw
In reply to Linus Torvalds

Hi Linus,

Quoted 33 lines · Linus Torvalds
Quoted 4 lines · Alexandre Oliva

Per this reasoning, Sun wouldn't be waiting for GPLv3, and it would have already released the OpenSolaris kernel under GPLv2, would it not? ;-)

Umm. You are making the fundamental mistake of thinking that Sun is in this to actually further some open-source agenda.

Here's a cynical prediction (but backed up by past behaviour of Sun):

- first off: they may be talking a lot more than they are or ever will be doing. How many announcements about Sun and Linux have you seen over the years? And how much of that has actually happened?

- They may like open source, but Linux _has_ hurt them in the marketplace. A lot.

They almost used to own the chip design market, and it took quite a long time before the big EDA vendors ported to Linux (and x86-64 in particular). But when they did, their chip design market just basically
disappeared: sparc performance is so horribly bad (especially on a workstation kind of setup), that to do chip design on them is just idiotic. Which is not to say that there aren't holdouts, but let's face it, for a lot of things, Solaris is simply the wrong choice these days.

Ergo: they sure as hell don't want to help Linux. Which is fine. Competition is good.

- So they want to use Linux resources (_especially_ drivers), but they do *not* want to give anything back (especially ZFS, which seems to be one of their very very few bright spots).

Quoted 8 lines

- Ergo: they'll not be releasing ZFS and the other things that people are drooling about in a way that lets Linux use them on an equal footing. I can pretty much guarantee that. They don't like competition on that level. They'd *much* rather take our drivers and _not_ give anythign back, or give back the stuff that doesn't matter (like core Solaris:
who are you kidding - Linux code is _better_).

Completely agreed :-)

Quoted 9 lines

End result:

- they'll talk about it. They not only drool after our drivers, they drool after all the _people_ who write drivers. They'd love to get kernel developers from Linux, they see that we have a huge amount of really talented people. So they want to talk things up, and the more "open source" they can position themselves, the better.

Definitely. They already began to pull some people like Ian Murdock. And I'm really very disappointed of this move,Ian did. Especially, such a person who has very good reputation and high profile in the Linux Community. He immediately shut down his company (also leaved Linux-Foundation) and joined to sun. After joining, he made statements like "How to make Solaris more like Linux ?" etc. Like a 40 years employee at Sun. Another interesting thing is the timing of this hiring. So, this situation is a good example of it.

Quoted 15 lines

- They may release the uninteresting parts under some fine license. See the OpenSolaris stuff - instead of being blinded by the code they _did_ release under an open source license, ask yourself what they did *not* end up releasing. Ask yourself why the open source parts are not ready to bootstrap a competitive system, or why they are released under licenses that Sun can make sure they control.

So the _last_ thing they want to do is to release the interesting stuff under GPLv2 (quite frankly, I think the only really interesting thing they have is ZFS, and even there, I suspect we'd be better off talking to NetApp, and seeing if they are interested in releasing WAFL for Linux).

Yes, they finally released Java under GPLv2, and they should be commended for that. But you should also ask yourself why, and why it took so long. Maybe it had something to do with the fact that other Java implementations started being more and more relevant?

Am I cynical? Yes. Do I expect people to act in their own interests? Hell yes! That's how things are _supposed_ to happen. I'm not at all berating Sun, what I'm trying to do here is to wake people up who seem to be living in some dream-world where Sun wants to help people.

So to Sun, a GPLv3-only release would actually let them look good, and still keep Linux from taking their interesting parts, and would allow them to take at least parts of Linux without giving anything back (ahh, the joys of license fragmentation).

Quoted 8 lines

Of course, they know that. And yes, maybe ZFS is worthwhile enough that I'm willing to go to the effort of trying to relicense the kernel. But quite frankly, I can almost guarantee that Sun won't release ZFS under the GPLv3 even if they release other parts. Because if they did, they'd lose the patent protection.

And yes, I'm cynical, and yes, I hope I'm wrong. And if I'm wrong, I'll very happily retract anything cynical I said about Sun. They _have_ done great things, and maybe I'm just too pessimistic about all the history I've seen of Sun with open source.

The _good_ news is that Jonathan Schwartz actually does seem to have made a difference, and I hope to God he is really as serious about open-sourcing things as he says he is. And don't get me wrong: I think a truly open-source GPLv3 Solaris would be a really really _good_ thing, even if it does end up being a one-way street as far as code is concerned!

Linus

One more time,agreed ;-)

Regards,

Tarkan

#31 lore raw
In reply to Linus Torvalds
Quoted 2 lines

licensing under the GPLv3, though. All I've heard are shrill voices about "tivoization" (which I expressly think is ok) and panicked worries about

GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not yours 8)

#32 lore raw
Quoted 4 lines · Alan Cox
Quoted 2 lines

licensing under the GPLv3, though. All I've heard are shrill voices about "tivoization" (which I expressly think is ok) and panicked worries about

GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not

             ^^^^^^^^

Now that is a bit waving in the air. GPLv2 forbids Tivoisation theoretically but practically it didnt stop them doing it practically. I agree with Linus that software licenses should have their influence only on the software part and leave the freedom of the hardware on which the software runs to the hardware manufacturers.

But was it the goal of GPLv2??

And what does Andrew Morton think of all this? I really want to know his opinions....

#33 lore raw
Quoted 2 lines · On Mon, 11 Jun 2007 01:02:42 +0530 "debian developer" <[email protected]>…

And what does Andrew Morton think of all this? I really want to know his opinions....

I have yet to see Linus make a statement on these matters with which I didn't agree.

#34 lore raw
In reply to debian developer
Quoted 5 lines
Quoted 1 line

GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not

              ^^^^^^^^

Now that is a bit waving in the air. GPLv2 forbids Tivoisation theoretically but practically it didnt stop them doing it practically.

They've never been given permission and there is no caselaw yet, doesn't mean they are allowed to.

GPL2 actually in some ways was saner than GPL3 on this - you could sensibly argue the key was part of the source/build environment but it didn't then get muddled in with questions like ROMs which the new GPL3 wording is a bit messy about still.

Alan

#35 lore raw
Quoted 8 lines · Alan Cox
Quoted 5 lines
Quoted 1 line

GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not

              ^^^^^^^^

Now that is a bit waving in the air. GPLv2 forbids Tivoisation theoretically but practically it didnt stop them doing it practically.

They've never been given permission and there is no caselaw yet, doesn't mean they are allowed to.

Are you sure? Tivo went and got a FSF "verification" of their system a number of years ago and got their blessing that what they were doing was just fine with regards to the GPLv2.

This is one reason Tivo's lawyers were so perplexed when the FSF then turned around and made their company's name into a term to describe DRM stuff and started preaching how it was so bad. It seemed to be in direct crontridiction from what they had previously been told by the very same people.

Now yes, they didn't consult with the individual owners of the kernel, who might hold different views as to if v2 covers keys like you have stated in the past, but the FSF's position in this area does hold some ammount of weight, especially in court if it were to come to that.

thanks,

greg k-h

#36 lore raw
Quoted 4 lines

Now yes, they didn't consult with the individual owners of the kernel, who might hold different views as to if v2 covers keys like you have stated in the past, but the FSF's position in this area does hold some ammount of weight, especially in court if it were to come to that.

The authors position does have rather a lot of weight too. Especially as they have been made plain to Tivo and various other relevant parties.

Alan

#37 lore raw
In reply to debian developer
Quoted 11 lines · On Sunday 10 June 2007 15:32:42 debian developer wrote:
Quoted 5 lines · Alan Cox
Quoted 3 lines

licensing under the GPLv3, though. All I've heard are shrill voices about "tivoization" (which I expressly think is ok) and panicked worries about

GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not

              ^^^^^^^^

Now that is a bit waving in the air. GPLv2 forbids Tivoisation theoretically but practically it didnt stop them doing it practically.

A law never stops anybody from doing anything. Enforcing the law does.

First of all, let's not confuse civil with criminal law:

http://nielsenhayden.com/makinglight/archives/009034.html

Quoted 3 lines

The difference between tort—breach of private rights—and crime—commission
of an offence designated as such by the State—is one of the key legal concepts which the pro lawyer understands and the fan lawyer does not

Most variants of copyright infringement are a civil, not criminal matter. This means the state has no interest in enforcing the, it's your job to sue for damages and a restraining order if you want to exercise these rights (some people choose not to), and you have to have standing (I.E. be a holder of one of the infringed copyrights, or a designated legal representative thereof) in order to sue. If none of the copyright holders sue to stop it, then it doesn't get stopped no matter how blatantly infringing it is. Did anybody even bother to send Tivo a cease and desist?

Erik Andersen burned himself out trying to enforce the copyrights on BusyBox before Pamela Jones hooked that project (and uClibc) up with the SFLC. Harald Welte's been burning the candle at both ends with gpl-violations.org, but he's focusing on stuff sold in Germany.

As for anti-tivoisation, you can make a case that your signed binary is a derived work of the GPL source code just like a non-signed binary is, therefore the signing key is part of the source code used to create that binary, therefore GPLv2 requires the signing key be handed over on request. (I don't know if you'd WIN, I just know you could reasonably argue it in court and probably get past the inevitable initial motions to dismiss.)

GPLv2 is a nice, elegant license. It's not perfect but it's very simple for what it does.

GPLv3 is not simple, not elegant, and contains numerous of special cases. Lots of the programmers here have an instinctive aversion to it because it reads like bad code. We don't necessarily have to program in legalese to sense bad code in that language, at least compared to a "good code" example we've been using for some time.

Rob

#39 lore raw
In reply to Linus Torvalds

Linus Torvalds wrote:
[ snip ]

Quoted 1 line

I consider dual-licensing unlikely (and technically quite hard), but at least _possible_ in theory. I have yet to see any actual *reasons* for licensing under the GPLv3, though.

[ snip ]

One thing that would make that easier in the future is if contributers at least started to dual-license their submissions. I.e. if instead of "GPL version 2", one could say "GPL version 2 or GPL version 3". It isn't the same thing as the problematic "GPL version 2 or later", because the developer is not agreeing to an unseen license (GPLv4, etc). What it does do is make it easier to move to GPLv3 a few years from now, if that is decided then, as a significant fraction of the code will already be GPLv3 compatible. That way, if a reason is ever found to move to v3, at least some of the work will already be done.

- Jim Bruce

#40 lore raw
Quoted 7 lines · James Bruce

Linus Torvalds wrote:
[ snip ]

Quoted 3 lines

I consider dual-licensing unlikely (and technically quite hard), but at least _possible_ in theory. I have yet to see any actual *reasons* for licensing under the GPLv3, though.

[ snip ]

Quoted 10 lines

One thing that would make that easier in the future is if contributers at least started to dual-license their submissions. I.e. if instead of "GPL version 2", one could say "GPL version 2 or GPL version 3". It isn't the same thing as the problematic "GPL version 2 or later", because the developer is not agreeing to an unseen license (GPLv4, etc). What it does do is make it easier to move to GPLv3 a few years from now, if that is decided then, as a significant fraction of the code will already be GPLv3 compatible. That way, if a reason is ever found to move to v3, at least some of the work will already be done.

Good luck convincing all contributors to do that.

Personally I'm happy with GPL v2, and I for one won't be dual-licensing anything I contribute until I see a clear benefit of doing so (and I don't yet).

In any case, this whole debate is still a bit premature since GPL v3 has not even arrived in its final form yet.

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
#41 lore raw
Quoted 11 lines · Jesper Juhl
Quoted 10 lines

One thing that would make that easier in the future is if contributers at least started to dual-license their submissions. I.e. if instead of "GPL version 2", one could say "GPL version 2 or GPL version 3". It isn't the same thing as the problematic "GPL version 2 or later", because the developer is not agreeing to an unseen license (GPLv4, etc). What it does do is make it easier to move to GPLv3 a few years from now, if that is decided then, as a significant fraction of the code will already be GPLv3 compatible. That way, if a reason is ever found to move to v3, at least some of the work will already be done.

Good luck convincing all contributors to do that.

Well, it's something that pro-GPLv3 people can do right now, instead of just lobbying/complaining. Given 1000 developers, if 400 start dual licensing now, and down the road some compelling reason for GPLv3 does arise (read: a lawsuit with teeth), that's 600 people you need to contact/convince to change, not 1000. This is made more interesting by that fact that 40% of the kernel code is already "GPLv2 or later", as someone else pointed out.

Quoted 3 lines

Personally I'm happy with GPL v2, and I for one won't be dual-licensing anything I contribute until I see a clear benefit of doing so (and I don't yet).

Well, all my personal (non-kernel) stuff is still GPLv2 only right now (Linus' opinion is what convinced me that "or later" is dumb), and like many I disliked the original GPLv3 draft. I'm willing to wait until the final one is out though, and I think my libraries will end up being dual-licensed, with contributions required to be dual-licensed. I want to avoid v3 lock-in, but I don't want to cripple v3 projects either.

Quoted 2 lines

In any case, this whole debate is still a bit premature since GPL v3 has not even arrived in its final form yet.

Agreed.

- Jim Bruce

#42 lore raw
In reply to Linus Torvalds

* Linus Torvalds:

Quoted 4 lines

I consider dual-licensing unlikely (and technically quite hard), but at least _possible_ in theory. I have yet to see any actual *reasons* for licensing under the GPLv3, though. All I've heard are shrill voices about "tivoization" (which I expressly think is ok)

In a strange twist, the last-call draft contains a clause that expressly permits some forms of "tivoization", provided a suitable contractual arrangement exists ("Basic Permissions", second paragraph).

Now a lot of the free software market follows this "sell yourself into slavery" model (and even the FSF recommends to make money this way), but I'm not sure if it's a good idea to state it so plainly in the license.

#43 lore raw
In reply to Tarkan Erimer
Quoted 29 lines · Tarkan Erimer
Quoted 24 lines · debian developer
Quoted 14 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright

owner can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law

orders at

Quoted 6 lines
Quoted 5 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better

idea to

Quoted 8 lines
Quoted 1 line

replace the code of this person as said before instead of waiting

such 90+

Quoted 1 line

years!

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Quoted 4 lines

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

Quoted 8 lines

Yep, the GPLv3 probably will release around July time. So;luckily, we had very little time to see the final decision about it :-) I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). So,we should have more fruits (like ZFS,DTrace etc.) ;-)

I don't think that upgrading to GPLv3 just for the sake of tools present in some other software should be the reason. We are capable enough of developing our own tools, and many experienced people are working on equivalent(etx4 etc.,) and much sophisticated tools for the linux kernel.

#44 lore raw
Quoted 5 lines · debian developer

I don't think that upgrading to GPLv3 just for the sake of tools present in some other software should be the reason. We are capable enough of developing our own tools, and many experienced people are working on equivalent(etx4 etc.,) and much sophisticated tools for the linux kernel.

I don't think that switch to GPLv3 can be described as upgrade. I certainly have no intention to do that to my code; some of it I might release under BSD license, and that can be used in any project. The rest of the kernel stuff I've done (and that's the majority of my contributions) is under GPLv2 *only*.

#45 lore raw
In reply to debian developer
Quoted 39 lines · debian developer
Quoted 30 lines · Tarkan Erimer
Quoted 12 lines · debian developer
Quoted 11 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright

owner can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law

orders at

Quoted 4 lines
Quoted 4 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 1 line

David Lang

Hmm... Really,it is damn too much time to wait! It's really better

idea to

Quoted 1 line

replace the code of this person as said before instead of waiting

such 90+

Quoted 1 line

years!

exactly, however as others are pointing out, there are a lot of

active

Quoted 8 lines
Quoted 3 lines

developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

Quoted 8 lines

Yep, the GPLv3 probably will release around July time. So;luckily, we had very little time to see the final decision about it :-) I hope we should upgrade to GPLv3 and Sun should "Dual License" the OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.). So,we should have more fruits (like ZFS,DTrace etc.) ;-)

Quoted 5 lines

I don't think that upgrading to GPLv3 just for the sake of tools present in some other software should be the reason. We are capable enough of developing our own tools, and many experienced people are working on equivalent(etx4 etc.,) and much sophisticated tools for the linux kernel.

It is not because of the sake of the tools and we have no capable enough developers. It's just about an example that came to my mind, as I mentioned before and also,it is the same thing as we, all the time, did. I mean getting and sharing codes from many different open source projects like BSD and countless others. So, OpenSolaris makes no difference at this.

Regards,

Tarkan

#46 lore raw
In reply to debian developer
Quoted 19 lines · debian developer
Quoted 18 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright owner

can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders

at

Quoted 6 lines
Quoted 5 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better idea

to

Quoted 1 line

replace the code of this person as said before instead of waiting such

90+

Quoted 1 line

years!

Quoted 8 lines
Quoted 3 lines

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

"future steps"? Hah.

My code is going to stay GPLv2 as the v3 license is horrible for kernel code for all of the reasons I have said in the past, plus a few more (what, I can make an "industrial" product but not a commercial one? That's horrible...)

thanks,

greg k-h

#47 lore raw
Quoted 29 lines · Greg KH
Quoted 19 lines · debian developer
Quoted 18 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright owner

can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law orders

at

Quoted 6 lines
Quoted 5 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better idea

to

Quoted 1 line

replace the code of this person as said before instead of waiting such

90+

Quoted 1 line

years!

Quoted 8 lines
Quoted 3 lines

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better it

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

Quoted 5 lines

"future steps"? Hah.

My code is going to stay GPLv2 as the v3 license is horrible for kernel code for all of the reasons I have said in the past, plus a few more (what, I can make an "industrial" product but not a commercial one?

    ^^^^^^^^^^^^^

What exactly in GPLv3 forbids you from making a commercial product?

#48 lore raw
Quoted 35 lines · debian developer
Quoted 34 lines · Greg KH
Quoted 4 lines · debian developer
Quoted 3 lines · On 6/10/07, [email protected] <[email protected]> wrote:
Quoted 1 line · Tarkan Erimer
Quoted 1 line
Quoted 1 line

And maybe another questions should be : How long a copyright

owner

Quoted 3 lines
Quoted 3 lines

can

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

hold the copyright, if died or lost for sometime ? if died, the copyright still should be valid or not ? If lost, what the law

orders

Quoted 7 lines
Quoted 7 lines

at

Quoted 6 lines
Quoted 5 lines
Quoted 1 line

this point for copyright holding ?

I believe that in the US it's life + 90 years.

David Lang

Hmm... Really,it is damn too much time to wait! It's really better

idea

Quoted 2 lines
Quoted 2 lines

to

Quoted 1 line

replace the code of this person as said before instead of waiting

such

Quoted 6 lines
Quoted 6 lines

90+

Quoted 1 line

years!

exactly, however as others are pointing out, there are a lot of active developers who do not agree with some of the key points of the GPLv3 (including Linus), so until you convince them that the GPLv3 is better

it

Quoted 5 lines

Last heard, Linus was quite impressed with the toned down version of the final draft of GPLv3. I think Linus, and other major developers should make their stand on this issue clear so that the kernel community can discuss the future steps.

Quoted 8 lines
Quoted 5 lines

"future steps"? Hah.

My code is going to stay GPLv2 as the v3 license is horrible for kernel code for all of the reasons I have said in the past, plus a few more (what, I can make an "industrial" product but not a commercial one?

     ^^^^^^^^^^^^^

What exactly in GPLv3 forbids you from making a commercial product?

Nothing "forbids" me, it's just the artifical distinstion of the two is, in my opinion, stupid and foolish. You are trying to define use-cases to justify their notion that you must give up the hardware keys for one type of device, yet not for another.

Even the people that feel that v2 says you need to give up the keys think this is dumb. But we've been through all of that before (see previous long thread about v3 and why the kernel developers hate it, it all still applys to the final draft.)

greg k-h

#49 lore raw
Quoted 2 lines · Greg KH

(see previous long thread about v3 and why the kernel developers hate it, it all still applys to the final draft.)

You mean all the misunderstandings? ;-)

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}
#50 lore raw
Quoted 1 line · Alexandre Oliva

You mean all the misunderstandings? ;-)

My impression as well is that there are many misunderstandings, even concerning the status of Linux itself. Linus is much better at kernel hacking than at license issues, and that's true for most other kernel hackers, too - that's why we have Eben Moglen to hack the license.

I want to add my two cents on what I think the legal status of the individual contributions to Linux are. The thing in question is not the GPLv2 itself (which is pretty clear that code without explicit statements is under "any", and if you make an explicit statement, it should read "GPL version two, or (at your option) any later version"), it's this text on the top of /usr/src/linux/COPYING:

"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.

Linus Torvalds"

This text was added in or around 2.4.0-test9, but without asking for permission (neither from the FSF, which has the copyright of the GPL, nor from the other authors of the Linux kernel), and with some controversion afterwards.

This particular comment to how the GPL is applied to the Linux kernel therefore doesn't change the GPL as such (it can't without breaking copyright), neither does it change the licensing conditions the original authors put on their contribution (it can't without breaking copyright, either), but may only provide interpretations downstream (for the user). Linus is also entitled to make clairifications there, which the first paragraph obviously does (i.e. the text Linus added is not a change of the license, but a comment on it).

Again: What Linus is entitled to do is to *select* the license under which he redistributes the code downstream. What he can't do is to *change* the intention of the original author. So if you can choose what this somewhat ambiguous message means, and restrict yourself to reasoning that doesn't go into nonsense or copyright infringement, you'll pretty much come to the conclusion that the only thing Linus could have done back then without asking for permission is the license condition how he *redistributes* the compiled work called "Linux kernel" (it's a "compiled work", because it consists of a compilation of individual files from many authors).

The GPLv2 however is very clear how the end user gets the license: from the original author. Not from the man in the middle, from a distributor or kernel maintainer, who can neither add nor drop restrictions/permissions (and thus the special rights of a compilation editor are void). The author can only speak for himself, not by behalf of somebody else, as well as the compilation editor. That's why the FSF is so strict about having each author stating copyright and the license conditions on the top of the file - nobody else can.

So my conclusion is: If you, as contributor to the Linux kernel, want to make clear that your work really is GPLv2 only, you have to do that yourself, you have to add a notice like above to files where you exclusively own copyright. Very few have done that in the past, most people who *did* explicitely declare what versions of the GPL they want their work under, did choose the default text from the GPLv2, which sais "GPLv2 or later" (most use the GPL text template). The rest (the majority) did not choose to say anything, which under the GPL regime means "any"; and nobody but the author himself can change that (by adding a specific version). Linus can't change the GPL regime, because he can't change the GPL.

So, IMHO and IANAL, technically, there are only a few files in Linux which really can't work in a GPLv2+GPLv3 compiled Linux, and a few files wouldn't be a problem.

Quoted 1 line

From a practical point of view, I fully agree with Linus that there's no

point in switching over to the GPLv3 next month unless there's some valueable contribution out there that's only available under GPLv3 (maybe from OpenSolaris), or the Linux kernel developers understand the GPLv3 better. I don't see this point in the near future.

But what I want to say: The route to GPLv3 is not as blocked as it appears. And the GPLv2 is even better than you think: It paves that road as well: In practice, only projects that have a thight authorship control can really make their project GPLv2 only (like MySQL), and those projects have no problem to change their mind later.

What I don't understand about the GPLv3 with keys is why that depends on the use case. As user of commercial devices like company routers, firewalls and such, which often are Linux based, I don't want them sealed by the vendor, as well. An explicit statement is even worse than an implicit one (as in the GPLv2, which has been tested in a German court by Harald Welte - Siemens had to turn in the keys).

And now flame me to death ;-).

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#51 lore raw
Quoted 4 lines · Bernd Paysan

I want to add my two cents on what I think the legal status of the individual contributions to Linux are. The thing in question is not the GPLv2 itself (which is pretty clear that code without explicit statements is under "any",

That's not exactly true. A work without explicit statements is not licenced at all.

Quoted 2 lines

This particular comment to how the GPL is applied to the Linux kernel therefore doesn't change the GPL as such

Of course.

Quoted 2 lines

Again: What Linus is entitled to do is to *select* the license under which he redistributes the code downstream.

Sure.

Quoted 2 lines

The GPLv2 however is very clear how the end user gets the license: from the original author.

I'd be surprised if it's for GPL to decide.

Quoted 5 lines

Not from the man in the middle, from a distributor or
kernel maintainer, who can neither add nor drop restrictions/permissions (and thus the special rights of a compilation editor are void). The author can only speak for himself, not by behalf of somebody else, as well as the compilation editor.

How about derived works?
Am I free to get BSD source, incorporate it in GPL project, and release the whole under GPL?
Sure, the original source stays BSD but I don't distribute it.

Quoted 3 lines

That's why the FSF is so strict about having each
author stating copyright and the license conditions on the top of the file - nobody else can.

I'm not sure the copyright laws define "files".

Quoted 4 lines

So my conclusion is: If you, as contributor to the Linux kernel, want to make clear that your work really is GPLv2 only, you have to do that yourself, you have to add a notice like above to files where you exclusively own copyright.

I don't think the law works like that.
By default you have no rights to someone's work (file or project). The only licence I can find with Linux is GPL v2, isn't it? And even that wasn't stated explicite until that 2.4.0something (though there is a consensus that the COPYING file was indeed a licence for the whole kernel).

Then you may have additional rights, such as those given in various source files.

Quoted 2 lines

The rest (the majority) did not
choose to say anything, which under the GPL regime means "any";

What exactly is the "GPL regime" and how is it defined by copyright law and/or the GPL licence itself (or will of copyright holders etc.)?

Signature · 1 line
Krzysztof Halasa
#52 lore raw
Quoted 4 lines · Krzysztof Halasa
Quoted 2 lines

The GPLv2 however is very clear how the end user gets the license: from the original author.

I'd be surprised if it's for GPL to decide.

If you choose the GPL as license, the text of the GPL are the conditions. Otherwise, the GPL would be pure nonsense (as would be any other license).

Quoted 10 lines
Quoted 5 lines

Not from the man in the middle, from a distributor or kernel maintainer, who can neither add nor drop restrictions/permissions (and thus the special rights of a compilation editor are void). The author can only speak for himself, not by behalf of somebody else, as well as the compilation editor.

How about derived works?
Am I free to get BSD source, incorporate it in GPL project, and release the whole under GPL?
Sure, the original source stays BSD but I don't distribute it.

Derivated work is a product of several authors, therefore each author may put different conditions on his part of the work - as long as they are compatible, it's ok. A derivated work originally under BSD, now with a patch under GPL can only be distributed under GPL, but not under BSD (because GPL requires redistribution under GPL, whereas BSD doesn't care). If you take out the patch, and revert the work to the BSD one, you are free to redistribute it under BSD.

There's no point of discussing that the Linux kernel *as a whole* (as compilation) currently is under GPLv2 only, since it sais so, and a few files also explicitely say so. The whole combination is GPLv2 only, but most parts aren't.

Quoted 5 lines
Quoted 3 lines

That's why the FSF is so strict about having each
author stating copyright and the license conditions on the top of the file - nobody else can.

I'm not sure the copyright laws define "files".

Copyright law defines "work", and in terms of computer programs, source code "work" goes into files. Or patches, but patches end up distributed over several files.

The nice thing about this is that you can make automatic checks about the license you actually have to fulfill. E.g. if you compile a hypothetical Linux 2.8.15.3 without ZFS and dtrace in 2009, you may end up with compiling only GPLv2-compatible code, and therefore can tivoize your system (unless you sell it to Germany, where the GPLv2 outlaws tivoizing by intent), but if you add either ZFS or dtrace, you can't.

Quoted 8 lines
Quoted 4 lines

So my conclusion is: If you, as contributor to the Linux kernel, want to make clear that your work really is GPLv2 only, you have to do that yourself, you have to add a notice like above to files where you exclusively own copyright.

I don't think the law works like that.
By default you have no rights to someone's work (file or project). The only licence I can find with Linux is GPL v2, isn't it?

Yes, and the GPLv2 sais "if the FSF releases a new version of the GPL, you may update" (section 9):

" 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

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."

This is normal contract law (you have to say "yes" to a new M$ EULA every few months or so if you are an unlucky Windows user, and like to use their patches), contracts can change over time. The FSF is rather nice here, they say users and contributors can make choices to which contract they use.

Given that the license you find with Linux is GPLv2, anyway, the comment from Linus seems to be superfluous. The license already says which version it is. But it has this upgrade option, and one possible interpretation of Linus' comment is "no, it doesn't have this update option".

Quoted 5 lines

And even
that wasn't stated explicite until that 2.4.0something (though there is a consensus that the COPYING file was indeed a licence for the whole kernel).

Quoted 8 lines

Then you may have additional rights, such as those given in various source files.

Quoted 2 lines

The rest (the majority) did not
choose to say anything, which under the GPL regime means "any";

What exactly is the "GPL regime" and how is it defined by copyright law and/or the GPL licence itself (or will of copyright holders etc.)?

If I use GPL as license, I'm under "GPL regime", i.e. the terms of the GPL apply. The GPL requires that I need to speak up explicitely if I want to limit the choice of licenses - if I don't say anything, it defaults to "any GPL". This is a restriction that goes from author to user, sinde the GPL cuts away all middle-men (restrictions applied by middle-men can be reverted).

If I decide to build my own compilation of Linux kernel patches* (i.e. a -bp kernel, like the -mm kernel is a different compilation of Linux kernel patches as the mainline kernel), I'm free to choose under which conditions I redistribute it, given that it's compatible with the conditions the original authors have chosen. Most of them have said nothing (other than implicitely that it's ok for them to put it under GPL, as they haven't opposed to inclusion into the Linux kernel), some have said GPLv2 or later, some say GPLv1.1 or later (e.g. the parport driver) and a few have said "GPLv2 only". Now, I may rewrite those few "GPLv2 only" files, and then I have a GPLv2-or later compatible linux-some.version-bp kernel. And into this kernel, I can add code under GPLv3 (once the GPLv3 is ready and there's code worth to add under GPLv3), which limits me to redistribute the whole thing under GPLv3.

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#53 lore raw
Quoted 4 lines · Bernd Paysan

There's no point of discussing that the Linux kernel *as a whole* (as compilation) currently is under GPLv2 only, since it sais so, and a few files also explicitely say so. The whole combination is GPLv2 only, but most parts aren't.

You claim that any source files without a notices are 'any version of the GPL'. But I read the license and you are totally wrong about that.

The GPL applies to "the Program" which in this case is the Linux kernel as a whole and it in fact does indicate a specific version. All code submitted and included in this program has has been submitted with the understanding that the work as a whole is specifically licensed as GPLv2. Some authors have granted additional rights, such as dual BSD/GPL or GPLv2 and later and explicitly added such a notice.

All other code is simply copyrighted, and the only available license is the GPLv2. Take for example fs/inode.c. Notice how it doesn't have GPL boilerplate, but it is clearly indicating that it is copyrighted. So taking that file by itself out of the context of the kernel and then distributing it would clearly be a copyright violation. The only one reason you can distribute that code is because of the GPLv2 that covers the Linux kernel (i.e. "the Program").

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So my conclusion is: If you, as contributor to the Linux kernel, want to make clear that your work really is GPLv2 only, you have to do that yourself, you have to add a notice like above to files where you exclusively own copyright.

The kernel is explicitly licensed as GPLv2, any contributions (source files/parts of the work) that wish to grant additional rights have to specify so explicitly, and not the other way around however much you'd like that.

Quoted 5 lines

patches as the mainline kernel), I'm free to choose under which conditions I redistribute it, given that it's compatible with the conditions the original authors have chosen. Most of them have said nothing (other than implicitely that it's ok for them to put it under GPL, as they haven't opposed to inclusion into the Linux kernel), some have said GPLv2 or later,

Reread section 9 and consider that "the Program" is the Linux kernel, which does explicitly state a version and does not include the "and any later" option. Any source that does not explicitly specify additional rights is GPLv2.

Jan

#54 lore raw
Quoted 7 lines

The GPL applies to "the Program" which in this case is the Linux kernel as a whole and it in fact does indicate a specific version. All code submitted and included in this program has has been submitted with the understanding that the work as a whole is specifically licensed as GPLv2. Some authors have granted additional rights, such as dual BSD/GPL or GPLv2 and later and explicitly added such a notice.

Since the Linux kernel as a whole does not have a single author, it is impossible to license it as a whole. Nobody has the authority to do that. (The GPL is not a copyright assignment type license.)

Fortunately, the GPL clears this up:

"Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."

Linus cannot impose any further restrictions on the recipients' exercise of the rights granted.

When you download a copy of the Linux kernel, you do not receive one license because nobody could grant you one license. You receive a logically separate license from each original licensor. You receive from Linus only a license to his contributions.

Note that you cannot take a GPLv2+ work and redistribute it as GPLv3 only. You can license your contributions as GPLv3 only of course. However, each recipient still receives a GPLv2+ license to the parts that were originally licensed that way. The people you distribute the work from receive licenses from the original licensors to those parts, and you have no right to modify that license. (See GPL section 6, quoted above.)

DS

#55 lore raw
Quoted 10 lines · On Thursday 14 June 2007 15:28:34 David Schwartz wrote:
Quoted 6 lines

The GPL applies to "the Program" which in this case is the Linux kernel as a whole and it in fact does indicate a specific version. All code submitted and included in this program has has been submitted with the understanding that the work as a whole is specifically licensed as GPLv2. Some authors have granted additional rights, such as dual BSD/GPL or GPLv2 and later and explicitly added such a notice.

Since the Linux kernel as a whole does not have a single author, it is impossible to license it as a whole. Nobody has the authority to do that. (The GPL is not a copyright assignment type license.)

Actually, Linus Torvalds, as maintainer, probably has a compilation copyright. See "compilations and abridgements" in
http://www.copyright.gov/circs/circ14.html

Quoted 10 lines

Fortunately, the GPL clears this up:

"Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."

Quoted 2 lines

Linus cannot impose any further restrictions on the recipients' exercise of the rights granted.

If you combine dual licensed code (such as MPL + GPL) with code under only one of those licenses (MPL only), the resulting derived work cannot be distributed under the dual license, only under one license. The giant derived work knows as Linux has only been distributable under exactly one license (GPLv2, the complete text of which is included in the source tarball and it's harder to be more explicit than that about which license you mean) since version 0.12.

By the way, this entire "oh no, we can use it GPLv3 no matter what you say" line of argument is rude. Linus and most of his lieutenants have explicitly said "our contributions are GPLv2 only". Linus said this explicitly seven years ago:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0009.1/0096.html

He confirmed and elaborated his position when people first started pestering about v3:
http://lwn.net/Articles/169825/

In James Bottomley's position paper last year, a number of prominent kernel developers stated their objection and that their contributions were GPLv2 only:
http://lkml.org/lkml/2006/9/22/217

James E.J. Bottomley Mauro Carvalho Chehab
Thomas Gleixner Christoph Hellwig Dave Jones
Greg Kroah-Hartman Tony Luck Andrew Morton
Trond Myklebust David Woodhouse

Let me translate this into simpler terms:

<lolcats>
GPLv3: Does not want!
</lolcats>

The _reason_ it's rude to go on about it is that several people have chosen to see this entire debate as an interesting intellectual exercise, "how much
code could a GPLv3 licensed project lift from the Linux kernel". Yet if you
substitute "BSD Licensed" in there, it's easy to recognize how obnoxious the pestering is, despite much of the code in Linux having come from BSD sources.

You don't take Linux kernel code and stick it into a BSD project, even though some of it was BSD originally, because Linux (every line of it) is GPLv2. If you want the code under a different license, you go to a differently licensed upstream source, such as the original author or the project we adapted it from. If you're not to lift code from Linux to BSD license it, lifting code from Linux to GPLv3 it is morally and legally no different.

Linus made his decision, most of his lieutenants explicitly confirmed that decision. Please admit to yourselves that you're arguing that they should all change their minds because you don't like their decision, not because they didn't have the right to make it or that there's some loophole that invalidates it. What's your argument here, developers who are now saying "GPLv2" _accidentally_ gave permission to distribute their code under other licenses? Go ahead and take that to court buddy: you will lose.

If you want to create a GPLv3 fork and can trace back specific files to authors who are ok with GPLv3, go create your fork. If you want to go work on Solaris, go do that. (But if you want to transplant Linux code into that thing, talk to Sun's lawyers first. And IBM's, and Red Hat's, and...)

If you want each and every Linux developer who has ever stated a GPLv2 only position to either publicly reverse said position or to be ejected from the project and their code tracked down and removed from the kernel via forensic analysis (which is the only way the Linux kernel itself could ever go GPLv3), then do us a favor and shut up.

Quoted 2 lines

When you download a copy of the Linux kernel, you do not receive one license because nobody could grant you one license.

Yes you do, you receive GPLv2. It's in the file "LICENSE" at the top level of the directory. This is the one and only license you receive.

You receive this one license applied to multiple copyrights, but if you're confusing a copyright with a license I can't help you.

Quoted 3 lines

You receive a logically
separate license from each original licensor. You receive from Linus only a license to his contributions.

A) Look up "compilation copyright".

B) The whole point of the GPL is that the license applies to the entire derived work, as a whole. You can either distribute the whole thing under the GPL, or you cannot distribute period. Therefore, you're saying you can take code that was distributed to you under GPLv2 (and only GPLv2), and redistribute it under another set of license terms. In the name of GPLv3, you're trying to weasel around GPLv2. Congratulations, you have achieved hypocrisy.

Rob

#56 lore raw
Quoted 11 lines
Quoted 6 lines

Since the Linux kernel as a whole does not have a single author, it is impossible to license it as a whole. Nobody has the authority to do that.
(The GPL is not a copyright assignment type license.)

Actually, Linus Torvalds, as maintainer, probably has a compilation copyright.
See "compilations and abridgements" in
http://www.copyright.gov/circs/circ14.html

It doesn't matter. He can license you his compilation, but that doesn't license you the underlying elements.

I can make a compilation CD of great works of Rock N' Roll. I can hold a copilation copyright in the compilation. I can license that compilation copryight. That doesn't mean you can make, copy, or sell a CD with my compilation on it, because you are also copying and distributing the original works.

Quoted 4 lines

If you combine dual licensed code (such as MPL + GPL) with code under only one
of those licenses (MPL only), the resulting derived work cannot be distributed under the dual license, only under one license.

That is a common simplification. The GPL is clear that it applies automatically with distribution. If you distribute a GPL'd work (or elements that are GPL'd inside a larger work), those elements are relicensed under the GPL automatically. You *cannot* prevent this from happening.

If I take the Linux kernel, modify it, and then give you a copy, you get a license under GPLv2 from Linus to all of those elements that he placed under the GPL. I cannot stop or modify this. It applies even if I get separate permission from Linus to distribute his contributions under some other conditions.

Quoted 7 lines

The giant
derived work knows as Linux has only been distributable under exactly one license (GPLv2, the complete text of which is included in the source tarball
and it's harder to be more explicit than that about which license you mean)
since version 0.12.

No, not true. I don't have the court citations handy, but it is well-settled law that a right to distribute a derivative work is useless without also having the right to distribute the original work from which the derivative was made.

Quoted 8 lines

By the way, this entire "oh no, we can use it GPLv3 no matter what you say"
line of argument is rude. Linus and most of his lieutenants have explicitly
said "our contributions are GPLv2 only". Linus said this explicitly seven
years ago:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0009.1/0096.html

Huh? I have never argued that any contribution made by Linus could be or had been licensed under GPLv3. Linus has clearly indicated, along with the works that he distributes, that the code is only offered under GPLv2. However, Linus cannot remove rights that other people grant to their code, even if he modifies that code.

Quoted 29 lines

You don't take Linux kernel code and stick it into a BSD project, even though
some of it was BSD originally, because Linux (every line of it) is GPLv2. If
you want the code under a different license, you go to a differently licensed
upstream source, such as the original author or the project we adapted it from. If you're not to lift code from Linux to BSD license it, lifting code
from Linux to GPLv3 it is morally and legally no different.

Linus made his decision, most of his lieutenants explicitly confirmed that
decision. Please admit to yourselves that you're arguing that they should
all change their minds because you don't like their decision, not because they didn't have the right to make it or that there's some loophole that invalidates it. What's your argument here, developers who are now saying "GPLv2" _accidentally_ gave permission to distribute their code under
other licenses? Go ahead and take that to court buddy: you will lose.

If you want to create a GPLv3 fork and can trace back specific files to authors who are ok with GPLv3, go create your fork. If you want to go work
on Solaris, go do that. (But if you want to transplant Linux code into that
thing, talk to Sun's lawyers first. And IBM's, and Red Hat's, and...)

Quoted 9 lines

If you want each and every Linux developer who has ever stated a GPLv2 only
position to either publicly reverse said position or to be ejected from the
project and their code tracked down and removed from the kernel via forensic
analysis (which is the only way the Linux kernel itself could ever go GPLv3),
then do us a favor and shut up.

I don't know who you are talking to or what you are talking about. I haven't seen anybody doing what you claim in this thread or anywhere else and I certainly am not.

Quoted 6 lines
Quoted 2 lines

When you download a copy of the Linux kernel, you do not receive one license because nobody could grant you one license.

Yes you do, you receive GPLv2. It's in the file "LICENSE" at the top level of
the directory. This is the one and only license you receive.

No, not true. Please read and understand GPLv2 section 6. If a work is available under GPLv2+, and you receive that work (even if it's as part of another work) you get it under GPLv2+. Nobody can take rights away.

Quoted 6 lines
Quoted 4 lines

You receive a logically
separate license from each original licensor. You receive from Linus only a
license to his contributions.

A) Look up "compilation copyright".

Do you seriously not understand that a compilation right in "Great Works of Fiction 2002-2006" doesn't give you the right to actually distribute the works in it? You also receive Linus' compilation copyright under GPLv2, but that has no effect on any case except when you wish to distribute the compilation. It isn't enough by itself to distribute the original works.

Quoted 2 lines

B) The whole point of the GPL is that the license applies to the entire derived work, as a whole.

Unfortunately, copyright law makes that impossible without assignment. If I write a work and you add on to it, the resulting work is one we both hold copyright to. Absent any assignment, you would need a license from each of us to distribute the resulting combination.

Quoted 3 lines

You can either distribute the whole
thing under
the GPL, or you cannot distribute period.

Again, wishful thinking. Copyright law does not work that way and that's why GPLv2 section 6 makes it clear that the license does *not* come from the distributor but from the original author. It follows necessarily that if there are multiple authors, there are multiple licenses.

Quoted 4 lines

Therefore, you're
saying you can
take code that was distributed to you under GPLv2 (and only GPLv2), and redistribute it under another set of license terms.

No, that's not what I am saying. I am saying that if I distribute works under GPLv2+ and you redistribute those works or works derived from them, everyone you distribute those works to automatically receives a GPLv2+ license from me. That is what GPLv2 section 6 says, and you cannot modify this process. You cannot take code I licensed under GPLv2+ and distribute it "under GPLv2 only". You cannot interfere with or control the license's grant of rights directly from me to the people you distribute to.

Quoted 4 lines

In the name
of GPLv3,
you're trying to weasel around GPLv2. Congratulations, you have achieved hypocrisy.

I'm not trying to weasel around anything. I'm trying to explain how GPLv2 actually operates. Complying with it and understanding it are not weaseling around.

DS

#57 lore raw
Quoted 3 lines · On Thursday 14 June 2007 18:24:42 David Schwartz wrote:

I don't know who you are talking to or what you are talking about. I haven't seen anybody doing what you claim in this thread or anywhere else and I certainly am not.

I'm asking what is the _point_ of the discussion?

Linux, the project, is available under GPLv2 only. It is not available under
GPLv3, and its maintainers (both Linus, his lieutenants, and numerous other contributors) have expressed an explicit desire NOT to license it as such.

So what are the people talking about GPLv3 trying to accomplish? Are they:

A) Trying to unanimously change the mind of Linus, his lieutentants, and all the other contributors who have spoken up in favor of GPLv2 only, so that future versions of Linux grew a new license? (Doesn't matter if this new license is GPlv3, MPL, or BSD. It's a new license Linux is not currently distributed under. Bits of Linux are separately distributed under other licenses such as BSD, but Linux is not and won't be any time soon.)

B) Proposing the creation of a fork of Linux which identifies and replaces all the code that can't be licensed under GPLv3?

C) Moving to another codebase (Solaris? The Hurd) and trying to identify Linux code that can be ported to that other OS under another license?

D) Blowing smoke to no actual purpose?

Right now, it's looking like D. Is there an E that I'm not seeing?

Rob

#58 lore raw
In reply to David Schwartz
Quoted 29 lines · David Schwartz
Quoted 6 lines

The GPL applies to "the Program" which in this case is the Linux kernel as a whole and it in fact does indicate a specific version. All code submitted and included in this program has has been submitted with the understanding that the work as a whole is specifically licensed as GPLv2. Some authors have granted additional rights, such as dual BSD/GPL or GPLv2 and later and explicitly added such a notice.

Since the Linux kernel as a whole does not have a single author, it is impossible to license it as a whole. Nobody has the authority to do that. (The GPL is not a copyright assignment type license.)

Fortunately, the GPL clears this up:

"Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."

Linus cannot impose any further restrictions on the recipients' exercise of the rights granted.

When you download a copy of the Linux kernel, you do not receive one license because nobody could grant you one license. You receive a logically separate license from each original licensor. You receive from Linus only a license to his contributions.

Quoted 6 lines

Note that you cannot take a GPLv2+ work and redistribute it as GPLv3 only. You can license your contributions as GPLv3 only of course. However, each recipient still receives a GPLv2+ license to the parts that were originally licensed that way. The people you distribute the work from receive licenses from the original licensors to those parts, and you have no right to modify that license. (See GPL section 6, quoted above.)

You have a good point. It can be argued that contributions before 2.4.0-test8 were in fact GPLv2+, but anything after that point has clearly been contributed as GPLv2 only.

So now we have a bunch of pre-2.4.0-test8 code that may possibly be v2+ and files that explicitly state v2+ in their boiler plate. However many of these files may have had additional contributions from other authors which (unless otherwise specified) were GPLv2-only. And because v2 and v3 are incompatible, all those files with v2-only contributions will become v2-only when version 3 is released. Of course it may be that all those copyright owners do not mind re-releasing their copyrighted code as v2+, but they will have to be contacted.

Several maintainers did pay attention to such details. I once submitted a patch that among others touched reiserfs, and I promptly got a friendly email from Hans asking me to sign off any rights he needed to re-release the related code under a different license, so he made sure the combined work wouldn't end up GPLv2 only.

Jan

#59 lore raw
In reply to Bernd Paysan
Quoted 2 lines · Bernd Paysan

If you choose the GPL as license, the text of the GPL are the conditions. Otherwise, the GPL would be pure nonsense (as would be any other license).

The licence can't redefine the copyright laws. It doesn't make it pure nonsense BTW.

Quoted 7 lines

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."

That would be the case if "the Program" (the whole or individual file(s)) contained something like:
"you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation".

Obviously, you could then choose any version including the first one.

Quoted 3 lines

This is normal contract law (you have to say "yes" to a new M$ EULA every few months or so if you are an unlucky Windows user, and like to use their patches),

This is very different (though unrelated) - patches are new work and I hope you're free to use your MS Windows under old conditions if you don't need the new work.

Quoted 2 lines

contracts can change over time. The FSF is rather nice here, they say users and contributors can make choices to which contract they use.

FSF has exactly nothing to say here (except that they've created a useful licence). The author can choose whatever conditions he/she likes.

Quoted 3 lines

Given that the license you find with Linux is GPLv2, anyway, the comment from Linus seems to be superfluous. The license already says which version it is.

It seems so.

Quoted 1 line

But it has this upgrade option, and one possible interpretation of

      ^^
Quoted 1 line

Linus' comment is "no, it doesn't have this update option".

It? What "it"?
I don't get it. If you say the licence is v2 only, then how can it have options?

Quoted 2 lines

If I use GPL as license, I'm under "GPL regime", i.e. the terms of the GPL apply.

First, the local and international laws apply. It's not like selling your soul to the devil.

Quoted 5 lines

The GPL requires that I need to speak up explicitely if I want to limit the choice of licenses - if I don't say anything, it defaults to "any GPL". This is a restriction that goes from author to user, sinde the GPL cuts away all middle-men (restrictions applied by middle-men can be reverted).

... theoretically, by removing their work, perhaps. Back to reality...

Quoted 7 lines

If I decide to build my own compilation of Linux kernel patches* (i.e. a -bp kernel, like the -mm kernel is a different compilation of Linux kernel patches as the mainline kernel), I'm free to choose under which conditions I redistribute it, given that it's compatible with the conditions the original authors have chosen. Most of them have said nothing (other than implicitely that it's ok for them to put it under GPL, as they haven't opposed to inclusion into the Linux kernel),

There is no assumption of "GPL", you can only assume GPL v2 as the kernel is v2. And it's not left for assumptions anymore, see "signed-off-by" and licence tags (though the tags often specify "GPL" when the actual licence, as indicated by the author, is GPL v2).

Quoted 2 lines

Now, I may rewrite those few "GPLv2 only" files, and
then I have a GPLv2-or later compatible linux-some.version-bp kernel.

Sure, you can rewrite all non "GPLv2 or later" code and have v3 Linux. The problem is you think only "few" files are v2.

Signature · 1 line
Krzysztof Halasa
#60 lore raw
Quoted 11 lines · Krzysztof Halasa

It seems so.

Quoted 1 line

But it has this upgrade option, and one possible interpretation of

      ^^
Quoted 1 line

Linus' comment is "no, it doesn't have this update option".

It? What "it"?
I don't get it. If you say the licence is v2 only, then how can it have options?

By section 9. The license is v2, and basically allows to update the license - and it makes this a choice of the user (who also has rights to change stuff and redistribute it).

Quoted 5 lines
Quoted 2 lines

If I use GPL as license, I'm under "GPL regime", i.e. the terms of the GPL apply.

First, the local and international laws apply. It's not like selling your soul to the devil.

Contract law means that first and foremost the contract itself defines the rules, and only if it is not or contradicts the law, the law jumps in. The GPL is not really a contract, it's a license, but the law is not much different here, especially once you accept the GPL. If you put your code under GPL, the text in the GPL is the deal. The law is only the framework under which the deal works.

If you accept the M$ EULA, international law still applies, yet you are selling your soul to the devil (because the EULA sais so).

Quoted 5 lines
Quoted 2 lines

Now, I may rewrite those few "GPLv2 only" files, and
then I have a GPLv2-or later compatible linux-some.version-bp kernel.

Sure, you can rewrite all non "GPLv2 or later" code and have v3 Linux. The problem is you think only "few" files are v2.

Because only few files say so, and they must say what they mean, because GPL is rather clear that if you put a file which doesn't say which version applies under GPL, it's "any GPL". Why is it so difficult to grok section 9 of the current GPLv2, which people claim is well understood?

A number of kernel hacker deliberately want their work under GPLv2 only (like Al Viro), and they are fully entitled to do that - but they must announce it in a propper place (not lkml or lwn.org), and a comment in COPYING signed by Linus Torvalds doesn't seem to be propper to me, especially when the GPLv2 gives a procedure how to do it (look for the
appendix: "How to Apply These Terms to Your New Programs").

There are good reasons to follow the advice there, and those who did follow the advice in the Linux kernel in the vast majority said "GPLv2 or later". Verbatim copy without understanding? Or is it rather that the other people who didn't follow the advice didn't read the GPL, and therefore understand it even less ;-)?

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#61 lore raw
Quoted 3 lines · Bernd Paysan

A number of kernel hacker deliberately want their work under GPLv2 only (like Al Viro), and they are fully entitled to do that - but they must announce it in a propper place (not lkml or lwn.org)

A court deposition if somebody tries to do relicensing. At that point I believe that I made myself sufficiently clear, so I really doubt that "all files without explicit license get the license defendant would like and not the one located in the tree" would fly. But you are welcome to test that, of course - will make for nice punitive damages. Just make sure to test it yourself - giving somebody else an advice that will land them in trouble is not nice...

#62 lore raw
Quoted 10 lines · Al Viro
Quoted 3 lines · Bernd Paysan

A number of kernel hacker deliberately want their work under GPLv2 only (like Al Viro), and they are fully entitled to do that - but they must announce it in a propper place (not lkml or lwn.org)

A court deposition if somebody tries to do relicensing. At that point I believe that I made myself sufficiently clear, so I really doubt that "all files without explicit license get the license defendant would like and not the one located in the tree" would fly. But you are welcome to test that, of course - will make for nice punitive damages.

If I test it, it would be in Germany, and I really doubt that relicensing one copyleft to another can ever cause puntative damages here. You are only entitled to collect damages here when you have actual losses (that's why Harald Welte never gets a dime except for his defense expenses and voluntary donations to the FSF), but you can demand compliance. That would basically mean that the hypothetical linux-something.subversion-bp with GPLv3 parts in it can't be shipped further, because I can't fulfill all my obligations.

It's probably completely hypothetical, but if I really liked to be nasty, I could release the blackfin sound driver I've written for our digital amplifyer under GPLv3 or later. The code I've modified is explicitely under GPLv2 or later.

Quoted 3 lines

Just make
sure to test it yourself - giving somebody else an advice that will land them in trouble is not nice...

As a non-lawyer, I can't give anybody legal advice in Germany, and I'd like to extend that to the rest of the world. This is my opinion, my interpretation of the GPLv2 and what's my logical reasoning what these three lines on top of /usr/src/linux/COPYING really mean. And there are only two possibilities:

* Either it means what it says, then it's quite likely a copyright infingement done by Linus to all those authors of linux-2.4.0-test8 and before, and you all may need to stop distributing Linux*, since you can't meet your obligations (and restart from linux-2.4.0-test8, which is the last legal version), or

* it does not exactly mean what it says, then you still can distribute Linux, but you can't really stop anyone who's updating it to GPLv3 - except for those few files that have explicit version numbers assigned.

BTW: If I grep through Linux, I find two files where you have noted your copyright and the release conditions (GPL v2), and I think last time I did the same thing, I found two GPLv2-files, as well - all other files with "Al Viro" in it apparently have multiple authors. These two files may be the same ones, or maybe there are two other files, making it four in total (or some further I missed, the text of v2 only is not as normed as the text for "v2 or later", but in general it's rare). These files clearly have to be rewritten or premission has to be asked when updating COPYING to GPLv3. But that's not a show-stopper.

Example, to test the legal issue:

/usr/src/linux/drivers/net/bmac.c

is Copyright (C) 1998 Randy Gobbel, and was modified by you in 1999, and has no specific GPL license. That's both before 2.4.0-test9, so without the implied "v2 only" of the "tree root". If I take this file up to GPLv3, what can you do against it? Nothing. What can Randy Gobbel do about it? Nothing, either. If you claim, it's "v2 only", Randy Gobbel could do something (e.g. asking puntative damages from you in the US, or denying you the right to redistribute Linux further, because you don't fulfill your obligations).

*) e.g. Microsoft lawyers will hunt down all pre-2.4.0-test9 copyright holders and pay the one who's willing to stop Linux a billion.

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#63 lore raw
Quoted 9 lines · Bernd Paysan

BTW: If I grep through Linux, I find two files where you have noted your copyright and the release conditions (GPL v2), and I think last time I did the same thing, I found two GPLv2-files, as well - all other files with "Al Viro" in it apparently have multiple authors. These two files may be the same ones, or maybe there are two other files, making it four in total (or some further I missed, the text of v2 only is not as normed as the text for "v2 or later", but in general it's rare). These files clearly have to be rewritten or premission has to be asked when updating COPYING to GPLv3. But that's not a show-stopper.

Rot. "Multiple authors" doesn't get you out of that. If you take a code available under GPLv2 or later and combine it with code under specific version of GPL, result is under than specific version of GPL. If you want to argue against that, make sure to Cc RMS on that, I would really like to hear his opinion.

Multiple authors == need permission from each author with enough contributions to that file to make the contributions in question copyrightable.

And in my case (and case of gregkh, and...) that would be considerably more than a couple of files. Really.

#64 lore raw
Quoted 18 lines · Al Viro
Quoted 9 lines · Bernd Paysan

BTW: If I grep through Linux, I find two files where you have noted your copyright and the release conditions (GPL v2), and I think last time I did the same thing, I found two GPLv2-files, as well - all other files with "Al Viro" in it apparently have multiple authors. These two files may be the same ones, or maybe there are two other files, making it four in total (or some further I missed, the text of v2 only is not as normed as the text for "v2 or later", but in general it's rare). These files clearly have to be rewritten or premission has to be asked when updating COPYING to GPLv3. But that's not a show-stopper.

Rot. "Multiple authors" doesn't get you out of that. If you take a code available under GPLv2 or later and combine it with code under specific version of GPL, result is under than specific version of GPL. If you want to argue against that, make sure to Cc RMS on that, I would really like to hear his opinion.

Quoted 6 lines

Multiple authors == need permission from each author with enough contributions to that file to make the contributions in question copyrightable.

And in my case (and case of gregkh, and...) that would be considerably more than a couple of files. Really.

I would expect that if you contribute to a file that explicitely says "GPL v2 or later" and you do not change that wording then you agree GPL v2 or later for that particular contribution. So for example drivers/net/plip.c could be changed to GPL v3 even though you contributed to it.

Signature · 1 line
Dmitry
#65 lore raw
Quoted 4 lines · Dmitry Torokhov
Quoted 4 lines

Multiple authors == need permission from each author with enough contributions to that file to make the contributions in question copyrightable.

Quoted 8 lines
Quoted 2 lines

And in my case (and case of gregkh, and...) that would be considerably more than a couple of files. Really.

I would expect that if you contribute to a file that explicitely says "GPL v2 or later" and you do not change that wording then you agree GPL v2 or later for that particular contribution. So for example drivers/net/plip.c could be changed to GPL v3 even though you contributed to it.

After you exclude such cases it's still more than a couple of files...

#66 lore raw
Quoted 8 lines · Al Viro
Quoted 7 lines · Dmitry Torokhov
Quoted 6 lines

Multiple authors == need permission from each author with enough contributions to that file to make the contributions in question copyrightable.

And in my case (and case of gregkh, and...) that would be considerably more than a couple of files. Really.

Quoted 8 lines
Quoted 5 lines

I would expect that if you contribute to a file that explicitely says "GPL v2 or later" and you do not change that wording then you agree GPL v2 or later for that particular contribution. So for example drivers/net/plip.c could be changed to GPL v3 even though you contributed to it.

After you exclude such cases it's still more than a couple of files...

Undoubtedly. I was just responding to neet to contact multiple authors point.

Signature · 1 line
Dmitry
#67 lore raw
In reply to Al Viro
Quoted 7 lines · Al Viro
Quoted 6 lines · Dmitry Torokhov
Quoted 6 lines

Multiple authors == need permission from each author with enough contributions to that file to make the contributions in question copyrightable.

And in my case (and case of gregkh, and...) that would be considerably more than a couple of files. Really.

Quoted 7 lines
Quoted 5 lines

I would expect that if you contribute to a file that explicitely says "GPL v2 or later" and you do not change that wording then you agree GPL v2 or later for that particular contribution. So for example drivers/net/plip.c could be changed to GPL v3 even though you contributed to it.

After you exclude such cases it's still more than a couple of files...

FWIW,

$ find -name "*.c" | xargs grep "any later version" | wc -l
3138
$ find -name "*.c" | wc -l
9482

Watching the output of the first grep without "wc -l" shows that, although it is not 100% accurate, it is still ok just to get a rough estimate.

So yes, ~6300 files are definitely more than a couple ;)

Signature · 3 lines
Paulo Marques - www.grupopie.com

"God is love. Love is blind. Ray Charles is blind. Ray Charles is God."
#68 lore raw
Quoted 4 lines · Paulo Marques
$ find -name "*.c" | xargs grep "any later version" | wc -l
3138
$ find -name "*.c" | wc -l
9482

How many of these don't mention version 2?

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}
#69 lore raw
Quoted 9 lines · Alexandre Oliva
Quoted 4 lines · Paulo Marques
$ find -name "*.c" | xargs grep "any later version" | wc -l
3138
$ find -name "*.c" | wc -l
9482

How many of these don't mention version 2?

It does not matter. GPL v2 and later can be reduced to v2 by recepient. Linus did just that so unless individual source file explicitely carries "and later" it is v2.

Signature · 1 line
Dmitry
#70 lore raw
Quoted 3 lines · Dmitry Torokhov

It does not matter. GPL v2 and later can be reduced to v2 by recepient. Linus did just that so unless individual source file explicitely carries "and later" it is v2.

Well, if it said "licenced under GPL" it would mean any GPL. Though it's probably uncommon.

Signature · 1 line
Krzysztof Halasa
#71 lore raw
In reply to Dmitry Torokhov
Quoted 2 lines · Dmitry Torokhov

It does not matter. GPL v2 and later can be reduced to v2 by recepient.

And expanded by the next recipient to GPLv2 or later, as long as the first recipient does not make a substantial modification ("substantial" is a copyright term - there is no precise definition how much must be modified, but a line or two may not count as "substantial"). This is because you receive the license from the original author, not from the man in the middle.

What's still open is how you can change the conditions if you do make substantial changes. My position is: If you modify work (i.e. work with multiple licensors), you are not in a position to change the conditions, since you have to pass on the rights you have (and that included "you may use any GPL" or "you may use GPLv2 or later"). If you create work, you are the only licensor, so you can choose (the created work needs to be sufficiently independent, which e.g. a ZFS from OpenSolaris clearly would be). If you combine work, you can ship the combined work only under a GPL version that matches the common subset, but you cannot change the license of the parts. By adding stuff under GPLv2 only, and then combining the work to a larger work, you may achieve the effect that the larger work is then GPLv2 only. You cannot achieve that people take out the GPLv2 only work, and recombine it for themselves - these people then can choose other license, and combine it e.g. with GPLv3 code.

If you distribute work under multiple possible license, you can also choose which conditions you want to fulfill. But that's not imposing restrictions to the next recipient, so the next recipient can choose again.

It's so simple: Only the author can impose restrictions, everybody else, when using the GPL, has to pass on all the rights he got. If you get a court verdict depends on the law system, and in an anglo-saxonian (roman) system, you might get away by exploiting loopholes, but in a Code Napoleon system, you don't, because exploiting loopholes is not "good faith".

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#72 lore raw
Quoted 11 lines · Bernd Paysan
Quoted 2 lines · Dmitry Torokhov

It does not matter. GPL v2 and later can be reduced to v2 by recepient.

And expanded by the next recipient to GPLv2 or later, as long as the first recipient does not make a substantial modification ("substantial" is a copyright term - there is no precise definition how much must be modified, but a line or two may not count as "substantial"). This is because you receive the license from the original author, not from the man in the middle.

No, you do receive the license from the person or entity you received the program. You have an _option_ to go to the original author and get copy of original code with original license (or maybe other license).

Signature · 1 line
Dmitry
#73 lore raw
Quoted 3 lines

No, you do receive the license from the person or entity you received the program. You have an _option_ to go to the original author and get copy of original code with original license (or maybe other license).

You receive the licence from the original author. The GPL contains no text allowing a third party to grant new licences.

You may well receive the COPYING file from a different party. The licence may well place duties on the person who supplied you but the actual right to use comes from the original author.

#74 lore raw
Quoted 7 lines · Alan Cox
Quoted 3 lines

No, you do receive the license from the person or entity you received the program. You have an _option_ to go to the original author and get copy of original code with original license (or maybe other license).

You receive the licence from the original author. The GPL contains no text allowing a third party to grant new licences.

GPL itself does not. But the author(s) may when they specify "any later version", "dual GPL/BSD", etc. In this case (IMHO) distributor in fact relicenses the code and may reduce license to sipmply BSD or simply GPL, or "GPL v3 from now on". To "restore" license you would need to go upstream and get the code from there.

Signature · 1 line
Dmitry
#75 lore raw

O> GPL itself does not. But the author(s) may when they specify "any

Quoted 4 lines

later version", "dual GPL/BSD", etc. In this case (IMHO) distributor in fact relicenses the code and may reduce license to sipmply BSD or simply GPL, or "GPL v3 from now on". To "restore" license you would need to go upstream and get the code from there.

I don't see anything in the GPL that permits a redistributor to change the licence a piece of code is distributed under. If my code is GPL v2 or later you cannot take away the "or later" unless explicitly granted powers by the author to vary the licence.

What you most certainly can do is modify it and decide your modifications are GPLv3 only thus creating a derived work which is GPLv3 only. However anyone receiving your modified version and reverting the modifications is back at v2 or later.

Alan

#76 lore raw
Quoted 11 lines · Alan Cox

O> GPL itself does not. But the author(s) may when they specify "any

Quoted 4 lines

later version", "dual GPL/BSD", etc. In this case (IMHO) distributor in fact relicenses the code and may reduce license to sipmply BSD or simply GPL, or "GPL v3 from now on". To "restore" license you would need to go upstream and get the code from there.

I don't see anything in the GPL that permits a redistributor to change the licence a piece of code is distributed under. If my code is GPL v2 or later you cannot take away the "or later" unless explicitly granted powers by the author to vary the licence.

Quoted 5 lines

What you most certainly can do is modify it and decide your modifications are GPLv3 only thus creating a derived work which is GPLv3 only. However anyone receiving your modified version and reverting the modifications is back at v2 or later.

Yes, I agree. When I am saying "distributor" it is someone like RedHat or TiVO who do modify the code, not merely use it in ints original form.

Signature · 1 line
Dmitry
#77 lore raw
In reply to Alan Cox
Quoted 12 lines · Alan Cox
Quoted 7 lines

GPL itself does not. But the author(s) may when they specify "any later version", "dual GPL/BSD", etc. In this case (IMHO) distributor in fact relicenses the code and may reduce license to sipmply BSD or simply GPL, or "GPL v3 from now on". To "restore" license you would need to go upstream and get the code from there.

I don't see anything in the GPL that permits a redistributor to change the licence a piece of code is distributed under. If my code is GPL v2 or later you cannot take away the "or later" unless explicitly granted powers by the author to vary the licence.

Quoted 4 lines

What you most certainly can do is modify it and decide your modifications are GPLv3 only thus creating a derived work which is GPLv3 only. However anyone receiving your modified version and reverting the modifications is back at v2 or later.

But that begs the question: How do you know what has been modified so you can revert the modifications? There won't necessarily be any indication of which files have been modified.

So I think Dmitry's point is valid. Don't you need to go upstream at least far enough to verify that you have unmodified code?

And how does the copyright work for kernel patches? Consider a dual licensed (i.e. anything beyond GPLv2 only) file. Someone supplies patches to Linus, he applies them, the resulting file is distributed with the kernel as GPLv2. What precisely has to happen for someone to get that same file with equivalent patches applied that can be distributed with the original dual license?

Somehow it seems to me that Linus would have to take the dual licensed files from his kernel repository and copy them to a separate archive and people would have to copy from there to keep the dual license. Aren't the files you extract from a linux tarball only licensed to you under the terms of GPLv2?

Signature · 1 line
Dan
#78 lore raw
Quoted 3 lines

But that begs the question: How do you know what has been modified so you can revert the modifications? There won't necessarily be any indication of which files have been modified.

There will

2a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

#79 lore raw
Quoted 9 lines · Alan Cox
Quoted 3 lines

But that begs the question: How do you know what has been modified so you can revert the modifications? There won't necessarily be any indication of which files have been modified.

There will

2a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

So how do you deduce what to revert (without going upstream for a pristine copy) if you see the following notice (I assume it is prominent enough):
:

/*
* ATTENTION!!!
* This file was modified from it's original version on 30-FEB-2345 by XYZ */

?

Signature · 1 line
Dmitry
#80 lore raw
In reply to Paulo Marques
Quoted 5 lines · Paulo Marques

Watching the output of the first grep without "wc -l" shows that, although it is not 100% accurate, it is still ok just to get a rough estimate.

So yes, ~6300 files are definitely more than a couple ;)

Most of them don't say anything, so they are "any GPL" by the author. When do you people accept that Linus can't change the GPL, he can only add comments of what he thinks is the case! His interpretation of the GPLv2 might be that not saying anything about the version means "v2 only", but if he does so, he's simply wrong. He was wrong in the module case, as well, and dropped this comment a while ago. He might drop this comment in future, as well. In fact, anybody can drop this comment, as it's just a comment.

The kernel *as a whole* is clearly under GPLv2 only from Linus' comment, which is in fact true, since the common subset of GPL versions from all authors is indeed GPLv2 (by virtue of some files from Al Viro, and maybe some other explicit GPL v2 files). The author must specify the version himself, there simply is no other way. If you don't specify any, it's "any version", because I can license all patches straight from the authors. The way the GPLv2 allows you to explicitely specify "any version" is by not saying anything about the version at all. Linus isn't in the positition to change that unless he does a substantial change to the file, and also adds a comment that this file is now GPLv2 only.

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#81 lore raw
Quoted 6 lines · Bernd Paysan
Quoted 5 lines · Paulo Marques

Watching the output of the first grep without "wc -l" shows that, although it is not 100% accurate, it is still ok just to get a rough estimate.

So yes, ~6300 files are definitely more than a couple ;)

I knew I shouldn't post into the yearly GPL flame-fest... :(

Quoted 1 line

Most of them don't say anything, so they are "any GPL" by the author.

I've contributed some code for the kernel (unlike yourself, AFAICT), and believe me, I did so under GPL v2. The COPYING file is pretty much self explanatory, so I didn't need to add any explicit license statement to my code.

Quoted 1 line

When do you people accept that Linus can't change the GPL, he can only add comments of what he thinks is the case! His interpretation of the GPLv2 might be that not saying anything about the version means "v2 only", but if he does so, he's simply wrong. He was wrong in the module case, as well, and dropped this comment a while ago. He might drop this comment in future, as well. In fact, anybody can drop this comment, as it's just a comment.

Linus can't and is not _changing_ the GPL. He can however use whatever license he sees fit for _his_ code just like all the other kernel developers do.

People seem to forget that the kernel license in COPYING *never had* the "v2 or later" clause. Never. Period.

The only change in license was from the previous hand-made one from Linus into GPL v2 only. And that is perfectly fine since the previous license was even more permissive than GPL v2.

Quoted 1 line

The kernel *as a whole* is clearly under GPLv2 only from Linus' comment, which is in fact true, since the common subset of GPL versions from all authors is indeed GPLv2 (by virtue of some files from Al Viro, and maybe some other explicit GPL v2 files). The author must specify the version himself, there simply is no other way. If you don't specify any, it's "any version", because I can license all patches straight from the authors.

No, it is not "any version". It is the license specified in COPYING and nothing else.

Quoted 1 line

The way the GPLv2 allows you to explicitely specify "any version" is by not saying anything about the version at all. Linus isn't in the positition to change that unless he does a substantial change to the file, and also adds a comment that this file is now GPLv2 only.

Man, I sure ain't a lawyer, but people in these discussions seem to not understand the basics at all.

And the basics are: "people who write the code decide the license to give it". And that's just it.

And people who write kernel code are perfectly aware that the kernel license is GPL v2 only, and always has been (except for the initial linus license).

So don't go around saying that because people don't put explicit license statements they don't care about the license. I care very much about the license, and would have never contributed to the kernel if it had a BSD license of some sort.

Putting a license statement in _every_ file in the kernel tree would just be idiotic when there is such a clear COPYING file in the root of the kernel tree.

Signature · 4 lines
Paulo Marques - www.grupopie.com

"Oh dear, I think you'll find reality's on the blink again."
Marvin The Paranoid Android
#82 lore raw
Quoted 4 lines · Paulo Marques

I've contributed some code for the kernel (unlike yourself, AFAICT), and believe me, I did so under GPL v2. The COPYING file is pretty much self explanatory, so I didn't need to add any explicit license statement to my code.

It's not, it's a personal comment from a misunderstanding of the GPL text. It's as valid as the "closed source kernel modules are legal" comment that was there some years ago.

Quoted 2 lines

People seem to forget that the kernel license in COPYING *never had* the "v2 or later" clause. Never. Period.

It's there in section 9.

Quoted 3 lines

The only change in license was from the previous hand-made one from Linus into GPL v2 only. And that is perfectly fine since the previous license was even more permissive than GPL v2.

??? Linus changed his own less permissive license (which excluded "commercial use", and certainly the TiVO device is commercial) in 0.0x time-frame. He added and deleted comments on top of COPYING in later years, some simply wrong like the assertion on proprietary kernel modules. He added his interpretation about the version issue in 2.4.0-test9, and he may delete it any time he wants. It's *his* interpretation.

Quoted 2 lines

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Quoted 2 lines

And the basics are: "people who write the code decide the license to give it". And that's just it.

Yo, then fucking do it! Write it in the files you contribute! If you don't, you haven't! You decide, not Linus Torvalds. Make it clear you have decided.

Quoted 3 lines

And people who write kernel code are perfectly aware that the kernel license is GPL v2 only, and always has been (except for the initial linus license).

Wrong.

Quoted 3 lines

Putting a license statement in _every_ file in the kernel tree would just be idiotic when there is such a clear COPYING file in the root of the kernel tree.

It's a personal comment from Linus, and not clear in any way. Do it the way the file COPYING itself suggests. It's not "idiotic", it's the most obvious way to do it.

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#83 lore raw
Quoted 8 lines · Bernd Paysan
Quoted 2 lines · Paulo Marques

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Please read this sentence over and over until it sinks:

"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."

Pay most attention to this part "If the Program specifies xxx and "any later version"", especially word "specifies".

Signature · 1 line
Dmitry
#84 lore raw
Quoted 10 lines · Dmitry Torokhov
Quoted 7 lines · Bernd Paysan
Quoted 2 lines · Paulo Marques

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Please read this sentence over and over until it sinks:

I believe he was talking about the sentence just after the one you quoted:

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

Linux files don't all specify version 2, but Linus, Al Viro and other authors very clearly mean their contributions to be version 2 only, while others very clearly mean their contributions to be v2+.

The moment anyone makes copyrightable changes to any such files, and offers them under GPLv2 only (if that's at all possible; I used to believe so, but I've read interesting, even if surprising, arguments indicating it might not be), the result of the modification is GPLv2 only.

So there's no doubt that the whole of the kernel is meant to be under GPLv2 only, even if some individual authors may choose to make their contributions available under other licenses, and be willing to make such offers when they are legally entitled to do so.

I don't quite understand what this fuss is all about. Even if a majority of the Linux authors had chosen GPLv2+, or GPLvany, if any single author makes a contribution under GPLv2 only, and that contribution is integrated, that's a veto for distributing the whole under any other license. This single contributor could dictate his choice upon others, as long as his contribution was present.

IANAL, but I believe that's how it works. And this means Linux is under GPLv2, no matter how much of the code in it is available under any other versions of the GPL, or even different (but compatible) 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}
#85 lore raw
Quoted 11 lines · Alexandre Oliva
Quoted 8 lines · Dmitry Torokhov
Quoted 7 lines · Bernd Paysan
Quoted 2 lines · Paulo Marques

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Quoted 9 lines
Quoted 1 line

Please read this sentence over and over until it sinks:

I believe he was talking about the sentence just after the one you quoted:

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

My response to this is that by including an entire copy of specific version of GPL in the release the version number was specified. You can't say that inclusion of copy of GPL is enough to specify class of licenses (all GPL) but not specific version.

Signature · 1 line
Dmitry
#86 lore raw
Quoted 17 lines · Dmitry Torokhov
Quoted 16 lines · Alexandre Oliva
Quoted 10 lines · Dmitry Torokhov
Quoted 7 lines · Bernd Paysan
Quoted 2 lines · Paulo Marques

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Please read this sentence over and over until it sinks:

I believe he was talking about the sentence just after the one you quoted:

Quoted 6 lines
Quoted 3 lines

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

My response to this is that by including an entire copy of specific version of GPL in the release the version number was specified.

It's not that simple. Including a copy of the license is a license requirement for any redistributor, yes.

But if you, a sole copyright holder, were to distribute your program, without any copy of the GPL, claiming "it's under the GPL", you're not a violator.

Then, any redistributor adds a copy of any version of the GPL (because you didn't specify a version number). At this point, is the program licensed by *you* only under this specific license?

Now, if you picked one of the various versions of the license, to make things easier for redistributors, does it mean you're choosing that particular version of the license, even though the license itself says otherwise?

Quoted 2 lines

You can't say that inclusion of copy of GPL is enough to specify class of licenses (all GPL) but not specific version.

I can't say either of these, indeed. Or rather, I can, but I wouldn't know whether I was 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}
#87 lore raw
Quoted 26 lines · Alexandre Oliva
Quoted 17 lines · Dmitry Torokhov
Quoted 16 lines · Alexandre Oliva
Quoted 10 lines · Dmitry Torokhov
Quoted 7 lines · Bernd Paysan
Quoted 2 lines · Paulo Marques

No, it is not "any version". It is the license specified in COPYING and nothing else.

COPYING says in section 9 that there may be other versions, and if you as author don't specify the version, it's "any version".

Please read this sentence over and over until it sinks:

I believe he was talking about the sentence just after the one you quoted:

Quoted 6 lines
Quoted 3 lines

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

My response to this is that by including an entire copy of specific version of GPL in the release the version number was specified.

Quoted 7 lines

It's not that simple. Including a copy of the license is a license requirement for any redistributor, yes.

But if you, a sole copyright holder, were to distribute your program, without any copy of the GPL, claiming "it's under the GPL", you're not a violator.

Distributing a copy of GPL is not a requirement for me as a licensor however I did chose to include a copy of a specific version of a specific license and did not make any other statements that is the license for the work.

Quoted 4 lines

Then, any redistributor adds a copy of any version of the GPL (because you didn't specify a version number). At this point, is the program licensed by *you* only under this specific license?

If they did not make any changes then they have to include the earliest version of GPL that applies. If they did modifications and chose GPLv4 they will have to include GPL v4 (if such requirement is in GPLv4) because what good any other license will do me?

Quoted 3 lines

Now, if you picked one of the various versions of the license, to make things easier for redistributors, does it mean you're choosing that particular version of the license,

Yes, this is my opinion.

Quoted 3 lines

even though the license itself
says otherwise?

License does not say otherwise. License says that if there is an _additional_ stipulation my the licensor then some other license (non existing yet license) may be used. They had to use this wording because these licensed do not exist yet. If GPL would say:

"If the Program specifies a version number of this License which applies to it and "or BSD license", you have the option of following the terms and conditions either of that version or of BSD license"

would you still say that BSD is allowed by default by GPL? "GPL v2 and later versions" is not different from "GPL v2 or BSD" or "GPLv2 or CDDL".

Quoted 6 lines
Quoted 2 lines

You can't say that inclusion of copy of GPL is enough to specify class of licenses (all GPL) but not specific version.

I can't say either of these, indeed. Or rather, I can, but I wouldn't know whether I was right ;-)

Signature · 1 line
Dmitry
#88 lore raw
Quoted 9 lines · Dmitry Torokhov
Quoted 3 lines · Alexandre Oliva
Quoted 3 lines
Quoted 3 lines

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

Distributing a copy of GPL is not a requirement for me as a licensor however I did chose to include a copy of a specific version of a specific license and did not make any other statements that is the license for the work.

And the copy you chose to include says the above.

Are you absolutely sure you could terminate the license of a distributor that refrains to pass on a patent license it obtained, if you included a copy of the GPLv2 without any other indication that you're choosing GPLv2 and no other version of the GPL, in spite of the above?

Would it change anything if you had released the program back when GPLv3 wasn't under discussion, and GPLv1 was long forgotten, so most people (yourself included) only referred to it as GPL, or GNU GPL?

Quoted 6 lines
Quoted 3 lines

Then, any redistributor adds a copy of any version of the GPL (because you didn't specify a version number). At this point, is the program licensed by *you* only under this specific license?

If they did not make any changes then they have to include the earliest version of GPL that applies.

Why? Why does it have to be the earliest?

Quoted 6 lines
Quoted 2 lines

even though the license itself
says otherwise?

License does not say otherwise. License says that if there is an _additional_ stipulation my the licensor then some other license (non existing yet license) may be used.

No, you're referring to the portion you quoted, but I'm referring to another portion, that I quoted above.

Quoted 7 lines

"If the Program specifies a version number of this License which applies to it and "or BSD license", you have the option of following the terms and conditions either of that version or of BSD license"

would you still say that BSD is allowed by default by GPL? "GPL v2 and later versions" is not different from "GPL v2 or BSD" or "GPLv2 or CDDL".

Agreed. But this is not what this is about. This is about the license saying something like:

If the program does not specify a license version number, then you're permitted to relicense the program under the BSD license.

Since the license file itself is not part of the program (if it were, a program under the GPL would require the GPL itself to be under the GPL, right?), I claim the program does not specify a license version number.

Now what?

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}
#89 lore raw
Quoted 12 lines · Alexandre Oliva
Quoted 9 lines · Dmitry Torokhov
Quoted 3 lines · Alexandre Oliva
Quoted 3 lines
Quoted 3 lines

If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

Distributing a copy of GPL is not a requirement for me as a licensor however I did chose to include a copy of a specific version of a specific license and did not make any other statements that is the license for the work.

Quoted 8 lines

And the copy you chose to include says the above.

Are you absolutely sure you could terminate the license of a distributor that refrains to pass on a patent license it obtained, if you included a copy of the GPLv2 without any other indication that you're choosing GPLv2 and no other version of the GPL, in spite of the above?

You never sure about anything taht involves lawyers ;)

Quoted 4 lines

Would it change anything if you had released the program back when GPLv3 wasn't under discussion, and GPLv1 was long forgotten, so most people (yourself included) only referred to it as GPL, or GNU GPL?

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Then, any redistributor adds a copy of any version of the GPL (because you didn't specify a version number). At this point, is the program licensed by *you* only under this specific license?

If they did not make any changes then they have to include the earliest version of GPL that applies.

Why? Why does it have to be the earliest?

Earliest is wrong I suppose. What I meant is post permissive. Otherwise it does not make any sense. And what about if there is a version of GPL that does not require passing a copy of the license along with the program?

I guess it does not matter because somewhere it would still state "this program is released under GPL" (as you said there is no version number) so receient can look up what versions of GPL were ever released.

This is different from attaching a specific license.

Quoted 22 lines
Quoted 7 lines
Quoted 3 lines

even though the license itself
says otherwise?

License does not say otherwise. License says that if there is an _additional_ stipulation my the licensor then some other license (non existing yet license) may be used.

No, you're referring to the portion you quoted, but I'm referring to another portion, that I quoted above.

Quoted 7 lines

"If the Program specifies a version number of this License which applies to it and "or BSD license", you have the option of following the terms and conditions either of that version or of BSD license"

would you still say that BSD is allowed by default by GPL? "GPL v2 and later versions" is not different from "GPL v2 or BSD" or "GPLv2 or CDDL".

Agreed. But this is not what this is about. This is about the license saying something like:

Quoted 8 lines

If the program does not specify a license version number, then you're permitted to relicense the program under the BSD license.

Since the license file itself is not part of the program (if it were, a program under the GPL would require the GPL itself to be under the GPL, right?), I claim the program does not specify a license version number.

Why don't you claim that actually the program is in public domain and the license file just got there by mistake? Attaching a specific license (and GPL v2 is a distinctive license, not a bumped up version of other license) places work under this (and only this) license. In my book this is different form just saying "the program is under GPL".

I guess we'll have to agree to disagree.

Signature · 1 line
Dmitry
#90 lore raw
Quoted 10 lines · Dmitry Torokhov
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Then, any redistributor adds a copy of any version of the GPL (because you didn't specify a version number). At this point, is the program licensed by *you* only under this specific license?

If they did not make any changes then they have to include the earliest version of GPL that applies.

Why? Why does it have to be the earliest?

Earliest is wrong I suppose. What I meant is post permissive.

Again, why? In the absence of a version number, why wouldn't the redistributor choose any one he liked?

Quoted 3 lines

I guess it does not matter because somewhere it would still state "this program is released under GPL" (as you said there is no version number) so receient can look up what versions of GPL were ever released.

Yes. The initial recipient knows that, because he received the announcement by e-mail, where the "released under GPL" was. But how about downstream recipients? (yeah, I'm filling in blanks and making this up on the fly, I hope you don't mind)

Quoted 1 line

This is different from attaching a specific license.

How can the downstream recipient tell this case from the case in which you attached one specific version of the license and didn't write anywhere that only that version applied?

Quoted 2 lines

Why don't you claim that actually the program is in public domain and the license file just got there by mistake?

License file there by mistake is a possibility, but this wouldn't make the program public domain, it would rather turn actions controlled by copyright law into copyright infringement, but as long as the recipient acted within the unclear intent of the licensor, the licensor probably wouldn't enforce the license anyway. And then, if he did, there'd be a number of defenses available for the licensee/infringer. But IANAL.

Quoted 3 lines

Attaching a specific license (and GPL v2 is a distinctive license, not a bumped up version of other license) places work under this (and only this) license.

We'll see if that works when someone tries to takes advantage of any of the holes in GPLv1 that GPLv2 plugged and you try to enforce GPLv2. I'm not sure whether to hope it will (such that this implied v2 gets better freedom protection than v1) or won't (such that I could redistribute under v3 ;-)

Quoted 2 lines

In my book this is different form just saying "the program is under GPL".

I hope you've consulted a lawyer about this. If not, it might be safer to state your intentions more explicitly, like Linus did.

Quoted 1 line

I guess we'll have to agree to disagree.

Works for me ;-)

Best regards,

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}
#91 lore raw
In reply to Bernd Paysan
Quoted 7 lines · Bernd Paysan
Quoted 4 lines · Paulo Marques

I've contributed some code for the kernel (unlike yourself, AFAICT), and believe me, I did so under GPL v2. The COPYING file is pretty much self explanatory, so I didn't need to add any explicit license statement to my code.

It's not, it's a personal comment from a misunderstanding of the GPL text. It's as valid as the "closed source kernel modules are legal" comment that was there some years ago.

These are not changes to the license text. These are just clarifications to help people understand the license. They don't change what the license already said.

Quoted 4 lines
Quoted 2 lines

People seem to forget that the kernel license in COPYING *never had* the "v2 or later" clause. Never. Period.

It's there in section 9.

The section 9 is meant to explain how you select one version of the license in a program without having to copy the entire license text to it, i.e., in simple programs you can just put the small text, suggested by FSF at the bottom of the gpl, and have the version number there, and that should be enough to reference the entire text.

But COPYING *is* the entire text and starts with: "

		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991"

so there is no confusion about the version.

Quoted 6 lines
Quoted 4 lines

[...]
And people who write kernel code are perfectly aware that the kernel license is GPL v2 only, and always has been (except for the initial linus license).

Wrong.

Why do you say "Wrong"? Have you contributed some code to the kernel thinking that the kernel was "v2 or later", only to find out later that it wasn't?

In case you haven't followed previous discussions, here's a pointer:

http://lkml.org/lkml/2006/9/22/176

The major kernel developers (and probably most of the total number of developers) are perfectly aware of the kernel license and chose GPL v2.

I'm getting pretty tired of listening to people that just _know_ what I should do with _my_ code. And people who treat kernel developers as morons who can't read a license.

We definitely need more Al Viro style comments on this thread ;)

Signature · 5 lines
Paulo Marques - www.grupopie.com

"The Mexicans have the Chupacabra. We have Al Viro. If you hear him roar, just _pray_ he's about to dissect somebody elses code than yours.. There is no point in running."

Linus Torvalds
#92 lore raw
Quoted 5 lines

But COPYING *is* the entire text and starts with: "

		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991"

so there is no confusion about the version.

The version of the COPYING file (and the licence document), not of the licence on the code.

Quoted 5 lines
Quoted 1 line

Wrong.

Why do you say "Wrong"? Have you contributed some code to the kernel thinking that the kernel was "v2 or later", only to find out later that it wasn't?

A fair bit of the kernel is probably v2 or later but not all of it and that shouldn't really matter as regards the kernel anyway, the GPLv2 only bits (if v2 only is a valid status) anchor it.

#93 lore raw
Quoted 9 lines · Alan Cox
Quoted 5 lines

But COPYING *is* the entire text and starts with: "

		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991"

so there is no confusion about the version.

The version of the COPYING file (and the licence document), not of the licence on the code.

Quoted 6 lines
Quoted 2 lines
Quoted 1 line

Wrong.

Why do you say "Wrong"? Have you contributed some code to the kernel thinking that the kernel was "v2 or later", only to find out later that it wasn't?

A fair bit of the kernel is probably v2 or later but not all of it and that shouldn't really matter as regards the kernel anyway, the GPLv2 only bits (if v2 only is a valid status) anchor it.

So we are violently agreeing, then?

This sub-thread started by me showing that:

Quoted 4 lines
$ find -name "*.c" | xargs grep "any later version" | wc -l
3138
$ find -name "*.c" | wc -l
9482

This is a somewhat crude measure but it shows that only about 30% of the kernel is "v2 or later" and those pieces could be used on some other "v2 or later" project (including v3). But the kernel as a whole is v2 and my point was that the claim that there are just a few "v2 only" files was bogus.

Signature · 4 lines
Paulo Marques - www.grupopie.com

"As far as we know, our computer has never had an undetected error."
Weisert
#94 lore raw
In reply to Alan Cox
Quoted 9 lines · Alan Cox
Quoted 5 lines

But COPYING *is* the entire text and starts with: "
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991"

so there is no confusion about the version.

The version of the COPYING file (and the licence document), not of the licence on the code.

Using this logic one can say that Linux kernel is BSD or even public domain and COPYING is there just for kicks.

Signature · 1 line
Dmitry
#95 lore raw
Quoted 5 lines · Dmitry Torokhov
Quoted 4 lines · Alan Cox
Quoted 4 lines

But COPYING *is* the entire text and starts with: "
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991"

Quoted 9 lines
Quoted 5 lines
Quoted 1 line

so there is no confusion about the version.

The version of the COPYING file (and the licence document), not of the licence on the code.

Using this logic one can say that Linux kernel is BSD or even public domain and COPYING is there just for kicks.

No. Only the original author can specify the license. If no license at all is specified only the author has any rights to the work, other people don't have any right to distribute, modify or whatever. So if the COPYING file doesn't specify the license for work without a license clause directly in the file, then only the author has any rights, you can't just then move in and assign an arbitrary license. But I think you would find it very hard to argue that files contributed to the Linux kernel without an explicit license notice does not fall under the terms set forth in the COPYING document.

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
#96 lore raw
In reply to Dmitry Torokhov
Quoted 5 lines · On Fri, 15 Jun 2007 10:52:27 -0400 "Dmitry Torokhov"…
Quoted 4 lines · Alan Cox
Quoted 4 lines

But COPYING *is* the entire text and starts with: "
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991"

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

so there is no confusion about the version.

The version of the COPYING file (and the licence document), not of the licence on the code.

Using this logic one can say that Linux kernel is BSD or even public domain and COPYING is there just for kicks.

Not really because
1. The file is called COPYING which rather suggests its purpose
2. There is a note at the top of it
3. Lots of the code contains GPL headers

Any sane Judge is going to come to the conclusion that this was the intended licence of the code. The fact people have said so also settles the matter pretty much.

One of the big differences between law (at least UK/US law) and code is that the legal process seeks in part to figure out the intention of a licence or contract. Civil law is a dispute resolution process. Not a very good one, not a very cheap one, but as the previous system involved sending large blokes around to the opponents HQ with swords and axes it was found to have distinct benefit.

Alan

#97 lore raw
In reply to Dmitry Torokhov

This was actually a part of a larger reply - but I decided not to sent that. Didn't want to throw away the work I did to get accurate numbers though ;)

I investigated:

   find -name "*.c" | wc --lines
   11100
   find -name "*.c" | xargs egrep "(version 2.*([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation))|(([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation).*version 2)" | sed -e 's/:.*//' | sort -u | wc --lines
   4042
   find -name "*.c" | xargs egrep "(version 2.*([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation))|(([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation).*version 2)" | egrep -v '(either version 2(\.[0-9])*|version 2(\.[0-9])*( of the License)*,* or)' | sed -e 's/:.*//' | sort -u | wc --lines
   1377
   find -name "*.c" | xargs egrep "(version 2.*([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation))|(([Ll]icense|redistribute|released|GNU|GPL|any later version|Foundation).*version 2)" | egrep -v '(either version 2(\.[0-9])*|version 2(\.[0-9])*( of the License)*,* or)' | sed -e 's/:.*//' | sort -u | xargs grep 'any later version' | wc --lines
   4

Hence there are 1377 - 4 = 1373 .c files that explicitely say 'version 2', and 4042 - 1373 = 2669 .c files that say 'version 2 or later'. There are 11100 - 1373 - 2669 = 7058 files that do not say anything.

#98 lore raw
In reply to Bernd Paysan
Quoted 8 lines · Bernd Paysan
Quoted 4 lines

I've contributed some code for the kernel (unlike yourself, AFAICT), and believe me, I did so under GPL v2. The COPYING file is pretty much self explanatory, so I didn't need to add any explicit license statement to my code.

It's not, it's a personal comment from a misunderstanding of the GPL text. It's as valid as the "closed source kernel modules are legal" comment that was there some years ago.

You forgot something. Namely, that file *without* any mentioning of GPL or other license is either illegal to distribute at all, under any license, *OR* inherits the default license of the project. Which is to say, what is stated in COPYING.

Take your pick. For what it's worth, it would be interesting to hear the opinion of RMS - both on how much of the kernel is possible to distribute under v3 according to him and on the morality of your position.

#99 lore raw
Quoted 1 line · Al Viro

*OR* inherits the default license of the project.

You got any case law for this? Seriously, I could use this for FSFLA's IRPF2007-Livre project.
http://fsfla.org/svnwiki/blogs/lxo/pub/freeing-the-lion

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}
#100 lore raw
Quoted 7 lines · Alexandre Oliva
Quoted 1 line · Al Viro

*OR* inherits the default license of the project.

You got any case law for this? Seriously, I could use this for FSFLA's IRPF2007-Livre project.
http://fsfla.org/svnwiki/blogs/lxo/pub/freeing-the-lion

Umm... What other license choices are there? Seriously, if file *does* get a license from somewhere (and if it doesn't, it can't be distributed at all), where else would that license come from?

I can see one arguing that it shouldn't be distributed at all (and we obviously don't want that), I can see one arguing that copyright statement floating in root of tree in file called "COPYING" and not tied to specific parts of that tree should apply, but I don't see how one would argue that some other license he happens to like should apply here.

No specific case law, but I'd expect serious [eventual] trouble for somebody trying to slap some different license in such case. Not sure if anybody actually ever tried that...

IIRC, the usual argument for slapping copyright into every file is along the lines of "making sure that it doesn't get lost when file is lifted into another project", not "it's free for grabbing by anyone" or "it can't be distributed at all"...

#101 lore raw
Quoted 10 lines · Al Viro
Quoted 7 lines · Alexandre Oliva
Quoted 1 line · Al Viro

*OR* inherits the default license of the project.

You got any case law for this? Seriously, I could use this for FSFLA's IRPF2007-Livre project.
http://fsfla.org/svnwiki/blogs/lxo/pub/freeing-the-lion

Umm... What other license choices are there?

Where does it say that there must be one?

Quoted 2 lines

No specific case law, but I'd expect serious [eventual] trouble for somebody trying to slap some different license in such case.

Consider this (to make the freeing-the-lion story short):

Jar file with .class files, with a copy of LGPL in the root of the tree. No other license anywhere to be seen. Is it safe to assume the whole thing is under the LGPL?

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}
#102 lore raw
Quoted 8 lines · Alexandre Oliva
Quoted 2 lines

No specific case law, but I'd expect serious [eventual] trouble for somebody trying to slap some different license in such case.

Consider this (to make the freeing-the-lion story short):

Jar file with .class files, with a copy of LGPL in the root of the tree. No other license anywhere to be seen. Is it safe to assume the whole thing is under the LGPL?

It certainly sounds like a reasonable first assumption; unless you are aware of couterexamples, you probably would be able at least to prove that you've acted in good faith if somebody starts to complain. IANAL, obviously, so ask FSF lawyers. Really. Especially if you are doing that for a text associated with FSF-LA in any way. That's what they are for.

#103 lore raw
Quoted 10 lines · Al Viro
Quoted 8 lines · Alexandre Oliva
Quoted 2 lines

No specific case law, but I'd expect serious [eventual] trouble for somebody trying to slap some different license in such case.

Consider this (to make the freeing-the-lion story short):

Jar file with .class files, with a copy of LGPL in the root of the tree. No other license anywhere to be seen. Is it safe to assume the whole thing is under the LGPL?

Quoted 5 lines

It certainly sounds like a reasonable first assumption; unless you are aware of couterexamples, you probably would be able at least to prove that you've acted in good faith if somebody starts to complain. IANAL, obviously, so ask FSF lawyers. Really. Especially if you are doing that for a text associated with FSF-LA in any way. That's what they are for.

I've covered my grounds and talked to lawyers in Brazil, where this all happened. But it wouldn't hurt me to have cases of law abroad, which is why I asked.

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}
#104 lore raw
In reply to Bernd Paysan
Quoted 13 lines
Quoted 2 lines

And the basics are: "people who write the code decide the license to give it". And that's just it.

Yo, then fucking do it! Write it in the files you contribute! If you don't, you haven't! You decide, not Linus Torvalds. Make it clear you have decided.

Quoted 3 lines

And people who write kernel code are perfectly aware that the kernel license is GPL v2 only, and always has been (except for the initial linus license).

Wrong.

Quoted 7 lines
Quoted 3 lines

Putting a license statement in _every_ file in the kernel tree would just be idiotic when there is such a clear COPYING file in the root of the kernel tree.

It's a personal comment from Linus, and not clear in any way. Do it the way the file COPYING itself suggests. It's not "idiotic", it's the most obvious way to do it.

If it wasn't clear someday, it seems to be utterly clear now, after all this discussion (that is not the first related, AFAIK). Why is the "spirit" so important for the GPLv{2,3} understanding, and not important at all here? The intention that the kernel is gplv2 is very clearly stated.

Signature · 5 lines
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."
#105 lore raw
In reply to Bernd Paysan
Quoted 8 lines · Bernd Paysan
Quoted 5 lines · Paulo Marques

Watching the output of the first grep without "wc -l" shows that, although it is not 100% accurate, it is still ok just to get a rough estimate.

So yes, ~6300 files are definitely more than a couple ;)

Most of them don't say anything, so they are "any GPL" by the author.

Woah! Stop right there. Since when a work without a license spelled out becomes "any GPL"?

Quoted 8 lines

When
do you people accept that Linus can't change the GPL, he can only add comments of what he thinks is the case! His interpretation of the GPLv2 might be that not saying anything about the version means "v2 only", but if he does so, he's simply wrong. He was wrong in the module case, as well, and dropped this comment a while ago. He might drop this comment in future, as well. In fact, anybody can drop this comment, as it's just a comment.

Quoted 6 lines

The kernel *as a whole* is clearly under GPLv2 only from Linus' comment, which is in fact true, since the common subset of GPL versions from all authors is indeed GPLv2 (by virtue of some files from Al Viro, and maybe some other explicit GPL v2 files). The author must specify the version himself, there simply is no other way. If you don't specify any, it's "any version", because I can license all patches straight from the authors.

Yes, you can. In this case you get _different_ software, maybe even under different license. I bet if you go straight to the authors you can get XFS or JFS under a commercial license, not GPL at all.

Quoted 3 lines

The
way the GPLv2 allows you to explicitely specify "any version" is by not saying anything about the version at all.

Let me quote GPLv2 for you:

"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."

As you can see for "ant later version" to apply the program must explicitely say "This program is distributed under GPLv2 and any later version". Supplying text of GPL v2 with the program does not automatically add that clause. IOW, if copying file would litrally read "Distributed under GPL v2. For the text of GPL v2 go to www.fsf.org" woudl you still argue that it is "GPLv2 and later"?

Signature · 1 line
Dmitry
#106 lore raw
In reply to Bernd Paysan
Quoted 3 lines · Bernd Paysan

Linus isn't in the positition to
change that unless he does a substantial change to the file, and also adds a comment that this file is now GPLv2 only.

Which would only have effect on future additions, not the current content of the file - of course.

Now - what if someone would write a patch for such a file (that was 'any version' before and then had a header added saying 'just version 2') under the license 'version 2 or later'? This patch could be transformed to 'just 2', and then applied to said source file - but, it could also be added to the previous version of that file (without the new header) as 'version 2 or later'. Hence, the file can still be constructed at any moment (provided the header is removed) as license 'version 2 or later', UNLESS someone adds a *crucial* patch (that cannot be removed as well, along with the header) that is explicitely made version 2 ONLY by its author.

Bottom line - adding a header to those files with "version 2 only" by Linus is pointless.

Signature · 1 line
Carlo Wood <[email protected]>
#107 lore raw
In reply to Bernd Paysan
Quoted 6 lines · Bernd Paysan

What I don't understand about the GPLv3 with keys is why that depends on the use case. As user of commercial devices like company routers, firewalls and such, which often are Linux based, I don't want them sealed by the vendor, as well. An explicit statement is even worse than an implicit one (as in the GPLv2, which has been tested in a German court by Harald Welte - Siemens had to turn in the keys).

My personal guess as to the reasoning behind this decision is that consumer devices are the ones that require most attention, mainly because the home users are the ones with least (individual) power to demand respect for their 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}
#108 lore raw
In reply to Alexandre Oliva
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines · Greg KH

(see previous long thread about v3 and why the kernel developers hate it, it all still applys to the final draft.)

You mean all the misunderstandings? ;-)

I see the smiley, but I hate it how the FSF thinks others are morons and cannot read or think for themselves.

Any time you disagree with the FSF, you "misunderstand" (insert condescending voice) the issue.

_Please_ don't continue that idiocy. Disagreement and thinking that the FSF is controlling and putting its fingers where they don't belong is _not_ misunderstanding. It's just not "blind and unquestioning obedience".

Linus

#109 lore raw
Quoted 11 lines · Linus Torvalds
Quoted 6 lines · Alexandre Oliva
Quoted 2 lines · Greg KH

(see previous long thread about v3 and why the kernel developers hate it, it all still applys to the final draft.)

You mean all the misunderstandings? ;-)

I see the smiley, but I hate it how the FSF thinks others are morons and cannot read or think for themselves.

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?

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.

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.

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.

With this different frame of mind, it is not surprising at all that you don't find GPLv3 a better license. With different goals in mind, reasonable people can reach different conclusions. But claiming that GPLv3 is changing the spirit of the license, or that it prohibits certain kinds of software, is plain false. 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.

Sure, this evokes a number of other nice behaviors in various players, and it's clear to me that it's in these other nice behaviors that you seek when you choose GPLv2. There's nothing inherently wrong in that.

However, it seems to me that GPLv3 would do an even better job at serving these goals than GPLv2, even if the holes v3 plugs that enabled players to disrespect others' freedoms might steer away the participants who are not willing to contribute, to really be part of your community. It's not like you lose much.

But the new defenses against disrespect for freedoms introduced in GPLv3 may turn out to be very helpful, not only in protecting your community from external threats, but also in strengthening participation, as the benefits of participation outweight the perceived costs of respecting others' freedoms.

It sure seems to me that trading some threats and non-contributors for some more-committed participants is a good idea.

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}
#110 lore raw
Quoted 4 lines · Alexandre Oliva

On Jun 13, 2007, Linus Torvalds <[email protected]> wrote:
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.

I believe a number of people don't think the GPL v3 is in the same spirit as the GPL v2. I guess it comes down to what people thought the spirit of the GPL v2 was. There certainly seems to be a variety of opinions on that, and I am not sure the FSF's opinion on it agrees with what most others believe, but that would be rather difficult to determine.

--
Len Sorensen

#111 lore raw
Quoted 3 lines · On Jun 13, 2007, [email protected] (Lennart Sorensen) wrote:

I believe a number of people don't think the GPL v3 is in the same spirit as the GPL v2. I guess it comes down to what people thought the spirit of the GPL v2 was.

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.

[...] 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?

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}
#112 lore raw
Quoted 13 lines · Alexandre Oliva

[...] 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?

What kind of logic is that? It sounds like "Can you prove that God doesn't exist?"

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

So the whole "to protect these rights, we take away other rigths" argument hinges on the false premise that the new language in GPLv3 is somehow needed. It's not. You still had the right to distribute the software (and modify it), even if the *hardware* is limited to only one version.

In other words, GPLv3 restricts rights that do not need to be restricted, and yes, I think that violates the spirit of the GPLv2 preamble!

Think of it this way: what if the GPLv3 had an addition saying "You can not use this software to make a weapon". Do you see the problem? It restricts peoples rights, would you agree? Would you _also_ agree that it doesn't actually follow that "To protect your rights" logic AT ALL?

And this is exactly where the GPLv3 *diverges* from the above logic. If I build hardware, and sell it with software installed, you can still copy and modify the software. You may not do so within the confines of the hardware I built, but the hardware was never under the license in the first place.

In other words, GPLv3 *restricts* peoples freedoms more than it protects them. It does *not* cause any additional stated freedoms - quite the reverse. It tries to free up stuff that was never mentioned in the first place.

And then the FSF has the gall to call themselves the "protector of freedoms", and claim that everybody else is evil. What a crock.

In other words, if you want to argue for the changes in GPLv3, you need to CHANGE THE PREAMBLE TOO! You should change:

When we speak of free software, we are referring to freedom, not price. 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, that you can do so in place on your devices, even if those devices weren't licensed under the GPL; and that you know you can do these things.

where I added the "that you can do so in place on your devices, even if those devices weren't licensed under the GPL".

That wasn't there in the original. Yet it's what the GPLv3 tries to shove down our throats in the name of "freedom".

I don't know if you've followed US politics very much over the last six years, but there's been a lot of "protecting our freedoms" going on. And it's been ugly. Maybe you could realize that sometimes "protecting your freedom" is *anything*but*!

Linus

#113 lore raw
Quoted 18 lines · Linus Torvalds
Quoted 17 lines · Alexandre Oliva

[...] 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.

[...] 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

Quoted 5 lines
Quoted 2 lines

Can anyone show me how any of the provisions of GPLv3 fails to meet this spirit?

What kind of logic is that? It sounds like "Can you prove that God doesn't exist?"

By this reasoning, it sounds like you've been claiming that "God does exist", even though you can't prove it.

It shouldn't be anywhere that difficult to show that the GPLv3 fails to meet the spirit of the GPLs. You just have to show a single counter-example. Since there are so many objections to the changes, it shouldn't be that hard. Can you at least try?

Quoted 2 lines

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

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.

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.

Quoted 1 line

In other words, GPLv3 restricts rights that do not need to be restricted,

That's correct. They don't need to be restricted. The whole idea of copyleft, implemented through the GPL, is not based on needs, but rather on the wish to defend the freedoms established in the preamble from those who would rather not respect them.

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?

Do you deny that they can still do it themselves?

Quoted 2 lines

Think of it this way: what if the GPLv3 had an addition saying "You can not use this software to make a weapon".

This would make GPLv3 a non-Free Software license.

But the GPLv3 last call draft doesn't say anything along these lines.

You can use the software as much as you like, even in DVRs, and even to implement DRM in them, as long as you respect the users' freedoms to change and share the software. Per the GPLv3 (paraphrased), if it is possible to install modified versions of the covered program in the device, you must tell the recipient how to do it. Otherwise, the freedom to modify the program is being too severely limited.

And, in the particular case of TiVo, it's a case of distributing incomplete source code, of refraining from including functional portions of the source code.

Quoted 2 lines

In other words, GPLv3 *restricts* peoples freedoms more than it protects them.

While you look at it from the point of view of TiVo, who wants to be free to prohibit people from modifying the workings of the device it sells while it can still modify it itself, and it does that in order to prohibit people from removing locks that stop them from doing things they're legally entitled to do, I see a lot more prohibitions than freedoms in what TiVo does. I don't understand why you'd stand up for it. Is it more important that a single company be allowed to impose prohibitions on others in order for its business model to work, than to maintain the spirit of hacking and sharing that enabled Free Software and Linux to flourish?

Do you expect Linux would have flourished if computers had locks that stopped people from modifying Linux in them?

Quoted 2 lines

where I added the "that you can do so in place on your devices, even if those devices weren't licensed under the GPL".

You're mistakenly focusing on the device. As you say, the device is not under the license.

What's under the license is the software in it. And that license spirit requires the distributor to pass on the right to modify the software.

Quoted 4 lines

I don't know if you've followed US politics very much over the last six years, but there's been a lot of "protecting our freedoms" going on. And it's been ugly. Maybe you could realize that sometimes "protecting your freedom" is *anything*but*!

Is this why you're overreacting?

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}
#114 lore raw
Quoted 11 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:
Quoted 2 lines · Linus Torvalds

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

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.

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.

Quoted 4 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

It does, can't you modify their kernel source? Where does it say you should be able to run you modifications on the same hardware?

Quoted 5 lines

Oops.

Sounds like a violation of the spirit to me.

Sounds like plugging this hole would retain the same spirit.

The only fear that I have with the whole Tivo saga, is that companies like Dell can use the same thing to say: "Our hardware will only run Company's X distribution of Linux".

Do we just hope users won't buy those Dell machines, or do you modify your software license to force Dell to allow custom distributions to run on their machines? Then where do we draw the line of "Software Licenses".

#115 lore raw
Quoted 10 lines · Bongani Hlope
Quoted 9 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:
Quoted 2 lines · Linus Torvalds

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

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

Quoted 7 lines
Quoted 1 line

So, TiVo includes a copy of Linux in its DVR.

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.
...

Wrong, 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.

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 Seed
#116 lore raw
In reply to Bongani Hlope
Quoted 11 lines · Bongani Hlope
Quoted 4 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:

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.

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.

Can they modify the software in their device?

Do they pass this right on?

Quoted 5 lines
Quoted 3 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

It does, can't you modify their kernel source?

It's not the kernel source. That's not where the TiVo anti-tampering machinery blocks modifications.

It's about that copy of the kernel that ships in the device in object code. That's the one that TiVo customers ought to be entitled to modify, if TiVo can modify it itself.

Quoted 2 lines

Where does it say you should be able to run you modifications on the same hardware?

Where it says that you should pass on all the rights that you have.

While TiVo retains the ability to replace, upgrade, fix, break or make any other change in the GPLed software in the device, it ought to pass it on to its customers.

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}
#117 lore raw
Quoted 7 lines · On Wednesday 13 June 2007 20:55:52 Alexandre Oliva wrote:
Quoted 6 lines · Bongani Hlope
Quoted 4 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:

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.

Quoted 8 lines
Quoted 4 lines

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.

Can they modify the software in their device?

Do they pass this right on?

But this *ISN'T* a right that the GPLv2 *REQUIRES* be passed on.

Quoted 4 lines
Quoted 4 lines
Quoted 3 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

Quoted 8 lines
Quoted 1 line

It does, can't you modify their kernel source?

It's not the kernel source. That's not where the TiVo anti-tampering machinery blocks modifications.

It's about that copy of the kernel that ships in the device in object code. That's the one that TiVo customers ought to be entitled to modify, if TiVo can modify it itself.

The GPLv2 makes no real provision for *DIRECTLY* modifying object code. What provisions the GPLv2 has apply to the source code.

And no, the end user *SHOULD* *NOT* be entitled to run whatever kernel they like on a TiVO. It was designed with the "install new kernel" functionality so that the TiVO corporation could update the kernel running on the hardware when security problems came up, when bugs were fixed or even when the new version gives better performance.

Quoted 8 lines
Quoted 2 lines

Where does it say you should be able to run you modifications on the same hardware?

Where it says that you should pass on all the rights that you have.

While TiVo retains the ability to replace, upgrade, fix, break or make any other change in the GPLed software in the device, it ought to pass it on to its customers.

It *DOES* *NOT* say "All rights that you have". It says "All rights that are granted you by this license". If every piece of software released under the GPL had *ALL* rights passed on, then *ANYONE* could do the "I'm granting company X the right to use this software outside the GPL for $50,000USD." instead of just the *creator* of the software.

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#118 lore raw
Quoted 6 lines · Daniel Hazelton
Quoted 4 lines · On Wednesday 13 June 2007 20:55:52 Alexandre Oliva wrote:
Quoted 3 lines · Bongani Hlope
Quoted 2 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:

if you distribute copies of such a program, [...] you must give the recipients all the rights that you have

Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line

So, TiVo includes a copy of Linux in its DVR.

Can they modify the software in their device?

Do they pass this right on?

But this *ISN'T* a right that the GPLv2 *REQUIRES* be passed on.

You may be right. The spirit says it should, but the legalese may have missed the mark. So GPLv3 makes it clear that it is.

Quoted 6 lines
Quoted 3 lines

It's about that copy of the kernel that ships in the device in object code. That's the one that TiVo customers ought to be entitled to modify, if TiVo can modify it itself.

The GPLv2 makes no real provision for *DIRECTLY* modifying object code.

Sure. And that's not what I'm talking about.

What I'm talking about is being able to replace, upgrade, fix, tweak, hack, and otherwise modify the program on the machine in the same way that the vendor still can.

Quoted 1 line

What provisions the GPLv2 has apply to the source code.

This is too narrow a view of the GPLv2 provisions.

Quoted 5 lines

And no, the end user *SHOULD* *NOT* be entitled to run whatever kernel they like on a TiVO. It was designed with the "install new kernel" functionality so that the TiVO corporation could update the kernel running on the hardware when security problems came up, when bugs were fixed or even when the new version gives better performance.

I.e., it was designed such that TiVo could modify the installed kernel, but the user couldn't. That's an outright violation of the spirit of the GPL.

Quoted 11 lines
Quoted 8 lines
Quoted 2 lines

Where does it say you should be able to run you modifications on the same hardware?

Where it says that you should pass on all the rights that you have.

While TiVo retains the ability to replace, upgrade, fix, break or make any other change in the GPLed software in the device, it ought to pass it on to its customers.

It *DOES* *NOT* say "All rights that you have". It says "All rights that are granted you by this license".

I suggest you to reboot into memtest ;-) The preamble of GPLv2 says:

For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Quoted 3 lines

If every piece of software released under the GPL had *ALL* rights passed on, then *ANYONE* could do the "I'm granting company X the right to use this software outside the GPL for $50,000USD."

The requirement above applies to licensees, not to the licensor. The licensor doesn't have to pass on all the rights s/he has, s/he only decides to respect the licensee's freedoms, conditioned to the respect of others' freedoms by means of passing on all rights the licensee has over the software.

Arguably, one could use this argument to state that any authors of derived works ought to pass on the right to choose the license for the derived work under the GPL, but since (a) the above is not in the legal terms, and (b) the downstream recipients would be bound by the terms of the GPL anyway, and that requires the use of the GPL itself, this would make no difference whatsoever.

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}
#119 lore raw
Quoted 9 lines · Alexandre Oliva
Quoted 2 lines

It *DOES* *NOT* say "All rights that you have". It says "All rights that are granted you by this license".

I suggest you to reboot into memtest ;-)  The preamble of GPLv2 says:

  For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So if I am a sole author of a program and I chose to distribute it under GPL then all recepients will get _all_ my rights, including right to re-license the program under BSD or a proprietory license? Yeah, riiight...

Thankfully it is just preamble and not the actual license text.

Signature · 1 line
Dmitry
#120 lore raw
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines · Alexandre Oliva

  For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So if I am a sole author of a program and I chose to distribute it under GPL

then you're not a licensee, you're a licensor, and these terms don't apply to you. Already covered upthread BTW.

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}
#121 lore raw
Quoted 8 lines · Alexandre Oliva
Quoted 5 lines · Dmitry Torokhov
Quoted 4 lines · Alexandre Oliva

For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Quoted 5 lines
Quoted 2 lines

So if I am a sole author of a program and I chose to distribute it under GPL

then you're not a licensee, you're a licensor, and these terms don't apply to you.

Heh. When you change a GPLed program and pass your changes you are the licensor for the new code. You still have a right and license pieces of the code you wrote under different license but you do not pass that right to recepient of modified work.

Signature · 1 line
Dmitry
#122 lore raw
Quoted 12 lines · Dmitry Torokhov
Quoted 11 lines · Alexandre Oliva
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines · Alexandre Oliva

For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So if I am a sole author of a program and I chose to distribute it under GPL

Quoted 7 lines
Quoted 2 lines

then you're not a licensee, you're a licensor, and these terms don't apply to you.

Heh. When you change a GPLed program and pass your changes you are the licensor for the new code. You still have a right and license pieces of the code you wrote under different license but you do not pass that right to recepient of modified work.

You are the author of the change, and you can license them however you like. Your change itself is not bound by the terms of the GPL, it is only if it is a derived work of the GPLed work.

If your change is not a derived work, you're not bound by the terms of the GPL as far as the change is concerned, so the GPL has no say whatsoever as to how you must release it. If you choose the GPL, then you're a licensor, and the requirements to pass on all the rights you have do not apply.

If it *is* a derived work, then you're constrained by the terms of the license, and you can only distribute it under the same license. You don't have a right to offer it under a different license in the first place, so you can't pass this right on.

Derived work or not, when you combine that change with the program, then you're bound by the terms of the license, and then you cannot change the licensing terms of the whole program, so you can't pass this right on either.

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}
#123 lore raw
Quoted 24 lines · Alexandre Oliva
Quoted 12 lines · Dmitry Torokhov
Quoted 11 lines · Alexandre Oliva
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines · Alexandre Oliva

For example, 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So if I am a sole author of a program and I chose to distribute it under GPL

Quoted 7 lines
Quoted 2 lines

then you're not a licensee, you're a licensor, and these terms don't apply to you.

Heh. When you change a GPLed program and pass your changes you are the licensor for the new code. You still have a right and license pieces of the code you wrote under different license but you do not pass that right to recepient of modified work.

You are the author of the change, and you can license them however you like.

[... skip...]

Quoted 6 lines

Derived work or not, when you combine that change with the program, then you're bound by the terms of the license, and then you cannot change the licensing terms of the whole program, so you can't pass this right on either.

Ok, consider non-derived work. Because I am distributing whole program I have to do it under GPL. However I still have the right to distribute just the portion that is written by me under whatevel license I want but you as a recepient of GPLed whole do not get this right. IOW I am not passing all the rights _I have_.

Signature · 1 line
Dmitry
#124 lore raw
Quoted 1 line · Dmitry Torokhov

Ok, consider non-derived work.

I did, you snipped it out:

Quoted 11 lines
Quoted 5 lines

If your change is not a derived work, you're not bound by the terms of the GPL as far as the change is concerned, so the GPL has no say whatsoever as to how you must release it. If you choose the GPL, then you're a licensor, and the requirements to pass on all the rights you have do not apply.

Because I am distributing whole program
I have to do it under GPL. However I still have the right to distribute just the portion that is written by me under whatevel license I want but you as a recepient of GPLed whole do not get this right. IOW I am not passing all the rights _I have_.

I see what you mean. IANAL, but I don't think that's how it works.

When your work is not a derived work, the GPL that applies to the rest of the program does not make you a licensee, and it only covers your work if you choose to license it that way. And then, you're the sole licensor of that piece of the work.

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}
#125 lore raw
Quoted 12 lines · Alexandre Oliva
Quoted 1 line · Dmitry Torokhov

Ok, consider non-derived work.

I did, you snipped it out:

Quoted 5 lines
Quoted 5 lines

If your change is not a derived work, you're not bound by the terms of the GPL as far as the change is concerned, so the GPL has no say whatsoever as to how you must release it. If you choose the GPL, then you're a licensor, and the requirements to pass on all the rights you have do not apply.

Yes, I did, thank you for putting the text back in.

Quoted 2 lines
Quoted 2 lines

Because I am distributing whole program
I have to do it under GPL.

Please notice this sentence. GPL still influences the way I release stuff (if I want to release the work as whole) but it does not mean passing all rigths I could possibly have.

Quoted 11 lines
Quoted 4 lines

However I still have the right to
distribute just the portion that is written by me under whatevel license I want but you as a recepient of GPLed whole do not get this right. IOW I am not passing all the rights _I have_.

I see what you mean. IANAL, but I don't think that's how it works.

When your work is not a derived work, the GPL that applies to the rest of the program does not make you a licensee, and it only covers your work if you choose to license it that way. And then, you're the sole licensor of that piece of the work.

So, with regard to TIVO, why are you saying that GPL shoudl affect their hardware (I assume that key check/enforce is done in firmware taht is separate from kernel image)?

Signature · 1 line
Dmitry
#126 lore raw
Quoted 2 lines · Dmitry Torokhov

So, with regard to TIVO, why are you saying that GPL shoudl affect their hardware

I'm not.

I'm just saying that TiVO, as a licensee of Linux, agreed that it wouldn't impose further restrictions on recipients of Linux on the exercise of the rights granted by the license.

So, just like it couldn't use a patent to stop people from modifying or sharing Linux, it can't use the hardware to do that.

And if they fail to supply portions of the functional source code in order to prevent modified versions to run, they are infringing the spirit and quite possibly the letter 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}
#127 lore raw
In reply to Alexandre Oliva
Quoted 2 lines · Alexandre Oliva

I see what you mean. IANAL, but I don't think that's how it works.

Why the hell do you keep saying that?

There *are* lawyers who have said that what Tivo did was legal. They were the FSF's own lawyers. So now you're saying "I am not a lawyer, but that's not right".

So you're trying to state some legal point, admitting that you're not a lawyer, and admitting that actual real-life lawyers disagree with you?

So please explain why the *hell* you would expect us to take your points seriously?

Linus

#128 lore raw
Quoted 5 lines · Linus Torvalds
Quoted 2 lines · Alexandre Oliva

I see what you mean. IANAL, but I don't think that's how it works.

There *are* lawyers who have said that what Tivo did was legal.

What I wrote above had ZERO to do with TiVO. Please re-read the message you responded to, and the two previous messages in that sub-thread for the context you snipped out.

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}
#129 lore raw
In reply to Alexandre Oliva
Quoted 29 lines · On Thursday 14 June 2007 02:55:52 Alexandre Oliva wrote:
Quoted 10 lines · Bongani Hlope
Quoted 4 lines · On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:

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.

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.

Can they modify the software in their device?

Do they pass this right on?

Quoted 5 lines
Quoted 3 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

It does, can't you modify their kernel source?

It's not the kernel source. That's not where the TiVo anti-tampering machinery blocks modifications.

It's about that copy of the kernel that ships in the device in object code. That's the one that TiVo customers ought to be entitled to modify, if TiVo can modify it itself.

Quoted 8 lines
Quoted 2 lines

Where does it say you should be able to run you modifications on the same hardware?

Where it says that you should pass on all the rights that you have.

While TiVo retains the ability to replace, upgrade, fix, break or make any other change in the GPLed software in the device, it ought to pass it on to its customers.

So according to your logic, I can go to Sharp's website and download the GPL source code for their Zaurus. But I don't own a Sharp Zaurus; to keep with your interpretation of the spirit of GPL, they have to give me a Zaurus so that I can run my modifications on the same hardware?

#130 lore raw
Quoted 10 lines · Bongani Hlope
Quoted 3 lines · On Thursday 14 June 2007 02:55:52 Alexandre Oliva wrote:

While TiVo retains the ability to replace, upgrade, fix, break or make any other change in the GPLed software in the device, it ought to pass it on to its customers.

So according to your logic, I can go to Sharp's website and download the GPL source code for their Zaurus. But I don't own a Sharp Zaurus; to keep with your interpretation of the spirit of GPL, they have to give me a Zaurus so that I can run my modifications on the same hardware?

Sharp can modify the copy of the code in your Zaurus as much as you do, when you don't have a Zaurus. I don't see how you can get to the conclusion that they have to give you a Zaurus, when all you're getting is 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}
#131 lore raw
In reply to Bongani Hlope
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

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

Quoted 7 lines
Quoted 2 lines

So, TiVo includes a copy of Linux in its DVR.

And they give you the same right that they had, which is obtain free software that you can modify and redistribute. There's nothing in there that says they should give you the tools they used after they received the software, which is what you seem to be looking for.

IANAL so I won't comment on the legal aspects of TiVo's doing.

However it definitely is against _MY_ understanding of the spirit of the GPL. At least to me that's quite obvious. I'm sure you all know the story of the printer driver RMS couldn't fix that reportedly made him start the whole FSF business.

Looking at what TiVo did I realize glaring similarities.

<disclaimer>
I'm in no way related with the FSF. I hereby state I'm not parroting anyone's else position but have come to this conclusion solely on my own.
</disclaimer>

Quoted 6 lines
Quoted 3 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

It does, can't you modify their kernel source? Where does it say you should be able to run you modifications on the same hardware?

Come on! The whole idea of software is to have it run on some HW. Why would I want to change it in the first place if I can't run it ?

If what they did is actually allowed by the wording of the legal phrases of the GPLv2 then that IMO is a loophole w/r to the spirit (as I understand) it and IMO should be plugged.

Quoted 3 lines

The only fear that I have with the whole Tivo saga, is that companies like Dell can use the same thing to say: "Our hardware will only run Company's X distribution of Linux".

Would not such a restriction voilate the spirit of the GPL ?

Anyway, my simplistic view is:
Once it is under the GPL I could change it and actually make the changes work as I see fit.

That's what I think my freedom as of the GPL is about.

Now all that needs to be done is make sure the legal phrases are such that they convince the judges they actually mean this in court too.

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
#132 lore raw
Quoted 1 line · Michael Gerdau
Quoted 1 line

able to run you modifications on the same hardware?

                                         ^^^^
Quoted 1 line

Come on! The whole idea of software is to have it run on some HW.

                                                           ^^^^
Quoted 1 line

Why would I want to change it in the first place if I can't run it ?

See the difference?

#133 lore raw
Quoted 7 lines
Quoted 1 line
Quoted 1 line

able to run you modifications on the same hardware?

                                         ^^^^
Quoted 1 line

Come on! The whole idea of software is to have it run on some HW.

                                                           ^^^^
Quoted 1 line

Why would I want to change it in the first place if I can't run it ?

See the difference?

Forgive my poor mastery of the english language and me letting slip this inconsistency.

The first sentence you cited was a general remark IMO valid outside of this context and possibly ill placed as it was.

The second sentence pertains the key msg I was trying to deliver and apparently I did a poor job in phrasing it so let me redo it:
Why would I want to change the SW targetted for some HW if I can't run the changed version on said HW ?

[note that for the TiVo case I possibly would not own or be able to own similar HW being able to run my modified SW; so even some HW would not
be triggered either] ^^^^

Remember I'm discussing my understanding of the spirit of the GPL, not whether the legal part actually does give me that right enforceable in court.

Here is another stmt which is valid outside of this context AFAIAC:
If the GPLv2 does not legally give me the right that I think its spirit gives me then the legal phrases should be changed to achieve that.

Whether or not others share my view of what the spirit of the GPL implies is completely theirs to decide and if they differ they likely won't agree on my previous stmt either. Fine with me.

And this leads to another observation:
IMO this thread is partly fueled by a fundamental mixing of PoVs. Some argue based on their perceived view of the spirit of the GPL and some based on the actual legal phrases in GPLv2 and GPLv3 and whether or how they reflect the perceived spirit.

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
#134 lore raw
In reply to Michael Gerdau
Quoted 8 lines · Michael Gerdau
Quoted 5 lines
Quoted 3 lines

TiVo retains the right to modify that copy of Linux as it sees fit.

It doesn't give the recipients the same right.

It does, can't you modify their kernel source? Where does it say you should be able to run you modifications on the same hardware?

Come on! The whole idea of software is to have it run on some HW. Why would I want to change it in the first place if I can't run it ?

Maybe this quote will summarize the situation:

Judith: [on Stan's desire to be a mother] Here! I've got an idea: Suppose you
agree that he can't actually have babies, not having a womb - which is nobody's fault, not even the Romans' - but that he can have the *right* to have babies.
Francis: Good idea, Judith. We shall fight the oppressors for your right to
have babies, brother... sister, sorry.
Reg: What's the *point*?
Francis: What?
Reg: What's the point of fighting for his right to have babies, when he can't
have babies?
Francis: It is symbolic of our struggle against oppression.
Reg: It's symbolic of his struggle against reality.

-- Monty Python's "Life of Brian"

#135 lore raw
In reply to Alexandre Oliva

On Wednesday 13 June 2007 19:49:23 Alexandre Oliva wrote:
<snip>

Quoted 12 lines
Quoted 2 lines

The fact is, Tivo didn't take those rights away from you, yet the FSF says that what Tivo did was "against the spirit". That's *bullshit*.

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.

Are you an idiot, or do you just choose to ignore all proof that doesn't fit your preconceived beliefs? TiVO gives you every right to the Linux kernel that they recieved. What they don't give you the right to do is use modified versions on their *HARDWARE* - which they have *NEVER* given you any rights to, except for "normal use". (And no, it isn't legal to put those 200G hard drives in your TiVO no matter what you think)

Quoted 9 lines
Quoted 1 line

In other words, GPLv3 restricts rights that do not need to be restricted,

That's correct. They don't need to be restricted. The whole idea of copyleft, implemented through the GPL, is not based on needs, but rather on the wish to defend the freedoms established in the preamble from those who would rather not respect them.

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.

Do you understand that, or do I need to break out the finger-puppets next ?

Quoted 7 lines

Do you deny that they can still do it themselves?

Quoted 2 lines

Think of it this way: what if the GPLv3 had an addition saying "You can not use this software to make a weapon".

This would make GPLv3 a non-Free Software license.

Quoted 8 lines

But the GPLv3 last call draft doesn't say anything along these lines.

You can use the software as much as you like, even in DVRs, and even to implement DRM in them, as long as you respect the users' freedoms to change and share the software. Per the GPLv3 (paraphrased), if it is possible to install modified versions of the covered program in the device, you must tell the recipient how to do it. Otherwise, the freedom to modify the program is being too severely limited.

And this unnaturally restricts the freedom of hardware manufacturers. If they add a custom, internal connector so a repair shop can restore the hardware to its *FACTORY* state then it is "possible to install modified versions", provided the person doing it has the specialized hardware needed.

And this is what the FSF, RMS and yes, *YOU*, Alexandre, fail to realize - the GPL covers *ONLY* the software. It has *ZERO* legal standing when applied to hardware. Not even the most draconian of MS EULA's tries to apply itself to the hardware.

In the case of 99% of the hardware targeted by the clause of the GPLv3 you elucidate on, the "ability to install modified versions of the software" was *NOT* intended for that use, nor was it intended for *ANYONE* *EXCEPT* trained service personell to have *ACCESS* to that functionality. Arguing otherwise is just idiotic - I have never found a piece of "high tech" hardware (like a TiVO) that was designed for the end-user to modify. (yes, installing a new version of the linux kernel is "modifying" the system)

Quoted 3 lines

And, in the particular case of TiVo, it's a case of distributing incomplete source code, of refraining from including functional portions of the source code.

And? They distribute the kernel source - as they recieved it - in compliance with the GPL. Their additions - whether they be "modules" or just the UI - do not, necessarily, fall under the GPL. (Yes, there have been discussions about whether a kernel module is a derived work, but most of the time those discussions ended "Legally they aren't, even though I feel they should be")

Quoted 13 lines
Quoted 2 lines

In other words, GPLv3 *restricts* peoples freedoms more than it protects them.

While you look at it from the point of view of TiVo, who wants to be free to prohibit people from modifying the workings of the device it sells while it can still modify it itself, and it does that in order to prohibit people from removing locks that stop them from doing things they're legally entitled to do, I see a lot more prohibitions than freedoms in what TiVo does. I don't understand why you'd stand up for it. Is it more important that a single company be allowed to impose prohibitions on others in order for its business model to work, than to maintain the spirit of hacking and sharing that enabled Free Software and Linux to flourish?

What "Legally Entitled" things?

And... You do realize that almost every difference between the GPLv2 and the GPLv3 is going to cause a hell of a lot of problems? The fact that the GPLv3 is designed to prevent things that RMS *PERSONALLY* finds distasteful - DRM and the like - is a big turn-off for a *LOT* of people. (Personally I don't like *ANY* version of the GPL, because there are chunks I have problems with)

Quoted 2 lines

Do you expect Linux would have flourished if computers had locks that stopped people from modifying Linux in them?

But you aren't talking about a "computer" here. You're talking about a mass-market device that must comply with both US and International copyright law - and that's just a TiVO. Other devices have other laws they have to comply with - in the US the FCC's regulations control all radio devices, so if you upload a modified linux kernel to your wireless router that gives it a 2000 foot range, you've just broken the law *AND* violated the license on the hardware which states that you "won't modify it or the controlling software" - in most cases "the controlling software" is just the firmware, but with modern wireless hardware, the firmware is loaded by the OS.

Quoted 5 lines
Quoted 2 lines

where I added the "that you can do so in place on your devices, even if those devices weren't licensed under the GPL".

You're mistakenly focusing on the device. As you say, the device is not under the license.

But he isn't. The GPLv3 says, and I'll quote you here - "Per the GPLv3 (paraphrased), if it is possible to install modified versions of the covered program in the device, you must tell the recipient how to do it."

Quoted 1 line

From the latest version of the GPLv3:

"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

and:

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

So it's not just a designed in ability to run modified code - ie: running of modified code is a feature meant for the user to take advantage of - but even things like the connectors used to upload the operating software at the factory that people now cannot have in a device that runs GPL(v3) covered software unless they ship the related "Installation Information". In other words, companies are no longer allowed to have a completely separate license for hardware and software.

That, to me, reads like RMS got mad about TiVO and said "I don't like it, lets add a clause making it wrong to the next GPL". Hell, that *IS* what happened, and nothing the FSF or Eben Moglen says will convince me otherwise. It's the same for the bits that were added after Novell signed their agreement with MS.

Quoted 3 lines

What's under the license is the software in it. And that license spirit requires the distributor to pass on the right to modify the software.

And since when did they have to enable people to use their hardware in violation of the licensing agreement they implicitly agree to when opening the package?

There is *NOTHING* stopping you from doing whatever you want with the code that runs on a TiVO (or any similar device). You (and everyone that thinks like you) are confusing a want to use the *HARDWARE* however you want with your GPL granted "right" to do what you want with the *SOFTWARE*.

Quoted 6 lines
Quoted 4 lines

I don't know if you've followed US politics very much over the last six years, but there's been a lot of "protecting our freedoms" going on. And it's been ugly. Maybe you could realize that sometimes "protecting your freedom" is *anything*but*!

Is this why you're overreacting?

No, he's making a point. RMS and the FSF, in drafting GPLv3 to include the language and clauses it does, is "protecting your freedom" the way a lot of the post 9/11 changes to the US Federal code does it. (ie: by saying "no, you can't do that anymore")

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#136 lore raw
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* covered by the GPL.

Indeed, TiVO has this legal right. But then they must not use software under the GPLv3 in it. And, arguably, they must not use software under the GPLv2 either.

Quoted 7 lines

In the case of 99% of the hardware targeted by the clause of the GPLv3 you elucidate on, the "ability to install modified versions of the software" was *NOT* intended for that use, nor was it intended for *ANYONE* *EXCEPT* trained service personell to have *ACCESS* to that functionality. Arguing otherwise is just idiotic - I have never found a piece of "high tech" hardware (like a TiVO) that was designed for the end-user to modify. (yes, installing a new version of the linux kernel is "modifying" the system)

It's about time for a change for better, wouldn't you think?

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Quoted 2 lines

And? They distribute the kernel source - as they recieved it - in compliance with the GPL.

This makes it seem like you think that passing on the source code is enough to comply with the GPL. Check your assumptions. It's not.

Quoted 4 lines
Quoted 2 lines

to prohibit people from removing locks that stop them from doing things they're legally entitled to do

What "Legally Entitled" things?

Time shifting of any shows, creating copies of shows for personal use, letting others do so. Think fair use, and how TiVO software and DRM in general gets in the way.

Quoted 2 lines

And... You do realize that almost every difference between the GPLv2 and the GPLv3 is going to cause a hell of a lot of problems?

For those who are not willing to abide by the spirit of the license, yes. Does it look like I'm concerned about them? If they're willing to look for and maybe even find holes in the license to disrespect users' freedoms, why should I worry about the problems that plugging these holes is going to cause them? If they'd taken the spirit of the GPL for what it is, instead of looking for loopholes, this improved wording wouldn't be causing them any problems whatsoever.

Quoted 3 lines

The fact that the GPLv3 is designed to prevent things that RMS *PERSONALLY* finds distasteful - DRM and the like - is a big turn-off for a *LOT* of people.

This is a pretty sad accusation. 2/3s of the Free Software packages use the GPL with its existing spirit, and you still haven't shown that any changes proposed in GPLv3 fail to abide by the same spirit. That some (many?) people misunderstood or disregarded the spirit is an unfortunate fact, but trying to pose the patching that's going into GPLv3 as if it was a matter of personal taste, rather than improved compliance with the spirit, is unfair and uncalled for.

Quoted 2 lines

(Personally I don't like *ANY* version of the GPL, because there are chunks I have problems with)

What are you doing lurking and spreading confusion in a list about a project that chose to use it, then?

Quoted 6 lines
Quoted 2 lines

Do you expect Linux would have flourished if computers had locks that stopped people from modifying Linux in them?

But you aren't talking about a "computer" here. You're talking about a mass-market device that must comply with both US and International copyright law - and that's just a TiVO.

Oh, sorry. I missed when the meaning of the word computer was narrowed from "machine with a general-purpose microprocessor, memory and other peripherals" to whatever you decide it is.

And then, the GPL doesn't talk about computers at all. It's not about the hardware, it's about the software, remember? ;-)

Quoted 2 lines

if you upload a modified linux kernel to your wireless router that gives it a 2000 foot range, you've just broken the law

At which point, you get punished by the law system.

Quoted 2 lines

*AND* violated the license on the hardware which states that you "won't modify it or the controlling software"

Err.. The hardware licensor who includes software under the GPL be supposed to be a licensee of the software in order to have legal permission to distribute it, at which point the following provision kicks in:

6. Each time you redistribute the Program (or any work based on the Program) [...] You may not impose any further restrictions on the recipients' exercise of the rights granted herein. [...]

And here's one of the rights granted herein that would be restricted by this hardware license:

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program,

So such a restriction in the hardware license seems to be failure to comply with the GPL, which means the violator may lose the license.

Quoted 4 lines

even things like the connectors used to upload the operating software at the factory that people now cannot have in a device that runs GPL(v3) covered software unless they ship the related "Installation Information".

This sounds like a reasonable point. Please bring it up at gplv3.fsf.org. If it requires specialized hardware to modify the software in the device, the hardware manufacturer can't modify the software without cooperation from the user, and then perhaps it would be fair for the user to need cooperation from the manufacturer.

Quoted 4 lines

That, to me, reads like RMS got mad about TiVO and said "I don't like it, lets add a clause making it wrong to the next GPL". Hell, that *IS* what happened, and nothing the FSF or Eben Moglen says will convince me otherwise.

If you've already made your mind about this, in spite of not having the facts, I guess it doesn't make sense for me to waste my time trying to convince you, does it?

Quoted 7 lines
Quoted 3 lines

What's under the license is the software in it. And that license spirit requires the distributor to pass on the right to modify the software.

And since when did they have to enable people to use their hardware in violation of the licensing agreement they implicitly agree to when opening the package?

Since they got permission to distribute the software under the condition of passing on the freedoms without imposing further restrictions on their exercise.

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}
#137 lore raw

since the latest draft of the GPLv3 now discriminates against some uses (industrial vs commercial I think are the terms used) does it even qualify as a Open Source lincense anymore by the OSI terms?

David Lang

#138 lore raw
Quoted 2 lines · On Jun 13, 2007, [email protected] wrote:

since the latest draft of the GPLv3 now discriminates against some uses (industrial vs commercial I think are the terms used)

A "User Product" is either (1) a "consumer product," which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.

Quoted 2 lines

does it even qualify as a Open Source lincense anymore by the OSI terms?

The definition is about the hardware, not the software, so it may still qualify.

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}
#139 lore raw
In reply to Alexandre Oliva
Quoted 10 lines · On Wednesday 13 June 2007 22:38:05 Alexandre Oliva wrote:
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* covered by the GPL.

Indeed, TiVO has this legal right. But then they must not use software under the GPLv3 in it. And, arguably, they must not use software under the GPLv2 either.

Yes. It can be argued. But I cannot find *ANYTHING* in the GPLv2 that stops anyone from doing that, unless you add extra meaning to one specific clause. (And I am willing to admit that *MOST* people do give it that extra meaning)

Quoted 10 lines
Quoted 8 lines

In the case of 99% of the hardware targeted by the clause of the GPLv3 you elucidate on, the "ability to install modified versions of the software" was *NOT* intended for that use, nor was it intended for *ANYONE* *EXCEPT* trained service personell to have *ACCESS* to that functionality. Arguing otherwise is just idiotic - I have never found a piece of "high tech" hardware (like a TiVO) that was designed for the end-user to modify. (yes, installing a new version of the linux kernel is "modifying" the system)

It's about time for a change for better, wouldn't you think?

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.

Quoted 2 lines

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Faulty logic. I have yet to find a computer that I couldn't change the OS on. I have run Linux on 3 different Mac's, every x86 machine I've ever owned and even had it running on my Palm. Whats more is that I have *never* heard of a person that knows what they are doing not being able to change the OS on a desktop computer.

Quoted 5 lines
Quoted 2 lines

And? They distribute the kernel source - as they recieved it - in compliance with the GPL.

This makes it seem like you think that passing on the source code is enough to comply with the GPL. Check your assumptions. It's not.

Hrm. Strange, but thats what most companies think. Hell, it even says that you have to do just that in the GPL. If you're talking about the fact that it can be argued that they are "distributing" Linux by selling their boxes and its a modified version then I'll agree with you.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

to prohibit people from removing locks that stop them from doing things they're legally entitled to do

What "Legally Entitled" things?

Time shifting of any shows, creating copies of shows for personal use, letting others do so. Think fair use, and how TiVO software and DRM in general gets in the way.

I thought that time shifting and creating personal copies was what the TiVO did already. Or do you mean "transferring the recorded copies off the TiVO and on to a different medium"? If that is what you mean by "Creating Copies" then, IIRC, you're wrong. DRM, I do agree, gets in the way of "Fair Use".

Quoted 10 lines
Quoted 2 lines

And... You do realize that almost every difference between the GPLv2 and the GPLv3 is going to cause a hell of a lot of problems?

For those who are not willing to abide by the spirit of the license, yes. Does it look like I'm concerned about them? If they're willing to look for and maybe even find holes in the license to disrespect users' freedoms, why should I worry about the problems that plugging these holes is going to cause them? If they'd taken the spirit of the GPL for what it is, instead of looking for loopholes, this improved wording wouldn't be causing them any problems whatsoever.

Okay. So you're not concerned that you're potentially pushing companies that would otherwise be major consumers of GPL'd software away? That doesn't make sense to me.

Quoted 11 lines
Quoted 3 lines

The fact that the GPLv3 is designed to prevent things that RMS *PERSONALLY* finds distasteful - DRM and the like - is a big turn-off for a *LOT* of people.

This is a pretty sad accusation. 2/3s of the Free Software packages use the GPL with its existing spirit, and you still haven't shown that any changes proposed in GPLv3 fail to abide by the same spirit. That some (many?) people misunderstood or disregarded the spirit is an unfortunate fact, but trying to pose the patching that's going into GPLv3 as if it was a matter of personal taste, rather than improved compliance with the spirit, is unfair and uncalled for.

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

And why shouldn't I pose it as a matter of "Personal Taste"? The biggest and most powerful voice in the FSF says "I don't like Tivoization" and "I don't like DRM" and when the GPLv3 appears it has language that makes those violations of the license. Just like people have started using "GNU/Linux" or "GNU+Linux" to refer to Linux - a big voice spoke and said "It should be GNU/Linux" and it happens. (Not that I really have anything against that - though I feel that "GNU/Linux" gives the wrong impression)

Quoted 5 lines
Quoted 2 lines

(Personally I don't like *ANY* version of the GPL, because there are chunks I have problems with)

What are you doing lurking and spreading confusion in a list about a project that chose to use it, then?

Just because I don't like the license doesn't make disqualify me from liking something that uses the license. And I doubt I've "confused" anyone - where I have someone has caught it and called me on it.

Quoted 10 lines
Quoted 6 lines
Quoted 2 lines

Do you expect Linux would have flourished if computers had locks that stopped people from modifying Linux in them?

But you aren't talking about a "computer" here. You're talking about a mass-market device that must comply with both US and International copyright law - and that's just a TiVO.

Oh, sorry. I missed when the meaning of the word computer was narrowed from "machine with a general-purpose microprocessor, memory and other peripherals" to whatever you decide it is.

The word "Computer", in the manner I used it there, means "General Purpose Computational Device". A "TiVO" is not, and has never been, a "General Purpose Computational Device".

(Perhaps I should have made the above clear)

Quoted 2 lines

And then, the GPL doesn't talk about computers at all. It's not about the hardware, it's about the software, remember? ;-)

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.

Quoted 4 lines
Quoted 2 lines

if you upload a modified linux kernel to your wireless router that gives it a 2000 foot range, you've just broken the law

At which point, you get punished by the law system.

But the GPLv2 gives companies a chance to protect themselves from legal actions by people that are sure to follow. With the GPLv3 they have none, because it becomes a case of "I was just doing what I have the right to do under the license for the software. If I wasn't supposed to do it, they shouldn't have made it possible."

Quoted 11 lines
Quoted 2 lines

*AND* violated the license on the hardware which states that you "won't modify it or the controlling software"

Err.. The hardware licensor who includes software under the GPL be supposed to be a licensee of the software in order to have legal permission to distribute it, at which point the following provision kicks in:

6. Each time you redistribute the Program (or any work based on the Program) [...] You may not impose any further restrictions on the recipients' exercise of the rights granted herein. [...]

Hrm... I'd forgotten that clause entirely. That must be why I can't find a WRT-54GL anywhere in the US anymore...

Quoted 8 lines

And here's one of the rights granted herein that would be restricted by this hardware license:

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program,

So such a restriction in the hardware license seems to be failure to comply with the GPL, which means the violator may lose the license.

My apologies. As I said above I totally forgot about section 6.

Quoted 10 lines
Quoted 4 lines

even things like the connectors used to upload the operating software at the factory that people now cannot have in a device that runs GPL(v3) covered software unless they ship the related "Installation Information".

This sounds like a reasonable point. Please bring it up at gplv3.fsf.org. If it requires specialized hardware to modify the software in the device, the hardware manufacturer can't modify the software without cooperation from the user, and then perhaps it would be fair for the user to need cooperation from the manufacturer.

Will do. I'm surprised that this situation never came up before, actually.

Quoted 8 lines
Quoted 4 lines

That, to me, reads like RMS got mad about TiVO and said "I don't like it, lets add a clause making it wrong to the next GPL". Hell, that *IS* what happened, and nothing the FSF or Eben Moglen says will convince me otherwise.

If you've already made your mind about this, in spite of not having the facts, I guess it doesn't make sense for me to waste my time trying to convince you, does it?

You've made some well reasoned and supported arguments here. I respect RMS and Eben Moglen because of what they've done, but that doesn't mean I have to like them. However, you are free to (try) to change my mind about them.

Quoted 11 lines
Quoted 7 lines
Quoted 3 lines

What's under the license is the software in it. And that license spirit requires the distributor to pass on the right to modify the software.

And since when did they have to enable people to use their hardware in violation of the licensing agreement they implicitly agree to when opening the package?

Since they got permission to distribute the software under the condition of passing on the freedoms without imposing further restrictions on their exercise.

Okay. Given the interpretation of GPLv2 you seem to have I will grant you this point. Personally, I do not feel that the "spirit" of the GPLv2 has anything to do with running modified binaries on a "closed" hardware platform (like a TiVO). But, as I said, I'll grant you the point, because our views on the "spirit" of the GPL and interpretations of it seem to be completely incompatible.

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#140 lore raw
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?

Quoted 5 lines · On Wednesday 13 June 2007 22:38:05 Alexandre Oliva wrote:
Quoted 2 lines

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Faulty logic. I have yet to find a computer that I couldn't change the OS on.

I was not talking about installing another OS, I was talking about making changes to the OS. As in, improving one particular driver, avoiding a blue screen, stuff like that.

Quoted 2 lines

Or do you mean "transferring the recorded copies off the TiVO and on to a different medium"?

Sure. Such that I can watch shows while wasting time in public transportation, in an airplane, whatever.

Quoted 1 line

DRM, I do agree, gets in the way of "Fair Use".

And the fact that TiVO can be, and has been modified remotely to add restrictions on what users could do, means nothing you do with it is safe. You, and everything you've recorded with the TiVO, are at the mercy of this one company.

Quoted 3 lines

So you're not concerned that you're potentially pushing companies that would otherwise be major consumers of GPL'd software away? That doesn't make sense to me.

What would their consuming GPL software buy us, if they won't respect users' freedoms, which is the very reason behind the GPL?

Heck, if they don't want to play by the rules, that's up to them. But then they shouldn't use the software at all.

Yeah, I wish they'd rather play by the rules, but if they don't want to, too bad, for us and for them.

Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

BTW, what license is Linux licensed under? It's GPLv2 plus userland exception, right? (There's some additional module exception, right?)

Quoted 4 lines

And why shouldn't I pose it as a matter of "Personal Taste"? The biggest and most powerful voice in the FSF says "I don't like Tivoization" and "I don't like DRM" and when the GPLv3 appears it has language that makes those violations of the license.

Have you ever wondered *why* he doesn't like them?

Could it possibly be because they harm the goal of his life, which is to enable people to live their digital lives in freedom?

Quoted 2 lines

Just like people have started using "GNU/Linux" or "GNU+Linux" to refer to Linux

No, no, you got it wrong. Linux is the kernel. GNU was the nearly-complete operating system it fit in. GNU+Linux is a complete operating system.

And you don't have to believe me, believe Linus, the initial author of Linux:

http://www.kernel.org/pub/linux/kernel/Historic/old-versions/RELNOTES-0.01

Although linux is a complete kernel

Sadly, a kernel by itself gets you nowhere. To get a working system you need a shell, compilers, a library etc. These are separate parts and may be under a stricter (or even looser) copyright. Most of the tools used with linux are GNU software and are under the GNU copyleft.

Quoted 2 lines

A "TiVO" is not, and has never been, a "General Purpose Computational Device".

Err... Last I looked it was a bunch of general-purpose components, packaged in a way that made it not look like a general-purpose computer. Who gets to decide? And with what motivations?

Quoted 3 lines

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.

2. You may modify your copy or copies of the Program or any portion of it

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

if you upload a modified linux kernel to your wireless router that gives it a 2000 foot range, you've just broken the law

At which point, you get punished by the law system.

But the GPLv2 gives companies a chance to protect themselves from legal actions by people that are sure to follow.

So does the GPLv3. It might be a bit narrower, to cut on other kinds of abuses, but all constraints I'm aware of that are mandated by law can still be achieved. The point is to forbid disrespecting users' freedoms to modify the software. Configuration parameters for the hardware, needed to comply with regulations, can be easily taken care of without disrespecting users' 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}
#141 lore raw
Quoted 7 lines · On Thursday 14 June 2007 01:51:13 Alexandre Oliva wrote:
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?

Nope. I've been tempted several times, but decided that the extra bits I'd thought about wouldn't add anything to the device.

Quoted 10 lines
Quoted 6 lines · On Wednesday 13 June 2007 22:38:05 Alexandre Oliva wrote:
Quoted 2 lines

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Faulty logic. I have yet to find a computer that I couldn't change the OS on.

I was not talking about installing another OS, I was talking about making changes to the OS. As in, improving one particular driver, avoiding a blue screen, stuff like that.

Ah, well... In the case of "Windos" and other proprietary OS's I try to educate people and get them to switch. I don't, personally, have any computers that run Windows (and I switched my Palm back to PalmOS because it wasn't getting the same performance under Linux - which rather surprised me. And rather than fight with it I just switched it back.

Quoted 5 lines
Quoted 2 lines

Or do you mean "transferring the recorded copies off the TiVO and on to a different medium"?

Sure. Such that I can watch shows while wasting time in public transportation, in an airplane, whatever.

Under the US Copyright law I'm not sure that making a "second copy" like that is legal. IIRC, "Fair Use" only allows for one copy.

Quoted 6 lines
Quoted 1 line

DRM, I do agree, gets in the way of "Fair Use".

And the fact that TiVO can be, and has been modified remotely to add restrictions on what users could do, means nothing you do with it is safe. You, and everything you've recorded with the TiVO, are at the mercy of this one company.

As has been noted in their TOS and the licenses for the hardware from the start. The FSF itself explicitly reserves the right to change the GPL at any time - which is no different. (when you remove all the bits explaining the purpose of the license)

Quoted 6 lines
Quoted 3 lines

So you're not concerned that you're potentially pushing companies that would otherwise be major consumers of GPL'd software away? That doesn't make sense to me.

What would their consuming GPL software buy us, if they won't respect users' freedoms, which is the very reason behind the GPL?

I'm not referring to companies that are embedding GPL'd software in their products. The companies I'm referring to are the ones that would like to use GPL'd software internally. A lot of them would probably have private modifications that would never be distributed - and under the GPLv2 it is clear that you can keep modifications private as long as you don't distribute them. "Pushing them away" means that they'd not do that because they would be concerned that the license will change under them in such a way that even those private modifications need to be released to the public.

(and don't try to argue that even though those modifications are truly private (to the company) they should be released anyway to comply with the "spirit" of the license. It is made clear that it isn't by the text of the license itself)

Quoted 11 lines

Heck, if they don't want to play by the rules, that's up to them. But then they shouldn't use the software at all.

Yeah, I wish they'd rather play by the rules, but if they don't want to, too bad, for us and for them.

Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

But he has. Whether you have accepted that his explanations are valid or not doesn't change the fact.

Quoted 2 lines

BTW, what license is Linux licensed under? It's GPLv2 plus userland exception, right? (There's some additional module exception, right?)

The kernel itself is GPLv2 (only). Individual components - even individual files - have other licenses or retain the "any later version" clause. (Someone pointed out, earlier in this thread, that there is GPLv1.1 code in the kernel)

Quoted 6 lines
Quoted 4 lines

And why shouldn't I pose it as a matter of "Personal Taste"? The biggest and most powerful voice in the FSF says "I don't like Tivoization" and "I don't like DRM" and when the GPLv3 appears it has language that makes those violations of the license.

Have you ever wondered *why* he doesn't like them?

Not really. I've always figured he had reasons similar to mine for not liking DRM. As to his dislike of "Tivoization", well, that I've always attributed to the fact that someone at that company managed to outsmart him. (and no, I wasn't being serious with that last line)

Quoted 9 lines

Could it possibly be because they harm the goal of his life, which is to enable people to live their digital lives in freedom?

Quoted 2 lines

Just like people have started using "GNU/Linux" or "GNU+Linux" to refer to Linux

No, no, you got it wrong. Linux is the kernel. GNU was the nearly-complete operating system it fit in. GNU+Linux is a complete operating system.

Yet I still find people that insist that the *ENTIRE* system - kernel and all - is a GNU project. Not just the common idiot you'd find on almost any street in the US, but also educated people in technical fields. The reason is the name.

*AND* you cut out the bit where I said "I have no problems with it"

Quoted 5 lines

And you don't have to believe me, believe Linus, the initial author of Linux:

http://www.kernel.org/pub/linux/kernel/Historic/old-versions/RELNOTES-0.01

Quoted 7 lines

Although linux is a complete kernel

Sadly, a kernel by itself gets you nowhere. To get a working system you need a shell, compilers, a library etc. These are separate parts and may be under a stricter (or even looser) copyright. Most of the tools used with linux are GNU software and are under the GNU copyleft.

Never claimed otherwise. The problem is that using a composite name like that *does* confuse a hell of a lot of people. See my statements above about that.

Quoted 6 lines
Quoted 2 lines

A "TiVO" is not, and has never been, a "General Purpose Computational Device".

Err... Last I looked it was a bunch of general-purpose components, packaged in a way that made it not look like a general-purpose computer. Who gets to decide? And with what motivations?

And so is every game console. But until the original XBox was released nobody tried using one as a "General Purpose" machine. The TiVO wasn't designed as a general purpose machine - it was designed for a specific purpose. That the *easiest* design to produce uses a bunch of general purpose components is an economic choice, nothing else.

I will not, however, argue about this anymore. As with other bits, we've reached a point where we disagree and no amount of explanation will change the others viewpoint. (I hope you understand mine as well as (I think) I understand yours)

Quoted 15 lines
Quoted 3 lines

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.

2. You may modify your copy or copies of the Program or any portion of it

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

if you upload a modified linux kernel to your wireless router that gives it a 2000 foot range, you've just broken the law

At which point, you get punished by the law system.

But the GPLv2 gives companies a chance to protect themselves from legal actions by people that are sure to follow.

Quoted 6 lines

So does the GPLv3. It might be a bit narrower, to cut on other kinds of abuses, but all constraints I'm aware of that are mandated by law can still be achieved. The point is to forbid disrespecting users' freedoms to modify the software. Configuration parameters for the hardware, needed to comply with regulations, can be easily taken care of without disrespecting users' freedoms.

Let me quote Linus here:

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".

In other words, GPLv3 is breaking with its predecessor - it's adding a requirement that doesn't exist in previous versions. *AND* it's dictating terms for *HARDWARE* when it isn't a hardware license. If I release software under the GPL and somebody modifies it to run on a different hardware platform I'll be happy, even if they don't send me a patchset for the new version. If I create a piece of hardware and run Linux on it, but have it locked to a specific version or versions from a specific source (ie: me) and release it to the public, I *WILL* release the version of Linux I'm running on it. What I won't do is release whatever tools and such that are needed to make the hardware run a different version of the kernel. Why? Because: the hardware was designed so that a specific version of the kernel runs without problems, there is hardware that is very picky and running a customized kernel could cause that hardware to fail, etc... There are more reasons than the legal protection I previously mentioned. Not a single one of them is "Because I want to restrict peoples freedoms re: the GPL'd software".

Admittedly the two examples I chose aren't very realistic, but those were the first two examples that came to mind.

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#142 lore raw
Quoted 9 lines · Daniel Hazelton
Quoted 7 lines · On Thursday 14 June 2007 01:51:13 Alexandre Oliva wrote:
Quoted 6 lines · Daniel Hazelton
Quoted 2 lines · On Wednesday 13 June 2007 22:38:05 Alexandre Oliva wrote:

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Faulty logic. I have yet to find a computer that I couldn't change the OS on.

Quoted 6 lines
Quoted 3 lines

I was not talking about installing another OS, I was talking about making changes to the OS. As in, improving one particular driver, avoiding a blue screen, stuff like that.

Ah, well... In the case of "Windos" and other proprietary OS's I try to educate people and get them to switch.

Good. So I presume you'd tell them to switch away from a turned-proprietary GNU/Linux operating system as well, right?

So, again, what do we gain if companies abuse the GPL and disrespect users' rights that we meant them to respect?

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Or do you mean "transferring the recorded copies off the TiVO and on to a different medium"?

Sure. Such that I can watch shows while wasting time in public transportation, in an airplane, whatever.

Under the US Copyright law I'm not sure that making a "second copy" like that is legal. IIRC, "Fair Use" only allows for one copy.

Even if you delete the "first copy"?

Actually, I thought fair use in US entitled you to make a backup copy. So the copy in your TiVO would be your original, and the external copy would be your fair-use backup.

Quoted 2 lines

As has been noted in their TOS and the licenses for the hardware from the start.

If it is used to disrespect the inalienable freedoms associated with the GPL software in the device, it seems like a license violation to me.

Quoted 2 lines

The FSF itself explicitly reserves the right to change the GPL at any time - which is no different.

Actually, it's completely different.

If the FSF revises the GPL, the old version remains available for anyone to use for any new software, and all software released under the old version remains available under that old version.

In contrast, your TiVO may get a software upgrade without your permission that will take your rights away from that point on, and there's very little you can do about it, other than unplugging it from the network to avoid the upgrade if it's not too late already.

Quoted 3 lines

A lot of them would probably have private modifications that would never be distributed - and under the GPLv2 it is clear that you can keep modifications private as long as you don't distribute them.

Likewise with GPLv3.

Quoted 4 lines

"Pushing them away" means that they'd not do that because they would be concerned that the license will change under them in such a way that even those private modifications need to be released to the public.

This would not only change the spirit of the license, but turn it into a non-Free Software license.

And then, again, the license can't possibly be changed from under them. A new revision of the GPL would only affect software licensed under that new revision. If you already got it under an earlier revision, you know what you got, and nobody can take that away from you.

Quoted 4 lines

(and don't try to argue that even though those modifications are truly private (to the company) they should be released anyway to comply with the "spirit" of the license. It is made clear that it isn't by the text of the license itself)

How could you possibly come to the conclusion that forcing anyone to release private modifications would be in compliance with the spirit of the license? can != must

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

But he has. Whether you have accepted that his explanations are valid or not doesn't change the fact.

His explanation is based on a reading of the license that doesn't match what its authors meant. I guess the authors know better what they meant the spirit of the license to be than someone else who studied it a lot but that until very recently couldn't even tell the spirit from the legal terms.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Just like people have started using "GNU/Linux" or "GNU+Linux" to refer to Linux

No, no, you got it wrong. Linux is the kernel. GNU was the nearly-complete operating system it fit in. GNU+Linux is a complete operating system.

*AND* you cut out the bit where I said "I have no problems with it"

Referring to Linux as GNU/Linux would be wrong, because Linux is the kernel, and that's unrelated with the GNU operating system. It's the combination of them that forms GNU+Linux. And it's referring to this combination as Linux that is wrong.

I'm sorry that I got the impression that you meant the combination when you wrote "refer to Linux" above. It looked like you meant the combination, since I've never seen anyone call the kernel GNU/Linux or GNU+Linux.

Quoted 2 lines

Never claimed otherwise. The problem is that using a composite name like that *does* confuse a hell of a lot of people.

Pronouncing the '+' or '/' helps a lot. GNU plus Linux makes a lot of sense, and so does GNU on Linux.

Quoted 7 lines
Quoted 6 lines
Quoted 2 lines

A "TiVO" is not, and has never been, a "General Purpose Computational Device".

Err... Last I looked it was a bunch of general-purpose components, packaged in a way that made it not look like a general-purpose computer. Who gets to decide? And with what motivations?

Quoted 5 lines

And so is every game console. But until the original XBox was released nobody tried using one as a "General Purpose" machine. The TiVO wasn't designed as a general purpose machine - it was designed for a specific purpose. That the *easiest* design to produce uses a bunch of general purpose components is an economic choice, nothing else.

So, if I put together a general-purpose computer, a general-purpose operating system, adding a label "not a general-purpose computer" is enough to make it so, just so that I can escape the obligations to respect users' freedoms?

Quoted 1 line

I will not, however, argue about this anymore.

Fair enough.

Quoted 7 lines

Let me quote Linus here:

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".

In other words, GPLv3 is breaking with its predecessor - it's adding a requirement that doesn't exist in previous versions.

No dispute about this. The requirements are being added to the legal terms, precisely such that they better reflect the spirit, under the light of the new threats that appeared since GPLv2 was published.

But the new requirements do abide by the same spirit, and that was a promise the FSF made WRT revisions of the GPL.

Quoted 2 lines

*AND* it's dictating terms for *HARDWARE* when it isn't a hardware license.

Only in as much as you try to use the hardware as means to disrespect the spirit of the license and escape from the obligation to respect users' freedoms.

Quoted 3 lines

If I release software under the GPL and somebody modifies it to run on a different hardware platform I'll be happy, even if they don't send me a patchset for the new version.

Yup. See the bit about GPL not being tit-for-tat.

Quoted 4 lines

If I create a piece of hardware and run Linux on it, but have it locked to a specific version or versions from a specific source (ie:
me) and release it to the public, I *WILL* release the version of Linux I'm running on it.

Good.

Quoted 5 lines

What I won't do is release whatever tools and such that are needed to make the hardware run a different version of the kernel. Why? Because: the hardware was designed so that a specific version of the kernel runs without problems, there is hardware that is very picky and running a customized kernel could cause that hardware to fail, etc...

Why do you care? It's no longer your hardware, it's theirs.

Why would you refrain from providing information to others such that they *could* make the software do what *they* want in their hardware that they got from you?

If you let them change it and they break it, they get to keep all the pieces. Your job is done. Why get out of your way to stop them from making the best out of *their* hardware?

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}
#143 lore raw
Quoted 14 lines · On Thursday 14 June 2007 03:11:45 Alexandre Oliva wrote:
Quoted 13 lines · Daniel Hazelton
Quoted 11 lines · On Thursday 14 June 2007 01:51:13 Alexandre Oliva wrote:
Quoted 6 lines · Daniel Hazelton
Quoted 2 lines · On Wednesday 13 June 2007 22:38:05 Alexandre Oliva wrote:

In 95% of the desktop computers, you can't make changes to the OS that runs on it. Whom is this good for?

Faulty logic. I have yet to find a computer that I couldn't change the OS on.

I was not talking about installing another OS, I was talking about making changes to the OS. As in, improving one particular driver, avoiding a blue screen, stuff like that.

Quoted 5 lines
Quoted 2 lines

Ah, well... In the case of "Windos" and other proprietary OS's I try to educate people and get them to switch.

Good. So I presume you'd tell them to switch away from a turned-proprietary GNU/Linux operating system as well, right?

If that happened I'd be lost. I've tried the various BSD's and found they had problems with hardware support and getting a new version of the BSD kernel to compile and boot is something of a black art.

The point is moot, though. It can never happen.

Quoted 9 lines

So, again, what do we gain if companies abuse the GPL and disrespect users' rights that we meant them to respect?

Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

Or do you mean "transferring the recorded copies off the TiVO and on to a different medium"?

Sure. Such that I can watch shows while wasting time in public transportation, in an airplane, whatever.

Quoted 8 lines
Quoted 2 lines

Under the US Copyright law I'm not sure that making a "second copy" like that is legal. IIRC, "Fair Use" only allows for one copy.

Even if you delete the "first copy"?

Actually, I thought fair use in US entitled you to make a backup copy. So the copy in your TiVO would be your original, and the external copy would be your fair-use backup.

Hrm... Perhaps.

Quoted 6 lines
Quoted 2 lines

As has been noted in their TOS and the licenses for the hardware from the start.

If it is used to disrespect the inalienable freedoms associated with the GPL software in the device, it seems like a license violation to me.

As much as the US "Declaration of Independence" and other sources want people to believe otherwise there is no such thing as "inalienable rights" or "inalienable freedoms". In this case I have been unable to find this "inalienable freedom" to run custom versions of software "on the same machine" that you received the original copy on anywhere before the GPLv3 - and even then it isn't explicitly clear. There is no restriction on your right to modify, copy, distribute or run the software as provided by versions of the GPL prior to version 3. If this "run modified copies on the same hardware you received the original on" *IS* the "spirit" of the license, then why isn't it stated anywhere before GPLv3? (After all, the FSF has have 20+ years to mention it)

Quoted 8 lines
Quoted 2 lines

The FSF itself explicitly reserves the right to change the GPL at any time - which is no different.

Actually, it's completely different.

If the FSF revises the GPL, the old version remains available for anyone to use for any new software, and all software released under the old version remains available under that old version.

I'll grant you that. But, at this point, where can I find a copy of the GPLv1 without having to dig around the net ?

Quoted 4 lines

In contrast, your TiVO may get a software upgrade without your permission that will take your rights away from that point on, and there's very little you can do about it, other than unplugging it from the network to avoid the upgrade if it's not too late already.

And because its a device that connects to their network - and TiVO isn't a telecommunications company - they have the right to upgrade and configure the software inside however they want. (In the US at least)

Quoted 5 lines
Quoted 3 lines

A lot of them would probably have private modifications that would never be distributed - and under the GPLv2 it is clear that you can keep modifications private as long as you don't distribute them.

Likewise with GPLv3.

I can see this, but will a company see this?

Quoted 7 lines
Quoted 4 lines

"Pushing them away" means that they'd not do that because they would be concerned that the license will change under them in such a way that even those private modifications need to be released to the public.

This would not only change the spirit of the license, but turn it into a non-Free Software license.

Point. But once again - would a company pay attention to that fact?

Quoted 5 lines

And then, again, the license can't possibly be changed from under them. A new revision of the GPL would only affect software licensed under that new revision. If you already got it under an earlier revision, you know what you got, and nobody can take that away from you.

True. But that doesn't save them from lawsuits trying to force them to obey the terms of the new revision even though they received the software under an earlier version.

Quoted 8 lines
Quoted 4 lines

(and don't try to argue that even though those modifications are truly private (to the company) they should be released anyway to comply with the "spirit" of the license. It is made clear that it isn't by the text of the license itself)

How could you possibly come to the conclusion that forcing anyone to release private modifications would be in compliance with the spirit of the license? can != must

I was trying to be sarcastic and inject a little humor here. Guess I should have used the old <sarcasm> tag :)

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

Quoted 8 lines
Quoted 2 lines

But he has. Whether you have accepted that his explanations are valid or not doesn't change the fact.

His explanation is based on a reading of the license that doesn't match what its authors meant. I guess the authors know better what they meant the spirit of the license to be than someone else who studied it a lot but that until very recently couldn't even tell the spirit from the legal terms.

And his interpretation is no less valid than that of anyone else. In fact, after a recent conversation with a couple of lawyers that I know, I can state that his interpretation isn't that far off from theirs.

Quoted 14 lines
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Just like people have started using "GNU/Linux" or "GNU+Linux" to refer to Linux

No, no, you got it wrong. Linux is the kernel. GNU was the nearly-complete operating system it fit in. GNU+Linux is a complete operating system.

*AND* you cut out the bit where I said "I have no problems with it"

Referring to Linux as GNU/Linux would be wrong, because Linux is the kernel, and that's unrelated with the GNU operating system. It's the combination of them that forms GNU+Linux. And it's referring to this combination as Linux that is wrong.

Quoted 4 lines

I'm sorry that I got the impression that you meant the combination when you wrote "refer to Linux" above. It looked like you meant the combination, since I've never seen anyone call the kernel GNU/Linux or GNU+Linux.

Then you're lucky. I've had a lot of people say something similar to the
following: "Oh, I've heard about that. So which version of the GNU-Linux kernel are you running?"

Quoted 5 lines
Quoted 2 lines

Never claimed otherwise. The problem is that using a composite name like that *does* confuse a hell of a lot of people.

Pronouncing the '+' or '/' helps a lot. GNU plus Linux makes a lot of sense, and so does GNU on Linux.

Yes, it does. While pronouncing the '/' or '+' sounds a bit odd it does get the point across that it's the GNU userspace running on top of the Linux kernel. (as does "GNU on Linux")

Quoted 30 lines
Quoted 7 lines
Quoted 6 lines
Quoted 2 lines

A "TiVO" is not, and has never been, a "General Purpose Computational Device".

Err... Last I looked it was a bunch of general-purpose components, packaged in a way that made it not look like a general-purpose computer. Who gets to decide? And with what motivations?

Quoted 5 lines

And so is every game console. But until the original XBox was released nobody tried using one as a "General Purpose" machine. The TiVO wasn't designed as a general purpose machine - it was designed for a specific purpose. That the *easiest* design to produce uses a bunch of general purpose components is an economic choice, nothing else.

So, if I put together a general-purpose computer, a general-purpose operating system, adding a label "not a general-purpose computer" is enough to make it so, just so that I can escape the obligations to respect users' freedoms?

Quoted 1 line

I will not, however, argue about this anymore.

Fair enough.

Quoted 7 lines

Let me quote Linus here:

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".

In other words, GPLv3 is breaking with its predecessor - it's adding a requirement that doesn't exist in previous versions.

Quoted 6 lines

No dispute about this. The requirements are being added to the legal terms, precisely such that they better reflect the spirit, under the light of the new threats that appeared since GPLv2 was published.

But the new requirements do abide by the same spirit, and that was a promise the FSF made WRT revisions of the GPL.

As I've stated before - I can find nothing in the history of the GPL or the FSF that makes the "on the same hardware" requirement clear and part of the "spirit" of "Free Software". The closest anything comes is the "printer driver" that was the (in)famous "last straw" for RMS and caused him to create the FSF and the GNU Project.

Quoted 6 lines
Quoted 2 lines

*AND* it's dictating terms for *HARDWARE* when it isn't a hardware license.

Only in as much as you try to use the hardware as means to disrespect the spirit of the license and escape from the obligation to respect users' freedoms.

Shouldn't matter. As I've repeated quite a bit I cannot find a single mention that "on the same hardware" has been a goal of the FSF or part of the "spirit" of the GPL at any point before the drafting of GPLv3.

Quoted 13 lines
Quoted 3 lines

If I release software under the GPL and somebody modifies it to run on a different hardware platform I'll be happy, even if they don't send me a patchset for the new version.

Yup. See the bit about GPL not being tit-for-tat.

Quoted 4 lines

If I create a piece of hardware and run Linux on it, but have it locked to a specific version or versions from a specific source (ie:
me) and release it to the public, I *WILL* release the version of Linux I'm running on it.

Good.

Quoted 7 lines
Quoted 5 lines

What I won't do is release whatever tools and such that are needed to make the hardware run a different version of the kernel. Why? Because:
the hardware was designed so that a specific version of the kernel runs without problems, there is hardware that is very picky and running a customized kernel could cause that hardware to fail, etc...

Why do you care? It's no longer your hardware, it's theirs.

Legal requirements in some countries that require manufacturers to provide support for their product for a period of time after it has been purchased.

Quoted 3 lines

Why would you refrain from providing information to others such that they *could* make the software do what *they* want in their hardware that they got from you?

See above.

Quoted 3 lines

If you let them change it and they break it, they get to keep all the pieces. Your job is done. Why get out of your way to stop them from making the best out of *their* hardware?

*thinks* Okay - looks like I had a thinko there. Arguments on this subject (ie: the theoretical hardware) are withdrawn and the point is conceded.

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#144 lore raw
Quoted 5 lines · Daniel Hazelton
Quoted 3 lines · On Thursday 14 June 2007 03:11:45 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton

Ah, well... In the case of "Windos" and other proprietary OS's I try to educate people and get them to switch.

Quoted 8 lines
Quoted 2 lines

Good. So I presume you'd tell them to switch away from a turned-proprietary GNU/Linux operating system as well, right?

If that happened I'd be lost. I've tried the various BSD's and found they had problems with hardware support and getting a new version of the BSD kernel to compile and boot is something of a black art.

The point is moot, though. It can never happen.

Look again, it's already happened in the TiVO and other devices.

The software that ships in them is no longer Free Software.

Consider a new microprocessor.

Consider that Linux is ported to it by the microprocessor manufacturer.

Consider that the manufacturer only sells devices with that microprocessor with TiVO-like locks.

How exactly can you enjoy the freedoms WRT the GPLed software you got from the manufacturer?

Now consider that you have a single computer, and that's built by TiVO.

How exactly can you enjoy the freedoms the author meant you to have, if the TiVO box won't run the program after you modify it?

Quoted 3 lines

If this "run modified copies on the same hardware you received the original on" *IS* the "spirit" of the license, then why isn't it stated anywhere before GPLv3?

For the same reasons that the pro-DRM laws weren't mentioned before, and the patent retaliation clauses weren't mention before: these specific cases hadn't been studied, only the general idea of respecting users' freedoms was.

Quoted 2 lines

I'll grant you that. But, at this point, where can I find a copy of the GPLv1 without having to dig around the net ?

In the program you received under GPLv1.

Hey, you said there was code under GPLv1.1 in the Linux tree. Then, there should be a copy of GPLv1.1 in there, otherwise AFAICT the distribution of that code is copyright infringement. IANAL.

Quoted 9 lines
Quoted 4 lines

In contrast, your TiVO may get a software upgrade without your permission that will take your rights away from that point on, and there's very little you can do about it, other than unplugging it from the network to avoid the upgrade if it's not too late already.

And because its a device that connects to their network - and TiVO isn't a telecommunications company - they have the right to upgrade and configure the software inside however they want. (In the US at least)

But do they have the right to not pass this right on, under the GPL?

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

A lot of them would probably have private modifications that would never be distributed - and under the GPLv2 it is clear that you can keep modifications private as long as you don't distribute them.

Likewise with GPLv3.

I can see this, but will a company see this?

In what sense does the GPLv3 make this particular point any less obscure?

Quoted 3 lines

True. But that doesn't save them from lawsuits trying to force them to obey the terms of the new revision even though they received the software under an earlier version.

Nothing saves anyone from silly lawsuits. This one would likely be laughed out of court in no time. Anyone worried about this should also be concerned about their neighbor suing them for copyright infringment every time they set their stereo loud enough for the neighbors to listen and be annoyed. (Hint: only the copyright holder would stand a chance of winning such a lawsuit)

Quoted 11 lines
Quoted 8 lines
Quoted 4 lines

(and don't try to argue that even though those modifications are truly private (to the company) they should be released anyway to comply with the "spirit" of the license. It is made clear that it isn't by the text of the license itself)

How could you possibly come to the conclusion that forcing anyone to release private modifications would be in compliance with the spirit of the license? can != must

I was trying to be sarcastic and inject a little humor here. Guess I should have used the old <sarcasm> tag :)

Aah. I'm not sure I'd have understood it either.

Quoted 15 lines
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

Quoted 8 lines
Quoted 2 lines

But he has. Whether you have accepted that his explanations are valid or not doesn't change the fact.

His explanation is based on a reading of the license that doesn't match what its authors meant. I guess the authors know better what they meant the spirit of the license to be than someone else who studied it a lot but that until very recently couldn't even tell the spirit from the legal terms.

Quoted 4 lines

And his interpretation is no less valid than that of anyone else. In fact, after a recent conversation with a couple of lawyers that I know, I can state that his interpretation isn't that far off from theirs.

Interpretation as applied to the legal terms, yes. As for the spirit of the license, the authors ought to know better than anyone else what they meant. Sure, other interpretations might lead to different understandings as to what the readers *think* it means, but that doesn't change what it was *intended* to mean.

Quoted 3 lines

Then you're lucky. I've had a lot of people say something similar to the
following: "Oh, I've heard about that. So which version of the GNU-Linux kernel are you running?"

Oh my. That's indeed unfortunate and unfair.

Quoted 3 lines

As I've stated before - I can find nothing in the history of the GPL or the FSF that makes the "on the same hardware" requirement clear and part of the "spirit" of "Free Software".

Put the considerations above, about a single computer or a uniformly-limited computing platform, and you'll see that this "on the same hardware" argument is just a means to deny people freedom. If I could stop you from running modified versions on one piece of hardware, then I could on two, and 3, and then soon it's all of them, and we're back to square zero in terms of freedom.

Quoted 10 lines
Quoted 7 lines
Quoted 5 lines

What I won't do is release whatever tools and such that are needed to make the hardware run a different version of the kernel. Why? Because:
the hardware was designed so that a specific version of the kernel runs without problems, there is hardware that is very picky and running a customized kernel could cause that hardware to fail, etc...

Why do you care? It's no longer your hardware, it's theirs.

Legal requirements in some countries that require manufacturers to provide support for their product for a period of time after it has been purchased.

If you replace a component in the hardware, are you still required to provide support or offer warranty? Why should this be different just because it's a software component?

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}
#145 lore raw
Quoted 5 lines · Alexandre Oliva

In the program you received under GPLv1.

Hey, you said there was code under GPLv1.1 in the Linux tree. Then, there should be a copy of GPLv1.1 in there, otherwise AFAICT the distribution of that code is copyright infringement. IANAL.

So now the copy of the GPL v2 isn't good enough for the GPLv1.1 code? Maybe that code said 'or later' in the license and hence someone added it to a GPL v2 project since that sounds perfectly OK.

--
Len Sorensen

#146 lore raw
Quoted 4 lines · Lennart Sorensen

So now the copy of the GPL v2 isn't good enough for the GPLv1.1 code? Maybe that code said 'or later' in the license and hence someone added it to a GPL v2 project since that sounds perfectly OK.

Where did that GPLv1.1 nonsense come from?

There is no GPLv1.1 code in the tree. By the time I selected the GPL for the kernel license, the GPLv1.1 had long since been discontinued. The kernel was *never* GPLv1.1-only compatible. That's just total nonsense.

There was indeed a kernel license before the GPLv2, but it wasn't the GPL at all, it was my own made-up thing. Appended here, for those who are too lazy to actually look up and check the original Linux-0.01 announcement.

Linus

---
This kernel is (C) 1991 Linus Torvalds, but all or part of it may be redistributed provided you do the following:

- Full source must be available (and free), if not with the distribution then at least on asking for it.

- Copyright notices must be intact. (In fact, if you distribute only parts of it you may have to add copyrights, as there aren't (C)'s in all files.) Small partial excerpts may be copied without bothering with copyrights.

- You may not distibute this for a fee, not even "handling" costs.

#147 lore raw
Quoted 7 lines · On Thursday 14 June 2007 14:53:47 Linus Torvalds wrote:
Quoted 3 lines · Lennart Sorensen

So now the copy of the GPL v2 isn't good enough for the GPLv1.1 code? Maybe that code said 'or later' in the license and hence someone added it to a GPL v2 project since that sounds perfectly OK.

Where did that GPLv1.1 nonsense come from?

Quoted 8 lines

There is no GPLv1.1 code in the tree. By the time I selected the GPL for the kernel license, the GPLv1.1 had long since been discontinued. The kernel was *never* GPLv1.1-only compatible. That's just total nonsense.

There was indeed a kernel license before the GPLv2, but it wasn't the GPL at all, it was my own made-up thing. Appended here, for those who are too lazy to actually look up and check the original Linux-0.01 announcement.

A hundred or so messages back someone stated that the parport driver in Linux is GPLv1.1 - however, on checking on this statement for myself I've found that there is no statement about it being v1.1 and, in fact, given that Linux itself is GPLv2 there is no possible way any code covered by GPLv1.1 can exist.

DRH

Quoted 16 lines

Linus

---
This kernel is (C) 1991 Linus Torvalds, but all or part of it may be redistributed provided you do the following:

- Full source must be available (and free), if not with the distribution then at least on asking for it.

- Copyright notices must be intact. (In fact, if you distribute only parts of it you may have to add copyrights, as there aren't (C)'s in all files.) Small partial excerpts may be copied without bothering with copyrights.

- You may not distibute this for a fee, not even "handling" costs.

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#148 lore raw
Quoted 5 lines

A hundred or so messages back someone stated that the parport driver in Linux is GPLv1.1 - however, on checking on this statement for myself I've found that there is no statement about it being v1.1 and, in fact, given that Linux itself is GPLv2 there is no possible way any code covered by GPLv1.1 can exist.

Wrong again.

If a piece of code was merged into the kernel with a GPL v1 "or later" license then it still has a GPL v1 "or later" license. The "or later" makes it compatible with the v2 code but does not change the fundamental copyright on the original work that was combined. Thus if you could identify specifically a GPL v1 work within the kernel you could use that GPL v1 work as per GPL v1 providing you didn't mix it with v2 code.

If I take a public domain book and create a derivative work from it the original work does not magically become restricted.

Alan

#149 lore raw
In reply to Daniel Hazelton
Quoted 2 lines · Daniel Hazelton

A hundred or so messages back someone stated that the parport driver in Linux is GPLv1.1

Probably a misinterpretation - there are comments in the parport driver mentioning the GFDL version 1.1. If you just grep through, you might think it's GPL version 1.1 (but the code is really v2 or later).

Signature · 3 lines
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
#150 lore raw
In reply to Lennart Sorensen
Quoted 8 lines · On Jun 14, 2007, [email protected] (Lennart Sorensen) wrote:
Quoted 5 lines · Alexandre Oliva

In the program you received under GPLv1.

Hey, you said there was code under GPLv1.1 in the Linux tree. Then, there should be a copy of GPLv1.1 in there, otherwise AFAICT the distribution of that code is copyright infringement. IANAL.

So now the copy of the GPL v2 isn't good enough for the GPLv1.1 code?

If it exists and it's 1.1-only, I believe it wouldn't, but IANAL.

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}
#151 lore raw
In reply to Alexandre Oliva
Quoted 13 lines · On Thursday 14 June 2007 13:26:30 Alexandre Oliva wrote:
Quoted 12 lines · Daniel Hazelton
Quoted 6 lines · On Thursday 14 June 2007 03:11:45 Alexandre Oliva wrote:
Quoted 2 lines · Daniel Hazelton

Ah, well... In the case of "Windos" and other proprietary OS's I try to educate people and get them to switch.

Good. So I presume you'd tell them to switch away from a turned-proprietary GNU/Linux operating system as well, right?

If that happened I'd be lost. I've tried the various BSD's and found they had problems with hardware support and getting a new version of the BSD kernel to compile and boot is something of a black art.

Quoted 6 lines
Quoted 1 line

The point is moot, though. It can never happen.

Look again, it's already happened in the TiVO and other devices.

The software that ships in them is no longer Free Software.

In *YOUR* opinion and by *YOUR* definition of the term. Yes, I have seen some evidence that TiVO hasn't made some of the modifications they made public - doesn't mean that they won't, just it hasn't *YET* been done. (Not that I'm so omniscient I can say, definitively, whether they will or won't - or even that they haven't done it already).

By my own definition replacement != modification.

Quoted 11 lines

Consider a new microprocessor.

Consider that Linux is ported to it by the microprocessor manufacturer.

Consider that the manufacturer only sells devices with that microprocessor with TiVO-like locks.

How exactly can you enjoy the freedoms WRT the GPLed software you got from the manufacturer?

The same as I would with a TiVO. I have the right to copy, modify, distribute and run the code - even if I can't do any of those things on the hardware the original binary operates on.

Quoted 6 lines

Now consider that you have a single computer, and that's built by TiVO.

How exactly can you enjoy the freedoms the author meant you to have, if the TiVO box won't run the program after you modify it?

Simple: I don't buy it. Each and every piece of hardware I buy has a rather laborious research process before I actually spend the money on it. This makes it a certainty that I can use the hardware in the manner I want without problems like your hypothetical.

Whats worse - forcing your morals and ideals on someone or giving them the same freedom of choice you had?

Before you answer remember that that is *EXACTLY* what is being done with GPLv3. With GPLv2 and prior there was a simple guarantee that every "Licensee" had exactly the same rights. With GPLv3 you are forcing your ethics and morals on people - and isn't this exactly what the Roman Catholic church did during the Spanish Inquisition?

Quoted 8 lines
Quoted 3 lines

If this "run modified copies on the same hardware you received the original on" *IS* the "spirit" of the license, then why isn't it stated anywhere before GPLv3?

For the same reasons that the pro-DRM laws weren't mentioned before, and the patent retaliation clauses weren't mention before: these specific cases hadn't been studied, only the general idea of respecting users' freedoms was.

Bzzt! Wrong! The reason is that it wasn't necessary - at all. It still isn't, but a group that feels modification == replacement wants it to be, so it has suddenly become necessary. (Note that anti-DRM stuff *IS* good - DRM is part of an attempt by failing business models to stop the failure)

Quoted 8 lines
Quoted 2 lines

I'll grant you that. But, at this point, where can I find a copy of the GPLv1 without having to dig around the net ?

In the program you received under GPLv1.

Hey, you said there was code under GPLv1.1 in the Linux tree. Then, there should be a copy of GPLv1.1 in there, otherwise AFAICT the distribution of that code is copyright infringement. IANAL.

Ah, but I never said I had a GPLv1 program. If GPLv1 is still valid and available I should be able to find a copy of it *RIGHT* *NOW* to license a new project if I want to use GPLv1 as its license. So your logic is again flawed.

Quoted 11 lines
Quoted 9 lines
Quoted 4 lines

In contrast, your TiVO may get a software upgrade without your permission that will take your rights away from that point on, and there's very little you can do about it, other than unplugging it from the network to avoid the upgrade if it's not too late already.

And because its a device that connects to their network - and TiVO isn't a telecommunications company - they have the right to upgrade and configure the software inside however they want. (In the US at least)

But do they have the right to not pass this right on, under the GPL?

Yes, they do. It isn't a right they have as "copyright holders" - in fact, it isn't a part of their rights under the copyright at all. It's a part of their rights as the owners of the network.

Quoted 10 lines
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

A lot of them would probably have private modifications that would never be distributed - and under the GPLv2 it is clear that you can keep modifications private as long as you don't distribute them.

Likewise with GPLv3.

I can see this, but will a company see this?

In what sense does the GPLv3 make this particular point any less obscure?

Never claimed it was less obscure, just that you've usually got a board-room filled with middle-aged men that might have problems agreeing that it is a clear-cut case.

Quoted 10 lines
Quoted 3 lines

True. But that doesn't save them from lawsuits trying to force them to obey the terms of the new revision even though they received the software under an earlier version.

Nothing saves anyone from silly lawsuits. This one would likely be laughed out of court in no time. Anyone worried about this should also be concerned about their neighbor suing them for copyright infringment every time they set their stereo loud enough for the neighbors to listen and be annoyed. (Hint: only the copyright holder would stand a chance of winning such a lawsuit)

Yes, but the fact that it would cost money to get the suit dropped is a problem.

Quoted 34 lines
Quoted 11 lines
Quoted 8 lines
Quoted 4 lines

(and don't try to argue that even though those modifications are truly private (to the company) they should be released anyway to comply with the "spirit" of the license. It is made clear that it isn't by the text of the license itself)

How could you possibly come to the conclusion that forcing anyone to release private modifications would be in compliance with the spirit of the license? can != must

I was trying to be sarcastic and inject a little humor here. Guess I should have used the old <sarcasm> tag :)

Aah. I'm not sure I'd have understood it either.

Quoted 15 lines
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

Why should I repeat Linus' explanation of the ways that GPLv3 violates the spirit of GPLv2?

Don't worry about parrotting here, he hasn't provided that explanation yet ;-) Please give it a try.

Quoted 8 lines
Quoted 2 lines

But he has. Whether you have accepted that his explanations are valid or not doesn't change the fact.

His explanation is based on a reading of the license that doesn't match what its authors meant. I guess the authors know better what they meant the spirit of the license to be than someone else who studied it a lot but that until very recently couldn't even tell the spirit from the legal terms.

Quoted 4 lines

And his interpretation is no less valid than that of anyone else. In fact, after a recent conversation with a couple of lawyers that I know, I can state that his interpretation isn't that far off from theirs.

Quoted 5 lines

Interpretation as applied to the legal terms, yes. As for the spirit of the license, the authors ought to know better than anyone else what they meant. Sure, other interpretations might lead to different understandings as to what the readers *think* it means, but that doesn't change what it was *intended* to mean.

Doesn't matter what the author intended it to mean - at all. What matters is how its interpreted when/if it shows up in court. This can be seen *ALL* the time with laws across the globe. In the US there is this thing called the "RICO" Laws- "Racketeering Influenced Criminal Organization" - that give the government the ability to seize anything that is deemed a "profit of drug sales" or of a "Criminal Organization". It has been used for that purpose, but its interpretation has caused it to be used to seize money that has had no source in either.

Quoted 25 lines
Quoted 3 lines

Then you're lucky. I've had a lot of people say something similar to the
following: "Oh, I've heard about that. So which version of the GNU-Linux kernel are you running?"

Oh my. That's indeed unfortunate and unfair.

Quoted 3 lines

As I've stated before - I can find nothing in the history of the GPL or the FSF that makes the "on the same hardware" requirement clear and part of the "spirit" of "Free Software".

Put the considerations above, about a single computer or a uniformly-limited computing platform, and you'll see that this "on the same hardware" argument is just a means to deny people freedom. If I could stop you from running modified versions on one piece of hardware, then I could on two, and 3, and then soon it's all of them, and we're back to square zero in terms of freedom.

Quoted 8 lines
Quoted 7 lines
Quoted 5 lines

What I won't do is release whatever tools and such that are needed to make the hardware run a different version of the kernel. Why? Because:
the hardware was designed so that a specific version of the kernel runs without problems, there is hardware that is very picky and running a customized kernel could cause that hardware to fail, etc...

Why do you care? It's no longer your hardware, it's theirs.

Quoted 7 lines
Quoted 3 lines

Legal requirements in some countries that require manufacturers to provide support for their product for a period of time after it has been purchased.

If you replace a component in the hardware, are you still required to provide support or offer warranty? Why should this be different just because it's a software component?

Artificial distinctions in the law

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#152 lore raw
Quoted 4 lines · Daniel Hazelton

With GPLv2 and prior there was a simple guarantee that every "Licensee" had exactly the same rights. With GPLv3 you are forcing your ethics and morals on people - and isn't this exactly what the Roman Catholic church did during the Spanish Inquisition?

I fail to see the distinction you're making between GPLv2 and GPLv3. AFAICT, with GPLv3, there still is a simple guarantee that every licensee has exactly the same rights.

Sure, GPLv3 follows the spirit of the GPLs more strictly than GPLv2 possibly could. How is that "forcing ethics and morals" any more than GPLv2 was?

Quoted 1 line

Ah, but I never said I had a GPLv1 program.

I thought you had a copy of Linux and, per what you'd said before, there was GPLv1 code in it. I was just trying to make it easy for you.

Quoted 3 lines

If GPLv1 is still valid and available I should be able to find a copy of it *RIGHT* *NOW* to license a new project if I want to use GPLv1 as its license.

http://www.gnu.org/copyleft/copying-1.0.html

Quoted 10 lines
Quoted 6 lines
Quoted 4 lines

And because its a device that connects to their network - and TiVO isn't a telecommunications company - they have the right to upgrade and configure the software inside however they want. (In the US at least)

But do they have the right to not pass this right on, under the GPL?

Yes, they do. It isn't a right they have as "copyright holders" - in fact, it isn't a part of their rights under the copyright at all. It's a part of their rights as the owners of the network.

How about the "no further restrictions" bit?

Quoted 6 lines

Never claimed it was less obscure, just that you've usually got a board-room filled with middle-aged men that might have problems agreeing that it is a clear-cut case.

Yes, but the fact that it would cost money to get the suit dropped is a problem.

Again, how are these arguments against GPLv3? They apply equally to any other license, including GPLv2.

Quoted 8 lines
Quoted 5 lines

Interpretation as applied to the legal terms, yes. As for the spirit of the license, the authors ought to know better than anyone else what they meant. Sure, other interpretations might lead to different understandings as to what the readers *think* it means, but that doesn't change what it was *intended* to mean.

Doesn't matter what the author intended it to mean - at all. What matters is how its interpreted when/if it shows up in court.

You're talking about the legal terms. The spirit of the license is a very different matter. It can guide the interpretation of the legal terms, but the author is at a better position than anyone else to know what he meant.

Quoted 5 lines
Quoted 3 lines

If you replace a component in the hardware, are you still required to provide support or offer warranty? Why should this be different just because it's a software component?

Artificial distinctions in the law

Well, then, lock down the software. Make it irreplaceable, even by yourself. Problem solved.

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}
#153 lore raw
Quoted 6 lines · On Thursday 14 June 2007 17:19:51 Alexandre Oliva wrote:
Quoted 4 lines · Daniel Hazelton

With GPLv2 and prior there was a simple guarantee that every "Licensee" had exactly the same rights. With GPLv3 you are forcing your ethics and morals on people - and isn't this exactly what the Roman Catholic church did during the Spanish Inquisition?

Quoted 7 lines

I fail to see the distinction you're making between GPLv2 and GPLv3. AFAICT, with GPLv3, there still is a simple guarantee that every licensee has exactly the same rights.

Sure, GPLv3 follows the spirit of the GPLs more strictly than GPLv2 possibly could. How is that "forcing ethics and morals" any more than GPLv2 was?

Because GPLv2 doesn't enforce limitations on the hardware a GPL'd work can be put on. It doesn't make artificial distinctions between "Commercial", "Industrial" and "User". What it does is *ATTEMPT* to ensure that nobody receiving a copy of a GPL'd work has the same rights as any other person that gets a copy. GPLv3 gives people *additional* rights beyond those. In the "TiVO" case it forces somebody releasing a HW platform to grant *additional* rights if they are going to use software covered by the GPLv3. The reason for forcing the giving of those additional rights is "the FSF and GPLv3 committees think that what TiVO did is 'morally and ethically' wrong, so were are enforcing our morals and ethics".

Note that these are the rights that TiVO got from the GPLv2:
1) The ability to make copies of Linux
2) The ability to modify Linux
3) The ability to distribute Linux
*NOTE* that those are the rights *GUARANTEED* by the GPL - despite what anyone *WISHES* it to say, or what the "Intent" or "Spirit" of the license may be, those are the only guaranteed rights.

In shipping their devices with an "object code" version of Linux on them they exercised their right to perform such a distribution, granted under section 3 of the GPLv2. They made modifications to the Linux so it functioned properly on their devices, as allowed by the GPL. They have made numerous copies of Linux, as allowed by the GPL. And, as required by the GPLv2, they made the source code form of their changes available. In fact, they went beyond the requirements of the GPL (which only requires you make the source available to people you have given an "object code" version to) in making it fully available to the public *AND* in contributing those changes back to Linux.

What rights did they give to "downstream" recipients of the "object code" version? *EXACTLY* those they received from the GPLv2.

What rights do they have as creators of a *PROPRIETARY* hardware platform:
1) The right to restrict what programs it will run
2) The right to update it as they choose, even if it makes it incompatible with earlier versions

Does the GPL *require* them to give up those rights? Version 3 does, but not any earlier version. Why does version 3 do this? Because one or more of the people behind its design and language feel that executing a piece of software on any given hardware platform automatically entitles them to all rights to the hardware that the creator of the hardware has.

Quoted 11 lines
Quoted 1 line

Ah, but I never said I had a GPLv1 program.

I thought you had a copy of Linux and, per what you'd said before, there was GPLv1 code in it. I was just trying to make it easy for you.

Quoted 3 lines

If GPLv1 is still valid and available I should be able to find a copy of it *RIGHT* *NOW* to license a new project if I want to use GPLv1 as its license.

http://www.gnu.org/copyleft/copying-1.0.html

Ah, see, I didn't even know it was still there. I hadn't seen it in a complete form anywhere.

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines

And because its a device that connects to their network - and TiVO isn't a telecommunications company - they have the right to upgrade and configure the software inside however they want. (In the US at least)

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

But do they have the right to not pass this right on, under the GPL?

Yes, they do. It isn't a right they have as "copyright holders" - in fact, it isn't a part of their rights under the copyright at all. It's a part of their rights as the owners of the network.

How about the "no further restrictions" bit?

As applies to the software. The rights that the GPL has (historically) granted are what I stated above. TiVO, and companies like them, are *NOT* imposing any restrictions on rights granted under GPLv2 and prior. Remember, because I'm getting tired of repeating myself: replace != modify

Quoted 9 lines
Quoted 6 lines

Never claimed it was less obscure, just that you've usually got a board-room filled with middle-aged men that might have problems agreeing that it is a clear-cut case.

Yes, but the fact that it would cost money to get the suit dropped is a problem.

Again, how are these arguments against GPLv3? They apply equally to any other license, including GPLv2.

Granted. But GPLv2 has been examined and re-examined by lawyer and lay-person alike for more than 10 years. If you recall, however, my original statement was about the "revise or change the license at any time" clause. If that is possible, then it is also possible for the mentioned "frivolous lawsuit" by someone applying the "revised" license to something licensed with the non-revised version.

Your argument is flawed, however. Most companies have done the work for defense with the "other licenses". And if it isn't possible for a "Licensor" to say "My work is released under version X of this license only" (with the GPL) - as you seem to have argued at several points - then it wouldn't matter if they've done the legwork to protect them from all but the most frivolous of lawsuits. All that needs to happen is for someone to release the same work under a later license (with modifications) and the company is now open to a new, unplanned for class of "frivolous lawsuits".

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines

Interpretation as applied to the legal terms, yes. As for the spirit of the license, the authors ought to know better than anyone else what they meant. Sure, other interpretations might lead to different understandings as to what the readers *think* it means, but that doesn't change what it was *intended* to mean.

Quoted 7 lines
Quoted 2 lines

Doesn't matter what the author intended it to mean - at all. What matters is how its interpreted when/if it shows up in court.

You're talking about the legal terms. The spirit of the license is a very different matter. It can guide the interpretation of the legal terms, but the author is at a better position than anyone else to know what he meant.

I do agree that the intent can guide interpretation, but in the US it is very rare. Consider the "Second Amendment", which states "The formation of militias being necessary for the defense of the state, the right of the people to keep and bear arms shall not be abridged." The *INTENT* is explained by the authors in several places, but the interpretation is still argued about. The meaning is *VERY* clear to me - and makes all "Gun Control" laws and such in direct violation of the US Constitution. But that doesn't matter, because nobody pays attention to the intent.

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

If you replace a component in the hardware, are you still required to provide support or offer warranty? Why should this be different just because it's a software component?

Artificial distinctions in the law

Well, then, lock down the software. Make it irreplaceable, even by yourself. Problem solved.

Yes, problem solved. But at the cost of taking hardware back 20 years.

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#154 lore raw
Quoted 2 lines · Daniel Hazelton

What rights did they give to "downstream" recipients of the "object code" version? *EXACTLY* those they received from the GPLv2.

Doing the e-mail equivalent of yelling about this will not change the fact that people who think Tivo did something wrong -- legally and/or morally -- consider DRM locks on a piece of software to be part of the "work based on the Program" that is governed by the GPL.

The fundamental reason for this is that neither the executable code nor the digital signature serves the desired function alone. The user received a copy of the executable for a particular purpose: to run the program on a particular platform. With DRM signatures, only the combination of program and signature will perform that function, and separating the two based on strictly read legal definitions is risky.

The question of whether DRM signatures are covered by the license must be resolved before one can determine whether Tivo gave "*EXACTLY*" the same rights to object-code recipients as Tivo received. GPLv2 is worded such that the answer to this does not depend on whether one is in file A and the other in file B, or whether one is on hard drive C and the other is in flash device D, as long as they are delivered as part of one unit; it *might* matter if, say, one is received on physical media and the other is downloaded on demand.

(Linus likes to say that FSF counsel thinks that Tivo did not violate GPLv2. I suspect the actual situation is that FSF counsel believes that there is no case law on point, and that it could go either way, making it improper to publicly claim that Tivo violated any copyright. Until a court rules on a close-enough case, the question of whether GPLv2 covers DRM signatures remains open. In the mean time, it makes more sense for the FSF to issue a new license that squarely addresses this -- such as the GPLv3 -- and persuade as many developers as possible that using it is the best way to protect free software.)

Michael Poole

#155 lore raw
Quoted 5 lines · On Thursday 14 June 2007 22:13:13 Michael Poole wrote:
Quoted 2 lines · Daniel Hazelton

What rights did they give to "downstream" recipients of the "object code" version? *EXACTLY* those they received from the GPLv2.

Doing the e-mail equivalent of yelling about this will not change the

Sorry, I wasn't trying to "yell" - just provide a note that at that point I would be providing verbal stress.

Quoted 3 lines

fact that people who think Tivo did something wrong -- legally and/or morally -- consider DRM locks on a piece of software to be part of the "work based on the Program" that is governed by the GPL.

All I've done is get a little annoyed that, despite evidence that it isn't legally wrong - at least under the laws I am most familiar with - people continue repeat that it is.

I can't argue that it isn't "morally" wrong. While it may not be against my morals, it could be against those of another person. It has never been my intent to try and convince people that their morals are wrong.

Quoted 6 lines

The fundamental reason for this is that neither the executable code nor the digital signature serves the desired function alone. The user received a copy of the executable for a particular purpose: to run the program on a particular platform. With DRM signatures, only the combination of program and signature will perform that function, and separating the two based on strictly read legal definitions is risky.

I agree.

Quoted 8 lines

The question of whether DRM signatures are covered by the license must be resolved before one can determine whether Tivo gave "*EXACTLY*" the same rights to object-code recipients as Tivo received. GPLv2 is worded such that the answer to this does not depend on whether one is in file A and the other in file B, or whether one is on hard drive C and the other is in flash device D, as long as they are delivered as part of one unit; it *might* matter if, say, one is received on physical media and the other is downloaded on demand.

I have read the GPLv2 at least three times since it was pointed out that I had forgotten part of it. At no point can I find a point where Tivo broke the GPLv2 requirement that they give the recipients of the object code the same rights they received when they acquired a copy of the object or source code.

Quoted 9 lines

(Linus likes to say that FSF counsel thinks that Tivo did not violate GPLv2. I suspect the actual situation is that FSF counsel believes that there is no case law on point, and that it could go either way, making it improper to publicly claim that Tivo violated any copyright. Until a court rules on a close-enough case, the question of whether GPLv2 covers DRM signatures remains open. In the mean time, it makes more sense for the FSF to issue a new license that squarely addresses this -- such as the GPLv3 -- and persuade as many developers as possible that using it is the best way to protect free software.)

In examining the GPLv2 and the situation from a strictly factual basis I can believe Linus' statement fully. The facts are as I stated them in a previous mail.

DRH

Quoted 1 line

Michael Poole

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#156 lore raw
Quoted 20 lines · Daniel Hazelton
Quoted 6 lines · On Thursday 14 June 2007 22:13:13 Michael Poole wrote:

The fundamental reason for this is that neither the executable code nor the digital signature serves the desired function alone. The user received a copy of the executable for a particular purpose: to run the program on a particular platform. With DRM signatures, only the combination of program and signature will perform that function, and separating the two based on strictly read legal definitions is risky.

I agree.

Quoted 8 lines

The question of whether DRM signatures are covered by the license must be resolved before one can determine whether Tivo gave "*EXACTLY*" the same rights to object-code recipients as Tivo received. GPLv2 is worded such that the answer to this does not depend on whether one is in file A and the other in file B, or whether one is on hard drive C and the other is in flash device D, as long as they are delivered as part of one unit; it *might* matter if, say, one is received on physical media and the other is downloaded on demand.

Quoted 4 lines

I have read the GPLv2 at least three times since it was pointed out that I had forgotten part of it. At no point can I find a point where Tivo broke the GPLv2 requirement that they give the recipients of the object code the same rights they received when they acquired a copy of the object or source code.

I am trying to reconcile your responses to those two paragraphs.

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

If they are one work, and the original Program was licensed under the GPLv2, the combined work must also be licensed under the terms of the GPLv2.

The input files required to generate a DRM-valid digital signature are part the preferred form for modifying that work.

If those bits are not distributed along with the rest of the GPL'ed work, the distributor is either not giving the same rights to the end user, not distributing the source code for the work, or both. Which is it?

Michael Poole

#157 lore raw
Quoted 5 lines · Michael Poole

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

So you want to make things like a 160-bit SHA1 hash of a binary be a "derived work" of that software?

Trust me, you *really* don't want to go there. It's an insane legal standpoint, and if you were right, we'd be in a *world* of trouble.

Think about something as simple as security software that creates filesystem checksums for verifying the integrity of the filesystem, and protects against tampering.

Do you *really* want to claim that the SHA1 checksum of your "oracle" binary is owned by Oracle, and you need to have a special license to copy that checksum around and verify it?

Do you *really* want to claim that the RIAA owns the CDDB checksums (well, I guess "feedb", these days) of the CD's that get uploaded for music databases?

Do you realize that in your INSANE world, there is no notion of "fair use", and you just tried to extend the notion of copyright so far that you turned your utopia into a total distopia.

In other words, anybody who claims that copyright in a program extends to the cryptographic hash of the binary, and at the same time makes a "free software" kind of argument is so damn clueless that it's not even funny. You're arguing for "freedom" by using logic that is the very *antithesis* of freedom.

That's just incredibly stupid and incredibly short-sighted.

If that were to seriously be an FSF argument, then I would officially lump the FSF as a *much*worse* danger to the free world than the RIAA and the MPAA combined!

I seriously doubt you really thought your idea through! Because it goes beyond stupid.

Linus

#158 lore raw
Quoted 9 lines · Linus Torvalds
Quoted 5 lines · Michael Poole

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

So you want to make things like a 160-bit SHA1 hash of a binary be a "derived work" of that software?

No. That is why I specified "not useful when separated". I also intentionally avoided the phrase "derived work": the legal definition of derived work is based on entirely different factors.

If the signature is one that serves to indicate origin, to detect tampering, or the other things you mentioned, the program's binary is useful when separated from the signature. My objection arises when a functionally equivalent binary -- including advertised functions such as "runs on platform XYZ" -- cannot be produced from the distributed source code.

Michael Poole

#159 lore raw
Quoted 7 lines · Michael Poole

If the signature is one that serves to indicate origin, to detect tampering, or the other things you mentioned, the program's binary is useful when separated from the signature. My objection arises when a functionally equivalent binary -- including advertised functions such as "runs on platform XYZ" -- cannot be produced from the distributed source code.

Ahh.

Ok, that's a totally different issue, and is one where I heartily agree with you. I would actually *love* for the GPL (any version) to have a "guarantee of authenticity", where if you distribute a binary, there has to be some documented way to get *exactly* that binary out of the source code that got distributed.

Of course, SHA1's can be used to verify that, although, quite frankly, I'd expect that a simple "cmp" would be the more straightforward approach.

So the "verification" can be used both to lock down a particular binary _and_ to authenticate that the binary really came from the source code it was claimed to come from.

Of course, in practice, it's actually really nasty to do that verification. Many compilers actually do things like insert date-stamps in the object files etc. So it's probably not all that practical.

Linus

#160 lore raw

Re: Dual-Licensing Linux And Medical Devices

Quoted 10 lines · Linus Torvalds
Quoted 7 lines · Michael Poole

If the signature is one that serves to indicate origin, to detect tampering, or the other things you mentioned, the program's binary is useful when separated from the signature. My objection arises when a functionally equivalent binary -- including advertised functions such as "runs on platform XYZ" -- cannot be produced from the distributed source code.

Quoted 7 lines

Ahh.

Ok, that's a totally different issue, and is one where I heartily agree with you. I would actually *love* for the GPL (any version) to have a "guarantee of authenticity", where if you distribute a binary, there has to be some documented way to get *exactly* that binary out of the source code that got distributed.

I would hope that this is *required*, somehow, when dealing with medical equipment. I don't think those appliances even have the capacity to build every upgrade from source. None that I've tinkered with do. These things almost need a license of their own.

As long as the signing mechanism can't be used to force clinics to pay for the privilege of upgrading free software, that is. It would truly suck if an ultrasound loaded with free software sat in a corner useless because a free clinic could not afford to pay for what they already paid for.

If you guys can find a way to make that practical given my above concerns, that would be entirely useful. I hate the fact that this kind of trust is needed because it is so very easily mis-used, but people dying due to hacked IV regulators really wouldn't much care about those politics.

I think, also privacy implications for patients. A rootkit in a MRI would be very bad.

Regardless, like it or not, kernel code is in or headed for medical devices, so I hope some more brain power is burned on this.

Best,
--Tim

#161 lore raw
In reply to Linus Torvalds
Quoted 9 lines · Linus Torvalds
Quoted 5 lines · Michael Poole

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

So you want to make things like a 160-bit SHA1 hash of a binary be a "derived work" of that software?

How about the combination of the software binary with the hash?

Considering that the hash is a functional part of the software, as in, if you take that out, it no longer works?

Quoted 1 line

If that were to seriously be an FSF argument,

Remember: I don't speak for the FSF, and I don't speak for FSFLA, just like I don't speak for Red Hat.

Just like you shouldn't redirect your qualms with the FSF to me, you shouldn't direct your qualms with me to the FSF. That would be very wrong.

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}
#162 lore raw
In reply to Linus Torvalds
Quoted 13 lines · Linus Torvalds
Quoted 5 lines · Michael Poole

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

So you want to make things like a 160-bit SHA1 hash of a binary be a "derived work" of that software?

Trust me, you *really* don't want to go there. It's an insane legal standpoint, and if you were right, we'd be in a *world* of trouble.

Quoted 7 lines

Think about something as simple as security software that creates filesystem checksums for verifying the integrity of the filesystem, and protects against tampering.

Do you *really* want to claim that the SHA1 checksum of your "oracle" binary is owned by Oracle, and you need to have a special license to copy that checksum around and verify it?

not only that, but it would instantly turn everyone who owns a hard drive or a CD-ROM into a copyright violator: the disks checksums the content of the disk _in a reversible way_. Same for RAID5 and RAID6 techniques. By installing Quake3 on a Windows box one sure does not have permission to create a derived work of Windows and Quake3, right? =B-)

a checksum, a one-way hash, or even reversible parity bit(s) that 'mixes' the copies of multiple works together clearly cannot be new work that falls under copyright protection.

Firstly, it is not a new work, because a 'work' has to be created by a human - and here the new content was created by a machine. Copyright protection only applies to sufficiently original works created by humans.

Secondly, it is _at most_ a new, partial copy of existing works and hence you need the permission to copy all the works in question. (but you needed that permission to create the harddisk anyway)

Thirdly, it could be argued that the sha1 is not even a copy, because it is irreversible and hence not even a single bit of the original work can be reconstructed from it hence it cannot even be a 'partial copy of the original'.

that's at least 3 robust levels of argument against the insane and absurd notion that the SHA1 key is somehow a derived work of the copy it checksums.

Ingo

#163 lore raw
Quoted 2 lines · Ingo Molnar

Secondly, it is _at most_ a new, partial copy of existing works and hence you need the permission to copy all the works in question.

Wouldn't you consider the signing key as one of these existing works?

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}
#164 lore raw
In reply to Michael Poole
Quoted 37 lines · On Thursday 14 June 2007 23:04:37 Michael Poole wrote:
Quoted 19 lines · Daniel Hazelton
Quoted 6 lines · On Thursday 14 June 2007 22:13:13 Michael Poole wrote:

The fundamental reason for this is that neither the executable code nor the digital signature serves the desired function alone. The user received a copy of the executable for a particular purpose: to run the program on a particular platform. With DRM signatures, only the combination of program and signature will perform that function, and separating the two based on strictly read legal definitions is risky.

I agree.

Quoted 8 lines

The question of whether DRM signatures are covered by the license must be resolved before one can determine whether Tivo gave "*EXACTLY*" the same rights to object-code recipients as Tivo received. GPLv2 is worded such that the answer to this does not depend on whether one is in file A and the other in file B, or whether one is on hard drive C and the other is in flash device D, as long as they are delivered as part of one unit; it *might* matter if, say, one is received on physical media and the other is downloaded on demand.

Quoted 5 lines

I have read the GPLv2 at least three times since it was pointed out that I had forgotten part of it. At no point can I find a point where Tivo broke the GPLv2 requirement that they give the recipients of the object code the same rights they received when they acquired a copy of the object or source code.

I am trying to reconcile your responses to those two paragraphs.

If the DRM signature and program executable are coupled such that they are not useful when separated, the implication to me is that they form one work that is based on the original Program. This is beyond the GPL's permission for "mere aggregation".

If they are one work, and the original Program was licensed under the GPLv2, the combined work must also be licensed under the terms of the GPLv2.

Quoted 7 lines

The input files required to generate a DRM-valid digital signature are part the preferred form for modifying that work.

If those bits are not distributed along with the rest of the GPL'ed work, the distributor is either not giving the same rights to the end user, not distributing the source code for the work, or both. Which is it?

Following your logic it would be a "failure to distribute the source code for a work".

However, since the signing is an automated process it cannot generate a "new" work - at least, not under the laws of the US - so the signature itself cannot have a copyright at all.

DRH
PS: This is the exact same reason that the GPL cannot apply to a Bison generated parser in the US. The "input" file that causes Bison to generate the output can have a copyright, but not the output - no matter what RMS or anyone else wants, and no matter what the GPL says about it.

Quoted 2 lines

Michael Poole

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#165 lore raw
Quoted 7 lines · Daniel Hazelton

Following your logic it would be a "failure to distribute the source code for a work".

However, since the signing is an automated process it cannot generate a "new" work - at least, not under the laws of the US - so the signature itself cannot have a copyright at all.

Quoted 5 lines

DRH
PS: This is the exact same reason that the GPL cannot apply to a Bison generated parser in the US. The "input" file that causes Bison to generate the output can have a copyright, but not the output - no matter what RMS or anyone else wants, and no matter what the GPL says about it.

I do not suggest that copyright subsists in the signature or in the signing key. Whether it does is irrelevant to the signing key being part of the source code (when the signature is needed for the binary to work properly).

Similarly, copyright might not subsist in a simple linker script -- its content being determined by the operating system and perhaps the rest of the program's source code -- but under the GPL, the linker script would be part of the source code for a compiled version.

Michael Poole

#166 lore raw
Quoted 3 lines · Michael Poole
Quoted 3 lines

However, since the signing is an automated process it cannot generate a "new" work - at least, not under the laws of the US - so the signature itself cannot have a copyright at all.

[...]

Quoted 5 lines

I do not suggest that copyright subsists in the signature or in the signing key. Whether it does is irrelevant to the signing key being part of the source code (when the signature is needed for the binary to work properly).

it is very much relevant. By admitting that the key is not part of the "work", you have lost all moral basis to claim control over it. Cutely "defining it" into the source code just hides what this really is: the key is a "payment" in exchange for the license, which payment goes outside the scope of the software itself. It has no relevance to the software work being "free", it reaches for paymeant beyond the work to advance the FSF's agenda.

yes, a copyright license can be used to control other works, it can be used to control the movement of non-copyrightable items as well (such as money), but the GPL always tried to stay out of that kind of business.

Where does this "reach out for more resources in exchange for the license" process stop? As the value of free software increases, will the FSF iterate the GPL to ask for more and more consideration for the privilege to license that software? (All in the name of achieving more freedom of course.)

Quoted 4 lines

Similarly, copyright might not subsist in a simple linker script -- its content being determined by the operating system and perhaps the rest of the program's source code -- but under the GPL, the linker script would be part of the source code for a compiled version.

the linker script is still part of the whole work though - even if that particular element might not be copyrightable in isolation. Likewise, the kernel contains code that is in the public domain - to which copyright protection does not extend either. But you cannot argue that the Tivo 'key' is part of the whole work. It is part of the _hardware_. The Tivo box is a compilation (at most a collection) of multiple works, and allowing the GPL to jump over derivation/modification lines is wrong. The GPLv2 certain doesnt do that land-grab.

Ingo

#167 lore raw
Quoted 7 lines · Ingo Molnar
Quoted 3 lines · Michael Poole
Quoted 3 lines

However, since the signing is an automated process it cannot generate a "new" work - at least, not under the laws of the US - so the signature itself cannot have a copyright at all.

[...]

Quoted 1 line
Quoted 7 lines
Quoted 4 lines

I do not suggest that copyright subsists in the signature or in the signing key. Whether it does is irrelevant to the signing key being part of the source code (when the signature is needed for the binary to work properly).

it is very much relevant. By admitting that the key is not part of the "work", you have lost all moral basis to claim control over it.

I have not admitted any such thing. I have said the key and signature do not have separate copyright protection. Variables named "i" in a file are not protected by copyright, but they are very much part of the source code in that file.

Quoted 5 lines
Quoted 4 lines

Similarly, copyright might not subsist in a simple linker script -- its content being determined by the operating system and perhaps the rest of the program's source code -- but under the GPL, the linker script would be part of the source code for a compiled version.

Quoted 8 lines

the linker script is still part of the whole work though - even if that particular element might not be copyrightable in isolation. Likewise, the kernel contains code that is in the public domain - to which copyright protection does not extend either. But you cannot argue that the Tivo 'key' is part of the whole work. It is part of the _hardware_. The Tivo box is a compilation (at most a collection) of multiple works, and allowing the GPL to jump over derivation/modification lines is wrong. The GPLv2 certain doesnt do that land-grab.

Where in the Tivo hardware is the signing key? There is a related key in the hardware, but that one is not used to generate an integral part of the kernel binary.

Michael Poole

#168 lore raw
Quoted 5 lines · Michael Poole
Quoted 5 lines
Quoted 4 lines

I do not suggest that copyright subsists in the signature or in the signing key. Whether it does is irrelevant to the signing key being part of the source code (when the signature is needed for the binary to work properly).

Quoted 7 lines
Quoted 2 lines

it is very much relevant. By admitting that the key is not part of the "work", you have lost all moral basis to claim control over it.

I have not admitted any such thing. I have said the key and signature do not have separate copyright protection. Variables named "i" in a file are not protected by copyright, but they are very much part of the source code in that file.

the problem with your argument is that the definition of what constitutes "work" is up to copyright law, _not_ the license writer. I.e. you cannot just cleverly define "source code" to include something unrelated and then pretend that it's all in one work. And that's exactly what the GPLv3 does: it creatively defines the hardware's key into the 'source code' of the software and then asks for that to be provided _not_ because somehow the key derives from the software (it clearly does not), but as a "compensation" for the right to redistribute! I.e. it's trying to extend its scope to some item that is not part of the software. See?

Ingo

#169 lore raw
Quoted 10 lines · Ingo Molnar
Quoted 8 lines · Michael Poole
Quoted 7 lines
Quoted 4 lines

I do not suggest that copyright subsists in the signature or in the signing key. Whether it does is irrelevant to the signing key being part of the source code (when the signature is needed for the binary to work properly).

it is very much relevant. By admitting that the key is not part of the "work", you have lost all moral basis to claim control over it.

Quoted 7 lines
Quoted 4 lines

I have not admitted any such thing. I have said the key and signature do not have separate copyright protection. Variables named "i" in a file are not protected by copyright, but they are very much part of the source code in that file.

the problem with your argument is that the definition of what constitutes "work" is up to copyright law, _not_ the license writer.

Linux is unquestionably a work protected under copyright law. When I compile Linux, copyright law still protects the executable form. This is not a problem.

Quoted 8 lines

I.e. you cannot just cleverly define "source code" to include something unrelated and then pretend that it's all in one work. And that's exactly what the GPLv3 does: it creatively defines the hardware's key into the 'source code' of the software and then asks for that to be provided _not_ because somehow the key derives from the software (it clearly does not), but as a "compensation" for the right to redistribute! I.e. it's trying to extend its scope to some item that is not part of the software. See?

No. The GPL does not care about the hardware's key, as I pointed out in the part of my email that you cut out. The GPL cares about the key used to generate an integral part of the executable form of the GPLed work. The executable does not function properly if it lacks that part. This is exactly the same way in which the GPL cares about the programming instructions in other parts of the source code: if you remove them, the resulting work does something quite different. See?

Michael Poole

#170 lore raw
Quoted 9 lines · Michael Poole
Quoted 8 lines

I.e. you cannot just cleverly define "source code" to include something unrelated and then pretend that it's all in one work. And that's exactly what the GPLv3 does: it creatively defines the hardware's key into the 'source code' of the software and then asks for that to be provided _not_ because somehow the key derives from the software (it clearly does not), but as a "compensation" for the right to redistribute! I.e. it's trying to extend its scope to some item that is not part of the software. See?

Quoted 5 lines

No. The GPL does not care about the hardware's key, as I pointed out in the part of my email that you cut out. The GPL cares about the key used to generate an integral part of the executable form of the GPLed work. The executable does not function properly if it lacks that part. [...]

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

now if you put the harddisk back into the Tivo, the Tivo's bootloader will refuse to run that modified kernel. So will it (and any Linux bootloader) refuse to load the kernel if you corrupt the compressed format and the gunzip function finds a CRC error. You cannot run arbitrary binaries on hardware without knowing the properties of that hardware. One such property of the hardware might be: "i only run applications that use at most 500 MB of RAM" - because ... the hardware might only have 512 MB of RAM. Another property of the hardware might
be: "i will only trust and run applications that match a given signature". Dont buy that hardware if you dont like its inherent limitations!

The modification the GPL talks about is about modification of the SOURCE CODE. But if you have a new binary, you have no expectation of being able to run that on a piece of hardware. It might or might not run. (for example if you modified the software to include a 1 GB static array then the software might not work on a system that has only 512 MB of RAM.)

go download the Tivo Linux kernel from:

http://dynamic.tivo.com/linux/811/linux-2.4.tar.gz

modify and build it. Boot it on your general purpose PC. It will quite likely work just fine!

Ingo

#171 lore raw
Quoted 17 lines · Ingo Molnar
Quoted 9 lines · Michael Poole
Quoted 8 lines

I.e. you cannot just cleverly define "source code" to include something unrelated and then pretend that it's all in one work. And that's exactly what the GPLv3 does: it creatively defines the hardware's key into the 'source code' of the software and then asks for that to be provided _not_ because somehow the key derives from the software (it clearly does not), but as a "compensation" for the right to redistribute! I.e. it's trying to extend its scope to some item that is not part of the software. See?

Quoted 5 lines

No. The GPL does not care about the hardware's key, as I pointed out in the part of my email that you cut out. The GPL cares about the key used to generate an integral part of the executable form of the GPLed work. The executable does not function properly if it lacks that part. [...]

Quoted 5 lines

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

Tivo did not program or sell the hard drive to be used in an arbitrary Linux PC. They sold the hard drive to be used in their hardware, with a Linux kernel specifically modified for that. Without the right digital signature, it does not do the same thing: it is *incomplete*. That is eminently a software issue. Hardware limitations -- whether they be RAM size or requirement for a certain digital signature -- are beside the point.

The requirement that I "modify a bit in the kernel image header" is also one of the most pathetic cop-outs I have seen. What makes that binary format the preferred form for modification of Linux?

Michael Poole

#172 lore raw
In reply to Ingo Molnar
Quoted 5 lines · Ingo Molnar

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

Ok, try this: take the disk out, remove/replace/modify the signature, put the disk back in, and tell me what it is that fail to run.

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}
#173 lore raw
Quoted 10 lines · Alexandre Oliva
Quoted 5 lines · Ingo Molnar

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

Ok, try this: take the disk out, remove/replace/modify the signature, put the disk back in, and tell me what it is that fail to run.

you mean back into the Tivo? That is not support for what you claimed. You claimed the "executable does not function properly" if it lacks that part (and you did not qualify your statement with anything). That was a false statement, because it still works fine in just about any bog-standard PC. A true statement would be: "the modified executable does not function properly _in the Tivo_". It still works fine on a general purpose PC.

In fact, you couldnt even modify the binary on the Tivo, because the Tivo is not a general purpose PC, it is a PVR. You'd have to put the disk into a PC to modify the binary. And then you'd have to put it back into the Tivo. So even in this silly example of yours you _already_ have to have a general purpose programmable system where the free software runs fine, and even under your strained and invalid interpretation of the GPLv2, your "rights" to modify the software are very well present on that general purpose system.

But you didnt really want to make use of Tivo's free software enhancements, right? Lets face the sad truth: the overwhelming majority of Tivo 'modders' wanted to hack the PVR not to enhance the Tivo, they more likely wanted to watch pay-per-view content without the pay bit and they perhaps wanted to get around service restrictions that the Tivo implements (and through which it funds lower-than-production-cost for the PVR). So the 'rights' you are trying to protect are invented 'rights' of mostly _freeloaders_ in fact. The 'Tivo community' was conjured up after the fact. So even in this supposedly golden and hand-picked DRM example of RMS, the whole story stinks from beginning to end and has all the classic earmarks of detached-from-the-real-world religious extremism in the works ...

and the whole effort is totally pointless anyway. Consumers are already voting with their feet against DRM restrictions. So the only DRM victims of the GPLv3 attack measures will be the _good_ uses of DRM. People will be able to use tamper-proof, vendor-upgradable hardware based on FreeBSD, but not based on any GPLv3 kernel. Nobody will care about content DRM at that point anymore, and all that remains is a license that is crippled for the _good_ uses. Smart move to advance free software, eh? Really, RMS should have kept hacking code a bit longer so that he doesnt become that totally detached from the rest of us.

Ingo

#174 lore raw
Quoted 13 lines · Ingo Molnar
Quoted 10 lines · Alexandre Oliva
Quoted 5 lines · Ingo Molnar

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

Ok, try this: take the disk out, remove/replace/modify the signature, put the disk back in, and tell me what it is that fail to run.

Quoted 7 lines

you mean back into the Tivo? That is not support for what you claimed. You claimed the "executable does not function properly" if it lacks that part (and you did not qualify your statement with anything). That was a false statement, because it still works fine in just about any bog-standard PC. A true statement would be: "the modified executable does not function properly _in the Tivo_". It still works fine on a general purpose PC.

I claimed that. Unless I missed something, Alexandre did not.

Ability to run on a standard PC is irrelevant. Tivo distributes the executable for the specific purpose of running on their hardware. Having the signature accepted by the hardware is a critical aspect of the executable. That purpose and function are what make the signature part of the work based on Linux.

Courts consider purpose and intent when analyzing actions; except when one has bought the best available legal system, they would not follow your logic. (The role the signature plays in controlling access to a copyrighted work, per DMCA, might also separately identify it as part of the work based on Linux.)

If I wished to distribute a kernel with extended functionality from a C file but not the C source files, under your logic I need not give them out -- a user could modify the binary and run it on a general purpose PC. Right? At most it would take clever linker tricks to make the change small enough.

As to the suggestion that vendors would use another kernel: I would not mind. A huge fraction of the interesting and useful work in open source kernels happens in Linux (first or only). Using any third party software is a trade-off of what you get versus what you give up.

Michael Poole

#175 lore raw
In reply to Ingo Molnar
Quoted 13 lines · Ingo Molnar
Quoted 10 lines · Alexandre Oliva
Quoted 5 lines · Ingo Molnar

it is a false statement on your part that the executable "does not function properly" if it lacks that part. Try it: take out the harddisk from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux PC, mount it, modify a bit in the kernel image header and it will likely still boot just fine on that PC.

Ok, try this: take the disk out, remove/replace/modify the signature, put the disk back in, and tell me what it is that fail to run.

Quoted 7 lines

you mean back into the Tivo? That is not support for what you claimed. You claimed the "executable does not function properly" if it lacks that part (and you did not qualify your statement with anything). That was a false statement, because it still works fine in just about any bog-standard PC. A true statement would be: "the modified executable does not function properly _in the Tivo_". It still works fine on a general purpose PC.

I stand """corrected""". It doesn't matter, because the TiVo is where the combination of the executable with the signature shipped, and, see, I didn't talk about modifying the executable, what I wrote about above was modifying the signature alone. See?

Quoted 8 lines

But you didnt really want to make use of Tivo's free software enhancements, right? Lets face the sad truth: the overwhelming majority of Tivo 'modders' wanted to hack the PVR not to enhance the Tivo, they more likely wanted to watch pay-per-view content without the pay bit and they perhaps wanted to get around service restrictions that the Tivo implements (and through which it funds lower-than-production-cost for the PVR). So the 'rights' you are trying to protect are invented 'rights' of mostly _freeloaders_ in fact.

Sony Betamax anyone?

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}
#176 lore raw
In reply to Michael Poole
Quoted 3 lines · Michael Poole

The GPL cares about the key
used to generate an integral part of the executable form of the GPLed work.

GLPv2 doesn't: why do you think the digital signature is an integral part of the executable? It can be a totally separate blob, distributed via a separate channel and even stored at a different location than the executable. Does it still look like an integral part of the executable to you then?

(unless of course you're trying to argue that the hash itself is a derivative work, but that has already been refuted many times before.)

Quoted 2 lines

The executable does not function properly if it lacks that part.

It works just fine given the right environment. The right environment may be some other hardware (without DRM restrictions) or the DRMed device + an authorized digital signature. The digital signature is not part of your executable.

Do you honestly believe GPLv2 requires the distributor to provide you with the right environment for your modified copy to "function properly"? I would say it doesn't, but feel free to point me to specific sections which *state* otherwise. AFAICT, GPLv2 is specifically limited to "copying, distribution and modification". How you use (or don't use, or can't use) your modified copy is totally outside its scope.

---
fm

#177 lore raw
Quoted 10 lines · Florin Malita
Quoted 3 lines · Michael Poole

The GPL cares about the key
used to generate an integral part of the executable form of the GPLed work.

GLPv2 doesn't: why do you think the digital signature is an integral part of the executable? It can be a totally separate blob, distributed via a separate channel and even stored at a different location than the executable. Does it still look like an integral part of the executable to you then?

Yes. If I cut a book in half and store the halves separately, does the second half become an independent work? The integral-ness is a function of how the thing is created and how it functions, not how it is stored. If you need part B for part A to execute as intended, then part A is not a complete work in itself. On top of this, in the Tivo case the two are distributed together, and even part of the same file.

[snip]

Quoted 7 lines

Do you honestly believe GPLv2 requires the distributor to provide you with the right environment for your modified copy to "function properly"? I would say it doesn't, but feel free to point me to specific sections which *state* otherwise. AFAICT, GPLv2 is specifically limited to "copying, distribution and modification". How you use (or don't use, or can't use) your modified copy is totally outside its scope.

The GPL does not require a distributor to provide me with any kind of environment. If I get a Tivo kernel image but do not have a Tivo, the GPL does not require anyone to give me hardware. Fortunately, that is not at all my argument.

Michael Poole

#178 lore raw
Quoted 16 lines · Michael Poole
Quoted 6 lines · Florin Malita
Quoted 4 lines · Michael Poole

The GPL cares about the key
used to generate an integral part of the executable form of the GPLed work.

Quoted 6 lines

GLPv2 doesn't: why do you think the digital signature is an integral part of the executable? It can be a totally separate blob, distributed via a separate channel and even stored at a different location than the executable. Does it still look like an integral part of the executable to you then?

Quoted 2 lines

Yes. If I cut a book in half and store the halves separately, does the second half become an independent work?

Except in this case you're not touching the book at all. If you write a review for a book (much better analogy methinks), then your review is obviously not an integral part of the book even though it's based on its content.

Quoted 4 lines

The integral-ness is a
function of how the thing is created and how it functions, not how it is stored. If you need part B for part A to execute as intended, then part A is not a complete work in itself.

Being an integral part (as in combined or derived work) has nothing to do with usability. There are many other bits and pieces your executable needs in order to function properly (or at all) but that doesn't make your CPU microcode & electricity provider an integral part of the program, does it?

Luckily, it doesn't really matter what you or I think that "integral-ness" means, all it matters is how copyright law defines a "derivative work" and whether a cryptographic hash is such a thing. Now are you seriously arguing that a hash is a derivative work?

Quoted 3 lines

On top of this, in the Tivo
case the two are distributed together, and even part of the same file.

It's mere aggregation, but it's totally irrelevant because they could just as easily change their approach.

---
fm

#179 lore raw
Quoted 16 lines · Florin Malita
Quoted 15 lines · Michael Poole
Quoted 11 lines · Florin Malita
Quoted 3 lines · Michael Poole

The GPL cares about the key
used to generate an integral part of the executable form of the GPLed work.

GLPv2 doesn't: why do you think the digital signature is an integral part of the executable? It can be a totally separate blob, distributed via a separate channel and even stored at a different location than the executable. Does it still look like an integral part of the executable to you then?

Quoted 7 lines
Quoted 2 lines

Yes. If I cut a book in half and store the halves separately, does the second half become an independent work?

Except in this case you're not touching the book at all. If you write a review for a book (much better analogy methinks), then your review is obviously not an integral part of the book even though it's based on its content.

Extremely poor analogy. I do not distribute my review with the book. Someone buying the book is able to use the book just fine (for the purpose for which it was sold) without my review. They need neither my review nor other modifications before the book becomes readable. As Ingo said, you need either the digital signature or other changes before a Tivo kernel image will load.

Quoted 10 lines
Quoted 4 lines

The integral-ness is a
function of how the thing is created and how it functions, not how it is stored. If you need part B for part A to execute as intended, then part A is not a complete work in itself.

Being an integral part (as in combined or derived work) has nothing to do with usability. There are many other bits and pieces your executable needs in order to function properly (or at all) but that doesn't make your CPU microcode & electricity provider an integral part of the program, does it?

No. Those are independent works. They are not distributed to make a certain piece of software function in a particular way or place. The presence of software in a box with CPU microcode is -- at least in every case I have seen -- what GPL calls "mere aggregation".

Quoted 4 lines

Luckily, it doesn't really matter what you or I think that "integral-ness" means, all it matters is how copyright law defines a "derivative work" and whether a cryptographic hash is such a thing. Now are you seriously arguing that a hash is a derivative work?

No. I explained this before. Try reading the thread and the GPL. I am not sure where people get the (wrong) idea that the GPL only concerns itself with "derivative work[s]".

Quoted 6 lines
Quoted 3 lines

On top of this, in the Tivo
case the two are distributed together, and even part of the same file.

It's mere aggregation, but it's totally irrelevant because they could just as easily change their approach.

If and when they do, I'll consider the rules that might apply. Until then, it is fairly stupid to try to defend Tivo by saying they *might* do something they currently don't, and if they did, they *might* have a defense that they currently don't.

Michael Poole

#180 lore raw
Quoted 8 lines · Michael Poole
Quoted 5 lines · Florin Malita
Quoted 3 lines · Michael Poole

Yes. If I cut a book in half and store the halves separately, does the second half become an independent work?

Quoted 8 lines
Quoted 5 lines

Except in this case you're not touching the book at all. If you write a review for a book (much better analogy methinks), then your review is obviously not an integral part of the book even though it's based on its content.

Extremely poor analogy. I do not distribute my review with the book.

But you do (because I say so ; ), and guess what? It makes no difference: your review is not a derivative work anymore than it was before.

Quoted 4 lines

Someone buying the book is able to use the book just fine (for the purpose for which it was sold) without my review. They need neither my review nor other modifications before the book becomes readable.

Exactly. So what's your difficulty in downloading the Tivo code, reading it and re-using it in your own projects, on your other devices? How is the missing signing key preventing you from doing any of that?

Someone buying the book may be free to read it anywhere but if they insist on reading it at your table you may sensibly require they bring a copy of your review with them (to prove their genuine interest ; ). Failure to comply only means they have to read the book someplace else. Can they read the book? Sure. Can they read it at your table? Only if you choose to allow them.

Quoted 3 lines

As Ingo said, you need either the digital signature or other changes before a Tivo kernel image will load.

GPLv2 guarantees that the book remains readable. It does not grant you (doesn't even try) the right to execute a modified copy on any particular piece of hardware. Your kernel is perfectly functional on any platform that supports it - it just so happens that the Tivo device does not support it.

Quoted 8 lines
Quoted 6 lines

Being an integral part (as in combined or derived work) has nothing to do with usability. There are many other bits and pieces your executable needs in order to function properly (or at all) but that doesn't make your CPU microcode & electricity provider an integral part of the program, does it?

No. Those are independent works.

So is a digital signature. Again, are you arguing the digital signature is a derivative work?

Quoted 11 lines
Quoted 6 lines

Luckily, it doesn't really matter what you or I think that "integral-ness" means, all it matters is how copyright law defines a "derivative work" and whether a cryptographic hash is such a thing. Now are you seriously arguing that a hash is a derivative work?

No. I explained this before. Try reading the thread and the GPL. I am not sure where people get the (wrong) idea that the GPL only concerns itself with "derivative work[s]".

I guess you'll have to explain again because copyright law and its definition of derivative works are the things that make the GPL work:

"0.This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law".

What I can't find though is any reference to "integral parts" or your taken-for-granted right to run a modified copy of the program on the same device used for distribution (or any mention of functionality at all for that matter). Actually: "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope".

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

On top of this, in the Tivo
case the two are distributed together, and even part of the same file.

Quoted 9 lines
Quoted 3 lines

It's mere aggregation, but it's totally irrelevant because they could just as easily change their approach.

If and when they do, I'll consider the rules that might apply. Until then, it is fairly stupid to try to defend Tivo by saying they *might* do something they currently don't, and if they did, they *might* have a defense that they currently don't.

But you're missing the whole point: the rules are the same, nothing changes! You are drawing an artificial distinction between the two cases and focusing on aggregation, which is totally irrelevant: either the digital signature is a derivative work or it isn't, and in either case its distribution method makes no difference in the world.

The reason I brought up the separate-signature example is to illustrate just how ridiculous is to think of the signature keys as source files: you can implement an equivalent DRM system without ever modifying the kernel blob. Only difference is the channel used for signature distribution, and I hope you won't argue that mere aggregation changes its nature.

---
fm

#181 lore raw
In reply to Ingo Molnar
Quoted 4 lines · Ingo Molnar

that's exactly what the GPLv3 does: it creatively defines the hardware's key into the 'source code' of the software and then asks for that to be provided _not_ because somehow the key derives from the software

Dude, you're 3 drafts behind. And some people already read GPLv2 like that.

Quoted 3 lines

(it clearly does not), but as a "compensation" for the right to redistribute! I.e. it's trying to extend its scope to some item that is not part of the software. See?

The "compensation" is and has always been "respecting others' freedoms". If the key is used to disrespect others freedoms, as it is by TiVO, then TiVO is failing to keep its part in the deal.

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}
#182 lore raw
In reply to Ingo Molnar
Quoted 2 lines · Ingo Molnar

it is very much relevant. By admitting that the key is not part of the "work", you have lost all moral basis to claim control over it.

legal basis, maybe. legality and morality are quite different concepts.

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}
#183 lore raw
In reply to Daniel Hazelton
Quoted 5 lines

Because GPLv2 doesn't enforce limitations on the hardware a GPL'd work can be put on. It doesn't make artificial distinctions between "Commercial", "Industrial" and "User". What it does is *ATTEMPT* to ensure that nobody receiving a copy of a GPL'd work has the same rights as any other person that gets a copy. GPLv3 gives people *additional* rights beyond those.

IMO this statement expressedly exposes the different viewpoints as used in various factions in this discussion.

Without adopting all the details I think I can agree to the above stmt. However I don't agree with the implied msg as I perceive it.

In the following I'll try to explain what I mean by the above.

I don't know whether what TiVo did actually was allowed by the legal phrases of the GPLv2. I can image it was legally valid but I don't know. But then I'm convinced it was one of the things the inventors of the GPL wanted to make illegal by it -- they may have failed to do so when wording the legal part.

I like to remind you of the story with the broken closed source printer driver RMS tried to fix at MIT (if I recall correctly) and the frustration that he couldn't do so that finally made him start the FSF.

No customer can fix his TiVo box without the cooperation of the HW vendor. If they refuse there is nothing that can be done. For me this is very much like printer story above.

Assuming you (the reader) agree so far:
I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

Now for a different PoV:
Do I think Tivoisation is bad for the community ? Of course I think it is but your mileage may vary.

Anyway, if one considers Tivoisation acceptable then there is no reason to stop using GPLv2.

If one wishes to prevent it there are two related questions:
- does GPLv2 prevent it ?
- if GPLv2 does not prevent it then how can we change it to achieve that ?

To me it seems as if the FSF tends to answer the first question with 'no' and consequently answers the second question with 'GPLv3'.

Whether or not the GPLv3 is truely an acceptable answer to prevent Tivoisation is a completely different issue that I can't really judge.

Last not least:
Nothing of the above has to do with ethics, moral or any such cathegories. This is by intention.

Thank you for reading thus far -- I hope I made myself clear.

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
#184 lore raw
Quoted 9 lines · On Friday 15 June 2007 02:24:37 Michael Gerdau wrote:
Quoted 6 lines

Because GPLv2 doesn't enforce limitations on the hardware a GPL'd work can be put on. It doesn't make artificial distinctions between "Commercial", "Industrial" and "User". What it does is *ATTEMPT* to ensure that nobody receiving a copy of a GPL'd work has the same rights as any other person that gets a copy. GPLv3 gives people *additional* rights beyond those.

IMO this statement expressedly exposes the different viewpoints as used in various factions in this discussion.

Agreed. And thanks for ignoring the obvious typo.

Quoted 10 lines

Without adopting all the details I think I can agree to the above stmt. However I don't agree with the implied msg as I perceive it.

In the following I'll try to explain what I mean by the above.

I don't know whether what TiVo did actually was allowed by the legal phrases of the GPLv2. I can image it was legally valid but I don't know. But then I'm convinced it was one of the things the inventors of the GPL wanted to make illegal by it -- they may have failed to do so when wording the legal part.

No doubt. However, GPLv2 actually states in clear and concise english that it doesn't cover *anything* but the rights to "copy, distribute and modify" covered works. It actually states that other rights are beyond the scope of the license. That statement, IMHO (and IANAL), obviates any other "intent" the "inventor" of the license may have had by making the scope of the license clear.

<snip>

Quoted 3 lines

No customer can fix his TiVo box without the cooperation of the HW vendor. If they refuse there is nothing that can be done. For me this is very much like printer story above.

I own an XBox 360. If it breaks I can't fix it without the cooperation of MS. The fact that a TiVO runs an OS that is licensed under the GPL doesn't change the fact that the situation is *exactly* the same. TiVO breaks? Manufacturer (or someone certified and licensed for the task by the manu) fixes it. XBox breaks? Manufacturer fixes it. My laptop breaks? As long as its under warranty, the manufacturer fixes it *FOR* *FREE* - if it's out of warranty, I pay for the "service" but they still fix it. QED: The "manufacturer must cooperate in or perform the repair" is not some new idea - its actually common practice.

Quoted 7 lines

Assuming you (the reader) agree so far:
I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

It might be that you are correct. However, thanks to someone having actually identified the exact scope of the GPLv2 *in* the legally active text of the license the "intent" shouldn't have much weight or bearing. Look at the first sentence of the second paragraph of section 0. "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope."

Quoted 4 lines

Now for a different PoV:
Do I think Tivoisation is bad for the community ? Of course I think it is but your mileage may vary.

And I happen to agree with you. What I disagree with is taking steps to make "bad == illegal". I also have a problem with doing things that force my viewpoint on other people.

Quoted 7 lines

Anyway, if one considers Tivoisation acceptable then there is no reason to stop using GPLv2.

If one wishes to prevent it there are two related questions:
- does GPLv2 prevent it ?
- if GPLv2 does not prevent it then how can we change it to achieve that ?

Quoted 5 lines

To me it seems as if the FSF tends to answer the first question with 'no' and consequently answers the second question with 'GPLv3'.

Whether or not the GPLv3 is truely an acceptable answer to prevent Tivoisation is a completely different issue that I can't really judge.

And neither am I. My whole point in arguing over it has been that, despite what some people want to believe, it isn't violating the GPLv2 in any way, shape or form.

Quoted 4 lines

Last not least:
Nothing of the above has to do with ethics, moral or any such cathegories. This is by intention.

Thank you for that.

Quoted 1 line

Thank you for reading thus far -- I hope I made myself clear.

Yes, you have.

DRH

Quoted 2 lines

Best wishes,
Michael

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#185 lore raw
Quoted 5 lines · Daniel Hazelton
Quoted 3 lines

Now for a different PoV:
Do I think Tivoisation is bad for the community ? Of course I think it is but your mileage may vary.

And I happen to agree with you. What I disagree with is taking steps to make "bad == illegal". I also have a problem with doing things that force my viewpoint on other people.

Surely it's more:
bad == go away and don't use future improvements to our software anymore please.
??

*If* you think it's bad (Linus doesn't as far as the kernel goes) then isn't it reasonable to exclude 'bad for the community' from the community?

This isn't retroactive - they can continue to use any V2 software they had, they wouldn't be able to use V3 developments.

That seems to me to be a very, very reasonable thing to do (and very much *not* bad == illegal IMHO)

David

PS well, I was just seeing if anyone had fixed my libata/md bug yet but this seemed more interesting. PPS and Tejun has, I'm off...

#186 lore raw
Quoted 5 lines · On Friday 15 June 2007 06:18:59 David Greaves wrote:
Quoted 4 lines · Daniel Hazelton
Quoted 3 lines

Now for a different PoV:
Do I think Tivoisation is bad for the community ? Of course I think it is but your mileage may vary.

Quoted 7 lines
Quoted 3 lines

And I happen to agree with you. What I disagree with is taking steps to make "bad == illegal". I also have a problem with doing things that force my viewpoint on other people.

Surely it's more:
bad == go away and don't use future improvements to our software anymore
please. ??

I agree. I stated it in the terms I did because Alexandre originally brought "ethics and morality" into the discussion. Not that my word choice is wrong at all - violating a copyright license is, after all, illegal.

Quoted 2 lines

*If* you think it's bad (Linus doesn't as far as the kernel goes) then isn't it reasonable to exclude 'bad for the community' from the community?

I agree that it is "bad for the community". The impression I've gotten from reading the GPLv3, reading transcripts of interviews with RMS, reading transcripts of interview with Eben Moglen *and* from the FSFLA members participating in this discussion the reason for the anti-tivoization language in GPLv3 isn't "its bad for the community" but "we find it ethically and morally wrong". That being the reason, what they are saying with the language in the GPLv3 is "this is bad/evil and things that are bad/evil should be illegal".

Quoted 5 lines

This isn't retroactive - they can continue to use any V2 software they had, they wouldn't be able to use V3 developments.

That seems to me to be a very, very reasonable thing to do (and very much *not* bad == illegal IMHO)

:) Same here

Quoted 4 lines

David

PS well, I was just seeing if anyone had fixed my libata/md bug yet but this seemed more interesting.

It is. Consumed a solid six-hour stretch of my day (5PM EDT to 11PM EDT, June 14, 2007) (FYI: EDT is UTC - 4)

Quoted 1 line

PPS and Tejun has, I'm off...

Good for you!

DRH

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#187 lore raw
In reply to David Greaves
Quoted 5 lines · David Greaves

Surely it's more:
bad == go away and don't use future improvements to our software anymore
please.
??

Well, with the understanding that I don't think that what Tivo did was bad in the first place, let me tackle that question *anyway*.

The answer is: Not necessarily.

Some people can be "bad" for the community. They may simply be disruptive and not productive at all. They may troll the mailing lists without actually ever doing something good, or they may do other "bad" things.

In fact, let's make it *very* specific: let's say that the bad person is a cracker, and specializes in finding security holes, and writing exploits for them, and selling those exploits to spammers.

Most of us might agree that that is a "bad" person for the community, no?

Now, by your own logic, let's look at what that means for the license. Should we write into our copyright license that you cannot try to find security holes? Would that be a good addition to the GPLv2?

Now, I stated that in a way where the answer is obvious: that would be a *horrible* addition to the GPLv2. I think everybody can agree on that. It would be really stupid to say "you cannot look for security holes" just because *some* people who do it are bad.

Now, think about that for a moment, and then go back to your question about whether Tivo is bad for the community, and whether being bad for the community should mean that the license should be written to say "go away and don't use future improvements to our software".

See where I'm trying to take you?

I think that even people who *do* think that what Tivo did was "bad", should think very deeply about the issue whether you should try to lock out "bad uses" in your license. Yes, the answer may be "yes, you should". But I'm arguing that the answer _may_ also be: "No, you shouldn't, becasue it turns out that you might lock out _good_ people too".

So in my cracker/spammer example, by trying to lock out the bad people, the obvious (and _stupid_ - don't get me wrong, I'm not at *all* suggesting anything like that should ever be done) license addition of "don't expose security problems" actually just causes more problems than it solves (if it solves anything at all - really bad people don't actually tend to even care about the license!).

It makes it harder for *valid* uses of security problem discovery. It makes it potentially illegal to try to do security research. And don't tell me stupid licenses and laws like that don't happen: people really *do* make these kinds of shortsighted decisions, to "protect" themselves from bad people.

I personally think that the same is true of the GPLv3 anti-tivoization clauses. Even if you don't like Tivo, you may well recognize that there are lots of *other* reasons for lock-down. Maybe you hate Tivo, and the RIAA and the MPAA. Fine. What about the FCC? Or what about secure terminals? What about any number of *other* reasons to use validated kernel images?

Now, I cannot speak for Alan Cox (he can speak damn well for himself), but I think Alan is an example of a person who actually really detests what Tivo did. But I also am pretty sure that he's also quite smart enough to see that the GPLv3 anti-tivoization clauses may stop *other* uses that he doesn't dislike and he doesn't think are "wrong", and even though he dislikes what Tivo does, as far as I know, I think his stance on the GPLv3 is that it's actually wrong for Linux.

See? You don't actually have to like Tivo to see downsides to trying to stop them. Because these kinds of things have consequences *outside* of just stopping Tivo.

Linus

#188 lore raw
Quoted 30 lines · Linus Torvalds

Now, by your own logic, let's look at what that means for the license. Should we write into our copyright license that you cannot try to find security holes? Would that be a good addition to the GPLv2?

Now, I stated that in a way where the answer is obvious: that would be a *horrible* addition to the GPLv2. I think everybody can agree on that. It would be really stupid to say "you cannot look for security holes" just because *some* people who do it are bad.

Now, think about that for a moment, and then go back to your question about whether Tivo is bad for the community, and whether being bad for the community should mean that the license should be written to say "go away and don't use future improvements to our software".

See where I'm trying to take you?

I think that even people who *do* think that what Tivo did was "bad", should think very deeply about the issue whether you should try to lock out "bad uses" in your license. Yes, the answer may be "yes, you should". But I'm arguing that the answer _may_ also be: "No, you shouldn't, becasue it turns out that you might lock out _good_ people too".

So in my cracker/spammer example, by trying to lock out the bad people, the obvious (and _stupid_ - don't get me wrong, I'm not at *all* suggesting anything like that should ever be done) license addition of "don't expose security problems" actually just causes more problems than it solves (if it solves anything at all - really bad people don't actually tend to even care about the license!).

Quoted 5 lines

It makes it harder for *valid* uses of security problem discovery. It makes it potentially illegal to try to do security research. And don't tell me stupid licenses and laws like that don't happen: people really *do* make these kinds of shortsighted decisions, to "protect" themselves from bad people.

in fact there was news in the last week or two about a law in Germany that does exactly this. it outlaws all programs that can be used for hacking systems.

David Lang

#189 lore raw
In reply to Linus Torvalds
Quoted 10 lines · Linus Torvalds
Quoted 4 lines · David Greaves

Surely it's more:
bad == go away and don't use future improvements to our software anymore
please.
??

Well, with the understanding that I don't think that what Tivo did was bad in the first place, let me tackle that question *anyway*.

The answer is: Not necessarily.

I do agree with what you say here. Maybe a summary:
Babies, bathwater...
When you have a hammer (license) everything looks like a nail...

Quoted 1 line

See? You don't actually have to like Tivo to see downsides to trying to stop them. Because these kinds of things have consequences *outside* of just stopping Tivo.

My concern is around embedded type systems and maybe even the 'trusted' frameworks etc.

I _think_ I can see a completely opensource system that the end user cannot modify _in any way_. Which kinda defeats the point (to me) of opensource.

This 5 minute design undoubtedly has flaws but it shows a direction:
A basically standard 'De11' PC with some flash.
A Tivoised boot system so only signed kernels boot.
A modified kernel that only runs (FOSS) executables whose signed hash lives in the flash.

Do we (you) _want_ to prevent this?

Do we trust in 'the market' to prevent this?

Do we use license tools?

David

#190 lore raw
Quoted 5 lines · David Greaves

This 5 minute design undoubtedly has flaws but it shows a direction:
A basically standard 'De11' PC with some flash.
A Tivoised boot system so only signed kernels boot.
A modified kernel that only runs (FOSS) executables whose signed hash lives in the flash.

How hard would it be to reprogramm the flash?

Signature · 1 line
Krzysztof Halasa
#191 lore raw
Quoted 9 lines · Krzysztof Halasa
Quoted 5 lines · David Greaves

This 5 minute design undoubtedly has flaws but it shows a direction:
A basically standard 'De11' PC with some flash.
A Tivoised boot system so only signed kernels boot.
A modified kernel that only runs (FOSS) executables whose signed hash lives in the flash.

How hard would it be to reprogramm the flash?

The flash contains hashes signed by the companies private key.

The kernel contains the public key. It can decrypt the hashes but the private key isn't available to encrypt them. So although you can put a new application onto the system, you can't create a signed hash to write to the flash.

The kernel only runs the executable if the hash is valid.
You can re-write the kernel to avoid this check - but the hardware is Tivoised - so you can't run it.

I am not suggesting the kernel should go down the GPLV2 route - I am wondering if this is a viable scenario or one of Schneiers' "movie-plot" threats :)

David

#192 lore raw
Quoted 9 lines · David Greaves
Quoted 1 line

How hard would it be to reprogramm the flash?

The flash contains hashes signed by the companies private key.

The kernel contains the public key. It can decrypt the hashes but the private key isn't available to encrypt them. So although you can put a new application onto the system, you can't create a signed hash to write to the flash.

Quoted 4 lines

The kernel only runs the executable if the hash is valid. You can re-write the kernel to avoid this check - but the hardware is Tivoised -
so you can't run it.

I read it: the flash contains everything from the bootloader to the kernel and file system.
The bootloader contains the public key and checks if the kernel/fs are ok. That includes calculating hashes and checking signatures. No encryption/decryption there at all.

Right?

Then how hard would it be to reprogram the flash, to get rid of all this crap? Or to just put your public key there.

Do they at least use BGA type of flash chips so you can't attach a clip and have to use something more demanding?

Signature · 1 line
Krzysztof Halasa
#193 lore raw
Quoted 10 lines · Krzysztof Halasa
Quoted 7 lines · David Greaves
Quoted 1 line

How hard would it be to reprogramm the flash?

The flash contains hashes signed by the companies private key.

The kernel contains the public key. It can decrypt the hashes but the private key isn't available to encrypt them. So although you can put a new application onto the system, you can't create a signed hash to write to the flash.

Quoted 5 lines

Then how hard would it be to reprogram the flash, to get rid of all this crap? Or to just put your public key there.

Do they at least use BGA type of flash chips so you can't attach a clip and have to use something more demanding?

Stop trying to technically crack my 5-minute fag-packet design - that's easy and boring :)

Tivo have solved this problem - use their solution - but do it on something more general purpose.

Help fix it - the point is more "is this feasible". And if it is, "does it matter?"

David

#194 lore raw
In reply to Michael Gerdau
Quoted 3 lines · Michael Gerdau

I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Umm. It may well have been meant by *rms*. But your argument fatally falls down on the fact that rms has had *nothing* to do with the Linux kernel.

Quoted 3 lines

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

Ehh. The intent that matters is not the intent of the person who authored the license, but the intent of the person who *chose* the license.

In other words, rms has *no* input on the kernel.

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

But to make it even less relevant: intent really only legally matters when the legal issues are unclear.

And they really aren't that unclear here.

Quoted 2 lines

Anyway, if one considers Tivoisation acceptable then there is no reason to stop using GPLv2.

Indeed.

Quoted 3 lines

If one wishes to prevent it there are two related questions:
- does GPLv2 prevent it ?
- if GPLv2 does not prevent it then how can we change it to achieve that ?

Well, I think it's fairly unquestionable that the GPLv3 does prevent it.

So your second question isn't even really interesting. We know the answer. So the only question that is even remotely interesting is the first one.

Quoted 2 lines

To me it seems as if the FSF tends to answer the first question with 'no' and consequently answers the second question with 'GPLv3'.

Yes, I do agree with that reasoning, but there are *other*, and more direct, reasons than just the FSF's answer to say that the answer to your first question is "no".

The fact is, plain reading of the license (which *always* takes precedence over "intent", even in Europe) simply doesn't make what Tivo did illegal.

You literally have to read the GPLv2 in ways that are obviously not true to get to any other situation.

For example, Alexandre made the same two mistakes over and over in his reading when he tried to argue that the GPLv2 disallows what Tivo did:

(a) The right to modify means "modify in place"

This was a point that Alexandre (and others) have tried to make, but it really is *not* supported by any reality.

First off, the GPLv2 simply never *ever* says "in place". That wording (or anything equivalent) simply does not exist! So you really have to add it by "reading" it some special way, and quite frankly, no such reading is sensible.

I can logically *prove* that such a reading is not sensible by the two examples I already made clear to Alexandre multiple times:

- Red Hat sends out DVD's with GPL'd software, and thus distributes copies that CANNOT be "modified in place". So thinking that "modified in place" is made illegal by the GPLv2 is simply untenable, unless you think that what Red Hat does is against the GPLv2.

Do you really believe that what Red Hat does is against the GPL? Does Alexandre? Judging by his email address, I don't think he does.

- I myself distribute Linux by making it available for download publicly, and no, I do *not* allow people to modify it in place, even though I do distribute Linux.

Alexandre tried to argue against this point by saying that I'm not really "distributing" Linux, and that the actual copying is being done by people who download it, and that they *can* modify their downloads "in place", but that only shows a lack of knowledge about what "distribution" means in copyright law.

The US courts have made it very clear that you "distribute" things not by downloading them, but by making them *available* for public download. So from a purely *legal* standpoint, I do actually *distribute* Linux by making it available! And no, I don't allow people to modify it in place!

Again, do you *really* think that I am in violation of the GPL by making the kernel available for download (== distributing it), but not letting others modify it in place?

So clearly, the whole "modify in place" argument is simply *wrong*.

It cannot *possibly* be a valid reading of the GPLv2! When the GPLv2 talks about "legal permissions to copy, distribute and/or modify" the software, it does *not* mean that you have to have the ability to modify it in place!

The other argument Alexandre made was different, but equally invalid from a legal standpoint:

(b) The language in the preamble: "must give the recipients all the rights that you have" means really *all* the rights and abilities!

This too is a totally flawed reading of the license, for a few reasons:

- It's not actually in the *conditions* section. It's part of the explanation of the conditions, and while it's part of the license, it actually *is* different in the sense that it's not even meant to specify the "precise terms and conditions". Those are explicitly laid out _elsewhere_ (look for that term:
"precise terms and conditions").

- However, I don't dispute that the language exists, I just dispute Alexandres _reading_ of it, and I offer an alternate meaning for it. I do not guarantee that *my* reading is the correct one (although practically speaking, I pretty much can guarantee that too), but I *do* guarantee that Alexandre's reading is wrong, because it is nonsensical and impossible.

It is nonsensical and impossible in the exact same way I showed that he was trying to claim something nonsensical and impossible in adding the "in place" reading to "right to modify".

- So the reason I want to mention the fact that it is in the "preamble" is exactly because the preamble is *not* meant to be the "exact terms and conditions", it's meant to be a much softer thing - something that _explains_ the exact terms and conditions.

In particular, in this case, it explains "Section 6" (and you could also say that it explains section 7 too, but the preamble actually talks about patents separately, so you should probably see "section 6" as just the most obvious example of what the preamble is talking about).

- In other words, the preamble is just a preliminary and inexact explanation for the _real_ requirements, which are spelled out elsewhere, in places like section 6 of the license. And *that* section actually makes it clear that "all rights" only concerns the rights SPELLED OUT IN THE LICENSE ITSELF.

Section 6 explicitly says:

"You may not impose any further restrictions on the
recipients' exercise of the rights granted herein."

and that is what I claim is the *correct* and exact reading of the explanatory language in the preamble. Yes, it is "all rights", but it is "all rights" ONLY AS FAR AS THE GPLv2 itself is concerned! It's not about any _other_ additional rights you may have outside the GPLv2!

- To finish that point, let me just point out that Alexandre's reading *cannot* possibly work!

In particular, reading the preamble to mean that you give the recipient *all* rights you have (even outside the actual requirements of the license itself) that Alexandre tried to argue, is actually legally simply impossible. The copyright owner *fundamentally* has more rights than any licensee, and no license can *ever* transfer all those legal rights!

In other words, Alexandre's reading of the preamble is simply not legally tenable, because it assumes that the license says something that simply is not legally possible. And obviously the license doesn't say anything like that at all: it's a legal document, it can only state legally valid things!

I'll use the *exact* same examples as previously to show how Alexandre's reading of "all the rights that you have" can not possibly be correct:

(a) Again, Red Hat makes DVD's that contain GPLv2'd programs on them. Red Hat is bound by the GPL, so each work they put on the DVD is always under the GPL, and Red Hat *must* give you the rights that the GPL specifies.

But does Red Hat actually give you *all* the rights they hold on the DVD? No, they definitely do not. They hold a compilation copyright on RHEL, and they very much do *not* give you the right to copy the whole distribution and sell it as RHEL. You only get the rights to the individual pieces, not to the whole thing!

(b) Again, I make the Linux kernel available to you on a web site, and thus distribute it to you. Do I actually give you *all* the rights I have in it? Hell no. I cannot (and do not even want to). As an author, I have special rights in my code that you do not get. You get the rights spelled out in the GPLv2, and *nothing* more.

In other words, Alexandre's reading of the text in the preamble is *impossible*. It absolutely *cannot* be the way the license works. It's not how Red Hat itself reads it, and it's not how it can even legally be made to work even if somebody *wanted* to read it that way.

See? Both of Alexandre's arguments about why Tivo did something "against the license" were actually totally bogus. Neither of them was relevant, they both hinged on Alexandre reading the GPLv2 *wrong*.

Quoted 2 lines

Whether or not the GPLv3 is truely an acceptable answer to prevent Tivoisation is a completely different issue that I can't really judge.

Absolutely. I do think it prevents Tivoisation, but I personally think it's unacceptable in even *trying* to prevent it, and as I've tried to make clear, the GPLv2 definitely did *not* prevent Tivo from doing what they did.

Linus

#195 lore raw
Quoted 7 lines · Linus Torvalds
Quoted 3 lines · Michael Gerdau

I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Umm. It may well have been meant by *rms*. But your argument fatally falls down on the fact that rms has had *nothing* to do with the Linux kernel.

You're mixing two separate issues:

1- does GPLv3 change the spirit of the GPL?

2- is GPLv3 better than GPLv2 for Linux?

The answers may be different, and the reason I got into this debate was to set the record straight on 1. As the discussion evolved (if developing into a flamewar can be characterized as evolving ;-), I realized the motivations for preferring v2 over v3 were not clear to me (and they still appear contradictory to me), so I started investigating that, which is indeed 2., but is not about 3:

3- is Linux going to switch to v3?

Quoted 8 lines
Quoted 4 lines

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

Ehh. The intent that matters is not the intent of the person who authored the license, but the intent of the person who *chose* the license.

+1

Quoted 1 line

So clearly, the whole "modify in place" argument is simply *wrong*.

When you leave an essential portion of the reasoning out, which you repeatedly did, this conclusion is obvious. But it's also obviously wrong to try to apply this conclusion to the argument that I phrased.

Quoted 4 lines

It cannot *possibly* be a valid reading of the GPLv2! When the GPLv2 talks about "legal permissions to copy, distribute and/or modify" the software, it does *not* mean that you have to have the ability to modify it in place!

Isn't a restriction on in-place modification a further restriction on the permission to modify granted by the license? A further restriction that is not permitted by the license?

Again, this is not about ROM, CD-ROMs and other unmodifiable media. In this case, the distributor is not imposing this restriction, it's not selecting the media with the strict purpose of forbidding modification. It doesn't retain the ability to modify without failing to pass it on. This is the key distiction that you repeatedly dropped. And then, presented it as if it were a separate argument.

Quoted 3 lines

rights", but it is "all rights" ONLY AS FAR AS THE GPLv2 itself is concerned! It's not about any _other_ additional rights you may have outside the GPLv2!

I agree, and I don't think I've ever claimed otherwise. It's rights as far as the software is concerned, and even this might be pushing it a bit too far. That's why the spirit gives the intuition, but the legal terms are precise in turning that into "no further restrictions", as I'd already explained long before you did.

But then, again, the license grants the right to modify, and prohibits further restrictions to it, so I claim that saying "you can modify, just not in place, because I won't let you do it" (rather than because it's impossible), that's a further restriction of a freedom granted by the license, which turns into a license violation.

Now we can turn into the debate on whether replacing is modifying, and the conclusion is quite possibly that, in legal terms, it isn't. I don't care. I'm not here to debate the legal terms. I'm in this debate to set the record straight on whether GPLv3 changes the spirit of the GPL.

Quoted 2 lines

See? Both of Alexandre's arguments about why Tivo did something "against the license" were actually totally bogus.

Actually... What you name as two separate arguments were two parts of *one* of the 3 arguments I've raised so far.

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}
#196 lore raw
In reply to Linus Torvalds
Quoted 5 lines
Quoted 2 lines

I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Umm. It may well have been meant by *rms*. But your argument fatally falls down on the fact that rms has had *nothing* to do with the Linux kernel.

While I raised this argument on the Lunix kernel ML it was not meant to be valid specifically for it.

My observation in this thread is that almost everybody discusses different aspects of the same thing and everybody is somehow right. I was trying to "go back to start" and have the look at the overall picture which in this case for me is the question what the GPL's spirit is.

Whether and which of it _you_ intended to adopt for the kernel I had no intention to sencond guess.

Quoted 6 lines
Quoted 3 lines

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

Ehh. The intent that matters is not the intent of the person who authored the license, but the intent of the person who *chose* the license.

That seems to imply that we have to deal with myriads of intended meanings, namely those of all who contributed to the kernel.

I'm pretty sure I don't wish to walk that road. If you want to we'll have to agree to disagree.

Quoted 2 lines

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

I beg to differ. By adopting _his_ license you adopted his view. If you don't like that then choose a different license (which obviously you are free to do).

It's just not feaseable to have something like "my GPL means a different thing than your GPL".

Quoted 4 lines

But to make it even less relevant: intent really only legally matters when the legal issues are unclear.

And they really aren't that unclear here.

We have to agree to disagree then.

Quoted 8 lines
Quoted 3 lines

If one wishes to prevent it there are two related questions:
- does GPLv2 prevent it ?
- if GPLv2 does not prevent it then how can we change it to achieve that ?

Well, I think it's fairly unquestionable that the GPLv3 does prevent it.

So your second question isn't even really interesting. We know the answer. So the only question that is even remotely interesting is the first one.

My second question leaves out whether or not GPLv3 is an acceptable answer to my second question. While the FSF says it is it is by no means clear that I will agree -- all I wanted to do is present the situation as I see it.

Quoted 3 lines

Yes, I do agree with that reasoning, but there are *other*, and more direct, reasons than just the FSF's answer to say that the answer to your first question is "no".

Note I only said the FSF seems to say "no". I'm not yet sure I do.

Quoted 2 lines

The fact is, plain reading of the license (which *always* takes precedence over "intent", even in Europe) simply doesn't make what Tivo did illegal.

I disagree and I don't see that plain reading of the license is that obvious w/r to the SHA1 key because from a certain perspective said key is required to create a working modification which I'm entitled to under the GPLv2. I also agree that your perspective has merrit too. I'm simply not sure which of the above is "correct" (as in agreeable from a judge's PoV).

Based on that I disagree with your above stmt, at least I don't think your implication every other reading being outright wrong is false.

This thread IMO clearly shows that apparently it isn't that clear -- far too many intelligent people do disagree on this IMO not so obvious reading.

Quoted 2 lines

You literally have to read the GPLv2 in ways that are obviously not true to get to any other situation.

I object against the word obvious as an obsolute measure. You have all right to consider it obvious from your PoV. My PoV may differ and I strongly claim it being equally valid.

Quoted 2 lines

For example, Alexandre made the same two mistakes over and over in his reading when he tried to argue that the GPLv2 disallows what Tivo did:

I do not agree with everything Alexandre wrote but I do agree with some parts.

Quoted 1 line

(a) The right to modify means "modify in place"

[snip]

Quoted 1 line

So clearly, the whole "modify in place" argument is simply *wrong*.

I tend to agree and I didn't like it when it was brought up. But IMO that does not invalidate his position as such.

Quoted 2 lines

(b) The language in the preamble: "must give the recipients all the rights that you have" means really *all* the rights and abilities!

I always did imply a "within reason". To me that means "if it is simple for them to do it and can be simply extended to me as well then they have to extend it". Handing out a SHA1 key definitely is simple and thus IMO something I can expect them to do.

I'm aware we have to disagree on this. I'm also aware that this is subject to the (IMO implied right) to run the modified code on the original HW, mostly because they can do that very easily (which would be covered by "within reason").

BTW:
I can easily take the position that from a metaphysical PoV the whole concept of a copy is an illusion because every copy is in fact a modified new version (that happens to be rather similar from a certain PoV... but I disgress and don't really wish to walk that bridge :)

Quoted 4 lines

(a) Again, Red Hat makes DVD's that contain GPLv2'd programs on them. Red Hat is bound by the GPL, so each work they put on the DVD is always under the GPL, and Red Hat *must* give you the rights that the GPL specifies.

[snipped the paragraph on RH "withholding rights]

Here the "within reason" kicks in. And I readily admit that you are an able intellectual acrobat who can twist arguments such that they become silly.

My experience with german courts has shown me that the judges I had to deal with always and foremost did apply a reality check and did not try to bisect the consequences like an algorithm evaluated by a machine, i.e. the tried to decide what is right and wrong and not whether the letter of the contract could be twisted this or that way.

Quoted 6 lines

(b) Again, I make the Linux kernel available to you on a web site, and thus distribute it to you. Do I actually give you *all* the rights I have in it? Hell no. I cannot (and do not even want to). As an author, I have special rights in my code that you do not get. You get the rights spelled out in the GPLv2, and *nothing* more.

I probably haven't read all Alexandre wrote but from what I read I'd be surprised he'd disagree (I don't).

Quoted 5 lines

In other words, Alexandre's reading of the text in the preamble is *impossible*. It absolutely *cannot* be the way the license works. It's not how Red Hat itself reads it, and it's not how it can even legally be made to work even if somebody *wanted* to read it that way.

I don't know whether Alexandre does read to preamble to mean what you imply he does. But whether he does or not is irrelevant for me to decide that IMO there is a strong argument to claim that what TiVo did is illegal even under the GPLv2. Note I'm merely saying "strong argument" as opposed to "clear beyond doubt".

Quoted 7 lines
Quoted 2 lines

Whether or not the GPLv3 is truely an acceptable answer to prevent Tivoisation is a completely different issue that I can't really judge.

Absolutely. I do think it prevents Tivoisation, but I personally think it's unacceptable in even *trying* to prevent it, and as I've tried to make clear, the GPLv2 definitely did *not* prevent Tivo from doing what they did.

Well, I think trying to prevent it is totally acceptable, after all I'm free to impose whatever restrictions to my code I see fit (I think it was long ago agreed that the GPLv2 does impose restrictions as well; they are just different).

We have to agree to disagree on both whether trying to prevent Tivoisation is acceptable and whether GPLv2 already prevents it.

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
#197 lore raw
Quoted 4 lines · Michael Gerdau
Quoted 2 lines

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

I beg to differ. By adopting _his_ license you adopted his view. [...]

ianal, but fortunately that's not what the law is. The license says what it says, and that is what controls. The intent of the author (of Linus and other copyright holders) is a secondary source of information /if and only if/ any ambiguity of meaning arises (as determined by a judge, not by you or me). But the opinion and intent of RMS (unless adopted by Linus) is quite immaterial.

( there is a legalistic special-case. If any dispute arises over
what license the COPYING file in Linux itself (and only that file) is under, then the intent of RMS matters too, but only for that limited matter for that single file. Btw., the COPYING file itself is not licensed under the GPL. )

Ingo

#198 lore raw
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

I beg to differ. By adopting _his_ license you adopted his view. [...]

ianal, but fortunately that's not what the law is. The license says what it says, and that is what controls. The intent of the author (of Linus and other copyright holders) is a secondary source of information /if and only if/ any ambiguity of meaning arises (as determined by a judge, not by you or me). But the opinion and intent of RMS (unless adopted by Linus) is quite immaterial.

I agree with the "/if and only if/ any ambiguity of meaning arises" part. I'm sorry I didn't make that clear before.

However if that situation arises (i.e. the judge decides there is an ambiguity) then as far as my experience tells me it is the intention of the author (RMS et al in this case) that counts. But I erred before...

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
#199 lore raw
Quoted 12 lines · On Friday 15 June 2007 19:39:57 Michael Gerdau wrote:
Quoted 11 lines
Quoted 4 lines
Quoted 2 lines

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

I beg to differ. By adopting _his_ license you adopted his view. [...]

ianal, but fortunately that's not what the law is. The license says what it says, and that is what controls. The intent of the author (of Linus and other copyright holders) is a secondary source of information /if and only if/ any ambiguity of meaning arises (as determined by a judge, not by you or me). But the opinion and intent of RMS (unless adopted by Linus) is quite immaterial.

Quoted 6 lines

I agree with the "/if and only if/ any ambiguity of meaning arises" part. I'm sorry I didn't make that clear before.

However if that situation arises (i.e. the judge decides there is an ambiguity) then as far as my experience tells me it is the intention of the author (RMS et al in this case) that counts. But I erred before...

I doubt this. In a situation like that the intent of the licensor is what matter, not the intent of the original author of the license.

DRH

Quoted 2 lines

Best wishes,
Michael

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#200 lore raw
In reply to Michael Gerdau
Quoted 23 lines · On Friday 15 June 2007 18:06:11 Michael Gerdau wrote:
Quoted 6 lines
Quoted 2 lines

I find it obvious that the GPL was meant to prevent such to be possible. This is what I mean by the "the spirit of the GPL".

Umm. It may well have been meant by *rms*. But your argument fatally falls down on the fact that rms has had *nothing* to do with the Linux kernel.

While I raised this argument on the Lunix kernel ML it was not meant to be valid specifically for it.

My observation in this thread is that almost everybody discusses different aspects of the same thing and everybody is somehow right. I was trying to "go back to start" and have the look at the overall picture which in this case for me is the question what the GPL's spirit is.

Whether and which of it _you_ intended to adopt for the kernel I had no intention to sencond guess.

Quoted 5 lines
Quoted 4 lines

Living in germany I'm also used to the courts valueing the intention over the exact wording of a contract (a licence after all is a contract). So I _think_ in germany TiVo would have lost a lawsuit if they had tried it.

Quoted 8 lines
Quoted 2 lines

Ehh. The intent that matters is not the intent of the person who authored the license, but the intent of the person who *chose* the license.

That seems to imply that we have to deal with myriads of intended meanings, namely those of all who contributed to the kernel.

I'm pretty sure I don't wish to walk that road. If you want to we'll have to agree to disagree.

Each person that contributed code to the linux kernel *CAN* have their own interpretations of the GPLv2 as it *APPLIES* to their code. The interpretation that matters when talking about the kernel, a a whole, is Linus'.

Quoted 9 lines
Quoted 2 lines

What matters is *my* intent in *choosing* the GPLv2, not *his* intent in writing it.

I beg to differ. By adopting _his_ license you adopted his view. If you don't like that then choose a different license (which obviously you are free to do).

It's just not feaseable to have something like "my GPL means a different thing than your GPL".

Wrong. If I adopt the GPL it will be because of the *interpretation* I give it when reading it. And because *I* am the one then granting the license, it is *MY* interpretation that matters.

Quoted 33 lines
Quoted 4 lines

But to make it even less relevant: intent really only legally matters when the legal issues are unclear.

And they really aren't that unclear here.

We have to agree to disagree then.

Quoted 10 lines
Quoted 4 lines

If one wishes to prevent it there are two related questions:
- does GPLv2 prevent it ?
- if GPLv2 does not prevent it then how can we change it to achieve that ?

Well, I think it's fairly unquestionable that the GPLv3 does prevent it.

So your second question isn't even really interesting. We know the answer. So the only question that is even remotely interesting is the first one.

My second question leaves out whether or not GPLv3 is an acceptable answer to my second question. While the FSF says it is it is by no means clear that I will agree -- all I wanted to do is present the situation as I see it.

Quoted 3 lines

Yes, I do agree with that reasoning, but there are *other*, and more direct, reasons than just the FSF's answer to say that the answer to your first question is "no".

Note I only said the FSF seems to say "no". I'm not yet sure I do.

Quoted 3 lines

The fact is, plain reading of the license (which *always* takes precedence over "intent", even in Europe) simply doesn't make what Tivo did illegal.

Quoted 6 lines

I disagree and I don't see that plain reading of the license is that obvious w/r to the SHA1 key because from a certain perspective said key is required to create a working modification which I'm entitled to under the GPLv2. I also agree that your perspective has merrit too. I'm simply not sure which of the above is "correct" (as in agreeable from a judge's PoV).

A plain reading of the license doesn't entitle you to create a "working modification". See the disclaimers of warranty and guarantee - sections 11 and 12 of the GPLv2. They mean that the person *GRANTING* the license doesn't have to make sure that the program will be useful for your purposes, is modifiable to fit your purposes or will even *NOT* damage your hardware when it runs. "THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU."

In other words there is no guarantee in the GPLv2 that you will be able to create a working modification. The *ONLY* guarantee that exists, in regards to modification, is that you will be able to make a modification.

Quoted 5 lines

Based on that I disagree with your above stmt, at least I don't think your implication every other reading being outright wrong is false.

This thread IMO clearly shows that apparently it isn't that clear -- far too many intelligent people do disagree on this IMO not so obvious reading.

I agree that "too many intelligent people disagree". But this is just human nature. That people believe it says one thing when it doesn't is analogous to the *erroneous* belief that the world is flat.

Quoted 13 lines
Quoted 2 lines

You literally have to read the GPLv2 in ways that are obviously not true to get to any other situation.

I object against the word obvious as an obsolute measure. You have all right to consider it obvious from your PoV. My PoV may differ and I strongly claim it being equally valid.

Quoted 2 lines

For example, Alexandre made the same two mistakes over and over in his reading when he tried to argue that the GPLv2 disallows what Tivo did:

I do not agree with everything Alexandre wrote but I do agree with some parts.

Quoted 8 lines
Quoted 1 line

(a) The right to modify means "modify in place"

[snip]

Quoted 1 line

So clearly, the whole "modify in place" argument is simply *wrong*.

I tend to agree and I didn't like it when it was brought up. But IMO that does not invalidate his position as such.

But the "modify in place" argument is part of the reasoning behind the claim that the "anti-tivoization" language in GPL3 doesn't break spirit with GPL2.

Quoted 7 lines
Quoted 2 lines

(b) The language in the preamble: "must give the recipients all the rights that you have" means really *all* the rights and abilities!

I always did imply a "within reason". To me that means "if it is simple for them to do it and can be simply extended to me as well then they have to extend it". Handing out a SHA1 key definitely is simple and thus IMO something I can expect them to do.

But the "within reason" isn't there. That some people have inferred that term applies doesn't matter.

Quoted 10 lines

I'm aware we have to disagree on this. I'm also aware that this is subject to the (IMO implied right) to run the modified code on the original HW, mostly because they can do that very easily (which would be covered by "within reason").

BTW:
I can easily take the position that from a metaphysical PoV the whole concept of a copy is an illusion because every copy is in fact a modified new version (that happens to be rather similar from a certain PoV... but I disgress and don't really wish to walk that bridge :)

You know, I actually could agree to that "metaphysical" view.

Quoted 10 lines
Quoted 4 lines

(a) Again, Red Hat makes DVD's that contain GPLv2'd programs on them. Red Hat is bound by the GPL, so each work they put on the DVD is always under the GPL, and Red Hat *must* give you the rights that the GPL specifies.

[snipped the paragraph on RH "withholding rights]

Here the "within reason" kicks in. And I readily admit that you are an able intellectual acrobat who can twist arguments such that they become silly.

And here is where it becomes obvious that an inference is needed. *BUT* the argument was that the preamble, as written, states the intent of the license. Having to add an unwritten phrase invalidates the argument.

Quoted 5 lines

My experience with german courts has shown me that the judges I had to deal with always and foremost did apply a reality check and did not try to bisect the consequences like an algorithm evaluated by a machine, i.e. the tried to decide what is right and wrong and not whether the letter of the contract could be twisted this or that way.

This is the way it should be. However, the letter of the contract, in this case, is very clear and that hasn't stopped Herr Welte at all.

Quoted 9 lines
Quoted 6 lines

(b) Again, I make the Linux kernel available to you on a web site, and thus distribute it to you. Do I actually give you *all* the rights I have in it? Hell no. I cannot (and do not even want to). As an author, I have special rights in my code that you do not get. You get the rights spelled out in the GPLv2, and *nothing* more.

I probably haven't read all Alexandre wrote but from what I read I'd be surprised he'd disagree (I don't).

He doesn't. But the fact is that he has claimed that the "give you all the rights I have" is to be read literally. Hence Linus' above statement.

Quoted 20 lines
Quoted 5 lines

In other words, Alexandre's reading of the text in the preamble is *impossible*. It absolutely *cannot* be the way the license works. It's not how Red Hat itself reads it, and it's not how it can even legally be made to work even if somebody *wanted* to read it that way.

I don't know whether Alexandre does read to preamble to mean what you imply he does. But whether he does or not is irrelevant for me to decide that IMO there is a strong argument to claim that what TiVo did is illegal even under the GPLv2. Note I'm merely saying "strong argument" as opposed to "clear beyond doubt".

Quoted 7 lines
Quoted 2 lines

Whether or not the GPLv3 is truely an acceptable answer to prevent Tivoisation is a completely different issue that I can't really judge.

Absolutely. I do think it prevents Tivoisation, but I personally think it's unacceptable in even *trying* to prevent it, and as I've tried to make clear, the GPLv2 definitely did *not* prevent Tivo from doing what they did.

Quoted 7 lines

Well, I think trying to prevent it is totally acceptable, after all I'm free to impose whatever restrictions to my code I see fit (I think it was long ago agreed that the GPLv2 does impose restrictions as well; they are just different).

We have to agree to disagree on both whether trying to prevent Tivoisation is acceptable and whether GPLv2 already prevents it.

Agreed.

DRH

Quoted 2 lines

Best wishes,
Michael

Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
#201 lore raw
Quoted 9 lines · Daniel Hazelton
Quoted 6 lines

My experience with german courts has shown me that the judges I had to deal with always and foremost did apply a reality check and did not try to bisect the consequences like an algorithm evaluated by a machine, i.e. the tried to decide what is right and wrong and not whether the letter of the contract could be twisted this or that way.

This is the way it should be. However, the letter of the contract, in this case, is very clear and that hasn't stopped Herr Welte at all.

btw., still ianal, but the GPLv2 is not a "contract" but a "pure copyright license". A contract, almost by definition is a restriction of rights in exchange for consideration - while if you accept the license of a GPLv2-ed work this act only gives rights that you did not have before. Furthermore when you get source code of free software then there is no "meeting of minds" needed for you to accept the GPL's conditions, and only the letter of the license (and, in case of any ambiguities, the intent of the author of the code) matters to the interpretation of the license, not the intent of the recipient. (while in contract cases both the meeting of minds is needed and the intent and understanding of both parties matters to the interpretation of the contract.)

Ingo

#202 lore raw
Quoted 3 lines · Ingo Molnar

btw., still ianal, but the GPLv2 is not a "contract" but a "pure copyright license".

I've been told by several independent sources that it really doesn't matter.

The "pure license" argument was born largely for silly reasons: people claimed (a _loong_ time ago) that the GPL wasn't enforceable in the US because in order to be enforceable, something of value has to change hands (in the US, for example, it would be common to "sell" something for a nominal sum of $1 USD rather than to give it outright, to "seal the deal" and make it irrevocable).

That's generally considered a specious argument, apparently. In most jurisdictions in the US, a license and a contract are judged to be legally exactly the same thing, and if you don't follow the GPL and have no other contract to show for it, you're in violation of federal copyright law, so whether it is a license or a contract really doesn't matter.

So it's true: the GPL just gives you rights, and without it you have no rights (other than fair use ones etc), and blah blah. But the distinction between "license" vs "contract" really isn't a very important one in any case.

Quoted 7 lines

Furthermore when you get source code of free software then there is no "meeting of minds" needed for you to accept the GPL's conditions, and only the letter of the license (and, in case of any ambiguities, the intent of the author of the code) matters to the interpretation of the license, not the intent of the recipient. (while in contract cases both the meeting of minds is needed and the intent and understanding of both parties matters to the interpretation of the contract.)

I do agree that you can probably use this to say that the intent of the copyright has a stronger position, and that his "intent" thus matters more.

But I suspect that the "intent" angle is fairly weak legally to begin with, and if you cannot show that the intent was mutual, it's probably weaker still. So yeah, the intent of the copyright owner arguably might matter more, but quite frankly, I suspect everbody is better off not worrying so much about "intent", and worrying more about the "terms and conditions" part.

(I've said several times that intent _matters_, I just don't want people to think that it matters a whole lot).

What is pretty clear, though, is that the intent of a third party in the license/cotnract matters not at all. In the case of the kernel, the FSF being such a third party.

Linus

#203 lore raw
Quoted 4 lines · On Friday 15 June 2007 18:59:14 Linus Torvalds wrote:

So it's true: the GPL just gives you rights, and without it you have no rights (other than fair use ones etc), and blah blah. But the distinction between "license" vs "contract" really isn't a very important one in any case.

Er, copyright law is federal, contract law is generally state level? So not only does contract law vary a lot more by jurisdiction, but it's enforced by different courts than suits over copyright? (You'll notice the GPL doesn't say which state law holds sway. If it was a contract this would be kind of important.)

Also, in addition to the "exchange of value" bit there's "privity of contract" and "informed consent" when dealing with contract, which are cans of worms which can be avoided by Not Going There (tm)...

(These were largeish issues in the SCO vs Novell case, involving lots of motions in Utah detailed blow-by-blow on Groklaw...)

Rob

Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
#204 lore raw
Quoted 11 lines · On Friday 15 June 2007 18:59:14 Linus Torvalds wrote:
Quoted 4 lines

So it's true: the GPL just gives you rights, and without it you have no rights (other than fair use ones etc), and blah blah. But the distinction between "license" vs "contract" really isn't a very important one in any case.

Er, copyright law is federal, contract law is generally state level? So not only does contract law vary a lot more by jurisdiction, but it's enforced by different courts than suits over copyright? (You'll notice the GPL doesn't say which state law holds sway. If it was a contract this would be kind of important.)

That seems to be a special property of the US legal system. At least I'm not aware of this or a similar distinction in e.g. germany (or most parts of europe AFAIK).

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
#205 lore raw
In reply to Linus Torvalds
Quoted 13 lines · Linus Torvalds
Quoted 8 lines

Furthermore when you get source code of free software then there is no "meeting of minds" needed for you to accept the GPL's conditions, and only the letter of the license (and, in case of any ambiguities, the intent of the author of the code) matters to the interpretation of the license, not the intent of the recipient. (while in contract cases both the meeting of minds is needed and the intent and understanding of both parties matters to the interpretation of the contract.)

I do agree that you can probably use this to say that the intent of the copyright has a stronger position, and that his "intent" thus matters more.

Quoted 6 lines

But I suspect that the "intent" angle is fairly weak legally to begin with, and if you cannot show that the intent was mutual, it's probably weaker still. So yeah, the intent of the copyright owner arguably might matter more, but quite frankly, I suspect everbody is better off not worrying so much about "intent", and worrying more about the "terms and conditions" part.

yeah - and from everything i know about this subject the distinction between contract and license is small and more of a technicality - but still, it's a nice touch that the "pure license" argument that the FSF has advanced for a long time (and which it is now more silent about, given the GPLv3's not so pure structure) neatly defeats the common argument:

"but, but, when i received the Tivo with GPL-ed software on it the
GPLv2 was not intended to be like that, there is a right to run modified software on the hardware!"

Quoted 3 lines

What is pretty clear, though, is that the intent of a third party in the license/cotnract matters not at all. In the case of the kernel, the FSF being such a third party.

yeah. But the argument goes a bit further: people who chose to _license_ the kernel (by receiving a Tivo for example and downloading its kernel source) claim that _their_ interpretation of the GPL is that of the FSF's and that Tivo ought to follow it. The whole "Tivo is cheating the GPL deal with the end users" line of PR. As far as license interpretation goes there is _no end user deal_ and the 'end user' does not even play in terms of intent - only if she choses to be an active member of the community. That's why i think it's better to talk about a license than a contract. (even though legally, at least in the US, the two are quite close to each other.)

so a 'pure copyright license' stresses the point even more that you only really count in the ecosystem if you contribute in one way or another. The system should be and _is_ assymetric towards the actual black letter text of the license and, as a second layer, towards the intent of the people who actually produced this 1+ billion lines of code, documentation, bugzilla entries and other nice works. And that is a thing the FSF is missing sometimes i believe - the "listen to _all_ the people who enabled this cool stuff" part.

Ingo

#206 lore raw
In reply to Ingo Molnar
Quoted 11 lines · Daniel Hazelton
Quoted 10 lines
Quoted 7 lines

My experience with german courts has shown me that the judges I had to deal with always and foremost did apply a reality check and did not try to bisect the consequences like an algorithm evaluated by a machine, i.e. the tried to decide what is right and wrong and not whether the letter of the contract could be twisted this or that way.

This is the way it should be. However, the letter of the contract, in this case, is very clear and that hasn't stopped Herr Welte at all.

And this is the beauty of a multi-author project. Even if some authors think that the license permits something, if any of them understands it doesn't, he can try to enforce that WRT his own contributions. So those exploiting the gray areas of the license can still get caught.

Quoted 5 lines · Ingo Molnar

btw., still ianal, but the GPLv2 is not a "contract" but a "pure copyright license". A contract, almost by definition is a restriction of rights in exchange for consideration - while if you accept the license of a GPLv2-ed work this act only gives rights that you did not have before.

In Brazil, this is kind of contract/license is called a beneficial contract.

Quoted 5 lines

Furthermore when you get source code of free software then there is no "meeting of minds" needed for you to accept the GPL's conditions, and only the letter of the license (and, in case of any ambiguities, the intent of the author of the code) matters to the interpretation of the license, not the intent of the recipient.

That's correct, but with a catch: since the contract or license is chosen by the licensor, in case of ambiguity in the terms, many courts will interpret it in a way that privileges the licensee, regardless of the fact that copyright licenses are to be interpreted restrictively (at least in Brazilian law). And IANAL ;-)

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}
#207 lore raw
Quoted 7 lines · Alexandre Oliva
Quoted 1 line · Daniel Hazelton

That's correct, but with a catch: since the contract or license is chosen by the licensor, in case of ambiguity in the terms, many courts will interpret it in a way that privileges the licensee, regardless of the fact that copyright licenses are to be interpreted restrictively (at least in Brazilian law). And IANAL ;-)

---

Hmm. In such a suit, however, the user would not be "the licensee" and would not be a party to the suit - some author would be the plaintiff and would be suing someone for doing something in violation of the license that author granted - that is, the *defendant* would be the licensee who would get the benefit of the doubt...

scott

#208 lore raw
Quoted 8 lines · Scott Preece
Quoted 7 lines · Alexandre Oliva
Quoted 1 line · Daniel Hazelton

That's correct, but with a catch: since the contract or license is chosen by the licensor, in case of ambiguity in the terms, many courts will interpret it in a way that privileges the licensee, regardless of the fact that copyright licenses are to be interpreted restrictively (at least in Brazilian law). And IANAL ;-)

Quoted 7 lines

---

Hmm. In such a suit, however, the user would not be "the licensee" and would not be a party to the suit - some author would be the plaintiff and would be suing someone for doing something in violation of the license that author granted - that is, the *defendant* would be the licensee who would get the benefit of the doubt...

Yes. And so justice is made. Licensor gets to pick the license, licensee gets the benefit of the doubt. What's the 'however' about? Was this not obvious?

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}
#209 lore raw
Quoted 18 lines · Alexandre Oliva
Quoted 8 lines · Scott Preece
Quoted 7 lines · Alexandre Oliva
Quoted 1 line · Daniel Hazelton

That's correct, but with a catch: since the contract or license is chosen by the licensor, in case of ambiguity in the terms, many courts will interpret it in a way that privileges the licensee, regardless of the fact that copyright licenses are to be interpreted restrictively (at least in Brazilian law). And IANAL ;-)

Quoted 7 lines

---

Hmm. In such a suit, however, the user would not be "the licensee" and would not be a party to the suit - some author would be the plaintiff and would be suing someone for doing something in violation of the license that author granted - that is, the *defendant* would be the licensee who would get the benefit of the doubt...

Quoted 3 lines

Yes. And so justice is made. Licensor gets to pick the license, licensee gets the benefit of the doubt. What's the 'however' about? Was this not obvious?

---

Sorry - I thought you were saying ambiguity would be resolved in favor of the user. If you meant in favor of the licensee (regardless of that limiting the user's rights), then I agree.

scott

#210 lore raw
In reply to Michael Gerdau
Quoted 2 lines · Michael Gerdau

I beg to differ. By adopting _his_ license you adopted his view.

I'm sorry, but that's simply bullshit.

The GPLv2 does not state that you have to become a slave of rms and follow him in all things, and agree with him. Really. You must have read some other (perhaps unreleased early draft?) version.

The GPLv2 says what it says. Not what you (or rms) *wished* it says.

You don't enter into contracts and licenses based on wishes and intents. That's just not how it works.

Quoted 4 lines
Quoted 2 lines

(b) The language in the preamble: "must give the recipients all the rights that you have" means really *all* the rights and abilities!

I always did imply a "within reason".

Your view is not relevant. The fact that the "preamble" is not the "conditions" is what's relevant.

The preamble is explicitly stated to be *different* from the exact conditions. It's not the real "terms of copying". It's there to explain, it's not there to *be* the license.

It's explanatory, but the wording that actually *matters* is the "terms and conditions".

And the fact that *you* can mentally add words to it when you read the license (adding a "within reason") has absolutely no relevance what-so-ever.

Linus

#211 lore raw
In reply to Linus Torvalds
Quoted 6 lines · On Friday 15 June 2007 13:03:53 Linus Torvalds wrote:

But does Red Hat actually give you *all* the rights they hold on the DVD? No, they definitely do not. They hold a compilation copyright on RHEL, and they very much do *not* give you the right to copy the whole distribution and sell it as RHEL. You only get the rights to the individual pieces, not to the whole thing!

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...)

The five main areas of IP law as I understand them are copyright, patent, trademark, contract, and trade secret. Each of which is a different animal with a different legal foundation and different enabling legislation. The GPL is a copyright license with some language about patents. It is not based on contract law (although that's a common misperception that Lawrence Lessig and Eben Moglen have spent some effort debunking), and doesn't even mention trademarks.

So Red Hat isn't saying "you can use some of our copyrights but not others", last I heard all of their copyrights are licensed GPLv2 as a matter of corporate policy. What you can't use is their trademarked name or logo, because they are explicitly refusing to license the trademarks to third parties.

And under GPLv2, this is allowed.

Rob

Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
#212 lore raw
Quoted 4 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.

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.

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!

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.

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. Exactly because open-source vendors usually don't want to look nasty by limiting the compilation, when they can't really limit the individual parts anyway.

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).

Linus