-ksh: /users/oracle/bin/blob-ksh: : cannot execute [I/O error]
instead of this [version of sh/ksh and UNIX I've used until now]:
ksh: blob: not found
when a non-existent command called blob is executed.
The new error message is so stupid I cannot believe it.
What possessed anyone to make this change ?
--
Lawrence V. Cipriani, l...@lucent.com, Lucent Technologies Inc.
The guilty party is actually UNIXWARE 7.1.0 which is setting errno
to EIO in the lxstat system call. Prior versions of UNIXWARE set
errno to ENOENT. The lxstat sets errno to EIO since a directory
in my $PATH does not exist.
I use the same login environment [and files] on 6 different machines,
so either I customize PATH for every machine or live with this stupid
error message. Sigh.
: -ksh: /users/oracle/bin/blob-ksh: : cannot execute [I/O error]
: instead of this [version of sh/ksh and UNIX I've used until now]:
: ksh: blob: not found
: when a non-existent command called blob is executed.
Is it a non-existent command, or is it an NFS directory in your PATH that's
no longer available? What does "type blob" say about the command?
If it's a command that it found once during this shell execution, but now
it can't find it because mount points have come and gone, the newer message
is probably "better".
It still beats Charles Rivers Data version of unix, with it's friendly
interface, which spouted an entire explanation about mispelled names and
the importance of PATH with every errant command, made worse by the
renaming of commands like ls to something more friendly ;-)
--
---
Clarence A Dold - do...@network.rahul.net
- Pope Valley & Napa CA.