Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

Proof SCO Knew IBM Was Involved in Linux From 1998 Onward

Login to Discuss or Reply to this Discussion in Our Community

 
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

LEARN ABOUT LINUX

mkfs.bfs

MKFS.BFS(8)						Linux System Administrator's Manual					       MKFS.BFS(8)

NAME

       mkfs.bfs - make an SCO bfs filesystem

SYNOPSIS

       mkfs.bfs [-N nr-of-inodes] [-V volume-name] [-F fsname] device [size-in-blocks]

DESCRIPTION

       mkfs.bfs creates an SCO bfs file-system on a block device (usually a disk partition or a file accessed via the loop device).

       The  size-in-blocks  parameter  is  the	desired size of the file system, in blocks.  If nothing is specified, the entire partition will be
       used.

OPTIONS

       -N     Specify the desired number of inodes (at most 512).  If nothing is specified some default number	in  the  range	48-512	is  picked
	      depending on the size of the partition.

       -V volume-label
	      Specify the volume label. I have no idea if/where this is used.

       -F fsname
	      Specify the fsname. I have no idea if/where this is used.

       -v     Be verbose.

EXIT CODES

       The exit code returned by mkfs.bfs is 0 when all went well, and 1 when something went wrong.

SEE ALSO

       mkfs(8).

AVAILABILITY

       The mkfs.bfs command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.

Util-linux 2.9x 						   12 Sept 1999 						       MKFS.BFS(8)