McDATA 8832 warranty IBM BladeCenter Deployment Guide

Models: 8832

1 54
Download 54 pages 35.19 Kb
Page 49
Image 49

IBM BladeCenter Deployment Guide

fi

gunzip -c < /tmp/mnt-$$/modules.cgz cpio -id

for moduleDir in *; do

for moduleFile in `find $moduleDir -name "*.o"`; do if [ -d /lib/modules/$moduleDir ]; then

targetModuleFiles=`find /lib/modules/$moduleDir -name "$moduleFile"`

if [ ."$targetModuleFiles" = ."" ]; then

cp $moduleFile /lib/modules/$moduleDir/kernel else

for targetModuleFile in $targetModuleFiles; do cp $moduleFile $targetModuleFile

done fi

#update module dependencies $DEPMOD -a $moduleDir

fi done

done

cd $CWD

umount /tmp/mnt-$$

# clean up

rm -rf /tmp/modules-$$ rm -rf /tmp/mnt-$$

4.Run “chmod +x update_modules.sh” to mark it executable.

5.Add the following text (with appropriate changes to reflect the names of the files you created) to the %post section of the kickstart file in order to facilitate execution of the script created in step #1.

#copy driver diskette image from the root directory of

#the NFS share to the root directory on the target machine

cp /mnt/source/dd.img /mnt/sysimage

#copy module update script from the root directory of

#the NFS share to the root directory on the target machine cp /mnt/source/update_modules.sh /mnt/sysimage

#Execute the script in the chrooted environment

chroot /mnt/sysimage ./update_modules.sh

Version 3.0, 3/10/2006

http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564

49

The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for

guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.

Page 49
Image 49
McDATA 8832 warranty IBM BladeCenter Deployment Guide