> Further, the error message printed when you run such a binary is totally
> unhelpful.

This is an old problem, and it's not easy to fix: the kernel knows when
no emulation package matched, but this information does not go back t
ouserland. Even if it did, it would be useless because we would have to
modify each program that calls execve() so that it would be able to
explain what is going on to th user. Modifying our shells would be
acceptable, but theses are not the only programs to use execve, so it's
not reasonable.

I proposed to make this information known to libc, and to output a
warning from libc on stderr or stdout when this situation arise, but
most peope thought it was not libc's job to output a message.

The other solution would be a warning in the kernel logs, but most users
won't see it as they launch their binary.

-- 
Emmanuel Dreyfus
p99dreyf@criens.u-psud.fr