From: Pavel Machek <pavel@ucw.cz>
To: Geoffrey Thomas <geofft@MIT.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Return ENOEXEC, not ENOENT, if a binary's or script's interpreter doesn't exist.
Date: Fri, 10 Jul 2009 18:17:59 +0200 [thread overview]
Message-ID: <20090710161758.GC1396@ucw.cz> (raw)
In-Reply-To: <1247125700-12630-1-git-send-email-geofft@mit.edu>
On Thu 2009-07-09 03:48:20, Geoffrey Thomas wrote:
> If you try to execute a binary compiled for ld-linux.so.1 (libc5) on a machine
> with only ld-linux.so.2 (libc6), your shell will claim "mybinary: No such file
> or directory", even though the binary exists. The ENOENT actually applies to
> the ELF intepreter, not to the file itself. The same happens if you have a
> nonexistent interpreter in a shell script's shebang line.
>
> Give a more helpful and more expected error, "cannot execute binary file", in
> these cases.
NAK. Current behaviour is useful -- and it is really file thats
missing.
Please improve manpage instead.
(chmod 000 /lib also produces 'interesting' error messages. Better
document those, too). Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-11 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 7:48 [PATCH] Return ENOEXEC, not ENOENT, if a binary's or script's interpreter doesn't exist Geoffrey Thomas
2009-07-10 5:18 ` Amerigo Wang
2009-07-10 16:17 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-30 17:08 Jonathan Reed
2009-07-30 20:12 ` Alan Cox
2009-07-30 20:17 ` Pavel Machek
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=20090710161758.GC1396@ucw.cz \
--to=pavel@ucw.cz \
--cc=geofft@MIT.EDU \
--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