Red Hat NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT, Reference Manual

Page: 125 / 318

Kickstart —
113
kickstart tree. Satellite customers will most likely locate this file here:
/var/www/satellite/rhn/
kickstart/ <kickstart label> /RedHat/base/comps.xml
.
7.4.9.3.13. Software � Package Profiles —
If you have previously created a Package Profile from one of your registered systems, you
can use that profile as a template for the files to be installed on a kickstarted system. Refer to
Section 7.4.2.9.2.2, “System Details � Software � Packages”
for more information about package
profiles.
7.4.9.3.14. Activation Keys —
Figure 7.12. Activation Keys
The
Activation Keys
tab, which has no sub-tabs, allows you select Activation Keys to include as part
of the kickstart profile. These keys, which must have been created previous to creating the kickstart
profile, will be used when re-registering kickstarted systems.
7.4.9.3.15. Scripts —
Figure 7.13. Scripts
The
Scripts
tab, which has no sub-tabs, is where %pre and %post scripts are created. This page lists
any scripts that have already been created for this kickstart profile. To create a new kickstart script:
1. Click the add new kickstart script link in the upper right
2. Enter the path to the scripting language used to create the script, such as /usr/bin/perl
3. Enter the full script in the large text box
4. Indicate whether this script is to be executed in the %pre or %post section of the kickstart process
5. Indicate whether this script is to run outside of the chroot environment. Refer to the
Post-
installation Script
section of the
Red Hat Enterprise Linux System Administration Guide
for further
explanation of the
nochroot
option
Note
RHN supports the inclusion of separate files within the Partition Details section of the
kickstart profile. For instance, you may dynamically generate a partition file based on the