From: Andreas Schwab <schwab@linux-m68k.org>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
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 18:00:01 +0200 [thread overview]
Message-ID: <m2k4svuni6.fsf@igel.home> (raw)
In-Reply-To: <b2cc26e41003290740i5c548cabgc95d91958cd1075a@mail.gmail.com> (Olaf van der Spek's message of "Mon, 29 Mar 2010 16:40:36 +0200")
Olaf van der Spek <olafvdspek@gmail.com> writes:
> File not found is a very common error message with a pretty will
> understood meaning.
And perfectly applicable here (as you write yourself in the subject).
> Overloading another error code would avoid this confusion, especially
> since it's far less used.
Changing a well understood error number into a totally misleading one
only increases confusion.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-03-29 16:00 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 ` execve() returns ENOENT when ld-linux.so isn't found 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 [this message]
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=m2k4svuni6.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.barbieri@gmail.com \
--cc=olafvdspek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.