
354 IBM BladeCenter JS23 and JS43 Implementation Guide
graphical display (via Blade Center’s KVM), as an alternative. See
Appendix A, “Consoles, SMS, and Open Firmware” on page 493 for more
information. Use the SOL console to display the SMS menu and the
Anaconda options during the installation.
The resource allocation of processors, I/O adapters, memory, and storage
devices in a native environment is
fixed.
Virtualization functions and features are not available.
8.5 Red Hat Enterprise Linux 5.3 automated installation
Red Hat provides an automated installation functionality known as Kickstart. The
system administrator performs a Kickstart automated installation by creating a
single file containing answers to all the questions normally asked during a Red
Hat installation. This file can reside on a single server system, and multiple
clients can read it during installation.
This section explains how to create Kickstart files and use them to perform an
unattended installation of Red Hat Enterprise Linux 5.3
8.5.1 Kickstart profile creation methods
There are three methods to create a Kickstart file:
1. Create the file using the Red Hat Kickstart Configurator tool.
2. Have Red Hat Anaconda Installer generate this file for you during a manual
installation. After the installation completes, the Kickstart file resides at
/root/anaconda-ks.conf and you can copy it to an installation server. The basic
file created during a manual NFS installation is given in Example 8-1.
3. Generate the file yourself using a text editor.
Example 8-1 Basic Kickstart configuration file created during manual installation
# Kickstart file automatically generated by anaconda.
install
nfs --server=9.3.80.16 --dir=/install/linuxRHEL5.3
key 2515-dd4e-2152-25dd
lang en_US.UTF-8
network --device eth1 --bootproto static --ip 9.3.233.177 --netmask
255.255.254.0 --gateway 9.3.232.1 --nameserver 9.3.192.21 --hostname
JS23-turkey-3-lp1.austin.ibm.com
rootpw --iscrypted $1$oVjuAHA9$6cqrT/Nfnh6pRYFBIBECy/
Commentaires sur ces manuels