Red Hat Linux 7.1 for zSeries

Red Hat Linux 7.1 for zSeries
=============================

The contents of this CD-ROM are Copyright (C) 1995-2002 Red Hat, Inc. and
others. Please see the individual copyright notices in each source package
for distribution terms. The distribution terms of the tools copyrighted by
Red Hat, Inc. are as noted in the file COPYING.

Red Hat and RPM are trademarks of Red Hat, Inc.

============================================================================

Directory Organization:
=======================

Red Hat Linux 7.1 for zSeries is delivered on two CD-ROMs (CD 1 and CD 2).
CD 1 contains the following directory structure:

/mnt/redhat
|----> RedHat
| |----> RPMS -- Binary packages
| `----> base -- Information on this release of Red Hat
| Linux used by the installation process
|----> images -- Boot and ramdisk images
|----> COPYING -- Copyright information
|----> README -- This file
|----> RELEASE-NOTES -- Latest information about, and tips for
| using this release
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat

CD 2 contains the following directory structure:

/mnt/redhat
|----> RedHat
| `----> RPMS -- Additional binary packages
| `----> installer -- Sources and specfiles for the installer
|----> SRPMS -- Source packages (more are on the
| dedicated SRPMS CD)
|----> COPYING -- Copyright information
|----> README -- This file
|----> RELEASE-NOTES -- Latest information about, and tips for
| using this release
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat

Installation options:
=====================

There are two installation programs available when installing Red Hat Linux
7.1 for zSeries. Depending upon your requirements you can use either the
standard Red Hat Linux Anaconda installer (invoked as "loader"), or a
custom installer available only for the S/390 and zSeries architecture
(invoked as "rhsetup"). Both installers allow installation via FTP, HTTP,
NFS or local DASD (hard disk).

Anaconda ("loader") is the default Red Hat Linux 7.1 for zSeries installer.
Unlike "rhsetup", Anaconda allows for:

- Selecting individual packages to install
- Creating multiple partitions on each DASD
- Making use of the ext3 filesystem and/or Software RAID
- Configuring services and authentication
- Adding users

The amount of memory required for an installation using Anaconda is 128 MB.
After installation the amount of memory allocated to an LPAR or virtual
machine may be reduced.

The advantages of the "rhsetup" installation program are that it has a
minimum RAM requirement (32 MB) and lets you quickly install a machine
using either a simple text interface or a non-interactive installation.
Being script based, "rhsetup" may also be tailored more easily to suit
site-specific requirements. Remember that "rhsetup" only supports one
partition for each DASD however.

(For detailed information on how to install, please refer to the section
"How to Install" below.)

Resources for S/390 and zSeries from Red Hat and others:
========================================================

- Red Hat provide a public mailing list for discussion of Red Hat Linux
running on S/390 and zSeries hardware:

- https://listman.redhat.com/mailman/listinfo/redhat-s390-list

Please report any problems or any other feedback to this public
mailing list at <[email protected]>.

- Report problems about specific RPMs to Red Hat's defect database:

- https://bugzilla.redhat.com/bugzilla/

- Download current development versions of Red Hat Linux for zSeries:

- ftp://ftp.redhat.com/pub/redhat/linux/rawhide/s390x/
- ftp://ftp.redhat.de/pub/s390x/
- rsync://ftp.redhat.de/s390x/

- Find general Linux, S/390 and zSeries information from IBM:

- http://www-1.ibm.com/servers/eserver/zseries/os/linux/

- Obtain technical information, drivers, etc from IBM:

- http://www10.software.ibm.com/developerworks/opensource/linux390/

- Explore other resources relating to Linux and S/390 or zSeries:

- http://linuxvm.org/
- http://linux.zseries.org/

- The directory /usr/src/linux/Documentation/s390/ are part of the current
kernel sources available from:

- ftp://ftp.kernel.org/pub/linux/kernel/

We at Red Hat welcome and value your feedback, comments and suggestions.

How to Install:
===============

Requirements for installation:
------------------------------
You can install the Red Hat Linux distribution via four different
installation methods / sources - over a network connection via FTP, HTTP or
NFS, or directly from a locally attached DASD (hard disk).

Memory requirements for installation depend upon which installer you use:

- Anaconda ("loader") 128 MB
- "rhsetup" 32 MB

(See above for more information on the two installers available.)

For the installation you must IPL (boot) the Red Hat Linux installer
environment, which is defined by several files:

- A Linux kernel suited for installation of Red Hat Linux.
(kernel.img or tapekrnl.img)
- An initial ramdisk ("initrd") consisting of a basic Linux system
and the Red Hat Linux installer environment.
(initrd.img or tapeinrd.img)
- an optional second "initrd" consisting of IBM proprietary object code
only modules required for use with certain hardware (ocord.img)
- A parameter file with information about your hardware and networking
configuration.

This environment provides TCP/IP networking and both SSH and Telnet
daemons. Once networking has been configured, one can log in via an ssh or
telnet, and begin the actual installation and configuration of Red Hat
Linux on DASD.

Common steps needed for installing Red Hat Linux to a VM or LPAR:
-----------------------------------------------------------------
The actual installation process requires access to the files and RPM
packages which are available from either official Red Hat CD-ROMs or via
FTP (see above). The breakdown of methods by which packages are provided
to the installer is as follows:

Via Network Access (if no existing Linux installation)
------------------
1. To an NFS, FTP or HTTP network location where the files are
provided in a single merged tree
-> SEE METHOD #1

2. To an FTP or HTTP network location where the files are provided
directly from:
- Official Red Hat CD-ROMs which have been mounted.
- CD-ROM ISO images which have been "loopback" mounted.
(Does not work with "rhsetup" / only works with Anaconda.)
-> SEE METHOD #2

From DASD
---------
3. From a DASD available to the target LPAR or virtual machine.
(This requires a Linux ext2 or ext3 filesystem to exist on the DASD,
and hence Linux will have already been installed previously, quite
possibly on the same LPAR or virtual machine. This also requires
having official Red Hat CD-ROMs.)
-> SEE METHOD #3

METHOD #1: NFS, FTP, HTTP w/ merged tree
----------
- Set up an FTP, HTTP or NFS server on a separate machine. We will
name the server RPMSERVER for the purposes of this document.

FTP, HTTP and NFS installation methods require that you copy the complete
installation CD-ROM (CD 1) into a new directory on the server. Insert
CD 1, and:

mount /mnt/cdrom
cp -a /mnt/cdrom/RedHat /target/directory
umount /mnt/cdrom

Next, you must copy the contents of the /RedHat/RPMS/ directory of the
second CD-ROM into the subdirectory RedHat/RPMS on the server. Replace
CD 1 with CD 2, and:

mount /mnt/cdrom
cp -a /mnt/cdrom/RedHat /target/directory
umount /mnt/cdrom

- Setup up RPMSERVER to export via NFS, or provide via FTP or HTTP, the
target directory you created.

- If you intend to provide the files via NFS, add the target directory to
/etc/exports using an editor (such as vi, emacs, etc). The correct
entry for a Red Hat Linux system would be:

/target/directory ip.of.your.s390(ro)

Then restart the NFS service. On a Red Hat Linux system:

service nfs restart

As root, you can verify what is being exported via NFS, with:

showmount -e

You can also verify NFS is working correctly from another machine by
mounting the exported directory.

METHOD #2: FTP, HTTP with mounted official Red Hat CD-ROMs or ISO images
----------
- An alternative to Method #1, either mount both CD-ROMs (CD 1 and CD 2)
directly on the server (requires two CD-ROM drives), e.g.:

mkdir /var/ftp/pub/RHL
mkdir /var/ftp/pub/RHL/disc1
mkdir /var/ftp/pub/RHL/disc2
mount /dev/cdrom /var/ftp/pub/RHL/disc1
mount /dev/cdrom1 /var/ftp/pub/RHL/disc2

or mount ISO image files of both CD 1 and CD 2 via loopback, e.g.:

mkdir /var/ftp/pub/RHL
mkdir /var/ftp/pub/RHL/disc1
mkdir /var/ftp/pub/RHL/disc2
mount -o loop -t iso9660 /tmp/CD1.iso /var/ftp/pub/RHL/disc1
mount -o loop -t iso9660 /tmp/CD2.iso /var/ftp/pub/RHL/disc2

- Assuming you have official Red Hat Linux 7.1 for zSeries CD-ROMs and
either prefer to mount ISO images or have only one CD-ROM drive, you can
create ISO image files. Mount each CD-ROM in turn on a Linux workstation
and issue a "dd" command similar to:

dd if=/dev/cdrom of=/tmp/CD1.iso

(Ensure sufficient free disk space exists in /tmp to create two ISO image
files. The command above also assumes the CD-ROM drive is available as
/dev/cdrom.)

- Installing via FTP requires that the CD-ROMs or mounted ISO images be
accessed using the following URLs:

* CD 1 accessible from ftp://.../disc1
* CD 2 accessible from ftp://.../disc2

- Installing via HTTP requires that the CD-ROMs or mounted ISO images be
accessed using the following URLs:

* CD 1 accessible from http://.../disc1
* CD 2 accessible from http://.../disc2

When prompted for the HTTP or FTP location (URL), enter the URL for the
first CD-ROM without a trailing slash.

METHOD #3: From DASD with an existing Linux filesystem
----------
- If you already have a working zSeries Linux system, you can install
from the CD-ROM images using the target system's own DASD.

- Assuming you have official Red Hat Linux 7.1 for zSeries CD-ROMs, you
will need to create ISO image files. Mount each CD-ROM in turn on a
Linux workstation and issue a "dd" command similar to:

dd if=/dev/cdrom of=/tmp/CD1.iso

(Ensure sufficient free disk space exists in /tmp to create two ISO image
files. The command above also assumes the CD-ROM drive is available as
/dev/cdrom.)

- Copy the ISO images of both CD 1 and CD 2 to the running DASD, and then
ensure that the DASD is available to the new virtual machine or LPAR.

- See "RPMSERVER=dasd" under the section "Customizing the Parameter File"
below.

Installing Red Hat Linux in VM (z/VM):
--------------------------------------
- Log in to 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 Linux systems. Alternatively, use the OS/2
3270 terminal emulator on the S/390 management console.

If you use x3270, the recommended character set is 'U.S.English'
If you do not use this character set, you will notice some garbled
characters. Add these lines to /usr/X11R6/lib/X11/app-defaults/X3270
or $HOME/.Xdefaults :

x3270.charset: us.intl
x3270.keymap: circumfix
x3270.keymap.circumfix: <key>asciicircum: Key("^")\n

"Alt-c" will clear the screen in x3270. "Ctrl-a c" or "Ctrl-c" will
clear the screen in c3270.

- If you are not already in CMS mode, enter it now:

i cms

- Ensure that you have enough free space available on your 191 disk to hold
~8MB of additional data.

- Connect via FTP to a machine containing the Red Hat Linux 7.1 for zSeries
boot images and log in.

- Enter the following FTP commands:

cd /where/the/boot/images/are
ascii
mget *.prm *.exec (repl
locsite fix 80
bin
mget kernel.img initrd.img (repl

if using optional OCO second ram disk:
cd /where/the/second/ramdisk/is
mget ocord.img (repl

quit

- If you wish to edit the parameter file "redhat.prm". For details, refer
to the section "Customizing the Parameter File" below.

If you do not customize the parameter file, you will be prompted for
the values during setup.

- Log out as the VM user maintaining Linux installations with the "logout"
CP command, as follows:

#cp log

(When Linux is running, CP commands must be entered by prefixing with
"#cp ". Some zSeries VM systems may require using the ATTN/attention
key instead, the place the 3270 terminal into CP READ mode. (Alt-A in
x3270))

- Reconnect and log in as the VM user / machine you wish to install to.
- If you are not in CMS, IPL CMS as follows:

i cms

- If you are choosing to use the second initial ramdisk (containing
the proprietary object code only drivers), you may need to adjust
your exec script to include the additional ramdisk:

for example, a redhat exec script that wouldn't use the second
ramdisk may look similar to:

/* */
'cl rdr'
'purge rdr all'
'spool punch * rdr'
'PUNCH KERNEL IMG A (NOH'
'PUNCH REDHAT PRM A (NOH'
'PUNCH INITRD IMG A (NOH'
'ch rdr all keep nohold'
'i 00c'

but the same exec script including the second ramdisk would have an
additional line:

/* */
'cl rdr'
'purge rdr all'
'spool punch * rdr'
'PUNCH KERNEL IMG A (NOH'
'PUNCH REDHAT PRM A (NOH'
'PUNCH INITRD IMG A (NOH'
'PUNCH OCORD IMG A (NOH'
'ch rdr all keep nohold'
'i 00c'

- Run the "redhat" script:

redhat

- Answer any questions the script asks (if you have set up all parameters
in the redhat.prm file, there should be no questions). Specify the
correct networking and DASD information for your hardware, LPAR and VM
environment.

For more information about networking, consult:

- The description of the CHANDEV= , QETHPARM= , HOST= parameters in
"Customizing the Parameter File" below.
- "Device Drivers and Installation Commands (March 4, 2002)" - a
document from IBM included with the distribution (docs/lzsdd08.pdf).
- The section "IBM's OCO Modules" below if using IBM's OCO QETH/QDIO
modules for Ethernet, Token Ring or HiperSockets networking.

- When the boot process is complete, use either an ssh or telnet client
to log in to the Red Hat Linux installer environment (no password is
required). To start the Anaconda installer, enter in the ssh or telnet
client:

loader

or to start the "rhsetup" installer:

rhsetup

(You may also run "rhsetup" from the 3270 console as well, however the
installation will proceed in text-mode only.)

- The Red Hat Linux installation process should proceed normally.

- When installation concludes, you are ready to IPL your installed Linux
system for the first time. IPL from the DASD which contains the
installed Linux boot image with the following CP command:

#cp i nnn

(where nnn is the address of the DASD containing the Linux boot image)

- Once the installed Red Hat Linux system has booted and is operational,
disconnect from the 3270 console with the "disc" CP command:

#cp disc

DO NOT log out (e.g. #cp logout), as logging out will stop the virtual
machine and consequently the running Linux system.

Installing in an LPAR with the Red Hat Linux CD-ROM:
----------------------------------------------------
- Use Single Object Operations on the HMC to access the Support Element
Workplace (SEW) 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 "Local CD-ROM" and click on
"Continue".

- In the dialog that follows, keep the default selection of redhat.ins and
click continue.

- Continue on to the section "Installing in an LPAR (common steps)" below.

Installing in an LPAR without the Red Hat Linux CD-ROM:
-------------------------------------------------------
- Use Single Object Operations on the HMC to access the Support Element
Workplace (SEW) 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:

- Host Computer: Hostname or IP address of the ftp server you wish to
install from
(e.g. ftp.redhat.com)
- User ID: Your user name on the ftp server (or "anonymous")
- Password: Your password (use your email address if you're
logging in as "anonymous")
- Account: Leave this field empty
- File location: Directory on the ftp server which contains Red Hat
Linux 7.1 for zSeries
(e.g. /pub/redhat/linux/7.1/en/os/s390x)

- Click "Continue".

- In the dialog that follows, keep the default selection of redhat.ins and
click continue.

- Continue on to the section "Installing in an LPAR (common steps)" below.

Continuing Installation in an LPAR (common steps):
--------------------------------------------------
- Once the Red Hat Linux installation program has started (the red field
behind the LPAR icon will disappear), select the LPAR and double-click
on "Operating System Messages".

- Answer any questions the script asks (if you have set up all parameters
in the redhat.prm file, there should be no questions). Specify the
correct networking and DASD information for your hardware, LPAR and VM
environment.

For more information about networking, consult:

- The description of the CHANDEV= , QETHPARM= , HOST= parameters in
"Customizing the Parameter File" below.
- "Device Drivers and Installation Commands (March 4, 2002)" - a
document from IBM included with the distribution (docs/lzsdd08.pdf).
- The section "IBM's OCO Modules" below if using IBM's OCO QETH/QDIO
modules for Ethernet, Token Ring or HiperSockets networking.

- When the boot process is complete, use either an ssh or telnet client
to log in to the Red Hat Linux installer environment (no password is
required). To start the Anaconda installer, enter in the ssh or telnet
client:

loader

or to start the "rhsetup" installer:

rhsetup

(You may also run "rhsetup" from the 3270 console as well, however the
installation will proceed in text-mode only.)

- The Red Hat Linux installation process should proceed normally.

Customizing the Parameter File:
===============================
- You may also customize the parameter file "redhat.prm" with the
following parameters:

* required parameters:

root=/dev/ram0 ro ip=off
These values are given directly to the Linux kernel and
should be left as provided.
nopfault
This parameter is currently required if one or more of the
following APARs have not been applied:
UM30216 - z/VM 3.1.0
UM30219 - z/VM 4.1.0
UM30220 - z/VM 4.2.0
DASD=x-y
Range of addresses for DASD devices to be used by Linux.
200-20f should be sufficient in many cases.
Note: Take care when the addresses of VM partitions are
within this range, since they will appear in the list of
available DASD devices and may be selected for formatting.
Do NOT format partitions which contain data required by VM.
CHANDEV=device,input,output
device: Type of device (ctc0, escon0, lcs0,qeth0)
input: Input port for this device
output: Output port for this device
e.g.: CHANDEV=ctc0,0x600,0x601
for CTC (vCTC)
CHANDEV=escon0,0x605,0x608
for ESCON
CHANDEV=lcs0,0x601,0x602
for LCS Ethernet, Token Ring
CHANDEV=qeth0,0x601,0x602,0x603
for QETH Ethernet, Token Ring, HiperSockets
Notes:
- Remember that IUCV does not use CHANDEV= ; see HOST= .
- To use QETH (qeth0), see the section "IBM's OCO Modules"
below.
- All QETH devices are described here as "qeth0" and not
as "eth0", "tr0" or "hsi0".
- See the IBM document "Device Drivers and Installation
Commands (March 4, 2002)" for more information.
(docs/lzsdd08.pdf)
- To force a specific CTC protocol, additionals parameters
can be added:
CHANDEV=ctc0,0x600,0x601,0,XXX
where XXX should be either
0 for compatibility mode, used with NON-Linux
peers other than OS/390 and z/OS
1 for extended mode
2 for 'CTC-based tty', only supported on
Linux-Linux connections
3 for compatibility mode with OS/390 and z/OS

* optional parameter for QETH installations using qeth0, hsi0 device:

QETHPARM=
Use this option to give additional parameters for your
QETH device (for chandev) such as:
add_parms,0x10,{lo_devno,hi_devno},portname:port_name
lo_devno: Low end of address range
hi_devno: High end of address range
port_name: Identifies port for sharing by other
OS images, 1-8 characters long.
e.g.: QETHPARM=add_parms,0x10,0x0600,0x0602,portname:port0600
With QETHPARM you can associate an OSA-Express feature in
QDIO mode with a port name.

* optional parameters:

HOST=<...>
The values for the HOST statement depend on whether you want to install
this machine via an Ethernet driver or via ctc/escon/iucv devices:
HOST=fqdn:device:ipaddr:gateway[:mtu]
for CTC, ESCON
fqdn: Fully qualified domain name of the virtual machine
device: "ctc0" for CTC
"escon0" for ESCON
ipaddr: Fixed IP address for the virtual machine
gateway: IP address of the gateway
mtu: Maximum Transfer Unit size
(optional; should be 1492 or 1500)
HOST=fqdn:device:ipaddr:host:gateway[:mtu]
for IUCV
fqdn: Fully qualified domain name of the virtual machine
device: "iucv0"
ipaddr: Fixed IP address for the virtual machine
host: VM host name of IUCV partner
(usually "TCPIP" for VM or "$TCPIP" for VIF)
gateway: IP address of the IUCV partner
mtu: Maximum Transfer Unit size (optional)
HOST=fqdn:device:ipaddr[:mtu]
for LCS Ethernet, Token Ring
fqdn: Fully qualified domain name of the virtual machine
device: "eth0" for Ethernet
"tr0" for Token Ring
ipaddr: Fixed IP address for the virtual machine
mtu: Maximum Transfer Unit size (optional)
HOST=fqdn:device:ipaddr[:mtu]
for QETH Ethernet, Token Ring, HiperSockets
fqdn: Fully qualified domain name of the virtual machine
device: "eth0" for Ethernet
"tr0" for Token Ring
"hsi0" for HiperSockets
ipaddr: Fixed IP address for the virtual machine
mtu: Maximum Transfer Unit size
(optional, should be 1492 / 1500, range 576-18000,
for HiperSockets maximum can be up to 57344 but
depends on the CHPID definition's max frame size)
NETWORK=IP:netmask:broadcast[:gw]
IP: address of the network
netmask: netmask
broadcast: broadcast address
gw: gateway IP for eth device (for eth device only)
DNS=list:of:dns:servers
the list of DNS servers, separated by colons
e.g.: 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
e.g.: SEARCHDNS=redhat.de:redhat.com
RPMSERVER=ftp://your.ftp.server/your.s390.rpm.dir
RPMSERVER=ftp://user:[email protected]//your.s390.rpm.dir
RPMSERVER=http://your.http.server/your.s390.rpm.path
RPMSERVER=IP:/dir
The Red Hat Linux 7.1 for zSeries binary RPM packages may
be located on any of your FTP or HTTP servers, or may be
provided by an NFS server (specified by IP address and
directory).
RPMSERVER=dasd[a-z][1]:<dir>/<CD image 1>,dasd[a-z]1:<dir>/<CD image 2>
Installation can also use a local DASD for RPM packages.
See above for information on this method. Specify the
device name, directory and file names for the two ISO
images (of CD 1 and CD 2). The images may reside on
different DASD.
LANG=en_US|de_DE|ja_JP
Sets the locale for the installer

* optional parameters for installations using the "rhsetup" installer:

DTZ=timezone
default time zone as returned by the tzselect-utility,
e.g.: DTZ=Europe/Berlin or DTZ=America/Chicago
VERBOSEWGET=
Use this option to supply additional parameters to the wget
command. If this parameter is non-empty, the downloading
of files from the FTP server will be more verbose. This may
help with tracking down errors, but the parameter should be
omitted if you do not have any problems with the
installation.
Setting VERBOSEWGET to a value which wget (see 'man wget')
does not understand will result in an error during the
installation.
This parameter applies to the FTP and HTTP installation
methods only.
INSTALL=package selection
defines the pre-selection of packages. It must be one of
"minimal", "desktop", "default", "server", "all".
MOUNTS=dev:mountpoint,dev2:mountpoint2
defines a comma-delimited list of DASD device-partitions
and where they should be mounted by default.
eg: MOUNTS=/dev/dasda1:/,/dev/dasdb1:/usr,/dev/dasdc1:/tmp
SWAP=list:of:swap:devices
the list of initial swap devices, delimited by colons
ROOTPW=my_secret_password
the default unencrypted root password.
e.g.: ROOTPW=sEcrEt
CROOTPW=my_crypted_password
the encrypted password for /etc/shadow (can be taken from
another Linux machine or generated manually)
DEBUG=<value>
if set to any value you will get a shell during
installation to debug if you encounter problems.
FORCEDASDFORMAT=<value>
if set to 'yes', rhsetup will not ask for confirmation
whether DASD from the MOUNT variable should be formatted
INTERACTIVE=<value>
if set to 0 (zero) and all needed parameters are given in
the .prm file, the rhsetup script will be called
automatically, therefore the telnet/login step may be
omitted and a complete installation without user interaction
is possible.

- 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 (880
characters).

- The DASD and the tape IPL have a limit of 896 characters
(include/asm/setup.h and arch/s390/kernel/head.S).

- If you omit any of these parameters, you will be prompted for them at
installation time.

Mounting DASD in the Red Hat Linux Installer Environment (Rescue Mode):
=======================================================================

In the event of a boot loader error or other problem, the need may arise
to mount DASD and access filesystem contents manually. Reinstallation may
be unnecessary.

Simply start the installer environment as for installation, and log in via
a telnet or ssh client. Load the dasd_mod and dasd_eckd_mod modules and
create the block device special files. For example:

insmod dasd_mod
insmod dasd_eckd_mod
mknod /tmp/dasda b 94 0
mknod /tmp/dasda1 b 94 1
mknod /tmp/dasdb b 94 4
mknod /tmp/dasdb1 b 94 5

Create the block device special files so that you can
Now, mount any filesystems on the available DASD under the directory
/mnt/sysimage (or a newly created directory) and run chroot to that
directory. For example:

mkdir /a
mount /tmp/dasda1 /a
mount /tmp/dasdb1 /a/usr/share
chroot /a

Complete any necessary tasks (e.g. re-run zipl), then exit from the chroot
environment and unmount any filesystems which you mounted. For example:

exit
umount /a/usr/share
umount /a

You can now re-IPL the machine.

Examples of Parameter (.prm) Files:
===================================

Install in a LPAR:
------------------
root=/dev/ram0 ro ip=off
HOST=lpar.redhat.de:eth0:172.16.2.176
NETWORK=172.16.2.0:255.255.255.0:172.16.2.255:172.16.2.1
DNS=172.16.2.2:172.16.2.15 SEARCHDNS=redhat.de:redhat.com
RPMSERVER=172.16.2.140:/ftp/pub/redhat/linux/s390x
MOUNTS=/dev/dasda1:/,/dev/dasdb1:/usr/share
INSTALL=default DTZ=CET
ROOTPW=sEcrEt FORCEDASDFORMAT=yes INTERACTIVE=0

Install in VM:
--------------
root=/dev/ram0 ro ip=off DASD=200-20f
CHANDEV=ctc0,0x600,0x601
HOST=s390.redhat.de:ctc0:172.16.3.225:192.168.20.1:1492
DNS=172.16.2.2:172.16.2.15 SEARCHDNS=redhat.de:redhat.com
RPMSERVER=ftp://172.16.2.140/pub/redhat/linux/s390x
MOUNTS=/dev/dasda1:/,/dev/dasdb1:/usr/share
INSTALL=default DTZ=CET

Common System Administration Tasks After Installation:
======================================================

- "chkconfig" (as root) can enable services including xinetd. To enable
the telnet daemon (not recommended for security reasons):

chkconfig telnet on
chkconfig xinetd on

This will make telnet or xinetd available upon next IPL. To start
xinetd or telnet immediately, use the "service" command:

service xinetd start

- "setup" (as root) an be used to configure your machine. "locale_config"
and "timetool" may also be of interest.

- Configure xdm and XDMCP for remote X:

- Set the desktop to 'AnotherLevel'.
Either:
Edit /etc/sysconfig/desktop and change the line DESKTOP=xxxx to
DESKTOP=AnotherLevel
or
Edit /etc/X11/prefdm and search for the line

if [ -n "$preferred" ] && which $preferred >/dev/null 2>&1; then

Add the following line:

preferred=xdm

ABOVE it.

- Edit /etc/X11/xdm/xdm-config and comment out the line

DisplayManager.requestPort: 0

by placing a ! in front of it.

- Edit /etc/X11/xdm/Xaccess and remove the first # from the following
line:

# * #any host can get a login window

IBM's OCO Modules:
==================

IBM provide some kernel networking drivers not as Open Source, but rather
as proprietary, binary modules that can be loaded into one specific version
of the Linux kernel. These are called Object Code Only (OCO) drivers.

OCO drivers compiled for the Red Hat Linux 7.1 for zSeries kernel are
available from IBM's DeveloperWorks web site:

http://www10.software.ibm.com/developerworks/opensource/linux390/special_oco_rh_2.4.shtml

** NOTE **
Due to the fact that these modules are proprietary IBM software, Red Hat
is not able to provide comprehensive support for these drivers and cannot
fix defects caused by these drivers. Also, linking (eg. loading) binary
only modules into the kernel affects the level of support that can be
provided for kernel issues. A kernel issue will not be covered by the SLA
unless the issue is reproducable after a clean reboot without OCO modules.

Red Hat recommends the use of drivers that match your exact kernel version
as they will not work reliably with a newer or older kernel release. Also
take care when using Red Hat Network to apply (security) upgrades; you need
to obtain matching modules from IBM before applying any kernel upgrades via
Red Hat Network or any other update mechanism.

The support for a second initrd may not be a long-term supported mechanism,
and systems should not be built to depend upon it.

Adding QETH and QDIO OCO Modules in a "Second Initial Ramdisk":
---------------------------------------------------------------
To add the QETH and QDIO modules into the Red Hat Linux 7.1 for zSeries
release and hence gain QETH and HiperSockets networking support, add the
initrd.img file which contains the IBM OCO modules as a second initial
ramdisk when preparing for installation.

Depending upon your type of installation, you need to specify the second
initial ramdisk in the appropriate file:

- VM -> redhat.exec (/images on CD 1)
- LPAR -> redhat.tdf (/images on CD 1)
- LPAR CD-boot -> redhat.ins (base directory of CD 1)

As an example, the redhat.exec file should read as follows, after
modification:

/* */
'cl rdr'
'purge rdr all'
'spool punch * rdr'
'PUNCH KERNEL IMG A (NOH'
'PUNCH REDHAT PRM A (NOH'
'PUNCH INITRD IMG A (NOH'
'PUNCH INITRD2 IMG A (NOH'
'ch rdr all keep nohold'
'i 00c'

The redhat.ins file would need to be modified to read like:

images/tapekrnl.img 0x00000000
images/tapeinrd.img 0x00800000
initrd-OCO.img 0x01200000
images/redhat.prm 0x00010480

Upon adding the second initial ramdisk to the installer environment:

- The installer will automatically detect the presence of the OCO modules
and provide the extra network interfaces for use during installation.
- The OCO modules will be copied to the installed Linux system for use
after installation. They are placed in:

/lib/modules/<kernel-version>/

Details of the Second Initial Ramdisk:
--------------------------------------
Filesystem structure of the second initrd:

-\
|
|- /<kernelversion1>/<oco-modules>
|
|- /<kernelversion2>/<oco-modules>
...

where <oco-modules> is the directory structure used by 'make modules_install'
when building a kernel.

This structure means that a single second initrd file can serve modules
for multiple supported kernelversions.

-----
RHL 7.1 s390x