Red Hat LINUX 7.2 - S-390 User manual

Red Hat Linux 7.2
The Official Red Hat Linux for S/390 Installation
Guide

ISBN: N/A
Red Hat, Inc.
2600 Meridian Parkway
Durham, NC 27713 USA
[phone] (Voice)
[phone] (FAX)
888 733 4281 (Voice)
P.O. Box 13588
Research Triangle Park, NC 27709 USA
© 2001 Red Hat, Inc.
rhl-ig-s390(EN)-7.2-Print-RHI (2001-08-27T12:27-0400)
Copyright © 2001 by Red Hat, Inc. This material may be distributed only subject to the terms and con-
ditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available
at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit per-
mission of the copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial
purposes is prohibited unless prior permission is obtained from the copyright holder.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo,
Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide
and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc.
in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
Motif and UNIX are registered trademarks of The Open Group.
Itanium is a registered trademark of Intel Corporation.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and
other countries.
Windows is a registered trademark of Microsoft Corporation.
SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
FireWire is a trademark of Apple Computer Corporation.
S/390 and zSeries are trademarks of International Business Machines Corporation.
All other trademarks and copyrights referred to are the property of their respective owners.
Printed in Canada, Ireland, and Japan
ii

Contents
Red Hat Linux 7.2
Introduction................................................................................... v
Document Conventions.................................................................... v
How to Use This Manual .................................................................. viii
Chapter 1 Steps to Get You Started....................................... 11
1.1 Do You Have the Right Red Hat Linux Components? ........................ 11
1.2 Additional S/390 Hardware Preparation for Installation Notes............... 13
1.3 Basic Overview of the Boot Method ............................................ 13
1.4 Common Steps Needed for Installing Red Hat Linux to a VM or LPAR..... 13
1.5 Installing under VM............................................................... 15
1.6 Installing in an LPAR using the Red Hat Linux LPAR CD .................... 20
1.7 Installing in an LPAR without the Red Hat Linux for S/390 CD-ROMs...... 20
1.8 Installing in an LPAR (Common Steps) ........................................ 22
1.9 Do You Have Enough Disk Space?............................................. 22
1.10 Which Installation Class is Best For You?...................................... 23
Chapter 2 Installing Red Hat Linux........................................ 27
2.1 The Installation Program User Interface ....................................... 27
2.2 Running the Installation Program............................................... 27
2.3 Language Selection.............................................................. 29
2.4 Welcome to Red Hat Linux ...................................................... 30
2.5 Install Options..................................................................... 30
2.6 Partitioning with fdasd............................................................ 31
2.7 Partitioning Your System......................................................... 35
2.8 Boot Loader Installation.......................................................... 38
2.9 Network Configuration ........................................................... 39
2.10 Firewall Configuration............................................................ 41
2.11 Language Support Selection.................................................... 44
2.12 Time Zone Configuration ........................................................ 45
iii

2.13 Account Configuration ........................................................... 46
2.14 Authentication Configuration .................................................... 48
2.15 Package Group Selection........................................................ 50
2.16 Preparing to Install ............................................................... 54
2.17 Installing Packages............................................................... 55
2.18 Installation Complete............................................................. 55
Chapter 3 Installing Red Hat Linux via Text Mode............... 57
3.1 Things You Should Know ........................................................ 57
3.2 The Installation Program User Interface ....................................... 58
3.3 Running the Installation Program............................................... 60
3.4 Installation Cross-reference Table .............................................. 61
3.5 Installing from Hard Drive (DASD).............................................. 63
3.6 Installing over a Network......................................................... 64
Appendix A Removing Red Hat Linux....................................... 67
Appendix B Sample Parameter Files for LPAR and VM
Configurations........................................................ 69
Appendix C Getting Technical Support.................................... 71
C.1 Remember to Sign Up ........................................................... 71
C.2 An Overview of Red Hat Support............................................... 71
C.3 How to Get Technical Support .................................................. 73
C.4 Questions for Technical Support................................................ 74
Appendix D Troubleshooting Your Installation of Red Hat
Linux ........................................................................ 77
D.1 You are Unable to Boot Red Hat Linux......................................... 77
D.2 Trouble During the Installation .................................................. 77
D.3 Problems After Installation....................................................... 78
iv

