Slashdot Mirror
SCO DOS'ed
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.""
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
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.
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
Isn't SCO's nework infrastructure in Utah, not Santa Cruz?
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
Kinda ironic that this is the same company that uses the phone number 1-888-GO-LINUX. It's right there on their feedback page.
SCO have made the code publicly available, long before they prepared or made complaint against IBM
Many people have mentioned this over the last few weeks. There's a problem in this logic.
The GPL that you mentioned is being imposed on the code by the party that contributed it (IBM, in this case). Even though SCO is distributing it as SCO Linux, the code is still the property and responsibility of the contributer. SCO can not be held responsible for any IP infiringement done by the developers.
Hence, if IBM put any of SCO's code in the Linux kernel and released it under the GPL, it's IBM who infringed SCO's IP.
Not that I am a SCO supporter, just pointing out the problem with the way some of us are looking at the issue.
I copied this sig.
"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.
I like the worlds-smallest-violin dept.
Here is a 2.5-inch model
Table-ized A.I.
It was unintentional until they discovered the code.
Today, Sunday May 4 2003, 2:23 am MDT, they know their code is in it, and they are still distributing it under the GPL. They'd have had a case if they'd pulled it, but they haven't. From this point forward, SCO, by knowingly distributing the code under the GPL, are knowingly licensing that code for use under the GPL.
This, by the way, also hurts their damage claims. "If this code is so valuable that its distribution under the GPL caused you harm, then why did you knowingly continue to distribute it under the GPL?"
Let's see how long until SCO picks up on this and stops distributing Linux with the disputed code in it. My bet: never.
They may have been running BGP with two T3's. :)
:)
:) It works well for them though, they're putting servers as close as you can get to the clients. Their's spiffy NOC is an office where their guys watch their stuff from.. My NOC is wherever I happen to be. :)
:)
:)
:) Rows and rows of WinNT (or Win2k, I don't remember now) DELL's. The machines were like 6u tall sitting on shelves in open racks, all inside a huge cage.. All I could keep thinking to myself was, "I could do all that with one Linux machine".. hehehee. I think I still have the unauthorized pictures stashed somewhere..
As for them having their own datacenter, don't be surprised if they don't.. Having your own datacenter is cool -n- all, but really overkill for many situations. We don't use our own, we use other providers for that. That way, we have the luxury of living in a datacenter, without actually having to run the facility. If you go somewhere like Switch&Data, you already have major providers with available bandwidth in the facility. It takes longer to do the paperwork than to actually get your connection wired up.
Don't be surprised to find out many companies don't have their own datacenters.. They may just be a cabinet or a cage in another companies datacenter. Take Akamai for example.. Read through all their stuff. Sounds really impressive.. In 3 colo facilities that I know of, they have an individual rack in each with a bunch of servers. They're easy to spot. Scan the room for a rack full of identical machines with pretty blue lights.
Someone once asked me "where's your NOC?".. I held up my phone. He asked, "Should I call them?".
"No. BoT pages 4 people if there are problems. He'll repeat the pages every 30 minutes until it's resolved."
"What about your network administration?"
"Four people can run any of the servers. Two of us do most of the work, another takes all the easier work (he's still learning), and the fourth plays boss sometimes."
"What if a server goes down at 4am?"
"Someone wakes up to the incessent ring of their pager, and fixes it. If it's one of many (like most of our servers), it doesn't really matter. If it means someone driving out to a colo, we're all within 20 minutes of our respective colo's."
"What if it's a hardware problem?"
"Then we fix it."
We thought about doing the 24/7 shifts, and crap like that. Honestly, the network runs itself, the machines maintain themselves, and normally we don't have to mess with anything. The only problems we've had lately are stupid people beating up on stupid free-hosting machines, but we just add or modify things to stop them from breaking things. For a while particular IP's would flood requests for movies, so now they're throttled, and if they try too hard they're blocked at the firewall. Last week some twits were hitting a CGI too hard, so I lowered it's threshold for abuse. Now if it thinks someone is trying, it'll slow them down. I don't see why places like SCO bitch that someone's doing a DoS against them. That's all part of the game. If they worked in porn, they'd be used to it by now.
I did get a kick out of seeing the Toys-R-Us Christmas online sales cluster-fuck a few years ago. I guess I shouldn't say which facility it was at, but it was in Manhattan.
Speaking of colo's. Pihana Pacific on 7th ave in LA has a new rule. no recording devices, no cameras.. So I went in there with my laptop bag, with my laptop, digital camera, a few hard drives, and a rats nest of cables (I just threw them in from the last colo I was at).. They "inspected" my bag, asking me what brand my laptop was, and looked at the wires. They didn't notice the camera sitting right on top of everything else.
That day, I was there to pull a bad hard drive that we had transfered data off of a fe
Serious? Seriousness is well above my pay grade.