Red Hat ENTERPRISE LINUX 3 - INSTALLATION GUIDE FOR IBM S-390 AND IBM ESERVER ZSERIES, Enterprise Linux 3 Installation Manual
Red Hat Enterprise Linux 3
Installation Guide for the IBM®
S/390® and IBM® eServer™
zSeries® Architectures
Red Hat Enterprise Linux 3: Installation Guide for the IBM® S/390® and IBM® eServer™ zSeries® Architectures
Copyright © 2003 by Red Hat, Inc.
Red Hat, Inc.
1801 Varsity Drive
Raleigh NC 27606-2072 USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588
Research Triangle Park NC 27709 USA
rhel-ig-s390-multi(EN)-3-Print-RHI(2003-07-25T17:10)
Copyright © 2003 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the
Open Publication License, V1.0 or later (the latest version is presentlyavailableat http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission 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 registeredtrademarks of The Open Group.
XFree86 is a trademark of The XFree86 Project, Inc, and is pending registration.
Intel and Pentium are registered trademarks of Intel Corporation. Itanium and Celeron are trademarks of Intel Corporation.
AMD, Opteron, Athlon, Duron, and K6 are registered trademarks of Advanced Micro Devices, Inc.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.
Java and Swing are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries.
Oracle is a registered trademark, and Oracle8i, Oracle9i, and interMedia are trademarks or registered trademarks of Oracle
Corporation.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
FireWire is a trademark of Apple Computer Corporation.
IBM, AS/400, OS/400, RS/6000, S/390, and zSeries are registered trademarks of International Business Machines
Corporation. eServer, iSeries, and pSeries are trademarks of International Business Machines Corporation.
All other trademarks and copyrights referred to are the property of their respective owners.
The GPG fingerprint of the security@redhat.com key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E
Table of Contents
Introduction..........................................................................................................................................i
1. Document Conventions..........................................................................................................i
2. How to Use This Manual .....................................................................................................iii
2.1. We Need Feedback! ..............................................................................................iii
3. Accessibility Solutions ........................................................................................................iv
1. Steps to Get You Started................................................................................................................. 1
1.1. Additional S/390 Hardware Preparation for Installation Notes ......................................... 1
1.2. Basic Overview of the Boot Method.................................................................................. 1
1.3. Preparing for a Network Installation.................................................................................. 1
1.3.1. Using ISO Images for NFS Installs .................................................................... 3
1.4. Preparing for a Hard Drive Installation.............................................................................. 3
1.5. Installing under VM........................................................................................................... 3
1.6. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD ............................. 7
1.7. Installing in an LPAR without the Red Hat Enterprise Linux for S/390 CD-ROMs.........7
1.8. Installing in an LPAR (Common Steps) ............................................................................ 8
1.9. Do You Have Enough Disk Space?.................................................................................... 8
2. Installing Red Hat Enterprise Linux............................................................................................. 9
2.1. The Graphical Installation Program User Interface ........................................................... 9
2.2. The Text Mode Installation Program User Interface ......................................................... 9
2.2.1. Using the Keyboard to Navigate ....................................................................... 11
2.3. Running the Installation Program .................................................................................... 11
2.3.1. Installation using X11 Forwarding ...................................................................12
2.3.2. Installation using VNC ..................................................................................... 12
2.4. Installing from a Hard Drive (DASD).............................................................................. 12
2.5. Installing via NFS ............................................................................................................ 13
2.6. Installing via FTP............................................................................................................. 13
2.7. Installing via HTTP.......................................................................................................... 14
2.8. Welcome to Red Hat Enterprise Linux ............................................................................15
2.9. Language Selection ..........................................................................................................15
2.10. Disk Partitioning Setup .................................................................................................. 16
2.11. Automatic Partitioning................................................................................................... 17
2.12. Partitioning Your System ............................................................................................... 18
2.12.1. Graphical Display of DASD Device(s)........................................................... 19
2.12.2. Disk Druid’s Buttons ..................................................................................... 19
2.12.3. Partition Fields ................................................................................................ 19
2.12.4. Recommended Partitioning Scheme ...............................................................20
2.12.5. Editing Partitions ............................................................................................ 20
2.13. Network Configuration ..................................................................................................21
2.14. Firewall Configuration ................................................................................................... 22
2.15. Language Support Selection .......................................................................................... 24
2.16. Time Zone Configuration...............................................................................................25
2.17. Set Root Password ......................................................................................................... 26
2.18. Package Group Selection ............................................................................................... 28
2.19. Preparing to Install .........................................................................................................29
2.20. Installing Packages......................................................................................................... 30
2.21. Installation Complete ..................................................................................................... 30
A. Removing Red Hat Enterprise Linux......................................................................................... 33
B. Sample Parameter Files ...............................................................................................................35
C. Red Hat Linux to Red Hat Enterprise Linux Migration Solution ..........................................37
D. Troubleshooting Your Installation of Red Hat Enterprise Linux............................................ 39
D.1. You are Unable to Boot Red Hat Enterprise Linux......................................................... 39
D.1.1. Is Your System Displaying Signal 11 Errors?..................................................39
D.2. Trouble During the Installation....................................................................................... 39
D.2.1. No devices found to install Red Hat Enterprise Linux Error
Message........................................................................................................... 39
D.2.2. Trouble with Partition Tables........................................................................... 39
D.2.3. Other Partitioning Problems.............................................................................39
D.2.4. Are You Seeing Python Errors? ....................................................................... 40
D.3. Problems After Installation ............................................................................................. 41
D.3.1. Problems with the X Window System (GUI)................................................... 41
D.3.2. Remote Graphical Desktops and XDMCP....................................................... 41
D.3.3. Problems When You Try to Log In..................................................................42
D.3.4. Your Printer Will Not Work ............................................................................. 42
D.3.5. Apache-based httpd service/Sendmail Hangs During Startup ...................... 42
E. Additional Boot Options ..............................................................................................................43
Index................................................................................................................................................... 45
Colophon............................................................................................................................................49
Introduction
Welcome to the Red Hat Enterprise Linux Installation Guide. This guide contains useful information
to assist you during the installation of Red Hat Enterprise Linux 3. From fundamental concepts such as
installation preparation to the step-by-step installation procedure, this book will be a valuable resource
as you install Red Hat Enterprise Linux.
1. Document Conventions
When you read this manual, certain words are represented in different fonts, typefaces, 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 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 (such as file names). In these cases, they are considered
to be part of the command, so the entire phrase is 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.
file name
File names, 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 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 file systems.
Install the webalizer RPM if you want to use a Web server log file analysis program.
application
This style indicates that the program is an end-user application (as opposed to system software).
For example:
Use Mozilla 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 displays
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 exits your graphical session and return you to the
graphical login screen or the console.
ii Introduction
text found on a GUI interface
A title, word, or phrase found on a GUI interface screen or window is shown in this style. Text
shown in this style is being used to identify a particular GUI screen or an element on a GUI
screen (such as text associated with a checkbox or field). Example:
Select the Require Password checkbox if you would like your screensaver to require a password
before stopping.
top level of a menu on a GUI screen or window
A word in this style 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 File on a GNOME terminal, the New Tab option allows you to open multiple shell
prompts in the same window.
If you need to type in a sequence of commands from a GUI menu, they are shown like the
following example:
Go to Main Menu Button (on the Panel) => Programming => Emacs to start the Emacs text
editor.
button on a GUI screen or window
This style indicates that the text can be found on a clickable button on a GUI screen. For example:
Click on the Back button to return to the webpage you last viewed.
computer output
Text in this style indicates text displayed to a shell prompt such as error messages and responses
to commands. For example:
The ls command displays the contents of a directory. For example:
Desktop about.html logs paulwesterberg.png
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, is
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 must type in the text command at the boot: prompt.
replaceable
Text used for examples which is meant to be replaced with data provided by the user is displayed
in this style. In the following example,
version-numberis displayed in this style:
Introduction iii
The directory for the kernel source is /usr/src/
version-number/, where
version-numberis the version of the kernel installed on this system.
Additionally, we use several different strategies to draw your attention to certain pieces of information. In order of how critical the information is to your system, these items are marked as note, tip,
important, caution, or a warning. For example:
Note
Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE.
Tip
The directory /usr/share/doc/ contains additional documentation for packages installed on your
system.
Important
If you modify the DHCP configuration file, the changes will not take effect until you restart the DHCP
daemon.
Caution
Do not perform routine tasks as root — use a regular user account unless you need to use the root
account for system administration tasks.
Warning
Be careful to remove only the necessary Red Hat Enterprise Linux partitions. Removing other partitions could result in data loss or a corrupted system environment.
2. How to Use This Manual
This manual focuses on a VM and LPAR-based installation and is ideal for users (both new and old)
who want a quick and simple installation solution. It helps you prepare your system and walk you
through the installation of Red Hat Enterprise 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 Enterprise Linux to begin the installation process.
iv Introduction
2.1. We Need Feedback!
If you discover a typo in the Red Hat Enterprise Linux Installation Guide or have thought of a way to
make this manual better, we would love to hear from you. Submit a bug report against the component
rhel-ig-s390-multi in Bugzilla at:
http://bugzilla.redhat.com/bugzilla/
When submitting a bug report, be sure to mention the manual’s identifier:
rhel-ig-s390-multi(EN)-3-Print-RHI (2003-07-25T17:10)
If you have a suggestion for improving the documentation, try to be as specific as possible when describing 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]), use the online support system by registering your product at:
http://www.redhat.com/apps/activate/
3. Accessibility Solutions
While the graphic user interface (GUI) is convenient for sighted users, it is often inhibiting to those
with visual impairments because of the difficulty speech synthesizers have interpreting graphics. Red
Hat Enterprise Linux is an ideal operating system for users with visual limitations because the GUI is
not required by the kernel. Most modern tools including email, news, Web browsers, calendars, calculators, and much more can run on Linux without a graphical environment. The working environment
can also be customized to meet the hardware or software needs of the user.
Red Hat, Inc. is the distribution of choice for people with special needs because of the outstanding
support that is offered with the purchase of any boxed set. Many Linux distributions provide limited
or nonexistent support to customers. Red Hat’s installation support is deliverable via email or via
the telephone and special circumstances will be considered and addressed for users with physical
limitations. Customers should inform the support technician if they require specialized support.
For more information, refer to:
• http://www.tldp.org/HOWTO/Accessibility-HOWTO/
• http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html
• The README-Accessibility file provides more information and instructions for
using some of the tools available for users with special needs. This file can be found in
/usr/share/doc/redhat-release-X/, where X is the release number of your installed
product.
Chapter 1.
Steps to Get You Started
The installation process assumes basic familarity with the IBM S/390 and IBM eServer zSeries platform and makes reference to the IBM Linux for S/390 Redbook (SG24-4987-00 and SG24-6264-00)
guide (refer to http://www.redbooks.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, visit http://www.ibm.com/eserver/zseries/.
Before you install Red Hat Enterprise Linux, you must to perform the following steps:
1. Allocate sufficient DASD1partitions to provide suitable disk space (for example, 2 GB is sufficient for server installations, while 5 GB is minimally required to install all packages).
2. Acquire a minimum of 256 MB RAM (512 MB is strongly recommended) 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. Such instances should be examined
on a case-by-case basis.
4. Decide what environment under which to run the Red Hat Enterprise Linux operating system
(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. Additional S/390 Hardware Preparation for Installation Notes
The network configuration must be determined beforehand. Red Hat Enterprise Linux for S/390 supports multiple network devices including CTC, IUCV, LCS, and QDIO-enabled devices. 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.2. Basic Overview of the Boot Method
For installation you must start a kernel (with the Linux kernel), an initrd.img, and a parameter
file with some information about your network configuration. Once this is started on the S/390, the
networking is configured. You can then use telnet or ssh on another computer to log into your Red
Hat Enterprise Linux install image and start an installation script to install Red Hat Enterprise Linux.
1. Direct Access Storage Devices (or DASDs) are hard disks that allow a maximum of three (3) partitions per
DASD. For example, dasda has dasda[123].
2 Chapter 1. Steps to Get You Started
1.3. Preparing for a Network Installation
The Red Hat Enterprise Linux installation media must be available for either a network installation
(via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if you are performing an NFS, FTP, or HTTP 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/ directory. Both the RedHat/base/ and RedHat/RPMS/
directories must be available and populated with all files from all installation CD-ROMs.
Note
The directory specified in the following refers to /location/of/disk/space/. This means it is the
directory up to, but not including, the RedHat/ distribution directory. For example, if you have Red Hat
Enterprise Linux 3 installation files located in /export/redhat/ on the installation staging server,
/location/of/disk/space/ would be /export/redhat/.
To copy the RedHat/ directory from the installation CD-ROMs to a Linux machine which acts as an
installation staging server, perform the following steps:
• For each binary CD-ROM, 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 /export/redhat/
• umount /mnt/cdrom/
• Note that the Release Notes are not included in the RedHat directory. Unless they are specifically
copied over, the Release Notes will not be available during your installation of Red Hat Enterprise
Linux. The Release Notes are formatted in HTML files located at the root of the disc. Copy the files
to your installation directory. For example:
cp /mnt/cdrom/RELEASE-NOTES*.html /location/of/disk/space/
The Release Notes are also available online from http://www.redhat.com/docs/.
• 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 a specific system:
/location/of/disk/space client.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)
Start the NFS daemon (on a Red Hat Enterprise Linux machine, use /sbin/service nfs
start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux
system, use /usr/bin/service nfs reload).
Be sure to test the NFS share following the directions in the Red Hat Enterprise Linux System
Administration Guide.
If the RedHat/ directory does not appear in the NFS shared directory, the wrong path may have
been mounted and/or exported.
Chapter 1. Steps to Get You Started 3
• FTP and HTTP installations also support a second type of tree structure. To make it easier to access
the contents of the installation CD-ROMs, mount each CD-ROM or ISO image with the following
mount point on the FTP or HTTP server (where X is the number of the CD-ROM or ISO image):
/location/of/disk/space/discX /
For example:
mount -o loop CD1.iso /location/of/disk/space/disc1/
1.3.1. Using ISO Images for NFS Installs
NFS installations can use ISO (or CD-ROM) images rather than copying an entire installation tree.
After placing the required ISO images (the binary Red Hat Enterprise Linux CD-ROMs) in a directory,
choose to install via NFS. You will then point the installation program at that directory to perform the
installation.
Verifying that the ISO images are intact before you attempt an installation will help to avoid problems
that are often encountered during an NFS installation. 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 server as the ISO images.
Additionally, if a file called updates.img exists in the directory from which you install, then it will
be used for installation program updates. Refer to the file install-methods.txt in the anaconda
RPM package for detailed information on the various ways to install Red Hat Enterprise Linux, as
well as how to apply the installation program updates.
Note
You can only have the ISO images for one release and one variant of Red Hat Enterprise Linux in the
directory.
1.4. Preparing for a Hard Drive Installation
Hard drive installations require a working Linux system installed and the use of ISO (or CD-ROM)
images rather than the entire installation tree.
Hard drive installations only work from ext2 or ext3 file systems.
• Set of CD-ROMs — Create CD-ROM ISO image files from each installation CD-ROMs. For each
CD-ROM, execute the following command on a Linux system:
dd if=/dev/cdrom of=/tmp/file-name.iso
This command may raise an error message when the end of data on the CD-ROM is reached which
can be ignored. The ISO images created can now be used for installation, once copied to the correct
DASD.
• ISO images — transfer these images to the system to be installed (or to the correct DASD).
Verifying that ISO images are intact before you attempt an installation, helps 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 installation.
4 Chapter 1. Steps to Get You Started
1.5. Installing under VM
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.
i cms
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):
• cd /location/of/boot/images/
• locsite fix 80
• bin
• get kernel.img (repl
• get initrd.img (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.
Important
Follow these guidelines when creating a parameter file.
• The parameter file should contain no more than 80 characters per line.
• The VM reader has a limit of 11 lines for the parameter file (for a total of 880 characters).
• The DASD and the tape IPL have limits of 896 characters.
The following parameters are required and must be included in the parameter file:
• DASD=
dasd-list
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.
• root=
file-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:
Chapter 1. Steps to Get You Started 5
• CHANDEV=
device,input,output
Where:
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
For example:
CHANDEV=ctc0,0x600,0x601
CHANDEV=escon0,0x605,0x608
CHANDEV=qeth,0x700,0x701,0x702,0,0
To force a specific CTC protocol, additionals parameters can be added. For example:
CHANDEV=ctc0,0x600,0x601,0,n
Wherenis 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
• IUCV=
userid
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:
IUCV=TCPIP
The following parameters are optional:
• HOSTNAME=
string
Where
string
is the hostname of the newly-installed Linux guest.
• NETTYPE=
type
Where
type
must be one of the following: ctc, escon, tr, hsi, iucv, or eth.
• IPADDR=
IP
Where
IP
is the IP address of the new Linux guest.
• NETWORK=
network
Where
network
is the address of your network.
• NETMASK=
netmask
Where
netmask
is the netmask.
• BROADCAST=
broadcast
Where
broadcast
is the broadcast address.
• GATEWAY=
gw
Where
gw
is either the gateway-IP for your eth device or the IP address of the ctc/escon/iucv
point-to-point partner.
• MTU=
mtu
6 Chapter 1. Steps to Get You Started
Where
mtu
is the Maximum Transmission Unit (MTU) for this connection.
• DNS=
server1:server2:...:serverN
Where
server1:server2:...:serverN
is a list of DNS servers, separated by
colons. For example:
DNS=10.0.0.1:10.0.0.2
• SEARCHDNS=
domain1:domain2:...:domainN
Where
domain1:domain2:...:domainN
is a list of the search domains, separated by
colons. For example:
SEARCHDNS=example.com:example.org
• chandev=ctc0,
read_channel_address,write_channel_address
CHANDEV=ctc0,read_channel_address,write_channel_address
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.
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 for both parameters.
The following parameter for installations using a qeth device is optional:
• QETHPARM=
Use this option to specify additional parameters for your QETH device (for CHANDEV) such as:
add_parms,0x10,{lo_devno,hi_devno},portname:port_name
The following parameter for kickstart installations is optional:
• RUNKS=
value
Where
value
is defined as 1 if you want to run the installation program in noninteractive mode
in the 3270 terminal, or 0 otherwise.
Note
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.
i cms
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:
Chapter 1. Steps to Get You Started 7
/* */
’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.
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 Enterprise Linux LPAR CD
The following steps must be taken when installing Red Hat Enterprise Linux onto an LPAR.
• Log in on the Support Element Workplace (SEW) (some older versions of the SEW are called
Hardware Management Consoles) 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 Enterprise Linux for
S/390 CD-ROMs
• Log in on the Support Element Workplace as a user with sufficient privileges to install a new OS to
an LPAR.
• 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:
8 Chapter 1. Steps to Get You Started
Host Computer:
Hostname or IP address of the FTP server you wish to install from (for example,
ftp.redhat.com)
User ID:
Your user name on the FTP server (or anonymous)
Password:
Your password (use your email address if you are logging in as anonymous)
Account:
Leave this field empty
File location (can be left blank):
Directory on the FTP server holding Red Hat Enterprise Linux for S/390 (for example,
/pub/redhat/linux/rawhide/s390)
• Click Continue.
• In the dialog that follows, keep the default selection of redhat.ins and click Continue.
• Refer to Section 1.8 Installing in an LPAR (Common Steps) to continue.
1.8. Installing in an LPAR (Common Steps)
Once the Red Hat Enterprise Linux installation program has started (if the red field behind the LPAR
icon is disappearing, the installation program has begun), select the LPAR and double-click on Oper-
ating System Messages.
The initial installation start-up script asks you questions about your networking and DASDs unless
you have specified all necessary information in the lpar.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.
Note
If you install over a network with FTP or HTTP you must perform a text mode installation.
1.9. Do You Have Enough Disk Space?
Nearly every modern-day operating system (OS) uses disk partitions, and Red Hat Enterprise Linux is
no exception. When you install Red Hat Enterprise Linux, you may have to work with disk partitions.
The disk space used by Red Hat Enterprise Linux must be separate from the disk space used by other
OSes you may have installed on your system.
For more information about disks and partition configuration, refer to Section 2.12.4 Recommended
Partitioning Scheme.
Chapter 2.
Installing Red Hat Enterprise Linux
This chapter explains how to perform a Red Hat Enterprise Linux installation using the graphical,
mouse-based installation program. The following topics are discussed:
• Becoming familiar with the installation program’s user interface
• Starting the installation program
• Selecting an installation method
• Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
• Finishing the installation
2.1. The Graphical Installation Program User Interface
If you have used a graphical user interface (GUI) before, you are already familiar with this process;
use your mouse to navigate the screens, click buttons, or enter text fields. You can also navigate
through the installation using the [Tab] and [Enter] keys.
2.2. The Text Mode Installation Program User Interface
The Red Hat Enterprise Linux text mode installation program uses a screen-based interface that includes most of the on-screen widgets commonly found on graphical user interfaces. Figure 2-1, and
Figure 2-2, illustrate the screens that appear during the installation process.
Note
While text mode installations are not explicitly documented, those using the text mode installation
program can easily follow the GUI installation instructions and obtain all needed information.
10 Chapter 2. Installing Red Hat Enterprise Linux
Figure 2-1. Installation Program Widgets as seen in Boot Loader Configuration
Figure 2-2. Installation Program Widgets as seen in Disk Druid
Here is a list of the most important widgets shown in Figure 2-1 and Figure 2-2:
• Window — Windows (usually referred to as dialogs in this manual) appear on your screen through-
out the installation process. At times, one window may overlay another; in these cases, you can only
interact with the window on top. When you are finished in that window, it disappears, allowing you
to continue working in the window underneath.
• Checkbox — Checkboxes allow you to select or deselect a feature. The box displays either an
asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press [Space] to
select or deselect a feature.
• Text Input — Text input lines are regions where you can enter information required by the installa-
tion program. When the cursor rests on a text input line, you may enter and/or edit information on
that line.
• Text Widget — Text widgets are regions of the screen for the display of text. At times, text widgets
may also contain other widgets, such as checkboxes. If a text widget contains more information
Loading...