Date: Wed, 24 Mar 2010 01:54:54 +0100 From: "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net> To: freebsd-current@freebsd.org Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32 Message-ID: <4BA962DE.3000107@stillbilde.net> In-Reply-To: <e71790db1003231749n5edf2cd2ubd39b74445297c1e@mail.gmail.com> References: <20100312171758.GB31089@dragon.NUXI.org> <20100312.125032.270969355930630649.imp@bsdimp.com> <20100322185331.GA88847@dragon.NUXI.org> <20100322.130939.70320533309323962.imp@bsdimp.com> <Pine.GSO.4.64.1003221538260.10584@sea.ntplx.net> <alpine.BSF.2.00.1003231933460.47414@qvfongpu.qngnvk.ybpny> <e71790db1003231749n5edf2cd2ubd39b74445297c1e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24.03.2010 01:49, Carlos A. M. dos Santos wrote: > On Tue, Mar 23, 2010 at 8:39 PM, jhell <jhell@dataix.net> 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. It may. But having a confusing directive (the COMPAT_FREEBSD32 vs COMPAT_FREEBSD[4567]) is likely to stay with us for a long, long, long time. Just like the scarring after a bullet wound to the foot. //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg Østli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkupYt4ACgkQODUnwSLUlKTWHQCePMfrdHKqTryA5DQ4T8aRlKfM jwUAnRmjdXdAwXB2gEvgNV8609ctqDY9 =q+B1 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BA962DE.3000107>