By the way: what large bodies of code? You say we've gained access to large bodies of code: What?
Show me the code? Other than the original Linksys code drop circa 2003 which predated the SFLC?
By the way, as a result of that original lawsuit, Linksys ceased all in-house Linux development, replaced Linux with another embedded OS on most of their routers, and outsourced the maintenance of their old Linux stuff to Taiwan.
Five years later, Linksys (now owned by Cisco) started up its in-house Linux development again, hired _me_ as a consultant to help make sure they were properly compliant and doing good things with the community. In addition to publishing all source before the actual product shipped, I was advising them to do things like order their WRT610n serial adapters in bulk and put up a web page where hobbyists could order them, create and release OpenOCD jtag profiles for their hardware, and so on.
That's right before the SFLC hooked up with the FSF, and went back and sued Linksys (now owned by Cisco) AGAIN over the same 5-year-old code as in the original lawsuits (this time over a gcc 3.3 compiler they got from Broadcom, which produced bog-standard unmodified mips output, just like the current ones do; there was NOTHING to be gained from this code-wise. Also, Cisco never recieved the source to that compiler in the first place, but of course the SFLC didn't sue broadcom, they sued Cisco).
The result was that Cisco terminated the Linksys division, reassigned the developers to work on Windows, ended all in-house Linux development, and outsourced the maintenance-only level again (this time to Red hat I think), and started looking at non-linux embedded OSes for future products again.
THIS is why I'm trying to stop busybox from being used as a bludgeon against the world at large. The SFLC sued an awful lot of companies that never got source from their upstream vendor, and COULDN'T do so five years later (and a lot of cases were pretty old since they were grinding through the "hall of shame" backlog), but the SFLC never once sued that upstream vendor (generally some taiwanese company that half-assed a board support package for the hardware they shipped). Instead the SFLC went after the local companies for enough money to sue the _next_ one, and when we did get code drops they were obsolete worthless things with nothing we didn't already have. (Generally some random SVN snapshot, or a release version with a couple backports from source control. The "local modifications" were debug printfs, commented out lines, and the occasional hardwired global variable from people who didn't know how to use the config system properly.)
So tell me: where's all this great code we got out of the lawsuits? In the entire time the SFLC or Conservancy have had the right to sue people over BusyBox, where is ONE LINE OF CODE it resulted in? I honestly want to know, because I can't name any, and I WAS A PLAINTIFF!
no subject
Show me the code? Other than the original Linksys code drop circa 2003 which predated the SFLC?
By the way, as a result of that original lawsuit, Linksys ceased all in-house Linux development, replaced Linux with another embedded OS on most of their routers, and outsourced the maintenance of their old Linux stuff to Taiwan.
Five years later, Linksys (now owned by Cisco) started up its in-house Linux development again, hired _me_ as a consultant to help make sure they were properly compliant and doing good things with the community. In addition to publishing all source before the actual product shipped, I was advising them to do things like order their WRT610n serial adapters in bulk and put up a web page where hobbyists could order them, create and release OpenOCD jtag profiles for their hardware, and so on.
That's right before the SFLC hooked up with the FSF, and went back and sued Linksys (now owned by Cisco) AGAIN over the same 5-year-old code as in the original lawsuits (this time over a gcc 3.3 compiler they got from Broadcom, which produced bog-standard unmodified mips output, just like the current ones do; there was NOTHING to be gained from this code-wise. Also, Cisco never recieved the source to that compiler in the first place, but of course the SFLC didn't sue broadcom, they sued Cisco).
The result was that Cisco terminated the Linksys division, reassigned the developers to work on Windows, ended all in-house Linux development, and outsourced the maintenance-only level again (this time to Red hat I think), and started looking at non-linux embedded OSes for future products again.
THIS is why I'm trying to stop busybox from being used as a bludgeon against the world at large. The SFLC sued an awful lot of companies that never got source from their upstream vendor, and COULDN'T do so five years later (and a lot of cases were pretty old since they were grinding through the "hall of shame" backlog), but the SFLC never once sued that upstream vendor (generally some taiwanese company that half-assed a board support package for the hardware they shipped). Instead the SFLC went after the local companies for enough money to sue the _next_ one, and when we did get code drops they were obsolete worthless things with nothing we didn't already have. (Generally some random SVN snapshot, or a release version with a couple backports from source control. The "local modifications" were debug printfs, commented out lines, and the occasional hardwired global variable from people who didn't know how to use the config system properly.)
So tell me: where's all this great code we got out of the lawsuits? In the entire time the SFLC or Conservancy have had the right to sue people over BusyBox, where is ONE LINE OF CODE it resulted in? I honestly want to know, because I can't name any, and I WAS A PLAINTIFF!