Please release a stable kernel Linux 3.0
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines · Alan Cox
Quoted 5 lines · On Fri, 29 Jun 2007 00:00:27 +0200 Rene Herman <[email protected]> wrote:
Quoted 1 line · Alan Cox
Public domain is GPL compatible.
Would you happen to have an opinion on the attached? I don't so much need it
The answer is "NO!!!!"
Public domain also means "I don't have to give you the source". If its merged with the kernel the resulting work is GPL anyway
Quoted 8 lines
Quoted 2 lines
Stating that code which one intends to be in the public domain has "GPL and additional rights" is a bit of a travesty though.
Indeed if its public domain you may have almost no rights at all depending what you were given. Once you get the source code you can do stuff but I don't have to give you that. If its public domain I can find security holes in it, and refuse to provide the fixed module in source form even.
The GPL forces nobody to not release his module under PD, therefore it can't protect you from that. Even minor changes - like adjusting the module to use to the current API - won't change that, at least in Germany they'd have to qualify as a work of their own in order to create a GPL-only derived work, because anything not qualifying for that could also be integrated into the PD version, and both would remain identical.
Signature · 4 lines
"Cluster bombing from B-52s is very, very accurate. The bombs are guaranteed to always hit the ground." -U.S.A.F. Ammo Troop Friß, Spammer: [email protected] [email protected]
Quoted 8 lines · Bodo Eggert
Quoted 5 lines · Alan Cox
Indeed if its public domain you may have almost no rights at all depending what you were given. Once you get the source code you can do stuff but I don't have to give you that. If its public domain I can find security holes in it, and refuse to provide the fixed module in source form even.
Quoted 6 lines
The GPL forces nobody to not release his module under PD, therefore it can't protect you from that. Even minor changes - like adjusting the module to use to the current API - won't change that, at least in Germany they'd have to qualify as a work of their own in order to create a GPL-only derived work, because anything not qualifying for that could also be integrated into the PD version, and both would remain identical.
What I focussed on when asking were only my wishes as an author but Alan (if I understood him right ofcourse) pointed out that _the kernel_ does not want integrated code to be in the public domain regardless of my wishes.
Arguably (no doubt, sigh...) someone could distribute the kernel in binary form but refuse to provide source for the bits marked as being in the public domain alongside it -- yes, can of worms when compared to GPL demands, but I believe I can see why one shouldn't even go near there.
Rene.
Quoted 15 lines · On Friday 29 June 2007 17:27:34 Rene Herman wrote:
Quoted 7 lines · Bodo Eggert
Quoted 5 lines · Alan Cox
Indeed if its public domain you may have almost no rights at all depending what you were given. Once you get the source code you can do stuff but I don't have to give you that. If its public domain I can find security holes in it, and refuse to provide the fixed module in source form even.
Quoted 6 lines
The GPL forces nobody to not release his module under PD, therefore it can't protect you from that. Even minor changes - like adjusting the module to use to the current API - won't change that, at least in Germany they'd have to qualify as a work of their own in order to create a GPL-only derived work, because anything not qualifying for that could also be integrated into the PD version, and both would remain identical.
Quoted 8 lines
What I focussed on when asking were only my wishes as an author but Alan (if I understood him right ofcourse) pointed out that
_thekernel_does not want integrated code to be in the public domain regardless of my wishes.Arguably (no doubt, sigh...) someone could distribute the kernel in binary form but refuse to provide source for the bits marked as being in the public domain alongside it -- yes, can of worms when compared to GPL demands, but I believe I can see why one shouldn't even go near there.
Actually, they couldn't. Second PD code became included in the kernel it would be covered by the GPL. If it can be shown that the kernel binary was the product of merging PD code in, then there is no way top refuse access to the PD code.
DRH
Quoted 7 lines
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 1 line
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Quoted 8 lines · Daniel Hazelton
Quoted 5 lines · On Friday 29 June 2007 17:27:34 Rene Herman wrote:
Arguably (no doubt, sigh...) someone could distribute the kernel in binary form but refuse to provide source for the bits marked as being in the public domain alongside it -- yes, can of worms when compared to GPL demands, but I believe I can see why one shouldn't even go near there.
Quoted 4 lines
Actually, they couldn't. Second PD code became included in the kernel it would be covered by the GPL. If it can be shown that the kernel binary was the product of merging PD code in, then there is no way top refuse access to the PD code.
If indeed. If the PD code compiles to a standalone module then this becomes every bit as arguable as binary modules. That's the "(no doubt, sigh)" bit.
Rene.