Red Hat NETWORK 3.3 - PROVISIONING, Справочное руководство

Страница: 77 / 130

Chapter 4. Red Hat Network Website 67
To develop a new key/certificate, click create new cryptokey in the upper-right corner of the page.
Enter a description, select the type, upload the file, and click the
Update Key
button. Note that a
unique description is required.
4.4.10.8. Distributions
The Distributions page enables you to identify custom installation trees that may be used for kick-
starting. (Satellite users should note that this does not display Red Hat distributions provided to them.
They can be found within the Distribution dropdown menu of the Kickstart Details page.) Before
creating a distribution, you will need to make an installation tree available, as described in the Kick-
start Installations chapter of the Red Hat Enterprise Linux 3 System Administration Guide . This tree
will need to be located in a public directory on a Web server.
To create a new distribution, enter an intuitive label (without spaces) in the
Distribution Label
field.
In the
External Location
field, paste the URL to the base of the installation tree. (You can test this by
appending "README" to the URL in a Web browser, hitting return, and ensuring the distribution’s
readme file appears.)
In the
Autokickstart Boot Image field, enter the auto-ks kernel image for the distribution. You can
find all of the available packages by searching RPMs for "auto-kickstart". Identify the appropriate
package based upon the distribution to be kickstarted. It should look something like, "auto-kickstart-
ks-rhel-i386-as-3". Then, strip everything preceding the "ks" to derive the boot image. For instance, in
the above example, you would put "ks-rhel-i386-as-3" in the
Autokickstart Boot Image
field. Then
select the matching distribution from the Base Channel and Installer Generation dropdown menus
and click the
Create
button.
4.4.10.9. Building Bootable Kickstart ISOs
Copy the contents of
/isolinux
from the first CD-ROM of the target distribution. Then edit the
isolinux.cfg
file to default to ’ks’. Change the ’ks’ section to look like this:
label ks
kernel vmlinuz
append text ks={url} initrd=initrd.img lang= devfs=nomount ramdisk_size=16438 \
{ksdevice}
The URL can be obtained from the Kickstart Details page. It will look something like this:
http://my.sat.server/kickstart/ks/org/1271287x2c4682f33b87ed1d4dbea8/label/my-rhel3-as-ks
IP addressed-based kickstart URLs will look something like this:
http://my.sat.server/kickstart/ks/mode/ip_range
The kickstart distribution selected by the IP range should match the distribution you are building from,
or errors will occur. {ksdevice} is optional, but looks like:
ksdevice=eth0
It is possible to change the distribution for a kickstart profile within a family, such as RHEL AS3 to
RHEL ES3, by specifying the new distribution label. Note that you cannot move between versions
(2.1 to 3) and between updates (U1 to U2).
Next, you may customize
isolinux.cfg
further for your needs, such as by adding multiple kickstart
options, different boot messages, shorter timeout periods, etc.
Then make the ISO, as described in the
Making an Installation Boot CD-ROM section of the Red Hat
Enterprise Linux 3 Installation Guide . Or by issuing the command: