From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 01:09:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C539106564A; Wed, 24 Mar 2010 01:09:09 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8D2848FC08; Wed, 24 Mar 2010 01:09:08 +0000 (UTC) Received: by gyh3 with SMTP id 3so933424gyh.13 for ; Tue, 23 Mar 2010 18:09:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:cc :subject:in-reply-to:message-id:references:user-agent :x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type:content-transfer-encoding; bh=LpRh7X7+9ex7zHDSFF5sKMTvxsUOkMnzm6D7Ti2umrA=; b=vRAbzPfkyZObfCJ4t3luqqEsGA2HcsKEkzfG6LkiW3buoFUgJX4+6y0ub6OTpH7d2q s+YXzMBZESFx4NsP6EszFpBNuAfoq7JrwxVg4A/ug6niVGFCRv1pjybbm6Y7BBgMJwVe fGKcgJFLXL4uQlHYGC4OtTu6DnwgKrQGDyjpA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:x-openpgp-key-id:x-openpgp-key-fingerprint:mime-version :content-type:content-transfer-encoding; b=JpBJNI1EbQans5WQHuiEp3YbYSDJvYG8030fBljRxWdjxMXG2mVOX4ifjdB0TKuti0 /M35vIN6lFevUfvslCfUpQU3j5g/tr5XhP6lAoJuC/122bjiHdaaHICll73d043PjySz muIfhOfwvHegeTP3qbax4GsEFcy1LQE4DhNWU= Received: by 10.150.56.7 with SMTP id e7mr3658986yba.203.1269392947516; Tue, 23 Mar 2010 18:09:07 -0700 (PDT) Received: from centel.dataix.local (adsl-99-109-124-168.dsl.klmzmi.sbcglobal.net [99.109.124.168]) by mx.google.com with ESMTPS id 21sm5521235iwn.3.2010.03.23.18.09.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 23 Mar 2010 18:09:06 -0700 (PDT) Sender: "J. Hellenthal" Date: Tue, 23 Mar 2010 21:08:59 -0400 From: jhell To: "Carlos A. M. dos Santos" In-Reply-To: Message-ID: References: <20100312171758.GB31089@dragon.NUXI.org> <20100312.125032.270969355930630649.imp@bsdimp.com> <20100322185331.GA88847@dragon.NUXI.org> <20100322.130939.70320533309323962.imp@bsdimp.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Cc: Daniel Eischen , freebsd-current@freebsd.org, "M. Warner Losh" Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2010 01:09:09 -0000 On Tue, 23 Mar 2010 20:49, Carlos A. M. dos Santos wrote: In Message-Id: > On Tue, Mar 23, 2010 at 8:39 PM, jhell wrote: >> >> On Mon, 22 Mar 2010 15:42, deischen@ wrote: >>> >>> [ Some CC's stripped ] >>> >>> On Mon, 22 Mar 2010, M. Warner Losh wrote: >>> >>>> P.S.  I think that there's much traction to the idea of moving from >>>> COMPAT_FREEBSDx to some other variable called, for example, >>>> COMPAT_FREEBSD_BACK_TO=x, which will give compatibility for binaries >>>> as old as FreeBSD x.0, and have all the other magic handled behind the >>>> scenes.  This would render the inconsistency with COMPAT_FREEBSDx part >>>> of the debate completely moot. >>> >>> Doesn't matter.  We're still use to COMPAT_FREEBSDx since >>> it's been here so long.  So regardless if you rename them >>> to COMPAT_FREEBSD_BACK_TO=x, it is still potentially confusing. >>> >>> COMPAT_ARCH32 and all other choices David mentions seem like >>> much better names - even if there wasn't any existing >>> COMPAT_FREEBSDx knobs. >>> >>> My $0.02. >>> >>> >> >> >> Ill say it again if I have to... COMPAT_ELF32 or possibly even ELF32_SUPPORT >> seems to me as a very likely possibility. >> >> Maybe even: >> SUPPORT_ELF32=          # Support for 32 Bit ELF Binaries >> >> This would add its own name structure that is expandabe later-in-future when >> 128 Bit systems come out ;) > > ELF may go away sometime, just like a.out went to the holly pastures. > > Alright, that's like anything else in the world of computer sciences. But that still does not dismiss its purpose and right now ELF is in full swing and when the time comes... 10, 20, 30 years down the road then you simply add something else but by that point 32 bit computing will probably be history so there wont need to be any of this fuss for ELF or 32 bit support at that time. -- jhell