Slashdot Mirror

← Back to Stories (view on slashdot.org)

SCO DOS'ed

Posted by michael on from the world's-smallest-violin dept.

Thomas Cort writes "BusinessWeek has an article about a DDoS attack against SCO. "At 10:45 a.m., the Unix and Linux seller was hit by a distributed denial-of-service attack (DDoS) that hampered its Internet operations, said SCO spokesman Blake Stowell ... the Utah-based company has incurred the wrath of many Linux enthusiasts infuriated with its lawsuit against IBM ... SCO's Internet service provider, ViaWest, told SCO that about 100 high-speed T1 data-transmission lines of network capacity--about 90 percent of its total bandwidth--was being consumed in the attack.""

5 of 519 comments (clear)

  1. Good Point. by robbyjo · · Score: 5, Informative

    For those of you who's lazy to click, here's two paragraphs summary:

    The upshot of this GPL paragraph is that by relicensing their own code under non-GPL terms, once having knowingly released said code under the GPL, they have forfeited their own rights to distribute Linux. Or, at least that's how I interpret it. Further, the same paragraph states that the rest of us still hold full GPL rights to the code SCO originally licensed to us via the GPL.

    The bottom line to us would appear to be that, even if there is IBM-introduced, SCO-owned, infringing code in Linux, it is now officially released under the GPL by the copyright holder, SCO. And, of course, no sanitizing of the Linux kernel is necessary. This spat should have no effect on Linus, Red Hat, SuSE, or any other Linux developer or distributor.

    --

    --
    Error 500: Internal sig error
  2. Re:Gotta love the way... by Geopoliticus · · Score: 5, Informative

    The SCO guy didn't say that it was, "unprofessional for us linux boys to do this sort of thing."

    What he said was, "It's one thing to have a complaint with SCO's lawsuit or with our position in terms of code being found in Linux. It's another thing to deal with that in an unprofessional way."

    The article does paint a picture of an outraged linux community, but doesn't come out and say that it was them who did it.

    Please read more carefully.

  3. The lines of code they are referencing are........ by conteXXt · · Score: 4, Informative

    contained in the SYS V startup scripts.

    It's time to move to bsd style startups to avoid having SCO pull an RIAA (removing them)

    --
    The truth about Led Zep should never be told on /. (Karma suicide ensues)
  4. But IBM did not take code from SCO Linux by mnmn · · Score: 4, Informative


    The code that was given to IBM was given as Unix, not under GPL. SCO claims IBM released THAT code under Linux. They can release it now.. and IBM could even claim they took the code released under SCO, incorporated that GPL code into their products, but theyre not claiming that now. Theyre claiming they never did release SCO code under Linux. We dont even know what product of Linux is accused of containing tainted code.

    Therefore they should be dDosed :)

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  5. Email SCO CEO... by furry_wookie · · Score: 3, Informative

    "If any of you have questions, concerns or comments, feel free to contact me directly at darl@sco.com or my direct dial office number is 801-932-5820.

    Very sincerely yours,

    Darl McBride
    President and CEO
    The SCO Group"


    found here

    --
    -- Given enough time and money, Microsoft will eventualy invent UNIX.