Red Hat ENTERPRISE LINUX 3 - FOR IBM S-390 AND IBM ESERVER ZSERIES, Installation Manual

Page: 16 / 108

i cms
If necessary, add the device containing z/VM's TCP/IP tools to your CMS disk list. For example:
vmlink tcpmaint 592 592
If using any of the qdio/qeth based network connection types (such as OSA express or
hipersockets), set the VM guest qioassist parameter off:
set qioassist off
FTP to the machine containing the Red Hat Enterprise Linux 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 redhat.parm (repl
•
quit
You may now create the parameter file (for example,
redhat.parm
). Refer to Appendix B,
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 new parameters which point the installation program at the new configuration file need to
be added to the
.parm
file:
Chapter 1. Steps to Get You Started
6