From owner-freebsd-current  Mon May 12 05:03:04 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA15519
          for current-outgoing; Mon, 12 May 1997 05:03:04 -0700 (PDT)
Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15504
          for <current@freebsd.org>; Mon, 12 May 1997 05:03:00 -0700 (PDT)
Received: (from sos@localhost) by sos.freebsd.dk (8.8.5/8.7.3) id OAA02191; Mon, 12 May 1997 14:03:33 +0200 (MEST)
From: Søren Schmidt <sos@sos.freebsd.dk>
Message-Id: <199705121203.OAA02191@sos.freebsd.dk>
Subject: Re: LINUX statically linked ELF nogo?
In-Reply-To: <Pine.BSF.3.95.970512130402.3934A-100000@totum.plaut.de> from Michael Reifenberger at "May 12, 97 01:14:58 pm"
To: root@totum.plaut.de (Michael Reifenberger)
Date: Mon, 12 May 1997 14:03:33 +0200 (MEST)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Michael Reifenberger who wrote:
> Hi,
> Is anybody aware of a problem with statically linked Linux-ELF binaries?

Yes, its a "feature" of ELF...
> 
> ./bin/xcontrol
> 	ELF binary type not known 
> 	Abort
> 
> Can anybody help?

man brandelf

> Probably we need to add the according identifying bits to the Linux-exe-loader

Allready there...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..