Slashdot Mirror
SCO DOS Harming Innocent Bystanders
An anonymous reader writes "The SCO-IBM-Linux controversy has certainly caused quite a stir. Unfortunately the vigilantes conducting the DOS attacks against SCO are harming innocent by-standers as described in this e-Week story. " Choice conspiracy theory quote: 'Given SCO's behavior recently, it's just as likely that they're attacking themselves in their continued attempt to pump up their stock price'
The white house can rationalize the murder of innocent people for freedom, and other BS. The DOS attackers can hire them.
what was the point of this comment?
you can pick your nose
but you can't pick your neighbor on the internet...
No more Micro$oft bashing from me. Its like bashing at the special olympics.
killing/mutilating yOUR creator's innocents.
.asp for va lairIE's whoreabull pateNTdead PostBlock(tm) devise?, used against the truth/to protect robbIE's payper liesense stock markup bosses/corepirate nazi 'sponsors'. yuk.
you KNOW that's not going to last much longer. the reparations will be made by you/us.
fauxking greed/fear/ego based phonIE payper liesense stock markup FraUD execrable/hivists they are.
that's right, after the walking dead finish exterminating themselves, & sadly enough, some of us, it won't take long to clean up this cesspool of greed/fear execrable.
we're calling it the planet/population rescue program (formerly unknown as the oil for babies initiatve).
the Godless wons are helping by continuing to show where their hearts lie.
fortunately, mr stallman et AL, etcetera, is now offering comparable/superior software, to the payper liesense spy/bug wear feechurned models, in almost every circumstance. there'll be few, if any more softwar billyonerrors, as if there's a need for even won. tell 'em robbIE. you are won of the last wons whois soul DOWt, right?
back on task.
what might happen to US if unprecedented evile/the felonious georgewellian southern baptist freemason fuddite rain of error, fails to be intervened on?
you already know that too. stop pretending. it doesn't help/makes things worse.
they could burn up the the main processor. that would be the rapidly heating planet/population, in case you're still pretending not to notice.
of course, having to badtoll va lairIE's whoreabully infactdead, pateNTdead PostBlock(tm) devise, robbIE's ego, the walking dead, etc..., doesn't slow us down a bit.
that's right. those foulcurrs best get ready to see the light. the WANing daze of the phonIE greed/fear/ego based, thieving/murdering payper liesense hostage taking stock markup FraUD georgewellian fuddite execrable are #ed. talk about a wormIE cesspool of deception? eradicating yOUR domestic corepirate nazi terrorist/gangsters will be the new national pastime.
communications will improve, using whatever power sources are available.
you gnu/software folks are to be commended. we'd be nearly doomed by now (instead, we're opening yet another isp service) without y'all. the check's in the mail again.
meanwhile... for those yet to see the light.
don't come crying to us when there's only won channel/os left.
nothing has changed since the last phonIE ?pr? ?firm? generated 'news' brIEf. lots of good folks/innocents are being killed/mutilated daily by the walking dead. if anything the situations are continuing to deteriorate. you already know that.
the posterboys for grand larcenIE/deception would include any & all of the walking dead who peddle phonIE stock markup payper to millions of hardworking conservative folks, & then, after stealing/spending/disappearing the real dough, pretend that nothing ever happened. sound familiar robbIE? these fauxking corepirate nazi larcens, want us to pretend along with them, whilst they continue to squander yOUR "investmeNTs", on their soul DOWt craving for excess/ego gratification. yuk
no matter their ceaseless efforts to block the truth from you, the tasks (planet/population rescue) will be completed.
the lights are coming up now.
you can pretend all you want. our advise is to be as far away from the walking dead contingent as possible, when the big flash occurs. you wouldn't want to get any of that evile on you.
as to the free unlimited energy plan, as the lights come up, more&more folks will stop being misled into sucking up more&more of the infant killing barrolls of crudeness, & learn that it's more than ok to use newclear power generated by natural (hydro, solar, etc...) methods. of course more information about not wasting anything/behaving less frivolously is bound to show up, here&there.
cyphering how many babies it costs for a barroll of crudene
Is that you speaking?
The crimson sunset in the toilet.
Oh wait, now I remember, this is all one big FUD campaign by Microsoft. They are funding SCO's nonsensical and suicidal actions in order to smear free software as somehow dishonest.
The "Slashdot effect" is a similar thing. Once a story drops off Slashdot's front page, traffic to any site drops back two orders of magnitude to normal. I imagine that much of that traffic is DoS.
Yes, Microsoft's standing is so low that I can say these things and believe them. Their represntatives have filled billboards with crap and denied their identity, written letters to senators for other (and sometimes dead) people on their behalf, created fictional characters for a "Mac Switcher" astroturf campaign when no real such person could be found and have even infiltrated meetings of grade shcool teachers with explicit direction to conceal their identity to gain trust. No lie seems beyond them and they are happy to harm others if it will do them some good.
Friends don't help friends install M$ junk.
is tihs becasue i hav to wack 13 times pre day??
I wouldn't worry about SCO DOS, I'm sure Microsoft will insert subtle incompatibilities so that Windows 3.1 won't run on it.
taken! (by Davidleeroth) Thanks Bingo Foo!
Version 1.1 - Note: Features/bugs listed may not apply to some SCO products/versions
/* SCO OpenServer */ darlsux() ;
/* UnixWare gcc */ darlsux() ;
/* Gemini I cc (SCO UnixWare 7 and UDK) */ darlsux() ;
/* SCO UnixWare cc */ darlsux() ;
/* ODT 3 or earlier */
/* Other platform */
NOTE: This report hereby placed in public domain, use it as you wish, at your own risk!
Additional suggestions, detailed specific recommendations, comments, requested.
Obviously it is a concern to GPL software authors that they maintain compatibility with the SCO platforms, while SCO publicly abuses them, tries to get the GPL declared invalid, and while SCO profits from selling their software and integrating it into future releases of the SCO product line.
Software authors will be aware that breaking SCO compatibility may cause problems for SCO users - (although strictly speaking that is SCO's problem, not the software author(s)', unless the author(s) have some contractual relationship with SCO or SCO customers).
SCO needs support revenue (and new sales revenue) that may depend on GPL products, to fund their PR and litigation. Thus, software authors, who not obligated to support SCO, presumably might want to.
Therefore here is a list of things NOT to do, if you don't want to break SCO compatibility.
1. Don't refactor your code, rearrange files, move functions between files, and rename files more logically in the same release as one which contains accidentally contains one or more SCO incompatible changes.
If you do this, it would make it harder for SCO or their partners to re-introduce any "lost" code that was necessary to support the SCO's platforms. Obviously you wouldn't want that.
2. Don't accidentally remove SCO support in a series of stages, which overlap in time with a bunch of critical security or bug fixes, without making it clear at which stages you accidentally removed SCO support.
3. Don't accidentally remove any special fixes or work rounds for SCO platforms.
4. Don't depend on functions, which are not implemented or perform differently on SCO platforms. Especially don't depend on those functions in lots of different places in your product.
In particular avoid these functions:
(please help with this list - "list 4")
Known bugs in SCO products:
Unixware: accept() does not set the sa_family value correctly for the AF_UNIX family. See http://mail.python.org/pipermail/patches/2001-Augu st/005630.html
Unixware: atan2() does returns pi instead of zero for atan2(0, x). See http://mail.python.org/pipermail/patches/2001-Augu st/005630.html
5. Don't depend on compiler features that might not be available on SCO platforms. This is especially true if, as has been suggested may occur, new versions of GCC don't support SCO platforms.
In particular don't depend on these compiler features:
(please help with this list if and when GCC loses SCO support)
6. Don't put in messages that display only on SCO's platforms.
Avoid putting in code like (and especially not commenting):
#if defined(_SCO_DS)
#elif defined(__UNIXWARE__)
#elif defined(__USLC__)
#if defined( __STDC_VERSION__ ) && __STDC_VERSION__ == 199409
#else
#endif
#elif defined(M_UNIX)
#else
#endif
7. Don't remove support in your makefile for building the application on SCO's platforms.
8. Don't rename your functions and variables with names that conflict with SCO-spec
oh, fudge!