32.9. Making the Kickstart File Available
- On removable media, such as a floppy disk, optical disk, or USB flash drive
- On a hard drive
- On a network
32.9.1. Creating Kickstart Boot Media
x86_64). Additionally, this procedure requires the genisoimage and isomd5sum packages; these packages are available on Red Hat Enterprise Linux, but if you use a different system, you may need to adjust the commands used.
ks.cfg. Separate boot media will be required.
Procedure 32.1. Including a Kickstart File on Boot Media
- Mount the ISO image you have downloaded:
mount /path/to/image.iso /mnt/iso
- Extract the ISO image into a working directory somewhere in your system:
cp -pRf /mnt/iso /tmp/workdir
- Unmount the mounted image:
- The contents of the image is now placed in the
iso/directory in your working directory. Add your Kickstart file (
ks.cfg) into the
cp /path/to/ks.cfg /tmp/workdir/iso
- Open the
isolinux/isolinux.cfgconfiguration file inside the
iso/directory. This file determines all the menu options which appear in the boot menu. A single menu entry is defined as the following:
label linux menu label ^Install or upgrade an existing system menu default kernel vmlinuz append initrd=initrd.imgAdd the
ks=boot option to the line beginning with
append. The exact syntax depends on how you plan to boot the ISO image; for example, if you plan on booting from a CD or DVD, use
ks=cdrom:/ks.cfg. A list of possible sources and the syntax used to configure them is available in Section 28.4, “Automating the Installation with Kickstart”.
iso/directory to create a new bootable ISO image with your changes included:
genisoimage -U -r -v -T -J -joliet-long -V "RHEL-6.9" -volset "RHEL-6.9" -A "RHEL-6.9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o ../NEWISO.iso .This comand will create a file named
NEWISO.isoin your working directory (one directory above the
ImportantIf you use a disk label to refer to any device in your
ks=hd:LABEL=RHEL-6.9/ks.cfg, make sure that the label matches the label of the new ISO you are creating. Also note that in boot loader configuration, spaces in labels must be replaced with
- Implant a md5 checksum into the new ISO image:
ks.cfgand must be located in the flash memory's top-level directory. The kickstart file should be on a separate flash memory drive to the boot media.
ks=boot option to specify which device contains the USB drive. See Section 28.4, “Automating the Installation with Kickstart” for details about the
rhel-variant-version-architecture-boot.isoimage file that you can download from the Software & Download Center of the Red Hat customer portal.