On Sun, 18 Oct 1998, Perry E. Metzger wrote:

: > That said, I'm not quite sure why it gave you the indicated behavior.  The
: > ELF magic number must be different and unrecognized by exec_elf32.  Even so,
: > that still doesn't quite explain it running under a shell....
: 
: Of course it does. If no executable format gets detected by the kernel 
: it tries to run it as a shell script.

Right, but even non-native ELF executables should trigger exec_elf32 to
print a message and not exec.

: The problem is that I can't figure out for the life of me why it isn't 
: detected as an executable.

Well:

On Sun, 18 Oct 1998, Rene Hexel wrote:

:   Hmm, I've just tried communicator-v45-export.x86-unknown-linux2.0 here
: on my NetBSD-1.3.2 box.  It gives me a 'libg++.so.2.7.2: cannot open
: shared object file: No such file or directory', but that's because I
: don't have a libg++.so.2.7.2 in my /emul/linux/usr/lib directory.  But
: that means that the executable must have been recognized as such ...

Perry, I suggest you double-check your kernel config and make sure it has
EXEC_ELF32.  We have all had the `duh!' factor before....

(BTW, do you have COMPAT_SVR4 turned on?)

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)