JLdL 19Feb08.

This directory is now rather obsolete, because the kernel configuration
files are now being maintained and published as part of the Linux image
packages, with names such as

linux-image-<kversion>-pmc-<cpu>_<kversion>-<d+lversions>_<arch>.deb
linux-image-<kversion>-srv-<cpu>_<kversion>-<d+lversions>_<arch>.deb
linux-image-<kversion>-trm-<cpu>_<kversion>-<d+lversions>_<arch>.deb

Currently the latest kernels available are these:

linux-image-2.6.22-pmc-k7_2.6.22-6~bpo40+2+dc1_i386.deb
linux-image-2.6.22-pmc-k7-smp_2.6.22-6~bpo40+2+dc1_i386.deb
linux-image-2.6.22-pmc-k8_2.6.22-6~bpo40+2+dc1_amd64.deb
linux-image-2.6.22-pmc-k8-smp_2.6.22-6~bpo40+2+dc1_amd64.deb

linux-image-2.6.22-srv-k7-ide_2.6.22-6~bpo40+2+dc1_i386.deb
linux-image-2.6.22-srv-k7-smp_2.6.22-6~bpo40+2+dc2_i386.deb
linux-image-2.6.22-srv-k7-smp-ide_2.6.22-6~bpo40+2+dc2_i386.deb
linux-image-2.6.22-srv-k8-smp_2.6.22-6~bpo40+2+dc1_amd64.deb

linux-image-2.6.22-trm-c3_2.6.22-6~bpo40+2+dc2_i386.deb
linux-image-2.6.22-trm-k7_2.6.22-6~bpo40+2+dc2_i386.deb
linux-image-2.6.22-trm-k7-gw_2.6.22-6~bpo40+2+dc2_i386.deb
linux-image-2.6.22-trm-p6_2.6.22-6~bpo40+2+dc2_i386.deb

--------------------------------------------------------------------------

This directory contains kernel configuration files for the remotely-booted
compute nodes and X11 terminals.  The compute-node configurations are very
lean, because a compute node should be a very lean machine, where one does
not expect to find any extra hardware. The configuration for X11 terminals
is much larger, with lots of modules containing device drivers.

These are just example configurations that you may want use at first. Note
that kernels compiled with these configurations will be rather large, even
without any modules loaded, because drivers for all possible network cards
are included.  You should eventually recompile the kernel maintaining only
the drivers you need, for the cards you actually have on the nodes.

If you cannot find here a configuration for the kernel version you want to
use, simply use the closest one, it probably will work.  In order to use a
configuration, uncompress the file with gunzip and copy it into the kernel
source directory with the name ".config". Then configure the kernel with

make oldconfig

If this command asks you any questions you no not know how to answer, just
hit [Enter] and accept the defaults. If you are using a 2.4-series kernel,
you should them compile it using a sequence of three commands,

make dep
make bzImage
make modules

In the case of the 2.6-series kernels, a single command will do all that,

make

For installation of the kernel images and modules into the nodes, use the
usual procedures. You may install the kernel in the boot/ subdirectory of
the root of each node and the modules into the lib/modules/ subdirectory,
using the environment variable INSTALL_MOD_PATH with the value

/<cluster_root>/<virtual_node> (for example, /trm/00 or /pmc/0000)

to do this last one in the kernel compilation directory, with the command

make modules_install

If you install everything only in one node, say the virtual node, you can
afterwards use the commands

hard-link-common-files --clone-missing -s /boot

and

hard-link-common-files --clone-missing -s /lib/modules

to distribute the files to all the nodes.

