Red Hat NETWORK 3.1 - PROVISIONING Reference Manual page 74

Hide thumbs Also See for NETWORK 3.1 - PROVISIONING:
Table of Contents

Advertisement

64
select the matching distribution from the Base Channel and Installer Generation dropdown menus
and click the Create button.
4.4.10.6. Building Bootable Kickstart ISOs
Copy the contents of
/isolinux
file to default to 'ks'. Change the 'ks' section to look like this:
isolinux.cfg
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/1271287x2c4682f33b87ed1dd4dbc64ef860bea8/label/my-rhel3-
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
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:
mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-tab
Note that
is the relative path to the directory containing the isolinux files you got from
isolinux/
the distribution cd, while
You may then burn the ISO to CD-ROM. To use the disc (assuming you left the label for the kickstart
boot as 'ks'), you should boot and type "ks" at the prompt. When you hit enter, the kickstart should
begin.
4.4.10.7. Integrating Kickstart with PXE
In addition to CD-ROM-based installs, RHN supports kickstarts through a Pre-Boot Execution Envi-
ronment (PXE). This is less error prone than CDs, enables kickstarting from bare metal, and integrates
with existing PXE/DHCP environments.
To use this method, you should make sure your systems have network interface cards (NIC) that sup-
port PXE, install and configure a PXE server, ensure DHCP is running, and then place the appropriate
files on an HTTP server for deployment. Once the kickstart profile has been created, you may use the
URL from the Kickstart Details page, just as you do for CD-ROM-based installs.
To obtain specific instructions for conducting PXE kickstarts, refer to the PXE Network Installations
chapter of the Red Hat Enterprise Linux 3 System Administration Guide.
from the first CD-ROM of the target distribution. Then edit the
further for your needs, such as by adding multiple kickstart
isolinux.cfg
is the output iso file, put into the current directory.
file.iso
Chapter 4. Red Hat Network Website

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWORK 3.1 - PROVISIONING and is the answer not in the manual?

Subscribe to Our Youtube Channel

Table of Contents