From owner-freebsd-hackers  Wed Jun  7 20:01:38 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA28537
          for hackers-outgoing; Wed, 7 Jun 1995 20:01:38 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA28523
          for <hackers@freebsd.org>; Wed, 7 Jun 1995 20:01:30 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id UAA05534; Wed, 7 Jun 1995 20:04:44 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA00420; Wed, 7 Jun 1995 20:01:37 -0700
Message-Id: <199506080301.UAA00420@corbin.Root.COM>
To: "House of Debuggin'" <wpaul@skynet.ctr.columbia.edu>
cc: hackers@freebsd.org
Subject: Re: BSDi 2.0 binary compatibility question 
In-reply-to: Your message of "Wed, 07 Jun 95 18:28:20 EDT."
             <199506072228.SAA00374@skynet.ctr.columbia.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 07 Jun 1995 20:01:36 -0700
Sender: hackers-owner@freebsd.org
Precedence: bulk

>In short, I couldn't find a magic incantation to make BSDI 2.0 produce
>executables that would run on FreeBSD, even though FreeBSD seems to
>recognize the executable format. I think it's kind of unfair that
>BSDI people can use our binaries, but not the other way around. Am
>I missing something here, or is this a bug?

   Based on what you said above, it sounds like the BSDI's crt0 is messing
with the environment strings and BSDI stores/deals with them differently that
FreeBSD. I suggest looking carefully at their crt0.c. It's quite possible that
this particular incompatiblity may not be easily fixed.

-DG