From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jonathan Reed <jdreed@MIT.EDU>
Cc: Pavel Machek <pavel@ucw.cz>, 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 21:12:56 +0100 [thread overview]
Message-ID: <20090730211256.31be54e6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0907301259170.5785@infinite-loop.mit.edu>
> They then go and look at /usr/bin/foo, find that it exists, and are
> extremely confused.
-ENOEXEC is just as confusing. It is executable, it will match
(cmp/md5sum etc) with one on another box etc.
> More advanced users might at that point try and run "ldd" on the binary
> (which will also fail, thanks to a missing interpreter).
So fix ldd ?
next prev parent reply other threads:[~2009-07-30 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 17:08 Jonathan Reed
2009-07-30 20:12 ` Alan Cox [this message]
2009-07-30 20:17 ` Pavel Machek
-- 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=20090730211256.31be54e6@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=geofft@MIT.EDU \
--cc=jdreed@MIT.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®