OK, some progress... by trial and error I found the right SATA port for the installation to recognize, and the adapter is now listed as "wd". Now there is a new issue - the following errors now prevent it from going further:
I have run a memory test as suggested on the web, all tests passed. I am using 2 Kingston KVR667D2D4F5/2G (2 GB each) memory modules. I have also cleaned various connectors, etc., as also suggested on the web. I have not touched the 2 CPUs because I don't want to make things worse.
Are there other suggestions I can try? Thanks.
Last edited by rbatte1; 11-16-2015 at 09:53 AM..
Reason: Added CODE tags for output/errors
Hi,
I have the following question :
As far as I know unix doesn't store file creation dates.
Would that imply the following?
tar -cvzf backup.tar --newer
is equal to:
tar -cvzf backup.tar --newer-mtime ? (1 Reply)
I've never had trouble installing freebsd or any linux/unix system on any computer i've tried to do it on. I just recently aquired a Packard Bell, 75mhz Pentium, 482 i believe. Im having difficulty installing it. I have FreeBSD 5.1 on cd and the computer wont even recognize the cd on boot, so it... (2 Replies)
hi all,
i want to setup a solaris10 lab for 50 trainees. kindly let me know all the basic hardware & system requirements for the lab .
with regards,
Raj (5 Replies)
hello everybody,
Is there any training to get deep knowledge an hands on lab with system p hardware firmware microcode upgrading etc... thanks in advance (2 Replies)
Hi All,
Can someone let me know the method or set of commands by which i can retrive manufacturer name of computer system (hardware of machine ) and manufacturer of processor. i get below information when fired psrinfo command :
psrinfo -vp
The physical processor has 1 virtual processor... (6 Replies)
-> We have 2 servers server1 and server2 server.
->server1 is master application and server2 is slave application server. ->output of server1 hardware and slave timing:
# hwclock --show Thu 05 Jun 2014 05:34:08 PM SGT -0.465666 seconds # date Thu Jun 5 17:34:16 SGT 2014
# cd... (6 Replies)
Hello guys.
I wanted to find the System Configuration and Hardware Information on one of my servers. Here is part of the cpu info:
CPU core info:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU... (2 Replies)
Discussion started by: Ymir
2 Replies
LEARN ABOUT DEBIAN
cfree
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.44 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)