From owner-freebsd-current Mon Feb 10 22:07:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA00999 for current-outgoing; Mon, 10 Feb 1997 22:07:10 -0800 (PST) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00994 for ; Mon, 10 Feb 1997 22:07:04 -0800 (PST) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.5) id WAA14472; Mon, 10 Feb 1997 22:07:02 -0800 (PST) Received: from localhost by newport.ece.uci.edu (8.8.5) id WAA23974; Mon, 10 Feb 1997 22:07:00 -0800 (PST) Message-Id: <199702110607.WAA23974@newport.ece.uci.edu> To: Michael Smith cc: current@freebsd.org Subject: Re: linux ELF codine no go on 2.2 Gamma In-reply-to: Your message of "Thu, 06 Feb 1997 16:57:12 +1030." <199702060627.QAA01550@genesis.atrad.adelaide.edu.au> Date: Mon, 10 Feb 1997 22:06:59 -0800 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Linux, SCO, and BSDI binaries. Why not make the assumption in the >> kernel that any binary loaded from /compat/[linux,sco,bsdi] is an elf binary >> of the type denoted by the subdirectory. This would eliminate any need >> to brand the binaries. You would just install them under the appropriate >> subdirectory of /compat. This makes the implicit and reasonable assumption >> that any elf binary not under /compat is a native FreeBSD one. > > I've already proposed this; I was assuming that SOS had already done it. > > If there's no major disagreement, I'll look at adding the code to > imgact_elf.c at some point soonish. > Umm, I think it is a bad idea to make the assumption that any elf binary not under /compat is a native FreeBSD one. I would still like to run branded/linked Linux binaries outside of /compat. Probably what would be reasonable to do is if all else fails and the elf type is not known, use the /compat/(*) as a hint for the type. Steven