|Red Hat Enterprise Linux 3: Installation Guide for the IBM® S/390® and IBM® eServer™ zSeries® Architectures|
|Prev||Chapter 1. Steps to Get You Started||Next|
Log onto the VM as the Linux guest account. You can use x3270 or c3270 (from the x3270-text package in Red Hat Enterprise Linux) to log in to the 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 are not in CMS mode, enter it now.
If necessary, add the device containing the VM's TCP/IP tools to your CMS disk list. For example:
vmlink tcpmaint 592
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):
locsite fix 80
get kernel.img (repl
get initrd.img (repl
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.
Follow these guidelines when creating a parameter file.
The following parameters are required and must be included in the parameter file:
Where <dasd-list> represents the list of DASD devices to be used by Red Hat Enterprise Linux.
Although autoprobing for DASDs is done if this parameter is omitted, it is highly recommended to include the DASD= parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in an unusable system.
where <file-system> represents the device on which the root file system can be found. For installation purposes, it should be set to /dev/ram0, which is the ramdisk containing the Red Hat Enterprise Linux installation program.
The following parameters are required to set up networking:
· <device> is the type of device (for example, ctc0, escon0, or lcs0)
· <input> is the input port for this device
· <output> is the output port for this device
To force a specific CTC protocol, additionals parameters can be added. For example:
Where <n> is one of the following:
· 0 for compatibility mode (used with non-Linux peers other than S/390 and zSeries operating systems)
· 1 for extended mode
· 2 for CTC-based tty (only supported on Linux-to-Linux connections)
· 3 for compatibility mode with S/390 and zSeries operating systems
Where <userid> represents the ID of the guest machines you want to connect to. Note that the ID must be written in capital letters. For example, an IUCV connection to the VM TCP/IP service machine should be written as:
The following parameters are optional:
Where <string> is the hostname of the newly-installed Linux guest.
Where <type> must be one of the following: ctc, escon, tr, hsi, iucv, or eth.
Where <IP> is the IP address of the new Linux guest.
Where <network> is the address of your network.
Where <netmask> is the netmask.
Where <broadcast> is the broadcast address.
Where <gw> is either the gateway-IP for your eth device or the IP address of the ctc/escon/iucv point-to-point partner.
Where <mtu> is the Maximum Transmission Unit (MTU) for this connection.
Where <server1>:<server2>:…:<serverN> is a list of DNS servers, separated by colons. For example:
Where <domain1>:<domain2>:…:<domainN> is a list of the search domains, separated by colons. For example:
This setup parameter allows 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.
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 for both parameters.
The following parameter for installations using a qeth device is optional:
Use this option to specify additional parameters for your QETH device (for CHANDEV) such as:
The following parameter for kickstart installations is optional:
Where <value> is defined as 1 if you want to run the installation program in noninteractive mode in the 3270 terminal, or 0 otherwise.
Make sure that your kickstart file contains all required parameters before you use this option.
If any of the network parameters required to make the network operate correctly are omitted from the parm file, a prompt appears during the installation boot process.
If you logged off, reconnect and log in using the VM guest ID you configured for installation. If you are not in CMS mode, enter it now.
Create an executable script containing the commands necessary to IPL the kernel image and start the installation. The following sample script is a typical initial start-up script:
/* */ 'CL RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'CH RDR ALL KEEP NOHOLD' 'IPL 00C CLEAR'
The initial installation start-up script prompts you for information about your networking and DASDs unless you have specified all necessary information in the parm file.
Once all questions have been answered, you are ready to begin the core installation program, loader. To continue with the installation, refer to Chapter 2 Installing Red Hat Enterprise Linux for further instructions.
If you install over a network with FTP or HTTP you must perform a text mode installation.