(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version



SCO gets to see the code

Fri Jan 21 10:44:27 2005



Referencing: Judge opens up Unix code for SCO

IBM has to cough up the code and any notes or other documents that the folks involved in making code changes might have. Groklaw (and IBM, of course) insist that there's nothing to be found, but they do get to look. SCO has an awful track record in finding anything, and with regard to Linux, if it was IBM's "stolen" code that is in there, why can't SCO just point at it in Linux source? Why am I so confused by this?

I am confused even more. I thought the Groklaw position was that SCO doesn't own anything - didn't the Novell agreement only give them the right to sell Unix? Obviously the judge must not agree, or we're talking about code SCO developed themselves, or bought, or.. oh well, it's as complicated and confusing as ever, but at least it's moving along.

Remember, folks, the ultimate decision will have nothing to do with morality and may have little to do with legality either: this is a highly technical and confusing mess that is going to be decided by non-technical people. Anything can happen, including the truly awful. Just look at our patent mess for an example of what happens when non-techs make decisions about these things. Judges and juries are going to be even more confused than I am, and the final results will be created from their confusion.

I'm still hoping for Linux walking away clean, of course. Anything else will be damaging to all of us, even those who have no investment in anything but Microsoft. If this lawsuit damages free code, Microsoft is strengthened, which of course locks more people into proprietary systems, where innovation is just a funny word marketing uses and engineering spends most of its efforts protecting code from unlicensed use and munging interfaces so that they are useless to competitors.

But it's too soon for doom and gloom.




Click here to add your comments


---January 22, 2005

"Obviously the judge must not agree"

This judge (there's two involved) can't rule on the right or wrong of this case. She just administers the initial fact-finding process. All she did in this ruling was to point out that there's disagreement on what is right and relevant, and therefore she will allow SCO to get most of what they asked for, in case their understanding later is proven to be correct.

As for "why can't SCO just point at it in Linux source?", they are claiming that they have controlling rights to IBM "homegrown code", through contracts. If they ever win on that claim, it will not matter to Linux, though IBM may be punished. Parties not involved in a contract can't be held to it, and as SCO don't claim other rights (like copyrights) to such code, Linux is free to continue using it.

NilsR


---January 22, 2005

Well, that would be good, then. I've said before that I don't care what happens between IBM and SCO, as long as it doesn't affect Linux. But I still do NOT understand the Linux part of this. You suggest here that Linux might be uninvolved, but that doesn't seem to be the case: SCO is still pursuing that licensing business. So I remain confused and wary :-)

--TonyLawrence


---January 22, 2005

"SCO is still pursuing that licensing business."

Are they? Several people have reported trying to actually get one of those, with no success whatsoever.

Confused is what SCO wants us to be, but to be wary of the outcome of any legal case, seems only wise to me. :-)

NilsR




Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar




Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


book graphic unix and linux troubleshooting guide

My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!



 I sell and support
 Kerio Mail server




pavatar.jpg
More:
       - Linux
       - Unix
       - OSR5
       - Blog


Unix/Linux Consultants

Skills Tests

Guest Post Here











My Favorites

Change Congress