hi,
is there any way to find the exact meaning of message given
by a Unix command
for example
mv: cannot access hello.c

similarly is there any way to find the meaning of the
error number or message displayed
by compilers

Rakesh UV

[ Post a follow-up to this message ]

rakesh uv <uvrakesh@gmail.com> writes:

> hi,
>            is there any way to find the exact meaning of message given
> by a Unix command
> for example
>           mv: cannot access hello.c

Ask Google for "mv: cannot access".  Remember the quotes.

>             similarly is there any way to find the meaning of the
> error number or message displayed
> by compilers

Ask Google for the invariant parts of the thing you need to know.
--
Thorbjørn Ravn Andersen

[ Post a follow-up to this message ]

On Fri, 21 Dec 2007 00:06:39 -0800 (PST) rakesh uv <uvrakesh@gmail.com> wrote:
> hi,
>            is there any way to find the exact meaning of message given
> by a Unix command
> for example
>           mv: cannot access hello.c

1) the documentation
2) truss or strace or whatever system call tracing facility your OS provides

sometimes you can't find a "precise" reason for an error as the kernel
simply does not return that info.  e.g. EACCES might be due to file
permissions, ACL or MAC controls and you wouldn't know which.

>             similarly is there any way to find the meaning of the
> error number or message displayed
> by compilers

1) the documentation
2) usenet or other forums

-frank

[ Post a follow-up to this message ]