12-15-2006
SCO and VMware
Jeroenix have you found solution to your problem yet? I have very similar situation over here with SCO/Ghost and VMWare. Thanks
6 More Discussions You Might Find Interesting
1. SCO
Hi folks,
First of all, sorry about my english, isn't the best and thks for advance.
Here es my problem...
I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies
2. SCO
I am haveing a problem with my VMware ESXi 4.1 server and a virtual SCO UnixWare 7.1.4 server that I need for a legacy application for my company. The problem seems simple but I can't find a solution. The UnixWare (UW) server is a clean install and patched as SCO recommends. I am able to telnet to... (1 Reply)
Discussion started by: DudeCrush
1 Replies
3. SCO
Sir I am trying to install UnixWare7.1.4 on vmware workstation9, virtualbox and I am getting the following error
FATAL BOOT ERROR: decompression failed
For installing SCO Unixware7.1.4 I have created virtual harddisk of size 18GB, 1024 RAM, 64bit video memory, chosen unixware7.1.4... (1 Reply)
Discussion started by: rupeshforu3
1 Replies
4. UNIX for Advanced & Expert Users
I've moved a physical server over to VMWare ESXi 5.1 using SCO 6.0 with MP4. For whatever reason, people are occasionally getting kicked out or are closing out their telnet session and it is leaving their processes running. When this happens, the sar %idle drops from 98-95% down to 25-20%. ... (1 Reply)
Discussion started by: Carlitos71
1 Replies
5. SCO
Some years ago our company chose to run a critical proprietary app under SCO Unix.
My predecessor tried to move A SCO Unix virtual machine from our dedicated VMWare environment to a shared Cloud VMWare environment. My predecessor received licensing messages from these critical servers so... (2 Replies)
Discussion started by: timfox1234
2 Replies
6. SCO
hi
i installed sco unix open server 5.0.7 on virtual machine vmware and runing it,
its work perfect and good.
now how i can configuare network at scoadmin that i able to access nework ?
---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ----------
nobody can... (2 Replies)
Discussion started by: farzad226
2 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)