When a user attempts to execute an executable that is not
recognized as an executable by the system, the generated error is "No
such file or directory"
Repeat-By:
Obtain an i386 executable instead of an amd64 executable and
attempt to run it via ./name_of_executable
Fix:
If the file exists but cannot be executed, issue an error
message that is not so misleading. The file does exist, so "No such file
or directory" seems plain wrong.