Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Trial in SCO v. Novell Now Scheduled for 15 Days Beginning March 8 Post 302384952 by Linux Bot on Wednesday 6th of January 2010 06:30:00 PM
Old 01-06-2010
Trial in SCO v. Novell Now Scheduled for 15 Days Beginning March 8

The trial schedule for SCO v. Novell in Utah has been altered. It was set as a 3-week trial; now it's set for 15 days:
01/06/2010 - 613 - AMENDED SCHEDULING ORDER: Final Pretrial Conference set for 2/25/2010 02:00 PM in Room 142 before Judge Ted Stewart. 15 day Jury Trial set for 3/8/2010 08:30 AM in Room 142 before Judge Ted Stewart. Signed by Judge Ted Stewart on 01/06/2010. (asp) (Entered: 01/06/2010)

Here's the article with reports from the status hearing where the original schedule was set. Yes, SCO wanted 2 to 2 1/2 weeks and Novell said 2 1/2 to 3, if I mash together the conflicting reports, but 15 days is what neither side asked for exactly, although tilted more in SCO's direction than Novell's, so it probably means one of these things: either Judge Stewart wants this over with, or more likely the parties worked out some issues and know now they don't actually need more than 15 days. It is also possible the judge doesn't care what they want. And it's possible there is some bias, unconscious or otherwise. I can't think of any other possibilities. I notice that the days are not full days. It's 8:30 am to 1:30 pm. This of course will affect how many witnesses each side can put on the stand. I think we may also assume that Judge Stewart isn't thinking of recusing himself, at least at this point.
In any case, we need to begin thinking about covering that many days of a trial. The cost for transcripts for something like this is way beyond our capabilities. So I'm asking the parties if they would please consider providing a copy of their transcripts when they order them? This is an historic case, one that will go down in history, I'm sure, no matter how it ends. So please would you consider the children, so to speak, the coming generations who will want to study and learn about this litigation?
And if anyone knows anyone who can take notes and will volunteer to attend a day or two or all of it, this is the moment for us to start to get prepared.

More...
 
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)
All times are GMT -4. The time now is 09:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy