Product SiteDocumentation Site

Chapter 32. Kickstart Installations

32.1. What are Kickstart Installations?
32.2. How Do You Perform a Kickstart Installation?
32.3. Creating the Kickstart File
32.4. Kickstart Options
32.4.1. Advanced Partitioning Example
32.5. Package Selection
32.6. Pre-installation Script
32.6.1. Example
32.7. Post-installation Script
32.7.1. Examples
32.8. Making the Kickstart File Available
32.8.1. Creating Kickstart Boot Media
32.8.2. Making the Kickstart File Available on the Network
32.9. Making the Installation Tree Available
32.10. Starting a Kickstart Installation

32.1. What are Kickstart Installations?

Many system administrators would prefer to use an automated installation method to install Red Hat Enterprise Linux on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
Kickstart files can be kept on a single server system and read by individual computers during the installation. This installation method can support the use of a single kickstart file to install Red Hat Enterprise Linux on multiple machines, making it ideal for network and system administrators.
Kickstart provides a way for users to automate a Red Hat Enterprise Linux installation.
All kickstart scriptlets and the log files of their execution are stored in the /tmp directory to assist with debugging installation failures.

Note — /tmp/netinfo no longer used

Anaconda now configures network interfaces with NetworkManager. Consequently, kickstart users that referenced the network settings located in /tmp/netinfo in previous versions of Red hat Enterprise Linux must now source the ifcfg files in /etc/sysconfig/network-scripts.