From owner-freebsd-questions Fri Aug 1 18:01:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23209 for questions-outgoing; Fri, 1 Aug 1997 18:01:44 -0700 (PDT) Received: from mutley.airtech.com.au (dp-m-a14.werple.net.au [203.17.40.114]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23197 for ; Fri, 1 Aug 1997 18:01:35 -0700 (PDT) Received: (from meb@localhost) by mutley.airtech.com.au (8.8.5/8.8.4) id KAA21602; Sat, 2 Aug 1997 10:45:04 +1000 (EST) Date: Sat, 2 Aug 1997 10:45:04 +1000 (EST) Message-Id: <199708020045.KAA21602@mutley.airtech.com.au> From: Matthew Barry To: freebsd-questions@freebsd.org Subject: Linux emulation X-Mailer: VM 6.22 under 19.15p4 XEmacs Lucid Reply-To: mbarry@acm.org Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a couple of linux programs that fail run under the emulation mode with the following message: ELF binary type not known Abort trap When I run file on them I get the type is ELF 32-bit LSB executable, Intel 80386, version 1 This is exactly the same as the information given for linux binaries that do run. The ones that don't run are also statically linked. Is this a known problem with the linux emulation or have I set it up incorrectly? I am running the linux lkm under FreeBSD 2.2.2-RELEASE on a 586 with 32M. Matthew