Section 0.1:Document Conventions v
Introduction
Welcome to the Official Red Hat Linux for S/390 Installation Guide.
The Official Red Hat Linux for S/390 Installation Guide contains useful information to assist you
during the installation of Red Hat Linux. From fundamental concepts such as installation preparation
(gathering information about your current system) to the step-by-step installation procedure, this book
will be a valuable resource as you install Red Hat Linux.
This manual will walk you through a typical S/3901installation. Once you have completed the instal-
lation as outlined in this manual, you will have a fully functioning Red Hat Linux system.
Document Conventions
When you read this manual, you will see that certain words are represented in different fonts, type-
faces, sizes and weights. This highlighting is systematic; different words are represented in the same
style to indicate their inclusion in a specific category. The types of words that are represented this way
include the following:
command
Linux commands (and other operating system commands, when used) are represented this way.
This style should indicate to you that you can type in the word or phrase on the command line
and press [Enter] to invoke a command. Sometimes a command contains words that would be
displayed in a different style on their own (e.g., filenames). In these cases, they are considered
to be part of the command, so the entire phrase will be displayed as a command. For example:
Use the cat testfile command to view the contents of a file, named testfile, in the
current working directory.
filename
Filenames, directory names, paths and RPM package names are represented this way. This style
should indicate that a particular file or directory exists by that name on your Red Hat Linux
system. Examples:
The .bashrc file in your home directory contains bash shell definitions and aliases for your
own use.
The /etc/fstab file contains information about different system devices and filesystems.
The /usr/share/doc directory contains documentation for various programs.
Install the webalizer RPM if you want to use a Web server log file analysis program.
1S/390 and zSeries hardware systems are commonly referred to as the mainframe.

vi Introduction
application
This style should indicate to you that the program named is an end-user application (as opposed
to system software). For example:
Use Netscape Navigator to browse the Web.
[key]
A key on the keyboard is shown in this style. For example:
To use [Tab] completion, type in a character and then press the [Tab] key. Your terminal will
display the list of files in the directory that start with that letter.
[key]-[combination]
A combination of keystrokes is represented in this way. For example:
The [Ctrl]-[Alt]-[Backspace] key combination will restart the X Window System.
text found on a GUI interface
A title, word or phrase found on a GUI interface screen or window will be shown in this style.
When you see text shown in this style, it is being used to identify a particular GUI screen or an
element on a GUI screen (e.g., text associated with a checkbox or field). Examples:
On the GNOME Control Center screen, you can customize your GNOME window manager.
SelecttheRequirePasswordcheckbox if you wouldlikeyour screensavertorequireapassword
before stopping.
top level of a menu on a GUI screen or window
When you see a word in this style, it indicates that the word is the top level of a pulldown menu.
If you click on the word on the GUI screen, the rest of the menu should appear. For example:
Under Settings on a GNOME terminal, you will see the following menu items: Preferences,
Reset Terminal,Reset and Clear, and Color selector.
If you need to type in a sequence of commands from a GUI menu, they will be shown like the
following example:
Click on Programs=>Applications=>Emacs to start the Emacs text editor.
button on a GUI screen or window
This style indicates that the text will be found on a clickable button on a GUI screen. For ex-
ample:
Click on the Back button to return to the Web page you last viewed.
computer output

Section 0.1:Document Conventions vii
When you see text in this style, it indicates text displayed by the computer on the command line.
You will see responses to commands you typed in, error messages and interactive prompts for
your input during scripts or programs shown this way. For example:
Use the ls to display the contents of a directory:
$ls
Desktop axhome logs paulwesterberg.gif
Mail backupfiles mail reports
The output returned in response to the command (in this case, the contents of the directory) is
shown in this style.
prompt
A prompt, which is a computer’s way of signifying that it is ready for you to input something,
will be shown in this style. Examples:
$
#
[stephen@maturin stephen]$
leopard login:
user input
Text that the user has to type, either on the command line, or into a text box on a GUI screen, is
displayed in this style. In the following example, text is displayed in this style:
To boot your system into the text based installation program, you will need to type in the text
command at the boot: prompt.
Another example, with the word root displayed as something the user needs to type in:
If you need to log in as root when you first log into your system, and you are using the graphical
login screen, at the Login prompt, type root. At the Password prompt, type in the root
password.
Additionally, we use several differentstrategies todraw yourattention to certain pieces of information.
In order of how critical the information is to your system, these items will be marked as a note, a
caution, or a warning. For example:

viii Introduction
Note
Remember that Linux is case sensitive. In other words, a rose is not a ROSE
is not a rOsE.
CAUTION
Do not do routine tasks as root — use a regular user account unless you need
to use the root account to administer your system.
WARNING
If you choose not to partition manually, a server installation will remove
all existing partitions on all installed hard drives. Do not choose this
installation class unless you are sure you have no data you need to save.
How to Use This Manual
This manual focuses on VM and LPAR-based installations. It will help you prepare your system, walk
you through the installation, and assist you in the configuration of Red Hat Linux.
If you are an experienced user and you do not need a review of the basics, you can skip ahead to
Chapter 2, Installing Red Hat Linux to begin the installation process.
Tip
Refer to the Red Hat Frequently Asked Questions for answers to questions
and problems that may occur before, during, or after the installation. You
will find the FAQ online at:
http://www.redhat.com/support/docs/faqs/rhl_general_faq/

