Configuring a Boot Device on an EMC Storage Array

a.To speed up the build process, only build for the architecture you wish to install. To accomplish this you can go into the

/mod_devel_kit/<kernel-version>/configs directory and rename any of the configs you DO NOT wish to be compiled.

For example for kernel version - 2.4.21-32.EL:

[mod_devel_kit]#

cd 2.4.21-32.EL/configs

 

[configs]# mv kernel-2.4.21-athlon.config old_kernel-2.4.21-

athlon.config

[configs]# cd

../../

 

!CAUTION

Do NOT rename or delete kernel-*-i386-BOOT.config.

The installer uses this version of the kernel/driver during installation. For 64bit environments, the ia32e config is required for installation.

b.For RHEL3, it is recommended that you rename or delete the kernel-<kernel version>.i386.config file. Due to errors in dependencies with this kernel config file, the make process may result in failure.

4.Build the driver using the following command: [mod_devel_kit]# make clean [mod_devel_kit]# make

(This will build modules.cpio.gz-xxxxfiles for different architectures in the rhxx directory. Example: In rhel3 dir for RedHat EL 3.0 dist)

5.Build the disk image using the following command: For 32bit:

[mod_devel_kit]# make disk

This builds a dd.img-xx.gzfile for different architectures in the rhxx directory, for example, rhel3 dir for RedHat EL 3.0 dist.

For 64bit:

[mod_devel_kit]# make disk1

This builds a v1-dd.img.gzfile for different architectures in the rhxx directory, for example, rhel3 dir for Red Hat EL 3.0 dist.

Installing onto the boot device with the QLogic HBA v3.x-Series driver

181

Page 181
Image 181
EMC P/N 300-002-803 manual 181