Re: execname not specified in AUX vector

[christos%astron.com@localhost (Christos Zoulas)]

In article <x63a8ia0as.fsf%dynalabs.de@localhost>,
Michael Piotrowski  <mxp%dynalabs.de@localhost> wrote:
>Hi,
>
>I've recently done a fresh install of NetBSD 5.0 (i386, on VMware
>Fusion).  So far, everything seems to be fine, except for one problem
>I've noticed with shell scripts:
>
>For most of my shell scripts I'm using ksh93, built from the original
>ast sources (not from pkgsrc; currently Version JM 93t+ 2009-05-01).  It
>is installed as /opt/ast/bin/ksh, so that's also what the shebang line
>says.
>
>Now, if I try to run such a script from the current directory, e.g.,
>
>  $ ./script
>
>I get the error message
>
>  execname not specified in AUX vector: No such file or directory
>
>There is no problem if the script is found in PATH and called as
>
>  $ script
>
>nor when I specify the full path, e.g.,
>
>  $ ~+/script
>
>Since I don't have this problem on NetBSD 4.0, it seems that something
>has changed in 5.0.  I've googled for the error message but have found
>nothing.
>
>I'd be grateful for any suggestion on what the problem may be.
>
>Thanks and greetings

You could turn on the #ifdef notyet's in kern_exec.c, or make ksh not use
$ORIGIN.

christos