Log onto the VM as the user maintaining Linux installations. You can use x3270
or c3270 (from the x3270-text package in Red Hat Linux) to log in to VM from other Linux
systems. Alternatively, use the OS/2 3270 terminal emulator on the S/390
management console. If you are working from a Windows based machine, Jolly
Giant (http://www.jollygiant.com)
offers an SSL enabled 3270 emulator.
If you aren't already in CMS mode, enter it now.
FTP to the machine containing the Red Hat Linux boot images
(kernel.img and initrd.img), log in,
and execute the following commands:
You may now customize the parameter file (redhat.parm). See
Appendix B for several examples of parm
files. Below is an explanation of the parm file contents.
These values are given directly to the linux kernel and should be left as
provided.
Table 1-1.
| Virtual Machine Network Device | Acceptable Values for
HOST=<...> |
|---|
| Ethernet (eth0) | HOST=fqdn:device:ipaddr[:mtu]
where, fqdn is the fully qualified domain
name of the vitual machine; device is eth0;
ipaddr is the fixed IP address for this
virtual machine; mtu is number of maximum
transfer units (optional, should be 1492 or 1500). For example:
HOST=s390.redhat.com:eth0:1.2.3.4:1500 |
| CTC (ctc0) | HOST=fqdn:device:ipaddr:gateway[:mtu]
where, fqdn is the fully qualified domain
name of the vitual machine; device is ctc0;
ipaddr is the fixed IP address for this
virtual machine; gateway is the IP address of
the gateway; mtu is number of maximum
transfer units (optional, should be 1492 or 1500). For example:
HOST=s390.redhat.com:ctc0:1.2.3.4:1.2.3.3:1500 |
| IUCV (iucv0) | HOST=fqdn:device:ipaddr:host:gateway[:mtu]
where, fqdn is the fully qualified domain
name of the vitual machine; device is iucv0;
ipaddr is the fixed IP address for this
virtual machine; host is the VM host name of
the IUCV partner; gateway is the IP address
of the IUCV partner; mtu is number of maximum
transfer units (optional, should be 1492 or 1500). For example:
HOST=s390.redhat.com:iucv0:1.2.3.4:1.2.3.3:1.2.3.2:1500 |
Range of addresses of your DASD devices. 200-20f should be sufficient in most
cases. Example: DASD=200-20f,B01-B03,F01
Default time zone as returned by the linux tzselect-utility, Examples:
DTZ=Europe/Berlin or DTZ=America/Chicago
LCS=lcs|qeth<dev_num>,<read>,<write>,<data (qeth only, ignored otherwise)>,<memory_usage>,
<port_no/protocol_no>, <checksum_received_ip_pkts>,<use_hw_stats> |
 | Note |
|---|
| | The above LCS line values have been broken
into segments for easier reading. Ideally, everything listed after
LCS= should be included as one line |
Type defines an OSA-2 with LCS (lcs) or an OSA-Express with QDIO/QETH (qeth)
device, where
<dev_num> is the device number
that is appended to lcs or qeth (values of -1 indicates driver chooses the value
and leaving this field blank will change <read> and <write> to a
probe range for non-qeth devices), <read> is the read address,
<write> is the write address, <data> is the data address valid only
if qeth is specified, <memory_useage> is the amount of memory in kilobytes
to allow the driver to use, <port_no/protocol_no> allows a port number or
protocol to be specified for use by the driver,
<checksum_received_ip_pkts> performs error checking on the packets, and
<use_hw_stats> will make the driver keep statistics on the hardware being
used. If one or more of the fields are not specified, the default values are
used. Example 1:
LCS=lcs0,0x9a4,0x9a5,0,0 for OSA-2 with
LCS, where read=
0x9a4 and
write=
0x9a5. Example 2:
LCS=qeth1,0x0fc00,0xfc01,0x7c02 for an OSA-Express with
QDIO/QETH, where read=
0x7c00,
write=
0x7c01, and
data=
0x7c02.
NETWORK=IP:netmask:broadcast[:gw] |
where,
IP is your S/390 virtual machine IP;
netmask the netmask;
broadcast the broadcast address;
gw the gateway-IP for your eth device (for eth-device
only).
The list of DNS servers, separated by colons. Examples: DNS=10.0.0.1:10.0.0.2
will use the DNS servers 10.0.0.1 and 10.0.0.2
SEARCHDNS=list:of:search:domains |
The list of the search domains, separated by colons. Example:
SEARCHDNS=redhat.com:redhat.de
RPMSERVER=ftp://your.ftp.server/your.s390.rpm.dir |
To access the S/390 binary RPM packages via FTP.
RPMSERVER=http://your.http.server/your.s390.rpm.path |
To access the S/390 binary RPM packages via HTTP.
RPMSERVER=IP:/your.s390.rpm.dir |
Give the IP address of the NFS server containing the S/390 binary RPM
packages (e.g. via an NFS mount of the Red Hat Linux for S/390 CD-ROM).
RPMSERVER=ftp://user:password@your.ftp.server//your.s390.rpm.dir |
To access the S/390 binary RPM packages via FTP with authentication.
MOUNTS=dev:mountpoint,dev2:mountpoint2 |
This defines a comma-delimited list of the DASD device-partitions and where they
should be mounted by default. For example:
MOUNTS=/dev/dasda1:/,/dev/dasdb1:/usr/share,/dev/dasdc1:/tmp |
SWAP=list:of:swap:devices |
The list of initial swap devices, delimeted by colons. For example:
SWAP=/dev/dasds1:/dev/dasdw1:/dev/dasdp1 |
If you encounter problems during an install, set
DEBUG to
any value to get a shell at certain steps during an installation.
chandev=ctc0,<read_channel_address>,<write_channel_address>
CHANDEV=ctc0,<read_channel_address>,<write_channel_address> |
This setup parameter will allow the ctc driver to properly connect to the ctc
read and write channels if connections are reversed. If the
chandev parameter is not set, the driver will default to
detected settings, which, depending on the system setup, may have ctc read and write
channels reversed. Example:
CHANDEV=ctc0,0x600,0x601
— As an alternative to setting this parameter, the read and write channel
connections can be physically swapped.
| Note |
|---|
| | When setting the parameters, you must either set
both or neither of the parameters (chandev and
CHANDEV). These values are necessary for proper
boot loader configuration, therefore exactly the same values have to be
given as CHANDEV. |
If any of the network parameters required to make the network operate correctly
are omitted from the parm file, a prompt will be appear
during the installation boot process.
Next, if the guest ID under which you wish to install is under a different
guest, then log out of the 3270 VM session.
If you logged off, reconnect and log in using the VM guest ID you configured
earlier for the install. If you are not in CMS mode, enter it now.
Run the redhat script.
The initial installation start-up script will ask you questions
about your networking and DASDs unless you have specified all necessary
information in the redhat.prm file.
Once all questions have been answered, you will be ready to begin the core
installation program, loader. To continue with
the installation, refer to Chapter 2 for further
instructions. Alternatively, refer to Chapter 3 if you
will perform a text mode installation.
| Note |
|---|
| | If you install over a network with FTP or HTTP you must
perform a text mode installation. |