It would also stand to reason that some plebian coder with access to the SCO source could use it as a basis for 'fixes' to the kernel and submit them through some 2nd or 3rd tier person who might submit a patch rollup to Linus who just merges it in under their name.
They'd have to be an absolute bloody genius to find code that was portable UnixWare-to-Linux and pleased Linus and all of the lieutenants standing before him.
It's possible that IBM's contributions were submitted en masse to Linus and company.
Linus is not fond of big blocks of code and flat-out refuses multi-purpose integrated patch sets.
Also, an awful lot of IBM innovations have so far been refused a place in the kernel, despite being useful and competent, because the competing system(s) was/were usefuller and/or competenter.
Since SCO seem to be manifestly incompetent, it goes without syaing that any of their UnixWare code would have been rejected out of hand.
According to find, grep and wc, a Mandrake 2.4.21-pre kernel (not including the Documentation/ tree) comes to 4.37 million non-blank lines. According to The SCO Group's lawyers, two thousandths of a percent of the Linux kernel was contributed by them. Gee, that was worthwhile. And considerably less than their own website claims.
Of course, they didn't nominate the file containing the 80 lines, it might well be net/tcp_ecn.h or better yet lines 3-24 of math-emu/single.h (-:
You are advocating the ends justify the means no matter the cost. That's not something I can agree with. Linux needs to win fairly. I think it has won fairly and SCO is full of shit, but I still think SCO deserves their right to be heard.
There are some things I violently disagree with you on, but here I'm in absolute, unqualified 100% agreement.
We lose because now we will NEVER be able to get a job here in the USA.
Everyone else will follow India's path: they'll become too expensive. Sooner or later, there will be no more new labour pools to open. We'll wind up with a teired arrangement of programming skills in descending order of both price and convenience.
Your troubles will really surface when some of those countries build real economies around more efficient production techniques than America's. Admittedly, some societies will bind them in a morass of social inefficiency which rival's America's own layers of politics and red tape, but there will still be plenty left who can industrially outperform America at all levels. Then America will no longer be top teir, they will. And if America doesn't adapt, they'll go from superpower to third-world.
Admittedly, "third-world" may not be such a bad status by then, if everyone's on the useful-technology bandwagon.
The consumers and the developers are one. All hold hands and chant "Om!" (-:
That's the way Linux works. The overlap's not perfect, but at least there's less backstabbing, graft and general politics than in a purely greed-powered system. And things get done with unprecedented quickness.
To retain the integrity of the sequence, it would be UnixME. Something at least a few people would evidently be glad to do to SCO's CEO.
Stupidity and desperation: similar, not identity
on
Latest SCO News
·
· Score: 1
Even I don't think SCO is that stupid.
They may well be that desperate. Desperate can be roughly equivalent to mindless.
all SCO could do is sue Linux companies and users to cease further infringement, not monetary damages. They couldn't even recoup legal costs for the cases.
Before SCO even do that, they have to serve notice on those people and give them a reasonable time to cease. Which to me sounds like a fine reason to update, no complaints there.
This is stating the obvious, but "cease further infringement" is precisely what the vast majority of Linux kernel developers are aching to do, if and when they are shown some genuine infringing code.
Slashdot Mirror
Time to transfer some assets and go on the dole? (-:
Oh, well, she probably snores anyway and is a terrible nag in private. (-:
@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{q *=2) +=$f=!fork;map{$P=$P[$f^ord[ P.]/&&
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^
close$_}%p;wait until$?;map{/^r/&&}%p;$_=$d[$q];sleep rand(2)if/\S/;print
Yes, Windows gets 17% higher TPC-C... with twice as many processors. The word "Pyrrhic" immediately springs to mind.
They'd have to be an absolute bloody genius to find code that was portable UnixWare-to-Linux and pleased Linus and all of the lieutenants standing before him.
gawk '{ t=t+$1; } END { print t }'
gawk '{ t=t+$1; } END { print t/$NR }' if you want average (mean) instead
...distributing it as at 00:26+08 on 09Jun2003. Yes, including full kernel source.
Linus is not fond of big blocks of code and flat-out refuses multi-purpose integrated patch sets.
Also, an awful lot of IBM innovations have so far been refused a place in the kernel, despite being useful and competent, because the competing system(s) was/were usefuller and/or competenter.
Since SCO seem to be manifestly incompetent, it goes without syaing that any of their UnixWare code would have been rejected out of hand.
...about 3 lines a day. Bugger, I drank some coffee and bankrupted the USA.
According to find, grep and wc, a Mandrake 2.4.21-pre kernel (not including the Documentation/ tree) comes to 4.37 million non-blank lines. According to The SCO Group's lawyers, two thousandths of a percent of the Linux kernel was contributed by them. Gee, that was worthwhile. And considerably less than their own website claims.
Of course, they didn't nominate the file containing the 80 lines, it might well be net/tcp_ecn.h or better yet lines 3-24 of math-emu/single.h (-:
If it was 80 lines of PERL, how could a layman decide that it was code, and not line noise?
This brings us back to a common coding practice: dumping the code and rewriting your own code underneath the comments. Still no data.
IMESHO the NDA is safe to sign because The SCO Group are about to become a memory, a bad dream.
I wonder if they had to use a hairdryer on it before they started photocopying and faxing?
Microsoft illegally distributed code from TimeLine Inc in SQL Server.
I move to delete "almost" and "slashdot". (-:
Are listed here, according to SCO.
There are some things I violently disagree with you on, but here I'm in absolute, unqualified 100% agreement.
Everyone else will follow India's path: they'll become too expensive. Sooner or later, there will be no more new labour pools to open. We'll wind up with a teired arrangement of programming skills in descending order of both price and convenience.
Your troubles will really surface when some of those countries build real economies around more efficient production techniques than America's. Admittedly, some societies will bind them in a morass of social inefficiency which rival's America's own layers of politics and red tape, but there will still be plenty left who can industrially outperform America at all levels. Then America will no longer be top teir, they will. And if America doesn't adapt, they'll go from superpower to third-world.
Admittedly, "third-world" may not be such a bad status by then, if everyone's on the useful-technology bandwagon.
That's the way Linux works. The overlap's not perfect, but at least there's less backstabbing, graft and general politics than in a purely greed-powered system. And things get done with unprecedented quickness.
Welcome to an XboX in Western Australia!
Eaten Caldera from the inside and destroyed it. Caldera did actually contribute useful code to Linux under Ransom Love's "unification" programme, but alas, no more.
Of course, The SCO Group now has to prove that the code in question wasn't contributed by Caldera.
To retain the integrity of the sequence, it would be UnixME. Something at least a few people would evidently be glad to do to SCO's CEO.
They may well be that desperate. Desperate can be roughly equivalent to mindless.
I think I'll start encouraging other people to invite SCO to sue them - oops, too late.
Before SCO even do that, they have to serve notice on those people and give them a reasonable time to cease. Which to me sounds like a fine reason to update, no complaints there.
This is stating the obvious, but "cease further infringement" is precisely what the vast majority of Linux kernel developers are aching to do, if and when they are shown some genuine infringing code.
Not intentionally, anyway. (-:
This is, after all is said and done, law and not reality.