This error occurs when users try to share a resource that is not on the local machine, or try to mount/unmount a device or path name that is on a remote machine.
The symbolic name for this error is EREMOTE, errno=66.
This is the OpenBoot PROM monitor prompt. From this prompt, you can boot the system (from disk, CD-ROM, or net), or you can use the go command to continue where you left off.
If you suddenly see this prompt, look at the messages above it to see if the system crashed. If no other messages appear, and you just typed Stop-A or plugged in a new keyboard, type go to continue. You might need to Refresh the window system from its Workspace Menu.
Never invoke sync from the ok prompt without first running the fsck(1M) command, especially if the filesystem has changed.
An operation was attempted on a non-blocking object that already had an operation in progress.
The symbolic name for this error is EALREADY, errno=149.
The associated asynchronous operation was canceled before completion.
The symbolic name for this error is ECANCELED, errno=47.
When you use admintool to add a user to a newly-created group, admintool issues this error.
Apply patch 101384-05 to fix bug ID 1151837 and to provide a workaround for bug ID 1153087.
This error indicates that no system support exists for some function that the application requested.
Ask the system vendor for an upgrade, or contact the vendor or author of the application for an update.
This message indicates that no system support exists for an operation. Many modules set this error when a programming function is not yet implemented. If you are writing a program that produces this message while calling a system library, try to find and use an alternative library function. Future versions of the system might support this operation; check system release notes for further information.
The symbolic name for this error is ENOSYS, errno=89.
For example, trying to accept a connection on a datagram transport endpoint.
The symbolic name for this error is EOPNOTSUPP, errno=122.
An operation that takes a long time to complete (such as a connect) was attempted on a non-blocking object.
The symbolic name for this error is EINPROGRESS, errno=150.
This error message occurred when the customer used the link from /opt/bin/jws to /opt/SUNWjws/JWS/sparc-S2/bin/jws, to start Java Workshop. Typing in the full pathname works fine, typing jws gives the error.
This happens because /opt/bin/jws is not /opt/SUNWjws/JWS/sparc-S2/bin/jws, which a script that runs another script: $_SS_JWS_HOME/solaris/bin/locate_dirs.
So whatever /opt/bin/jws is, it is not setting $_SS_JWS_HOME correctly. Take that out of your path and put /opt/SUNWjws/JWS/sparc-S2/bin/jws in your path so which jws returns: /opt/SUNWjws/JWS/sparc-S2/bin/jws.
A bad option or level was specified when getting or setting options for a protocol.
The symbolic name for this error is ENOPROTOOPT, errno=99.
Hundreds of different programs can produce this message when the system is running many large applications simultaneously. This message usually means that the system has run out of swap space (virtual memory).
See the message "Not enough space" for details. Any data written during this condition will probably be lost.
During a STREAMS open, either no STREAMS queues or no STREAMS head data structures were available. This is a temporary condition; one may recover from it if other processes release resources.
The symbolic name for this error is ENOSR, errno=63.
After creating volumes in rootdg to be used as additional swap and adding these to the /etc/vfstab file, an error message is displayed at boot time complaining about overlapping swap volumes.
Change the names of these volumes to read swap1, swap2, etc...
If you still get this message after making the above change, edit the /sbin/swapadd script. Find the line:
c=`$SWAP -l | grep -c '\\<'${special}'\>'`and change it to
=`$SWAP -l | grep -c ''${special}''`Also see bug number 1215062 for more information on this behavior.