Date: Thu, 25 Jul 1996 21:53:27 -0700 (PDT) From: Sujal Patel <smpatel@umiacs.umd.edu> To: Mostyn/Annabella <mrl@teleport.com> Cc: Chuck Robey <chuckr@Glue.umd.edu>, current@FreeBSD.ORG Subject: Re: Current, elfkit, linux ELF static bin Message-ID: <Pine.NEB.3.92.960725214836.177A-100000@localhost> In-Reply-To: <199607252142.OAA06919@linda.teleport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 25 Jul 1996, Mostyn/Annabella wrote: > > > 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/ With a dynamic binary, the image activater can uses some of the ELF header to determine which system the ELF binary was meant to run on. Unfortuantely, with the static binary, you can't tell whether the binary is meant for FreeBSD or for Linux. FreeBSD needs to implement a way of differentiating Linux & FreeBSD ELF binaries. Problem report 1102, describes one possible solution, but it is completely brain dead (it should work though). I believe NetBSD recently implemented a 'hack' to get this working for them. > > > ./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/ This is consistent with running a Linux ELF binary with the FreeBSD's sysvec. Sujal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960725214836.177A-100000>