From: Pavel Machek <pavel@ucw.cz>
To: Jonathan Reed <jdreed@MIT.EDU>
Cc: Geoffrey Thomas <geofft@MIT.EDU>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Return ENOEXEC, not ENOENT, if a binary's or script's interpreter doesn't exist.
Date: Thu, 30 Jul 2009 22:17:20 +0200 [thread overview]
Message-ID: <20090730201720.GA30001@elf.ucw.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.0907301259170.5785@infinite-loop.mit.edu>
On Thu 2009-07-30 13:08:58, Jonathan Reed wrote:
>> NAK. Current behaviour is useful -- and it is really file thats
>> missing.
>
> The current behavior is only useful to people who have an understanding
> of how interpreters and binaries work on Linux. The average desktop
> user
Proposed behaviour is useless to everyone.
> does not have that understanding. The average user gets an error message
> such as:
>
> /usr/bin/foo: No such file or directory.
>
> They then go and look at /usr/bin/foo, find that it exists, and are
> extremely confused.
ENOEXEC is confusing, too. It will have x bit.
>> Please improve manpage instead.
>
> What manpage do you suggest needs improvement? execve(2)? That
>again
execve, I'd say.
> requires an average user to realize that they need to go look at the
> execve(2) manpage. The average user is not going to realize that.
Improve shells to provide more helpful error message?
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-30 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 17:08 [PATCH] Return ENOEXEC, not ENOENT, if a binary's or script's interpreter doesn't exist Jonathan Reed
2009-07-30 20:12 ` Alan Cox
2009-07-30 20:17 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 7:48 Geoffrey Thomas
2009-07-10 5:18 ` Amerigo Wang
2009-07-10 16: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=20090730201720.GA30001@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=geofft@MIT.EDU \
--cc=jdreed@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