Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Stewart Rules: Novell Wins! CASE CLOSED! Post 302428736 by Linux Bot on Thursday 10th of June 2010 06:45:09 PM
Old 06-10-2010
Stewart Rules: Novell Wins! CASE CLOSED!

Here you go, munchkins. Judge Ted Stewart has ruled for Novell and against SCO. Novell's claim for declaratory judgment is granted; SCO's claims for specific performance and breach of the implied covenant of good fair and fair dealings are denied. Also SCO's motion for judgment as a matter of law or for a new trial: denied. Novell is entitled to waive, at its sole discretion, claims against IBM, Sequent and other SVRX licensees.
CASE CLOSED!
Maybe I should say cases closed. The door has slammed shut on the SCO litigation machine. The judge writes in the Memorandum Decision and Order about SCOsource, "Finally, while SCO's witnesses testified that the copyrights were'required' for SCO to run its SCOsource licensing program, this was not something that SCOever acquired from Novell." He totally got it. He noticed Darl McBride admitted that SCO didn't need the copyrights for anything but SCOsource. It couldn't be any better if I'd written it myself.
Was the jury misled or confused? Not at all, the judge writes: "The jury could have rejected the testimony of SCO's witnesses for a number ofreasons, including their lack of involvement in drafting the APA, the fact that there was littletestimony on any actual discussions concerning the transfer of copyrights, or that many of thewitnesses had a financial interest in the litigation."
"The Clerk of the Court is directed to close this case forthwith," Stewart writes in the final judgment. I believe that means SCO v. IBM is essentially over now, unless IBM wishes to pursue its counterclaims.
And now it is -- finally -- time, once again, for my red dress! And a huge thank you to Michael Jacobs and the team at Morrison & Foerster, who never gave up but, more importantly, showed that you can fight hard and win with ethics and dignity, and to Sterling Brennan of Workman|Nydegger, who was frankly absolutely wonderful at trial. And thank you to you, Groklaw volunteers, because we made a difference in this world.

More...
This User Gave Thanks to Linux Bot For This Post:
 
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.25 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 08:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy