The best thing the community can do now - when the source has leaked - is to actually perform a peer review of the MS source code, and HELP MS close the security holes. After all, we all do want a more secure internet, with less virii, worms and bugs. So why not help out? I can't imagine what MS reaction would be if they actually started getting serious _help_ from the open source community, instead of the regular bashing. And - it would be a Good Thing as well... Remember - it's Valentine's day tomorrow...
Seriously, this is the last death-twitch before the body stops moving. SCO is as dead as... death. Their tactics are getting more and more desperate, and they are trying to scare the world into believing their claims without presenting any real proof that the claims are valid. The bigwigs are selling off shares while they are still worth something, and as more and more information leaks out about the lawsuit, we get more and more confident that it does not have any valid grounds. The code in the Heise screenshots was quickly identified and reviewed, and failed miserably - instead of proving to the Linux community and IBM that the lawsuit really could be something we need to think about, instead it proved the opposite.
My guess is this is what is going to happen:
1. More information about the code SCO claims infringes their copyright will leak out.
2. Code will be reviewed and shown as not proving SCO-s case.
2b. Code can not be shown as "innocent" and will be rewritten quickly.
2c. The Linux kernel will be cleaned from any "suspicious" code and released. Joe User with an x86 uniprocessor desktop architecure will be able to use the "clean" kernel right away.
3. SCO will fall apart together with the lawsuit.
In fact I don't think it will ever even come near a courthouse. My firm belief is that IBM and the Linux community will finally prevail and have an even better position than before the lawsuit.
He may actually be entitled to the trademark - that he filed the application to register the trademark with the USPTO at a certain time doesn't exclude the possibility that he did own the rights to the trademark prior to that. But he might have a "slight" difficulty proving it...;-)
sure, the amateur sites should be there, and sure, the amount of knowledge required to make such a site shouldn't be too high, BUT: large companies _should_ stick to standards when developing webpages, as should webpage-authoring programs such as Dreamweaver, Homesite, Netscape composer and Frontpage. (Consider the latter two as complete (but extremely bad) jokes.)
I am looking forward to a standards-compliant web, and I really hope there will be diversity in the browser market so that web authors are _forced_ to adhere to standards to make their pages accessible to everyone. 'Cause that's what it's about, right? If a webpage adheres to standards, everybody can access it. Which should be the ultimate goal for webmasters, and it has been shown to be the ultimate challenge as well, at least with the crappy tools some companies provide them with...
Slashdot Mirror
Perhaps you could turn it into... an SSH server? To uuuhhh.. ssh into it and... uhh... do things...
just wait until all we gentoousers connect our computers together with distcc... then we'll all emerge KDE faster than you can blink! HAHA!
You did have a warning - the releasepage for 2004.2 mentioned that it was in the last stages of being finalized a couple of days ago...
The best thing the community can do now - when the source has leaked - is to actually perform a peer review of the MS source code, and HELP MS close the security holes.
After all, we all do want a more secure internet, with less virii, worms and bugs. So why not help out?
I can't imagine what MS reaction would be if they actually started getting serious _help_ from the open source community, instead of the regular bashing.
And - it would be a Good Thing as well... Remember - it's Valentine's day tomorrow...
World to SCO:
Fuck you too!
Seriously, this is the last death-twitch before the body stops moving. SCO is as dead as... death. Their tactics are getting more and more desperate, and they are trying to scare the world into believing their claims without presenting any real proof that the claims are valid. The bigwigs are selling off shares while they are still worth something, and as more and more information leaks out about the lawsuit, we get more and more confident that it does not have any valid grounds.
The code in the Heise screenshots was quickly identified and reviewed, and failed miserably - instead of proving to the Linux community and IBM that the lawsuit really could be something we need to think about, instead it proved the opposite.
My guess is this is what is going to happen:
1. More information about the code SCO claims infringes their copyright will leak out.
2. Code will be reviewed and shown as not proving SCO-s case.
2b. Code can not be shown as "innocent" and will be rewritten quickly.
2c. The Linux kernel will be cleaned from any "suspicious" code and released. Joe User with an x86 uniprocessor desktop architecure will be able to use the "clean" kernel right away.
3. SCO will fall apart together with the lawsuit.
In fact I don't think it will ever even come near a courthouse. My firm belief is that IBM and the Linux community will finally prevail and have an even better position than before the lawsuit.
Because I'm not in charge of change & problem management and those who aren't haven't addressed the problem until today?
I actually watched T3 yesterday... Coincidence??
Are you serious or are you joking??
He may actually be entitled to the trademark - that he filed the application to register the trademark with the USPTO at a certain time doesn't exclude the possibility that he did own the rights to the trademark prior to that. But he might have a "slight" difficulty proving it... ;-)
sure, the amateur sites should be there, and sure, the amount of knowledge required to make such a site shouldn't be too high, BUT: large companies _should_ stick to standards when developing webpages, as should webpage-authoring programs such as Dreamweaver, Homesite, Netscape composer and Frontpage. (Consider the latter two as complete (but extremely bad) jokes.) I am looking forward to a standards-compliant web, and I really hope there will be diversity in the browser market so that web authors are _forced_ to adhere to standards to make their pages accessible to everyone. 'Cause that's what it's about, right? If a webpage adheres to standards, everybody can access it. Which should be the ultimate goal for webmasters, and it has been shown to be the ultimate challenge as well, at least with the crappy tools some companies provide them with ...