So did HP find the leaker? What were they hoping for as the return on the investment?
Robinson from Leslie A. I know you join me in thanking Mark for writing this for us. No dips or huge peaks.
With a gazillion exhibits.
Boies will end up a witness in this case, if IBM's motion is denied and SCO gets to proceed with its interference claims. Maybe someone has the time to go over the list and match it up with what we already have?
No moss growing on that case.
This is what the lawyers normally will have done before including a case in any brief. In any case, now we know the rest of the story about BayStar. Another secret in SCO's mountain of secret offenses for which they would like IBM to pay them billions.
I wish to say thank you to the British Library for issuing this document. That's what the experts are probably trying to figure out, at least SCO's experts, although with no specific code to work with, they may be having a hard time doing the math.
So did HP find the leaker?
Yet they released over and over under the GPL. Then pull up a chair, my friends.
Microsoft assured me that it would in some way guarantee BayStar's investment in SCO. And leaving specific code out of this, they never noticed file systems in Linux, for example, were quite a lot like Unix? The buck stops nowhere.
I pledge that I will dig harder and deeper and I will get to the bottom of this. Well, not to try to teach Mr.
He now works for SUSE. And SCO worked hard to make Linux POSIX compliant because they wanted Linux to have Unix capabilities for the enterprise. I was reminded of this by an email from Marbux, and I asked if I could share it with you.