From owner-freebsd-current  Thu Jul 25 14:43:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA03336
          for current-outgoing; Thu, 25 Jul 1996 14:43:26 -0700 (PDT)
Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA03323
          for <current@freebsd.org>; Thu, 25 Jul 1996 14:42:56 -0700 (PDT)
Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.7.5/8.7.3) with ESMTP id OAA17783; Thu, 25 Jul 1996 14:42:41 -0700 (PDT)
From: Mostyn/Annabella <mrl@teleport.com>
Received: (from mrl@localhost) by linda.teleport.com (8.7.5/8.7.3) id OAA06919; Thu, 25 Jul 1996 14:42:38 -0700 (PDT)
Message-Id: <199607252142.OAA06919@linda.teleport.com>
Subject: Re: Current, elfkit, linux ELF static bin
To: chuckr@Glue.umd.edu (Chuck Robey)
Date: Thu, 25 Jul 1996 14:42:38 -0700 (PDT)
Cc: current@freebsd.org
In-Reply-To: <Pine.OSF.3.91.960725164830.8213D-100000@modem.eng.umd.edu> from "Chuck Robey" at Jul 25, 96 04:54:44 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> On Thu, 25 Jul 1996, Mostyn/Annabella wrote:
> 
> > Howdy,
> > 
> > Running current with elfkit set up to provide /usr/libexec/ld-elf.so.1
> > seems to run hand rolled ELF bins fine.
> > However, importing an ELF linux static bin and running (after installing
> > the linux lkm) bombs.
> > The binary is the "Bulldozer" WYSIWYG HTML editor from
> > http://cscsun1.larc.nasa.gov/~rboykin/Dozer/
> > 
> > Running it gets
> > 
> > ./dozer
> > Memory fault (core dumped)
> > 
> > and produces a "garbled" directory which looks like
> > 
> > drw-r-----  2 root  wheel      512 Jul 23 15:45 <V?o/
> > 
> 
> The ld-elf.so.1 is only for linux executeables that are dynamically 
> linked.  When you do a 'file Bulldozer' (assuming that's the name of your 
> executeable) what does FreeBSD tell you (what type of file is it really?)

Thanks, I was aware of the dynamic loader - I was imprecise - statically
linked ELF bins made locally work too. I was only pointing out that it
seems the kernel image activator for ELF seemed to be working OK.

The "dozer" file, by the way, owns up to being ->

file dozer
dozer: ELF 32-bit LSB executable, Intel 80386, version 1

Mostyn