McDATA 8832 Manual Do Utilizador
IBM BladeCenter Deployment Guide
8 Red Hat Boot Diskette Modification Process
1.
Copy the Network Boot Diskette (bootnet.img) and Supplemental Driver Diskette (drvnet.img) files
from the installation media (CD or ISO) to a temporary staging area.
# cp /mnt/cdrom/images/{bootnet.img,drvnet.img} .
# ls
bootnet.img drvnet.img
from the installation media (CD or ISO) to a temporary staging area.
# cp /mnt/cdrom/images/{bootnet.img,drvnet.img} .
# ls
bootnet.img drvnet.img
2.
Create the temporary mount point and two module directories.
# mkdir -p mnt/{boot,drv,initrd}
# ls mnt
boot drv initrd
# mkdir modules-boot modules-drv
# ls
bootnet.img drvnet.img mnt modules-boot modules-drv
# mkdir -p mnt/{boot,drv,initrd}
# ls mnt
boot drv initrd
# mkdir modules-boot modules-drv
# ls
bootnet.img drvnet.img mnt modules-boot modules-drv
3.
Mount the bootnet.img file via the loopback device
# mount -o loop bootnet.img mnt/boot
# ls mnt/boot
boot.msg general.msg ldlinux.sys rescue.msg vmlinuz
expert.msg initrd.img param.msg syslinux.cfg
# mount -o loop bootnet.img mnt/boot
# ls mnt/boot
boot.msg general.msg ldlinux.sys rescue.msg vmlinuz
expert.msg initrd.img param.msg syslinux.cfg
4.
Uncompress the initrd.img file to the staging area.
# gunzip -c < mnt/boot/initrd.img > tmp.img
# ls
bootnet.img drvnet.img mnt modules-boot modules-drv tmp.img
# gunzip -c < mnt/boot/initrd.img > tmp.img
# ls
bootnet.img drvnet.img mnt modules-boot modules-drv tmp.img
5.
Mount the uncompressed initrd.img file (tmp.img) via the loopback device.
# mount -o loop tmp.img mnt/initrd
# ls mnt/initrd
bin dev etc linuxrc lost+found modules proc
sbin tmp var
# ls mnt/initrd/modules
module-info modules.cgz modules.dep pcitable
# mount -o loop tmp.img mnt/initrd
# ls mnt/initrd
bin dev etc linuxrc lost+found modules proc
sbin tmp var
# ls mnt/initrd/modules
module-info modules.cgz modules.dep pcitable
6.
Mount the drvnet.img file via the loopback device.
# mount -o loop drvnet.img mnt/drv/
# mount -o loop drvnet.img mnt/drv/
7.
Extract the driver modules from the archive stored in the initrd.img file to the first module directory
created in step #2 (modules-boot).
# cd modules-boot
# gunzip -c < ../mnt/initrd/modules/modules.cgz | cpio –id
1412 blocks
# ls
2.4.9-e.40BOOT
# ls 2.4.9-e.40BOOT/
3c59x.o hid.o lockd.o scsi_mod.o usb-ohci.o vfat.o
eepro100.o input.o nfs.o sunrpc.o usb-storage.o
fat.o keybdev.o pcnet32.o usbcore.o usb-uhci.o
# cd ..
created in step #2 (modules-boot).
# cd modules-boot
# gunzip -c < ../mnt/initrd/modules/modules.cgz | cpio –id
1412 blocks
# ls
2.4.9-e.40BOOT
# ls 2.4.9-e.40BOOT/
3c59x.o hid.o lockd.o scsi_mod.o usb-ohci.o vfat.o
eepro100.o input.o nfs.o sunrpc.o usb-storage.o
fat.o keybdev.o pcnet32.o usbcore.o usb-uhci.o
# cd ..
8.
Extract the driver modules from the archive stored in the drvnet.img file to the second module
directory created in step #2 (modules-drv).
# cd modules-drv
# gunzip -c < ../mnt/drv/modules.cgz | cpio –id
3714 blocks
directory created in step #2 (modules-drv).
# cd modules-drv
# gunzip -c < ../mnt/drv/modules.cgz | cpio –id
3714 blocks
Version 3.0, 3/10/2006
http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564
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.
45