Slashdot Mirror


FSF Files Suit Against Cisco For GPL Violations

Brett Smith writes "This morning the Free Software Foundation filed suit against Cisco for violations of the GPL and LGPL. There's a blog post with background about the case. The full complaint is available too." The short version, as excerpted by reader byolinux, is that "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

409 comments

  1. This is why copyright laws are bad by Throtex · · Score: 5, Funny

    They allow abusive entities such as the Free Software Foundation to go after Cisco. If only the software was distributed without cumbersome GLP and LGPL licensing restrictions, and was truly free like software wants to be, then Cisco wouldn't have been forced to violate the licenses.

    For shame.

    1. Re:This is why copyright laws are bad by jalet · · Score: 3, Funny

      Are you joking ?

      --
      Votez ecolo : Chiez dans l'urne !
    2. Re:This is why copyright laws are bad by Throtex · · Score: 5, Informative

      Yes.

    3. Re:This is why copyright laws are bad by tripdizzle · · Score: 1

      I almost snapped when I missed the sarcasm.

      --
      "A claim for equality of material position can be met only by a government with totalitarian powers." Hayek
    4. Re:This is why copyright laws are bad by mrsteveman1 · · Score: 4, Funny

      Dammit, if you had kept that going longer than 3 minutes i would have had some entertainment for the afternoon

    5. Re:This is why copyright laws are bad by Amazing+Quantum+Man · · Score: 1

      OK. This story's threads are officially over. Nobody can top that one, it's the best tongue-in-cheek post I've seen on Slashdot.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    6. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0, Insightful

      Though there is an element of truth to it. I'd argue that BSD and the like are more "free" then GPL.

    7. Re:This is why copyright laws are bad by calmofthestorm · · Score: 4, Funny

      I agree, copyright law is stifling innovation by preventing large American corporations from using the work of small, independent inventors without contributing in kind. Clearly there should be a fee to copyright works, to ensure that only properly-licensed corporations, using licensed, trusted compilers, can produce them.

      I'm Ted Stevens, convicted felon, and I approved this message*!

      * California v. Drew Disclaimer: No I'm not.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    8. Re:This is why copyright laws are bad by LtGordon · · Score: 3, Funny

      Replied Cisco, "Curse you, Stallman!"

    9. Re:This is why copyright laws are bad by LarsG · · Score: 5, Insightful

      BSD and the like are more "free" for the developer / manufacturer while GPL is more "free" for the user / recipient of the software.

      Which license that is more free depends on whose freedom one is concerned about.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    10. Re:This is why copyright laws are bad by 0xdeadbeef · · Score: 1

      How "free" is your iPhone?

    11. Re:This is why copyright laws are bad by jalet · · Score: 1, Troll

      Ouch ! This hurts !!!

      Thanks for the laugh, then.

      --
      Votez ecolo : Chiez dans l'urne !
    12. Re:This is why copyright laws are bad by Amazing+Quantum+Man · · Score: 5, Funny

      Replied Cisco, "Curse you, Stallman!"

      Actually, their exact words were, "Curse you, Stallman! We'd have gotten away with it, too; if it wasn't for you meddling kids!"

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    13. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      Sorry, I tried to make it very sarcastic :)

    14. Re:This is why copyright laws are bad by QuantumRiff · · Score: 1

      More free than your Tivo!

      --

      What are we going to do tonight Brain?
    15. Re:This is why copyright laws are bad by Hal_Porter · · Score: 5, Funny

      How "free" is your iPhone?

      Free as in stolen.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    16. Re:This is why copyright laws are bad by geminidomino · · Score: 0, Flamebait

      BSD and the like are more "free" for the developer / manufacturer while GPL is more "free" for the user / recipient of the software.

      Which license that is more free depends on whose freedom one is concerned about.

      Neither is more "free" for the user. Both are distribution licenses and don't cover use. If the recipient wants to change and distribute the source code, he is a developer. Point: BSD-like.

    17. Re:This is why copyright laws are bad by jellomizer · · Score: 3, Funny

      All the customers of their product will also need to pay an extra 25% of the cost because they need to add redoing the wheel software development. Before Linksys started to use the GNU tools Hubs even small ones were expensive. After Linksys incorporated GNU you can for relatively cheap get a Router, Switch and Firewall which is good enough for most people and small businesses. If you choose GNU as a developer you really forfeit a lot of your rights to your code. So if a big corporation takes your code and uses it on a loophole in the licence, you don't have much recourse.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    18. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 4, Insightful

      Wrong.

      The BSD licence allows a developer to incorporate code into a proprietary project which may very well NOT be free (in any sense of the word) to use and which may well be under a licence (EULA) that very much covers use.

      This is not to say that the BSD licence is flawed in any way, BTW: just that you're wrong and that the stated difference between the GPL and BSD licences is correct.

    19. Re:This is why copyright laws are bad by mcgrew · · Score: 2, Funny

      We woosh that the RIAA would offer music under the GPL!

    20. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 5, Funny

      That's what she said!

      Oh...uhhh, nevermind.

    21. Re:This is why copyright laws are bad by calmofthestorm · · Score: 4, Funny

      I suppose you're right. It's especially important that Cisco use quality, trusted software developed in-house or offshore, rather than trusting the danger-fraught open source community. Even aside from patent violations and other blatant disregard of others' IP rights, and the far lower quality of code produced by enthusiastic volunteers as compared to paid, apathetic employees, can you really trust that these self-described "hackers" haven't put in backdoors for their Russian friends? There's just no way to know with open source, and given all this, and studies showing that open source has an astronomically higher total cost of ownership, this is probably the last straw.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    22. Re:This is why copyright laws are bad by Dogtanian · · Score: 0

      Though there is an element of truth to it. I'd argue that BSD and the like are more "free" then GPL.

      Oh no, not another bloody massive "BSD is more free than the GPL" "Oh not it isn't" "Oh yes it is" subthread where people restate the same established arguments for their respective sides.

      No, you're not the first person to make this observation. We've heard it all before- again and again and again and... :/

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    23. Re:This is why copyright laws are bad by calmofthestorm · · Score: 5, Insightful

      The way I see it, the free software community is just another company. We use each other's work, just like members of a company usually can, provided we agree on the ground rules. We work for communal benefit.

      So let me ask you: If I get access to the windows source code via a contract (copyright) with Microsoft, should I be able to take Microsoft's work and sell it for personal profit? This is of course absurd. I see it as equally absurd that other companies should be able to take the open source community's work for free. They get the binaries and sources under a contract, they can follow it or their rights terminate.

      A better example: Someone wrote a library that does something I want, and will license it to me for like $5 per copy for use in my software. Does this give me the right to take it for free (assuming I can) because I don't want to raise my product's prices to cover the increased cost? No. I can either accept their terms or not.

      Of course I also don't buy all this omfg "free software good, bad software bad" crap. We're a company that works for its own interest, plain and simple. Just one that produces products far more to my liking, far more intuitive to my (granted, odd) mind, and far more useful in my line of work (CS research)

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    24. Re:This is why copyright laws are bad by Jah-Wren+Ryel · · Score: 1

      Neither is more "free" for the user. Both are distribution licenses and don't cover use.

      Both licenses use copyright's restriction on distribution to enforce specific terms. GPL requires distribution of usable source to the user. BSD does not. Since you can't use what you don't have, GPL clearly guarantees more freedom to the end user than BSD.

      --
      When information is power, privacy is freedom.
    25. Re:This is why copyright laws are bad by Hatta · · Score: 1, Insightful

      If I'm a developer and I receive a binary I want to modify, which helps me more? The BSD license or GPL? Under the BSD license there may be no way for me to get the code and make the necessary modifications. Under the GPL, I am entitled to the code. Point: GPL.

      --
      Give me Classic Slashdot or give me death!
    26. Re:This is why copyright laws are bad by jsalbre · · Score: 1

      :...and that dog."

    27. Re:This is why copyright laws are bad by profplump · · Score: 2, Insightful

      I know you're joking, but you could just as easily say that copyright law is stifling innovation by preventing small, independent inventors from using the work of large American corporations without contributing in kind -- the law works both ways.

    28. Re:This is why copyright laws are bad by profplump · · Score: 1

      I'd be surprised if any hub Linksys ever sold contained a copy of any GNU tool in such a fashion that it would require distribution of the source.

      Routers, firewalls, sure. Maybe even switches. But if you've got a modified glibc on your hub you're doing it wrong. Hub prices fell because the requisite hardware got cheaper, not because they used free tools.

    29. Re:This is why copyright laws are bad by hansamurai · · Score: 2, Funny

      Stallman's beard?

    30. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      So if someone chooses to not use the BSD for his code, that makes code licensed with BSD less free?

    31. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      How is this informative?

    32. Re:This is why copyright laws are bad by bigstrat2003 · · Score: 2, Interesting

      Isn't this rather misleading, considering that if you can't get at the source, the project isn't under the BSD license? It doesn't make the BSD license less free if a derivative is not BSD-licensed, it reflects on the license of the derivative. Furthermore, the original BSD-licensed code will always be available once it's been given up to the public (barring the project dying out altogether, which can just as easily happen to a GPL project).

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    33. Re:This is why copyright laws are bad by riceboy50 · · Score: 1

      I also don't buy all this..."bad software bad" crap

      What else can bad software be except bad?

      --
      ~ I am logged on, therefore I am.
    34. Re:This is why copyright laws are bad by dkleinsc · · Score: 2, Funny

      That sounds like it ought to be an exclamation, along the lines of "Stallman's beard! I wasn't expecting that error."

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    35. Re:This is why copyright laws are bad by tonyray · · Score: 1

      Actually, there used to be, in 1981, a $5 fee to copyright software. Also, you had to send the Copyright Office a complete copy of your source code. That was back in the days I was writing games for Apple II's and Atari 800's. As programs got longer, they started requiring only the first 50 pages and the last page.

    36. Re:This is why copyright laws are bad by Bert64 · · Score: 1

      But a BSD project can move towards a closed source fork, with the original BSD licensed code dying out... If the closed source version ends up more widely used and incompatible, then having the original version isn't terribly useful.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    37. Re:This is why copyright laws are bad by init100 · · Score: 1

      As programs got longer, they started requiring only the first 50 pages and the last page.

      If your program consists of multiple source files, which ones contain the first 50 pages and which one contains the last page?

    38. Re:This is why copyright laws are bad by SEE · · Score: 4, Interesting

      Oh, my.

      Imagine, for a moment, that various $BIG_COMPANIES decide they want to be able to use code from free software in their products without a fuss, while still keeping protection for their own code.

      So, what they do is approach various national governments, WIPO, etc., and have copyright protection removed from source code.

      The companies then sit back with the fact that their binary code is still copyright protected, and their source code is safely hidden under "trade secret" protections . . . but the source code of free software is neither copyrighted nor secret. So the companies can take the known, non-copyrighted source code from free software, and combine it with their secret source code to make their copyrighted binary blobs . . .

    39. Re:This is why copyright laws are bad by Larryish · · Score: 1

      That's what she said!

      Oh... uhhh, nevermind.

    40. Re:This is why copyright laws are bad by thtrgremlin · · Score: 1

      "Liberty is the right to scream theater in a crowded fire". BSD is the NICE GPL, but when it comes down to reality and what people want from their 'free' software, you need to be specific, and you need to fight for it. The best example from both sides is MacOSX. Is MacOSX FreeBSD? NO, actually, hell no. It is BASED on FreeBSD, but many of the things that made FreeBSD great are dead IMO. If you want to write "free and forget about it" code, BSD is great so long as you can comfortably never care what happens to it. If you write code to be part of a community, but selfishly want to keep it free the way you want to keep it free for "everyone or no one", then you want GPL. There had once been more controversy over "the more free license". BSD is more free to do ANYTHING, but GPL is more free to stay free. Personally, I like the direction things have gone. I would like to see a stronger community of BSD developers, but who wants to work for gratis. Libre has the selfish intrinsic rewards devs need to earn their time... again, in my somewhat limited observation.

      Honestly, this is not flame bait, but I compare in my mind, BSD is free like giving the government the freedom to take all your rights away. Do you want a free government, or an oppressed one. GPL is the regime of oppression :) and proud of it!

      --
      Want Big Business out of government? Take away the incentive and start by getting government out of big business!
    41. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      damn corporate pirates.
      yaaarrh me shareholders

    42. Re:This is why copyright laws are bad by BrainInAJar · · Score: 1

      It actually makes you less free, since the modifications you write have to be under the GPL. More free licenses like the mozilla/apache style allow you to both receive the code, but don't force you as a developer to choose a license you may not agree with as a condition of linking against it.

      The problem isn't the GPL makes you share the GPL'ed code, that's pretty acceptable; The problem is the GPL makes you share your code too, and not any way you'd like either: your only option is to GPL your code too.

      There's a reason FreeBSD has ZFS and not any code from Linux and that's because to even make a module out of Linux code, all of FreeBSD would have to go GPL. Sun's CDDL doesn't make them relicense the whole project. Meanwhile if a closed source OS used ZFS they still have to share the code in question and any modifications on request

    43. Re:This is why copyright laws are bad by Ihmhi · · Score: 1

      Sweet merciful crap, don't give them ideas!

    44. Re:This is why copyright laws are bad by jc42 · · Score: 2, Informative

      I see it as equally absurd that other companies should be able to take the open source community's work for free. They get the binaries and sources under a contract, they can follow it or their rights terminate.

      Actually, this is where you got it wrong. You don't get a contract to use GPL'd code; you get a license. Ask your friendly local corporate lawyer to explain the difference.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    45. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      "...and was truly free like software wants to be..."

      Software is alive now? Dear dear... when was the last time you saw sunlight?

    46. Re:This is why copyright laws are bad by mysidia · · Score: 1

      The BSD license requires the BSD license's list of conditions and a disclaimer to be included for redistributions.

      So just like the GPL, the redistributed code must be redistributed under the same list of conditions.

      HOWEVER, with code licensed under a BSD license, the binary form can be distributed, and there is no obligation to distribute source.

      A key difference, since the GPL requires distribution of source code.

    47. Re:This is why copyright laws are bad by andy_t_roo · · Score: 1

      someone quite clearly needed to be informed about the first post joke.

    48. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      thank you.

      btw your music sucks.

    49. Re:This is why copyright laws are bad by jellomizer · · Score: 0, Troll

      So let me ask you: If I get access to the windows source code via a contract (copyright) with Microsoft, should I be able to take Microsoft's work and sell it for personal profit? This is of course absurd. I see it as equally absurd that other companies should be able to take the open source community's work for free. They get the binaries and sources under a contract, they can follow it or their rights terminate.

      How is it absurd to purchase Microsoft's work and sell it for profit. People do it all the time. That is the point of licensing software from a company. Apple did it they licensed Microsoft Exchanges protocol to incorporate it into the iPhone. No you probably wont get away with making your version of windows with just a recompile... (However similar things have been done in the past).

      A better example: Someone wrote a library that does something I want, and will license it to me for like $5 per copy for use in my software. Does this give me the right to take it for free (assuming I can) because I don't want to raise my product's prices to cover the increased cost? No. I can either accept their terms or not.

      Yes but the terms are usually quite clear. You buy it do what you want with it. With the GNU there are these hooks Sure you can use it but you need to release your source as well. This is where the problem is and the main confusion by Cisco. They may have made a mistake and Put GPL Code with their code. Now there is the problem of what happens if you can't release your code as GPL. Breaking other peoples contracts in the process. Even if you go back and Get rid of the GPL there will still be systems with the GPL still running.

      Of course I also don't buy all this omfg "free software good, bad software bad" crap. We're a company that works for its own interest, plain and simple. Just one that produces products far more to my liking, far more intuitive to my (granted, odd) mind, and far more useful in my line of work (CS research)

      Well my main point was to show that aggressive attempts to push full GPL compliance (even if it was in the FSF rights to do so) has consequences. FSF has this paranoid view of Corporations and when they treat them as evil companies the companies will be naturally defensive. If FSF wins then a company on the defensive will not take a financial hit but pass the cost to the consumers. (Ok fine you got what you want now you all have to pay for it)

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    50. Re:This is why copyright laws are bad by HermMunster · · Score: 1

      I believe the distribution of the binaries is enough to require distribution of the source.

      --
      You can lead a man with reason but you can't make him think.
    51. Re:This is why copyright laws are bad by sumdumass · · Score: 1

      Well, there is bad as in "Bad dog, do your business outside". Then there is bad and in "wow, those previews were bad, I can't wait to see the movie."

      Then again, there is the bad usage of the word bad as in am acronym for Better Ask Dave or Big Ass Dick.

      I suggest you take your pick and run with it.

    52. Re:This is why copyright laws are bad by PincusJr · · Score: 0

      There is some truth in what you're saying... This is from the Free Software song: When we have enough free software At our call, hackers, at our call, We'll throw out those dirty licenses Even Stallman recognises them as being bad, or "dirty".

    53. Re:This is why copyright laws are bad by JackieBrown · · Score: 1

      Everyone knows that one source file is enough for anyone.

      That's what goto is for :)

    54. Re:This is why copyright laws are bad by Anonymous Coward · · Score: 0

      But then, you can disassemble/reverse engineer the binary blob using an automatic tool and redistribute it as no longer protected "source code", right? Such "source code" may lack readability, but $BIG_COMPANIES could not restrict its distribution...

    55. Re:This is why copyright laws are bad by SEE · · Score: 1

      Your source code created by disassembly itself isn't covered by copyright . . . but it's easy to make sure the law declares that it's a derivative of a copyrighted work, and so distribution violates copyright.

      It's not the sort of thing I can see easily getting passed, because its aim is too obvious. But it flows from the general idea that copyleft is just as dependent as copyright on the law recognizing the rights of creators to control their works.

    56. Re:This is why copyright laws are bad by SharpFang · · Score: 1

      Horrible?
      Scary?
      Annoying?

      Of course "bad software is bad" deserves -1, Informative.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    57. Re:This is why copyright laws are bad by berbo · · Score: 1
      I agree: corporate software is just inherently safer. Especially when it comes with DRM.

      - this message brought to you by your friends as Sony.

    58. Re:This is why copyright laws are bad by calmofthestorm · · Score: 1

      Not exactly a troll in my opinion. Essentially I'm having trouble understanding your position. Do you believe that companies have the right to protect their IP but individuals and nonprofits like the FSF don't? The GPL is quite clear (if you're a lawyer, and unlike EULAs and the individual, corporations surely have lawyers to review their licenses) about what is required, just like their other contracts.

      Your point that releasing their source would cause them to violate other agreements is invalid, so they should be released from it. This is equivalent to saying that since the other agreements require them not to distribute the source, and this conflicts with the GPL, they should be exempt from those other agreements.

      Why should a corporate license involving monetary exchange be any different than licenses exchanging nonmonetary things of value* (a promise to release source). Do you think that corporate licenses don't also have "hooks" that make you do this or that or include an advertising clause or whatnot?

      So I ask: do you believe that corporate licenses have more rights than individual/nonprofit ones? Or do you believe that a promise to release code is an invalid condition in a contract? Or perhaps the GPL isn't clear? Aside from those, I can't really see where you're basing your arguments.

      Also if all they want to include is glibc or whatnot, they can just release the source to that, it's not an all or nothing thing, free and proprietary software can mix on a system (aggregation) under the LGPL, which most base GNU/Linux libraries are. And the kernel explicitly states that systems running it need NOT have all their software released under the GPL, as a clarification in a grey area.

      * See Jacobsen v. Katzer, the document I link to from the still-in-progress case makes it extremely clear that nonmonetary promises of sharing alike are valid terms for the purpose of a license/contract.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    59. Re:This is why copyright laws are bad by Erikderzweite · · Score: 1

      Hmm... Then some code is leaked, recompiled with another compiler and brought to public domain. It works both ways, I think.

    60. Re:This is why copyright laws are bad by Amazing+Quantum+Man · · Score: 1

      By Stallman's Beard! I'm going to have to start using that phrase!

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    61. Re:This is why copyright laws are bad by garaged · · Score: 1

      GPL forces people to be kind in return, BSD is Ok with you even if you take the code a close a derivated.

      Which one is more free is a philosofical question

      --
      I'm positive, don't belive me look at my karma
    62. Re:This is why copyright laws are bad by badkarmadayaccount · · Score: 1

      ..friendly lawyer...

      LOLs. You, sir owe me a new keyboard.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    63. Re:This is why copyright laws are bad by geminidomino · · Score: 1

      But a BSD project can move towards a closed source fork, with the original BSD licensed code dying out...

      So can GPLed code. The copyright holder of the code can set whatever license he wants. If he doesn't accept any patches, or insists on copyright control over any he accepts, then he can change the license however he likes, leading to the same end.

    64. Re:This is why copyright laws are bad by Tubal-Cain · · Score: 1

      Some of the Windows 2000 source code was leaked a while back.

  2. The thing about these lawsuits by Anonymous Coward · · Score: 0

    The thing about these lawsuits is that I hope the FSF tried to resolve the violations outside of court before litigating. Remember: court is supposed to be a last resort, not first recourse.

    1. Re:The thing about these lawsuits by Paradise+Pete · · Score: 5, Informative

      The thing about these lawsuits is that I hope the FSF tried to resolve the violations outside of court before litigating.

      If only there were some way to find out. It's hard to say for sure, but based on this:

      As we always do in violation cases, we began a process of working with Cisco to help them understand their obligations under our licenses, and how they could come into compliance. Early on it seemed likely that we could resolve the issues without any fuss.

      I'm thinking maybe they did.

    2. Re:The thing about these lawsuits by aardvarkjoe · · Score: 4, Informative

      The thing about these lawsuits is that I hope the FSF tried to resolve the violations outside of court before litigating. Remember: court is supposed to be a last resort, not first recourse.

      According to the blog post linked in the summary, the FSF has been working with Cisco since 2003 to resolve the issue of GPL compliance, and has received only halfhearted attempts on their part to come into compliance. We're only seeing the FSF's side of the story here, of course, but assuming that they're telling it like it is, the FSF tried many other avenues before deciding to file the lawsuit.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    3. Re:The thing about these lawsuits by Wonko+the+Sane · · Score: 1

      "We began working with Cisco in 2003 to help them establish a process for complying with our software licenses, and the initial changes were very promising," explained Brett Smith, licensing compliance engineer at the FSF. "Unfortunately, they never put in the effort that was necessary to finish the process, and now five years later we have still not seen a plan for compliance. As a result, we believe that legal action is the best way to restore the rights we grant to all users of our software."

    4. Re:The thing about these lawsuits by calmofthestorm · · Score: 1

      I seem to recall that the FSF generally sues for costs + compliance, not damages. If so, going to court is a silly way to get what you want as anything but a last resort.

      I know this is what gplviolations does.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    5. Re:The thing about these lawsuits by mrsteveman1 · · Score: 2, Funny

      You are an enabler, you enable people to avoid RTFA :D

    6. Re:The thing about these lawsuits by Anonymous Coward · · Score: 5, Informative

      Yes, usually it is just costs + compliance.

      But this time, they seem to be pissed (from the stuff they filled with the court, the URI is in the press release):

      "Prayer to Relief"
      [...]
                (2) That the Court order Defendant to pay Plaintiff's actual and consequential damages in-curred, in an amount to be determined at trial or, in the alternative, statutory damages as set forth in 17 U.S.C. 504(c);
                (3) That the Court order Defendant to account for and disgorge to Plaintiff all profits derived by Defendant from its unlawful acts;
      [...]

      In other words: OUCH!

    7. Re:The thing about these lawsuits by alain94040 · · Score: 1

      According to the FSF blog: "Cisco also provides written offers for source, but we regularly hear about requests going unfulfilled."

      I hope the entire case won't revolve around whether Joe failed to click on the proper button to download the source code. It looks like Cisco has some way to pretend they are in compliance.

      It would be bad if the case was lost by the FSF on such technicality, since the headlines would just say "GPL lost in court". Anyway, any decision is probably years away, if it even goes that far.
      --
      alain - fairsoftware.net

    8. Re:The thing about these lawsuits by BeeRockxs · · Score: 1

      Have you even tried to RTFA? None of what you say is true.

    9. Re:The thing about these lawsuits by Anonymous Coward · · Score: 0

      I seem to recall that the FSF generally sues for costs + compliance, not damages. If so, going to court is a silly way to get what you want as anything but a last resort.

      I know this is what gplviolations does.

      If you look at the text of the lawsuit, they ask for
      "all profits derived by Defendant from its unlawful acts"

      They want the money.

    10. Re:The thing about these lawsuits by hmar · · Score: 2, Funny

      "You are an enabler, you enable people to avoid RTFA :D" For which we thank you

    11. Re:The thing about these lawsuits by Sancho · · Score: 1

      If you're willing to settle for less than you initially asked for, it tends to look good. I don't think that the FSF wants or expects to get what they've officially requested.

    12. Re:The thing about these lawsuits by BlargIAmDead · · Score: 4, Funny

      (3) That the Court order Defendant to account for and disgorge to Plaintiff all profits derived by Defendant from its unlawful acts; [...]

      So am I the only one who thinks disgorge is an awesomely awkward word. All I can see is something like "2 Routers 1 Port!"

    13. Re:The thing about these lawsuits by AVee · · Score: 1

      "You are an enabler, you enable people to avoid RTFA :D" For which we thank you

      Because the articles, this one is no exception, would provide the same and more information using far less text. Actually reading the article is a highly inefficient way of wasting time. It's over before you know it, which obviously not the point of wasting time.

      If we wanted quick, condensed, reliable information we won't reading slashdot. And yes, this comment could have been just as pointless with far less text.

    14. Re:The thing about these lawsuits by Darby · · Score: 1

      Really? Because I thought that Stallman really did have lawyers nesting in his beard!

      Don't listen to that guy. It's true.

    15. Re:The thing about these lawsuits by AVee · · Score: 1
      They did, but they did that in their very own fsf way. From the blog post:

      We asked them to notify customers about previous violations and inform them about how they can now obtain complete source code; they have refused to do this, along with the other reasonable demands we have made to consider this case settled.

      I'm not 100% sure how what to read into this, but it sounds like they expected Cisco to contact each owner of a violating Linksys device. That's just totally impossible, these are consumer devices, there is no way Cisco is going to find out where they ended up. The only way to reach a reasonable percentage of these customers would be a big worldwide 'We, Cisco, are copyright violating bastards' advertising campain. I can understand how they would not like that idea either. And if they other demands where just a 'reasonable' I can understand why there was no settelment.

      Still, it seems they kept violating the GPL even after it was explained to them several times. That would mean they knowingly violated the GPL, which perfectly warrents a lawsuit. After 5 years of talking there is no such thing as an honest mistake anymore.

    16. Re:The thing about these lawsuits by innocent_white_lamb · · Score: 1

      "We are suspending you over disgorge. Pray we do not lose our grip."

      --
      If you're a zombie and you know it, bite your friend!
    17. Re:The thing about these lawsuits by eldepeche · · Score: 1

      It wouldn't be too hard to publish that information on their website and send a letter to everyone who registered their hardware to that effect. I think that would have satisfied the FSF to the point where there wouldn't have been a lawsuit.

    18. Re:The thing about these lawsuits by badkarmadayaccount · · Score: 1

      That's a very fucked up perception about circular routing...

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  3. I am conflicted. by cobaltnova · · Score: 1

    When (or if) the FSF wins this suit, it will almost certainly be a boon for custom firmware development for these devices. Like the WRT5GL, I'd expect the new router firmwares to make the router much more useful.

    How should I proceed? Should I buy these (forcibly) open-sourced devices? Or should I avoid Linksys because of their repeated violations of the GPL?

    1. Re:I am conflicted. by Anonymous Coward · · Score: 0

      Can't you answer that yourself?

    2. Re:I am conflicted. by immortalpob · · Score: 3, Insightful

      By the time this lawsuit has gotten though the legal system you will have forgotten why you bought the router and/or it will have died... proceed with the boycott

    3. Re:I am conflicted. by pipatron · · Score: 5, Interesting

      Don't buy a linksys, but do buy one of the ones with similar hardware.

      When I bought my Asus WL-500g Premium it shipped with the complete modified linux source in a folder on the CD that contained the usual windows-crapware you seem to get with every product these days (you know, the outdated copy of acrobat reader, some documentation wrapped in a shiny executable and such).

      I did install OpenWRT on it, and I'm very happy with the result. I'm also happy with Asus for actually shipping the source, but I never did write them a line and told them. Maybe I should.

      --
      c++; /* this makes c bigger but returns the old value */
    4. Re:I am conflicted. by Ma8thew · · Score: 1

      Buy Buffalo. I have this router. It came with DD-WRT preinstalled, so it was a cinch to install Tomato over that. It's been solid as a rock, and, due to its excellent traffic shaping, I can barely tell when a torrent is downloading, when before, other traffic would slow to a crawl during peak hours.

  4. Be patient... by Benanov · · Score: 1

    I'd wait until the dust settles, to be honest--but if you want a recommendation for the interim, here's one:

    Don't buy out-of-compliance devices. Boycott Cisco until they fix this problem, either by settling the case and releasing code...or until the trial is complete.

    1. Re:Be patient... by mrsteveman1 · · Score: 1

      At least on the 54g series, they aren't even using Linux anymore except the GL device, so their "fix" has been to just avoid Linux in that situation, though i'm sure there were other reasons as well.

    2. Re:Be patient... by Anonymous Coward · · Score: 0

      Linux firmware is bigger than VxWorks one. When Linksys cut off memory and flash, they had to go VxWorks.

    3. Re:Be patient... by rufus+t+firefly · · Score: 1

      Linux firmware is bigger than VxWorks one. When Linksys cut off memory and flash, they had to go VxWorks.

      I can't honestly believe that it costs that much extra for 8MB of flash compared to 2MB of flash. You can run DD-WRT on there, but it requires jumping through some hoops first. Plus, it makes it more difficult to install any optware packages, etc.

      --
      "He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
    4. Re:Be patient... by mrchaotica · · Score: 3, Interesting

      The really weird thing is that the WRT54G, with Linux, cost $50 years ago. The new WRT54G, with less hardware, cost -- guess what -- $50 today! Or, alternatively, the WRT54GL costs more than $50. Isn't hardware supposed to get cheaper and better over time, rather than worse or more expensive?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    5. Re:Be patient... by Sancho · · Score: 1

      I can't honestly believe that it costs that much extra for 8MB of flash compared to 2MB of flash.

      Linksys sells a lot of these things per year. A whole lot. http://wifinetnews.com/archives/006101.html claims "hundreds of thousands per month" back in 2005. With numbers like that, even small savings add up. And frankly, I'm certain that they ran the numbers and found that it would be cheaper to go with VxWorks. These sorts of things aren't just decided willy-nilly.

      They also managed to segregate their customers. Since they still ship a version based on Linux and running the Linux kernel, people who are buying the routers specifically to get the extra features of an alternate firmware will probably be buying a different model. They can increase the price of that model a bit and increase their profits even more.

    6. Re:Be patient... by Anonymous Coward · · Score: 1, Interesting

      To give more context:

      More than a decade ago I interned at Lucent BCS (Now Avaya), doing, among other things, cost-to-build analysis of other products for comparison to ours. i.e. "how much profit is the other guy making".

      An interesting story was that Lucent business phones had this two-LED (one red one green) indicator system for each line button.

      There were effectively ongoing holy wars over the UI benefits of the extra 4-8 low-brightness SMT LEDs per phone vs. the 10-20 cent cost of said LEDs on a high end business phone that sold for $200+ per unit.

    7. Re:Be patient... by Cramer · · Score: 2, Insightful

      They went back to VxWorks. Their claim is it's smaller, so they can put smaller (cheaper) flash chips, and less RAM in the systems. But I seriously doubt the cost savings amounts to what they have to pay Wind River in licensing.

      Both OpenWRT and DD-WRT produce fully opensource firmwares for a number of systems, including the crippled 54g v5+. All of my linksys toys run dd-wrt (well, except the uber-ancient WAP11, but it's just an atmel microcontroller with a PCMCIA wireless card bolted to it.)

    8. Re:Be patient... by mrsteveman1 · · Score: 1

      It doesn't really matter what the cost of the components is on such a scale, we are talking pennies in difference if that, which they would pass on to the consumer anyway.

      I do think the licensing is part of the switch to vxworks, as we can see here they aren't so fond of complying with the GPL, so when Cisco took over i imagine they started looking for something else.

    9. Re:Be patient... by Sancho · · Score: 1

      And then went right ahead with the WRT54GL (among other versions that still use Linux)?

  5. Linksys routers? by MMC+Monster · · Score: 2, Informative

    I love my Linksys router.

    I was under the impression that other than the wrt54gl (the one I bought, naturally), none of them run linux anymore.

    --
    Help! I'm a slashdot refugee.
    1. Re:Linksys routers? by tmroyster · · Score: 1

      The early model wrt54g s did use linux,
      then they "upgraded" the later models
      (actually cut the amount of ram) and replaced
      linux with something else. By popular
      demand the produced the GL, which is the
      original model.

    2. Re:Linksys routers? by LarsG · · Score: 3, Informative

      According to the complaint: "in
      the Firmware for Linksysâ(TM) models EFG120, EFG250, NAS200, SPA400, WAG300N, WAP4400N,
      WIP300, WMA11B, WRT54GL, WRV200, WRV54G, and WVC54GC, and in the program Quick-
      VPN."

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    3. Re:Linksys routers? by Hal_Porter · · Score: 1

      The early model wrt54g s did use linux,
      then they "upgraded" the later models
      (actually cut the amount of ram) and replaced
      linux with something else.

      They replaced it with vxWorks which is expensive but is my favourite OS by far. It's also a lot smaller than Linux so they could cut build costs by reducing memory.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    4. Re:Linksys routers? by afidel · · Score: 1

      Which is funny because they moved their enterprise AP's off of VxWorks and onto IOS so that the switching guys would be more comfortable admining them.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    5. Re:Linksys routers? by Creepy · · Score: 4, Interesting

      yeah - probably true.

      Part of this was a chain reaction. Linksys was a low end router company and they adopted Linux to save money on development. As such, they had no need to cripple their routers to not compete against their high end brand, since they didn't have one. Unfortunately for Cisco, who bought them, they do have a high end brand, and releasing the source for their low end brand that people have tuned to outperform their high end routers (with overclocking and mods) is not really in their best interest (illegal, yes, in best interest, no).

      Personally, I think they were gambling as long as possible that the FSF wouldn't file a suit.

    6. Re:Linksys routers? by mikkelm · · Score: 1

      Which high-end routers would they be? I've never seen a piece of Linksys gear that got even close to the 870 series Cisco high-end equivalent.

    7. Re:Linksys routers? by Andy+Dodd · · Score: 2, Informative

      FAVORITE OS? WHAT ARE YOU ON AND WHERE CAN I FIND SOME?

      I routinely deal with VxWorks 5.x at work, and it's a nightmarish POS, especially its networking support. I'm assuming Linksys must be using 6.x or a HIGHLY customized 5.x variant with an alternative network stack for their product line, given that the standard 5.x network stack is a halfassed port the 1990 4.4BSD "Reno" release with no new features and a LOT of new bugs.

      --
      retrorocket.o not found, launch anyway?
    8. Re:Linksys routers? by Cramer · · Score: 1

      First off, Cisco bought a company to get the "aironet" stuff, just like they bought Linksys and landed in this mess. If they could get ANY IOS image to fit in 2M flash, and run in less than 8M RAM, I'm sure all the little linksys trash would be using it too. The enterprise hardware isn't as price sensitive as the consumer/retail market, so they can afford to go a bit overboard with the hardware.

    9. Re:Linksys routers? by Cramer · · Score: 1

      Actually, Linksys did have "business class" hardware (WAP4400, etc.) that was (is) much more expensive. But I still wouldn't call it "enterprise" hardware.

    10. Re:Linksys routers? by mrmeval · · Score: 2, Informative

      It is shit. The rev 8 hardware with vxWherks crashed when I tried to configure it. Crashed when the load got too high. Crashed when I would change one minor thing. Crashed if more than two wireless connections were made.

      I took it back and got a Buffalo before that black dress wearing Texas judge made it illegal.

      --
      I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
    11. Re:Linksys routers? by afidel · · Score: 3, Interesting

      I know full well where the tech came from, I supported the former Aironet employees for 3 years after they were bought by Cisco =) The VxWorks stuff was more stable than IOS at least for the first year or two after IOS was ported and if our AP's at work are any indication that's still true as of a few years ago (noone is using them but they still crash once in a while).

      p.s.
      An interesting aside, the VxWorks software was also easier to maintain since it was written in modern C++ vs old straight C for IOS. This became very clear one day when a particular large school called and said all of their AP's were rebooting randomly at fairly short intervals. It turns out they had a HUGE flat network with 28k+ visible MAC addresses. This was more than the AP's were speced for but Cisco couldn't just let a large customer's install die, so after they figured out the cause they had to come up with a solution. For the VxWorks code they simply modified the MAC table class and recompiled, a patch was available within a few hours of the trouble starting. The IOS patch was much more difficult with tons of searching through header files and later after the first patch failed searching through the entire codebase. The small minority of new AP's which were running IOS were flashed in the field to VxWorks with an unsupported dev tool because officially the 'upgrade' to IOS was one way.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    12. Re:Linksys routers? by Cramer · · Score: 1

      One word, on one line, in one file... but you have to know which file. C vs. C++ doesn't matter. It's all a matter of knowing the codebase.

      The real WTF is why code a fixed size for something that is dynamic by nature. The MAC table may need 5 entries, and it might need 5000. (I had this *cough*discussion*cough* with a bunch of pure idiots at 3com 15+ years ago... hardcoded, static sized route tables. I have not bought a single piece of 3Com crap since then.)

    13. Re:Linksys routers? by afidel · · Score: 1

      Could be worse, it could be a L3 switch with hardware MAC tables in the ASIC that becomes crippled when the ASIC's table becomes overrun and you have to do switching with the SLOW CPU. The fact is that there are resource limits to all hardware and sometimes limiting things in software is better than allowing a buffer overflow.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    14. Re:Linksys routers? by Cramer · · Score: 1

      We're talking about software here. The hardware's limit is something very different -- software cannot make the hardware buffer any larger. I've seen "tricks" where the hardware switches the most active traffic (or the first MACs to get in the table) and then process switch the rest. And I've seen cheap (ala netgear, but everyone uses the same broadcom crap) switches that either stops passing new traffic, or starts unicast flooding packets like mad.

      (However, it's been a long time since I was around a network that would fill a 4k mac table. And then it was a 10base-2 network.)

    15. Re:Linksys routers? by afidel · · Score: 1

      There's only so much RAM in those beasts and they have to fit a ton of features into that space so having a hard limit on datastructures makes sense since then they can make sure they never exceed the devices capabilities, it's not like they have swap space to fall back to =)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    16. Re:Linksys routers? by Hal_Porter · · Score: 1

      People that don't like vxWorks should be shot.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    17. Re:Linksys routers? by Cramer · · Score: 1

      This isn't a limit; it's a static size. Having the system allocate memory to support what it needs is a far better system than being a lazy coder and creating a ton of fixed size tables. Over the last 20 odd years, I have seen code from far too many (stupid) lazy "programmers" who create fixed size structures for things that do not have a fixed size. It's a combination of lazy programming reinforced by every improving technology. Why should we spend the time writing fast, efficient code when we can "just through more GHz at it." The same is said for memory... why use memory efficiently when the machine has multiple GB of really fast memory.

      (ASICs aren't exactly little tiny CPUs with their own OS to manage alloc() and free(), so they have to have bits carved in stone -- unless they are FPGAs that can be reprogrammed on the fly.)

    18. Re:Linksys routers? by ZerdZerd · · Score: 1

      At first there was only one WRT54G, which had enough memory for custom firmwares. But then they cut down on the memory to reduce cost, so the new WRT54G didn't have enough memory for custom firmware. But the customers complained and wanted more memory. So they released WRT54GL, which had more memory. So I think all of the WRT54G and GL-series run linux.

      --
      I'm not insane! My mother had me tested.
  6. It's about time by Anonymous Coward · · Score: 5, Interesting

    I've worked at Cisco, and the general attitude among many (not all) is that they don't care about GPL violations. Linux is used as it's the fastest path to get the products out.

    The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility. Which means that those files now fall under the GPL. And the only way to integrate them is to use various Linux API's. That is, key files are derived works from the GPL. From the bootstrap code on up.

    But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL.

    One could try to maintain that those files need to be dual-licensed. However, though some hold that to be valid, I don't believe such a dual license has ever been held up in court. So that might get interesting if the FSF wanted to push it. In any case, it could be a useful bargaining chip.

    In any case, those files don't have the appropriate copyrights stating how they are licensed.

    The amusing part here is that this has come about mostly because of Cisco's dedication to using as much H1-B/L1 labor as possible. It's been those guys who have mostly (not entirely) done this work in order to get things done quickly. And believe me, protestations about the licensing have been ignored completely when they've been raised. Hack-it-in quickly and damn the lawyers has been the attitude.

    It's very amusing to see that Cisco's use of cheap labor has come back to bite them in a way that has the potential to cost them more money than if they had done things in the right fashion originally.

    1. Re:It's about time by mrsteveman1 · · Score: 1

      I assume you are talking about devices other than the 54g series? I can't imagine what backward compatibility would be needed there with IOS.

    2. Re:It's about time by Anonymous Coward · · Score: 5, Interesting

      I've worked at Cisco, and the general attitude among many (not all) is that they don't care about GPL violations. Linux is used as it's the fastest path to get the products out.

      The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility. Which means that those files now fall under the GPL. And the only way to integrate them is to use various Linux API's. That is, key files are derived works from the GPL. From the bootstrap code on up.

      But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL.

      The same thing applies to Symbian - at one point they statically linked GPL code to the OS Kernel, so technically the whole OS should be GPL'd. Which means they ought to release all the source code to customers years ago. This is not something they want to do - their recent announcements have been about releasing the source code to selected components over time.

      Posting AC because I fear their lawyers.

    3. Re:It's about time by ahsile · · Score: 1

      I was under the impression that if you used a GPL library (statically linked or not) your program must be covered by the GPL. On the other hand, if the library was LGPL your assessment would be fine... I think.

      http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#IfLibraryIsGPL

    4. Re:It's about time by Anonymous Coward · · Score: 5, Informative

      That misunderstanding is why so many people fear the GPL.

      The GPL can not force you to relicense your code. None of Cisco's code or Symbians code has to be released. However, unless they chose to relicense it then they are in violation of the GPL and have no license to distribute the GPL'd software.

      So they're committing copyright infringement. They can be forced to stop distributing their products, they can be sued for damages, but under no circumstance can they be forced to turn over code-- though that might be the easiest way to settle the lawsuit.

    5. Re:It's about time by evanbd · · Score: 1

      No, that doesn't place the files under the GPL. The only way something can become GPLed is if the copyright owner willfully uses the license. It may, however, mean that those works are derived works and cannot be distributed under an incompatible license without violating Cisco's obligations under the GPL. If that is the case, Cisco would need to cease distribution of the files in question (or fix the licensing problem, by applying a compatible license).

      But make no mistake: Cisco will not be obligated to release anything under the GPL. They always have the option to simply cease distribution of the works in question entirely. Which one is easier for them may be in question, but that's entirely their decision.

    6. Re:It's about time by arkanes · · Score: 1

      But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL.

      To prevent scare-mongering: This isn't how GPL viralness (virality?) works. Assuming that they have mixed IOS with GPL code in a way that would "infect" IOS (they'll argue that it doesn't, of course) they can either 1) GPL IOS to bring everything into compliance (fat chance) or they can stop doing that, stop distributing the stuff they have, pay a big fine, and rewrite everything in a hurry and at great expense - exactly what Linksys did before them. IOS being forcibly placed under the GPL is a vanishingly unlikely possibility (not even sure that a ruling that they must do so would be legal).

    7. Re:It's about time by Anonymous+Psychopath · · Score: 1

      I'm not sure what he's talking about. None of the Linksys products run IOS, which IIRC was originally based on a BSD kernel a couple decades ago. Perhaps he means that some Linksys products have included libraries from IOS somehow, but I don't see how that would make those libraries then fall under GPL.

      At least some, possibly all, of the GPL violations predate Cisco's acquisition of Linksys, not that it excuses anything; they own Linksys now so they are responsible for compliance. I'm just not certain that there is a link between some Linksys GPL violations and Cisco as an entity willfully violating copyright on a daily basis.

      --

      Eagles may soar, but weasels don't get sucked into jet engines.

    8. Re:It's about time by TheMMaster · · Score: 1

      But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL.

      No matter how you slice it, Cisco still owns the copyright to those 'key files'. Cisco can do whatever the hell they want with them too.

      While, it is true that they would have to grant a GPL licensed copy to all customer to whom they distribute those files combined with GPL code (and only if they are actually linked together) They are more than free to ALSO use those files in a completely proprietary product, without granting any rights to third parties.

      Now, should the community improve those files, cisco would not be able to incorporate the improvements done under the GPLd versions, because they do not own the copyright to those changes and the GPL does not grant Cisco any more rights than anyone else.

      I hope that cleared things up for you a bit :)

      --
      Fighting for peace is like fucking for virginity
    9. Re:It's about time by TheMMaster · · Score: 1

      sorry for the reply to self, I imply that cisco would be FORCED to release those IOS files under the GPL. This is not true, one outcome of the lawsuit may be that Cisco has to refrain from distributing the combined work altogether, and that the FSF will simply get damages for a copyright infringement.

      Although, releasing the files under the GPL would probably be the fastest and easiest way for Cisco to get out of this lawsuit, as this is the goal of the FSF.

      The FSF isn't like the RIAA trying to get maximum cash from any GPL violation ;) they just want the code to be free.

      --
      Fighting for peace is like fucking for virginity
    10. Re:It's about time by dedazo · · Score: 3, Interesting

      The amusing part here is that this has come about mostly because of Cisco's dedication to using as much H1-B/L1 labor as possible. It's been those guys who have mostly (not entirely) done this work in order to get things done quickly.

      This is an interesting statement. If my experience with on/offshoring at large companies is any indication (and I assure you it is), the H1-B guys were simply taking orders from a US-based manager or director. Those kinds of decisions are not made in Pune or Gurgaon.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    11. Re:It's about time by Anonymous Coward · · Score: 0, Insightful

      ...this has come about mostly because of Cisco's dedication to using as much H1-B/L1 labor as possible. It's been those guys who have mostly (not entirely) done this work in order to get things done quickly.

      It sounds like you are trying to make foreigners the scapegoat for Cisco's unprofessional practices. This is completely unfair. Cisco should have in place proper processes for clarifying the licenses of the various software components they use. Trying to scapegoat one group of people based on them not being from USA is ridiculous and small minded.

    12. Re:It's about time by Nick+Ives · · Score: 3, Insightful

      They can be forced to stop distributing their products, they can be sued for damages, but under no circumstance can they be forced to turn over code-- though that might be the easiest way to settle the lawsuit.

      And also the easiest way to stay in business. If you wind up as a large scale GPL violator then the only sane option is likely to be releasing the code. If it's basically a choice between not distributing the code and going out of business or releasing the code and hoping it's all OK then a company can only really do the latter.

      That's fine for hardware companies like Cisco and Nokia who mainly derive value from their hardware but I'm sure it'd kill a proprietary software company.

      --
      Nick
    13. Re:It's about time by Jah-Wren+Ryel · · Score: 1

      One could try to maintain that those files need to be dual-licensed. However, though some hold that to be valid, I don't believe such a dual license has ever been held up in court.

      The GPL has never been held up in US court either. That doesn't mean it isn't valid. If the US legal system were to forbid dual licensing with the GPL, they would end up invalidating millions of other contracts where different customers are sold different rights to the same material - like television syndication rights for example.

      --
      When information is power, privacy is freedom.
    14. Re:It's about time by Nick+Ives · · Score: 1

      But make no mistake: Cisco will not be obligated to release anything under the GPL. They always have the option to simply cease distribution of the works in question entirely. Which one is easier for them may be in question, but that's entirely their decision.

      Presumably if they don't release they'll also be forced to pay full statutory damages for each infringement, i.e. each time GPL linked code was downloaded. Those kinds of damages are designed to bankrupt companies, they may very well end up in the situation whereby they've got to choose between being bankrupted or just giving away their software.

      FSF have already filed suit meaning they're well past the cease-and-desist stage.

      --
      Nick
    15. Re:It's about time by mrsteveman1 · · Score: 2, Informative

      The old IOS is fairly simple compared to BSD, but their IOS-XR (name?) is based on QNX

    16. Re:It's about time by bn557 · · Score: 3, Informative

      The Linksys WRVS4400N Router (a distinctly post Cisco acquisition product), violates the GPL in that it distributes a binary only U-Boot, and the sources for it are not available. In this case, I believe the board maker(Star Semiconductors), are also in violation, as the people at Linksys I e-mailed said that they were only provided with a binary of it by Star Semi. But in either case, I have a router that I have all the source for, except the source for the binary only Marvell TopDog Wireless Card, and the U-Boot bootloader. I have contacted the U-Boot project to notify them of this, and hopefully they get on board in this.

      --
      Humans are slow, innaccurate, and brilliant; computers are fast, acurrate, and dumb; together they are unbeatable
    17. Re:It's about time by evanbd · · Score: 4, Interesting

      The FSF does not need to pursue such damages. Given that their goal is to make a point while not scaring away potential FOSS users, I would imagine they would seek damages that were neither trivial nor crippling. Damages appropriate to what Cisco actually did, unlike evil record companies and their ilk.

    18. Re:It's about time by mrchaotica · · Score: 1

      None of the Linksys products run IOS, which IIRC was originally based on a BSD kernel a couple decades ago. Perhaps he means that some Linksys products have included libraries from IOS somehow, but I don't see how that would make those libraries then fall under GPL.

      Or maybe he means that some Cisco-branded hardware that the FSF doesn't know about is running GPL'd software too! It seems reasonable to me that that could have happened; after all, why would Cisco want to keep making two completely separate lines of hardware when they could just integrate them and then differentiate between high-end and low-end by branding only?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    19. Re:It's about time by maxume · · Score: 1

      If Cisco owns the copyright to the code, they are free to license under the GPL and whatever other licenses they feel like. They may have implicitly released a particular version of those files under the GPL (or violated the GPL by not licensing those files, whatever), but that doesn't have any repercussions towards other uses of that code.

      If you are saying that they have used code that is under someone else's copyright in IOS, then it is more complicated.

      --
      Nerd rage is the funniest rage.
    20. Re:It's about time by TekPolitik · · Score: 1

      The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility. Which means that those files now fall under the GPL. And the only way to integrate them is to use various Linux API's. That is, key files are derived works from the GPL. From the bootstrap code on up.

      Mere use of an API (assuming dynamic linking - static linking is still a problem but so rare now it should be disregarded) will rarely make the code using it a derivative work since it will not incorporate protected expression in the compiled code. It sounds like what Cisco needeed was to shell out a few dollars for some advice from a lawyer who knows enough about software development to tell them this.

      There are some exceptions that arise when the headers contain inline code (but it needs to be significant inline code - a macro "#define min(a,b) ((a) < (b) ? (a) : (b))" won't count.

      Are there any other ways you suggest Cisco has been creating derivative works?

      But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL.

      One could take any view one likes, but one would be wrong. Distributing code in breach does not render the code not released under the GPL to be licensed under the GPL. It just means the code was distributed in breach of copyright, with the usual actions available. Compliance would require the code to be licensed under the GPL. Non-compliance does not result in the code being licensed under the GPL.

    21. Re:It's about time by LarsG · · Score: 3, Insightful

      That's fine for hardware companies like Cisco [...] who mainly derive value from their hardware

      I was more under the impression that Cisco's business model was more like a software company that happens to sell expensive hardware dongles.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    22. Re:It's about time by Chandon+Seldon · · Score: 3, Insightful

      That's fine for hardware companies like Cisco and Nokia who mainly derive value from their hardware but I'm sure it'd kill a proprietary software company.

      Would it? How about compared to a similar scenario where they based their product on unlicensed proprietary software?

      With the unlicensed GPL software they have one more option, so they're strictly less screwed than if it were unlicensed proprietary software.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    23. Re:It's about time by Nick+Ives · · Score: 1

      Which is pretty much the point I was trying to make. If they had been ripping off Windows then they'd already be dead by now. They can always just come into compliance by releasing the source and hope for the best when it comes to the GPL.

      --
      Nick
    24. Re:It's about time by Nick+Ives · · Score: 1

      Oh, then I guess if they've linked GPL software into their core products then they're fuxx0red (to put it technically). Maybe that's why they're defending this suit?

      --
      Nick
    25. Re:It's about time by Xtifr · · Score: 1

      That's fine for hardware companies like Cisco and Nokia who mainly derive value from their hardware but I'm sure it'd kill a proprietary software company.

      If their systems were so heavily dependent on Libre/Copyeft Software that they can't untangle it from their own work, perhaps it's a bit of a stretch to call them a "proprietary software company" in the first place. No matter what they may have deluded themselves into believing.

      In any case, this is not limited to companies using Free Software. Over the years, I've known several small vertical-market companies who would basically bundle an illegal copy of DOS/Window/Netware/etc., along with generic hardware and their own specialty software. Bottom line--companies don't like paying for stuff, and will try to avoid it if they think they can get away with it. When this dislike causes them to cross the line into illegal activities, though, there may well be consequences they don't like. And...what? You want me to be sympathetic?

    26. Re:It's about time by Nick+Ives · · Score: 5, Interesting

      If I were in the FSF shoes then I'd go for every penny I could get. They need to drive home the message that if companies want to play the Free Software game, they have to give back. If companies think they can rip off GPL software and then get off cheap five years later then they wont respect the GPL. Remember Cisco would have gained significant advantage in terms of saved development costs by ripping off the GPLed software named in the suit.

      I don't think that would scare too many firms away. The no-licensing cost aspect of GPL software makes it too tempting for firms who don't necessarily gain any advantage from using proprietary software. Much easier to just slap something together using Free Software and pay a programmer to customise it for whatever product it is you want to sell.

      --
      Nick
    27. Re:It's about time by Anonymous Coward · · Score: 0

      Wait a second now, lets blame the immigrants?

      Better paid American citizens do a better job not violating the GPL?

      Come on folks, who's moderating here. This is really objectionable.

    28. Re:It's about time by Anonymous Coward · · Score: 0

      "I've worked at Cisco"

      And judging by your ability for analysis and critical thought, it comes to not surprise why you are working at Cisco no more.

      "The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility"

      That is certainly half of the story. Cisco doesn't want their IP published everywhere (they have no problem stealing other's IP, though).

      "But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL."

      And since ducks do float, one could take the view that ducks are made up of wood (just like witches).

      "One could try to maintain that those files need to be dual-licensed."

      This has nothing to do with "dual licensing". It's that the copyright owner retains copyright, so they can distribute as they see fit, and that's all.

      "The amusing part here is that this has come about mostly because of Cisco's dedication to using as much H1-B/L1 labor as possible. It's been those guys who have mostly (not entirely) done this work in order to get things done quickly."

      Because proud American labour knows that it's impossible to get things done quicker if you start from a base that is 90% already done. Proud American labour can finish a 20 storey building faster if they start from the foundations than if it is already properly built up to the 18th floor.

      "It's very amusing to see that Cisco's use of cheap labor has come back to bite them"

      As if H1/B1 workers had any saying on this. If anything, you could say that it's very amusing to see that Cisco's use of crap management has come back to bite them. It's only that such a thing is not amusing at all.

    29. Re:It's about time by the_womble · · Score: 1

      I was under the impression that if you used a GPL library (statically linked or not) your program must be covered by the GPL.

      Well, yes, it must, because otherwise it is a breach of copyright.

      The point is that no one can force you to change the license on your own code. The courts will just make you pay damages for breach of copyright.

    30. Re:It's about time by nedlohs · · Score: 1

      Nope. All it would mean is that they infringed the copyright by distributing without being authorised by the copyright holders.

      Which makes them pirates and thieves these days, but has no effect on their own code.

    31. Re:It's about time by Anonymous Coward · · Score: 1, Insightful

      Just because its gpl doesnt mean that releasing the code NOW fixes your violations in the past.

      That would provide zero incentive for any company to release there gpl additions untill they get caught.
       

    32. Re:It's about time by LarsG · · Score: 1

      From the complaint, it looks like it is only consumer-grade products that they got when they bought Linksys. Even if they included some IOS software in some of the products, the absolute worst case scenario for Cisco would be that they would have to dual-license those particular files as GPL. It would not force Cisco to GPL the entire IOS.

      My guess is that Cisco has been dragging their feet because (1) it would be expensive to get into full compliance (they would have to dig up the build environment / source code repositories for old Linksys products, some of which they might not even have anymore) (2) by providing full source to the consumer-grade products, 3rd party firmware for those could be developed that would compete with Cisco's more expensive gear, and (3) they never expected the FSF to sue.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    33. Re:It's about time by dkleinsc · · Score: 1

      If the lack of caring about GPL violations is documented anywhere, then I'd say the FSF has a pretty open and shut case. And if you wanted to help out the FSF a bunch, a few forwarded emails might do the job.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    34. Re:It's about time by mortonda · · Score: 1

      That misunderstanding is why so many people fear the GPL.

      The GPL can not force you to relicense your code.

      Or to put it another way, they shouldn't fear the GPL... they *should* fear the repercussions of stealing other people's code. GPL code simply means, you cannot use this code unless you are willing to share yours too.

    35. Re:It's about time by sparetiredesire · · Score: 2, Insightful

      Wrong. I actually *do* work at Cisco, and we are all required to take lengthy open source training that teaches us about the GPL, LGPL, and BSD licenses. Cisco is taking this very seriously.

      The saying "don't attribute to malice what can be explained by incompetence" comes to mind.

      Cisco is not some evil corporation trying to piss off GPL people, contrary to 90% of the comments on here.

      There are, what, 40k engineers at Cisco? They have many products and it is hard to keep every engineer from pasting some GPL code into their project.

      Cisco is very proactive about this. As I said, we are required to take lengthy training and be quizzed on it.

      Also, Cisco has Linux kernel contributers (on my team) on the payroll--so we certainly give back.

    36. Re:It's about time by Cramer · · Score: 1

      Actually, there are several Cisco products that have Linux under the hood. Most notablly the ASA line of firewalls -- and there's no mention in anything Cisco provides to say it's running Linux, or offer source code, nor do they hand over any source if you ask them for it. In this case, it's just the kernel; the entire thing that makes it a cisco firewall is the single application ("lisa") it runs.

    37. Re:It's about time by DarkVader · · Score: 1

      I'm not sure why you think this.

      A court could certainly order software released under the GPL, the courts are not limited to purely monetary awards.

    38. Re:It's about time by DarkVader · · Score: 2, Insightful

      I don't know why people keep repeating this.

      A judge has it within his or her power to order the release of source code under the GPL, if he or she determines that it would be the best way to remedy the problem.

      If it's a large amount of GPL code, and the plaintiff is willing to accept the GPL release as a resolution to the dispute, there's no reason a judge wouldn't issue an order like that.

      I suppose the company could still refuse to release the code, but judges have pretty broad contempt of court powers, so there could conceivably be a "release the code GPL, or you can sit in jail until it's released" order issued.

    39. Re:It's about time by msuarezalvarez · · Score: 1

      Hey! Don't do that! That is my min macro!

    40. Re:It's about time by Anonymous Coward · · Score: 0

      > I've worked at Cisco, and the general attitude among many (not all) is that they don't care about GPL violations.

      Nah. Developers at Cisco, like at many other companies, are not particularly knowledgeable about copyrights. That's how Cisco and other companies often end up doing wrong things.

      I know I've had, at various places that I've worked, to raise a flag to management about code that had been copied without attribution, and in violation of the copyright of that code.

      > Linux is used as it's the fastest path to get the products out.

      Actually, Linux is used on SOME products, but not all.

    41. Re:It's about time by Anonymous Coward · · Score: 2, Interesting

      Try the MDS9000 series. (Big SAN switches)
      And what about the Content Engine Series.

      Toss in (Some) Catalyst 6500 Services modules and (Some) NM's and AIM's; NM-NAM certainly does, including ethereal, except the NAM has a REAL NetFlow 9 collector/analyzer.

      Bust open some install images and look and see, if you aren't able to console into them...

      Profits from the MDS9000 series will hurt, since the software licenses are pure profit... and are the expensive part.

      Licenses for Cat 6k SM's aren't exactly cheap either, although most of those do not run Linux.

    42. Re:It's about time by Anonymous Coward · · Score: 1, Interesting

      Wrong again. Once you are in violation of your license, you are in violation of your license; releasing the code at that point may earn you brownie points, or you may be able to work out a deal whereby the rightholder does not seek redress, but you have still violated your license even if you attempt later to fulfill your obligations under it.

    43. Re:It's about time by shutdown+-p+now · · Score: 1

      If my experience with on/offshoring at large companies is any indication (and I assure you it is), the H1-B guys were simply taking orders from a US-based manager or director.

      Why do you think the manager is necessarily in US himself? :)

      That said, I don't think this matters in this case. Greed is a universal human trait.

    44. Re:It's about time by ThinkTwicePostOnce · · Score: 1

      | The amusing part here is that this has come about mostly because of
      | Cisco's dedication to using as much H1-B/L1 labor as possible.

      H1-B/L1 labor? So THAT's the reason that Linksys home routers are
      such a pathetic joke! I mean, the help screens they contain are missing
      descriptions of like half of the configuration fields.

      Even first graders get F's if they leave out answers to half the
      questions.

      And when you register a specific model and include your email address,
      can they be bothered to drop you a line when the firware updates? NO!

      Linksys/Cisco you are pathetic!

      --
      Hide all sigs: Click HELP+Prefs (top), VIEWING (last on right), DISABLE SIGS (3rd on left) and SAVE (hidden at bottom).
    45. Re:It's about time by Draek · · Score: 1

      If companies think they can rip off GPL software and then get off cheap five years later then they wont respect the GPL.

      There's just one thing, though: payment for damages isn't a license, so they'll have to pay *AND* release the code or stop distributing the software. And if they refuse to do either, the FSF won't even have to bother, the courts themselves will milk Cisco for money 'til they bleed.

      --
      No problem is insoluble in all conceivable circumstances.
    46. Re:It's about time by Anonymous Coward · · Score: 0

      But the GPL is stated in such a way that companies can't CHOOSE where and how they want to contribute. I don't know of any company that is inherently against contributing, but they would like the ability to choose WHERE their support goes.

    47. Re:It's about time by mdavids · · Score: 1

      My understanding is that under GPLv2, if you violate the terms of the license, your right to use the software under the terms of the license are instantly revoked, and there is no mechanism provided by the license for getting it back. In practice you have to go back to the copyright holder and ask permission.

      Section 8 of GPLv3 does allow you to automatically get out of jail free if you fix the violation voluntarily or within a reasonable time period after an infringement notice. GPLv3 is much kinder to well-intentioned, inadvertent infringers.

      In Cisco's case anyway, I think we can assume they've been knowingly violating for a lot longer than is reasonable.

  7. 5 years to bulk email links to archives? by pembo13 · · Score: 1

    Based on the background, seems like Cisco have 5 years to essentially send an email to all their known customers and post a notice on their website to a public ftp site with the relevant software. Am I oversimplifying?

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    1. Re:5 years to bulk email links to archives? by TemporalBeing · · Score: 1
      What like this:
      1. Go to
      2. Click on "Downloads"
      3. Select your product category (w.g. wireless router
      4. Select your product (e.g. WRT54G)
      5. Select your product version (e.g. 2.0)
      6. Click on "Click here to view GPL Code" link

      This brings you to the following page (for the US): WTR54G GPL Code Web Page. That page also lists the following FTP site: Cisco/LinkSys Open Source FTP site

      So what are the missing that the FSF thinks they need to sue over?

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    2. Re:5 years to bulk email links to archives? by Jah-Wren+Ryel · · Score: 1

      This brings you to the following page (for the US): WTR54G GPL Code Web Page. That page also lists the following FTP site: Cisco/LinkSys Open Source FTP site

      So what are the missing that the FSF thinks they need to sue over?

      Similar pages for a bunch of other products that also use GPL license code.
      Cisco doesn't just make WRT54G's you know.

      --
      When information is power, privacy is freedom.
    3. Re:5 years to bulk email links to archives? by Dan+Ost · · Score: 1

      According to the FSF, that code is either incomplete or not actually the code that runs on the device (I wasn't really sure what they were saying).

      Whatever the problem, the FSF claims that the code Cisco makes available doesn't meet the requirements of the GPL.

      --

      *sigh* back to work...
    4. Re:5 years to bulk email links to archives? by Cramer · · Score: 1

      The code is incomplete and not current. Sadly, this is a near universal problem with commercial use of linux. Netgear is horrible in this respect -- they put broken tarballs up and then take months to correct it. All things concidered, Linksys is pretty good at it -- they rarely post 100% of the source, but across many releases you can find 99% of everything, and they don't take months to put up the source for current firmware releases.

      (What 3rd party devs would love to see is current source for the wireless drivers. The last broadcom source that was "leaked" was years ago -- I don't think linksys intended to include *that* directory in the tarball.)

  8. BSD by Richard+W.M.+Jones · · Score: 4, Insightful

    Cisco / Linksys set themselves up for a fall here. If they wanted code they could just rip off and use whilst largely ignoring the license, why on earth didn't they just use BSD code? These are large companies, presumably they have lawyers. But they're acting like some kid who downloads an image from Google Image Search and uses it on their webpage - "I downloaded it off the web for free so I can just use it right?"

    1. Re:BSD by aztracker1 · · Score: 2, Interesting

      I always wonder that myself.. though I am not familiar with "small" bsd distributions, I am certain they are out there..

      --
      Michael J. Ryan - tracker1.info
    2. Re:BSD by Anonymous Coward · · Score: 0

      All I know is they are making a crapload of money selling linux as a value added feature on the wrt54gl series. Why eliminate that by being idiots about licensing?

      In other news, has Cisco released the code for their Linux switch module they were talking about a few months back?

    3. Re:BSD by moderatorrater · · Score: 2, Interesting

      The problem is that a corporation is made up of people, and individual people can easily make the mistake of using the wrong code. If you hire some intern who writes something that uses gccor other GPL code, there might not be anybody who notices and realizes what's going on. I see it as very easy to get GPL'd code into a large project if you don't have the right people with the right knowledge in place to prevent it. IMHO, this may be especially true since I could see the developers of the firmware being either electrical engineers who would rather be doing the hardware or treated as an afterthought to the people who do the hardware, much like programmers treat sales. Sure, they're required for the product, but it's not like they're the important part or anything.

      On the other hand, the FSF said they tried to work with Cisco and the negotiations outside of court fell through, so who knows? At the very least Cisco's guilty of not heeding the warnings after they were given. They probably aren't guilty of doing this maliciously (at least not at first), but they're definitely guilty of not rectifying their mistake.

    4. Re:BSD by Anonymous Coward · · Score: 0

      you mean I can't? but it's free!

    5. Re:BSD by jellomizer · · Score: 1

      These are large companies, presumably they have lawyers.

      Yea that is an excellent business plan have a lawyer for every technical decision you make, the bigger you are the more lawers you need. That is not good business. You are better off going in a direction if someone complains fight it. If you loose pay the fine, then make the decision to keep going or drop you plan and start over. However in the mean time Cisco has made money from their products.

      But if Cisco wins the against FSF then than all they loss is the part time use of some lawyers. If they loose then they will pay the fine, and probably dump the GNU code, and have a company policy of avoiding GNU at all costs. But if you are going to tiptoe and have a lawyer determine if every step is legal even a big company will die.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:BSD by Richard+W.M.+Jones · · Score: 1

      This is not some tiny, insignificant business decision. This is a major decision - they've got some hardware, the hardware is no good without an operating system, do they use Linux or BSD or license a commercial operating system or write their own OS? Licensing the commercial operating system or writing an alternative would have cost them $100millions. They saved all that money by using Linux in this case.

      Imagine also Microsoft's reaction if they'd just downloaded Windows "for free" off the net somewhere and used it on their routers - it wouldn't have taken them 5 years to find out the consequences of that decision.

      Rich.

    7. Re:BSD by rhizome · · Score: 1

      If you're running the kind of business where you *need* a lawyer to "determine if every step is legal," maybe you should rethink your approach, eh?

      --
      When I was a kid, we only had one Darth.
    8. Re:BSD by Nick+Ives · · Score: 1

      If they loose then they will pay the fine

      The fine being, if FSF can show wilful infringement, $150,000 per work. I think (IANAL, obviously) that applies per infringement (i.e. each time it was downloaded from their website / shipped on a router). There are at least 8 programmes named in the FSFs complaint, so that's a potential $1.2m dollars per infringement. Not a fine any company can just brush off.

      --
      Nick
    9. Re:BSD by Dogtanian · · Score: 1

      Cisco / Linksys set themselves up for a fall here. If they wanted code they could just rip off and use whilst largely ignoring the license, why on earth didn't they just use BSD code?

      Maybe because there wasn't suitable equivalent code available under the BSD license? Or to put it another way, no-one who had written such code felt like releasing it under a BSD license. You can read into that what you will.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    10. Re:BSD by Sancho · · Score: 1

      I think it's actually just a sign that software licenses are out of control.

    11. Re:BSD by Anonymous Coward · · Score: 0

      Just FYI, the word is "lose", not "loose." I mention it only because you used it incorrectly multiple times in the post, and I thought that you might want to know the correct word.

      In other words, I would have assumed that one misuse was a typo or other simple error.

    12. Re:BSD by AaronLawrence · · Score: 1

      Maybe we should let it go. Is there any other word with one 'o' but a long o sound? Lose might be the odd one out.

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
    13. Re:BSD by Anonymous Coward · · Score: 0

      Move is the loneliest word that you'll ever do
      Lose can be as bad as Move
      It's the loneliest word since the word Move ...I think my rapidly escaping point is that lose isn't alone in its long/single o. Move and lose both have long, throbbing, single ohs.

  9. The horror by LtGordon · · Score: 3, Funny

    You guys just don't get it. The FSF protects software. Then Cisco went and muddied it all up like your sister's proprietary, tattooed boyfriend. Now every time you use GCC, it'll be thinking of Cisco.

    1. Re:The horror by Hal_Porter · · Score: 2, Funny

      Then Cisco went and muddied it all up like your sister's proprietary, tattooed boyfriend. Now every time you use GCC, it'll be thinking of Cisco.

      Grunting from the next room disturbing your chain of thought, eh?

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    2. Re:The horror by d3ac0n · · Score: 1

      Wait. Every time you do WHAT with your sister?

      Dude, what kind of family do you HAVE?

      --
      Official Heretic from the "Church of Global Warming". Proven right thanks to whistle blowers. AGW = Flat Earth Theory
    3. Re:The horror by moderatorrater · · Score: 1

      This is the last time the FSF will allow Cisco to fuck with their family. GPLv3: this time, it's personal.

    4. Re:The horror by jimwelch · · Score: 1

      Reminds me a line from "Jonathan Creek" (BBC-mystery). Man walks in on GF and best friend in bed.
      "I'm sorry, where you praying? I heard a lot of O God!s"

      --
      Never trust a man wearing a coat and tie!
  10. aprouter.com.br? by Anonymous Coward · · Score: 0

    what about aprouter.com.br? they offer firmware based on linux for edimax wireless routers. the catch? you need a license to use the wireless device no sources AFAICS :(

  11. Purchase decisions by Britz · · Score: 1

    There are companies that contribute greatly top open source, like SUN for example (OpenOffice, Open Solaris, ...). And there are companies out there that leech off of it and even refuse to open up if they are asked to do so by the FSF.

    Next time you make a purchase decision you should take that into account if your company is using oss.

    1. Re:Purchase decisions by Anonymous Coward · · Score: 1, Informative

      Maybe you should do some research beyond a single incident before you go calling for a boycott

      http://www.cisco.com/web/about/doing_business/open_source/givebacks/index.html

  12. Well, that may well be the result of this lawsuit by PolygamousRanchKid+ · · Score: 1

    I was under the impression that other than the wrt54gl (the one I bought, naturally), none of them run linux anymore.

    If the folks at Cisco decide that potential lawsuits and being forced to open source code that they would rather not, is not worth the risk/trouble.

    It's a shame, really. I would have preferred to have seen the FSF and Cisco settle this behind closed doors, without a lawsuit, as a win-win for everyone.

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  13. There goes my WRT54GL by syousef · · Score: 1

    That sucks. I'm glad I have a couple of WRT54GL boxes, because I can easily see the entire range being dumped if the FSF wins. It's a lose lose sort of situation. FSF has talked to CISCO about this repeatedly and there has been no resolution. Now CISCO refuses to talk so the FSF has to persue the matter or else allow the GPL be flouted. If it persues the matter CISCO/Linksys may well just dump the products but if it doesn't there's a very bad precedent set for the GPL being abused, and FSF has no teeth in any similar situtions.

    I'd be surprised if the routers aren't simply pulled if the FSF does win. Damn it I love my WRT54GL. Most reliable and flexible router I've owned.

    --
    These posts express my own personal views, not those of my employer
    1. Re:There goes my WRT54GL by Iphtashu+Fitz · · Score: 1

      That would probably just hurt Cisco/Linksys in the long run. The last two Linksys routers I bought, I bought mainly because I knew I could install modified firmware on (dd-wrt). If they no longer offer routers with this capability then I'll simply stop buying Linksys gear and start shopping their competitors products who still use GPL'd code and lets me install custom firmware. Granted, I'm only one individual but you can bet I'll also mention this fact to family/friends (and as a professional sysadmin I'm just the kind of person lots of family/friends ask about this sort of thing). And I seriously doubt I'm alone in this regard.

    2. Re:There goes my WRT54GL by Anonymous Coward · · Score: 2, Informative

      Don't worry about it, Buffalo is allowed to sell wireless routers in the states again.

      http://www.buffalotech.com/press/releases/buffalos-wireless-injunction-stayed/

      WRT54GL is done for now.

    3. Re:There goes my WRT54GL by Hatta · · Score: 2, Informative

      There are plenty of other routers that support dd-wrt. My ASUS wl-520gu is excellent.

      --
      Give me Classic Slashdot or give me death!
    4. Re:There goes my WRT54GL by Doug+Neal · · Score: 1

      Yup, I'm running DD-WRT on a Buffalo WHR-HP-G54 in client bridge mode. S'alright.

    5. Re:There goes my WRT54GL by waferbuster · · Score: 1

      True, the ASUS is good. But there aren't too many routers that can match the WRT54G-TM with DD-WRT on it. $30.00 each was a bargain... I bought 3 of them at the T-Mobile store. 32MB of RAM, 8MB flash, 200Mhz CPU... Most excellent.

      Up until about a week ago you could order them from the T-mobile site, but I can't find them now. Most of the retail T-mobile stores still have some in stock, though.

      --
      I'm an individual! Just like everyone else!
  14. Fix article title!!! by Crispy+Critters · · Score: 4, Informative
    The title of the article is erroneous.

    The FSF has filed suit against Cisco for copyright violations. Cisco distributed code owned by the FSF without permission.

    Yes, Cisco could easily be distributing with permission, and hence legally, if they followed the requirements of the GPL. Instead, they chose to distribute without permission, a violation of federal copyright law.

    1. Re:Fix article title!!! by Cajun+Hell · · Score: 1

      Exactly. The outcome of the JMRI case is that these types of things are copyright violations, not merely contract violations.

      --
      "Believe me!" -- Donald Trump
    2. Re:Fix article title!!! by Anonymous Coward · · Score: 0

      Does anyone have more specifics about what Cisco is not releasing? I thought that the higher profile Linux-running products like the WRT54G have had code downloads on their site for awhile now. (Not having time to play with that myself these days, I have no idea if the toolkit is complete.) Is this not the case, or are other products missing code?

    3. Re:Fix article title!!! by Anonymous Coward · · Score: 0

      Semantics, GPL gave them permission given certain conditions which they broke. Same same

  15. Re:Well, that may well be the result of this lawsu by fuzzyfuzzyfungus · · Score: 1

    The FSF had been trying to quietly resolve this for 5 years. They didn't exactly jump the gun on this one.

  16. Maybe this wasn't intentional. by Samschnooks · · Score: 1, Redundant
    There's a lot of posts accusing of Cisco of intentionally violating the GPL; even an alleged ex-employee saying that Cisco "didn't care".

    It could be a misunderstanding of the GPL or bad advice from an expert. Why, if I asked a question about the GPL, I would get dozens of posts each having their own and differing "expert" opinion of what is meant.

    1. Re:Maybe this wasn't intentional. by repvik · · Score: 5, Interesting

      It could be a misunderstanding of the GPL or bad advice from an expert. Why, if I asked a question about the GPL, I would get dozens of posts each having their own and differing "expert" opinion of what is meant.

      Yes, it could be a misunderstanding. Especially when FSF has spent five years communicating with Cisco trying to resolve the issue peacefully. If there's a misunderstanding, the people at Cisco need to get some working brains...

    2. Re:Maybe this wasn't intentional. by Tetsujin · · Score: 2, Funny

      There's a lot of posts accusing of Cisco of intentionally violating the GPL; even an alleged ex-employee saying that Cisco "didn't care".

      It could be a misunderstanding of the GPL or bad advice from an expert. Why, if I asked a question about the GPL, I would get dozens of posts each having their own and differing "expert" opinion of what is meant.

      ...Generally prefixed with "IANAL"...

      Well, Cisco has to consult some people who do not anal... Those people should have a much less ambiguous view of the GPL.

      --
      Bow-ties are cool.
  17. Re:Well, that may well be the result of this lawsu by EnglishTim · · Score: 5, Informative

    If you read the article, you'll see that they did. They've been working with Cisco for the last five years on it, but according to the FSF never became fully compliant:

    As we always do in violation cases, we began a process of working with Cisco to help them understand their obligations under our licenses, and how they could come into compliance. Early on it seemed likely that we could resolve the issues without any fuss.

    While we were working on that case, though, new reports came in. Other Cisco products were not in full compliance either. We started talking to the company about those as wellâ"and that's how a five-years-running game of Whack-a-Mole began. New issues were regularly discovered before we could finish addressing the old ones.

    During this entire time, Cisco has never been in full compliance with our licenses. At first glance, the situation might look good. It's not difficult to find "source code" on the Linksys site. But you only have to dig a little deeper to find the problems. Those source code downloads are often incomplete or out-of-date. Cisco also provides written offers for source, but we regularly hear about requests going unfulfilled.

    Despite our best efforts, Cisco seems unwilling to take the steps that are necessary to come into compliance and stay in compliance. We asked them to notify customers about previous violations and inform them about how they can now obtain complete source code; they have refused to do this, along with the other reasonable demands we have made to consider this case settled. The FSF has put in too many hours helping the company fix the numerous mistakes it's made over the years. Cisco needs to take responsibility for its own license compliance.

  18. Nothing is automatically GPLed by Crispy+Critters · · Score: 5, Informative
    "But, since these files are key to IOS as well, one could take the view that IOS is now under the GPL."

    No no no.

    Cisco has violated copyright law by distributing GPLed FSF code under terms other than specified in the only available license. The ownership and licensing of IOS code is not affected by this in any way. This is the past.

    Now for the future. If Cisco wants to keep distributing IOS code mixed with FSF code, there is only one way of doing it. That is to release the code under the GPL, because the FSF doesn't offer any other licenses. Only the IOS code which is mixed with FSF code needs to be released under the GPL. This has no effect on any other IOS code (older or in other products or whatever).

    1. Re:Nothing is automatically GPLed by Tony+Hoyle · · Score: 1

      It would, because the moment you licensed part of IOS under the GPL you'd be caught in the same trap - you couldn't distribute the whole of IOS without breaking the license on the GPL parts.

      LGPL is a nice answer to this because it doesn't have this horrible linking clause.. if they LGPL the IOS parts they're compatible with both the GPL and the proprietary code.

    2. Re:Nothing is automatically GPLed by listen · · Score: 1

      You are a dunce. Cisco is the copyright holder, they are not bound by the terms of a licence they grant to other legal entities, no matter how that grant was brought about.

  19. Disappointing / Boycott possible by foxalopex · · Score: 1

    Don't forget that Linksys isn't the only Linux compatible router on the market. Other companies such as Asus, Buffalo and others make routers that work with Linux based custom firmware and in some cases use more powerful hardware. So if you're going to boycott you still have options.

  20. Re:Hypocrisy in action by Anonymous Coward · · Score: 2, Insightful

    Exactly! You'd almost think there are several people writing comments!

  21. Blobs by Benanov · · Score: 2, Informative

    WRT54GL boxes use broadcom ('blobcom') chipsets with non-Free binary only drivers for the 2.4 kernels. No 2.6 / ipv6 for me. :(

    I love my WRT54GL--but I'm ready for something better supported.

    1. Re:Blobs by Atti+K. · · Score: 1

      I've used OpenWrt on a WRT54GL, and IPv6 seemed to work just fine. The kernel was 2.4 of course. What's the problem?

      --
      .sig: No such file or directory
    2. Re:Blobs by Benanov · · Score: 1

      I stand corrected--I had read that IPv6 wasn't coming to 2.4.

      At any rate, still blobtastic...

    3. Re:Blobs by Luke-Jr · · Score: 1

      The proprietary/2.4 is a problem, sure, but Linux 2.4 supports IPv6...

      --
      Luke-Jr
  22. BSD is less free for the user by Anonymous Coward · · Score: 4, Informative

    Since the user doesn't get the code.

    Or when are MS going to release the BSD code in Windows, including all enhancements?

    So they can't change the BSD code in Windows, can they.

    The user doesn't have to be a developer either. They can PAY a developer to do it. They are still the user. And, since the BSD allows the new developer to give the binary closed, the developer the user has paid can take the freedom to get someone else to do more work from the user who paid for it.

    Don't be an idiot.

    1. Re:BSD is less free for the user by init100 · · Score: 1

      They can PAY a developer to do it. They are still the user. And, since the BSD allows the new developer to give the binary closed, the developer the user has paid can take the freedom to get someone else to do more work from the user who paid for it.

      If you pay someone to write software, you can include a condition in the contract that voids the contract (i.e. you don't have to pay) if the developer refuses to hand over the source code licensed in an appropriately free manner, or any other clause to a similar effect.

    2. Re:BSD is less free for the user by RazzleDazzle · · Score: 1

      Since the user doesn't get the code.

      What? If I release BSD licensed code... how is the user restricted from the code??????? I fail to understand your nonsense.

      --
      ZERO ZERO ONE ZERO ONE ZERO ONE ONE! Just brushing up for my next big invention: Ethernet over Voice (EoV)
    3. Re:BSD is less free for the user by msuarezalvarez · · Score: 1

      Wow.

      The thing is: you release some code under BSD, I take your code, modify it, and use it in my SuperPropietary App 3000, and distribute it to users. And because I am so inclined, and because your license allows me to, I refuse to give them the code to my modifications.

      There. That's how the user is restricted from the code and its derivative works.

    4. Re:BSD is less free for the user by Tony+Hoyle · · Score: 1

      Why would a user give a shit about the code?

      I don't hear people screaming they don't have the windows source code.. they just use it.

    5. Re:BSD is less free for the user by thtrgremlin · · Score: 1

      That is because it is easy to find on TPB for anyone that really wants it, like everything else... and where do people not complain about windows, and when does it "just work"? Actually, I wouldn't know. I never used Vista and havn't used any kind of windows in a very long time. Guess they got all the bugs out. Good to hear for those that really held on there. Way to go Microsoft.

      --
      Want Big Business out of government? Take away the incentive and start by getting government out of big business!
    6. Re:BSD is less free for the user by Anonymous Coward · · Score: 0

      I've always considered the GPL a dirty hack at best, not because I hate the copyleft requirements but that they only apply to the software in question. In order to receive copyright protection you should be required to publish your sources in some method (escrow and release at end of term, publication at copyright office, etc) so when-and-if the software hits Public Domain we can make full use of it like other works in that category. Patents have this requirement since the idea behind patents is that the public has a net benefit that knowledge passes to the public domain. Not forcing source code publication amounts to an infinite copyright term.

      Captcha: deposes

    7. Re:BSD is less free for the user by Eunuchswear · · Score: 1

      Well, once upon a time there was this guy who had a printer, with a buggy printer driver, and he wanted the code for the printer driver so he could fix the bug, which the manufacturer didn't want to do, and they wouldn't give him the code, and because he, unlike you, did give a shit...

      And the rest is history.

      --
      Watch this Heartland Institute video
    8. Re:BSD is less free for the user by badkarmadayaccount · · Score: 1

      Then you must be new here. We all would like nice laugh.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    9. Re:BSD is less free for the user by geminidomino · · Score: 1

      Wow.

      The thing is: you release some code under BSD, I take your code, modify it, and use it in my SuperPropietary App 3000, and distribute it to users. And because I am so inclined, and because your license allows me to, I refuse to give them the code to my modifications.

      There. That's how the user is restricted from the code and its derivative works.

      Wrong. The user is restricted from YOUR SPECIFIC derivative work. You taking my code, closing it, and releasing a derivative doesn't make my source any less available.

    10. Re:BSD is less free for the user by Anonymous Coward · · Score: 0

      End users shouldn't really need the code: do end user need to even know how to program?

      Real freedom is about not having anyone else put limits on what you can do.

  23. Not exactly by Crispy+Critters · · Score: 5, Insightful
    Look at what the FSF is asking for: an injunction to stop Cisco from distributing any more code, pay damages, give previous profits to the FSF, and pay the FSF's costs.

    This is not exactly "put some code on the web for download."

    If you mean that Linksys/Cisco could have avoided this at any time in the past five years by releasing the code, you are probably right. The FSF is easy to get along with. It is anybody's guess what they need to offer the FSF now to make it go away.

    1. Re:Not exactly by Mikeytsi · · Score: 1

      My guess is get compliant and pay the legal costs. The rest of it is to let Cisco know that they mean business and they need to get in line with compliance, or pay the price.

      --
      I've been called a "Fucking Dick" by better people than you.
    2. Re:Not exactly by Anonymous Coward · · Score: 0

      probably at the bare minimum FSF will require a blood sacrifice of Cisco's first born child to The Great and Mighty Stallman

      warm up the sacrifical brazers its time for idolatry and some fresh smoked heart.

    3. Re:Not exactly by Anonymous Coward · · Score: 0

      I'm not sure the FSF is "easy" to get along with. I used to work for a large public company and we went through hell to get permission from the FSF to contribute to one of their projects. It took almost 2 years. The agreement was straight forward...but we'd submit it, it would go into a legal black hole for a few months, then the FSF lawyers would come back wanting to move a comma or something. Rinse and repeat over and over.

      Now does that extend to their enforcement group? I have no idea, but we don't know how easy or difficult it would be to work with them.

  24. Re:Hypocrisy in action by DaveV1.0 · · Score: 0, Troll

    It is not a troll, it is the truth. You don't like it because you know it is true.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  25. Cisco still pirated by Anonymous Coward · · Score: 0

    Did Jammie get off from her $220,000 fine because she said she'd stop?

    And Cisco restarted selling linux routers because they were so popular and the closed source ones were not.

    And why, WHY, would Cisco make their routers MORE expensive (and have to, to cover the licensing costs) just because they don't wanna let people modify the code they wanted to modify.

    1. Re:Cisco still pirated by Just+Some+Guy · · Score: 1

      Cisco still pirated

      If the allegations are true, then they really are pirates in that they committed widespread unauthorized commercial distribution of copyrighted software.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Cisco still pirated by Anonymous Coward · · Score: 1, Insightful

      Cisco still pirated

      If the allegations are true, then they really are pirates in that they committed widespread unauthorized commercial distribution of copyrighted software for profit.

      There, fixed it for you.

    3. Re:Cisco still pirated by Just+Some+Guy · · Score: 1

      Ceded.

      --
      Dewey, what part of this looks like authorities should be involved?
  26. Discussion by DiegoBravo · · Score: 2, Insightful

    The existence of this kind of discussion (regardless who has the reason) is what scares a lot to many managers that are not interested (or are not able) to get the correct-freedom-flavor philosophy, so they end avoiding free software as a whole....

    In their minds, everything, if free, has a catch... well, the catch is that legalese with the freedom concept, that after a long time can return and "destroy" (that is, force to open your code) the competitive advantage secrets or whatever is called.

    I'm really not sure at the end what approach will provide more benefits to the users, the developers, the proprietary software enterprises (yes, they pay the checks for a lot of people), or humanity as a whole.

    1. Re:Discussion by JoeBuck · · Score: 2, Informative

      These very same companies would vigorously prosecute anyone who violates their own intellectual property rights. Oh, and you repeat the commonly believed false claim that a GPL violator can be forced to open his or her own code. This is incorrect. The violator is a copyright infringer, loses the license to modify or distribute the code in question, and can be forced to pay damages. But the violator cannot be forced to open-source any of its own code (though in many cases, the FSF and others have accepted open-sourcing of the code as a settlement). However, just losing the license is a damaging enough blow, as it could require Cisco to withdraw a ton of products from the market and never use Linux or glibc again.

    2. Re:Discussion by DiegoBravo · · Score: 1

      >> Oh, and you repeat the commonly believed false claim that a GPL violator can be forced to open his or her own code.

      Maybe I expressed incorrectly about some (many) people's fears. Now, that belief is typically (albeit incorrectly) deduced from the "GPL-viral-quality" propaganda that RMS and others (with other intentions) have expressed and repeated.

      >> These very same companies would vigorously prosecute anyone who violates their own intellectual property rights

      Yes... but now the FSF is applying eye by eye, and that's maybe right. Just sounds a bit weird that always it is a GPL issue... never Free BSD/MIT/CC/etc. Of course FSF can argue that these licenses are stupid but I'm just not sure about their perfection.

    3. Re:Discussion by init100 · · Score: 1

      Just sounds a bit weird that always it is a GPL issue... never Free BSD/MIT/CC/etc.

      What issues are people going to have with code that says that "you can do anything you want with it, as long as you keep this copyright notice"?

  27. Re:GPL vs BSD by Dogtanian · · Score: 5, Informative

    This is why free licenses such as BSD should be adopted for any commercial project.

    Cisco didn't "adopt" the GPL; quite the opposite, they're trying to avoid it. However, they put *themselves* in a position where they'll either be forced to or be guilty of breaking the license terms.

    Avoid viral licenses such as *GPL.

    Who should? The people who wrote the original code? Maybe they don't want companies like Cisco using it if it means closing the code off and not returning anything. That's their choice.

    Cisco? They knew- or should have known- the implications of the GPL and had- as you imply- the choice of using BSD-licensed software instead.

    Perhaps there wasn't a BSD-licensed version of what they were looking for? If so, tough shit! No-one's under any obligation to provide them with that for free. Cisco could of course pay someone to write it (and release it under the BSD license if they so wish). Or they're free to use the GPLed code and adhere to the terms it was released under.

    But they thought they could get away with using the no-cost GPL code without honouring the obligations. They knew what they were doing.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  28. Re:Hypocrisy in action by sjames · · Score: 1

    It's not necessarily hypocrisy. At least some people on /. get upset w/ the RIAA because they don't do enough to make sure there really was a violation before they sue. In that case, there is no hypocrisy in being against the RIAA's suits and in favor of the FSF's.

    It could also be a matter of how the FSF handles the matters. Many people here might have a lot less sympathy for defendants in RIAA lawsuits if the RIAA willingly spent 3 years explaining where they went wrong and how they can come into compliance (at practically zero cost) and was willing to consider the matter settled afterwards.

    Typically, copyright holders who license under GPL (including the FSF) have been far more forgiving of violations than the RIAA. Perhaps that's pert of it.

    Slack begets slack.

  29. P2P makes no money by Anonymous Coward · · Score: 0

    Now, will Cisco sell the routers free?

  30. Re:FSF lawsuit could make GPL to risky. by Joe+U · · Score: 1

    I'm not sure I follow your logic, it would be better to violate Microsoft's license instead of the FSF?

    Trust me, if you ignored the license Microsoft included with their products they would be "ready to pounce on you" as well.

  31. Re:FSF lawsuit could make GPL to risky. by Anonymous Coward · · Score: 0

    Correction: If you use GPL'ed code and do not follow the license you will get sued, in the same way that if you buy source code rights from Microsoft and then ignore the terms you have agreed you will get sued.

  32. There are options by Benanov · · Score: 1

    You can always hack an SD card in. :)

    There are instructions floating around to do it. Honestly I could never bring myself to sac SD card reader...although I have a few SD-micro adapters that I could probably consider doing that to.

    Plus with the SD-micro card removed if I fry the adapter I'm not out of a card.

  33. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    People violate the copyright of corporations, corporations sue the violators with no hard evidence discovered through illegal means, slashdotters bitch about the corporations and get firmly behinds the people and decry abuse of copyright and copyright litigation.

    Corporation violates the copyright of the FSF, FSF sues corporation after working with corporation through other means for five years and building up credible evidence, slashdotters bitch about the corporations and get firmly behind the FSF and support copyright and copyright litigation.

    There. Fixed. Easy to think things are the same when you omit key points of the arguments.

  34. Re:Hypocrisy in action by _Sprocket_ · · Score: 1

    No, I'm pretty sure you're wrong. When Cisco announced that their network had been compromised and IOS source code was copied, nobody blamed Cisco for trying to track down the perpetrators. Likewise, nobody seemed at all upset at Cisco when discussions about Cisco knock-offs with illegal copies of IOS have been mentioned. I don't believe there's been any criticism of copyright in these cases.

  35. BSD uses gcc by sdssds · · Score: 1

    BSD uses gcc too, and FSF claims infringement on gcc too.

    1. Re:BSD uses gcc by msuarezalvarez · · Score: 1

      If you compile your code with a gcc, in absolutely no way does your code become GPL'ed.

      After all these years, one would have expected this trivialities to be better known...

    2. Re:BSD uses gcc by sdssds · · Score: 1

      FSF claims that Cisco infringes on GCC. how would using BSD help them there?

  36. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    Yeish, i totally botched that first one...

    Replace "with no hard evidence discovered through illegal means" with "with no hard evidence, and what evidence they do have discovered through illegal means"

  37. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    No, it is hypocrisy because it is not just the *AA that slashdotters bitch about. The fact is that slashdotters are only against copyright when it is used against them or their pet causes. But, when one of their pet projects use the same laws, then the law is good.

    It is the classic definition of hypocrisy.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  38. Curious... by Anonymous Coward · · Score: 0

    What's the problem. Cisco did nothing wrong.

    1. They only copied, NOT STOLE OR VIOLATED ANYTHING, a couple of bits.
    2. They wouldn't have bought it anyway.
    3. The FSF is not going to give an type of damages to the people who origianlly created the works.
    4. The FSF and it's failing business model...blah blah blah.

    Now think...

    1. Re:Curious... by bug1 · · Score: 2, Informative

      1. They only copied, NOT STOLE OR VIOLATED ANYTHING, a couple of bits.
      The right to copy is the problem copyright seeks to address. To copy without permission is a copright violation. FSF hasnt claimed that cisco stole something ?

      2. They wouldn't have bought it anyway.
      The yhad to buy it or an equivalent product, if not they wouldnt have been able to sell their product.

      3. The FSF is not going to give an type of damages to the people who origianlly created the works.
      Copyleft has never been about protecting the people who created the works, its about protecting people who USE the works.

      4. The FSF and it's failing business model...blah blah blah.
      Sharing is not a business model, nobody claimed it was.

      Now think...
      These are not the droids your looking for.

      FSF has very different goals to the music and video distribution corporations, you shouldnt get them confused.

      detrolled

  39. The GPL does not force things under the GPL by Anonymous Coward · · Score: 5, Informative

    The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility. Which means that those files now fall under the GPL.

    This is false. Releasing GPL code can never automatically force other code to be licensed under the GPL. What it does mean is that someone was distributing code without a license, and may be liable for copyright infringement damages. If they *had* licensed their other code under the GPL, they wouldn't have been liable.

    In general, a number of GPL-using authors tend to be okay with someone who has infringed doing a subsequent GPL-based release as a way to clear the air (and often then forgive previous damage caused by earlier infringements), but (a) they need not forgive the damages in such a case, (b) the infringer need never do a GPL-based release of their own code, instead simply paying damages.

    1. Re:The GPL does not force things under the GPL by blurryrunner · · Score: 1

      You forgot: (c) either they obtain a separate license from each of the original programmers, distribute under the GPL (which requires them to GPL their code), or stop distributing their product.

      br/

    2. Re:The GPL does not force things under the GPL by vinsci · · Score: 1

      either they obtain a separate license from each of the original programmers

      This option is actually not available to Cisco, as almost all of the original authors (including me) have assigned their copyright to the FSF. Thus, we can't re-assign it to some other party after the fact. Some may have made their contributions public domain so they could be used, although I'd expect this to be a rare case.

      --

      Trusted Computing FAQ | Free Dawit Isaak!
  40. "Oh Jeez, not this shit again!" by Dogtanian · · Score: 4, Insightful

    *sigh* Cueing the millionth identical replay of the exact same longwinded "BSD is freer because...." "No, GPL is freer because...." discussion subthread, in which the contributors get to restate the established position using the same old arguments to make the same old points, and neither side changes the other's mind.

    Nothing wrong with that, but we don't need to hear it over and over and over again. Can't we just find an old subthread on the subject and link to that instead? :)

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    1. Re:"Oh Jeez, not this shit again!" by 19thNervousBreakdown · · Score: 4, Funny

      That's what scrollbars are for. Thank God they're under the GPL license, or I might not be able to scroll past this tired old discussion.

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    2. Re:"Oh Jeez, not this shit again!" by Culture20 · · Score: 3, Funny

      We reenact this important drama annually, lest we forget.

    3. Re:"Oh Jeez, not this shit again!" by zotz · · Score: 1

      "Can't we just find an old subthread on the subject and link to that instead? :)"

      Hmmm. Perhaps we should write up an official RFC for it and refer to it by number henceforth...

      It would have to contain a good bit of wit and humour to be worth it though. And no references to Hitler...

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    4. Re:"Oh Jeez, not this shit again!" by frost_knight · · Score: 1

      Can't we just find an old subthread on the subject and link to that instead?

      BSD versus GPL Subthread Link

      --
      It always takes longer than you expect, even when you take into account Hofstadter's Law. --Hofstadter's Law
    5. Re:"Oh Jeez, not this shit again!" by TaoPhoenix · · Score: 1

      Come on! We're the Mighty Dot community!

      I forget the latest legal rulings on deep linking, but What if we made a modular database of the arguments and strung them together like a cross between madlibs and Star Trek's Binars?

      "12A152!!!!"
      "No, no. 37H11 PART TWO!!"

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    6. Re:"Oh Jeez, not this shit again!" by AmyRose1024 · · Score: 1

      Can't we just find an old subthread on the subject and link to that instead? :)

      But Slashdot doesn't allow us to post anything in old discussions!

    7. Re:"Oh Jeez, not this shit again!" by Darby · · Score: 1

      *sigh* Cueing the millionth identical replay of the exact same longwinded "BSD is freer because...." "No, GPL is freer because...." discussion subthread, in which the contributors get to restate the established position using the same old arguments to make the same old points, and neither side changes the other's mind.

      Yeah, they're probably Emacs users, the lot of them.

    8. Re:"Oh Jeez, not this shit again!" by Dogtanian · · Score: 1

      Can't we just find an old subthread on the subject and link to that instead? :)

      But Slashdot doesn't allow us to post anything in old discussions!

      Doesn't really matter, it's all been said anyway, which was kind of the point I was making! :/

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    9. Re:"Oh Jeez, not this shit again!" by Anonymous Coward · · Score: 0

      Like a Linux nativity, centered around an OS conceived by a God and ultimately delivered by virgins in a stable (source branch).

    10. Re:"Oh Jeez, not this shit again!" by WhiteDragon · · Score: 1

      Like a Linux nativity, centered around an OS conceived by a God and ultimately delivered by virgins in a stable (source branch).

      Hail, Linus, full of Source. Blessed art thou among coders, and blessed is the fruit of thy code, Linux.

      --
      Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
  41. Re:Hypocrisy in action by sjames · · Score: 1

    There are some on /. who do fit your description. There are many who fit mine.

    An additional issue I left out is the HUGE resource imbalance when a corporation sues an individual.

  42. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    What about the hundreds of other stories about copyright infringement? Or, do you suggest that we should only consider the few stories that don't prove my contention?

    Go back and read the stories on copyright. By far, the majority are filled with screeds against copyright and copyright enforcement. Most of comments are of the vein "Copyright is bad because we can't get something for nothing." Check out the stories on binary only drivers, which are binary only because of copyright issues.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  43. Am I mistaken? by slimjim8094 · · Score: 0, Redundant

    I have a WRT54G (not the L, but before they went to that shitty crashy excuse of an OS.. v4 I think)

    Before I had DD-WRT on it, I went to the Linksys website to download firmware updates. The source was available.

    Has this since changed, or was it incomplete? I've always applauded Linksys (before they were Cisco) for specifically making the Linux-based GL for us tinkerers. You can pull off some cool shit with those routers.

    Hopefully this is just a misunderstanding.

    --
    I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    1. Re:Am I mistaken? by Kalriath · · Score: 2, Insightful

      Now try that with a Siemens router... clearly running Linux, yet they go to even less effort than Linksys to comply with the license (which is to say, getting source is impossible). Why is Linksys in trouble while Siemens gets ignored?

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    2. Re:Am I mistaken? by Anonymous Coward · · Score: 1, Insightful

      Cause the FSF with its limited resources can only focus on litigating one costly major case at a time? If it wins against Cisco and collect damages, then it can go after other big name violators. However, as has been mentioned elsewhere in the thread, the FSF would prefer compliance with the license over litigation. For all you know, the FSF may be in negotiation with Siemens right now.

    3. Re:Am I mistaken? by badkarmadayaccount · · Score: 1

      One unbeliever at a time, grasshopper.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  44. Re:Well, that may well be the result of this lawsu by PolygamousRanchKid+ · · Score: 1

    The FSF had been trying to quietly resolve this for 5 years.

    That's what troubles me: given that the FSF were obviously patient about it, what caused Cisco *not* to comply?

    I guess we'll just have to wait to hear Cisco's side of the story.

    But again, regardless of who's right, and who's wrong, publicity like this is not good for open source, and I wish this lawsuit did not come to be.

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  45. Re:BSA lawsuit could make proprietary sw to risky. by Experiment+626 · · Score: 2, Interesting

    This could send the wrong message. If you Use bootleg proprietary software and make a lot of money from it you will get Sued. Details of the reasons will fade just the face the proprietary software is considered to Risky for a corporate environment. You better off getting a License from GPL as you can choose to agree to the terms before hand, then going with a product which wile may be backed by a big company will have a bunch of people ready to pounce on you if you make this code successful.

  46. Re:Not for GPLv2 by JohnFluxx · · Score: 1

    You really expect it to cost a lot of money to keep the code on an ftp server, and send a copy to those who request it (which will be nearly none) ?

  47. Bout time they backed up words with actions by Anonymous Coward · · Score: 0

    When Virgin violated the GPL the FSF didn't bother.

    Bout time FSF did something.

  48. I just don't get it!! by mlwmohawk · · Score: 5, Interesting

    Cisco is being REALLY REALLY stupid here and I just don't understand why.

    I've done a lot of commercial software that uses LGPL and GPL code, and its not rocket science. RMS himself even says that "mere aggregation" is not a problem.

    Here are the rules:

    if its LGPL, link to it, but don't modify it. If you need to modify it, make the modification in the form of a generic API extension and call it from the application. Make your extensions public.

    If it is GPL, make it a service and call it through a socket.

    If it is a kernel module, there seems to be some wiggle room there, otherwise make a public mini-driver and a proprietary user space app.

    How hard is that? Jeez, if you screw up GPL compliance, you are not paying attention.

    1. Re:I just don't get it!! by Fred+Ferrigno · · Score: 1

      I'm sure Linksys was aware of their responsibilities and always intended to release the source. Reading the actual complaint, the problem appears to be that Linksys didn't release the exact source corresponding to the released versions, didn't release everything needed to compile the source, or didn't release updated source to go along with new versions. It just sounds like stuff that got overlooked in the rush to get the software out.

      To correct that, the FSF wants Linksys to appoint a Free Software Compliance Officer to make sure the source is always available.

    2. Re:I just don't get it!! by Anonymous Coward · · Score: 0

      I think this misses the point. The premise behind the GPL is encourage, or force, the sharing of code. If you link to GPL code or extend already GPL'd tools and then redistribute you must include the source code. If you don't distribute then you don't have to share the source. IF YOU'RE JUST GOING TO FIND SOME LOOPHOLE IN THE GPL (BY USING SOCKETS OR SOMETHING) IT KIND OF DEFEATS THE PURPOSE OF THE GPL ENTIRELY.

      In this case its more so that Cisco/Linksys uses GPL'd software in their products and distributes it (via firmware) to its customers. They don't supply the source code for this GPL'd software as required by the GPL when distributing.

    3. Re:I just don't get it!! by jmknsd · · Score: 1

      if its LGPL, link to it, but don't modify it. If you need to modify it, make the modification in the form of a generic API extension and call it from the application. Make your extensions public.

      If it is GPL, make it a service and call it through a socket.

      but that is asking alot from an H1B visa worker who's working from an O'Reilly 'nutshell' book and bitching about how much better php is then C.

    4. Re:I just don't get it!! by mlwmohawk · · Score: 1

      I think this misses the point. The premise behind the GPL is encourage, or force, the sharing of code.

      I think *you* miss the point. The GPL in no way is trying to tell you what to do with YOUR code. It is, however, insisting that you respect the rights of the people who wrote the GPL code you use.

      If you link to GPL code or extend already GPL'd tools and then redistribute you must include the source code.

      Yup.
      IF YOU'RE JUST GOING TO FIND SOME LOOPHOLE IN THE GPL (BY USING SOCKETS OR SOMETHING) IT KIND OF DEFEATS THE PURPOSE OF THE GPL ENTIRELY.

      Not at all and I would bet that RMS himself would agree. I have not defined any such thing as a loophole. I have defined a way that is legally safe and sound for using GPL as a base for your project which is *not* GPL. It allows you to do what you feel you need too while respecting the rights of the people who have offered to share the code so generously.

      RMS is about freedom, he is not about forcing anyone to do anything.

      In this case its more so that Cisco/Linksys uses GPL'd software in their products and distributes it (via firmware) to its customers. They don't supply the source code for this GPL'd software as required by the GPL when distributing.

      I obviously, but it is about taking someone else's work and incorporating it into a product in a way that is counter to the license through which they receive access to the source code.

      They have modified someone else's code and, against the license, not shared their changes.

    5. Re:I just don't get it!! by Anonymous Coward · · Score: 0

      RMS's opinion is about as relevant to whether or not "mere aggregation" is a problem as my great-aunt's opinion is. He's neither a lawyer nor a judge, so he's not qualified to make that evaluation.

      (Of course, he can always decide not to file suit for cases where the FSF owns the copyright in question, but when that isn't the case he's almost totally irrelevant)

    6. Re:I just don't get it!! by Anonymous Coward · · Score: 0

      >How hard is that? Jeez, if you screw up GPL compliance, you are not paying attention.

      Or the violater is a legal masochist.

    7. Re:I just don't get it!! by Raenex · · Score: 1

      I've done a lot of commercial software that uses LGPL and GPL code, and its not rocket science.

      It's quite debatable what all the terms mean and what you are allowed to do. Most of the issues have not been settled in court. Personally, I think your advice is simplistic and wrong, though it does seem to be commonly accepted.

      RMS himself even says that "mere aggregation" is not a problem.

      This is like compiling a shareware disk where the programs aren't related. Once you combine the programs to create a greater program, you are no longer "merely aggregating".

      If it is GPL, make it a service and call it through a socket.

      This doesn't save you. If you slap a GUI on top of a GPLd program and use sockets, do you really think your program is "mere aggregation"?

    8. Re:I just don't get it!! by mlwmohawk · · Score: 1

      While this is most likely a FUD troll, people may be scared about what is said.

      It's quite debatable what all the terms mean and what you are allowed to do. Most of the issues have not been settled in court.

      This is pure FUD on the highest level. Thus far the courts have ruled that the GPL is what it says it is and the language is plain enough. What organizations like Cisco are trying to to in the courts is limit the powers of the GPL, and are failing.

      Personally, I think your advice is simplistic and wrong, though it does seem to be commonly accepted.

      Everyone is entitled to their opinion, I guess.

      This is like compiling a shareware disk where the programs aren't related. Once you combine the programs to create a greater program, you are no longer "merely aggregating".

      Maybe you misunderstood my original post, but "combine the programs to create a greater program" is a bit ambiguous. I suspect intentionally so.

      The GPL and its supporting documents describe exactly the methods by which programs can be created and how any encumbrances work. You are obscuring the facts in order to spread FUD.

      If you slap a GUI on top of a GPLd program and use sockets, do you really think your program is "mere aggregation"?

      As long as the GPL program runs unmodified in its own process space, absolutely, yes.

      While I am not a lawyer, I have worked with several IP lawyers in creating GPL compliance guidelines.

    9. Re:I just don't get it!! by Anonymous Coward · · Score: 0

      If it is GPL, make it a service and call it through a socket.

      In many cases this would be OK, except when it's not :p

      The question is: are you doing a derived work of the GPL licensed program or not. If you do, whether you're using a socket or smoke signals does not matter.

    10. Re:I just don't get it!! by Raenex · · Score: 1

      Thus far the courts have ruled that the GPL is what it says it is and the language is plain enough. What organizations like Cisco are trying to to in the courts is limit the powers of the GPL, and are failing.

      The basic idea of GPL is valid, but what I'm talking about are the finer issues, such as what constitutes "mere aggregation". If you can, cite a case law that covers something like using sockets to avoid GPLing your program.

      Maybe you misunderstood my original post, but "combine the programs to create a greater program" is a bit ambiguous. I suspect intentionally so.

      It's ambiguous because the license itself is ambiguous on this issue.

      The GPL and its supporting documents describe exactly the methods by which programs can be created and how any encumbrances work. You are obscuring the facts in order to spread FUD.

      Provide a quote then. Use GPLv2 please, since that's the version under suit, the one most commonly used, and the one I've studied in detail.

      As long as the GPL program runs unmodified in its own process space, absolutely, yes.

      The FSF disagrees with you:

      http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation

      "By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program."

      While I am not a lawyer, I have worked with several IP lawyers in creating GPL compliance guidelines.

      You are citing authorities I have no way to verify. Furthermore, lawyers can be wrong, just like anybody else, and case law is what counts.

    11. Re:I just don't get it!! by mlwmohawk · · Score: 1

      If you can, cite a case law that covers something like using sockets to avoid GPLing your program.

      You are looking as courts as the one's granting the rights, not the GPL and the FSF, this is the wrong approach.

      It's ambiguous because the license itself is ambiguous on this issue.

      again, FUD.

      Reposting the FSF link:
      http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation [fsf.org]

      Specifically, your concern is this part, I assume:
      But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.

      This section of the FAQ is legal conjecture about what the FSF thinks might be an issue. And while I can see their point, in practice it would be difficult to keep with the separate process space guideline and "exchanging complex internal data structures" guideline without red flags going up as it would almost assuredly mean you are using common structure and data definitions during the build process which would be source of the GPL violation.

      You are citing authorities I have no way to verify.

      Yup. anyone could claim anything. One must evaluate based on what is said and independent corroborating facts instead of reputation. Its harder, but better.

      Furthermore, lawyers can be wrong, just like anybody else, and case law is what counts.

      Case law is important *only* if there is serious ambiguity and a hostile party. One can always ASK the FSF if they have an issue BEFORE it becomes an issue. The WANT to help!!

      Furthermore, the FUD thing is old. Courts only LIMIT rights based on law, they do not grant rights. The GPL defines what rights you have to GPL code. The only thing the court can do is limit the FSF's rights, and thus far the GPL has been held up as valid in all tests.

    12. Re:I just don't get it!! by Raenex · · Score: 1

      You are looking as courts as the one's granting the rights, not the GPL and the FSF, this is the wrong approach. [...] This section of the FAQ is legal conjecture about what the FSF thinks might be an issue.

      These are in contradiction. If there's a legal issue then the courts will ultimately decide, which will become case law to guide future interpretations.

      It's ambiguous because the license itself is ambiguous on this issue.

      again, FUD.

      Then cite the GPLv2 where it makes it clear what is "mere aggregation" and what isn't. You'll find nowhere does it talk about sockets vs linking, for example. In fact, I think it was wisely made ambiguous to avoid loopholes like sockets or other technical variations.

      And while I can see their point, in practice it would be difficult to keep with the separate process space guideline and "exchanging complex internal data structures" guideline without red flags going up as it would almost assuredly mean you are using common structure and data definitions during the build process which would be source of the GPL violation.

      Then your simplistic advice which started this thread isn't so clear anymore, now is it?

      Case law is important *only* if there is serious ambiguity and a hostile party. One can always ASK the FSF if they have an issue BEFORE it becomes an issue. The WANT to help!!

      The FSF is not the only owner of GPL code. As an example, the Linux kernel has countless owners, since they don't get copyright assignments. Personally, if I was the author of a GPL program, and you trivially wrapped it with a proprietary GUI using sockets, I would definitely sue. Also, since ultimately the FSF desires more people to GPL their code, if there's any doubt they'll ask you to GPL.

      Furthermore, the FUD thing is old.

      What's old are people carelessly tossing around the words FUD and troll every time somebody disagrees with them.

      The GPL defines what rights you have to GPL code.

      That's why I've been asking you to cite it.

    13. Re:I just don't get it!! by mlwmohawk · · Score: 1

      Then cite the GPLv2 where it makes it clear what is "mere aggregation" and what isn't.

      In contract law, where there are complex terms and concepts in the contract, supporting documents are used to interpret their definitions. The FAQ you posted as a link is a pretty clear discussion about what is meant by "mere aggregation."

      Then your simplistic advice which started this thread isn't so clear anymore, now is it?

      Actually it is very clear. Everything created by people is imperfect, and anyone can create a discussion and argument where black looks like white for the sake of an argument. This is exactly the FUD you are employing. FUD -- "fear uncertainty & doubt"

      My original posted rules:

      (1) if its LGPL, link to it, but don't modify it. If you need to modify it, make the modification in the form of a generic API extension and call it from the application. Make your extensions public.

      (2) If it is GPL, make it a service and call it through a socket.

      (3) If it is a kernel module, there seems to be some wiggle room there, otherwise make a public mini-driver and a proprietary user space app.

      These have not been refuted. All you have done is raise a border condition that in all likelihood can't be accomplished without violating standard GPL copyright to begin with.

    14. Re:I just don't get it!! by Raenex · · Score: 1

      In contract law, where there are complex terms and concepts in the contract, supporting documents are used to interpret their definitions. The FAQ you posted as a link is a pretty clear discussion about what is meant by "mere aggregation."

      The FAQ says that ultimately a judge will decide, and only gives an opinion, and even then it doesn't give carte blanche for sockets. Besides the FAQ, there are the stated goals of the GPL and the GPL itself. The GPLv2, which you seem extremely averse to quoting, says the following:

      "If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."

      Now what happens when I show the judge this license, show that the defendant slapped a proprietary GUI on top of my GPL program via sockets, and sold it as a whole? Do you think I might have cause for legal complaint, even if data structures were not shared?

    15. Re:I just don't get it!! by mlwmohawk · · Score: 1

      There is a part you are missing about copyright itself, and that is the term "based" from "based on the Program" which is analogous to "derived from."

      This is not mere aggregation.

    16. Re:I just don't get it!! by Raenex · · Score: 1

      You're making a legal claim as to what "a work based on the Program" means. Unless you can show a specific legal definition for that phrase, then it can easily be argued that slapping a GUI on top of another program to create a larger program is basing your work on somebody else's.

      In fact, the paragraph I quoted specifically used the phrase "not derived" in the first sentence, and then made sure to use a different phrase in the second sentence where you were required to GPL the whole work. It seems clear to me that the whole point of this paragraph is to prevent "but I didn't derive from your work, so I can use it!" defense. Which makes complete sense, when you consider the point of the GPL. The LGPL was designed for wrapping, not the GPL.

  49. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    I would say that it is a very few who fit your description and many who fit mine.

    Is it your contention that the huge resource imbalance makes it OK for an individual to violate the copyright of corporations, or that the huge resource imbalance makes it wrong for corporations to defend their copyrights?

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  50. Re:Hypocrisy in action by Nick+Ives · · Score: 1

    No it's not the truth, it's a very bad troll (I mean, feeding your own post? No points for you!).

    Are you arguing that /.ers would try to defend someone who ripped off MS code and shipped it in their own product? Or are you muddying up the water when it comes to the whole MPAA/RIAA situation which is itself objectionable for reasons wholly unrelated to whether or not violations took place in particular cases e.g. UMG v Lindor.

    There's also alternative views on copyright held by people such as RMS in his Copyright and Globalization in the Age of Computer Networks and a wide spectrum of other copyright reformists that post here. No position on copyright that I'm aware of is hypocritical in the fashion you describe.

    Of course, it's always much easier to fling names around rather than engage with someone who has different ideas. I've at least tried that with you meaning I get the moral high ground and I get to call you a stupid idiot troll.

    --
    Nick
  51. Re:Hypocrisy in action by SanityInAnarchy · · Score: 1

    Slashdot is not a single user with a single mind, despite what you'd like to think.

    But when you think about it, if copyright didn't exist, there'd be far less need for something like the GPL.

    --
    Don't thank God, thank a doctor!
  52. Re:Hypocrisy in action by mrchaotica · · Score: 3, Insightful

    "Slashdotters" want the software to be freely distributed, freely used, and freely modified. Corporations use copyright to prevent that, so Slashdotters are against them. The FSF uses copyright to promote that, so Slashdotters support it. That's not hypocritical at all: in all cases Slashdotters are trying to work towards the same goal. You only thought it was hypocritical because you weren't looking at the whole issue.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  53. Re:FSF lawsuit could make GPL to risky. by maugle · · Score: 2, Insightful

    Seriously. Microsoft wouldn't spend 5 years talking with you in an attempt to get you to comply with their license. They'd just send in the lawyers and sue for millions in damagaes.

  54. Re:Hypocrisy in action by Nick+Ives · · Score: 1

    huge resource imbalance makes it wrong for corporations to defend their copyrights?

    Of course the fact that the record companies have much better legal representation makes it wrong for them to extort money through pre-settlement letters. The RIAA lawyers are better funded and better informed so it's wrong for them to abuse the legal process to force scared people, a large number of whom have done nothing wrong, to pay up. Their methodology is so flawed that even in cases where someone probably did share some tunes they don't have enough evidence to prove it was the defendant.

    Judges in the USA have even gone on record and said exactly that, so hopefully the tide is turning.

    --
    Nick
  55. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    This case is about whether Cisco violated the General Public License. /.ers already have supported a company, Psystar, that violates the license, and thus the copyright, of another company, Apple.

    Psystar violated the license and /.ers support them vociferously.

    And, I would not doubt for a second that /.ers would support and defend someone who ripped off MS code.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  56. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    It is hypocritical. It is a case of "Do as we say, not as we do". The law applies to all or none. Either everyone has a right to defend their copyrights or no one does. To say that "we" have the right to defend our copyrights but "they" don't is blatant hypocrisy.

    You only think it is not hypocritical because you are a hypocrite.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  57. BSD and corporate disasters by rtfa-troll · · Score: 2, Interesting

    It's a funny thing, but my experience with BSD in a corporate environment is that it doesn't end up as much of a success. There are some exceptions, but even in the case of OS-X, Apple seems to have completely failed to build the community they wanted at the beginning. Most other cases, starting with BSD/OS (BSD 386) and going through IPSO, Ipsilon's home grown BSD based OS, and many others you haven't heard of (AlchemyOS etc.) end up completely dead. Even Microsoft's TCP stack seems to have been rewritten with little BSD left behind.

    I think the reason the BSD code dies is precisely because of it's non copyleft license. The companies mostly know that the best way to handle maintenance is to contribute back to the original developer. However, that's not a requirement of the license and so needs to be agreed to by the corporate lawyers. Separately for each contribution. The always want a justification and it just isn't worth any programmer's effort. With GPL code, the fact you have to give back makes the justification very easy to provide. That puts the corporate developers easily in touch with the "community" of other developers on that software and makes the development end up more successful. I'd love to hear other explanations for this. The main data point I have is that across a bunch of different projects I have seen, it always seems that the GPL ones have an active process for contributing back and have developers who are active and known in the original development community. On the other hand the BSD ones, even though they've included a number of former BSD developers don't seem to and those developers seem to give up on making contributions back to the original system.

    I know that's CISCO, in this case is probably not really getting as much benefit from this as they could if they followed the GPL, but I think there gets to be a general perception that Linux leads to success and BSD leads to dead ends. People select software based on that perception

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  58. Re:Hypocrisy in action by mcgrew · · Score: 1

    People vote GW Bush into office, and what happens? Letters to the editor of every newspaper in American saying he's a bad President.

    Hypocrisy, thy name is America.

    Hint: in the RIAA threads there are always posters defending the corporations. They may be in the minority, but they are there. If you put ten people in a room together, do they have Multiple Personality Syndrome?

    From my reading of comments in those threads, most slashdotters are in favor of both copyright's existance and its badly needed reform.

    Lets talk about Apple vs Microsoft (or vi vs emacs or KDE vs Gnome) if you want "hypocricy".

    "I'm sorry, Dave, I can't let you do that." -HAL

  59. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    So, you admit that you believe that the strong should not be able to defend themselves against the weak, simply because they are stronger than their attackers. Nice to know that.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  60. Re:Not for GPLv2 by morgan_greywolf · · Score: 1

    GPLv2 requires physical media if requested.

    No. You can also include the source along with the binaries on a 'medium customarily used for software interchange'. It has been commonly interpreted that this wording is meant to include a link to a public ftp or www site. The 'written offer for source code' is optional. Cisco could just as easily have either A) add links to the source on the CD-ROM setup thingy they distribute with the each Linksys router or B) just put the source right on the CD-ROM setup thingie. It's not like their setup code takes 650MB. Sheesh.

    considering how convoluted the licensing is when using linux, there is probably some GPLv1 code still in there somewhere.

    There is no GPLv1 code in the Linux kernel. The kernel has been GPL v2 pretty much since the beginning. If you mean 'sitting in userland', AFAIK there no GPL v1 code in any modern Linux distro.

    Once a business has released anything GPL, they are required to support it forever.

    Incorrect. They can discontinue support at any time.

  61. Re:Not for GPLv2 by Anonymous Coward · · Score: 0

    "but the GPLv2 requires physical media if requested."

    What's the fucking point so stating?

    "3. You may copy and distribute the Program...
    a) Accompany it with the complete corresponding machine-readable
            source code, which must be distributed under the terms of Sections
            1 and 2 above on a medium customarily used for software interchange;"

    It even goes to *explicitly* stating that no physical media is needed:

    "If distribution of executable or object code is made by offering
    access to copy from a designated place, then offering equivalent
    access to copy the source code from the same place counts as
    distribution of the source code, even though third parties are not
    compelled to copy the source along with the object code."

  62. Re:Hypocrisy in action by mrchaotica · · Score: 3, Informative

    The law applies to all or none.

    It's not about "the law," though. Laws are reflection of society, not the other way around -- you don't avoid doing something because it's against the law, you make it against the law because it was a bad thing to do in the first place. But because of this, laws don't always get it right. It used to be illegal to aid an escaping slave, for example. But does that make such an action wrong? Of course not (unless you're a KKK member)! Laws should be followed when they are just, but when they are unjust they should be broken.

    By your logic, ambulance drivers should lose their driver's licenses and soldiers should be jailed for murder.

    It is a case of "Do as we say, not as we do".

    Wanna bet? Here's "what we say:"

    "We want users of information to be able to freely modify and share it without restriction."

    Copyright holders of proprietary information (like the RIAA) try to prevent it from being free to modify and share without restriction, so we oppose them. "What we do" is completely consistent with "what we say" in this case.

    Copyright holders of Free information (like the FSF) try to force it to be free to modify and share without restriction, so we support them. "What we do" is also completely consistent with "what we say" in this case too!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  63. Re:Hypocrisy in action by Nick+Ives · · Score: 1

    Mac freak /.ers already have supported a company, Psystar, that violates the license, and thus the copyright, of another company, Apple.

    Fixed that for you. They're a derided subculture even around these parts, real /.ers are Free Software True Believers!

    --
    Nick
  64. Re:Hypocrisy in action by Nick+Ives · · Score: 1

    No, I believe that justice implies a certain equality. When it's possible for one side to win just because they have more money, regardless of what really happened, then justice has failed.

    --
    Nick
  65. Get the name right by SnarfQuest · · Score: 5, Funny

    Get the name right. It's Gnu/Cisco.

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    1. Re:Get the name right by shutdown+-p+now · · Score: 1

      You mean, it's GNC (GNC's Not Cisco)

  66. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    That is not what you are saying in this case. In this case, you are saying "We should be able to use the copyright laws to protect our copyright. But, people who don't believe as we do should not be able to protect their copyright in the same way". And, that is hypocrisy.

    You want the law to only apply to when it benefits you and your position. If it would benefit people who hold a view different from yours, you do not want the law to apply and think it is unfair that they are allowed to use the same laws you are allowed to use.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  67. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    That is not what you have said. You have said that because one has more money or is stronger, one should not be able to defend one's copyright against someone who lass less money or is less powerful.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  68. Not exactly either by Fred+Ferrigno · · Score: 3, Informative

    If you mean that Linksys/Cisco could have avoided this at any time in the past five years by releasing the code, you are probably right.

    If you read the complaint, the FSF acknowledges that Linksys* has already released most of the code they are required to release. The big problem is that Linksys has a habit of releasing the binary versions first, then neglecting to release the source until the FSF complains and dragging their feet even then.

    The bottom line is that the FSF wants Linksys to be more proactive about releasing source files (by appointing a Free Software Compliance Officer) and to pay them for past abuse.

    * The complaint specifically and exclusively references Linksys products. It says nothing about IOS or any Cisco-branded products.

  69. It's not one issue that took 5 years by Fred+Ferrigno · · Score: 1

    The complaint is that there were multiple violations, most of which were resolved eventually, but the problem is that they keep happening and they take too long to resolve. The FSF wants Linksys to appoint a Free Software Compliance Officer to be more proactive about providing source.

    Also, note that this is all about Linksys-branded products, not Cisco-branded ones. IIRC, Linksys mostly operates independently from the rest of Cisco.

  70. It's the FSF's first lawsuit! by jonaskoelker · · Score: 4, Insightful

    They allow abusive entities such as the Free Software Foundation to go after Cisco.

    I know you're just trying to be funny, but what's worth noticing is that this is the FSF's first lawsuit:

    [...] Peter Brown, executive director of the FSF. "In the fifteen years we've spent enforcing our licenses, we've never gone to court before. We have always managed to get the companies we have worked with to take their obligations seriously.

    Isn't that interesting? I'm not sure whether Cisco decided to call the FSF's bluff or whether they have some other thinking behind their decisions; but I know that this is going to be interesting to watch.

    IIRC, the GPL has been upheld in court before, so (depending on the details of Cisco's actions) the FSF is probably in a good position to win.

    1. Re:It's the FSF's first lawsuit! by Anonymous Coward · · Score: 0

      I'm not sure whether Cisco decided to call the FSF's bluff ...

      What bluff?

    2. Re:It's the FSF's first lawsuit! by jonaskoelker · · Score: 1

      The bluff that might exist in Cisco's mind: that the FSF really can't or won't file a lawsuit and won't put their money where their mouth is.

  71. It's shorthand by tepples · · Score: 2, Insightful

    The title of the article is erroneous.

    Not if "GPL violation" is a common shorthand for "infringement of copyright in a work ordinarily distributed under the GNU General Public License".

  72. Links**t? Uggh! by Mathinker · · Score: 1

    After getting the "our developers are working on it" runaround for months and months when Linksys didn't issue new drivers without the Broadcom vulnerability for my WPC54G adapter, rendering it totally useless, I decided to never, never, again buy Linksys equipment.

  73. GCC and Binutils are being shipped with routers? by AReilly · · Score: 1

    The lined FSF news item names GCC and binutils as licenced items that Cisco is not doing the right thing with. GNU libc I can understand (but thought that most of those sorts of gizmos used newlib), but gcc itself? How are GCC and Binutils being brought into the complaint?

    --
    -- Andrew
  74. Single-tasking OS; code signing by tepples · · Score: 1

    If it is GPL, make it a service and call it through a socket.

    This doesn't work in a few cases:

    • It doesn't work if your kernel isn't heavyweight enough to have a process scheduler. In the case of Linux, it is, but in the case of something that runs on a handheld or embedded device with 4 MB of RAM and a single-tasking OS, it might not be. (Example: Nintendo DS)
    • It doesn't work if the library is GPLv3 or LGPLv3 and your hardware's operating system requires all code to have been digitally signed by the hardware maker, unless you provide external hardware to run the covered code. (Example: DVRs and video game consoles)
    1. Re:Single-tasking OS; code signing by mlwmohawk · · Score: 1

      It doesn't work if your kernel isn't heavyweight enough to have a process scheduler. In the case of Linux, it is, but in the case of something that runs on a handheld or embedded device with 4 MB of RAM and a single-tasking OS, it might not be. (Example: Nintendo DS)

      Then that's just too bad. Pay someone to write it.

      It doesn't work if the library is GPLv3 or LGPLv3 and your hardware's operating system requires all code to have been digitally signed by the hardware maker, unless you provide external hardware to run the covered code. (Example: DVRs and video game consoles)

      If you have to make something as loathsome as a DRM protected anything, too f-ing bad.

    2. Re:Single-tasking OS; code signing by Ungrounded+Lightning · · Score: 1

      It doesn't work if the library is GPLv3 or LGPLv3 and your hardware's operating system requires all code to have been digitally signed by the hardware maker, unless you provide external hardware to run the covered code. (Example: DVRs and video game consoles)

      Part of the POINT of the GPL is to prevent things like that. B-)

      Code signing is only OK if the owner of the box has sufficient control that he can get the box to run stuff HE signed. If the manufacturer of the box has to sign it the owner of the box is locked out of his own box. So the manufacturer has to do without GPLv3 code.

      Boo Hoo.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  75. Boycotting the whole Internet? by tepples · · Score: 1

    Boycott Cisco

    I use a Netgear router, but Cisco products may be upstream of my home. I know of two residential Internet service providers in Fort Wayne, Indiana: Verizon and Comcast. Verizon has been seen palling around with Cisco, and so has Comcast. So how do I boycott Cisco without boycotting the whole Internet?

  76. Well past time. by Anonymous Coward · · Score: 1, Interesting

    CallManager 5.x, Redhat-based
    CallManager 6.x, Redhat-based

    Content Engine (CE560,CE590): Redhat-based

    MDS switches: Redhat-based.
    NM-NAM module for routers: Redhat-based

    Some 7600/Catalyst 6500 service modules: Linux-based.

    Want proof?
    Connect to the console for a cold boot... Redhat is explicitly mentioned.

    Heck, the update patches for some of the modules are UNSIGNED RPM's.

    The interesting thing is that the modules have router/switch backplane connectivity, i.e. that Linux on the module has a network interface that is attached to the router/switch, and the Router/Switch sees the module as one or more interfaces... Drivers anyone?

    The NM-NAM may also use other open source code as the basis for analysis and display of collected NetFlow data...

    The initial install images may contain more common file formats, (Gzip, cpio, tar) with proprietary headers prepended...

    Busting images open is an excercise for some geek with time and CCO access thats entitled to updates for the products they want to investigate.

  77. Re:Well, that may well be the result of this lawsu by Cramer · · Score: 1

    what caused Cisco *not* to comply?

    "We're a multi-billion dollar company. F*** off!"

    But don't be so quick to jump on Cisco. They bought this problem when they bought Linksys. Linksys has been doing this half-assed source code BS since the beginning of time.

  78. Re:Not for GPLv2 by Anonymous Coward · · Score: 0

    Once a business has released anything GPL, they are required to support it forever.

    Incorrect. They can discontinue support at any time.

    So why are they being sued by the FSF? Couldn't they just say that they are canceling support and avoid the entire issue.

    They already have an FTP site to download the source, so you're argument that the GPL is easy to comply with is, prima facia, false.

  79. Libraries and other 'infrastructure', maybe? by JSBiff · · Score: 1

    Someone please correct me if I'm wrong, but I think that when you compile C-code with gcc, particularly if you use .so files instead of a monolithic binary, doesn't the program have some dependencies on a libgcc.so or something like that? I suspect that you're right that the devices don't have a fully functioning GCC build environment, but I think they may distribute some components of GCC which are required to execute programs compiled with gcc. Same for binutils - I think you pretty much *need* the ld programs which are part of binutils to have a functioning Linux environment (unless you statically compile *everything*), because they implement and manage so loading on behalf of the kernel, no?

    1. Re:Libraries and other 'infrastructure', maybe? by Z-MaxX · · Score: 1

      No, the reason that gcc/binutils are part of the suit is because binary releases are made available on the Linksys web site for download.

      From the complaint:

      29. On May 12, 2006, Plaintiff notified Defendant of Defendantâ(TM)s unlawful conduct based upon its failure to comply with the Licenses for GCC and Binutils, which it distributed in object code form on its website.

      --
      Dr Superlove 300ml. I use my powers for awesome
  80. There are some limits. . . by JSBiff · · Score: 1

    The Free Software Foundation can only file suit when someone directly violates the copyrights of FSF software. There is a lot of GPL licensed software which the FSF does not hold copyrights for. FSF can't sue just because a program is licenses by GPL.

    To sue, you either have to be the copyright holder, or maybe (not sure on this one), a downstream 'recipient' of the software. E.g. if you bought a Cisco device with GPL'ed softare, and you couldn't get the source from Cisco, you might have grounds to sue them for breaching your rights wrt to the GPL as a recipient of a binary.

    I suppose that might leave some wiggle room for FSF to simply arrange to receive a copy from the violator (e.g. by a non-compliant linksys device at Best Buy), then file the lawsuit.

  81. Re:Hypocrisy in action by sjames · · Score: 1

    I would say that the resource imbalance demands a certain amount of mercy (rather than mercenary) in defending their copyrights. It also calls for them to be a LOT more careful with their accusations. They have been reprimanded by more than one judge so far for abuse of the legal process and for dragging out weak cases that probably shouldn't have been filed at all. That's not /., that's judges who generally have little or no problem with copyright law who believe that the RIAA has gone too far.

    Considering the RIAA's rather abysmal record in the cases where a defendant DOES manage to mount a defense, it would seem that as a whole they're more about an extortion racket than legitimate defense of copyright. One would expect some wins if their cases had any merit, you'd expect them to win once in a while.

  82. Re:Well, that may well be the result of this lawsu by Risen888 · · Score: 1

    I actually welcome this news, I think when these things happen it sends a strong signal that free software means business, and we're here to stick around. It might be "free speech," it might even be "free beer," but it ain't "freeloader."

    --
    Hey, I finally got my first freak! Took you long enough!
  83. ...which sounds like willful infringement to me by PCM2 · · Score: 1

    If you read the complaint [fsf.org], the FSF acknowledges that Linksys* has already released most of the code they are required to release. The big problem is that Linksys has a habit of releasing the binary versions first, then neglecting to release the source until the FSF complains and dragging their feet even then.

    That sounds like there's a helluva good case to be made for willful infringement. Penalties for copyright violation are a lot harsher when the infringer knew that the material was copyrighted, vs. if they were ignorant of its status. It sounds like the FSF has some statutory damages coming.

    --
    Breakfast served all day!
  84. FSF need to seek damages, not just compliance by bug1 · · Score: 4, Insightful

    If FSF forces them into compliance without cisco feeling some pain or regret then i suspect they wont hesitate to repeat their deeds.

    I understand FSF wants to be the good guys,they have principles and ethics, but Cisco is fighting from a different rulebook, one where the winner is the one with the most money, not the highest morals.

    The only way Cisco and other similar companies will accept defeat is you beat them on their own turf, playing by their own rules. That means take their money, as much as you can get.

  85. Re:Hypocrisy in action by _Sprocket_ · · Score: 1

    What about the hundreds of other stories about copyright infringement? Or, do you suggest that we should only consider the few stories that don't prove my contention?

    No - I'm suggesting you stay remotely on subject (i.e. binary drivers?!).

  86. Re:Not for GPLv2 by msuarezalvarez · · Score: 1

    There is a difference between supporting the code and having it sit in an FTP server.

  87. IOS has nothing to do with this by Fred+Ferrigno · · Score: 1

    The reason why this will be unsettling to Cisco is because some of the products have integrated key IOS files in order to retain backwards compatibility.

    IOS isn't even mentioned in the complaint. All of the products involved are Linksys products, which don't run IOS.

  88. hitler was evil by emmons · · Score: 2, Funny

    Hitler is evil. Microsoft is evil. Microsoft uses software licenses. That makes software licenses tools of evil.

    Therefore software licenses are tools of Hitler and must be destroyed!

    There.. can we be done with this now?

    --
    Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
  89. Funny... by Anonymous Coward · · Score: 0

    "in the course of distributing various products under the Linksys brand Cisco has violated the licenses of many programs on which the FSF holds copyright, including GCC, binutils, and the GNU C Library. In doing so, Cisco has denied its users their right to share and modify the software."

    ===========

    Funny - Linksys probably was doing it long before Cisco bought them....so they waited a bit after Cisco purchased Linksys, and are now going after the big fish...

    Leave it to the FSF - must stand for Foolish Stupid Fucktards

  90. I don't get it either by huckamania · · Score: 1

    It looks like Cisco was, at some point, distributing the binaries for GCC and other things necessary to build their firmware. From the standpoint of their users, this was a nice thing to do. However, they didn't provide the source for GCC or the other things, which immediately and automatically removes their rights to distribute GCC and the other things.

    According to the complaint, "On May 12, 2006, Plaintiff notified Defendant of Defendant's unlawful conduct based upon its failure to comply with the Licenses for GCC and Binutils, with it distributed in object code form on its website." (That's the first contact that the FSF acknowledges, which is 2 1/2 years, not the 5 that everyone keeps repeating.)

    It should be noted that their products did not require GCC or the other things to be distributed with them, it was only provided so that their customers could build the firmware. WTF, isn't that the whole purpose of the f'ing GPL? To empower the end user.

    From there, it appears that other products also had firmware that needed GCC and other stuff, which sounds basically like saying there were multiple links on their website for each. The rest of the complaint is small things like missing build scripts and outdated source.

    It should be an interesting trial. I just hope that Cisco chooses trial by jury, that will make it even more interesting.

    1. Re:I don't get it either by Anonymous Coward · · Score: 1, Interesting

      According to the complaint, "On May 12, 2006, Plaintiff notified Defendant of Defendant's unlawful conduct based upon its failure to comply with the Licenses for GCC and Binutils, with it distributed in object code form on its website." (That's the first contact that the FSF acknowledges, which is 2 1/2 years, not the 5 that everyone keeps repeating.)

      I believe there is a three-year statutory limitation, so they can only persue violations that occured within the last three years.

  91. Bad Timing Award by Anonymous Coward · · Score: 0

    It's too bad that the guy at Cisco in charge of finding GPL violations - Caleb Mulford - found a bunch that were promptly ignored by executive officials because a stink wasn't being made yet (ala this article) recently threw himself in front of a train.

  92. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    Wanker.

  93. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    You would ask mercy of them but would show them no mercy. You keep trying to justify you position by stating they should treat you better than you treat them.

    You and your ilk continually violate their copyrights, then demand they show you mercy when you are caught. You taunt the giant, knowing its wrath, then cry for help and mercy when it turns it strength on you.

    Your ilk has the mindset of children.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  94. Re:Hypocrisy in action by AcidPenguin9873 · · Score: 1

    "We want users of information to be able to freely modify and share it without restriction."

    But what you're missing is that this is not possible in a capitalist society where zero-cost-of-replication "Intellectual Property" (IP) is considered to have value. Let me break it down for you.

    Businesses amortize the development cost of a product in with the manufacturing costs, and they come up with a sale price which covers both. That way, if they sell enough copies of the product, they cover the initial cost of developing the product, as well as the production costs. Fortunately for them, the value of the product is both in the idea/design/creation, as well as in the physical item itself. So they can get away with charging a price *higher* than just the manufacturing costs, and people have to pay it because they can't manufacture it themselves.

    With IP, the production cost is 0. The *entire cost*, and also the *entire value* of the IP, is in the idea/design/creation. The cost of replication is zero, and there is no value in any physical item because there is none.

    Say I produce some non-tangible IP (code, music, hardware designs in Verilog, pictures, film, whatever) which in its final form is just some bits on my hard drive. My IP, in and of itself, has worth because other people enjoy it, or because they want it but cannot produce it on their own. Producing that IP took many months or even years of my time. I'd like to be able to sell my IP for whatever the economy deems its *creation* value so I can cover the cost of creation, and maybe make some profit like any good capitalist should be able to.

    So how do I go about getting paid? In an "information wants to be free" society, I can only get paid for the first instance of that IP. Every other copy nets me $0, because once the information is out there, it's free. So, I better set my price for that first copy really high, because that one lump sum is all I'm ever going to get, and I have to cover months or years of development costs in a single shot. Since the price is so high, no one can afford my IP. The only price anyone can afford won't cover my development costs. Learning from this, I then decide to never do IP development again, since I am now broke and penniless. (Remember, we're still in a capitalist society). IP, and all the good things that come with it, die a quick death.

    In a perfect communist society, I wouldn't mind putting a year into the creation of some IP that I would give away for free, because over the course of that year I'd have my needs met for "free" as well.

    The old arguments are that you can't sell just the IP - you have to sell "service" or a "live show" or something else which isn't zero-cost-of-replication, and in doing that, recoup the initial creation cost. But whenever someone makes that argument, they imply that the IP itself has no dollar value because it can't be sold for anything more than $0. I strongly disagree with that implication.

    Anyway, what we capitalists have come up with is this artificial restriction on IP, so that IP creators can amortize the cost of conception/design/creation over more than one sale. The only way to enforce this is to restrict what people do with the IP. It's up to the creator of the IP what those restrictions are. FSF might choose one way of restricting the IP (and ironically that restriction basically throws to the wind the whole point of the restriction), but that's not the only restriction possible.

  95. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    And, that is hypocrisy.

    Nonsense. Copyright is a legal tool, nothing more. Depending on the context a tool is used in it may be good or bad. Deal with it.

    You are the hypocrite actually; refusing to acknowledge that tools have nothing to say about morals and ethics even though you know full well it's the [mis]use of the tool that matters, not what the tool is. As but one example gun use can be good (defending democracy) or bad (defending dictatorships).

  96. Re:Hypocrisy in action by bug1 · · Score: 1

    You would ask mercy of them but would show them no mercy. You keep trying to justify you position by stating they should treat you better than you treat them.

    You and your ilk continually violate their copyrights, then demand they show you mercy when you are caught. You taunt the giant, knowing its wrath, then cry for help and mercy when it turns it strength on you.


    Its not about the copyright laws themselves, its about what they are used to achieve.

    FSF uses copyright to achieve good things, Music and Movie cartels use copyrights to do bad things.

    Try thinking a bit deeper, its about intent and purpose.

  97. Re:Hypocrisy in action by SpacePunk · · Score: 1

    The goal seems to be 'free as in beer', not 'free as in speech'.

    GCC, and GNU C are tools, nothing more. It's like if I built something with Black and Decker tools, Black and Decker could sue me for not making the thing that I created free (as in beer).

    For years the GPL was being presented as being non-viral, but current events speak otherwise.

    Fuck em, I'm going back to using Microsoft tools.

  98. Re:Hypocrisy in action by bug1 · · Score: 1

    In this case, you are saying "We should be able to use the copyright laws to protect our copyright. But, people who don't believe as we do should not be able to protect their copyright in the same way"

    No, we (err I) say we should be able to use copyright laws to promote the use and distribution of software. The music and movie cartels should also be allowed to use copyright to promote the use and distribution of their works.

    The difference is that the music and movie cartels want to promote the use of their works in a more restrictive manner.

    Again, its not about copyright, its about what its used to achieve.

  99. it's extremely useful to them by r00t · · Score: 1

    Even if they never look at the code, never pay a consultant to add a feature, etc., the source code is useful.

    It's like a mark of quality. In this case, "quality" means that misbehavior is unintentional. There might be bugs, but it won't be an evil mess of spyware and DRM.

    Looking at free downloads, you can pretty much answer "Will I get screwed?" by asking if the source is available. To some extent, this even works for things that aren't free downloads.

    This is all without getting into the issue of having your business depend on the whims of some software developer who may discontinue their product or go out of business. We so quickly forget how many Y2K problems were unfixable because the source code was unavailable.

  100. Re:Hypocrisy in action by init100 · · Score: 1

    May I humbly suggest that there are more than one or two slashdotters? There are many thousands of them, many with wildly different opinions. Is it so hard to imagine that there could very well be different subsets of the Slashdot crowd having different opinions on various matters? Then there would be no hypocrisy.

    Slashdotters are not one uniform group of people, with one set of opinions. But of course, what can I really expect from a troll?

  101. Re:Hypocrisy in action by mrchaotica · · Score: 1

    So what?

    See, that's the thing: I completely understand your argument. No really, I do!

    The thing is, though, that I simply don't care. It's not my problem when creators of Imaginary Property can't find a working business model for themselves. They're perfectly welcome to go find something else to do with their lives. It's also not my fault that they want to delude themselves into thinking that they can stop the copying. No matter what DRM or legal measures they try to go to, it's just not going to happen. And that's nto some "hippie idealism;" that's just a pragmatic statement of fact. They can either acknowledge it and deal with it, or they can thrash and die.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  102. Re:Hypocrisy in action by mrchaotica · · Score: 1

    Look, if you're going to be willfully stupid and refuse to understand what I'm telling you, then you might as well not reply at all.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  103. Step 3 Profit by Anonymous Coward · · Score: 0

    What is the current going rate per copyright violation? I bet Cisco use lots and lots of these fandangled linux things.

  104. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    "FSF use copyright to achieve things I think are good because they benefit me. Music and Movie cartels use copyright to make a profit and I think that is a bad thing."

    There fixed that for you.

    By the way, copyright law exists for the benefit of the copyright holder. Its intent and purpose is for the betterment of copyright holder, not you and not other people.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  105. Re:Not for GPLv2 by morgan_greywolf · · Score: 1

    Bingo. Lots of poeple have open source software sitting on their FTP servers that they never plan to support ...

  106. Re:Hypocrisy in action by bug1 · · Score: 1

    copyright law exists for the benefit of the copyright holder. Its intent and purpose is for the betterment of copyright holder, not you and not other people.

    Google "purpose" and "Copyright" and you will see your wrong.

    "The primary purpose of copyright law is not so much to protect the interests of the authors/creators, but rather to promote the progress of science and the useful arts--that is--knowledge.To accomplish this purpose, copyright ownership encourages authors/creators in their efforts by granting them a temporary monopoly, or ownership of exclusive rights for a specified length of time. However, this monopoly is somewhat limited when it conflicts with an overriding public interest, such as encouraging new creative and intellectual works, or the necessity for some members of the public to make a single copy of a work for non profit, educational purposes." - http://www.lib.byu.edu/departs/copyright/tutorial/module1/page3.htm

  107. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    So, you think that copyright should not be used in the manner that it was orignally intended but rather in the manner you see fit.

    Here is the text from the Constitution which provides for the creation of patents and copyrights:

    To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries

    You will notices it does not say anything about promoting "the use and distribution" of works. It states that, for a limited time, authors and inventors have an exclusive right to their works to do with as they see fit. If they wish to make money on it, or even get rich on it, it is their right to do so. The authors and inventors have sole right and have the ability to sell that right to others. And, if those others who buy the copyrights (publishers, studios, RIAA, etc) want to make money from the work, it is their right.

    The intent of the law is to benefit the copyright holder as the copyright holder sees fit. If they want to "promote the use of their works in a more restrictive manner", it is their right to do so. You may not agree with it, but you don't fucking matter because it is not your copyright. Don't like it, don't use their copyrighted work.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  108. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    From your own post:

    To accomplish this purpose, copyright ownership encourages authors/creators in their efforts by granting them a temporary monopoly, or ownership of exclusive rights for a specified length of time.

    And, they can sell those rights, in whole or in part, or just a license to use the work. The monopoly exists for the betterment of copyright holder, not you and not other people.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  109. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    I suggest you try actually reading the comments. Yes, there are many slashdotters and many of them are hypocrites when it comes to this issue.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  110. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    Look, if you are going to be willfully stupid and refuse to recognize the law and its intent, maybe you should shut your hole, shithead.

    Copyright holders of proprietary information (like the RIAA) try to prevent it from being free to modify and share without restriction, so we oppose them.

    It is their right to do that. That is why it is called copyright. It gives the right to control the copying of a work to the holder. You don't like that companies use copyright against you to their benefit. You bitch and whine and decry copyright and copyright litigation and copyright holders defending their rights. Then, you turn around and use copyright against them to your benefit and talk about how great it is.

    You talk about your rights to other people's copyrighted work. You don't have any right to other people's work.

    Refusing to see your hypocrisy does not make the hypocrisy go away. That just makes you an asshole.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  111. Re:Hypocrisy in action by bug1 · · Score: 1

    "The intent of the law is to benefit the copyright holder as the copyright holder sees fit." My POV is that the intention is to empower the copyright holder (which is a benefit in itself), whether they use that power to further benefit themselves or benefit others is not stated, and you should make assumptions. Do you have any argument to support your POV that the purpose of copyright law is benefit the copyright holder exclusively ?

  112. Re:Hypocrisy in action by bug1 · · Score: 1

    (damnit should have used preview button)

    "The intent of the law is to benefit the copyright holder as the copyright holder sees fit."

    My POV is that the intention is to empower the copyright holder (which is a benefit in itself), whether they use that power to further benefit themselves or benefit others is not stated, and you should NOT make assumptions.

    Do you have any argument to support your POV that the purpose of copyright law is benefit the copyright holder exclusively ?

  113. could backfire by firewood · · Score: 1

    One of these days the FSF will go after some organization big enough to buy enough legislators or legislation to take the teeth of U.S. copyright law (but only as it applies to the more psuedo-coercive OSS licenses. e.g. not the way Stallman dreams).

    .

  114. Re:Hypocrisy in action by AcidPenguin9873 · · Score: 1

    It's not my problem when creators of Imaginary Property can't find a working business model for themselves. They're perfectly welcome to go find something else to do with their lives.

    That's the scary thing! What if all IP creators decided they'd be better off if they didn't try to survive on thinking up/designing/creating new non-physical goods because they can't get paid? What would happen if all the auxiliary software-as-a-service type business models fail? I sincerely hope some smart people keep finding business models to support the creation of IP, so that IP creators can continue doing their thing and not having to take jobs at McDonald's or selling shoes or something. Lots of innovation and ideas are at stake. Then it might become everyone's problem.

    I realize this is almost certainly a non-plausible scenario, that taken to that extreme the free market would find a way to reward IP creators monetarily. But I'm trying to make a point by taking the limit of your utopian "information should be free" idea, and apply that same point to today's situation.

    No matter what DRM or legal measures they try to go to, it's just not going to happen.

    I hate DRM too, I wish it would die. But that's orthogonal to my point: that IP has value, and the IP creator deserves to be compensated appropriately for that value, somehow. I obviously don't know how given the zero-replication-cost problem.

  115. It's moot point anyway by Darkk · · Score: 1

    Much as I like to see fairness of this deal but Cisco will prevail simply because they have integrated themselves tightly in several key areas including the governments and the military who uses Cisco networking equipment. Cisco will not be able to release the source code due to national security concerns, same thing with Microsoft.

    And I think Cisco knew this from the beginning.

  116. Re:It's about time you checked you theories by Anonymous Coward · · Score: 0

    Even if your allegations about key IOS files is true, This is the worst kind of GPL FUD. Repeated misrepresentations like this hinder the understanding and acceptance of Free Software, I fear. 1) there is no "automatic" relicensing, and 2) you seem to be intimating all of IOS. Unless you're saying that all of IOS was linked with GPL code, then how can anyone ask for a remedy that all of IOS be licensed under GPL?

    What are you talking about? If I release my code under GPL, just what empowers a court to limit my freedom by prohibiting me from making additional or alternate agreements? "I don't believe such a dual license has ever been held up in court." is a sign you haven't been hanging around a courtroom lately. Not only are alternate licenses legal, but defendants can and do routinely argue innocence via alternative, even incompatible, theories, instruments, and findings of fact.

    Back to Groklaw boot-camp for you.

  117. Re:Hypocrisy in action by bug1 · · Score: 1

    From your own post "The monopoly exists for the betterment of copyright holder, not you and not other people." Where is it written that other parties arent supposed to benefit from copyright, i dont know what planet your living on, but nobody i know would buy something that has no value to them. The copyright holder cannot benefit in any practical way from copyrighted works unless the copyrighted works benefit society, where else are they going to draw their benefit from ? Yes a copyright holder benefits from copyright laws (at least by having control), BUT THEY DONT AND CANNOT BENEFIT EXCLUSIVELY, the benefit has to come from somewhere... that somewhere is OTHER PEOPLE, i dont know why you cannot understand such a simple concept. Im sure you must be trolling me...

  118. Oligopoly by tepples · · Score: 1

    If the manufacturer of the box has to sign it the owner of the box is locked out of his own box

    But what set-top box doesn't lock its owner out?

    1. Re:Oligopoly by badkarmadayaccount · · Score: 1

      Then it's okay, I guess.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  119. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    You're an idiot. Have a nice day!

  120. Re:Hypocrisy in action by mrchaotica · · Score: 1

    It is their right to do that.

    No, free speech is a right (along with the rest of the stuff listed in the Bill of Rights). Copyright is a privilege of Congress, for the explicit purpose of "promot[ing] the progress of science and the useful arts" and nothing else.

    It was the right of fathers in ancient Rome to kill his child if he wanted to. Should we honor that "right" too?

    You don't have any right to other people's work.

    On the contrary, they don't have the right to steal their work from the Public Domain! So there! See, I can jabber on about "rights" too!

    You're assuming that your particular ideology is the Gospel Fucking Truth, and deluding yourself into thinking that anyone who disagrees -- even when they're reasoning from a different set of axioms -- is a hypocrite. Here's a newsflash: that makes you the asshole, not me!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  121. Bad way to go... by Anonymous Coward · · Score: 0

    FSF is loosing the head...

    First a friendly free software evangelist, as it should be, then gone deep thanks to richard stallman's stupidity and now they totally loosed their head.

    I quit supporting free software from now on until FSF and Stallman disappears from the scene in a definitive way.

    Those two parties are the DRM of the free software.

  122. You have to include that though by Anonymous Coward · · Score: 0

    There was a case recently where a company forgot to put that clause in and the contractor kept the copyrights.

    Copyrights must be specifically transferred. This can be because the contract says "all work for this contract must give copyright to the buyer" but it has to be there.

    And who knows that about copyright and source code?

    Nobody if they aren't programmers or lawyers.

    And if you're a programmer, you could write the code yourself.

  123. Re:GPL vs BSD by shutdown+-p+now · · Score: 1

    This is why free licenses such as BSD should be adopted for any commercial project. Avoid viral licenses such as *GPL.

    So far, not a single place I have worked in was an OSS shop or produced OSS. Nonetheless, in all of them I had used at least one bit of LGPL code, and occasionally GPL as well. All that's needed is lawyers and managers and developers with understanding of what it is - hardly rocket science.

  124. Re:RTFC: (Complaint) FSF IS seeking damages by JetScootr · · Score: 2, Insightful

    But just enough to pay for the litigation hassle. Judges (usually) pay close attention to the level of courtesy and maturity shown by the litigants prior to filing the suit. By bending over backwards being nice and trying to work things out, FSF has set themselves on the moral high ground, which (usually) pays back big time in the judge's decision.

    --
    Pavlov wouldn't be so famous if he'd used a can opener instead of a bell.
  125. Re:Hypocrisy in action by LarsG · · Score: 1

    I hate DRM too, I wish it would die. But that's orthogonal to my point: that IP has value, and the IP creator deserves to be compensated appropriately for that value, somehow. I obviously don't know how given the zero-replication-cost problem.

    Is it really zero cost? While the cost is going down, and will go further down in the future with better/faster/larger/cheaper storage devices and transmission networks there is always going to be some cost in maintaining the distribution network, cataloging, indexing, making sure metadata is correct, making sure the content is malware free, updates/fixes. As such, people might find that an all-you-can-eat DRM-free subscription to a music label or software company might be preferable even if the same content is available for free on P2P.

    Information goods also don't exist in a vacuum, communities form around many of them. Downloading an album from piratebay does not give the same experience as being a member of a fan club / community and interacting with the rock band. Downloading a software program from P2P is of less value than being part of a community around the author of the software. For information goods where you have a large and/or very faithful fanbase/community, it might be possible for the creator to extract sufficient income from them. (I think I once saw a paper showing that a book author or a band could get a fairly decent living out of a surprisingly small number of faithful fans)

    There is also the fact that IP creators are in a rather privileged position compared to other workers. For example, the need for farmers dropped because the work they did were replaced by machines; the same thing has happened time and again, human labor replaced by machines. I don't really see how machines can replace the need for human creativity. Unless we create true AI, we will always need IP creators. We will always want music, books, better medicines, software.. If the market can't find solutions for how to compensate them, government will have to step in.

    --
    If J.K.R wrote Windows: Puteulanus fenestra mortalis!
  126. long story short... by SharpFang · · Score: 1

    If you hesitated about buying a Linksys router running Linux, hurry up.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  127. WSA, not BSD! by hbr · · Score: 1

    Or when are MS going to release the BSD code in Windows, including all enhancements?

    Yeah, then we could all use WSAGetLastError().

    We could ask Bill, but EWOULDBLOCK it.

  128. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    Oh noes. But if information is free, how will we monetize it to sinergify paradigm shifts over parallelized computation?

    (Protip: some people will _never_ understand the concept and importance of "public domain" and "free culture")

  129. Re:Hypocrisy in action by Anonymous Coward · · Score: 0

    woah. mrchaotica 1 - 0 DoucheV1.0

  130. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    I see you are resorting to the old tactic of putting words in other people's mouths. I said that the copyright holder has an exclusive right to his work, not that the purpose of the law is to benefit the copyright holder exclusively.

    If you are going to lie, you may as well shut the fuck up now.

    I have the argument that the law provides the copyright holder an exclusive monopoly, for a limited time, on his creation and he can do with that creation what he sees fit. The creation is solely his, as is the rights copy and/or sell the creation and the right to said creation.

    What exactly is the copyright holder empowered to do, if not benefit from his creation as he sees fit? Is he only empowered to benefit others? That seems to be your argument, that copyright is only valid if the copyright holder only uses the copyright to benefit others.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  131. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    You want to quote the Constitution, maybe you should try quoting the whole sentence, you lying sack of shit:

    To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries;
    (emphasis added)

    Oh, look, they use the word RIGHT. Congress grants a legal right to authors and inventors.

    It was the right of fathers in ancient Rome to kill his child if he wanted to. Should we honor that "right" too?

    Do we live in ancient Rome? No, we do not. Why would we honor a right that is not part of our laws and cultures? Maybe you shouldn't try such a pathetic red herring, shithead.

    You don't have any right to other people's work.

    On the contrary, they don't have the right to steal their work from the Public Domain!

    1) One can not, by definition, steal from the Public Domain.
    2) That statement makes no sense in relation to what I said. Works come into public domain in a number of ways, including but not limited to one giving up one's copyright and one's copyright expiring. You don't have any right to other people's copyrighted work until and unless that work passes into the public domain. There, happy now, dumbass?

    I suggest you look a little closer, fuckwit. You assume that your ideology allows you to ignore the law and other people's rights. But then you use those same rights and laws, which you have decried other having and using, against other who do not share your ideology. That is hypocrisy in action.

    You are not just an asshole, you are an ignorant, arrogant, self-righteous, hypocritical asshole.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  132. Or use GPLv3 by Anonymous Coward · · Score: 0

    LGPL is a nice answer to this because it doesn't have this horrible linking clause

    Or another way to avoid linking problems is to use GPLv3 instead, at least for those packages that are under a "GPLv2 or higher" license.

    Eben Moglen went to a lot of trouble to redefine the language used in GPLv3 so as to get rid of GPLv2's very fuzzy use of the concept of derivation, which was so fuzzy that every man and his dog developed a different interpretation. Eben replaced all that by "conveying", and defined it very precisely so that if there is no conveying then there is no license virality.

    This makes it black and white now: GPLv3 doesn't trigger on *usage* at all (it's not a usage license), but only on the *conveying" that occurs at distribution. As a result, linking for usage doesn't cause virality, because usage isn't conveying. In other words, Eben made GPLv3 consistent with the Copyright Office's notion of "derived work", which required an original work of authorship to be partly copied into a different work for it to be considered "derived", and mere usage of a work of authorship had nothing to do with creating derived works from it.

    This now applies to the latest GPL too: if dynamic linking is used for the purpose of *usage* of a GPLv3 work, then conveying is not occurring and hence license tainting is not possible either. That would keep Cisco out of trouble, unless they actually copied GPLv3 code and modified their copy, in which case nothing will save them of course. (Static linking is a mixture of usage and replication, so the grey area would probably end up in court too, ie. best avoided, whereas dynamic linking is the primary example of normal usage of a library, and hence entirely free of conveying taint.)

    Analysing Section 0 of GPLv3 with a toothcomb is actually very eye-opening. If all you know is GPLv2, you're in for a surprise.

  133. Legal Stalingrad? by MarkvW · · Score: 1

    All the posts that I have seen on this thread assume that Cisco will lie down and admit that their software has copied GPL'd code. That makes sense. They appear to be pretty much caught dead to rights on that one.

    There is another question, however: Is the original GPL code subject to copyright protection? In other words, Britney Spears can copy my songs note for note and word for word, and she won't be able to successfully sue me if I copied those songs note for note and word for word from Johann Sebastian Bach.

    Think for a moment about how utterly EXPENSIVE it is to prove such a point or defend such a point. Think how COMPLICATED this is. You need really expensive experts to prove this kind of stuff and you pay them godawful fees per hour to do their work.

    If the FSF is smart, they ought to be able to enlist a LOT of skilled programmers to grok on this (think about the SCO litigation). They can prioritize and organize their expert code review among expert DONATED help. I would expect (or hope) that the FSF has people organizing this kind of cooperative, coordinated help right now!!

    Cisco will have to pay for their labor intensive expert code review--in a declining economy. They'll also have to pay their big-firm lawyers. Those firms salivate like Niagara Falls when they see cases like this.

    The point of all this is that Cisco ought to roll over on its back and get really submissive right now because if they want to win their lawsuit against the FSF they are going to have to pay and pay and pay. Cost-benefit tips way in favor of an early amicable settlement.

    No early settlement means protracted war. Cisco will have to put scarce resources into its attack on GPL'd code (lawyers and experts), while the FSF has lots of experts motivated and available to donate expert help. This is where the Stalingrad metaphor comes in. The GPL can afford to throw more bodies at the problem than Cisco can.

    I sure hope this settles quickly and amicably.

    1. Re:Legal Stalingrad? by MarkvW · · Score: 1

      Sorry: I should have said that I won't be able to successfully sue Britney if I copied the note for note and word for word from Mr. Bach.

  134. Re:Hypocrisy in action by mrchaotica · · Score: 1

    Oh, look, they use the word RIGHT. Congress grants a legal right to authors and inventors.

    I turned RIGHT a couple of times driving home today. And look, here's a Wikipedia article about the RIGHT whale. And I bet that guy on the game show last night was happy that he got the RIGHT answer!

    Try getting yourself some reading comprehension skills sometime! "Right" is just a word. It has different meanings in different contexts. In particular, there are two kinds of "rights" in relation to the government. There are fundamental rights, as in the Bill of Rights, and there are incidental "rights" which really aren't rights at all, but are rather privileges conferred by the government.

    For example, I could say that my driver's license gives me the "right" to drive. But it's not really a right; it's a privilege granted by the government. In contrast, the right to free speech is a fundamental right, because it is inherent and irrevocable.

    So, how do you tell the difference between fundamental and incidental rights? Well, when referring to fundamental rights the Constitution uses language like "this right shall not be infringed." It explicitly affirms that the right was preexisting -- not granted by the government -- and that the government cannot take it away. In contrast, the copyright clause says "Congress shall have the power... [to secure the right]." That's not a description of a "right" at all; that's a description of a privilege granted by Congress. Note that "hav[ing] the power" doesn't mean Congress must use that power. If it wanted, Congress could invalidate every copyright in existence simply by passing a law (not an Amendment) abolishing it. Also note that copyrights explicitly may only exist for limited times. They expire. Fundamental rights do not, and cannot, expire; therefore "copyright" is not a right!

    1) One can not, by definition, steal from the Public Domain. 2) That statement makes no sense in relation to what I said. Works come into public domain in a number of ways, including but not limited to one giving up one's copyright and one's copyright expiring. You don't have any right to other people's copyrighted work until and unless that work passes into the public domain. There, happy now, dumbass?

    The only thing that stops everything from entering the Public Domain immediately is congressional privilege. That privilege is conferred -- or is supposed to be conferred -- only when it would "promote the progress of science and the useful arts." By asserting copyright in such a way that it fails to "promote progress," copyright holders violate their part of the bargain and prevent works that should enter the Public Domain immediately from doing so. That, in a colloquial sense, is "stealing" from the Public Domain.

    I suggest you look a little closer, fuckwit. You assume that your ideology allows you to ignore the law and other people's rights. But then you use those same rights and laws, which you have decried other having and using, against other who do not share your ideology. That is hypocrisy in action.

    I advocate using copyright to promote progress, as intended in the Constitution. I oppose people who want to pervert it into performing exactly the opposite function! If you still think that's somehow "hypocrisy," then no word even exists to sufficiently describe how idiotic you are!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  135. Re:Hypocrisy in action by bug1 · · Score: 1

    I said that the copyright holder has an exclusive right to his work, not that the purpose of the law is to benefit the copyright holder exclusively.

    You said, and i quote "The monopoly exists for the betterment of copyright holder, not you and not other people."

    Your saying that the monopoly (from copyright law) exists to benefit the copyright holder and not other people, sounds pretty exclusive to me.

    But maybe your didnt say what you meant :/

    And whats with the swearing in a lot of your responses, do you feel threatened ?

  136. Re:Hypocrisy in action by DaveV1.0 · · Score: 1

    That is right, I did say that. The monopoly exists for the betterment of the copyright holder. The copyright holder gets to decide what that is. Not you, shithead. You got that? Or do you need beaten into your fucking head?

    I am swearinbg because I am frustrated with you and your ilk. You refuse to see that you do nott get to be the arbitars of what is best for the copyright holders. You have the mindsets of three year olds, "he world should revolve around me and what I want. Fuck what everyone else wants for themselves and what their rights are. Gimme Gimme Gimme." But, when someone does the exact fucking thing to you, you piss your collective pants, cry "No fair!" and throw a tantrum.

    You people are the absolute worst of humanity.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  137. Re:Well, that may well be the result of this lawsu by badkarmadayaccount · · Score: 1

    I want that on a t-shirt.

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  138. Re:Hypocrisy in action by bug1 · · Score: 1

    The copyright holder gets to decide what that is. Not you, shithead. You got that? Or do you need beaten into your fucking head?
    You people are the absolute worst of humanity.

    And in the same post you accuse me of throwing a tantrum.