linux操作系统作为自由开发维护的操作系统.易于移植等特点.被许多硬件平台.从普通PC到服务器.小型机.中型机.大型机.都支持linux . IBM大型机S/390也不例外.下面就是redhat linux for s/390版本的介绍.拿出来 与大家分享.
Red Hat Linux for S/390 7.2 Release Notes
=========================================
Feedback is always appreciated and can be provided both via:
- Bugzilla Defect Tracking System
https://bugzilla.redhat.com/bugzilla/
- Mailing List
https://listman.redhat.com/mailman/listinfo/redhat-s390-list
General Notes
=============
- A wealth of information is included with this release. View:
docu/index.html
with a web browser for easy access to this content.
- Testing of IBM Java, WebSphere, DB2 and Oracle 9i Enterprise Edition
have been tested favourably. Please refer the two HOWTO documents at:
docu/Oracle-RHL72-s390-HOWTO.html
docu/WebSphereDB2-RHL72-s390-HOWTO.html
for notes on installing and using these products with Red Hat Linux
for S/390.
- This release runs on zSeries (64-bit, z900) hardware in 31-bit mode in
addition to 31-bit S/390 hardware.
- The x3270-text package offers a text-based 3270 emulator called c3270.
"Ctrl-a c" or "Ctrl-c" can be used to clear the screen in c3270.
("Alt-c" clears the screen in x3270.)
- Some S/390 and zSeries systems may not support the issuing of CP
commands with "#CP " from the 3270 console whilst Linux is
running. In this case, use of the ATTN/attention key may place the
3270 terminal into CP READ mode.
- If you are using 3390-3 DASDs, it may be necessary to use more than
one DASD for an installation. Red Hat recommends "/usr/share" as a
mount point to consider, if you wish to balance DASD use between two
DASDs.
- Software RAID is also included to effectively remove the size
limitations imposed by DASD model sizes. Anaconda supports creation
of RAID0 devices that span multiple partitions on multiple DASDs.
- Firewall Configuration -- If you are using Anaconda to install, you
can configure a firewall as part of your system installation for
additional security.
You can choose from two levels of security, as well as choosing which
common system services should be allowed or disallowed by default.
Please note that both "medium" and "high" firewall settings will cause
RPC-based services (such as NIS or NFS) to be blocked and fail to
initialize.
- The initscripts now use /sbin/ip (from the iproute packages) for most
operations. /sbin/ip requires the netlink and netlink routing features
of the kernel to function properly; it is impossible to make use of
the kernel';s full routing functionality without these features. If you
are building your own kernel, make sure that CONFIG_NETLINK and
CONFIG_RTNETLINK are enabled during kernel configuration.
- Initial unified support for Korean has been added.
- Red Hat Linux now includes the first release of the Gnome XSLT
processor (xsltproc) using version 2 of the associated XML library.
- ODBC-support has been added to php, postgresql has been updated to
7.1.3, python interfaces have been added, and perl interfaces
updated.
- Several new configuration tools are included. With these tools you can
configure:
* Network (redhat-config-network)
* Date and Time (redhat-config-date)
* System Services Control (redhat-config-services)
* Users and Groups (redhat-config-users)
- If you boot the first time after the installation has finished, you can
only log in over the network using ssh, since the telnet daemon is not
enabled by default. Also, remember that if you choose a "medium" or
"high" firewall setting you MUST enable inbound SSH access; otherwise,
SSH will also be unavailable.
- The following packages/features are deprecated, and may be removed
in a future Red Hat Linux release:
- Enlightenment window manager
- Linuxconf
- Ncpfs
Anaconda/rhsetup Installer Notes
================================
Boot loader
----------
- z/IPL is the standard boot loader used. Zilo is outdated and is no
longer supported.
- z/IPL does not support the selection of a specific kernel during IPL.
The only way to switch between different kernel versions is to install
different boot loaders on different DASDs, and IPL the corresponding
DASD.
- To boot into single-user mode from VM, create a parameter file with the
parameter "single", and boot the kernel using the installation scripts
rather than IPLing directly from the DASD.
- To boot an LPAR in single user mode, simply add the parameter "single"
when loading the LPAR.
Partitioning with Anaconda / "loader"
-------------------------------------
- The Disk Druid user interface has been redesigned to incorporate an
interface that takes better advantage of a graphical environment.
- The EXT3 journaling file system is now available.
- Pre-existing file systems may be selected for reformatting during the
installation.
- Pre-existing ext2 file systems may be migrated to ext3 during installs
and upgrades. This process does not affect the data on the file
system.
- Additional sanity checks have been made against user-created mount
points; this should avoid most common problems (such as a "/" mount
point of only 5 MB).
- Up to three partitions are supported per DASD (e.g. dasda1, dasda2,
dasda3).
- Only the z/OS Compatible Disk Layout (CDL) is supported. Linux Disk
Layout (LDL) is not supported.
- New partitions can only be created using the fdasd method.
Partitioning with rhsetup
-------------------------
- The rhsetup installation program does not support multiple partitions
on one DASD, while Anaconda does. If you select a DASD to initialize, it
will format with CDL and automatically create a single partition.
- Swap must be configured from the parameter file. You cannot setup swap
from the installation program.
- Linux Disk Layout (LDL) can be used, however Compatible Disk Layout
(CDL) is recommended. rhsetup can convert DASDs from LDL to CDL.
Kickstart
---------
- Kickstart is currently not supported on S/390. An (almost)
noninteractive installation is possible with the rhsetup installation
program when all necessary parameters are given in the .parm file.
Miscellaneous
-------------
- The individual package selection screen of Anaconda now supports a
flat view of all packages.
- For FTP-based Anaconda installation, it is now possible to loopback
mount the Red Hat Linux ISO images on an FTP server. The ISO images
should be loopback mounted as /disc1, /disc2, and so on -- in the same
directory. This directory should be then be specified when an
FTP-based installation is started.
- If you already have an working Linux system on your S/390, you can
install from loopback mounted CD images on a local DASD.
- In order to maximize space in the install image, the BusyBox program
now provides support for many commonly-used commands.
Kernel Notes
============
- The LCS and QETH/QDIO drivers are not supported by Red Hat as they
are proprietary OCO drivers that cannot be included as a part of our
standard Red Hat Linux distribution. Contact IBM for modules compiled
for use with Red Hat Linux for S/390.
See "Adding OCO modules to the installation program" for a description
on how to add these modules.
- The kernel now includes the EXT3 journalling file system. This
file system has three modes of operation:
- ';ordered';
- ';journal';
- ';writeback';
The default is ';ordered';, which will make sure that after a crash you
should always see valid data in recently-written files.
The ';writeback'; mode can be faster in some cases, but it does not
force data to disk so rigorously; therefore, after a crash you may see
corruption in recently-written files.
The ';journal'; mode copies all data to the journal, and can result in
great speed boosts if you are performing lots of synchronous data
writes (for example, on mail spools or synchronous NFS servers).
However, in normal use ';journal'; mode is usually significantly slower.
The mode is set by using the ';data='; mount option in /etc/fstab
or as ';mount -o data='; on the mount command line.
Normally, an ext2 file system is checked automatically once either a
certain period of time or a given number of mounts have passed since
the file system was last checked. At these times, a full ';fsck'; (file
system check) of the file system will be forced at system boot time in
order to check the integrity of the file system.
When the installation program creates an ext3 file system or upgrades
an ext2 file system to ext3, it disables these automatic checks. Use
';tune2fs'; with the ';-c'; and/or ';-i'; options to re-enable them, or to
disable them on ext3 file systems that you create manually.
Note that these cleanup fsck scans have nothing to do with the
file system';s behavior when an error is discovered on disk, or when
a crash occurs. If a file system consistency error is found on
disk, then on subsequent reboot a fsck will always be forced, both
for ext2 and ext3 file systems. If a crash occurs on an otherwise
intact file system, ext2 will always force a fsck, and ext3 will
always perform its file system recovery step; these cleanups are not
affected by the ';tune2fs'; forced-check interval settings.
Please keep in mind that even a journaling file system can be damaged
by power loss. When a system loses power, that system';s behavior is
undefined. For example, memory contents can decay (become randomly
corrupt) as the contents are copied to a hard drive running on the
last bit of power. This is a fundamentally different situation from
the more defined sequence of events caused by pressing the system';s
"reset" button while the system is running. In addition, IDE hard
drives do not provide all of the write order guarantees that SCSI
drives do.
Therefore, after a system crash, you will be offered a chance to
choose to check the integrity of your file systems. The file
/.autofsck is the "crash flag" used to provide this functionality.
You will be given five seconds to type "y" to check your file systems
during a boot after your system has crashed for any reason.
- The tape driver is included as /dev/ntibm0 with major number 37.
Printing Notes
==============
- The printconf system now provides a printconf-tui program, for text-
mode printer configuration.
- The printconf-tui program provides command line import and export
capabilities. The import can merge printer definitions with those that
are already present, or it can override them (the default).
Example:
printconf-tui --Xexport > settings.xml
printconf-tui --Ximport < settings.xml
or:
printconf-tui --Ximport --merge < settings.xml
Combined with redirection -- such as bash';s ';here documents'; (see the
bash man page for more information) -- it is now easy to put printer
setups into kickstart files.
- The printconf-tui program can clear settings completely.
Example:
printconf-tui --Xclear
- The printconf tools now provide limited printer auto-detection.
- redhat-config-printer-tui and redhat-config-printer-gui alias
printconf-tui and printconf-gui, respectively.
- Ghostscript has been updated to 6.51, and supports many additional
drivers, as well as encrypted PDF files.
- Support has been added for Hewlett Packard';s hpijs ghostscript
print drivers. Though they are not shipped with the distribution,
due to license restrictions, they can be downloaded from the project
site at: http://hpinkjet.sourceforge.net, and should work as drop-in
components.
Directory Sizes After a Complete "Everything" Installation
==========================================================
Directory Size in MB
/usr 3000
/usr/bin 200
/usr/lib 950
/usr/share 1400
/usr/X11R6 170
/var 130
Some Known Issues To Consider
=============================
- If NFS is performing poorly, or is resulting in errors appearing
in /var/log/messages, e.g.:
kernel: nfs: task can';t get a request slot
kernel: nfs: server not responding, still trying
you should specify the following options when mounting
the NFS share:
rsize=1024,wsize=1024,hard
- Software RAID1 is not supported in the installer due to an observed
issue with synchronization. This issue being investigated further.
- Due to some outstanding problems with the compilation of the Mozilla
source code for this architecture, Mozilla is not available
in Red Hat Linux for S/390 for this release. This means that Galeon and
Nautilus also cannot render web pages, thus Galeon is also not included.
Netscape Communicator 4.x is not released for this architecutre, so
for web browsing purposes, you may use Konqueror, lynx or links.
- Relating to the above Mozilla issue, Help is unavailable inside the
graphical printconf-gui tool. Alternatively, printconf-gui help is
available if you open a web browser and browse the documentation at
/usr/share/doc/printconf-gui/ or 文件:///usr/share/doc/printconf-gui/
- There have been observed instances of corrupted splash screens when the
graphical Anaconda installer begins. This may be followed by the
Anaconda installation program crashing with an error such as the
following:
Gdk-ERROR **: BadAccess
serial 187 error_code 10 request_code 147 minor_code 1
Gdk-ERROR **: BadIDChoice
serial 188 error_code 14 request_code 147 minor_code 5
In both cases this was resolved by changing the video card in the
workstation where the installation was being performed from. The issue
appears to be a video driver issue with XFree86 and remote X displays.
- GnoRPM - a problem exists wherein "--allmatches --nodeps" is used, by
default, when removing packages. This is an issue if, for example, one
installs a new kernel with "rpm -ivh" but then decides to remove the
old kernel with GnoRPM. Red Hat recommends against using GnoRPM to
remove any important packages from the system, including the kernel
packages.
- mcserv appears not to allow remote connections from other mc clients.
Starting the mcserv service (with "service mcserv start") appears to
work, however when an mc client tries to connect the error returned
is "MCFS invalid password". This problem is not specific to the S/390
architecture.
- If using an OpenSSH ssh client to connect to the installer environment
is unsuccessful, then you may consider forcing the use of version 1 of
the SSH protocol with:
ssh -o "Protocol 1 root@"
- Ensure that, when prompted for a FQDN (fully qualified domain name),
you do provide a FQDN rather than a simple hostname. This is of
particular importance if performing a network installation via FTP.
- If you are performing an installation of Red Hat Linux onto a new DASD
that has never previously been initialized with either CDL or LDL, you
may encounter a situation where even though initialization (with
dasdfmt) and partitioning (with fdasd) is successful, Anaconda cannot
detect the device to allow mount points to be assigned and partitions
to be formatted.
In this event, simply re-IPL the installer environment (e.g. with
#cp i 00c) and Anaconda should now successfully detect the new DASD
device and allow full use of that DASD.
- Sometimes DASD devices may be marked "active", but are not completely
formatted. In this event, DASD error messages and file system error
messages will be output from the Linux kernel to the console during
installation. In this case, use "dasdfmt" to completely re-format and
re-initialize the DASD, and then partition it with "fdasd".
Adding OCO Modules to the Installation Program
==============================================
IBM provides some kernel networking drivers not as Open Source, but only
as proprietary, binary modules that can be loaded into one specific version
of the Linux kernel. These are called OCO - object code only - drivers.
IBM';s OCO drivers can be downloaded from:
http://www.ibm.com/developerworks/opensource/linux390/download_obj.html
Due to the fact that these modules are proprietary IBM software, Red Hat can not
provide support for these drivers and are unable to assist in fixing bugs related
to these drivers. Also, linking (eg. loading) binary only modules into the
kernel affects the level of support we can provide on any kernel issues and
places kernel support outside the SLA agreement unless they can be reproduced
after completely removing the OCO modules (meaning it must be 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 get matching modules from IBM before upgrading the kernel.
If you want to add these drivers into the Red Hat Linux release, you have
to modify the files "initrd.img" or "tapeinrd.img". Run the following
commands as root on a running Linux machine:
# decompress the initrd
gunzip < ~redhat/images/initrd.img > initrd.img_unc
mkdir initrd
mount -t ext2 -o loop initrd.img_unc initrd
for i in lcs qdio qeth; do
cp /path/to/modules/$i*.o initrd/lib/$i.o
done
umount initrd
rmdir initrd
gzip -c initrd.img_unc > initrd.img
If you install with such a modified initrd, these modules will also be
copied into "/lib/modules/ibm" of the installed Linux machine.
-----
RHL 7.2 s390作者: 风三 时间: 2006-3-10 15:59 标题: 无处不在的linux...
