Red Hat Enterprise Linux Installation Guide 5.2 - linux.meuhobby.com

Chapter 16. Steps to Get You Started
set qioassist off
FTP to the machine containing the boot images (kernel.img and initrd.img), log in, and
execute the following commands (use the (repl option if you are overwriting existing
kernel.img and initrd.img image files):
• cd /location/of/boot/images/
• locsite fix 80
• bin
• get kernel.img (repl
• get initrd.img (repl
• ascii
• get generic.prmredhat.parm (repl
• quit
You may now create the parameter file (for example, redhat.parm). Refer to Chapter 19,
Sample Parameter Files for sample parm files. Below is an explanation of the parm file contents.
There is a limit of 32 total parameters in the parameter file. In order to accommodate limitations
with parameter files, a new configuration file on a CMS DASD should be used to configure the
initial network setup and the DASD specification.
A .parm file is still required for the real kernel parameters, such as root=/dev/ram0 ro ip=off
ramdisk_size=40000, and single parameters which are not assigned to variables, such as vnc.
Two parameters which are used in z/VM installs to point the installation program at the new
CMS configuration file need to be added to the .parm file:
CMSDASD=191 CMSCONFFILE=redhat.conf
CMSDASD is the device ID of the CMS formatted DASD which contains the configuration file.
CMSDASD is often the 'A' DASD (usually disk 191) of the z/VM guest account. The name of the
configuration file must be set with CMSCONFFILE and needs to be all lowercase.
The syntax of the CMSCONFFILE is bash style with variable="value" pairs, one on each line.
Example redhat.parm file:
root=/dev/ram0 ro ip=off ramdisk_size=40000
CMSDASD=191 CMSCONFFILE=redhat.conf
vnc
170