Sponsored Content
Full Discussion: SCO sues IBM
Special Forums News, Links, Events and Announcements SCO sues IBM Post 34732 by LivinFree on Saturday 8th of March 2003 11:35:51 PM
Old 03-09-2003
Well, I don't think anybody really understands whats going on with this - it seems to be some sort of poli-techinal "fireman's contest", to put it politely.

There's a short article on it here:
http://seattletimes.nwsource.com/htm...nixsuit08.html

I don't think they've hit it quite on the head, though. Just as a further evidence on the misunderstandings of this issue, below is a link to a comment posted on Slashdot by Bruce Perens ( for those who have not heard the name before, Bruce Perens is an adamant Open Source advocate, and I believe he still works for HP):
http://slashdot.org/comments.pl?cid=...=56225&tid=123

As for the trademark name, X/Open {(r)(t) and so on} does acknoledge the use of the Unix name to companies who have "bought" the name before they had it - one of them being SCO (the current owner of the direct descendent sysVr4 code). Heck, you can browse true Unix code online now: http://minnie.tuhs.org/UnixTree/ . I've even gotten SystemV and older versions running on a linux box using PDP-11 emulators...

And then again, maybe Bruce (and the rest of the world) is way off... Hey, being that I'm up here in Cupertino for a while for training at HP (Their campus is across the street right now - in fact I can see it out the window), maybe I could track down Mr. Perens and ask him whats going on Smilie
 

2 More Discussions You Might Find Interesting

1. 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

2. 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
CFREE(3)						     Linux Programmer's Manual							  CFREE(3)

NAME
cfree - free allocated memory SYNOPSIS
#include <stdlib.h> /* In SunOS 4 */ int cfree(void *ptr); /* In glibc or FreeBSD libcompat */ void cfree(void *ptr); /* In SCO OpenServer */ void cfree(char *ptr, unsigned num, unsigned size); /* In Solaris watchmalloc.so.1 */ void cfree(void *ptr, size_t nelem, size_t elsize); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): cfree(): _BSD_SOURCE || _SVID_SOURCE DESCRIPTION
This function should never be used. Use free(3) instead. 1-arg cfree In glibc, the function cfree() is a synonym for free(3), "added for compatibility with SunOS". Other systems have other functions with this name. The declaration is sometimes in <stdlib.h> and sometimes in <malloc.h>. 3-arg cfree Some SCO and Solaris versions have malloc libraries with a 3-argument cfree(), apparently as an analog to calloc(3). If you need it while porting something, add #define cfree(p, n, s) free((p)) to your file. A frequently asked question is "Can I use free(3) to free memory allocated with calloc(3), or do I need cfree()?" Answer: use free(3). An SCO manual writes: "The cfree routine is provided for compliance to the iBCSe2 standard and simply calls free. The num and size argu- ments to cfree are not used." RETURN VALUE
The SunOS version of cfree() (which is a synonym for free(3)) returns 1 on success and 0 on failure. In case of error, errno is set to EINVAL: the value of ptr was not a pointer to a block previously allocated by one of the routines in the malloc(3) family. CONFORMING TO
The 3-argument version of cfree() as used by SCO conforms to the iBCSe2 standard: Intel386 Binary Compatibility Specification, Edition 2. SEE ALSO
malloc(3) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2007-07-26 CFREE(3)
All times are GMT -4. The time now is 09:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy