Here's the deal. The whole Linksys GPL flap started because Linksys was NOT releasing their drivers for Linux. Those of us with wireless cards containing the Broadcom 4301 chipset were told to f-off and that Linksys would NEVER offer a driver for our chip. Because of this, I started "The Linux Broadcom 4301 Driver Project" (http://linux-bcom4301.sourceforge.com). It was a member of our project who exposed Linksys' use of GPL initially. Companies profiting from GPL, as Linksys clearly is, must be willing to "give back" -- that is the whole purpose of GPL.
First let me preface this by saying I am a Linux user, and a huge fan of Linux. However, I can also say, without a doubt, that UN*X hackers over the years have almost certainly copied code from the old Unix/Sys V codebase into Linux. These people know who they are, and once SCO reveals which source is in violation, they will be revealed (there are CVS logs, ya know). I would encourage these people to step forward now and help diffuse the situtation. If everyone who lifted code (possibly believing it was "open") came forward, the community could exercise this code in a number of weeks. Let's fix the problem before the issue ever makes it into court.
Slashdot Mirror
Here's the deal. The whole Linksys GPL flap started because Linksys was NOT releasing their drivers for Linux. Those of us with wireless cards containing the Broadcom 4301 chipset were told to f-off and that Linksys would NEVER offer a driver for our chip. Because of this, I started "The Linux Broadcom 4301 Driver Project" (http://linux-bcom4301.sourceforge.com). It was a member of our project who exposed Linksys' use of GPL initially. Companies profiting from GPL, as Linksys clearly is, must be willing to "give back" -- that is the whole purpose of GPL.
First let me preface this by saying I am a Linux user, and a huge fan of Linux. However, I can also say, without a doubt, that UN*X hackers over the years have almost certainly copied code from the old Unix/Sys V codebase into Linux. These people know who they are, and once SCO reveals which source is in violation, they will be revealed (there are CVS logs, ya know). I would encourage these people to step forward now and help diffuse the situtation. If everyone who lifted code (possibly believing it was "open") came forward, the community could exercise this code in a number of weeks. Let's fix the problem before the issue ever makes it into court.