Paul Beard put forth on 10/28/2009 11:48 AM: > On Oct 28, 2009, at 9:13 AM, Stan Hoeppner <s...@hardwarefreak.com> wrote: > >> Debian GNU/Linux isn't OSX (it's better). Dunno if this is a >> possibility for you, but it is an option if you want to keep that PPC >> hardware humming away with fully up to date modern code. >> > > If mgmt doesn't want someone compiling a native version, how does > arguing for a different OS help? (and FreeBSD is better still. Let the > flames rage. )
I think you may have misunderstood me. I was merely pointing out that there is a mature and supported Power(PC) OS available for his hardware now that Apple stopped supporting PowerPC, in the event the hardware itself will continue to be sufficient for his needs for a while longer. I say "mature" as the FreeBSD site seems to indicate the PowerPC FreeBSD port is not fully baked at the moment (otherwise I'd have mentioned that option as well). The Debian PowerPC is fully baked, along with S/390, Alpha, IA-64, SPARC, and many other architectures. Just one of the many nice things about Debian--full supported releases simultaneously across the most diverse set of architectures of any *inux distribution. >> Or you could always grab the Postfix source and compile/install it >> yourself, assuming you have current OSX dev tools installed on the host >> and prerequisite libraries etc. > > This is the easiest approach. There are certainly docs available for > building postfix on OS X. And the MacPorts toolchain is worth installing > for things like this though bootstrapping that may take more time than > you have. I agree. But like you said, it may be more worth his time to just wait until the aforementioned new x86-64 servers arrive, if indeed this new hardware is a done deal. In that case there's no good reason to duplicate effort, as the OP previously mentioned. -- Stan
