18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Exec format error<br />

Cause<br />

This often happens when trying to run software compiled for different systems or<br />

architectures, such as when executing Solaris 2 programs on a SunOS 4.1 system, or<br />

when trying to execute SPARC-specific programs on an x86 machine. On a Solaris 2<br />

system, it can also occur if the Binary Compatibility Package was not installed.<br />

Action<br />

Make sure that the software matches the architecture and system you’re using. The<br />

file(1) command can help you determine the target architecture. If you’re using<br />

SunOS 4.1 software on a Solaris 2 system, make sure that the Binary Compatibility<br />

Package is installed. You can check for it using this command:<br />

$ pkginfo | grep SUNWbcp<br />

Technical Notes<br />

A request was made to execute a file that, although it has the appropriate<br />

permissions, does not start with a valid format.<br />

The symbolic name for this error is ENOEXEC, errno=8.<br />

See Also<br />

See the a.out(4) man page for a description of executable files.<br />

"F"<br />

failed to initialize adapter<br />

Cause<br />

Using an Adaptec AHA-154x Cx SCSI HBA during installation of Solaris 2.x x86, you<br />

may see the message during the mdb device probe that says<br />

66 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!