From owner-freebsd-hackers Wed Oct 16 04:55:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA15295 for hackers-outgoing; Wed, 16 Oct 1996 04:55:43 -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 EAA15288; Wed, 16 Oct 1996 04:55:35 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id VAA03723; Wed, 16 Oct 1996 21:25:26 +0930 From: Michael Smith Message-Id: <199610161155.VAA03723@genesis.atrad.adelaide.edu.au> Subject: Re: Linux compat issue(s) To: sos@FreeBSD.org Date: Wed, 16 Oct 1996 21:25:26 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, jdp@polstra.com, hackers@FreeBSD.org In-Reply-To: <199610161145.NAA21933@ra.dkuug.dk> from "sos@FreeBSD.org" at Oct 16, 96 01:45:44 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: > > > > Native would be pointless, as native binaries will always be > > identifiable. The reason I ask is that for the situation where the > > NO, wrong, we can't even see if the bin is native !!!! Yes we can. You're coming up with a means of identifying FreeBSD binaries which JDP will be putting in the linker. There aren't many BSD ELF binaries out there, so _now_ is the time to mandate that for a FreeBSD ELF binary to be recognised as such, it must be branded. Alternatively, get JDP to use the PT_NOTE idea. Regardless, a FreeBSD ELF binary _must_ be uniquely identifiable; there is no room for debate on this 8) > Hypothetical ?? I have a SVR4 emu :), I just can't/wont't release the code... If you're going to dangle teasers, at least explain them 8) > I would wote for ALWAYS branding the ELF files, that way there is > NO doubt what sex they are, thus giving least trouble. Agreed. > > The last ditch "I have no idea, winging it" case could just default to > > the last interpreter in the list - that would let the user alter the > > default if there were more than one available by unloading and > > reloading the LKM. > > I'd rather have it give up and say unknown binary format or something like > that, or try running it as a FreeBSD ELF bin. 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". 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. > Now, for a practical question, what should I call the little util ?? > > markelf, brandelf or just plan elf (fixelf sounds a bit harsh :) ) Heh. "smurf" > 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 [[