Re: Unfortunate error message for invalid executable

[Andrew Athan]

I’ll give it a shot.

A.

> On May 28, 2022, at 4:35 PM, Dale R. Worley <worley@alum.mit.edu> wrote:
> 
> AA via Bug reports for the GNU Bourne Again SHell <bug-bash@gnu.org>
> writes:
>> I.e., something like "I'm not sure what's going on, but your path 
>> definitely exists, yet the kernel says otherwise."
>> 
>> ... something like fprintf(STDERR,"No such file or directory while 
>> attempting to execute %s (it exists, but cannot be executed)",path);
> 
> Historically, the way to get something like this to happen is to design
> and code the modification that does it.  That has the advantage that you
> have to bite the bullet and instead of just describing the general idea,
> decide on a concrete implementation.  That sounds obvious, but there is
> a long history of ideas in software that *sound good* but for which
> there is no implementation that sucks less than the problem the idea
> seeks to solve.
> 
> Dale