Pre-Installation Script - Red Hat ENTERPRISE LINUX 4 System Administration Manual

Chapter 1. Kickstart Installations
In most cases, it is only necessary to list the desired groups and not individual packages. Note that the
Core and Base groups are always selected by default, so it is not necessary to specify them in the
%packages section.
Here is an example %packages selection:
%packages @ X Window System @ GNOME Desktop Environment @ Graphical Internet @ Sound and
Video dhcp
As you can see, groups are specified, one to a line, starting with an @ symbol, a space, and then the
full group name as given in the comps.xml file. Groups can also be specified using the id for the
group, such as gnome-desktop. Specify individual packages with no additional characters (the dhcp
line in the example above is an individual package).
You can also specify which packages not to install from the default package list:
-autofs
The following options are available for the %packages option:
--resolvedeps
Install the listed packages and automatically resolve package dependencies. If this option is not
specified and there are package dependencies, the automated installation pauses and prompts
the user. For example:
%packages --resolvedeps
--ignoredeps
Ignore the unresolved dependencies and install the listed packages without the dependencies. For
example:
%packages --ignoredeps
--ignoremissing
Ignore the missing packages and groups instead of halting the installation to ask if the installation
should be aborted or continued. For example:
%packages --ignoremissing

1.6. Pre-installation Script

You can add commands to run on the system immediately after the ks.cfg has been parsed. This
section must be at the end of the kickstart file (after the commands) and must start with the %pre
command. You can access the network in the %pre section; however, name service has not been
configured at this point, so only IP addresses work.
22