Bash-4.2 Official Patch 42

2013-01-02 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.2 Patch-ID: bash42-042 Bug-Reported-by:Adam Pippin Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2012-11/msg00087.html Bu

Bash-4.2 Official Patch 41

2013-01-02 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.2 Patch-ID: bash42-041 Bug-Reported-by:Andrey Borzenkov Bug-Reference-ID: <20121202205200.21344...@opensuse.site> Bug-Reference-URL: http://lists.gnu.org/arch

Bash-4.2 Official Patch 40

2013-01-02 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.2 Patch-ID: bash42-040 Bug-Reported-by:Andrey Zaitsev Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2012-04/msg00144.html

Fwd: No such file or directory

2013-01-02 Thread Michael Williamson
-- Forwarded message -- From: Eric Blake Date: Wed, 02 Jan 2013 10:41:07 -0700 Subject: Re: No such file or directory To: Michael Williamson On 01/02/2013 10:30 AM, Michael Williamson wrote: > Hi Eric, > > Thanks for your explanation. I realize now that I should > submit my sugge

Re: No such file or directory

2013-01-02 Thread Mike Frysinger
On Wednesday 02 January 2013 07:07:49 Roman Rakus wrote: > On 01/02/2013 02:25 AM, Mike Frysinger wrote: > > On Tuesday 01 January 2013 15:10:00 Chet Ramey wrote: > >> On 1/1/13 2:49 PM, Aharon Robbins wrote: > >>> Michael Williamson wrote: > I have a complaint. Apparently, when unknowingly at

Re: No such file or directory

2013-01-02 Thread Mike Frysinger
On Wednesday 02 January 2013 09:47:10 Roman Rakus wrote: > On 01/02/2013 03:31 PM, Eric Blake wrote: > > On 01/02/2013 07:28 AM, Michael Williamson wrote: > >> Thanks for your explanation. Now I have another question. > >> Why is the error message for ENOENT simply > >> "No such file or directory",

Re: No such file or directory

2013-01-02 Thread Roman Rakus
On 01/02/2013 03:31 PM, Eric Blake wrote: On 01/02/2013 07:28 AM, Michael Williamson wrote: Hi Aharon, Thanks for your explanation. Now I have another question. Why is the error message for ENOENT simply "No such file or directory", when the man page for execve has this complete description: "T

Re: No such file or directory

2013-01-02 Thread Eric Blake
On 01/02/2013 07:28 AM, Michael Williamson wrote: > Hi Aharon, > > Thanks for your explanation. Now I have another question. > Why is the error message for ENOENT simply > "No such file or directory", when the man page for execve > has this complete description: > "The file filename or a script or

Re: No such file or directory

2013-01-02 Thread Michael Williamson
Hi Aharon, Thanks for your explanation. Now I have another question. Why is the error message for ENOENT simply "No such file or directory", when the man page for execve has this complete description: "The file filename or a script or ELF interpreter does not exist, or a shared library needed for

Re: No such file or directory

2013-01-02 Thread Roman Rakus
On 01/02/2013 02:25 AM, Mike Frysinger wrote: On Tuesday 01 January 2013 15:10:00 Chet Ramey wrote: On 1/1/13 2:49 PM, Aharon Robbins wrote: Michael Williamson wrote: I have a complaint. Apparently, when unknowingly attempting to run a 32-bit executable file on a 64-bit computer, bash gives th