tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: sh(1) vs. ksh(1)



On Thu, 23 Oct 2008, Hauke Fath wrote:
> From <http://issues.sxemacs.org/show_bug.cgi?id=89>:
>
> [hf@Gstoder] /<2>sxemacs/sxemacs-22.1.9 > /bin/sh ./config.sub sun4
> sparc-sun-sunos4.1.1
> [hf@Gstoder] /<2>sxemacs/sxemacs-22.1.9 > /bin/ksh ./config.sub sun4
> "./config.sub" not found
> [hf@Gstoder] /<2>sxemacs/sxemacs-22.1.9 > /usr/pkg/bin/bash ./config.sub sun4
> sparc-sun-sunos4.1.1

What are the permissions of that file?  I checked the web page you
mentioned, and found that the file was a symlink, but I didn't notice
any ls(1) output showing the permissions of the target file.  I was
unable to reproduce the problem myself on NetBSD-current using a symlink
to a readable but non-executable file.

The first line of content may also be relevant, if ksh is trying to
parse "#!" lines itself (though I see no hint in the NetBSD ksh source
code that it might be doing that).

--apb (Alan Barrett)


Home | Main Index | Thread Index | Old Index