Section 0.2:How to Use This Manual ix
We Need Feedback!
If you spot a typo in the Official Red Hat Linux for S/390 Installation Guide, or if you have thought of
a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla
( http://www.redhat.com/bugzilla/) against the component rhl-ig-s390.
Be sure to mention the manual’s identifier:
rhl-ig-s390(EN)-7.2-Print-RHI (2001-08-27T12:27-0400)
That way we will know exactly which version of the guide you have.
If you have a suggestion for improving the documentation, try to be as specific as possible when de-
scribing it. If you have found an error, please include the section number and some of the surrounding
text so we can find it easily.
If you have a support question (for example, if you need help configuring X, or if you are not sure how
to partition your hard drive[s]), please register your product at http://www.redhat.com/apps/activate/
and use the online support system for those type of requests.

x Introduction

Section 1.1:Do You Have the Right Red Hat Linux Components? 11
1 Steps to Get You Started
The installation process assumes basic familarity with the IBM S/390 platform and makes reference
to the IBM Linux for S/390 Redbook (SG24-4987-00 and SG24-6264-00) guide (see http://www.red-
books.ibm.com for more information). In general, this section assumes that you have reviewed the
Redbook and are familiar with setting up logical partitions (LPARs) and virtual machines (VMs) on
an S/390 system.
Note
For the most current IBM resources, please visit http://www.ibm.com/es-
erver/zseries.
Before you install Red Hat Linux, you will need to perform the following steps:
1. Allocate DASD1partitions (2 recommended of at least 2 GB each).
2. Acquirea minimum of 64 MB RAM (128 MB is stronglyrecommended) to designate for the Linux
virtual machine.
3. Determine if you need swap space and if so how much. While it is possible (and recommended) to
assign enough memory to the VM and let the VM do the necessary swapping, there may be cases
where the amount of required RAM is not predictable. In cases such as this, the amount of swap
dedicated should be equal to two times the amount of RAM.
4. Decide what environment under which the Red Hat Linux operating system will run (on an LPAR
or as a guest operating system on one or more virtual machines).
5. Finally, it is important to review sections 3.3 through 3.8 and Chapters 5 and 6 of the IBM Linux
for S/390 Redbook, as it explains the different configurations and install scenarios available on the
S/390 platform as well as how to setup an initial LPAR or Linux virtual machine (VM).
1.1 Do You Have the Right Red Hat Linux
Components?
If you have purchased the Official Red Hat Linux boxed set, you are ready to go. However, mistakes
occasionally happen, so now is a good time to double-check the contents of your boxed set.
1Direct Access Storage Devices (or DASDs) are hard disks that allow a maximum of three (3) partitions per
DASD. For example, dasda has dasda[123].

12 Chapter 1:Steps to Get You Started
A black, red, and white Registration Information card is included in your boxed set. A list of the
contents of your boxed set version is on the back of the card. Please read over the list and check to
make sure that you have all the CDs and manuals that are included with the version of Red Hat Linux
that you purchased.
If you have purchased the Official Red Hat Linux boxed set from Red Hat, Inc. (or one of its distrib-
utors), and you are missing one or more of the items listed, please let us know. Contact information
is also available on the box as well as on the Registration Information card.
How to identify our official boxed set: The bottom of our box has an ISBN number next to one of the
bar codes. That ISBN number should be in this form:
1-58569- x - y
(The xand ywill be unique numbers.)
Red Hat partners with companies (international and domestic) so that we can make Red Hat Linux
available to you in the most convenient form. Because of these partnerships, you might find that your
Red Hat Linux boxed set may not have been actually produced by Red Hat.
Red Hat provides support for only official Red Hat Linux products. If your box has a different ISBN
number (or none at all), you will need to contact the company that produced your boxed set. Normally,
third-party producers will include their logo and/or contact information on the outside of their box; an
official Red Hat Linux boxed set lists only our name and contact information.
1.1.1 Where to Find Other Red Hat Linux Manuals
If your particular boxed set did not include all of the printed Red Hat Linux manuals, you can find
them online or on the Red Hat Linux Documentation CD included with your official Red Hat Linux
boxed set.
To find the manuals in both HTML and PDF formats online, go to http://www.redhat.com/docs.
1.1.2 Registering Your Red Hat Linux Boxed Set
If you have purchased an Official Red Hat Linux 7.2 boxed set, you should register your product.
Registration offers many useful services, such as installation support, access to Red Hat Network, and
more.
To register your product, go to http://www.redhat.com/apps/activate/. You will find your Product ID
on the Registration Information card in your Official Red Hat Linux boxed set. Once registered, you
will have access to all the extras that Red Hat provides to its registered users.
For more information on registering and the scope of Red Hat’s technical support offerings, see Ap-
pendix C, Getting Technical Support.

Section 1.4:Common Steps Needed for Installing Red Hat Linux to a VM or LPAR 13
1.2 Additional S/390 Hardware Preparation for
Installation Notes
The network configuration must be determined beforehand. Red Hat Linux for S/390 supports
CTC/Escon and IUCV network device configurations. For the purposes of this installation, it is
recommended that two 2 GB DASD partitions be allocated for the installation process. All DASD
disk allocations should be completed prior to the install process. After the installation, more DASD
disk partitions may be added or deleted as necessary.
1.3 Basic Overview of the Boot Method
For installation you must start a kernel (with the Linux kernel), an initrd.img for VM installa-
tions or a tapeinrd.img for LPAR installation (with some basic network applications and kernel
drivers), and a parameter file with some information about your network configuration. Once this
is started on the S/390, the networking will be configured. You can then use telnet or ssh on another
computer to log into your S/390 Linux install image and start an installation script to install S/390
Linux onto your file system.
1.4 Common Steps Needed for Installing Red Hat
Linux to a VM or LPAR
The Red Hat Linux for S/390 media must be available for either a network installation (via NFS, FTP
or HTTP) or installation via local hard disk (DASD). The following steps, common to both VM and
LPAR installations, prepare for the chosen method of installation.
Network Installation
The NFS, FTP or HTTP server to be used for installation over the network must be a seperate
machine which can provide the complete RedHat tree — this machine is referred to as RPM-
SERVER. Both the RedHat/base/ and RedHat/RPMS/ directories must be available and
populated with all files from the two installation CD-ROMs.
Note
The directory specified in the following refers to /loca-
tion/of/disk/space
. This means it is the directory up
to, but NOT including, the RedHat distribution directory. For
example, if you have a Red Hat Linux 7.2 CD-ROM mounted
on /mnt/cdrom,
/location/of/disk/space would be
/mnt/cdrom.

14 Chapter 1:Steps to Get You Started
To copy the RedHat tree from each CD-ROM on a Linux machine, and make this tree available:
• Insert CD-ROM 1 and execute the following commands:
–mount /mnt/cdrom
–cp -var /mnt/cdrom/RedHat /location/of/disk/space
Where
/location/of/disk/space is a directory you create such as /ex-
port/7.2/.
–unmount /mnt/cdrom
• Insert CD-ROM 2 and execute the following commands:
–mount /mnt/cdrom
–cp -var /mnt/cdrom/RedHat /location/of/disk/space
Where
/location/of/disk/space is a directory you create such as /ex-
port/7.2/.
–unmount /mnt/cdrom
• Next, make
/location/of/disk/space accessible to the installation program via
NFS, FTP, or HTTP and verify access from a client.
• For NFS, export the directory by adding an entry to /etc/exports. To export to only
one S/390 VM or LPAR add an entry like:
/location/of/disk/space your.s390.ip.address(ro,no_root_squash)
To export to all machines (not appropriate for all NFS systems), add:
/location/of/disk/space *(ro,no_root_squash)
Restart the NFS daemon (on a Red Hat Linux machine, use /sbin/service nfs
restart) to force NFS to reload the /etc/exports file.
Attempt to mount the directory exported to a temporary directory and view its contents fol-
lowing this example (assuming a Red Hat Linux machine):
mkdir /mnt/mytemp
mount -o rw,rsize=8192 -t nfs /whatever/s390-root /mnt/mytemp
cd /mnt/mytemp
ls
umount /mnt/mytemp
rmdir /mnt/mytemp
If, with ls, you did not see the RedHat directory, then the wrong path may have been
mounted and/or exported.

Section 1.5:Installing under VM 15
• FTP and HTTP installations also support a second tree structure. To make it easier to access
the contents of the two CD-ROMs, you can mount your CD-ROMs or ISO images with the
following mount points:
/location/of/disk/space/disc1/
/location/of/disk/space/disc2/
For example:
mount -o loop CD1.iso /location/of/disk/space/disc1/
Hard Disk Installation
Hard Disk installations require a working Linux system on your S/390, and the use of ISO (or
CD-ROM) images rather than the entire installation tree. Depending upon how Red Hat Linux
for S/390 was acquired, you may have either a set of CD-ROMs, or ISO images.
Hard drive installations only work from ext2 or ext3 filesystems. If you have a filesystem other
than ext2 or ext3 you will not be able to perform a hard drive installation.
• Set of CD-ROMs — you need to create CD-ROM ISO image files from the two installation
CD-ROMs. These can be created on a Linux machine by inserting the first CD-ROM into
the CD-ROM drive and running:
dd if=/dev/cdrom of=/tmp/CD1.iso
Repeat for the second CD-ROM, with:
dd if=/dev/cdrom of=/tmp/CD2.iso
This command may raise an error message when the end of data on the CD-ROM is reached
- this can be ignored. The ISO images created can now be used for installation, once copied
to the correct DASD.
• ISO images — simply transfer these images to the correct DASD.
Verifying that ISO images are intact before you attempt an installation, will help to avoid
problems. To verify the ISO images are intact prior to performing an installation, use an
md5sum program (many md5sum programs are available for various operating systems).
An md5sum program should be available on the same Linux machine as the ISO images.
Make the correct DASDs accessible to the new VM or LPAR, and then proceed with instal-
lation.
1.5 Installing under VM
Log onto the VM as the user maintaining Linux installations. You can use x3270 or c3270 (from the
x3270-textpackage inRed Hat Linux)to log in toVM from other Linux systems. Alternatively, use the

16 Chapter 1:Steps to Get You Started
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.
i cms
FTP to the machine containing the Red Hat Linux boot images (kernel.img and initrd.img),
log in, and execute the following commands:
•cd/where/the/boot/images/are
• locsite fix 80
• bin
• get kernel.img (repl
• get initrd.img (repl
• ascii
• mget *.parm *.exec (repl
• quit
You may now customize the parameter file (redhat.parm). See Appendix B, Sample Parameter
Files for LPAR and VM Configurations for several examples of parm files. Below is an explanation
of the parm file contents.
root=/dev/ram0 ro ip=off
These values are given directly to the linux kernel and should be left as provided.
HOST=<...>
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

Section 1.5:Installing under VM 17
Virtual Machine
Network Device Acceptable Values for HOST=<...>
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
DASD= x-y[,a-c...]
Range of addresses of your DASD devices. 200-20f should be sufficient in most cases. Example:
DASD=200-20f,B01-B03,F01
DTZ= timezone
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 read-
ing. 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,

18 Chapter 1:Steps to Get You Started
<port_no/protocol_no> allows a port number or protocol to be specified for use by the driver, <check-
sum_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).
DNS= list:of:dns:servers
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:[email protected]//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

Section 1.5:Installing under VM 19
DEBUG= <value>
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. Ex-
ample: 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 pa-
rameters (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.
#cp log
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.
i cms
Run the redhat script.
redhat
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, Installing Red Hat Linux for further
instructions. Alternatively, refer to Chapter 3, Installing Red Hat Linux via Text Mode if you will
perform a text mode installation.

20 Chapter 1:Steps to Get You Started
Note
If you install over a network with FTP or HTTP you must perform a text
mode installation.
1.6 Installing in an LPAR using the Red Hat Linux
LPAR CD
The following steps are to be taken when installing Red Hat Linux onto an LPAR.
• Log in on the Support Element Workplace (some older versions of the SEW are called Hardware
Management Console) as a user with sufficient privileges to install a new OS to an LPAR. The
"SYSPROG" user is recommended.
• Select Images, then select the LPAR to which you wish to install. Use the arrows in the frame on
the right side to navigate to the CPC Recovery menu.
• Double-click on Load from CD-ROM or Server.
• In the dialog box that follows, select Local CD-ROM then click Continue.
• In the dialog that follows, keep the default selection of redhat.ins then click Continue.
• Skip to Section 1.8, Installing in an LPAR (Common Steps) to continue.
1.7 Installing in an LPAR without the Red Hat Linux
for S/390 CD-ROMs
1.7.1 Installing in an LPAR without the Red Hat Linux LPAR
CD using a recent SEW
• Log in on the Support Element Workplace as a user with sufficient privileges to install a new OS
to an LPAR. The "SYSPROG" user is recommended.
• Select Images, then select the LPAR you wish to install to.
• Use the arrows in the frame on the right side to navigate to the CPC Recovery menu.
• Double-click on Load from CD-ROM or Server.
• In the dialog box that follows, select FTP Source, and enter the following information:
Host Computer:
hostnameorIPaddressoftheFTPserveryouwish to installfrom(e.g. ftp.redhat.com)