From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 19:36:19 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 8EB3E16A4CE for ; Tue, 18 Jan 2005 19:36:19 +0000 (GMT) Received: from pegasus.cc.ucf.edu (ucf.edu [132.170.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F30C43D41 for ; Tue, 18 Jan 2005 19:36:19 +0000 (GMT) (envelope-from ewayte@pegasus.cc.ucf.edu) Received: from pegasus (pegasus [132.170.240.30]) by pegasus.cc.ucf.edu (Postfix) with ESMTP id 505A22903 for ; Tue, 18 Jan 2005 14:36:18 -0500 (EST) Date: Tue, 18 Jan 2005 14:36:18 -0500 (EST) From: Eric Wayte X-X-Sender: ewayte@pegasus To: freebsd-amd64@freebsd.org In-Reply-To: <20050118044101.GA38434@dragon.nuxi.com> Message-ID: References: <20050117203818.GA29131@dragon.nuxi.com> <20050118044101.GA38434@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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:36:19 -0000 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. Eric Wayte Sr. DBA Univ. of Central Florida ewayte@pegasus.cc.ucf.edu