From owner-freebsd-hackers Wed Oct 16 19:30:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24569 for hackers-outgoing; Wed, 16 Oct 1996 19:30:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24519; Wed, 16 Oct 1996 19:29:58 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA09992; Thu, 17 Oct 1996 11:59:44 +0930 From: Michael Smith Message-Id: <199610170229.LAA09992@genesis.atrad.adelaide.edu.au> Subject: Re: Linux compat issue(s) To: sos@FreeBSD.org Date: Thu, 17 Oct 1996 11:59:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, jdp@polstra.com, hackers@FreeBSD.org In-Reply-To: <199610161218.OAA22084@ra.dkuug.dk> from "sos@FreeBSD.org" at Oct 16, 96 02:18:32 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org stands accused of saying: > > Ahh, yes, I misunderstood you, WHEN we have this in place it will > work (of cause), but I have allready some FreeBSD ELF bins which dont > know :) (Yeah I know I can recompile them). > What I meant was that default is native, not something else... Understood. I just think that the default should be more intelligent. > > Please, no. If it is unidentifiable, it is by definition not a FreeBSD > > ELF binary. I stand by "if it can't be identified, feed it to the > > most recently-loaded ELF interpreter and pray". > > Gee, then we will have to keep track on what was loaded last :( Just walk to the end of interp_list[] and throw it at whichever interpreter is lurking there. Perhaps have the code which exterminates such a process if it goes wrong be a little more forthcoming with why, if having a useful error message would help. > > In the short term, this will have the happy side effect that static > > Linux ELF binaries will suddenly magically work, which is a Good Thing. > > IF, the linux emu is loaded, and libs are installed, and you are > lucky to have the right versions of them :( Ok, "modulo the usual Linux crap". Note that the path-detecting code probably wants to understand /compat/netbsd, which hadn't occurred to me before. NetBSD people lurking - is there a reliable way to discriminate a static NetBSD ELF i386 binary from any other static i386 ELF binary? > > > markelf, brandelf or just plan elf (fixelf sounds a bit harsh :) ) > > > > Heh. "smurf" > > Didn't think of that one myself :) I considered "squish" too, but thought it was a little too obscure. I sprayed my breakfast all over my desk when I read "elfspay" 8) I can just see the example now : "elfspay -t ogrampay" > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[