From owner-freebsd-questions  Sun Mar 17 19:19:57 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA24842
          for questions-outgoing; Sun, 17 Mar 1996 19:19:57 -0800 (PST)
Received: from birk04.studby.uio.no (birk04.studby.uio.no [129.240.214.13])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA24836
          for <freebsd-questions@freebsd.org>; Sun, 17 Mar 1996 19:19:52 -0800 (PST)
Received: (from aagero@localhost) by birk04.studby.uio.no (8.7.4/8.6.12) id EAA00321; Mon, 18 Mar 1996 04:19:29 +0100 (MET)
Date: Mon, 18 Mar 1996 04:19:29 +0100 (MET)
Message-Id: <199603180319.EAA00321@birk04.studby.uio.no>
From: "Åge Røbekk" <aagero@aage.aage.priv.no>
To: freebsd-questions@freebsd.org
Subject: statically linked linux ELF binaries
MIME-Version: 1.0
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


In -current, I've noticed that statically linked linux ELF binaries
get executed even though the linux binary loader is not installed. I
assume this is valid since the linux emul only loads and executes
a.out binaries. Can the freebsd ELF binary loader distinguish between
FreeBSD ELF and Linux ELF? Or is it a problem with the linux emulation
code. I noticed this when running the ELF version of "ldconfig"
(1.7.14) in order to sort out the symlinks in /compat/linux/lib and
make a valid ld.so.cache.

-aage