On 15/02/06, Brett Curtis <[EMAIL PROTECTED]> wrote:
> I have 6 production servers most with different archs. I feel there
When you say "arches", are you referring to the host architecture or
to x86 class systems that are just using different processors? No
doubt this has been discussed before but if you're using x86 class
systems then there are ways to build a suitably generic system. For
example, let's assume that all of your servers are using i686 class
processors (yet most of them are P3 based so you'd like to optimise
for that case). You could use the following in make.conf:
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -mtune=pentium3 -O2"
CXXFLAGS="${CFLAGS}"
Here's another example which allows a system to be deployed to 586
class systems but still tunes for i686 class processors in general:
CHOST="i586-pc-linux-gnu"
CFLAGS="-march=i586 -mtune=i686"
CXXFLAGS="${CFLAGS}"
Note that gcc-3.3 uses the -mcpu parameter in place of -mtune. gcc-3.4
will recognise the -mcpu parameter but warn about it (eventually it
will be dropped).
> is a lot of overhead also. not to mention we are a start up and all
> of my servers are being used to the fullest. We at this point in time
> cant afford to have a test server.
A chrooted setup that reflects the environment used on one's server(s)
can be deployed on any existing Linux system (even a lowly desktop).
Although this may not address every concern that may arise in terms of
testing it can make for a perfectly suitable playground in terms of
building binary packages to be deployed. For fuller testing,
qemu/vmware can also be helpful.
Cheers,
--Kerin
--
[email protected] mailing list
