-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 02 May 2003 22:22, Charles Philip Chan wrote:
On Fri, 2 May 2003 22:27:59 -0400
"Fred A. Miller" <fmiller@lightlink.com> wrote:
Instead, SCO CEO Darl McBride refuses to release that information out of fear the community would "launder the evidence."
Yes, I read several stories about that a couple of hours ago. While he is claiming that, another SCO official claims that the vanilla Linux kernel is not tainted. Go figure, they can't even keep their story straight. Personally, I think they are just trying to scare IBM into buying them.
On other news, their web site was just hit by a DoS attack:
http://news.com.com/2100-1002_3-999584.html
Although I don't condone this kind of behaviour, I think in this case they deserve it.
Charles
A) IBM don't scare easy to say the least. M$ may be the world largest and most successful software company, but IBM is the overall industry 8000 lbs gorilla. I mean these guys don't <explitive deleted> around. If anything is in the works on IBMs side regarding a buyout I'll bet my last dollar that they wait until SCO is so desperate and get the best bang for the buck, on IBMs terms rather than SCOs ( or someone like M$ swoops in for the kill at an opportune moment). B) Many smell a Redmondian rat behind the scenes (as if this were a shock coming from the M$ haters and the paranoid - but "just because [they're] paranoid doesn't mean they (M$) aren't out to get [them]). This vaguely reminds of a recent tort involving M$ and one of it's partners. The partner/plaintiff alledged the M$ took proprietary codes and technologies and folding them into an SDK (IIRC). When this came to light many of M$ other partners and clients contacted M$ to ask if there was any risk to using the SDK in light of the allegations. Of course you know what M$ said... NO! Now the final verdict has been rendered in favor of the plaintiff and M$ as well as their other partners and clients that used this SDK are now liable for punitive damages, substantial punitive damages. The rub is M$' partner owe more than M$ does by a fair amount - not good fuzzy feelings regarding M$ if you talk to said partners. Now, SCO is in a way doing the same thing. This may be an attempt to curtail the fairly steady and increasing adoption of OSS/Linux (especially in light of the improvements forthcoming - kernel 2.5/2.6 is going to absolutely rock). So, start this sort of crap and see if those on the fence don't swing back to the M$ side of the gate. The possible motives could (well do) give one a headache. But on the otherhand this borders on the absurd. I mean McBride and Co had been long on accusations and short on about anything else substantial. I mean fearing that disclosing even a hint at what part of the Linux kernel is under SCO license/patents for fear of them scrubbing out the evidence is, well...., just dumb. Every http/ftp server, hard drive, cdrom, etc... will either be wiped or destroyed borders on outrageous and ludicrious - were talking many millions of copies here. I know that disclosing everything that one has before a trial is not smart (or as most attorneys would direct that nothing at all be discussed). On the other hand the "rules of disclosure and discovery" mandates that if he/SCO has said proof that it must be made available at some point, barring surprise witnesses or evidence. But seeing how this is still pretrial and discovery he will eventually have to bring some sort of plausible documentation forth. This is where, if it has any merit, we will get a better indication about what's going on. On the otherhand, this is where if it's smoke and mirrors then it will quickly fall apart and unravel IMO. On the matter of the DDoS attack. I love the statement about not knowing who's doing it or why! Ya Right!! If he thinks this is a pain I'll wager he aint seen nothng yet. Talk about professional suicide and begging to be Black Listed. Sheesh, what a bunch of buffoons. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE+tJZi7WVLiDrqeksRAsrtAKDCsChEKJgyRw08Ppo7VW6gLU9VcQCUD3VU YcRP6v4yYtIRpFXDxeSBHw== =Htlz -----END PGP SIGNATURE-----