SCO Wants to Sell Java Patent and (Mostly) Pay the Professionals

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News SCO Wants to Sell Java Patent and (Mostly) Pay the Professionals
# 1  
Old 03-30-2010
SCO Wants to Sell Java Patent and (Mostly) Pay the Professionals

SCO Chapter 11 Trustee Edward Cahn has now reported to the bankruptcy court that he's closed on the loan from Ralph Yarro and his friends, and now Cahn wants to pay most of the bills in the bankruptcy from SCO's numerous professionals. And he wants to sell the Java patent, since SCO's never used it and has no use for it going forward. He has a buyer, Liberty Lane, LLC, and so he asks the court to approve the sale to Liberty Lane "or another higher and better bidder." That seems unlikely, in that they claim to have shopped the patent to around 40 potential purchasers. Liberty Lane is offering $100,000.
Cahn says he "will pay 80% of fees and 100% of expenses to all of the estates' professionals who have filed (i) monthly and/or interim fee applications for such fees and expenses and (ii) certifications of no objections with respect thereto pursuant to the Interim Compensation Order", but doesn't yet want to pay the last 20% of PSZ&J's bill "until such time as the Trustee has reviewed and evaluated the reasonableness of all fees and expenses generated by the Debtors' and these estates' professionals".
So that's where the loan goes, for starters. He's not singling them out, by the way, except for the fact that he wants to wait until all the final bills are in, so he can evaluate reasonableness in a context, and so far they are the only ones that have filed a final bill.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. SCO

Issue using SCO java SerialDemo

I recently installed the Java Communications API (v2.0Aa) on SCO and I'm having some issues running the SerialDemo application that comes with it. I can open a connection and send text from SCO to a toy windows app I wrote - that works fine. However, when I try and close the connection, I get... (2 Replies)
Discussion started by: jdsnatl
2 Replies
Login or Register to Ask a Question
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.53 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)