From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 02:48:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEE4916A54D for ; Tue, 18 Jan 2005 02:48:07 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7677043D1D for ; Tue, 18 Jan 2005 02:48:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 18878 invoked from network); 18 Jan 2005 02:48:07 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) AES256-SHA encrypted SMTP for ; 18 Jan 2005 02:48:06 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0I2lqaL092340; Mon, 17 Jan 2005 21:48:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 17 Jan 2005 21:46:17 -0500 User-Agent: KMail/1.6.2 References: <20050117203818.GA29131@dragon.nuxi.com> In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501172146.17965.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: David O'Brien Subject: Re: [RFC] what to name linux 32-bit compat X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 02:48:08 -0000 On Monday 17 January 2005 03:38 pm, David O'Brien wrote: > [ Respect the Reply-to:! ] > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... > > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). > > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. > > What do others think? Personally, I think /compat/linux32 and /compat/linux (for linux64) would be the best way to go. The idea being that /compat/linux runs native binaries on any given arch, and if there's more than one arch supported, the non-native ones get the funky names. I don't think it will really matter all to the end user much as acroread goes in /usr/local/bin and is in the path and that's all the user has to worry about. The ports stuff to put linux32 in /compat/linux32 on amd64 is going to be stuff the user doesn't have to worry or care about, so I don't think there's any user-visible benefit to linux and linux64 versus linux32 and linux. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org