Building your own client kit 3–3
• ia32e/RHEL3.0_U8
• ia64/RHEL3.0_U8
• x86_64/RHEL3.0_U8
• i686/RHEL4_U1
• ia32e/RHEL4_U1
• ia64/RHEL4_U1
• x86_64/RHEL4_U1
• i686/RHEL4_U2
• ia32e/RHEL4_U2
• ia64/RHEL4_U2
• x86_64/RHEL4_U2
• i686/RHEL4_U3
• ia32e/RHEL4_U3
• ia64/RHEL4_U3
• x86_64/RHEL4_U3
• i686/RHEL4_U4
• ia32e/RHEL4_U4
• ia64/RHEL4_U4
• x86_64/RHEL4_U4
• i686/SLES_9
• ia32e/SLES_9
• ia64/SLES_9
• x86_64/SLES_9
The arch/distro subdirectories may also contain additional kernel patches in a patches
subdirectory and Lustre patches in a lustre_patches subdirectory.
The common subdirectory contains sources for Lustre, build tools, interconnects, diagnostic tools,
kernels, Lustre client tools and configurations.
3.2 Building your own client kit
When you build an HP SFS client kit using the SFS Client Enabler, you will perform some or all of the
following tasks (depending on the client architecture/distribution you are building for). Detailed instructions
are given in Section 3.2.2:
• Identify the source code required.
• Identify the appropriate Lustre patches.
• Identify the appropriate Lustre kernel patches.
• Patch the kernel.
• Rebuild the kernel with the appropriate kernel configuration file.
• Patch the Lustre sources with the appropriate Lustre patches.
• Rebuild any interconnect drivers.
• Rebuild Lustre.
• Rebuild additional user-space tools.
The remainder of this section is organized as follows:
• Prerequisites for the SFS Client Enabler (Section 3.2.1)
• Building an HP SFS client kit using the sample script (Section 3.2.2)
• Output from the SFS Client Enabler (Section 3.2.3)
Commentaires sur ces manuels