From owner-freebsd-current Mon Apr 22 05:34:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01845 for current-outgoing; Mon, 22 Apr 1996 05:34:52 -0700 (PDT) Received: from s1.GANet.NET (s1.GANet.NET [199.18.201.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA01840 Mon, 22 Apr 1996 05:34:50 -0700 (PDT) Received: (from ec0@localhost) by s1.GANet.NET (8.6.11/8.6.11) id IAA09784; Mon, 22 Apr 1996 08:33:30 -0400 Date: Mon, 22 Apr 1996 08:33:29 -0400 (EDT) From: Eric Chet To: "matthew c. mead" cc: smpatel@freebsd.org, current@freebsd.org Subject: Re: possible 4th option? [Re: kern/1102] In-Reply-To: <317B1566.41C67EA6@Glock.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, matthew c. mead wrote: > 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? > Hello Well how about Slowaris ELF binaries? Eric J. Chet (ejc@nasvr1.cb.att.com || ec0@ganet.net) Lucent Technologies, Bell Labs Innovations > > -matt > > -- > Matthew C. Mead > > mmead@Glock.COM > http://www.Glock.COM/~mmead/ >