3.5.1 Matrix Server Installation Guide (June 2008)

Appendix A: Install the RHEL4 Operating System 44
binutils, cpp and patch are installed by default if you select the default
server installation during the initial installation procedure.
You can install the remaining packages via a Package Management tool of
your choice or directly from the RHEL4 distribution media.
2. Build the Kernel
Build the kernel from source if desired:
•For PolyServe source kernels, see “Build a RHEL4 Kernel from
PolyServe Sources” on page 59.
• For non-PolyServe source kernels, see “Build a RHEL4 Kernel from
Non-PolyServe Sources” on page 63.
NOTE: If you will be using a PolyServe binary kernel, you can install it
later as specified in the installation procedure in Chapter 2.
3. HBA Drivers and Matrix Server
When configuring the operating system, you will need to consider
whether the HBA driver should be loaded either during the initial
booting of the kernel or when Matrix Server is started. The following
scenarios describe the appropriate action for common Matrix Server
configurations. You may need to take certain steps to ensure that the HBA
driver is booted at the correct point.
Matrix Server-Provided HBA
If you will be using an HBA driver provided with Matrix Server, the HBA
driver should not be loaded during the initial boot of the kernel. Instead,
when Matrix Server is started, it will load its own HBA driver.
To prevent the HBA driver from being loaded with the kernel, you will
need to take these steps later in this procedure:
1. Remove the HBA drivers from the “initrd” kernel image. This is done
by editing the /etc/modprobe.conf file as described under step “4.
Modify System Files” on page 46.
•gcc •patch
• glibc-devel