Slashdot Mirror
Microsoft Not Underwriting SCO's Legal Fees?
An anonymous reader wrote in to say "Linux Business Week carries this morning a claim that Microsoft only bought a Unix license from SCO Group because there's been a prior development project underway at Redmond that warranted it. "The license was not seen as a way to underwrite SCO's legal fees," says a source within the company. "The idea of getting a SCO license had been under consideration prior to the IBM lawsuit." "
There is no way of either truly confirming or denying this. Microsoft won't, i am prepared to bet, actually say what they are working on, and Very few people trust M$ to be telling the truth. End discussion, really.
An infinite number of monkeys will eventually come up with the complete works of
Always remember these two words:
"Plausible Deniability"
Dateline OZ.... As reported earlier the Wicked Witch and her consortium of mean little monkeys has licensed rights to the Ruby Slippers from Glenda the Good Witch. Glenda, who is suffering financial problems, and was unable to leverage her IP against the Dorothy Corp (NYSE-DC) and with little opportunities elswhere in the Good Witch market it was assumed that the Good Witch franchise (NYSE-GWF) would soon collapse under the weight of farm houses. Timing IS everything!
Translation: SCO was looking to f*** over Linux and IBM, and we liked that. Most of the other software vendors, traitorous bastards that they are, have been all too happy to port their stuff over to Linux.
Microsoft has been distributing their Services for Unix software for some time now. If you will remember, the entire purpose they attended LinuxWorld last year was to show this product and even hand out free CD's to try.
Basically, Services for Unix runs on Windows and is designed to replace UNIX servers by offering some similiar services such has NFS and NIS. The idea here is for companies to gracefully migrate their servers away from UNIX and lock them into a MS products.
I just don't understand why Microsoft didn't purchase this license years ago when the Services for UNIX was first started.
Microsoft was planning long before the SCO lawsuit to respond to the popularity of Apache web servers with Apache helicopters.
Last week I received this months copy of SysAdmin magazine in the mail. What happened to accompany my magazine in the shrink wrap? None other than Microsoft's Services for UNIX 3.0 which used to be Interix Services. It's possible that this product has the potential to contain code that could be obtained from other sources.
I don't remember much about Interix before Microsoft bought them, but I do remember using a demo copy of the Interix Services package and what it did do was pretty cool. It gave a UNIX functionality layer to the NT system. You could log in via SSH and perform all command line functions that you would find on any *BSD, *Linux box. Including cross compile. I seem to remember the demo package including GCC that had been compiled specifically for this package.
Unfortunately I don't have a single MS box in my current possession to install this on to play with. One of my poor, ailing, FreeBSD boxes might get wiped to play with this for a few weeks.
Since everyone else is throwing out conspiracy theories, I suppose I'll throw my own into the arena. CAUTION the following is frivolous bullshit that has no way to be proven except in my own mind. But isn't that true of most of these theories people have?
Interix starts out as a company to build a UNIX compatibility layer for the NT kernel. What better way than to look at the source that is freely available to decide what road to take. Looking at *BSD and *Linux they find that with a little effort they can write a compatibility layer and run pure *NIX apps right on top of NT. (They even have a XR11 port for this layer) All fun, all native, all fast.
Since this is starting out as an exercise in theoretical mechanics of getting UNIX to operate directly on NT, they borrow some "free" code to figure out how exactly to get it all to fit together. Purely with the intention of yanking all "borrowed" code later should this prove to work as they can afford to.
Their compatibility layer works better than expected, apps can easily cross compile to their pseudo-kernel and anyone that isn't directly in front of the box doesn't know they aren't talking to UNIX. This causes Uncle Bill to take notice. He likes what they are doing, and since his own Services for UNIX is pretty piss poor he does what he does best. Buys the company. (I'm not just an Interix client, I liked them so much I bought the company.)
So now, instead of ripping out all the "borrowed" code that is working so well, the new team, who is partnered with pieces of the old team, continue to develop along side each other, integrating the MS UNIX codebase that was Services for UNIX into the Interix codebase to build SFU 3.0.
SCO comes along and starts the whole lawsuit procedure but isn't giving any examples of code. Uncle Bill, preferring to stay quiet and in control, doesn't know if they need to scrap the project or not. Easiest solution? Buy the rights to the problem. License the technology you've already stolen and improved upon, gaining the legal right to use it, before the originating company realizes what you are doing and comes after you.
MS may have deep pockets, but they aren't bottomless, and I believe the legal battles with Apple taught them one very important lesson. End it quick and as painless as possible, keep the government out of it, because they have a tendency to side with people who may be my enemy (MS almost lost the anti-trust suit before Clinton left office?) So make it go away quietly so as not to draw attention to us.
End Rant ..... just my two cents.
"Genius may shine aloof and alone, like a star, but goodness is social, and it takes two men and God to make a Brother."