Cat /proc/cpuinfo or don't trust your cores to rackspace part i

Re:Cat /proc/cpuinfo or don't trust your cores to rackspace ... by jacquesm on Wednesday October 28, 2009 @11:55AM (#908057)

It's not for the 'new shiny' at all, it's got to do with optimizing your kernel to match your hardware and getting rid of loadable module support in favor of a kernel that has on board exactly that which is needed to operate your system.

A 'stock' kernel has a whole pile of things in it that might be the next remote exploit, by removing such stuff you marginally increase security.

Other things you might need:

   - kernel support for booting from raid filesystems without trickery
   - processor family optimizations
   - maximum number of cores (stock = 8, we run 16 on quite a few machines)

As for compiling, I do that anyway, it's a small job compared to the number of times that you need to do it. And you're just as much 'on your own' to solve problems, the chances of having them are less though (because the system you are running is considerably leaner).

Second your redhat enterprise solution, that's not what I'm using though on most of our machines (either centos or debian), but that's a good solution too.

[ Parent | on HN ]

Re:Cat /proc/cpuinfo or don't trust your cores to rackspace ... by nailer on Thursday October 29, 2009 @07:08AM (#909815)

Not a big user of software RAID, but AFAIK booting from a metadisk / is still out of the box doable as it was a few years ago:

"- processor family optimizations"

RHEL / CentOS include a variety of kernels precompiled for different CPU architectures.

"- maximum number of cores (stock = 8)"

What distro? RHEL / Centos support far more than that, we've got quite a number of 32 core machines and have a few 64 core boxes in test.

[ Parent | on HN ]