From: Olaf van der Spek <olafvdspek@gmail.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Luca Barbieri <luca.barbieri@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: execve() returns ENOENT when ld-linux.so isn't found
Date: Mon, 29 Mar 2010 16:40:36 +0200 [thread overview]
Message-ID: <b2cc26e41003290740i5c548cabgc95d91958cd1075a@mail.gmail.com> (raw)
In-Reply-To: <a36005b51003270505s42b5e69co14d2acbb27dc204a@mail.gmail.com>
On Sat, Mar 27, 2010 at 1:05 PM, Ulrich Drepper <drepper@gmail.com> wrote:
> On Sat, Mar 27, 2010 at 04:50, Olaf van der Spek <olafvdspek@gmail.com> wrote:
>> It didn't 'work' for me.
>
> You still don't get it? No shell provides you with a correct error
> message. There is quite some work involved (reading program header,
> finding the interpreter entry, checking the file) to give a meaningful
> error message. Changing the error code alone achieves nothing.
File not found is a very common error message with a pretty will
understood meaning. Overloading it in this way causes confusion.
Overloading another error code would avoid this confusion, especially
since it's far less used.
Olaf
next prev parent reply other threads:[~2010-03-29 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
2010-03-24 22:35 ` drepper
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=b2cc26e41003290740i5c548cabgc95d91958cd1075a@mail.gmail.com \
--to=olafvdspek@gmail.com \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.barbieri@gmail.com \
/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