Proof SCO Knew IBM Was Involved in Linux From 1998 Onward

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Proof SCO Knew IBM Was Involved in Linux From 1998 Onward
# 1  
Old 08-23-2010
Proof SCO Knew IBM Was Involved in Linux From 1998 Onward

Look what I just found, SCO's Partners page from 2002, on Internet Archive, and lo and behold, it provides proof positive that SCO, then calling itself Caldera, knew that IBM was involved with Linux as far back as 1998. That's the year Santa Cruz and IBM signed the agreement regarding Project Monterey, executed in October of 1998. No one, therefore, Santa Cruz or Caldera, had any reason to be in the dark about IBM's Linux activities while IBM was also working on Project Monterey.
Now that the old caldera.com pages are on Internet Archive again, thanks to SCO selling off the domain name, many interesting things are surfacing, and we find out why SCO tried to hide them for so long. They should have waited a little bit longer.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. SCO

Sco 5.0.7 on ibm server, no floppy drive.

I cannot install sco on this particular ibm server because sco cannot find the raid controller and thefore the logical drive. I have a floppy disk that I use in other machines when boot: shows on the screen. I usually type restart link=ad320 and it works but this time i have no floppy drive. ... (1 Reply)
Discussion started by: iNetForce
1 Replies

2. SCO

Install SCO Openserver 6.0.0 on an IBM x3500 7977E6U

Even though IBM states that the x3500 server is Openserver 6.x compatible, it is still a bit of a trick to install SCO Openserver 6 to the machine because the standard method of installing the BTLD required to install the OS requires that the driver be written to a floppy which doesn't exist on... (3 Replies)
Discussion started by: qkrenge
3 Replies

3. News, Links, Events and Announcements

SCO sues IBM

http://www.sco.com/scosource/SCOFilesComplaintAgainstIBM.html in my opinion, there is a simple solution to this, a large company, like IBM, should buy the rights from SCO, and then make their rights to UNIX freely available. could they do something likethat? could they even change the license... (6 Replies)
Discussion started by: norsk hedensk
6 Replies
Login or Register to Ask a Question
GSIGNAL(3)						     Linux Programmer's Manual							GSIGNAL(3)

NAME
gsignal, ssignal - software signal facility SYNOPSIS
#include <signal.h> typedef void (*sighandler_t)(int); int gsignal(signum); sighandler_t ssignal(int signum, sighandler_t action); DESCRIPTION
Don't use these functions under Linux. Due to a historical mistake, under Linux these functions are aliases for raise() and signal(), respectively. Elsewhere, on SYSV-like systems, these functions implement software signalling, entirely independent of the classical signal and kill func- tions. The function ssignal() defines the action to take when the software signal with number signum is raised using the function gsig- nal(), and returns the previous such action or SIG_DFL. The function gsignal() does the following: if no action (or the action SIG_DFL) was specified for signum, then it does nothing and returns 0. If the action SIG_IGN was specified for signum, then it does nothing and returns 1. Otherwise, it resets the action to SIG_DFL and calls the action function with parameter signum, and returns the value returned by that function. The range of possible values signum varies (often 1-15 or 1-17). CONFORMING TO
SVID2, XPG2. These functions are available under AIX, DG-UX, HPUX, SCO, Solaris, Tru64. They are called obsolete under most of these sys- tems, and are broken under Linux libc and glibc. Some systems also have gsignal_r() and ssignal_r(). SEE ALSO
kill(2), signal(2), raise(3) notGNU 2002-08-25 GSIGNAL(3)