Replies

Just to add grist to the mill:

"Darl McBride, president and CEO continued, "These positive quarterly financial results, including net income for the first time in the Company's history, have strengthened our balance sheet and financial position. Our increased cash balance and working capital has positioned the Company for its launch of SCOx, our web services strategy, and will provide us with other opportunities to drive growth in future quarters."

SCO's next "big thing" is a "web services strategy" called SCOx?

And suddenly they've integrated Microsoft Active Directory. I wonder if more MS technology will be integrated soon?

Smoking gun? No.

But interesting, none the less. Something to watch in the future. Maybe a move to .NET for SCO?

Ah, never mind. Pure, random speculation here, folks. Just the ramblings of a senile old programmer. Nothing to see here. Move along.

Did you see that Novell has stepped in to this?

Novell Says SCO Doesn't Own Unix
Novell challenges SCO's right to sue IBM and Linux users for
violations of intellectual property rights.
http://update.internetweek.com/cgi-bin4/DM/y/eMED0Bpxq10V30Bzpg0Af

Back in 1999 I was doing the TCP/IP components for Borland Delphi. I was stuck on the statement in the microsoft documenation that NT could not do raw sockets. Yet NT came with a command line ping untility. Ping and trace root use raw sockets. It turned out that one had to use a dll called Icmp.dll to programatically access raw sockets in windows nt. It seemed to me that if ICMP.dll could do raw sockets, I could write code that would do also without using the ICMP.DLL.

To try to get a handle on how the MS TCP/IP stack worked I downloaded the BSD Unix TCP/IP code and tried to compile it in Visual Studio C++ 6.0. I found the order of the functions in the BSD code was the same as the MS TCP/IP stack code. I also found the only thing missing from the MS Winsock dll was the raw socket data struture. If the data address was passed to the rawsocket function (not documented in MS) and called as if it were the BSD raw socket fuction the dang thing worked. I think the Winshoes components that shipped with delphi 5 or perhaps 6 had this component.

Perhaps I am wrong but my conclusion was someone at MS just lifted the BSD Unix TCP/IP Stack code and did what it took to get it to compile in windows. Then put that windsock dll in NT 4.0 SP3. The one diference from the BSD code was you had to allocate the data structure and pass its address to the raw socket function in the Winsock dll. ICMP.Dll just contained the data structure and a call to the windsock dll.

Could windows NT contain UNIX code? Could be.