From owner-freebsd-arch Fri Feb 23 14:36: 4 2001 Delivered-To: freebsd-arch@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4481837B401 for ; Fri, 23 Feb 2001 14:36:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1NMV0l43659; Fri, 23 Feb 2001 14:31:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A96AC92.F14A90B9@cup.hp.com> Date: Fri, 23 Feb 2001 14:33:16 -0800 (PST) From: John Baldwin To: Marcel Moolenaar Subject: Re: sysctl kern.fallback_elf_brand Cc: arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Feb-01 Marcel Moolenaar wrote: > David O'Brien wrote: >> >> The real fix is to teach the ELF image loader to read the .note.ABI-tag >> section. Then statically linked Linux binaries would be correctly >> identified [since our branding scheme isn't accepted by anyone other than >> us]. > > The use of the section seems broken to me. It's the first time I've > heard of it (so I won't really know how it's used :-). AFAICT, ABI > information is written in e_ident[EI_OSABI] and annotated with flags in > e_flags. That should be enough for our ELF loader. I talked with O`Brien about this today. Many other people view this field as being used when you _extend_ the ELF specification itself. Not as a mechanism for running a plain ELF binary and marking which set of system calls, etc. it assumes. The other method is apparently already used by Linux, BSD/OS, {Net,Open}BSD, etc. I.e., by the rest of the world. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message