Please read TUV release notes that are attached.
--------------------------------------------------------------------------
Scientific Linux Release 4.8 on i386 July 28, 2009
Items marked with a "*" indicate changes since 4.7
It may be possible to upgrade to this release from Scientific Linux 3.0.x
i386 if the anaconda installer is used. Yum is known to NOT work.
*This includes Update 8
See SL.documentation for the vendor release notes.
Send comments/issues/test reports to [log in to unmask]
--------------------------------------------------------------------------
Table of contents
DOWNLOAD INFO
ADDED compared to Enterprise 4
UPDATED compared to Enterprise 4
Installer/legal modifications
ADDED by Upstream Vendor
TECHNOLOGY PREVIEW by Upstream Vendor
/contrib
SRPMS
HARDWARE REQUIREMENTS
LIMITATIONS
INFO
ERRATA
_____________________________________________________________________________
DOWNLOAD INFO
_____________________________________________________________________________
http://ftp.scientificlinux.org/linux/scientific/48/i386
ftp://ftp.scientificlinux.org/linux/scientific/48/i386
http://ftp.scientificlinux.org/linux/scientific/48/iso/i386
ftp://ftp.scientificlinux.org/linux/scientific/48/iso/i386
-----------------------------------------------------------------------------
ADDED compared to vendor
-----------------------------------------------------------------------------
*915resolution
915resolution is a tool to modify the video BIOS of the 800 and 900
series Intel graphics chipsets. This includes the 845G, 855G, and
865G chipsets, as well as 915G, 915GM, and 945G chipsets. This
modification is necessary to allow the display of certain graphics
resolutions for an Xorg or XFree86 graphics server.
915resolution's modifications of the BIOS are transient. There is
no risk of permanent modification of the BIOS. This also means that
915resolution must be run every time the computer boots inorder for
it's changes to take effect.
915resolution is derived from the tool 855resolution. However, the i
code differs substantially. 915resolution's code base is much simpler.i
915resolution also allows the modification of bits per pixel.
* 915resolution-0.5.3-6.el4.i386.rpm
*alpine
Alpine is a tool for reading, sending, and managing electronic messages.
Alpine is the successor to Pine and was developed by Computing &
Communications at the University of Washington.
* Our version of alpine 2.00 has the following changes compared to
* our 1.0 version
* An /etc/alpine/pine.conf.sample file is installed, no longer overwriting
* an existing pine.conf Therefore an existing pine.conf in /etc/alpine
* will be left untouched even after the upgrade. For an installation from
* scratch it is advantageous to copy the sample conf file to pine.conf,
* but alpine works also without it.
* Users are now able to use a .alpine.passfile
*
* This version of alpine when it writes to a large old Unix mailbox format
* email area can be very slow. The best solution to this is to convert
* your old Unix mailbox files to "mix" format mail files.
* More info can be obtained from
*
* Evaluation of file formats:
* http://mailman2.u.washington.edu/pipermail/alpine-info/2008-July/000971.html
* Problem description:
* http://mailman2.u.washington.edu/pipermail/alpine-info/2009-February/thread.html#1658
* Conversion :
* http://www.phwinfo.com/forum/comp-mail-imap/198358-mailutil-mix-file-size.html
*
* alpine-2.00-2.el4.i386.rpm
apt
apt-0.5.15cnc6-9.SL.i386.rpm
apt-devel-0.5.15cnc6-9.SL.i386.rpm
* apt-sourceslist-48-1.SL.i386.rpm
apt-autoupdate-1-5.SL.noarch.rpm
apt-firstboot-1-5.SL.noarch.rpm
apt-scripts-1-5.SL.noarch.rpm
*cfitsio
CFITSIO is a library of C and FORTRAN subroutines for reading and
writing data files in FITS (Flexible Image Transport System) data format
CFITSIO is widely used in the astronomical community.
* cfitsio-3.100-1.el4.i386.rpm
* cfitsio-devel-3.100-1.el4.i386.rpm
Cluster Suite & GFS
A bug fix required a minor change to the cman/sm message formats
between SL 4.1 and SL 4.2 that make the two versions incompatible, so all
nodes need to be running the SL 4.2 version.
In other words:
If you have to upgrade from SL 4.0 and 4.1, you have to updated your
whole cluster at once.
ccs-1.0.11-1.i686.rpm
ccs-devel-1.0.11-1.i686.rpm
* cluster-cim-0.11.2-1.el4.i386.rpm
* cluster-snmp-0.11.2-1.el4.i386.rpm
* cman-1.0.27-1.el4.i686.rpm
* cman-devel-1.0.27-1.el4.i686.rpm
* cman-kernel-2.6.9-56.7.4.i686.rpm
* cman-kernel-hugemem-2.6.9-56.7.4.i686.rpm
* cman-kernel-smp-2.6.9-56.7.4.i686.rpm
* cman-kernel-xenU-2.6.9-56.7.4.i686.rpm
* cman-kernheaders-2.6.9-56.7.4.i686.rpm
* cmirror-1.0.2-1.el4.i386.rpm
* cmirror-kernel-2.6.9-43.12.1.i686.rpm
* cmirror-kernel-hugemem-2.6.9-43.12.1.i686.rpm
* cmirror-kernel-smp-2.6.9-43.12.1.i686.rpm
* cmirror-kernel-xenU-2.6.9-43.12.1.i686.rpm
dlm-1.0.7-1.i686.rpm
dlm-devel-1.0.7-1.i686.rpm
* dlm-kernel-2.6.9-58.6.1.i686.rpm
* dlm-kernel-hugemem-2.6.9-58.6.1.i686.rpm
* dlm-kernel-smp-2.6.9-58.6.1.i686.rpm
* dlm-kernel-xenU-2.6.9-58.6.1.i686.rpm
* dlm-kernheaders-2.6.9-58.6.1.i686.rpm
* fence-1.32.67-1.el4.i686.rpm
* GFS-kernel-2.6.9-85.2.1.i686.rpm
* GFS-kernel-hugemem-2.6.9-85.2.1.i686.rpm
* GFS-kernel-smp-2.6.9-85.2.1.i686.rpm
* GFS-kernel-xenU-2.6.9-85.2.1.i686.rpm
* GFS-kernheaders-2.6.9-85.2.1.i686.rpm
* gnbd-kernel-2.6.9-10.56.3.i686.rpm
* gnbd-kernel-hugemem-2.6.9-10.56.3.i686.rpm
* gnbd-kernel-smp-2.6.9-10.56.3.i686.rpm
* gnbd-kernel-xenU-2.6.9-10.56.3.i686.rpm
* gnbd-kernheaders-2.6.9-10.56.3.i686.rpm
gulm-1.0.10-0.i686.rpm
gulm-devel-1.0.10-0.i686.rpm
iddev-2.0.0-4.i686.rpm
iddev-devel-2.0.0-4.i686.rpm
* luci-0.11.2-2.el4.i386.rpm
* lvm2-cluster-2.02.37-3.el4.i386.rpm
magma-1.0.8-1.i686.rpm
magma-devel-1.0.8-1.i686.rpm
* magma-plugins-1.0.15-1.i386.rpm
* modcluster-0.11.2-1.el4.i386.rpm
perl-Net-Telnet-3.03-3.noarch.rpm
* piranha-0.8.3.1-4.i386.rpm
* rgmanager-1.9.87-1.el4.i386.rpm
* ricci-0.11.2-2.el4.i386.rpm
* system-config-cluster-1.0.56-1.0.noarch.rpm
dropit
dropit's intended purpose is to remove directories entries from a
PATH shell variable value, which has colon separated fields.
dropit is usable in sh, ksh, and csh shell script files.
dropit-1.2-1.i386.rpm
FUSE
With FUSE it is possible to implement a fully functional filesystem
in a userspace program.
fuse-smb: you can seamlessly browse your network neighbourhood as if
it were on your own filesystem. Only when you're accessing a share is
a connection made to the remote computer. This also allows users to
mount smb shares using kerberos.
fuse-sshfs: A FUSE-filesystem client based on the
SSH File Transfer Protocol. On the client side mounting the
filesystem is as easy as logging into the server with ssh.
fuse-2.7.3-1.SL.i386.rpm
fuse-devel-2.7.3-1.SL.i386.rpm
fuse-libs-2.7.3-1.SL.i386.rpm
fuse-smb-0.8.7-1.i386.rpm
fuse-sshfs-2.1-1.SL.i386.rpm
* kernel-module-fuse-2.6.9-89.0.3.EL-2.7.3-1.SL.i686.rpm
* kernel-module-fuse-2.6.9-89.0.3.ELhugemem-2.7.3-1.SL.i686.rpm
* kernel-module-fuse-2.6.9-89.0.3.ELsmp-2.7.3-1.SL.i686.rpm
* kernel-module-fuse-2.6.9-89.0.3.ELxenU-2.7.3-1.SL.i686.rpm
icewm
A lightweight window manager for the X Window System.
* icewm-1.2.37-1.i386.rpm
* icewm-l10n-1.2.37-1.i386.rpm
Intel wireless firmware
Firmware for the Intel® PRO/Wireless 2100 and 2200 Driver.
Please read the license that comes in the rpm carefully.
ipw2200-firmware-2.4 includes both version 2.4.xx and 2.2.xx
This is needed because newer kernels have a newer driver that
needs the newer firmware. Older kernels, with older drivers,
need the 2.2 firmware version.
ipw2100-firmware-1.3-5.noarch.rpm
ipw2200-firmware-3.0-1.noarch.rpm
ipw3945d is needed to control the ipw3945 wireless card
kernel-module-ipw3945 is needed because this driver is not in
the standard kernel. Note that the installer does NOT know
how to enable the 3945 wireless. You will have to add the
starting of the /sbin/ipw3945d in your startup scripts.
This driver is known to work on the Dell 820 and Dell 620.
It is known to NOT work on the FJS S7110 (Fujitsu).
ipw3945-firmware-1.13-2.noarch.rpm
ipw3945d-1.7.18-1.i386.rpm
* kernel-module-ipw3945-2.6.9-89.0.3.EL-1.1.0-1.SL4.i686.rpm
* kernel-module-ipw3945-2.6.9-89.0.3.ELhugemem-1.1.0-1.SL4.i686.rpm
* kernel-module-ipw3945-2.6.9-89.0.3.ELsmp-1.1.0-1.SL4.i686.rpm
* kernel-module-ipw3945-2.6.9-89.0.3.ELxenU-1.1.0-1.SL4.i686.rpm
*JAVA
* java-1.6.0-sun-compat-1.6.0.12-1.sl4.jpp.i586.rpm
This package provides JPackage compatibility symlinks and
directories for Sun's JDK rpm.
* jdk-1.6.0_12-fcs.i586.rpm
This packages is the java sdk from sun.
It's license is found at misc/licenses/j2sdk-1.4.2-x.license
To have all of it's links (including plugins) setup correctly you should
also install java-1.5.0-sun-compat
So the easiest thing to do is
yum install java-1.6.0-sun-compat
as it will automatically pull in the current jdk-1.5.0 rpm.
There is no gpg signature on this rpm. Putting one would violate
the user license. It also does not load if one is put on.
ksh
From ATT. Same version as one in SL30x.
ksh93-2000.10.31.0-1.i386.rpm
madwifi
Support for Atheros G wireless
madfifi is the Multiband Atheros Driver for WiFi, a linux device driver
for 802.11a/b/g universal NIC cards - either Cardbus, PCI or MiniPCI -
that use Atheros chipsets (ar5210, ar5211, ar5212).
madwifi-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-2.6.9-89.0.3.EL-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-2.6.9-89.0.3.ELhugemem-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-2.6.9-89.0.3.ELsmp-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-hal-2.6.9-89.0.3.EL-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-hal-2.6.9-89.0.3.ELhugemem-0.9.4-10.sl4.i686.rpm
* kernel-module-madwifi-hal-2.6.9-89.0.3.ELsmp-0.9.4-10.sl4.i686.rpm
multimedia
Updated to latest version
gstreamer-plugins-mp3-0.8.5-1.SL4x.i386.rpm from livna Repository
k3b-mp3-0.11.24-2.SL4x.i386.rpm from livna Repository
mpg321-0.2.10-5.SL.i386.rpm from Dag's Repository
xmms-mp3-1.2.10-11.1.SL.i386.rpm from Dag's Repository
These are dependencies of the above rpms.
lame-3.96.1-4.SL4x.i386.rpm from Dag's Repository
lame-devel-3.96.1-4.SL4x.i386.rpm from Dag's Repository
libid3tag-0.15.1b-3.SL.i386.rpm from Dag's Repository
libid3tag-devel-0.15.1b-3.SL.i386.rpm from Dag's Repository
libmad-0.15.1b-3.SL.i386.rpm from Dag's Repository
libmad-devel-0.15.1b-3.SL.i386.rpm from Dag's Repository
ndiswrapper
The ndiswrapper project makes it possible to use WLAN-Hardware
with Linux by means of a loadable kernel module that "wraps
around" NDIS (Windows network driver API) drivers. These rpms contain
just the kernel module and loader. You will also need the Windows driver
for your card.
The installer does NOT install ndiswrapper, you have to install it by
either selecting it on the Packages Install page during the install or
adding later via yum or apt.
WARNING: Scientific Linux-Kernels use 4K size stack. Many Windows drivers
will need at least 8K size stacks. For details read the wiki on:
http:/ndiswrapper.sourceforge.net
ndiswrapper-1.41-1.SL.i686.rpm
* kernel-module-ndiswrapper-2.6.9-89.0.3.EL-1.41-1.SL.i686.rpm
* kernel-module-ndiswrapper-2.6.9-89.0.3.ELhugemem-1.41-1.SL.i686.rpm
* kernel-module-ndiswrapper-2.6.9-89.0.3.ELsmp-1.41-1.SL.i686.rpm
* kernel-module-ndiswrapper-2.6.9-89.0.3.ELxenU-1.41-1.SL.i686.rpm
NumPy
http://numpy.scipy.org//
NumPy derives from the old Numeric code base and can be used as a
replacement for Numeric. It also adds the features introduced by
Numarray and can also be used to replace Numarray.
This package contains:
- a powerful N-dimensional array object
- sophisticated (broadcasting) functions
- basic linear algebra functions
- basic Fourier transforms
- sophisticated random number capabilities
- tools for integrating Fortran code.
* numpy-1.2.1-1.i386.rpm
OpenAFS
* Upgraded to newer version
new optional packages openafs-authlibs and openafs-authlibs-devel
with shared versions of the afsauthent and afsrpc libraries
(using a patch from Russ Allbery to correct the sonames)
man pages for many commands are now included, preferring those
prepared by Alf Wachsmann and Elizabeth Cassell where available
* openafs-1.4.7-68.2.SL4.i386.rpm
* openafs-authlibs-1.4.7-68.2.SL4.i386.rpm
* openafs-authlibs-devel-1.4.7-68.2.SL4.i386.rpm
* openafs-client-1.4.7-68.2.SL4.i386.rpm
* openafs-compat-1.4.7-68.2.SL4.i386.rpm
* openafs-debug-1.4.7-68.2.SL4.i386.rpm
* openafs-devel-1.4.7-68.2.SL4.i386.rpm
* openafs-kernel-source-1.4.7-68.2.SL4.i386.rpm
* openafs-kpasswd-1.4.7-68.2.SL4.i386.rpm
* openafs-krb5-1.4.7-68.2.SL4.i386.rpm
* openafs-server-1.4.7-68.2.SL4.i386.rpm
* kernel-module-openafs-2.6.9-89.0.3.EL-1.4.7-68.2.SL4.i686.rpm
* kernel-module-openafs-2.6.9-89.0.3.ELhugemem-1.4.7-68.2.SL4.i686.rpm
* kernel-module-openafs-2.6.9-89.0.3.ELsmp-1.4.7-68.2.SL4.i686.rpm
* kernel-module-openafs-2.6.9-89.0.3.ELxenU-1.4.7-68.2.SL4.i686.rpm
Performance Co-Pilot (PCP)
Performance Co-Pilot (PCP) is a framework and services to
support system-level performance monitoring and performance
management. Not installed by default.
pcp-2.4.0-1.1.i386.rpm
These perl modules have been added as they are useful. They came from CERN
perl-BSD-Resource-1.24-1.i386.rpm
perl-Compress-Zlib-1.16-12.i386.rpm
perl-MailTools-1.62-1.noarch.rpm
perl-Parse-RecDescent-1.94-1.noarch.rpm
perl-Proc-ProcessTable-0.39-1.i386.rpm
perl-SQL-Statement-1.06-1.noarch.rpm
perl-TermReadKey-2.20-12.i386.rpm
perl-Text-CSV_XS-0.23-1.i386.rpm
perl-Text-Template-1.44-1.noarch.rpm
perl-Tk-804.027-1.i386.rpm
*R
http://www.r-project.org/
R is a language and environment for statistical computing and graphics.
It is a GNU project which is similar to the S language and environment
which was developed at Bell Laboratories by John Chambers and colleagues.
R can be considered as a different implementation of S. There are some
important differences, but much code written for S runs unaltered under R.
* R-2.9.1-2.sl4.i386.rpm
* R-devel-2.9.1-2.sl4.i386.rpm
* libRmath-2.9.1-2.sl4.i386.rpm
* libRmath-devel-2.9.1-2.sl4.i386.rpm
r1000
This is the Linux device driver released for RealTek Ethernet controllers,
which are listed as following.
1. RTL8169S/SB/SC (Gigabit Ethernet with PCI interface)
2. RTL8168B (Gigabit Ethernet with PCI-Express interface)
3. RTL8101E (Fast Ethernet with PCI-Express interface)
These are not installed by the installer. You must install them either by
selecting them during the install or later with yum or apt.
r1000-2.2-1.SL4x.i686.rpm
* kernel-module-r1000-2.6.9-89.0.3.EL-2.2-2.SL4x.i686.rpm
* kernel-module-r1000-2.6.9-89.0.3.ELhugemem-2.2-2.SL4x.i686.rpm
* kernel-module-r1000-2.6.9-89.0.3.ELsmp-2.2-2.SL4x.i686.rpm
* kernel-module-r1000-2.6.9-89.0.3.ELxenU-2.2-2.SL4x.i686.rpm
SL_afs_no_dynroot-2.0-1.noarch.rpm
This package removes the -dynroot option from the openafs config
Restarting of afs is needed for this to take effect.
This rpm does not restart afs
SL_desktop_tweaks-2.0-4.noarch.rpm
This adds a terminal icon to the kicker panel for both KDE and GNOME.
This also enables 'Last Session' in gdm login screen.
Installed by default for both KDE and GNOME.
SL_disable_print_notification-1.0-4.noarch.rpm
Removes eggcups notification. Not installed by default.
SL_enable_serialconsole-3.1-4.noarch.rpm
This script makes all the changes necessary to send
console output to both the serial port and the screen. This
also creates a login prompt on the serial port and allows users
to login at this prompt.
Update to include a missing dependency.
SL_enable_slocate_cron-1.0-1.noarch.rpm
By default slocate does not run daily, it is turned off in it's
config file. This turns it on when the rpm is added, and
turns it back off when the rpm is removed.
SL_firefox_parentlock_fix-1.0-10.noarch.rpm
When a users home area is in AFS space, it is possible for
firefox, thunderbird, and/or seamonkey to leave a lock file called
.parentlock when they are closed. The user is then not able to
restart firefox, thunderbird, and/or seamonkey until that lock file
is removed. This puts in a startup script that removes the .parentlock
lock file.
SL_inittab_change-1.0-6.noarch.rpm
Changes /etc/inittab to require the root password for
single user mode. Not installed by default.
SL_libg2c.a_change-3.4.3-1.noarch.rpm
Creates a missing symbolic link in the gcc-g77 package from
/usr/lib/libg2c.a to it's proper place
Installed with gcc-g77.
SL_no_colorls-1.0-2.noarch.rpm
Turns off "color" of ls. Not installed by default.
SL_pc_speaker-1.0-1.noarch.rpm
This package changes the rc.sysinit boot script so that
the pcspkr kernel module is loaded at an early stage.
This will allow the PC speaker to beep again.
SL_rpm_show_arch-1.0-1.noarch.rpm
Adds arch to "rpm -qa" listing.
SL_sendmail_accept-1.1-3.noarch.rpm
Changes Sendmail config so that it allows incomming mail.
Not installed by default.
Changed to not obsolete the older zz_sendmail_accept which is
not needed any more
*squashfs
*
* Squashfs is a compressed read-only filesystem for Linux.
*
* squashfs-3.1.2-3.i686.rpm
* kernel-module-squashfs-2.6.9-89.0.3.EL-3.1.2-3.i686.rpm
* kernel-module-squashfs-2.6.9-89.0.3.ELhugemem-3.1.2-3.i686.rpm
* kernel-module-squashfs-2.6.9-89.0.3.ELsmp-3.1.2-3.i686.rpm
* kernel-module-squashfs-2.6.9-89.0.3.ELxenU-3.1.2-3.i686.rpm
tidy
When editing HTML it's easy to make mistakes. Wouldn't it be nice if
there was a simple way to fix these mistakes automatically and tidy up
sloppy editing into nicely formated markup?
Dave Raggett's HTML TIDY is a free utility for doing just that.
It also works great on the atrociously hard to read markup generated
by specialized HTML editors and conversion tools, and can help you
identify where you need to pay further attention on making your i
pages more accessible to people with disabilities.
tidy-2005.9.21-2.sl4.i386.rpm
tidy-devel-2005.9.21-2.sl4.i386.rpm
*unionfs
*
* Unionfs builds a stackable unification file system, which
* can appear to merge the contents of several directories (branches),
* while keeping their physical content separate. Unionfs is useful
* for unified source tree management, merged contents of split
* CD-ROM, merged separate software package directories, data grids,
* and more. Unionfs allows any mix of read-only and read-write
* branches, as well as insertion and deletion of branches anywhere
* in the fan-out.
*
* unionfs-1.1.5-3.i686.rpm
* kernel-module-unionfs-2.6.9-89.0.3.EL-1.1.5-3.i686.rpm
* kernel-module-unionfs-2.6.9-89.0.3.ELsmp-1.1.5-3.i686.rpm
yum
NOTE: That just because a yum repository exists does NOT mean
it is SL 4.4 compatible with all other SL 4.4 yum repositories.
Use of other "packages" such as "smart" may cause the rpm database
to be not compatible with yum.
createrepo is used to create yum repositories on the server for
yum 2.1 and above, and possibly future versions of apt.
yum-conf has the check for a running yum in it, so that if
yum has been running for a long time, when the yum.cron
starts up, it will kill the old yum. This was changed because we
had reports that yum was "hanging".
yum-conf-4.1-4.SL has atrpms, dag, and dries repo's in it, but they
are not enabled by default. To enable them for one time use, use the
--enablerepo command, such as
yum --enablerepo=atrpms list madwifi
yum --enablerepo=dag install mplayer
If you want the repositories to be enabled all the time then you need
to edit the config files and change enabled=0 to enabled=1.
The config files are
/etc/yum.repos.d/atrpms.repo
/etc/yum.repos.d/dag.repo
/etc/yum.repos.d/dries.repo
Yum version 2.4 and above has the kernel-module plugin that let's yum
understand how kernel-module rpm's are related to kernels. Because of
this updates dealing with kernel-module rpm's (such as afs) now work
python-elementtree, python-sqlite, sqlite, and urlgrabber are all
needed for yum 2.4 and above.
New for yum-conf-4.3: a sl-testing area (not on by default)
and yum.cron now checks to see how long the machine is been up
If it is up less than 20 hours, it doesn't wait, but does the update
This uptime check was done to help laptops and other machines that
might not be on long enough to wait for the random time.
metadata_expire variable was set to 20 hours to allow for normal users
to be able to use yum for those commands they can run
There is a fastbug repo area to correspond to the vendors fasttrack
This is not on by default.
yum-conf-4x was created for those users who want to be at the latest
stable release. It is always pointing at the 4x area. This means
that when we make new versions you will automatically be upgraded to
them.
We have changed flash.repo to be adobe.repo
adobe.repo now points to the repository at linuxdownload.adobe.com
* yum-2.4.3-10.SL.noarch.rpm
* yum-conf-48-1.SL.noarch.rpm
yum-conf-4x-1-7.SL.noarch.rpm
createrepo-0.4.4-1.noarch.rpm
* yum-versionfix-1.0-10.sl4.noarch.rpm
python-elementtree-1.2.6-4.i386.rpm
python-sqlite-1.1.6-1.i386.rpm
sqlite-3.1.2-3.i386.rpm
sqlite-devel-3.1.2-3.i386.rpm
urlgrabber-2.9.6-1.noarch.rpm
Yumex is a graphical user interface for yum.
Yumex-applet replaces rhn-applet, and users yumex instead of up2date
Yumex 0.43 and above support plugins
yumex-1.0.2-1.0.noarch.rpm
yumex-applet-2.1-2.i386.rpm
yum-utils is a collection of utilities and examples for the yum
package manager. It includes utilities by different authors that
make yum easier and more powerful to use. Some utilities are
plugin's.
yum-utils-0.6-1.SL.noarch.rpm
yum-changelog-0.6-1.SL.noarch.rpm
yum-downloadonly-0.6-1.SL.noarch.rpm
yum-fastestmirror-0.6-1.SL.noarch.rpm
yum-installonlyn-0.6-1.SL.noarch.rpm
yum-protectbase-0.6-1.SL.noarch.rpm
yum-tsflags-0.6-1.SL.noarch.rpm
yum-updateonboot-0.6-1.SL.noarch.rpm
yum-versionlock-0.6-1.SL.noarch.rpm
MISC
Added these rpms because they are important but upstream vendor did
not include them.
pine was replaced by alpine
gv-3.5.8-29.i386.rpm from Fedora Core 3
jpilot-0.99.8-7.1.i386.rpm from Scientific Linux 5.x
ncurses4-5.0-12.i386.rpm from Scientific Linux 3.0.x
readline41-4.1-17.i386.rpm from Scientific Linux 3.0.x
Documentation
rhd-dg-en-4-2.SL1.noarch.rpmi Desktop Deployment Guide
rhel-ig-x8664-multi-en-4-3.SL1.noarch.rpm Installation Guide
rhel-isa-en-4-3.SL1.noarch.rpm Intro System Admin Guide
rhel-rg-en-4-3.SL1.noarch.rpm Reference Guide
rhel-sag-en-4-3.SL1.noarch.rpm System Administrator Guide
rhel-sbs-en-4-1.SL1.noarch.rpm Step-by-Step Guide
rhel-selg-en-4-1.SL1.noarch.rpm SElinux Guide
rhel-sg-en-4-3.SL1.noarch.rpm Security Guide
rh-glossary-en-2-1.SL1.noarch.rpm Glossary
-------------------------------------------------------------------------
UPDATED compared to vendor
-------------------------------------------------------------------------
*anaconda(installer)
Added support for sites
Added support for openafs on smp
Added support for openafs on xen
Updated icons
* anaconda-10.1.1.103-1SL.i386.rpm
anaconda-help-10.0.5-1SL1.noarch.rpm
* anaconda-runtime-10.1.1.103-1SL.i386.rpm
Vendor "logo" and other required changes
There are minimal changes compared to the "vendor" release. We have changed
the "rpms" that are required to be changed. These changes are defined
by the "vendor".
sl-release has been determined to be the place to change several
global properties. This is how fedora does it.
sl-release changes the default mozilla and firefox bookmarks.
sl-release changes the default up2date configuration to use yum and
points this configuration to ftp.scientificlinux.org
Fixes /etc/redhat-release containing "Release" vs "release"
Includes SL.releasenote
Changes grub to put in the new release name for the default kernel
indexhtml-4.1-1.SL.1.noarch.rpm
redhat-artwork-0.120.1-1.2SL.2.i386.rpm
redhat-logos-1.1.25-1.SL.8.noarch.rpm
* sl-release-4.8-1.noarch.rpm
These rpm's are not required to be changed by the vendor, we removed
some vendor references customizations
desktop-backgrounds-basic-2.0-26.2.3SL.noarch.rpm
desktop-backgrounds-extra-2.0-26.2.3SL.noarch.rpm
*comps-48-0.*.i386.rpm
RPM which contains the comps.xml file used during the install.
Needed by Rocks.
The comps.xml file got a update with SL 4.7.
All groups are now alphabetical
Groups that are completely commented out have been removed.
Where available, I have updated the international group name and
description to be the same as Update 7
Except for where I have specifically added or removed a package
or default setting, I have updated the groups to be the same as Update 7
Most changes were minor, but the following were noteworthy
- audit is now optional in the core group
- development-tools now includes the group emacs and xemacs
* The comps.xml file got a update with SL 4.8.
* Group - Cluster Suite - Updated to match Vendors
* Group - compat-arch-support - Updated to match Vendors
* Group - openfabrics-enterprise-distribution - Updated to match Vendors
* Group - compat-arch-development - Updated to match Vendors
* Group - editors - Fixed vim-X11 entry
* Group - yum - added optional yum-utils and various yum plugins
glade2-2.6.0-1.SL4.i386.rpm
glade2 has an bug so that all you got was a blank window when it started.
This was an infinate loop bug, which was fixed.
Apache
Changed index.html to not have Upstream Vendor info but to
have SL info.
* httpd-2.0.52-41.sl4.2.i386.rpm
* httpd-devel-2.0.52-41.sl4.2.i386.rpm
* httpd-manual-2.0.52-41.sl4.2.i386.rpm
* httpd-suexec-2.0.52-41.sl4.2.i386.rpm
* mod_ssl-2.0.52-41.sl4.2.i386.rpm
-------------------------------------------------------------------------
ADDED BY UPSTREAM VENDOR
-------------------------------------------------------------------------
*Added as part of Update 8
*
* mpitests-mvapich2-3.1-1.sl4.i386.rpm
* mpitests-mvapich-3.1-1.sl4.i386.rpm
* mpitests-openmpi-3.1-1.sl4.i386.rpm
* mvapich-1.1.0-0.3143.4.el4.i386.rpm
* mvapich2-1.2-0.p1.4.el4.i386.rpm
* nss-tools-3.12.2.0-4.el4.i386.rpm
* openmpi11-1.1.5-7.el4.i386.rpm
* uuidd-1.35-12.24.el4.i386.rpm
Added as part of Update 5
dapl-1.2.1-7.i386.rpm
dapl-devel-1.2.1-7.i386.rpm
ibutils-1.0-4.i386.rpm
dmraid-1.0.0.rc14-5_RHEL4_U5.i386.rpm
dmraid-devel-1.0.0.rc14-5_RHEL4_U5.i386.rpm
ibutils-devel-1.0-4.i386.rpm
ibutils-libs-1.0-4.i386.rpm
kernel-xenU-2.6.9-55.EL.i686.rpm
kernel-xenU-devel-2.6.9-55.EL.i686.rpm
lam-7.1.2-8.i386.rpm
lam-devel-7.1.2-8.i386.rpm
lam-libs-7.1.2-8.i386.rpm
libacl-devel-2.2.23-5.3.el4.i386.rpm
libibcm-0.9.1-7.i386.rpm
libibcm-devel-0.9.1-7.i386.rpm
libibcommon-1.0.1-7.i386.rpm
libibcommon-devel-1.0.1-7.i386.rpm
libibmad-1.0.1-7.i386.rpm
libibmad-devel-1.0.1-7.i386.rpm
libibumad-1.0.1-7.i386.rpm
libibumad-devel-1.0.1-7.i386.rpm
libibverbs-1.0.4-7.i386.rpm
libibverbs-devel-1.0.4-7.i386.rpm
libibverbs-utils-1.0.4-7.i386.rpm
libmthca-1.0.3.1-7.i386.rpm
libmthca-devel-1.0.3.1-7.i386.rpm
librdmacm-devel-0.9.1-7.i386.rpm
librdmacm-utils-0.9.1-7.i386.rpm
libsdp-1.1.0-7.i386.rpm
numactl-0.6.4-1.39.i386.rpm
openib-1.1-7.i386.rpm
openib-mstflint-1.0.1-7.i386.rpm
openib-perftest-1.0.1-7.i386.rpm
openib-srptools-0.0.5-7.i386.rpm
openib-tvflash-0.9.1-7.i386.rpm
openmpi-1.1.1-8.i386.rpm
openmpi-devel-1.1.1-8.i386.rpm
openmpi-libs-1.1.1-8.i386.rpm
opensm-2.0.0-7.i386.rpm
opensm-devel-2.0.0-7.i386.rpm
opensm-libs-2.0.0-7.i386.rpm
pam_ccreds-3-3.rhel4.2.i386.rpm
setools-devel-2.3-4.i386.rpm
sg3_utils-devel-1.22-3.1.i386.rpm
sg3_utils-libs-1.22-3.1.i386.rpm
sysfsutils-1.2.0-1.i386.rpm
systemtap-runtime-0.5.12-1.i386.rpm
wpa_supplicant-0.4.9-1.1.el4.i386.rpm
Added as part of Update 4
dapl-1.2.0-1.i386.rpm
dapl-devel-1.2.0-1.i386.rpm
dmraid-devel-1.0.0.rc11-3_RHEL4_U4.i386.rpm
ibmasm-3.0-7.i386.rpm
kernel-ib-1.0-1.i386.rpm
libgomp-4.1.0-18.EL4.i386.rpm
libgssapi-0.8-1.i386.rpm
libgssapi-devel-0.8-1.i386.rpm
libibcm-0.9.0-1.i386.rpm
libibcommon-1.0-1.i386.rpm
libibcommon-devel-1.0-1.i386.rpm
libibmad-1.0-1.i386.rpm
libibmad-devel-1.0-1.i386.rpm
libibumad-1.0-1.i386.rpm
libibumad-devel-1.0-1.i386.rpm
librdmacm-0.9.0-1.i386.rpm
mstflint-1.0-1.i386.rpm
nfs-utils-lib-1.0.6-3.i386.rpm
nfs-utils-lib-devel-1.0.6-3.i386.rpm
oddjob-0.26-1.1.i386.rpm
oddjob-devel-0.26-1.1.i386.rpm
oddjob-libs-0.26-1.1.i386.rpm
openib-diags-1.0-1.i386.rpm
perftest-1.0-1.i386.rpm
sblim-cmpi-base-1.5.4-12.EL4.i386.rpm
sblim-cmpi-base-devel-1.5.4-12.EL4.i386.rpm
sblim-cmpi-base-test-1.5.4-12.EL4.i386.rpm
sblim-cmpi-devel-1.0.4-12.EL4.i386.rpm
sblim-cmpi-fsvol-1.4.3-12.EL4.i386.rpm
sblim-cmpi-fsvol-devel-1.4.3-12.EL4.i386.rpm
sblim-cmpi-fsvol-test-1.4.3-12.EL4.i386.rpm
sblim-cmpi-network-1.3.7-12.EL4.i386.rpm
sblim-cmpi-network-devel-1.3.7-12.EL4.i386.rpm
sblim-cmpi-network-test-1.3.7-12.EL4.i386.rpm
sblim-cmpi-nfsv3-1.0.13-12.EL4.i386.rpm
sblim-cmpi-nfsv3-test-1.0.13-12.EL4.i386.rpm
sblim-cmpi-nfsv4-1.0.11-12.EL4.i386.rpm
sblim-cmpi-nfsv4-test-1.0.11-12.EL4.i386.rpm
sblim-cmpi-params-1.2.4-12.EL4.i386.rpm
sblim-cmpi-params-test-1.2.4-12.EL4.i386.rpm
sblim-cmpi-sysfs-1.1.8-12.EL4.i386.rpm
sblim-cmpi-sysfs-test-1.1.8-12.EL4.i386.rpm
sblim-cmpi-syslog-0.7.9-12.EL4.i386.rpm
sblim-cmpi-syslog-test-0.7.9-12.EL4.i386.rpm
sblim-gather-2.1.1-12.EL4.i386.rpm
sblim-gather-devel-2.1.1-12.EL4.i386.rpm
sblim-gather-provider-2.1.1-12.EL4.i386.rpm
sblim-gather-test-2.1.1-12.EL4.i386.rpm
sblim-testsuite-1.2.4-12.EL4.i386.rpm
sblim-wbemcli-1.5.1-12.EL4.i386.rpm
srptools-0.0.4-1.i386.rpm
tog-pegasus-test-2.5.1-2.EL4.i386.rpm
tvflash-0.9.0-1.i386.rpm
Added as part of Update 3
frysk-0.0.1.2006.02.19.rh1-0.EL4.1.i386.rpm
keyutils-1.0-2.i386.rpm
keyutils-devel-1.0-2.i386.rpm
keyutils-libs-1.0-2.i386.rpm
libibverbs-1.0.rc4-0.4265.2.EL4.i386.rpm
libibverbs-devel-1.0.rc4-0.4265.2.EL4.i386.rpm
libibverbs-utils-1.0.rc4-0.4265.2.EL4.i386.rpm
libmthca-1.0.rc4-0.4265.2.EL4.i386.rpm
libmthca-devel-1.0.rc4-0.4265.2.EL4.i386.rpm
libsdp-0.90-0.4265.2.EL4.i386.rpm
opensm-1.0-0.4265.2.EL4.i386.rpm
opensm-devel-1.0-0.4265.2.EL4.i386.rpm
opensm-libs-1.0-0.4265.2.EL4.i386.rpm
rarpd-ss981107-18.40.2.i386.rpm
udapl-1.2-0.4265.2.EL4.i386.rpm
udapl-devel-1.2-0.4265.2.EL4.i386.rpm
Added as part of Update 2
audit-libs-1.0.3-6.EL4.i386.rpm
audit-libs-devel-1.0.3-6.EL4.i386.rpm
amtu-1.0.2-2.EL4.i386.rpm
convmv-1.08-3.EL.noarch.rpm
device-mapper-multipath-0.4.5-6.0.RHEL4.i386.rpm
gamin-python-0.1.1-3.EL4.i386.rpm
iscsi-initiator-utils-4.0.3.0-2.i386.rpm
keyutils-0.3-1.i386.rpm
keyutils-devel-0.3-1.i386.rpm
lksctp-tools-1.0.2-6.4E.1.i386.rpm
lksctp-tools-devel-1.0.2-6.4E.1.i386.rpm
lksctp-tools-doc-1.0.2-6.4E.1.i386.rpm
OpenIPMI-1.4.14-1.4E.7.i386.rpm
OpenIPMI-devel-1.4.14-1.4E.7.i386.rpm
OpenIPMI-libs-1.4.14-1.4E.7.i386.rpm
OpenIPMI-tools-1.4.14-1.4E.7.i386.rpm
systemtap-0.4-0.EL4.i386.rpm
tog-pegasus-2.4.1-4.4.rhel4.i386.rpm
tog-pegasus-devel-2.4.1-4.4.rhel4.i386.rpm
gcc4-java-4.0.1-4.EL4.2.i386.rpm
libgcj4-4.0.1-4.EL4.2.i386.rpm
libgcj4-devel-4.0.1-4.EL4.2.i386.rpm
libgcj4-src-4.0.1-4.EL4.2.i386.rpm
-----------------------------------------------------------------------------
REMOVED by Upstream Vendor
-----------------------------------------------------------------------------
Removed as part of Update 8
* modversions-1.0-4.el4_6.1.x86_64.rpm
-----------------------------------------------------------------------------
TECHNOLOGY PREVIEW by vendor
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
/contrib
-----------------------------------------------------------------------------
RPMS provided by colaboraters that either cannot go in main release or are
intesting before going into main release.
/contrib/RPMS/
/contrib/SRPMS/
-----------------------------------------------------------------------------
/errata/
-----------------------------------------------------------------------------
SL/RPMS/
Security errata
fastbugs/RPMS/
Packages rebuilt from the Upstream Vendor Fastrack rpms
These are rpms that are expected to be in the next Update
They have gone through full QA by the Upstream Vendor
bugfix45/RPMS/
Reserved for packages from the next Update.
obsolete/RPMS/
Packages that used to be in the release but have been
updated
---------------------------------------------------------------------------
/../SRPMS/
---------------------------------------------------------------------------
/
Contains the SRPMS for what we added or changed. Put these in the
top level directory as these are really the ones we changed. All
the others can be obtained from the upstream vendor ftp updates area
/vendor/
/errata
SRPMS from vendor for errata.
/original
SRPMS from vendor for originally released Enterpise 4 .
sites/<sites>/SRPMS
SRPMS for site if there is a site
-----------------------------------------------------------------------------
LIMITATIONS
-----------------------------------------------------------------------------
Virtulization
Scientific Linux 4.5 can *not* be a xen host, only a guest.
Scientific Linux 4.5 and above have a xen kernel. This allows them
to be installed as a xen paravirtulizaed guest. Follow the Virtual Host's
instructions for installing a paravirtulizaed guest, to install
Scientific Linux 4.5 as a xen guest.
Paravirtualizaed guests on Scientific Linux 5.0
This is a limitation of Scientific Linux 5.0, but affects installing
Scientific Linux 4.5 as a paravirtulized guest. These limitations will
hopefully be fixed in Scientific Linux 5.1 or 5.2
- 32 bit (i386) paravirtualized guests cannot run on a
64 bit (x86_64) host (dom0). It will fail.
- 64 bit (x86_64) paravirtualized guests cannot run on a
32 bit (i386) host (dom0). It will fail.
Fully Virtualizaed guests on Scientific Linux 5.0
This is a limitation of Scientific Linux 5.0, but affects installing
Scientific Linux 4.5 as a fully virtulized guest.
- 64 bit fully-virtulizaed guests cannot run on a
32 bit (i386) host (dom0). It will fail.
system-config-packages add,remove packages
This does NOT work use yum instead.
up2date
up2date is not supported in Scientific Linux.
Please use yum instead.
ipw3945
Does not work in the installer and does not work on some laptops.
3ware 8xxx and 9xxx in same system
Grub can get confused about which "drives" are which if both
of these cards are installed. You can either run grub manually
before rebooting or use "noprobe" during the install and install
only the 3ware driver for the card that you will be booting off of.
-----------------------------------------------------------------------------
INFO
-----------------------------------------------------------------------------
Web Site
https://www.scientificlinux.org
FTP
ftp://ftp.scientificlinux.org/linux/scientific/40rolling/
Mailing Lists
[log in to unmask] Development of Scientific Linux
[log in to unmask] Users of Scientific Linux supporting
each other
[log in to unmask] Announcements concerning Scientific Linux
[log in to unmask] Announcements about Security Errata
-------------------------------------------------------------------------
ERRATA rebuilt from SRPMS
-------------------------------------------------------------------------
* kdelibs-3.3.1-14.el4.i386.rpm
* kdelibs-devel-3.3.1-14.el4.i386.rpm
* lvm2-2.02.42-5.el4_8.2.i386.rpm
* thunderbird-1.5.0.12-23.el4.i386.rpm
* kernel-2.6.9-89.0.3.EL.i686.rpm
* kernel-devel-2.6.9-89.0.3.EL.i686.rpm
* kernel-doc-2.6.9-89.0.3.EL.noarch.rpm
* kernel-hugemem-2.6.9-89.0.3.EL.i686.rpm
* kernel-hugemem-devel-2.6.9-89.0.3.EL.i686.rpm
* kernel-smp-2.6.9-89.0.3.EL.i686.rpm
* kernel-smp-devel-2.6.9-89.0.3.EL.i686.rpm
* kernel-xenU-2.6.9-89.0.3.EL.i686.rpm
* kernel-xenU-devel-2.6.9-89.0.3.EL.i686.rpm
* seamonkey-1.0.9-44.el4_8.i386.rpm
* seamonkey-chat-1.0.9-44.el4_8.i386.rpm
* seamonkey-devel-1.0.9-44.el4_8.i386.rpm
* seamonkey-dom-inspector-1.0.9-44.el4_8.i386.rpm
* seamonkey-js-debugger-1.0.9-44.el4_8.i386.rpm
* seamonkey-mail-1.0.9-44.el4_8.i386.rpm
* finch-2.5.8-1.el4.i386.rpm
* finch-devel-2.5.8-1.el4.i386.rpm
* irb-1.8.1-7.el4_8.3.i386.rpm
* libpurple-2.5.8-1.el4.i386.rpm
* libpurple-devel-2.5.8-1.el4.i386.rpm
* libpurple-perl-2.5.8-1.el4.i386.rpm
* libpurple-tcl-2.5.8-1.el4.i386.rpm
* pidgin-2.5.8-1.el4.i386.rpm
* pidgin-devel-2.5.8-1.el4.i386.rpm
* pidgin-perl-2.5.8-1.el4.i386.rpm
* ruby-1.8.1-7.el4_8.3.i386.rpm
* ruby-devel-1.8.1-7.el4_8.3.i386.rpm
* ruby-docs-1.8.1-7.el4_8.3.i386.rpm
* ruby-libs-1.8.1-7.el4_8.3.i386.rpm
* ruby-mode-1.8.1-7.el4_8.3.i386.rpm
* ruby-tcltk-1.8.1-7.el4_8.3.i386.rpm
* dhclient-3.0.1-65.el4_8.1.i386.rpm
* dhcp-3.0.1-65.el4_8.1.i386.rpm
* dhcp-devel-3.0.1-65.el4_8.1.i386.rpm
* rsh-0.17-25.4.1.i386.rpm
* rsh-server-0.17-25.4.1.i386.rpm
* libtiff-3.6.1-12.el4_8.4.i386.rpm
* libtiff-devel-3.6.1-12.el4_8.4.i386.rpm
* firefox-3.0.12-1.el4.i386.rpm
* seamonkey-1.0.9-45.el4_8.i386.rpm
* seamonkey-chat-1.0.9-45.el4_8.i386.rpm
* seamonkey-devel-1.0.9-45.el4_8.i386.rpm
* seamonkey-dom-inspector-1.0.9-45.el4_8.i386.rpm
* seamonkey-js-debugger-1.0.9-45.el4_8.i386.rpm
* seamonkey-mail-1.0.9-45.el4_8.i386.rpm
Copyright © 2009 Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at
[1]http://www.opencontent.org/openpub/.
--------------------------------------------------------------------------
Introduction
The following topics are covered in this document:
o Installation-Related Notes
o Feature Updates
o Kernel-Related Updates
o Driver Updates
o Technology Previews
o Resolved Issues
o Known Issues
Some updates on Red Hat Enterprise Linux 4.8 may not appear in this
version of the Release Notes. An updated version of the Red Hat Enterprise
Linux 4.8 Release Notes may also be available at the following URL:
[2]http://www.redhat.com/docs/manuals/enterprise/
Lifecycle
The Red Hat Enterprise Linux 4 Life Cycle is available at:
[3]https://www.redhat.com/security/updates/errata/
As previously announced, the release of Red Hat Enterprise Linux 4.8 will
mark the beginning of Production 2 phase of the Red Hat Enterprise Linux
4. No new hardware enablement will be expected during this phase.
[4]https://www.redhat.com/archives/nahant-list/2008-July/msg00059.html
Customers should note that their subscriptions provide access to all
currently supported versions of Red Hat Enterprise Linux.
Installation-Related Notes
The following section includes information specific to installation of Red
Hat Enterprise Linux and the Anaconda installation program.
Note
When updating from one minor version of Red Hat Enterprise Linux 4 (such
as 4.6 to 4.7) to Red Hat Enterprise Linux 4.8, it is recommended that you
do so using Red Hat Network, whether through the hosted web user interface
or Red Hat Network Satellite.
If you are upgrading a system with no available network connectivity, use
the "Upgrade" functionality of Anaconda. However, note that Anaconda has
limited abilities to handle issues such as dependencies on additional
repositories or third-party applications. Further, Anaconda reports
installation errors in a log file, not interactively.
As such, Red Hat recommends that when upgrading offline systems, you
should test and verify the integrity of your upgrade configuration first.
Be sure to carefully review the update log for errors before applying the
upgrade to your production environment.
In-place upgrades between major versions of Red Hat Enterprise Linux (for
example, upgrading from Red Hat Enterprise Linux 3 to Red Hat Enterprise
Linux 4.8) is not supported. While the "Upgrade" option of Anaconda allows
you to perform this, there is no guarantee that the upgrade will result in
a working installation. In-place upgrades accross major releases do not
preserve all system settings, services, and custom configurations. For
this reason, Red Hat strongly recommends that you perform a fresh
installation when planning to upgrade between major versions.
o If you are copying the contents of the Red Hat Enterprise Linux 4.8
CD-ROMs (in preparation for a network-based installation, for example)
be sure you copy the CD-ROMs for the operating system only. Do not
copy the Supplementary CD-ROM, or any of the layered product CD-ROMs,
as this will overwrite files necessary for Anaconda's proper
operation.
These CD-ROMs must be installed after Red Hat Enterprise Linux is
installed.
o The version of GRUB shipped with Red Hat Enterprise Linux 4 (and all
updates) does not support software mirroring (RAID1). As such, if you
install Red Hat Enterprise Linux 4 on a RAID1 partition, the
bootloader will be installed in the first hard drive instead of the
master boot record (MBR). This will render the system unbootable.
If you wish to install Red Hat Enterprise Linux 4 on a RAID1
partition, you should clear any pre-existing bootloader from the MBR
first.
o When installing Red Hat Enterprise Linux 4 in Text Mode on systems
that use flat-panel monitors and some ATI cards, the screen area may
appear shifted. When this occurs, some areas of the screen will be
obscured.
If this occurs, perform the installation with the parameter linux
nofb.
o When upgrading from Red Hat Enterprise Linux 4.6 to this release,
minilogd may log several SELinux denials. These error logs are
harmless, and can be safely ignored.
o Previously, in the Anaconda kickstart documentation (located at:
/usr/share/doc/anaconda-<anaconda-version>/kickstart-docs.txt), the
section detailing the --driveorder option in a kickstart file stated:
Specify which drive is first in the BIOS boot order.
However, the --driveorder option actually requires a list of all
drives on the system, with the first boot device appearing first in
the list. With this update, the documentation has been clarified and
now reads:
Specify which drive is first in the BIOS boot order.
The ordered list must include all the drives in the system.
When using the --driveorder option in a kickstart file The ordered
list must include all the drives in the system.
Feature Updates
o Systemtap is now a fully supported feature in Red Hat Enterprise Linux
4. systemtap provides a free software (GPL) infrastructure to simplify
the gathering of information about the running Linux system. This
assists diagnosis of a performance or functional problem. With the
help of systemtap, developers no longer need to go through the tedious
and disruptive sequence of instrument, recompile, install, and reboot
that may be otherwise required to collect data.
Note that some features of systemtap for newer Red Hat Enterprise
Linux or Linux systems will not work on Red Hat Enterprise Linux 4 due
to missing kernel features. The absence of the kernel utrace precludes
support for any user-space probing.
o dmidecode gives information about BIOSes and motherboard revisions.
The version of kernel-utils supplied with this advisory updates
dmidecode from version 2.2 to version 2.9. This version identifies
newer processors, PCI-express slots and devices, and blade chassis. It
also offers enhanced support for the SMBIOS v2.6 specification.
o a new version of kernel-utils is included in this release, updating
the Intel microcode file to version 20080910, to support newer Intel
processors.
o smartmontools has been extended to support newer CCISS controllers
found in newer HP ProLiant hardware.
o The Samba package has been rebased to the upstream version 3.0.33. The
3.0.x version series is a bugfix only branch of the Samba code base.
By rebasing to 3.0.33 we will include a number of important bug fixes
and security fixes. No new features will be added by this rebase.
For more information on the upstream fixes provided by this rebase,
refer to the Samba Release Notes:
[5]http://samba.org/samba/history/samba-3.0.33.html
o ipmitool has been updated to the upstream version 1.8.11, which
provides several bug fixes and enhancements over the previous release,
including the following:
o Documentation update
o Bugfixes for SDR/FRU, SOL and many others
o New commands and options
Please note that behaviour of the -K command line switch has changed
from prompt for Kg key to read Kg key from environment variable. The
-Y flag now behaves as the -K did prior to this update.
Kernel-Related Updates
o The ibmphp module is not safe to unload. Previously, the mechanism
that prevented the ibmphp module from unloading was insufficient, and
eventually triggered a bug halt. With this update, the method to
prevent this module from unloading has been improved, preventing the
bug halt. However, attempting to unload the module may produce a
warning in the message log, indicating that the module is not safe to
unload. This warning can be safely ignored.
o With this update, physical memory will be limited to 64GB for 32-bit
x86 kernels running on systems with more than 64GB. The kernel splits
memory into 2 separate regions: Lowmem and Highmem. Lowmem is mapped
into the kernel address space at all times. Highmem, however, is
mapped into a kernel virtual window a page at a time as needed. If
memory I/Os are allowed to exceed 64GB, the mem_map (also known as the
page array) size can approach or even exceed the size of Lowmem. If
this happens, the kernel panics during boot or starts prematurely. In
the latter case, the kernel fails to allocate kernel memory after
booting and either panics or hangs.
o Previously, if a user pressed the arrow keys continously on a Hardware
Virtual Machine (HVM) an interrupt race condition between the hardware
interrupt and timer interrupt was encountered. As a result, the
keyboard driver reported unknown keycode events. With this update, the
i8042 polling timer has been removed, which resolves this issue.
o With this update, the diskdump utility (which provides the ability to
create and collect vmcore Kernel dumps) is now supported for use with
the sata_svw driver.
o With this update, the "swap_token_timeout" parameter has been added to
/proc/sys/vm.
This file contains valid hold time of swap out protection token. The
Linux Virtual Memory (VM) subsystem has a token based thrashing
control mechanism and uses the token to prevent unnecessary page
faults in thrashing situation. The unit of the value is in `second`.
The value would be useful to tune thrashing behavior. Setting it to 0
will disable the swap token mechanism.
o Previously, when a NFSv4 (Network File System Version 4) client
encountered issues while processing a directory using readdir(), an
error for the entire readdir() call was returned. With this update,
the fattr4_rdattr_error flag is now set when readdir() is called,
instructing the server to continue on and only report an error on the
specific directory entry that was causing the issue.
o Previously, the NFS (Network File System) client was not handling
malformed replies from the readdir() function. Consequently, the reply
from the server would indicate that the call to the readdir() function
was successful, but the reply would contain no entries. With this
update, the readdir() reply parsing logic has been changed, such that
when a malformed reply is received, the client returns an EIO error.
o The RPC client stores the result of a portmap call at a place in
memory that can be freed and reallocated under the right
circumstances. However, under some circumstances, the result of the
portmap call was freed from memory too early, which may have resulted
in memory corruption. With this update, reference counting has been
added to the memory location where the portmap result is stored, and
will only free it after it has been used.
o Under some circumstances, the allocation of some data structures for
RPC calls may have been blocked when the system memory was low.
Consequently, deadlock may have been encountered under heavy memory
pressure when there were a large number of NFS pages awaiting
writeback. With this update, the allocation of these data structures
is now non-blocking, which resolves this issue.
o Previously, degraded performance may have been encountered when
writing to a LVM mirrored volume synchronously (using the O_SYNC
flag). Consequently, every write I/O to a mirrored volume was delayed
by 3ms, resulting in the mirrored volume being approximately 5-10
times slower than a linear volume. With this update, I/O queue
unplugging has been added to the dm-raid1 driver, and the performace
of mirrored volumes has been improved to be comparable with that of
linear volumes.
o A new tuning parameter has been added to allow system administrators
to change the max number of modified pages kupdate writes to disk per
iteration each time it runs. This new tunable
(/proc/sys/vm/max_writeback_pages) defaults to a value of 1024 (4MB)
so that a maximum of 1024 pages get written out by each iteration of
kupdate. Increasing this value alters how aggressively kupdate flushes
modified pages and decreases the potential amount of data loss if the
system crashes between kupdate runs. However, increasing the
max_writeback_pages value may have negative performance consequences
on systems that are sensitive to I/O loads.
o A new allowable value has been added to the
/proc/sys/kernel/wake_balance tunable parameter. Setting wake_balance
to a value of 2 will instruct the scheduler to run the thread on any
available CPU rather than scheduling it on the optimal CPU. Setting
this kernel parameter to 2 will force the scheduler to reduce the
overall latency even at the cost of total system throughput.
o When checking a directory tree, the kernel module could, in some
circumstances, incorrectly decide the tree was not busy. An active
offset mount with an open file handle being used for expires caused
the file handle to not count toward the busyness check. This resulted
in mount requests being made for already mounted offsets. With this
update, the kernel module check has been corrected and incorrect mount
requests are no longer generated.
o During system initalization, the CPU vendor was detected after the
initialization of the Advanced Programmable Interrupt Controllers
(APICs). Consequently, on x86_64 AMD systems with more than 8 cores,
APIC clustered mode was used, resulting in suboptimal system
performance. With this update, the CPU vendor is now queried prior to
initializing the APICs, resulting in APIC physical flat mode being
used by default, which resolves this issue.
o The Common Internet File System (CIFS) code has been updated in Red
Hat Enterprise Linux 4.8, fixing a number of bugs that had been
repaired in upstream, including the following change:
Previously, when mounting a server without Unix extensions, it was
possible to change the mode of a file. However, this mode change could
not be permanently stored, and may have changed back to the original
mode at any time. With this update, the mode of the file cannot be
temporarily changed by default; chmod() calls will return success, but
have no effect. A new mount option, dynperm needs to be used if the
old behavior is required.
o Previously, in the kernel, there was a race condition may have been
encountered between dio_bio_end_aio() and dio_await_one(). This may
have lead to a situation where direct I/O is left waiting indefinitely
on an I/O process that has already completed. With this update, these
reference counting operations are now locked so that the submission
and completion paths see a unified state, which resolves this issue.
o Previously, upgrading a fully virtualized guest system from Red Hat
Enterprise Linux 4.6 (with the kmod-xenpv package installed) to newer
versions of Red Hat Enterprise Linux 4 resulted in an improper module
dependency between the built-in kernel modules: xen-vbd.ko &
xen-vnif.ko and the older xen-platform-pci.ko module. Consequently,
file systems mounted via the xen-vbd.ko block driver, and guest
networking using the xen-vnif.ko network driver would fail.
In Red Hat Enterprise Linux 4.7, the functionality in the
xen-platform-pci.ko module was built-in to the kernel. However, when a
formally loadable kernel module becomes a part of the kernel, the
symbol dependency check for existing loadable modules is not accounted
for in the module-init-tools correctly. With this update, the
xen-platform-pci.ko functionality has been removed from the built-in
kernel and placed back into a loadable module, allowing the
module-init-tools to check and create the proper dependencies during a
kernel upgrade.
o Previously, attempting to mount disks or partitions in a 32-bit Red
Hat Enterprise Linux 4.6 fully virtualized guest using the
paravirtualized block driver(xen-vbd.ko) on a 64-bit host would fail.
With this update, the block front driver (block.c) has been updated to
inform the block back driver that the guest is using the 32-bit
protocol, which resolves this issue.
o Previously, installing the pv-on-hvm drivers on a bare-metal kernel
automatically created the /proc/xen directory. Consequently,
applications that verify if the system is running a virtualized kernel
by checking for the existence of the /proc/xen directory may have
incorrectly assumed that the virtualized kernel is being used. With
this update, the pv-on-hvm drivers no longer create the /proc/xen
directory, which resolves this issue.
o Previously, paravirtualized guests could only have a maximum of 16
disk devices. In this update, this limit has been increased to a
maximum of 256 disk devices.
Driver Updates
o The Intel® High Definition Audio (HDA) driver in ALSA has been
updated. This update improves audio support for newer hardware with
HDA integrated audio.
o Previously, network devices using the forcedeth driver may have
stopped responding while doing rcp command from multiple clients. With
this update, the forcedeth driver has been updated, which resolves
this issue.
o Previously, the Automatic Direct Memory Access (ADMA) mode was enabled
by default in the sata_nv driver. Consequently, device errors and
timeouts may have been encountered with some devices that utilize the
sata_nv driver. With this update, ADMA mode is now disabled by
default, which resolves this issue.
o The drivers for virtio, the platform for I/O virtualization in KVM,
has been backported to Red Hat Enterprise Linux 4.8 from Linux Kernel
2.6.27. These drivers will enable KVM guests to achieve higher levels
of I/O performance. Various user space components such as: anaconda,
kudzu, lvm, selinux and mkinitrd have also been updated to support
virtio devices.
o The r8169 driver has been updated to provide support for newer network
chipsets. With this update, all variants of RTL810x/RTL8168(9) are now
supported in Red Hat Enterprise Linux 4.8.
o The mptsas driver has been updated to version 3.12.29.00. This update
includes bug fixes and enables the following new features:
o Dual Port support.
o SAS chip Power Management.
o The lpfc driver has been updated to version number to 8.0.16.46. This
update applies several bug fixes and enhancements, including:
o support for FCoE LP21000 HBAs
o support for HBAnyware 4.0
o The megaraid_sas driver for SAS based RAID controllers has been
updated to version 4.01-RH1. Several bug fixes and improvements are
applied by this update, including:
o Added support for the LSI Generation 2 Controllers (0078, 0079)
o Added a command to shutdown DCMD in the shutdown routine to
improve firmware shutdown.
o A bug that caused unexpected interrupts in the hardware Linux
driver has been fixed.
o The eHEA ethernet device driver for IBM eServer System P has been
updated to version 0078-08.
o The EHCA infinband device driver will not be supported for Red Hat
Enterprise Linux 4.8 and all future Red Hat Enterprise Linux 4
releases.
Technology Previews
Technology Preview features are currently not supported under Red Hat
Enterprise Linux 4.8 subscription services, may not be functionally
complete, and are generally not suitable for production use. However,
these features are included as a customer convenience and to provide the
feature with wider exposure.
Customers may find these features useful in a non-production environment.
Customers are also free to provide feedback and functionality suggestions
for a technology preview feature before it becomes fully supported.
Erratas will be provided for high-severity security issues.
During the development of a technology preview feature, additional
components may become available to the public for testing. It is the
intention of Red Hat to fully support technology preview features in a
future release.
For more information on the scope of Technology Previews in Red Hat
Enterprise Linux, please view the [6]Technology Preview Features Support
Scope page on the Red Hat website.
OpenOffice 2.0
OpenOffice 2.0 is now included in this release as a Technology
Preview. This suite features several improvements, including ODF
and PDF functionalities, support for digital signatures and
greater compatibility with open suites in terms of format and
interface. In addition to this, the OpenOffice 2.0 spreadsheet has
enhanced pivot table support, and can now handle up to 65,000
rows.
For more information about OpenOffice 2.0, please refer to
[7]http://www.openoffice.org/dev_docs/features/2.0/index.html .
Resolved Issues
o Previously, if the Red Hat Network applet was used to re-register the
client to a different Red Hat Satellite Server, the applet would
continue to show updates that had been available on the previous
server, even if they were not available on the current server. The
/etc/sysconfig/rhn/rhn-applet would not change to reflect the details
of the new server. The version of the applet provided with this update
associates a cache of updates with a server url, and therefore ensure
that the updates displayed to the user are actually available. This
version can also detect when its configuration file has changed. If
such a change is detected, the applet will automatically reload the
configuration variables and create new server connections.
o sysreport.legacy used $HOME as its root directory. In case this
environment variable did not exist or the directory it referred to was
not writable, sysreport.legacy could not generate its report and would
exit with the message Cannot make temp dir. Sysreport.legacy now uses
a randomly created directory as its root directory and therefore can
generate a report even on a system without a usable $HOME.
o The automount daemon used fixed size buffer of 128 bytes long to
receive information from the SIOCGIFCONF ioctl about local interfaces
when testing for the proximity of a host corresponding to a given
mount. Since the details of each interface are 40 bytes long, the
daemon could receive information on no more than three local
interfaces. If the host corresponding to the mount had an address that
was local but did not correspond to one of the three interfaces the
proximity would be classified incorrectly.
The automount daemon now dynamically allocates a buffer, ensuring that
it is large enough to contain information on all interfaces on the
system providing the ability to correctly detect proximity of a host
given for an NFS mount.
o Automount map entries that refer to multiple hosts in the mount
location (replicated mount), the automount daemon probes a list of
remote hosts for their proximity and NFS version. If hosts fail to
respond, they are removed from the list. If no remote hosts reply at
all, the list may become empty. Previously, the daemon did not check
if the list was empty following the initial probe which would lead to
a segmentation fault (by dereferencing a NULL pointer). This check has
been added.
o the ttfonts-zh_CN package formerly included the Zhong Yi Song TrueType
font. The copyright in this font belongs to Beijing Zhong Yi
Electronics Co., which has licensed Red Hat Inc. to distribute the
font only in products and software under the Red Hat name. The
inclusion of this font in ttfonts-zh_CN would therefore preclude Red
Hat from freely distributing this package. The Zhong Yi Song TrueType
font is still available to Red Hat customers via the Red Hat Network
and the Supplementary CD in the fonts-chinese-zysong package.
o multipathd crashed with a status of with a multipathd dead but pid
file exists when multipath was configured for 1024 or more paths,
because it was unable to open a file descriptor for each path. This
may also have caused error calling out /sbin/mpath_prio_ontap
/dev/[device] errors. Now, a new multipath.conf parameter, max_fds,
allows end-users to set the maximum number of file descriptors that
the multipathd process can have open, or to use max to set the number
to the system maximum. Setting max_fds to either a sufficiently high
number or to max avoids this crash in multipathd.
o Previously, when using the accraid driver with an Adaptec 2120S or
Adaptec 2200S controller, the system may have failed to bootup,
returning the error: aac_srb:aac_fib_send failed with status 8195.
With this update, the accraid driver has been updated, which resolves
this issue.
o SOS is a set of tools that gathers information about a system's
hardware and current configuration. The information can then be used
for diagnostic purposes and debugging.
With this update, the reports generated by sosreport now include five
types of information that were not previously collected:
o the content of /var/log/cron* and the output of crontab -l to
show what was running at the time that the problem occurred.
o partition information from parted instead of what was previously
collected from fdisk, since parted can collect partition
information in situations where fdisk cannot (for example, GUID
partitions).
o output from dumpe2fs -l.
o the content of /etc/inittab.
o output from "/sbin/service --status-all" to show the current
status of services. Previously, only their settings at boot time
were collected (from "chkconfig --list").
o automount uses umount(8) when expiring mounts and umount(8) can wait
indefinitely for a server to respond. This can lead to the expire
being blocked causing mounts not to be expired for a long period of
time in the same /usr/sbin/automount process (that is, the mount that
the given automount process in managing). Consequently, if a server
was unreachable, then automount would not unmount any expired mounts,
even on the servers that are responding. Systems can then be left with
a large number of mounts that can be expired but are not. Automount
now includes a command line option to specify a time for automount to
wait before giving up and moving on to remaining mounts. Expired
mounts can therefore be unmounted even if some servers do not respond.
o The netpbm package has been updated to fix the following bugs:
o Several utilities shipped with netpbm did not accept files from
standard input even though this method was in accordance with
documentation. With this update, this issue has been resolved.
o Several utilities shipped with netpbm may have crashed during
processing of image files. With this update, this issue has been
resolved.
o the ICQ Internet message protocol servers recently changed and now
require clients to use a newer version of the ICQ protocol. Logging in
to ICQ with Pidgin 2.5.2 (the version previously shipped with Red Hat
Enterprise Linux 4) failed with an error message as a result. With
this update, Pidgin has been updated to version 2.5.5, which resolves
this issue.
o Previously, the Red Hat Knowledgebase article documenting Fibre
Channel rescan in Red Hat Enterprise Linux 4 was not accurate. This
procedure has now been updated, and can be viewed at:
[8]http://kbase.redhat.com/faq/docs/DOC-3942
o After successfully connecting to an SSH server, the server may return
a text based banner back to the SSH client. Consequently, if gftp (a
graphical ftp client) attempted to connect (via SFTP) to an SSH server
that returns a banner, gftp would interpret the banner as an error,
and close the connection. With this update, gftp has been updated to
version 2.0.18, allowing connections to servers with banners.
o When uploading a single file to a NFS directory, the timestamp
indicating the modification and access times of the file may not have
been recorded correctly. With this update, the timestamp is now always
updated, which resolves this issue.
o The probing code in kudzu for PCI devices would not properly find some
modules that work by binding to specific PCI classes, notably, the
sgiioc4 driver on SGI Altix systems. Without these modules loaded, the
system would not detect devices that depended on the driver. A new
version of the probing code is included in this updated package, which
is able to successfully find the affected modules.
Known Issues
o The Logical Volume Manager in Red Hat Enterprise Linux 4.8 reports
file descriptor leaks, resulting in the following error returned to
the installation output:
File descriptor NUM (socket:XXXX) leaked on lvm invocation.
This message can be safely ignored.
o When installing Red Hat Enterprise Linux 4 through an Network File
System (NFS) server, the installer is unable to correctly close the
NFS mount points. This might cause the NFS server to misbehave. In
these cases Red Hat suggests the use of an HTTP server for
installations.
o On systems where the BIOS is able to do both legacy (acpiphp) and
native (pciehp) PCI hotplugging, it is necessary for the administrator
to choose a preferred method and explicitly prevent Red Hat Enterprise
Linux 4 from loading the module for the undesired method. This is done
by blacklisting the undesired module in /etc/modprobe.conf.
o Hardware testing for the Mellanox MT25204 has revealed that an
internal error occurs under certain high-load conditions. When the
ib_mthca driver reports a catastrophic error on this hardware, it is
usually related to an insufficient completion queue depth relative to
the number of outstanding work requests generated by the user
application.
Although the driver will reset the hardware and recover from such an
event, all existing connections at the time of the error will be lost.
This generally results in a segmentation fault in the user
application. Further, if opensm is running at the time the error
occurs, then you need to manually restart it in order to resume proper
operation.
o A bug in previous versions of openmpi and lam may prevent you from
upgrading these packages. This same bug may cause up2date to fail when
upgrading all packages.
This bug manifests in the following error when attempting to upgrade
openmpi or lam:
error: %preun(openmpi-[version]) scriptlet failed, exit status 2
This bug also manifests in the following error (logged in
/var/log/up2date) when attempting to upgrade all packages through
up2date:
up2date Failed running rpm transaction - %pre %pro failure ?.
As such, you need to manually remove older versions of openmpi and lam
first in order to avoid these errors. To do so, use the following rpm
command:
rpm -qa | grep '^openmpi-\|^lam-' | xargs rpm -e --noscripts
--allmatches
o When a LUN is deleted on a configured storage system, the change is
not reflected on the host. In such cases, lvm commands will hang
indefinitely when dm-multipath is used, as the LUN has now become
stale.
To work around this, delete all device and mpath link entries in
/etc/lvm/.cache specific to the stale LUN. To find out what these
entries are, run the following command:
ls -l /dev/mpath | grep <stale LUN>
For example, if <stale LUN> is 3600d0230003414f30000203a7bc41a00, the
following results may appear:
lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4
lrwxrwx--rwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
This means that 3600d0230003414f30000203a7bc41a00 is mapped to two
mpath links: dm-4 and dm-5.
As such, the following lines should be deleted from /etc/lvm/.cache:
/dev/dm-4
/dev/dm-5
/dev/mapper/3600d0230003414f30000203a7bc41a00
/dev/mapper/3600d0230003414f30000203a7bc41a00p1
/dev/mpath/3600d0230003414f30000203a7bc41a00
/dev/mpath/3600d0230003414f30000203a7bc41a00p1
o In a HA-RAID two-system configuration, two SAS adapters are plugged in
to two systems and connected to a shared SAS disk drawer. Setting the
Preferred Dual Adapter State attribute to Primary on both SAS adapters
can trigger a race condition and cause infinite failover between the
two SAS adapters. This is because only one SAS adapter can be set to
Primary.
To prevent this error, ensure that the Preferred Dual Adapter State of
one SAS adapter is set to None if the other SAS adapter should be set
to Primary.
o If you need to use the hp_sw kernel module, install the updated
device-mapper-multipath package.
You also need to properly configure the HP array to correctly use
active/passive mode and recognize connections from a Linux machine. To
do this, perform the following steps:
1. Determine what the world wide port name (WWPN) of each connection
is by using show connections. Below is a sample output of show
connections on an HP MSA1000 array with two connections:
Connection Name: <Unknown>
Host WWNN = 200100E0-8B3C0A65
Host WWPN = 210100E0-8B3C0A65
Profile Name = Default
Unit Offset = 0
Controller 2 Port 1 Status = Online
Connection Name: <Unknown>
Host WWNN = 200000E0-8B1C0A65
Host WWPN = 210000E0-8B1C0A65
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Online
2. Configure each connection properly using the following command:
add connection [connection name] WWPN=[WWPN ID] profile=Linux
OFFSET=[unit offset]
Note that [connection name] can be set arbitrarily.
Using the given example, the proper commands should be:
add connection foo-p2 WWPN=210000E0-8B1C0A65 profile=Linux
OFFSET=0
add connection foo-p1 WWPN=210100E0-8B3C0A65 profile=Linux
OFFSET=0
3. Run show connections again to verify that each connection is
properly configured. As per the given example, the correct
configuration should be:
Connection Name: foo-p2
Host WWNN = 200000E0-8B1C0A65
Host WWPN = 210000E0-8B1C0A65
Profile Name = Linux
Unit Offset = 0
Controller 1 Port 1 Status = Online
Connection Name: foo-p1
Host WWNN = 200100E0-8B3C0A65
Host WWPN = 210100E0-8B3C0A65
Profile Name = Linux
Unit Offset = 0
Controller 2 Port 1 Status = Online
o Red Hat discourages the use of quota on EXT3 file systems. This is
because in some cases, doing so can cause a deadlock.
Testing has revealed that kjournald can sometimes block some
EXT3-specific callouts that are used when quota is running. As such,
Red Hat does not plan to fix this issue in Red Hat Enterprise Linux 4,
as the modifications required would be too invasive.
Note that this issue is not present in Red Hat Enterprise Linux 5.
o Hardware testing for the Mellanox MT25204 has revealed that an
internal error occurs under certain high-load conditions. When the
ib_mthca driver reports a catastrophic error on this hardware, it is
usually related to an insufficient completion queue depth relative to
the number of outstanding work requests generated by the user
application.
Although the driver will reset the hardware and recover from such an
event, all existing connections at the time of the error will be lost.
This generally results in a segmentation fault in the user
application. Further, if opensm is running at the time the error
occurs, then you need to manually restart it in order to resume proper
operation.
o The Desktop Sharing connection icon displays its context menu when you
double-click it, not when you right-click it. All other icons display
their context menus when you right-click on them.
o If the ib_ehca InfiniBand driver is loaded in port auto-detection mode
(using module parameter nr_ports=-1), the IP-over-InfiniBand network
interfaces (ibX) might become available too late. When this occurs,
the ifup ibX command issued from the openibd startup script will fail;
consequently, the ibX interface will not become available.
When this occurs, use the command rcnetwork restart to fix the
problem.
o In the [9]IBM Redbook "Implementing InfiniBand in IBM System p
(SG247351) manual, Table 6-3 (on page 220 of the PDF version)
describes debug code bit definitions, where several HCA error
indicator bits are also described.
Note that with eHCA2 adapters, bits 46 and 47 of these error indicator
bits might return false positives.
o On HP ICH10 workstations, audio is only enabled through the front
3.5mm jacks. As such, to receive any audio output or use recording,
you should plug in your headphones, speakers, or microphones to the
front jacks. At present, the rear jacks, internal speaker, and master
volume for this workstation do not work.
o With this update, the default PCI detection and ordering mode for the
following models have changed:
o HP Proliant DL 580 G5
o HP Proliant DL 385 G2
o HP Proliant DL 585 G2
These models use a device scanning and enumeration mode which is not
the default for Red Hat Enterprise Linux 4 or 5. The mode used by
these HP Proliant models could result in add-on cards being detected
and added prior to onboard/internal devices. This unexpected ordering
could cause difficulties when installing new instances of Red Hat
Enterprise Linux, adding hardware, and maintenance.
The numbering of network interface cards (NIC) for the aforementioned
HP Proliant models may change when they are updated with the Red Hat
Enterprise Linux 4.7 kernel. The installer changes NIC numbering if
the HWADDR=MAC ADDRESS parameter is not defined in
/etc/sysconfig/network-scripts/ifcfg-eth[X] for each installed NICs.
As such, Red Hat recommends that you ensure this parameter is defined
in order to avoid any problems arising from an unexpected NIC
enumeration.
In addition, to avoid any NIC enumeration changes after updating these
HP Proliant models to Red Hat Enterprise Linux 4.7, add the kernel
boot parameter pci=nobfsort to /boot/grub/grub.conf.
o When a volume group contains a mirror or snapshot, issuing the
lvchange command with a volume group parameter may result in the
following error messages:
Unable to change mirror log LV fail_secondary_mlog directly
Unable to change mirror image LV fail_secondary_mimage_0 directly
Unable to change mirror image LV fail_secondary_mimage_1 directly
These messages can be safely ignored.
o Dell PowerEdge SC1435s systems may hang during boot-up. To avoid this,
edit the terminal line in grub.conf and replace the string serial
console with console serial.
o The updated ixgbe driver does not support the Intel 82598AT (Copper
Pond 10GbE).
o Red Hat Enterprise Linux 5.3 can detect online growing or shrinking of
an underlying block device. However, there is no method to
automatically detect that a device has changed size, so manual steps
are required to recognize this and resize any file systems which
reside on the given device(s). When a resized block device is
detected, a message like the following will appear in the system logs:
VFS: busy inodes on changed media or resized disk sdi
If the block device was grown, then this message can be safely
ignored. However, if the block device was shrunk without shrinking any
data set on the block device first, the data residing on the device
may be corrupted.
It is only possible to do an online resize of a filesystem that was
created on the entire LUN (or block device). If there is a partition
table on the block device, then the file system will have to be
unmounted to update the partition table.
o There is a known memory leak with the res_n* family of resolver
routines (i.e. res_nquery, res_nsearch and res_nmkquery). Programs
that use these functions will leak memory over time. It has been fixed
in newer versions of glibc, however, the fix is too invasive to be
applied to Red Hat Enterprise Linux 4. Programs that use these
functions may need to be restarted occasionally to free memory.
o The number of devices that can be handled during installation of Red
Hat Enterprise Linux 4 depends on the size of the installation initrd
image. Therefore, in situations where there are many devices attached
to a machine (such as heavily populated Fibre Channel setups)
installation will not be possible unless number of visible devices is
reduced.
o The aacraid driver update that was first introduced in Red Hat
Enterprise Linux 4.7 requires up to date Adaptec PERC3/Di firmware.
Subsequent updates of Red Hat Enterprise Linux 4 (including this 4.8
update) require, that the PERC3/Di firmware is at version 2.8.1.7692,
A13 or newer. The firmware may be obtained at the following location:
[10]http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R168387&SystemID=PWE_PNT_PIII_1650&servicetag=&os=WNET&osl=en&deviceid=1375&devlib=0&typecnt=0&vercnt=9&catid=-1&impid=-1&formatcnt=4&libid=35&fileid=228550
o During installation anaconda may not remove all the Logical Volume
Manager (LVM) metadata that exists on a system prior to installation.
This extra metadata may cause LVM tools to report missing volume
groups or logical volumes after installation. To work around this
issue, remove the stale LVM metadata after the installation is
complete.
o multipath does not silence the error messages printed by any of it's
callout programs. Therefore, if multipath is run when paths are down,
various error messages may be displayed. The messages that are
displayed depend on the specific callout programs that multipath is
using. For example, if multipath is run while there are failed scsi
devices, scsi_id will print
<H>:<B>:<T>:<L>:Unable to get INQUIRY vpd 1 page 0x0.
<H>:<B>:<T>:<L>:sg_io failed status 0x0 0x1 0x0 0x0
Or, if multipath -ll is run while an EMC CLARiiON is down, the
mpath_prio_emc priority callout will print query command indicates
error
( x86 )
References
Visible links
1. http://www.opencontent.org/openpub/
2. http://www.redhat.com/docs/manuals/enterprise/
3. https://www.redhat.com/security/updates/errata/
4. https://www.redhat.com/archives/nahant-list/2008-July/msg00059.html
5. http://samba.org/samba/history/samba-3.0.33.html
6. http://www.redhat.com/support/policy/soc/production/preview_scope/
7. http://www.openoffice.org/dev_docs/features/2.0/index.html
8. http://kbase.redhat.com/faq/docs/DOC-3942
9. http://www.redbooks.ibm.com/abstracts/sg247351.html
10. http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R168387&SystemID=PWE_PNT_PIII_1650&servicetag=&os=WNET&osl=en&deviceid=1375&devlib=0&typecnt=0&vercnt=9&catid=-1&impid=-1&formatcnt=4&libid=35&fileid=228550%20%20%20
|
