From: Olaf van der Spek <olafvdspek@gmail.com>
To: drepper@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: execve() returns ENOENT when ld-linux.so isn't found
Date: Wed, 24 Mar 2010 23:10:58 +0100 [thread overview]
Message-ID: <b2cc26e41003241510k64fdcf3udbe9a4ca102f9792@mail.gmail.com> (raw)
In-Reply-To: <g766ycf6hwz4din58tUYAxe124vaj_firegpg@mail.gmail.com>
On Wed, Mar 24, 2010 at 2:49 PM, <drepper@gmail.com> wrote:
> On Thu, Mar 18, 2010 at 07:42, Olaf van der Spek <olafvdspek@gmail.com>
> wrote:
>>
>> $ ls -l
>> -rwxr-xr-x 1 olaf olaf 560165 2010-03-18 15:21 xwis
>> $ ./xwis
>> -bash: ./xwis: No such file or directory
>
> Your shell should handle this. I'm not sure whether it's in the upstream
Why?
And why can't the kernel returned the more appropriate ENOEXEC?
> bash (it should be) but I wrote a long, long time ago a patch which produces
> better messages. On my system I get:
>
> $ ./u
> bash: ./u: /some/path/does-not-exist: bad ELF interpreter: No such file or
> directory
>
>
> It doesn't really matter what the kernel returns. The shell should do its
> job and at least the RHEL/Fedora version does it for a long time now.
That should be pushed upstream then.
Olaf
next prev parent reply other threads:[~2010-03-24 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 14:42 Olaf van der Spek
2010-03-24 13:35 ` Olaf van der Spek
2010-03-24 13:49 ` drepper
2010-03-24 22:10 ` Olaf van der Spek [this message]
2010-03-24 22:35 ` drepper
[not found] <b2cc26e41003241537h228028c4n1374f4b042175885@mail.gmail.com>
2010-03-24 22:45 ` drepper
2010-03-25 19:29 ` Olaf van der Spek
2010-03-25 21:00 ` Luca Barbieri
2010-03-26 11:56 ` Ulrich Drepper
2010-03-26 18:40 ` Olaf van der Spek
2010-03-26 21:06 ` Luca Barbieri
2010-03-26 21:15 ` Ulrich Drepper
2010-03-27 11:50 ` Olaf van der Spek
2010-03-27 12:05 ` Ulrich Drepper
2010-03-29 14:40 ` Olaf van der Spek
2010-03-29 14:57 ` Ulrich Drepper
2010-03-29 16:00 ` Andreas Schwab
2010-03-31 19:36 ` Olaf van der Spek
2010-03-27 14:51 ` Luca Barbieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2cc26e41003241510k64fdcf3udbe9a4ca102f9792@mail.gmail.com \
--to=olafvdspek@gmail.com \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome