Red Hat Enterprise Linux 5 Administration Unleashed

Installing with Kickstart 47Use a specific scripting language such as /usr/bin/python to process the script.--erroronfail1If the script fails, pause the installation and display an error dialog showing the locationof the failure in the script.Post-installation SectionOptionally, a script can be run immediately after the installation is complete and beforethe system is rebooted. After installation, the network is available. However, DNS serversare not available unless a primary nameserver was specified when configuring a static IPaddress. If DHCP was used, DNS lookup is not available and IP addresses must be used.The section must begin with the %post line. The following parameters can be specifiedafter %post on the same line:--nochrootDon’t run the post-installation script in the change root environment. By default, thepost-installation script is run in a change root environment where the /mnt/sysimagedirectory is treated as the root filesystem. Thus, by default, certain operations such ascopied files from the installation media will not work unless the --nochroot option isused.--interpreter Use a specific scripting language such as /usr/bin/python to process the script.--erroronfailIf the script fails, pause the installation program and display an error dialog showing thelocation of the failure in the script.Making the Kickstart File AccessibleThe kickstart file must be copied to a location accessible by the installation program.These locations include the following:. Hard drive partition. Floppy disk. HTTP, FTP, or NFS share. Boot CDThe first three locations are self-explanatory. For example, after setting up an HTTP, FTP,or NFS server, place the kickstart file in a directory shared by the network protocol.However, placing the file on the boot CD created from the boot.iso file needs furtherdetails. This section also explains how to provide an NFS server location via DHCP.