non-free firmware in kernel modules, aggregation and unclear copyright notice.
Quoted 4 lines · Theodore Ts'o
You know, the fact that Red Hat, SuSE, Ubuntu, and pretty much all other commercial distributions have not been worried about getting sued for this alleged GPL'ed violation makes it a lot harder for me (and others, I'm sure) take Debian's concerns seriously.
I said in other e-mail, and I will repeat: it's not their (Debian's) fault. Their responsibility is greater. Why? Because when RedHat puts something it shouldn't in their distro it's *their* assets that will answer for some copyright violation damages. In Debian's case, it's the assets of: some DDs, the mirror network, derived-distro distributors, CD vendors, etc... This is just a case of Debian being "fiscally responsible", i.e., not treating other people's money as trash.
Quoted 18 lines
The problem may be that because Debian is purely a non-profit, and so it can't clearly balance the costs and benefits of trying trying to avoid every single possible risks where someone might decide to file a lawsuit. Anytime you do *anything* you risk the possibility of a lawsuit, and if you allow the laywers to take over your business decisions, the natural avoid-risks-all-costs bias of lawyers are such that it will either drive a company out of business, or drive a non-profit distribution into irrelevance.....
If Debian wants to be this fanatical, then let those Debian developers who care do all of the work to make this happen, and stop bothering LKML. And if it continues to remain the case that a user will have to manually edit
/etc/apt/sources.lists(using vi!) to include a reference to non-free in order to install Debian on a system that requires the tg3 device driver, then I will have to tell users who ask me that they would be better off using some other distribution which actually cares about their needs.
Quoted 1 line
- Ted
In this I agree with you, and Greg KH was singing approximately the same tune, if I understood correctly: this is a matter to be resolved by distributors and, if someone solves this in a practical and good way, it will eventually end in the pristine-blessed-Linus-kernel-tree, to the benefit of others.
But, the question made here was a subtler one and you are all biting around the bush: there *are* some misrepresentations of licenses to the firmware blobs in the kernel (-- ok, *if* you consider that hex dumps are not source code). What Sven asked was: "Hey, can I state explicitly the distribution state in the source files, by means of adding some comments?".
Maybe he should contact each file's maintainer individually, but it seems (IMHO) that he thought "hey, they all hang around lkml anyway"...
I think even a clarification "this firmware hexdump is considered to be the source code, and it's GPL'd" would do, but I must put my asbestos suit everytime I say it. :-)
HTH,
Massa
Quoted 3 lines · Humberto Massa
But, the question made here was a subtler one and you are all biting around the bush: there *are* some misrepresentations of licenses to the firmware blobs in the kernel (-- ok, *if* you consider that hex dumps are not source code). What Sven asked was: "Hey, can I state explicitly the distribution state in the source files, by means of adding some comments?".
I think even a clarification "this firmware hexdump is considered to be the source code, and it's GPL'd" would do, but I must put my asbestos suit everytime I say it. :-)
We do not add comments to the kernel source code which simply state the obvious.
Jeff
Quoted 7 lines · Humberto Massa
Quoted 4 lines · Theodore Ts'o
You know, the fact that Red Hat, SuSE, Ubuntu, and pretty much all other commercial distributions have not been worried about getting sued for this alleged GPL'ed violation makes it a lot harder for me (and others, I'm sure) take Debian's concerns seriously.
Quoted 7 lines
I said in other e-mail, and I will repeat: it's not their (Debian's) fault. Their responsibility is greater. Why? Because when RedHat puts something it shouldn't in their distro it's *their* assets that will answer for some copyright violation damages. In Debian's case, it's the assets of: some DDs, the mirror network, derived-distro distributors, CD vendors, etc... This is just a case of Debian being "fiscally responsible", i.e., not treating other people's money as trash.
This is where you are wrong, and i believe this is caused because you don't understand how debian works on this.
The ftp-master are the ones reviewing the licencing problems, and they are the ones handling the infrastructure, and putting their responsability on the stake. If they feel that some piece of software has dubious legal issues which come at a risk of having them personally come on the receiving end of a legal case, then they will say, no, we don't distribute this software, and that is the end of it.
The other point is that other entities, like redhat, or suse (which is now novel and thus ibm) and so have stronger backbones, and can more easily muster the ressources to fight of a legal case, even one which is a dubious one, especially given the particularities of the US judicial system, where it is less important to be right, and more important to have lot of money to throw at your legal machine. Debian has nothing such, and SPI which would stand for this, is not really upto it either, so in this case, apart from all ideology and fanatism, it is for purely pragmatic reasons that they don't distribute undistributable files from the non-free part of our archive. You would do the same in their case.
Also, you have to ask yourself what the above mentioned companies where to do if they where to be made aware of the issue, and ask their lawyers to attend this. Also you have to consider the case of some of those companies ending in the arms of a legally predative company and pulling another SCO at us.
Friendly,
Sven Luther
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Humberto Massa
But, the question made here was a subtler one and you are all biting around the bush: there *are* some misrepresentations of licenses to the firmware blobs in the kernel (-- ok, *if* you consider that hex dumps are not source code). What Sven asked was: "Hey, can I state explicitly the distribution state in the source files, by means of adding some comments?".
Quoted 6 lines
Quoted 3 lines
I think even a clarification "this firmware hexdump is considered to be the source code, and it's GPL'd" would do, but I must put my asbestos suit everytime I say it. :-)
We do not add comments to the kernel source code which simply state the obvious.
The only thing here is that it has to be obvious not only to you, but to the judge too :)
In this case, it is not comments, but proper copyright attribution, which was added in the tg3.c case since the first checkin :
/*
* tg3.c: Broadcom Tigon3 ethernet driver.
*
* Copyright (C) 2001, 2002, 2003, 2004 David S. Miller ([email protected])
* Copyright (C) 2001, 2002, 2003 Jeff Garzik ([email protected])
* Copyright (C) 2004 Sun Microsystems Inc.
*
* Firmware is:
* Copyright (C) 2000-2003 Broadcom Corporation.
*/
The firmware part was not present in the original checkin you did in 2002. Adding something about the licencing status of it would be enough.
Or even adding some comment in the toplevel COPYING file saying that firmware blobs come under their own licence or something such, and then listing all the firmware blobs and their licencing condition in a separate toplevel file would be enough.
Friendly,
Sven Luther
Quoted 19 lines · Sven Luther
Quoted 7 lines · Humberto Massa
Quoted 4 lines · Theodore Ts'o
You know, the fact that Red Hat, SuSE, Ubuntu, and pretty much all other commercial distributions have not been worried about getting sued for this alleged GPL'ed violation makes it a lot harder for me (and others, I'm sure) take Debian's concerns seriously.
Quoted 8 lines
I said in other e-mail, and I will repeat: it's not their (Debian's) fault. Their responsibility is greater. Why? Because when RedHat puts something it shouldn't in their distro it's *their* assets that will answer for some copyright violation damages. In Debian's case, it's the assets of: some DDs, the mirror network, derived-distro distributors, CD vendors, etc... This is just a case of Debian being "fiscally responsible", i.e., not treating other people's money as trash.
Quoted 2 lines
This is where you are wrong, and i believe this is caused because you don't understand how debian works on this.
I was not commenting on Debian works; I was commenting on civil and criminal liabilities. If Debian, knowingly or not, distributes a copyrights-infringing work, the work's package(s) maintainer(s) are civil and criminally liable, and so are: CD distributors where said work is distributed in the CD, derived-distro distributors, and the mirror network members. Why? Because they are all distributing infringing works.
Let me explain how this works. In 1999, the police went into a videostore in the city where I worked as a paralegal in the DA's office. There were a lot of pirated VHS tapes there (without the "not pirated" holographic seal that our MPAA-equivalent gives to the members to glue on their tapes/DVDs). The guy from the videostore did not make the copies, but he distributed (renting is a form of distribution, yes) the infringing works, so... unless he proves that he had all the good reasons to think that the works he bought were non-infringing (for instance, if they all had seals like the "official" one, undistinguishable by the naked eye), he is liable for the infringement. And so, the guy got some years of jailtime, plus some hefty fines.
Quoted 6 lines
The ftp-master are the ones reviewing the licencing problems, and they are the ones handling the infrastructure, and putting their responsability on the stake. If they feel that some piece of software has dubious legal issues which come at a risk of having them personally come on the receiving end of a legal case, then they will say, no, we don't distribute this software, and that is the end of it.
This is not the only thing that is at stake, as I demonstrated / illustrated by my anecdote above. But yes, probably ftp-master guys are liable, too.
Quoted 12 lines
The other point is that other entities, like redhat, or suse (which is now novel and thus ibm) and so have stronger backbones, and can more easily muster the ressources to fight of a legal case, even one which is a dubious one, especially given the particularities of the US judicial system, where it is less important to be right, and more important to have lot of money to throw at your legal machine. Debian has nothing such, and SPI which would stand for this, is not really upto it either, so in this case, apart from all ideology and fanatism, it is for purely pragmatic reasons that they don't distribute undistributable files from the non-free part of our archive. You would do the same in their case.
Quoted 5 lines
Also, you have to ask yourself what the above mentioned companies where to do if they where to be made aware of the issue, and ask their lawyers to attend this. Also you have to consider the case of some of those companies ending in the arms of a legally predative company and pulling another SCO at us.
Yes and yes. But their lawyers have an option Debian does not, also:
they can negotiate ($$$) an exclusive license to redistribute. As in:
"Novell can redistribute this work in their Linux distro, at will". This would not be DFSG-free.
Quoted 4 lines
Friendly,
Sven Luther
Friendly, HTH,
Massa
Quoted 50 lines · Sven Luther
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Humberto Massa
But, the question made here was a subtler one and you are all biting around the bush: there *are* some misrepresentations of licenses to the firmware blobs in the kernel (-- ok, *if* you consider that hex dumps are not source code). What Sven asked was: "Hey, can I state explicitly the distribution state in the source files, by means of adding some comments?".
Quoted 6 lines
Quoted 3 lines
I think even a clarification "this firmware hexdump is considered to be the source code, and it's GPL'd" would do, but I must put my asbestos suit everytime I say it. :-)
We do not add comments to the kernel source code which simply state the obvious.
The only thing here is that it has to be obvious not only to you, but to the judge too :)
In this case, it is not comments, but proper copyright attribution, which was added in the
tg3.ccase since the first checkin :/*
*tg3.c: Broadcom Tigon3 ethernet driver.
*
* Copyright (C) 2001, 2002, 2003, 2004 David S. Miller ([email protected])
* Copyright (C) 2001, 2002, 2003 Jeff Garzik ([email protected])
* Copyright (C) 2004 Sun Microsystems Inc.
*
* Firmware is:
* Copyright (C) 2000-2003 Broadcom Corporation.
*/The firmware part was not present in the original checkin you did in 2002. Adding something about the licencing status of it would be enough.
Or even adding some comment in the toplevel COPYING file saying that firmware blobs come under their own licence or something such, and then listing all the firmware blobs and their licencing condition in a separate toplevel file would be enough.
Friendly,
Sven Luther
-
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/
Quoted 4 lines · Sven Luther
...
The other point is that other entities, like redhat, or suse (which is now novel and thus ibm) and so have stronger backbones, and can more easily muster the ressources to fight of a legal case, even one which is a dubious one,
Quoted 8 lines
especially given the particularities of the US judicial system, where it is less important to be right, and more important to have lot of money to throw at your legal machine. Debian has nothing such, and SPI which would stand for this, is not really upto it either, so in this case, apart from all ideology and fanatism, it is for purely pragmatic reasons that they don't distribute undistributable files from the non-free part of our archive. You would do the same in their case.
...
There are many possible legal risks for a Linux distribution.
This thread is about one.
Another one is that RedHat removed MP3 support in their distribution from programs like xmms ages ago because of the legal risks due to patents. The Debian distribution still contains software that is capable of playing MP3's.
I'd say of the two above cases, the MP3 patents are far more likely to cause a lawsuit.
YMMV.
If your statement was true that Debian must take more care regarding legal risks than commercial distributions, can you explain why Debian exposes the legal risks of distributing software capable of decoding MP3's to all of it's mirrors?
Quoted 3 lines
Friendly,
Sven Luther
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 26 lines · Adrian Bunk
Quoted 4 lines · Sven Luther
...
The other point is that other entities, like redhat, or suse (which is now novel and thus ibm) and so have stronger backbones, and can more easily muster the ressources to fight of a legal case, even one which is a dubious one,Quoted 8 lines
especially given the particularities of the US judicial system, where it is less important to be right, and more important to have lot of money to throw at your legal machine. Debian has nothing such, and SPI which would stand for this, is not really upto it either, so in this case, apart from all ideology and fanatism, it is for purely pragmatic reasons that they don't distribute undistributable files from the non-free part of our archive. You would do the same in their case.
...There are many possible legal risks for a Linux distribution.
This thread is about one.
Another one is that RedHat removed MP3 support in their distribution from programs like xmms ages ago because of the legal risks due to patents. The Debian distribution still contains software that is capable of playing MP3's.
Quoted 4 lines
I'd say of the two above cases, the MP3 patents are far more likely to cause a lawsuit.
YMMV.
Yes, possibly, especially in these troubled times.
Quoted 4 lines
If your statement was true that Debian must take more care regarding legal risks than commercial distributions, can you explain why Debian exposes the legal risks of distributing software capable of decoding MP3's to all of it's mirrors?
I don't know and don't really care. I don't maintain any mp3 player (err, actually i do, i package quark, but use it mostly to play .oggs, maybe i should think twice about this now that you made me aware of it), but in any case, i am part of the debian kernel maintainer team, and as such have a responsability to get those packages uploaded and past the screening of the ftp-masters. I believe the planned solution is vastly superior to the current one of simply removing said firmware blobs from the drivers, which caused more harm than helped, which is why we are set to clarifying this for the post-sarge kernels.
That said, i was under the understanding that after the SCO disaster, clarification of licencing issues and copyright attributions was a welcome thing here, but maybe i misunderstood those whole issues.
Friendly,
Sven Luther
Quoted 7 lines · Sven Luther
On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
...Quoted 4 lines
If your statement was true that Debian must take more care regarding legal risks than commercial distributions, can you explain why Debian exposes the legal risks of distributing software capable of decoding MP3's to all of it's mirrors?
Quoted 9 lines
I don't know and don't really care. I don't maintain any mp3 player (err, actually i do, i package quark, but use it mostly to play .oggs, maybe i should think twice about this now that you made me aware of it), but in any case, i am part of the debian kernel maintainer team, and as such have a responsability to get those packages uploaded and past the screening of the ftp-masters. I believe the planned solution is vastly superior to the current one of simply removing said firmware blobs from the drivers, which caused more harm than helped, which is why we are set to clarifying this for the post-sarge kernels.
Debian doesn't seem to care much about the possible legal problems of patents.
The firmware issues are an urgent real problem?
Debian should define how much legal risk they are willing to impose on their mirrors and distributors and should act accordingly in all areas.
But ignoring some areas while being more religious than RMS in other areas is simply silly.
Quoted 3 lines
That said, i was under the understanding that after the SCO disaster, clarification of licencing issues and copyright attributions was a welcome thing here, but maybe i misunderstood those whole issues.
"SCO disaster"?
It is a disaster for SCO.
Quoted 3 lines
Friendly,
Sven Luther
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 19 lines · Adrian Bunk
Quoted 7 lines · Sven Luther
On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
...Quoted 4 lines
If your statement was true that Debian must take more care regarding legal risks than commercial distributions, can you explain why Debian exposes the legal risks of distributing software capable of decoding MP3's to all of it's mirrors?
Quoted 9 lines
I don't know and don't really care. I don't maintain any mp3 player (err, actually i do, i package quark, but use it mostly to play .oggs, maybe i should think twice about this now that you made me aware of it), but in any case, i am part of the debian kernel maintainer team, and as such have a responsability to get those packages uploaded and past the screening of the ftp-masters. I believe the planned solution is vastly superior to the current one of simply removing said firmware blobs from the drivers, which caused more harm than helped, which is why we are set to clarifying this for the post-sarge kernels.
Quoted 2 lines
Debian doesn't seem to care much about the possible legal problems of patents.
patents are problematic, and upto recently there where no software patents in europe, so i don't really care. I am not sure about the details of the above problem you mention, could you provide me some link to the problem at hand. I also believe that in the larger scheme restriction of this kind, as is the US restriction on distribution to cuba and everything else, is not-right and even immoral, and *I* personally would fight back if i was ever sued for such things, and there may be higher courts involved than just the US judicial system, which is for sale anyway, where redhat is dependent on. I cannot talk about the whole of debian on this though, and i feel it is for someone else to tackle and handle. If you feel strongly about this, you are free to go take it over with whoever handles this, post to debian-legal and debian-project about it, and help get the issue solved.
(/me believes such restrictions of the above are a violation of the elemental human rights to go where one wants and run what operating system on wants).
Quoted 1 line
The firmware issues are an urgent real problem?
It is a problem that concerns me and the debian kernel team, thus we are out to fix it. If you have a problem at hand, even if it is not as important as others, would you sit back and not do anything just because others didn't solve other problems ?
Quoted 2 lines
Debian should define how much legal risk they are willing to impose on their mirrors and distributors and should act accordingly in all areas.
That is for the ftp-masters to decide, i am not in best speaking term with them, so you are free to go ask the question directly.
Quoted 2 lines
But ignoring some areas while being more religious than RMS in other areas is simply silly.
Come on, i am just asking for a damn explicit declaration that the firmware is not something covered by the GPL, and that we should have explicit distribution licence for it. We all agree that these are not covered by the GPL for various reasons, so why not have the copyright holder state it explicitly ? I don't see how do you jump to "more religious than RMS" from that, given that my analysis making the firmware aggregate works are a wee bit different from what they explicitly write in their GPL FAQ.
Quoted 7 lines
Quoted 3 lines
That said, i was under the understanding that after the SCO disaster, clarification of licencing issues and copyright attributions was a welcome thing here, but maybe i misunderstood those whole issues.
"SCO disaster"?
It is a disaster for SCO.
Now, yes. but we did strengthen our admission of patches policy for more tracability, didn't we, and there where companies who paid SCO for fear of retribution, and they where project who post-poned their linux adoptions, and what not. If nothing else, be it only for all the time we all lost following that story over the past tree years.
Friendly,
Sven Luther
Quoted 20 lines · Sven Luther
Quoted 19 lines · Adrian Bunk
Quoted 16 lines · Sven Luther
On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
...Quoted 4 lines
If your statement was true that Debian must take more care regarding legal risks than commercial distributions, can you explain why Debian exposes the legal risks of distributing software capable of decoding MP3's to all of it's mirrors?
I don't know and don't really care. I don't maintain any mp3 player (err, actually i do, i package quark, but use it mostly to play .oggs, maybe i should think twice about this now that you made me aware of it), but in any case, i am part of the debian kernel maintainer team, and as such have a responsability to get those packages uploaded and past the screening of the ftp-masters. I believe the planned solution is vastly superior to the current one of simply removing said firmware blobs from the drivers, which caused more harm than helped, which is why we are set to clarifying this for the post-sarge kernels.
Quoted 6 lines
Quoted 2 lines
Debian doesn't seem to care much about the possible legal problems of patents.
patents are problematic, and upto recently there where no software patents in europe, so i don't really care. I am not sure about the details of the above problem you mention, could you provide me some link to the problem at hand. I
The patent problems in the USA alone should impose enough legal risks. IANAL, but even RedHat considers them to be serious problems.
And note that most of their patents are also valid in the EU. If they are enforcible is a different question, but it might be enough to become a legal risk that a lawsuit might be started against e.g. a mirror.
Quoted 5 lines
also believe that in the larger scheme restriction of this kind, as is the US restriction on distribution to cuba and everything else, is not-right and even immoral, and *I* personally would fight back if i was ever sued for such things, and there may be higher courts involved than just the US judicial system, which is for sale anyway, where redhat is dependent on. I cannot talk
Which court is "higher ... than just the US judicial system"?
If you are in the USA, there's no legal instance between the US supreme court and god.
Quoted 8 lines
about the whole of debian on this though, and i feel it is for someone else to tackle and handle. If you feel strongly about this, you are free to go take it over with whoever handles this, post to debian-legal and debian-project about it, and help get the issue solved.
(/me believes such restrictions of the above are a violation of the elemental human rights to go where one wants and run what operating system on wants).
...
Unfortunately, life isn't fair.
It's Debian's choice how cautiously or brave they are regarding legal risks. But it has to be consistent.
Debian simply needs an overall policy for this.
But if you say that you want to avoid any legal risks in one area while saying "these are not my packages" about perhaps even more likely legal risks in other areas doesn't help anyone.
Quoted 3 lines
Friendly,
Sven Luther
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