From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 13:39:02 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2B13106564A for ; Fri, 4 Mar 2011 13:39:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 68CE48FC17 for ; Fri, 4 Mar 2011 13:39:02 +0000 (UTC) Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta02.westchester.pa.mail.comcast.net with comcast id F1KW1g0051ZXKqc521f2C9; Fri, 04 Mar 2011 13:39:02 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta21.westchester.pa.mail.comcast.net with comcast id F1ez1g00d0PUQVN3h1f0Hy; Fri, 04 Mar 2011 13:39:01 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E95999B422; Fri, 4 Mar 2011 05:38:57 -0800 (PST) Date: Fri, 4 Mar 2011 05:38:57 -0800 From: Jeremy Chadwick To: Tom Evans Message-ID: <20110304133857.GA27130@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110304131849.GA26774@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, Dr Josef Karthauser Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 13:39:02 -0000 On Fri, Mar 04, 2011 at 05:18:49AM -0800, Jeremy Chadwick wrote: > Speculative: Joe may be in the same boat I am with one of my customers: > they use PHP eAccelerator (binary-only, only works on i386 *and* uses > compat6x) as well as ZendOptimizer (works on amd64 but I'm not sure if > this works with newer PHP), plus cannot upgrade to PHP 5.3 for a > multitude of reasons. I also have no idea how the above two PHP > extensions would play with a PHP built natively for amd64 (e.g. PHP > amd64, eAcclerator i386 + compat6x libraries/libc/etc., ZendOptimizer > amd64). I have fought time and time again with this customer about the > use of this software ("is there REALLY any way you can get rid of it?"), > but they absolutely will not budge. Off-topic: I just re-reviewed this. I'm trying to recall the "doesn't work on amd64" bits I kept encountering when dealing with either www/eaccelerator or devel/ZendOptimizer, or maybe something one of those two depended on. I'm looking at the Makefiles for both ports and neither seem to indicate this is the case, so I'm at a bit of a loss and feel ashamed stating something that may not be true. But rest assured there was, for quite some time, something related to those two which did not work/build on amd64. (Even file annotations aren't really helping me track down what I was encountering) I guess I'll need to re-visit this situation with a test/devel box for the customer. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |