Re: No such file or directory

2013-04-04 Thread Roman Rakus
On 01/02/2013 06:27 PM, Mike Frysinger wrote: that ship has already sailed Sorry for late response, but do you have some link or something? I would like to track it. RR

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

Re: No such file or directory

2013-01-01 Thread Mike Frysinger
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 the error > >> message "No such file

Re: No such file or directory

2013-01-01 Thread Chet Ramey
On 1/1/13 2:49 PM, Aharon Robbins wrote: > In article , > Michael Williamson wrote: >> Hi, >> >> I have a complaint. Apparently, when unknowingly attempting to run a >> 32-bit executable file on a 64-bit computer, bash gives the error message >> "No such file or directory". That error message is

Re: No such file or directory

2013-01-01 Thread Aharon Robbins
In article , Michael Williamson wrote: >Hi, > >I have a complaint. Apparently, when unknowingly attempting to run a >32-bit executable file on a 64-bit computer, bash gives the error message >"No such file or directory". That error message is baffling and frustratingly >unhelpful. Is it possible