From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 19:53:34 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 9C2D916A4CE for ; Tue, 18 Jan 2005 19:53:34 +0000 (GMT) Received: from mail13.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3730D43D1F for ; Tue, 18 Jan 2005 19:53:34 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6805 invoked from network); 18 Jan 2005 19:53:34 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 19:53:33 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0IJrRCW098493; Tue, 18 Jan 2005 14:53:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Tue, 18 Jan 2005 14:53:57 -0500 User-Agent: KMail/1.6.2 References: <20050117203818.GA29131@dragon.nuxi.com> <20050118044101.GA38434@dragon.nuxi.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181453.57467.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx 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 19:53:34 -0000 On Tuesday 18 January 2005 02:36 pm, Eric Wayte wrote: > On Mon, 17 Jan 2005, David O'Brien wrote: > > Date: Mon, 17 Jan 2005 20:41:01 -0800 > > From: David O'Brien > > Reply-To: freebsd-amd64@freebsd.org > > To: freebsd-amd64@freebsd.org > > Subject: Re: [RFC] what to name linux 32-bit compat > > > > On Mon, Jan 17, 2005 at 12:38:18PM -0800, David O'Brien wrote: > >> 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). > > > > kan (Alexander Kabaev) fealt we could probably just follow Red Hat > > Enterprise Linux - which would put both 32-bit and 64-bit bits under > > /compat/linux. Upon thinking more about this; I think this will work. > > The linux32(1) command will be a little harder to impliment than seperate > > /compat/linux* (and I'm sure other details will have to be solved); but > > this does simplify things from a ports application POV. > > > > jhb agreed this was probably the better approach so I think this is what > > we'll do. > > > > -- > > -- David (obrien@FreeBSD.org) > > A previous post mentioned having 64-bit Linux around for Oracle. Why > don't we follow their standard of /lib (/compat/linux) for 64-bit > libraries and /lib32 (/compat/linux32) for the 32-bit libraries? This is > how it's done on 64-bit Solaris anyway. What RedHat apparently does is /lib for 32-bit libraries and /lib64 for 64-bit libraries, and kan's suggestion would be for us to do the same with /compat/linux/lib and /compat/linux/lib64. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org