Sponsored Content
Operating Systems SCO memfs.fs I/O Error - urgent attention please Post 98485 by R@LE on Wednesday 8th of February 2006 01:30:29 PM
Old 02-08-2006
Error memfs.fs I/O Error - urgent attention please

Hy guys,

During installation of machine (Pentium x86, 64MB RAM), well during booting SCO UnixWARE 7.1.1 diskette 1/2 i get following error (after SCO logo)

"memfs.fs: I/0 error or unexpected EOF"
Bootstrap Command Processor
...
[boot] _

Please advise!
 

5 More Discussions You Might Find Interesting

1. AIX

Turn off attention LED ( P275)

How can I turn off the attention led (amber led)??. My machine is a P275 with AIX 5.2. Thanks for your time. Reinaldo F. Dias Unix Support Analyst PLM & Engineering T-Systems do Brasil (2 Replies)
Discussion started by: Reinaldo Dias
2 Replies

2. Shell Programming and Scripting

Attention Shell Scripters

Hi mates, Hope this is very simple for those who r well versed wth scripting but I'm literally new to scripting so please guys help me out in writing these basic scripts.I'm using Bash and Vi editor. 1 ....How to write a script that takes a file as an argument. The script should be able to... (1 Reply)
Discussion started by: bobby36
1 Replies

3. Shell Programming and Scripting

please pay your attention on this .......

HI All, I am working on Solaris 5.9 servers.Now i want a script which collect files with format like msgs_cheux301_10Jun2008 , login_cheux301_10Jun2008 and history_cheux301_10Jun2008.tar into seperate folders with a specific name. The script will collect files with one week old and it should... (2 Replies)
Discussion started by: Renjesh
2 Replies

4. AIX

Attention Led on HMC

We use HMC to manage two logical partitions. LPARs don't have any problem but HMC's, itself, attention led is on. :eek: I am not sure if that's going to affect LPARs, but just wanted to be sure.... :confused: Has anyone come across such problem on HMC? Where can you suggest to look for logs... (1 Reply)
Discussion started by: royalliege
1 Replies

5. UNIX for Advanced & Expert Users

Solaris sendmail not paying attention to virtusertable

I'm on Solaris 5.11 running sendmail. Local usernames are of the form <letters><numbers> (e.g. hn06511). In the past we used aliases to make point to <username>@olddomain.com. <username> <username>@olddomain.com Now there's a new email address scheme and a new domain. Now email... (8 Replies)
Discussion started by: defaria
8 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)
All times are GMT -4. The time now is 12:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy