From owner-freebsd-current  Sun Apr 21 22:13:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA10361
          for current-outgoing; Sun, 21 Apr 1996 22:13:15 -0700 (PDT)
Received: from neon.Glock.COM (neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA10356
          Sun, 21 Apr 1996 22:13:12 -0700 (PDT)
Received: from neon.Glock.COM (localhost [127.0.0.1]) by neon.Glock.COM (8.7.5/8.7.3) with SMTP id BAA01330; Mon, 22 Apr 1996 01:13:10 -0400 (EDT)
Message-ID: <317B1566.41C67EA6@Glock.COM>
Date: Mon, 22 Apr 1996 01:13:10 -0400
From: "matthew c. mead" <mmead@Glock.COM>
Organization: Glock Telecommunications
X-Mailer: Mozilla 3.0b2 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: smpatel@freebsd.org
CC: current@freebsd.org
Subject: possible 4th option? [Re: kern/1102]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I was looking through your discussion on the difficulties of
differentiating a Linux ELF binary from a FreeBSD ELF binary.  The 2nd
option you mention is the one in which you would use currently unused
bytes in the ELF e_ident tag.  What you proposed for this method of
distinguishing the two different systems' binaries was to modify each
Linux executable so that it has an identification byte in it.  Since at
this point we only (am I wrong here?) support Linux and FreeBSD ELF
binaries, wouldn't it be sufficient to have our ELF binary generation
utilities put an identifier for FreeBSD into the ELF binary as mentioned
above, and if that is detected, use the FreeBSD sysvec set, otherwise
assume the Linux sysvec set?


-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/