HI,
Can it be installed on top of the SL 5.1??
> Scientific Linux 5.2 i386 is now officially released and available.
> We want to thank everyone for their contributions, testing and
> feedback. With all your effort we have been able to get this release
> out in a timely manner.
>
> There are CD and DVD iso images available at
>
> http://ftp.scientificlinux.org/linux/scientific/52/iso/i386/
> ftp://ftp.scientificlinux.org/linux/scientific/52/iso/i386/
>
> -Connie Sieh
> -Troy Dawson
>
> --SL 5.2 release notes --
>
> Scientific Linux "SL 5.2" for i386 June 26, 2008
>
> --------------------------------------------------------------------------
>
> Table of contents
>
> DOWNLOAD INFO
> ADDED compared to Enterprise 5.2
> UPDATED compared to Enterprise 5.2
> Installer/legal modifications
> ADDED by Upstream Vendor
> /contrib
> SRPMS
> HARDWARE REQUIREMENTS
> LIMITATIONS
> INFO
> ERRATA
> _____________________________________________________________________________
>
> DOWNLOAD INFO
> _____________________________________________________________________________
>
>
> ftp://ftp.scientificlinux.org/linux/scientific/52/i386
> ftp://ftp.scientificlinux.org/linux/scientific/52/iso/i386
>
> -----------------------------------------------------------------------------
>
> ADDED compared to vendor
> -----------------------------------------------------------------------------
>
> 915resolution-0.5.3-6.el5.i386.rpm
> 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.
>
>
> 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.
>
> * alpine-1.10-1.i386.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.030-1.sl5.i386.rpm
> cfitsio-devel-3.030-1.sl5.i386.rpm
>
> *dkms
> *
> * This package contains the framework for the Dynamic
> * Kernel Module Support (DKMS) method for installing
> * module RPMS as originally developed by Dell.
> *
> * dkms-2.0.17.4-1.9.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.
> * Updated to latest fuse-smb and fuse-sshfs
>
> fuse-2.6.3-1.SL.i386.rpm
> fuse-devel-2.6.3-1.SL.i386.rpm
> fuse-libs-2.6.3-1.SL.i386.rpm
> * fuse-smb-0.8.7-1.SL.i386.rpm
> * fuse-sshfs-2.0-1.SL.i386.rpm
> * kernel-module-fuse-2.6.18-92.1.6.el5-2.6.3-1.sl5.i686.rpm
> * kernel-module-fuse-2.6.18-92.1.6.el5PAE-2.6.3-1.sl5.i686.rpm
> * kernel-module-fuse-2.6.18-92.1.6.el5xen-2.6.3-1.sl5.i686.rpm
>
> *Graphviz
>
> Graph Visualization Tools
> * Updated to latest release
> *
>
> * graphviz-2.18-3.sl.i386.rpm
> * graphviz-devel-2.18-3.sl.i386.rpm
> * graphviz-doc-2.18-3.sl.i386.rpm
> * graphviz-graphs-2.18-3.sl.i386.rpm
> * graphviz-guile-2.18-3.sl.i386.rpm
> * graphviz-java-2.18-3.sl.i386.rpm
> * graphviz-lua-2.18-3.sl.i386.rpm
> * graphviz-ocaml-2.18-3.sl.i386.rpm
> * graphviz-perl-2.18-3.sl.i386.rpm
> * graphviz-php-2.18-3.sl.i386.rpm
> * graphviz-python-2.18-3.sl.i386.rpm
> * graphviz-ruby-2.18-3.sl.i386.rpm
> * graphviz-tcl-2.18-3.sl.i386.rpm
>
> *icewm
>
> A lightweight window manager for the X Window System.
> * Updated to the latest version
> * icewm-1.2.35-1.i386.rpm
> * icewm-l10n-1.2.35-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-3.0 includes version 2.2, 2.3, 2.4, and 3.0
>
> ipw2100-firmware-1.3-5.noarch.rpm
> ipw2200-firmware-3.0-1.noarch.rpm
>
> ipw3945d is needed to control the ipw3945 wireless card
> * ipw3945d is now turned on by default. The startup script
> * looks for the ipw3945 hardware, and if it finds it
> * it starts up the ipw3945 deamon. kernel-module-ipw3945 is
> needed because this driver is not in
> the standard kernel.
> 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-1.2.0-2.sl5.i686.rpm
> * ipw3945d-1.7.22-11.sl5.i386.rpm
> ipw3945-firmware-1.14.2-1.sl5.noarch.rpm
> * kernel-module-ipw3945-2.6.18-92.1.6.el5-1.2.0-2.sl5.i686.rpm
> * kernel-module-ipw3945-2.6.18-92.1.6.el5PAE-1.2.0-2.sl5.i686.rpm
> * kernel-module-ipw3945-2.6.18-92.1.6.el5xen-1.2.0-2.sl5.i686.rpm
>
> The file iwlwifi-4965.ucode is required to be
> present on your system in order for the Intel Wireless WiFi Link
> 4965AGN driver for Linux (iwlwifi) to be able to operate on your
> system.
>
> iwlwifi-4965-ucode-4.44.17-5.sl5.noarch.rpm
>
>
> *JAVA
>
> * java-1.5.0-sun-compat-1.5.0.15-1jpp.noarch.rpm
> * jdk-1.5.0_15-fcs.i586.rpm
>
> This packages is the java sdk from sun.
> It's license is found at SL.documentation/jdk-1.5.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.5.0-sun-compat
> as it will automatically pull in the current j2sdk-1.5.0 rpm.
>
> java-1.5.0-sun-compat-1.5.0.15-1jpp.noarch.rpm
>
> This package provides JPackage compatibility symlinks and
> directories for Sun's JDK rpm.
>
> *kdeedu
> *
> * Educational/Edutainment applications for KDE
> * kstars is part of this package
> *
> * kdeedu-3.5.4-1.el5.i386.rpm
> * kdeedu-devel-3.5.4-1.el5.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-15.i686.rpm
> * kernel-module-madwifi-2.6.18-92.1.6.el5-0.9.4-15.sl5.i686.rpm
> * kernel-module-madwifi-2.6.18-92.1.6.el5PAE-0.9.4-15.sl5.i686.rpm
> * kernel-module-madwifi-2.6.18-92.1.6.el5xen-0.9.4-15.sl5.i686.rpm
> * kernel-module-madwifi-hal-2.6.18-92.1.6.el5-0.9.4-15.sl5.i686.rpm
> * kernel-module-madwifi-hal-2.6.18-92.1.6.el5PAE-0.9.4-15.sl5.i686.rpm
> * kernel-module-madwifi-hal-2.6.18-92.1.6.el5xen-0.9.4-15.sl5.i686.rpm
>
> Multimedia
>
> gstreamer-plugins-extras-0.10.9-2.sl.i386.rpm from SL4 (updated
> tarball)
> k3b-extras-0.12.17-3.sl.i386.rpm from livna Repository
>
> These are dependencies of the above rpms.
>
> lame-3.97-1.sl.i386.rpm from RPMforge
> lame-devel-3.97-1.sl.i386.rpm from RPMforge
> libid3tag-0.15.1b-3.sl.i386.rpm from RPMforge
> libid3tag-devel-0.15.1b-3.sl.i386.rpm from RPMforge
> libmad-0.15.1b-4.sl.i386.rpm from RPMforge
> libmad-devel-0.15.1b-4.sl.i386.rpm from RPMforge
> taglib-1.4-1.2.sl.i386.rpm from RPMforge
> taglib-devel-1.4-1.2.sl.i386.rpm from RPMforge
>
> *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.
>
> 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
> * Updated to the latest version
>
> * ndiswrapper-1.53-1.SL.i686.rpm
> * kernel-module-ndiswrapper-2.6.18-92.1.6.el5-1.53-1.SL.i686.rpm
> * kernel-module-ndiswrapper-2.6.18-92.1.6.el5PAE-1.53-1.SL.i686.rpm
> * kernel-module-ndiswrapper-2.6.18-92.1.6.el5xen-1.53-1.SL.i686.rpm
>
> nedit
> NEdit is a GUI text editor for the X Window System and Motif.
>
> nedit-5.5-10.el5.i386.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.0.4-1.i386.rpm
> *OpenAFS
>
> * We have put in the latest 1.4.7 release of openafs
>
> * openafs-1.4.7-68.SL5.i686.rpm
> * openafs-authlibs-1.4.7-68.SL5.i686.rpm
> * openafs-authlibs-devel-1.4.7-68.SL5.i686.rpm
> * openafs-client-1.4.7-68.SL5.i686.rpm
> * openafs-compat-1.4.7-68.SL5.i686.rpm
> * openafs-debug-1.4.7-68.SL5.i686.rpm
> * openafs-devel-1.4.7-68.SL5.i686.rpm
> * openafs-kernel-source-1.4.7-68.SL5.i686.rpm
> * openafs-kpasswd-1.4.7-68.SL5.i686.rpm
> * openafs-krb5-1.4.7-68.SL5.i686.rpm
> * openafs-server-1.4.7-68.SL5.i686.rpm
> * gfs-utils-0.1.12-1.el5_1.1.i386.rpm
> openafs-firstboot-1.4-1.SL.noarch.rpm
> * kernel-module-openafs-2.6.18-92.1.6.el5-1.4.7-68.SL5.i686.rpm
> * kernel-module-openafs-2.6.18-92.1.6.el5PAE-1.4.7-68.SL5.i686.rpm
> * kernel-module-openafs-2.6.18-92.1.6.el5xen-1.4.7-68.SL5.i686.rpm
>
>
> These perl modules have been added as they are useful. They came from
> CERN
>
> perl-MailTools-1.62-1.noarch.rpm
> perl-Parse-RecDescent-1.94-1.noarch.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
> perl-TimeDate has been added to the release by The Upstream Vendor
> We decided to use TUV's version of perl-TimeDate
>
> *R
>
> http://www.r-project.org/
> R is a language and environment for statistical computing and
> graphics.
> R 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.
> * Latest version
>
> * R-2.7.0-1.sl5.i386.rpm
> * R-devel-2.7.0-1.sl5.i386.rpm
> * libRmath-2.7.0-1.sl5.i386.rpm
> * libRmath-devel-2.7.0-1.sl5.i386.rpm
> *r1000
> *
> * The r1000 driver is now the r8169 driver, now in the SL 5.2 kernel.
> * Because it is now in the kernel, we have removed the r1000 packages.
>
>
> SL_afs_no_dynroot-2.0-2.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-5-4.noarch.rpm
>
> This adds a terminal icon to the kicker panel for both KDE and GNOME.
> This also changed the KDE startup background from red to black
> Installed by default for both KDE and GNOME.
>
> SL_enable_serialconsole-3.1-6.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.
>
> SL_no_colorls-1.0-3.noarch.rpm
>
> Turns off "color" of ls. Not installed by default.
>
> SL_password_for_singleuser-1.0-1.noarch.rpm
>
> Changes /etc/inittab to require the root password for
> single user mode. Not installed by default.
> This used to be SL_inittab_change
>
> *SL_rpm_show_arch-1.0-2.noarch.rpm
>
> Adds arch to "rpm -qa" listing.
> * Now umask friendly
>
> SL_sendmail_accept-1.1-3.noarch.rpm
>
> Changes Sendmail config so that it allows incomming mail.
> Not installed by default.
>
> 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 layed out markup? Well now there is! 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 pages
> more accessible to people with disabilities.
>
> tidy-0.99.0-12.20070228.sl5.i386.rpm
> libtidy-0.99.0-12.20070228.sl5.i386.rpm
> libtidy-devel-0.99.0-12.20070228.sl5.i386.rpm
>
> *XFS
> * XFS is a highly scalable, high-performance journaling filesystem
> * that provides rapid recovery from system crashes.
> *
> * xfs-0.4-1.el5.i686.rpm
> * xfsdump-2.2.46-1.sl5.i386.rpm
> * xfsprogs-2.9.4-1.sl5.i386.rpm
> * xfsprogs-devel-2.9.4-1.sl5.i386.rpm
> * dmapi-2.2.8-1.sl5.i386.rpm
> * dmapi-devel-2.2.8-1.sl5.i386.rpm
> * kernel-module-xfs-2.6.18-92.1.6.el5-0.4-1.sl5.i686.rpm
> * kernel-module-xfs-2.6.18-92.1.6.el5PAE-0.4-1.sl5.i686.rpm
> * kernel-module-xfs-2.6.18-92.1.6.el5xen-0.4-1.sl5.i686.rpm
>
>
> *Yumex
>
> Yumex is a graphical user interface for yum.
> * Updated to the latest stable version
>
> * yumex-2.0.3-1.0.el5.noarch.rpm
>
>
> *yum-utils
> 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.
> * These plugin's have been updated to version 1.1.10, corresponding
> * to the yum-utils version provided by TUV
> * yum-installonlyn has been incorporated into yum
> * See comments in yum.conf on how to change settings for installonlyn
>
> * yum-allowdowngrade-1.1.10-10.el5.noarch.rpm
> * yum-fastestmirror-1.1.10-10.el5.noarch.rpm
> * yum-merge-conf-1.1.10-10.el5.noarch.rpm
> * yum-priorities-1.1.10-10.el5.noarch.rpm
> * yum-refresh-updatesd-1.1.10-10.el5.noarch.rpm
> * yum-tsflags-1.1.10-10.el5.noarch.rpm
> * yum-upgrade-helper-1.1.10-10.el5.noarch.rpm
>
> * The following have been replaced by a new version which is included
> * by TUV
> * yum-metadata-parser-1.0.4-1.sl5.i386.rpm
> * yum-utils-1.0.4-1.el5.noarch.rpm
> * yum-downloadonly-1.0.4-1.el5.noarch.rpm
> * yum-changelog-1.0.4-1.el5.noarch.rpm
> * yum-fedorakmod-1.0.4-1.el5.noarch.rpm
> * yum-installonlyn-1.0.4-2.sl5.noarch.rpm
> * yum-protectbase-1.0.4-1.el5.noarch.rpm
> * yum-skip-broken-1.0.4-1.el5.noarch.rpm
> * yum-updateonboot-1.0.4-1.el5.noarch.rpm
> * yum-versionlock-1.0.4-1.el5.noarch.rpm
>
> MISC
> Added these rpms because they are important but upstream vendor did
> not include them.
>
> gv-3.6.2-2.sl5.i386.rpm from Stephan Wiesand
> * Pine has been replaced by alpine
> -------------------------------------------------------------------------
> Changed RPMS compared to vendor
> -------------------------------------------------------------------------
>
> Installer(anaconda)
>
> * anaconda-11.1.2.113-3.SL.i386.rpm
> * anaconda-runtime-11.1.2.113-3.SL.i386.rpm
> *
> * Added kernel-module.py yum plugin during the install
> Modified pkgorder with patches from CentOS
> Modified installclasses/rhel.py to remove key request
> Modified installclasses/rhel.py to include SL groups
> sites support
> see sites/example
>
> Note: Installing sites on a virtual machine
> When installing a paravirtulized site, you have to point at the
> site directory, such as 5rolling/i386/sites/example
>
> When installing a fully virtulized site, you only have to point
> to the base directory, like you usually would, such as
> 5rolling/x86_64/sites/example
>
> *comps.xml
> *
> * Updated some group names and descriptions to work better
> internationally
> *
> * In Update 1 The Upstream Vendor changed their comps.xml files to
> * reflect a different sorting structure, as well as clean up extra
> * files from their short term linux release.
> *
> * In Update 2 The Upstream Vendor added more packages to their
> comps.xml
> * comps-sl.xml has been changed to incorporate most of
> * TUV changes. Since we have merged their various comps.xml files,
> * our comps.xml will never really look like theirs. But this
> * change brings ours more in line with their Update 2 versions.
>
> 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".
>
> redhat-artwork-5.0.9-1.SL.2.i386.rpm
> redhat-logos-4.9.16-1.SL.6.noarch.rpm
> * sl-release-5.2-1.i386.rpm
> * sl-release-notes-5.2-1.noarch.rpm
> sl-release changes the default mozilla and firefox bookmarks.
> sl-release changes the default rhn configuration to use yum and
> points this configuration to ftp.scientificlinux.org
> sl-release removed the firstboot additional cd's question
> redhat-logos was changed to add the "photographs" shown during
> the install
>
> These rpm's are not required to be changed by the vendor, but we felt
> they needed to be changed
>
> * gdm-2.16.0-46.sl5.i386.rpm
> Changed the default theme from RHEL to EaseOfBlue
> * pirut-1.3.28-13.sl.noarch.rpm
> * Removed "Requires: rhn-setup-gnome"
> rhgb-0.16.4-8.sl.1.i386.rpm
> Changed the colors.
>
> python-virtinst
>
> virtinst is a module to help in starting installations inside of
> virtual machines. It supports both paravirt guests as well as
> fully virtualized guests. It uses libvirt (http://www.libvirt.org)
> for starting things. Also contained is a simple
> script virt-install which uses virtinst in a command line mode.
> It was only configured to know about TUV virtual machines. We
> added
> a patch so that it knew about Scientific Linux, and thus be able to
> install SL paravirtual machines.
> * python-virtinst-0.300.2-8.sl.noarch.rpm
>
> yum
>
> 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
>
> yum-conf
> * priorities have been set on the repositories. But you have to have
> * yum-priorities installed for them to take effect.
> 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
> yum-conf has the following repositories in it
> sl-base (enabled)
> sl-security (enabled)
> sl-testing (not enabled)
> sl-fastbugs (not enabled)
> sl-bugfix-51 (not enabled)
> atrpms (not enabled)
> dag (not enabled)
> flash (not enabled)
> Not all repositories are enabled by default.
> To enable them for one time use, use the --enablerepo command, such as
> yum --enablerepo=atrpms list mplayer
> yum --enablerepo=dag install xine
> yum --enablerepo=adobe install flash-player
>
> 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 in the /etc/yum.repos.d/ directory and are
> named like
> /etc/yum.repos.d/atrpms.repo
> /etc/yum.repos.d/dag.repo
> NOTE1: Just because a yum repository exists does NOT mean
> it is compatible with all other yum repositories. We have included
> the repositories we did because they usually work well together.
> But if
> there is a problem with one of the packages in a repository, please
> contact that repository maintainer.
>
> yum-autoupdate
>
> yum-autoupdate has the check for a running yum in it, so that if
> yum has been running for a long time (close to 24 hours), when the
> yum.cron starts up, it will kill the old yum. This was changed
> because we had reports that yum was hanging and we didn't want
> this
> to interfere with updates.
>
> yum-autoupdate 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.
> If it is longer than 20 hours, it waits a random time, up to 3 hours.
> This uptime check was done to help laptops and other machines that
> might not be on long enough to wait for the random time.
> The random time was put it in so that servers arn't overwhelmed.
>
> yum-conf-5x was created for those users who want to be at the latest
> stable release. It is always pointing at the 5x area. This means
> that when we make new versions you will automatically be upgraded to
> them.
> * yum-conf-epel has been added so that people could use the epel yum
> * repository. This rpm requires both yum-provides and
> yum-fastestmirror
>
> * yum-3.2.8-10.sl.noarch.rpm
> yum-autoupdate-1-1.SL.noarch.rpm
> * yum-conf-52-2.SL.noarch.rpm
> * yum-conf-5x-1-5.SL.noarch.rpm
> * yum-conf-epel-5-1.noarch.rpm
> * yum-rhn-plugin-0.5.3-6.el5_2.6.noarch.rpm
> * yum-updatesd-0.9-2.sl.noarch.rpm
>
> Apache
> Changed index.html to not have Upstream Vendor info but to
> have SL info.
>
> * httpd-2.2.3-11.sl5.3.1.i386.rpm
> * httpd-devel-2.2.3-11.sl5.3.1.i386.rpm
> * httpd-manual-2.2.3-11.sl5.3.1.i386.rpm
> * mod_ssl-2.2.3-11.sl5.3.1.i386.rpm
>
> Changed in order to be built
>
> Some rpm's had to be changed in order for us to build them.
> The following rpm's had to have a variable changed so that they
> point to the current include file
>
> brlapi-0.4.1-1.fc6.1.i386.rpm
> brlapi-devel-0.4.1-1.fc6.1.i386.rpm
> brltty-3.7.2-1.fc6.1.i386.rpm
>
>
> -----------------------------------------------------------------------------
>
> /SL/
> -----------------------------------------------------------------------------
>
> The Upstream Vendor's release consists of 2 cd sets, Server and
> Client. Each
> cd set has a group of directories which contain the actual rpms. On
> the Client
> cd this consists of Client,Workstation and VT. On the Server cd this
> consists
> of Server,VT,Cluster, ClusterStorage. The VT directory contains the
> same rpms
> on each cd. The Cluster, ClusterStorage and Workstation directories
> do not
> have any common rpms. The Client and Server directories contain many
> common
> rpms along with many unique rpms.
>
> Scientific Linux has combined all of the rpm's from Client, Server,
> VT, Cluster,
> ClusterStorage, and Workstation into the SL directory.
> You are not asked to enter any key, since you have access to all
> packages.
>
> -----------------------------------------------------------------------------
>
> /contrib/
> ------------------------------------------------------------------------------
>
> RPMS provided by colaboraters that either cannot go in main release or
> are
> intesting before going into main release.
>
> See the SRPMS section for source rpms
>
> -----------------------------------------------------------------------------
>
> /updates/
> -----------------------------------------------------------------------------
>
> security
> Security errata
> fastbugs
> 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
> bugfix51
> Reserved for packages from the next Update.
>
> ---------------------------------------------------------------------------
>
> /../SRPMS/
> ---------------------------------------------------------------------------
>
>
> /SL/
> 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/
> The upstream vendors SRPMS.
> This directory contains both the original released SRPMS, as well as
> the updated SRPMS
> /contrib/
> SRPMS for the contrib packages
> /sites/<site>/SRPMS
> SRPMS for sites, if there is a site
>
> ---------------------------------------------------------------------------
>
> /../archive/
> ---------------------------------------------------------------------------
>
> /obsolete/
> Packages that used to be in the release but have been
> updated
> /debuginfo/
> Debuginfo packages
>
> -----------------------------------------------------------------------------
>
> LIMITATIONS
> -----------------------------------------------------------------------------
>
> ipw2100, ipw2200, ipw3945
> Does not work in the installer
>
> ftp install
> Currently, during an ftp install when it get's the the graphical
> section, there is a long pause (close to a minute) when it sits
> at a blank screen. It is NOT frozen, it is just searching for
> files that are not there. Give it a couple minutes and it
> will continue. This will be fixed before the final release.
>
> NVIDIA motherboard chipsets
> May need to use
> linux noapic
> to install.
>
> Intel 965 motherboard chipset
> May need to use
> linux all-generic-ide
> if you have pata hardware
> -----------------------------------------------------------------------------
>
> INFO
> -----------------------------------------------------------------------------
>
> Web Site
>
> https://www.scientificlinux.org
>
> FTP
>
> ftp://ftp.scientificlinux.org/linux/scientific/52/
>
> 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
>
>
>
> ------------------------------------------------------------------------
>
> Copyright © 2008 Red Hat, Inc. and others ^[1 <#ftn.id3776873>]
>
> ------------------------------------------------------------------------
>
>
> Introduction
>
> The following topics are covered in this document:
>
> *
>
> Installation-Related Notes
>
> *
>
> Feature Updates
>
> *
>
> Driver Updates
>
> *
>
> Kernel-Related Updates
>
> *
>
> Virtualization
>
> *
>
> Technology Previews
>
> *
>
> Resolved Issues
>
> *
>
> Known Issues
>
> Some updates on Red Hat Enterprise Linux 5.2 may not appear in this
> version of the Release Notes. An updated version may also be available
> at the following URL:
>
> http://www.redhat.com/docs/manuals/enterprise/
>
>
> Installation-Related Notes
>
> This section includes information specific to Anaconda and the
> installation of Red Hat Enterprise Linux 5.2.
>
> To upgrade an already-installed Red Hat Enterprise Linux 5, you can
> use Red Hat Network to update those packages that have changed.
> Alternatively, you can also use Anaconda to perform a fresh
> installation of Red Hat Enterprise Linux 5.2 or to upgrade an
> already-installed Red Hat Enterprise Linux 5.
>
> Note that upgrading from beta releases to GA releases is not
> supported. Further, Red Hat does not support in-place upgrades between
> major versions of Red Hat Enterprise Linux. Although Anaconda provides
> an option that allows an upgrade from earlier major versions of Red
> Hat Enterprise Linux (such as Enterprise Linux 4 to Enterprise Linux
> 5), there is no guarantee that the upgrade will result in a fully
> functional configuration. In-place upgrades across 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 rather than a system upgrade between major versions.
>
> *
>
> When installing from CD-ROM or DVD-ROM on a system with an
> iBFT-configured network device, Anaconda will not include any
> iBFT-configured storage devices unless networking is configured.
> To enable networking for the installation, use the command
> *linux updates=http:///|[any]|/* at the installation boot
> prompt. Note that */|[any]|/* can be replaced with any URL.
>
> If your system requires a static IP configuration, use the
> command *linux updates=http:///|[any]|/ ip=/|[IP address]|/
> netmask=/|[netmask]|/ dns=/|[dns]|/*.
>
> *
>
> If you are copying the contents of the Red Hat Enterprise Linux
> 5 CD-ROMs (in preparation for a network-based installation, for
> example) be sure to 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.
>
> The contents of the |Supplementary CD-ROM| and other layered
> product CD-ROMs must be installed /after/ Red Hat Enterprise
> Linux 5.2 is installed.
>
> *
>
> When installing Red Hat Enterprise Linux 5.2 on a fully
> virtualized guest, do /not/ use the |kernel-xen| kernel. Using
> this kernel on fully virtualized guests can cause your system to
> hang.
>
> If you are using an Installation Number when installing Red Hat
> Enterprise Linux 5.2 on a fully virtualized guest, be sure to
> deselect the |Virtualization| package group during the
> installation. The |Virtualization| package group option installs
> the |kernel-xen| kernel.
>
> Note that paravirtualized guests are not affected by this issue.
> Paravirtualized guests always use the |kernel-xen| kernel.
>
> *
>
> If you are using the Virtualized kernel when upgrading from Red
> Hat Enterprise Linux 5 to 5.2, you must reboot after completing
> the upgrade. You should then boot the system using the updated
> Virtualized kernel.
>
> The hypervisors of Red Hat Enterprise Linux 5 and 5.2 are not
> ABI-compatible. If you do not boot the system after upgrading
> using the updated Virtualized kernel, the upgraded
> Virtualization RPMs will not match the running kernel.
>
> *
>
> When upgrading to Red Hat Enterprise Linux 5.1 or later from Red
> Hat Enterprise Linux 4.6, |gcc4| may cause the upgrade to fail.
> As such, you should manually remove the |gcc4| package before
> upgrading.
>
> *
>
> The *firstboot* language plugin has been removed, as this plugin
> does not properly and completely reconfigure the system when a
> new language is selected.
>
> *
>
> The use of Challenge Handshake Authentication Protocol (CHAP)
> during installation is not supported. As such, CHAP should only
> be enabled after installation.
>
> If your system boots through an iFBT device, configure CHAP in
> the iFBT BIOS/firmware setup screen. Your CHAP settings will
> then be used in the next boot.
>
> If your system boots through PXE iSCSI, configure CHAP through
> *iscsiadm*. After configuring, use *mkinitrd* to ensure that
> your CHAP settings are used in the next boot.
>
>
> Feature Updates
>
> Systemtap
>
> /Systemtap/ provides free software (GPL) infrastructure to
> simplify the gathering of information about the running Linux
> system. This assists the diagnosis of a performance or functional
> problem. With the help of *systemtap*, developers no longer need
> to go through the tedious and disruptive instrument, recompile,
> install, and reboot sequence that may be otherwise required to
> collect data.
>
> Systemtap is now fully supported. For more information about
> Systemtap, refer to http://sources.redhat.com/systemtap.
>
> iSNS-utils
>
> /Internet storage name service/ for Linux (*isns-utils*) is now
> supported. This allows you to register iSCSI and iFCP storage
> devices on the network. *isns-utils* allows dynamic discovery of
> available storage targets through storage initiators.
>
> *isns-utils* provides intelligent storage discovery and management
> services comparable to those found in fibre-channel networks. This
> allows an IP network to function in a similar capacity as a
> storage area network.
>
> With its ability to emulate fibre-channel fabric services,
> *isns-utils* allows seamless integration of IP and fibre-channel
> networks. In addition, *isns-utils* also provides the utilities
> for managing both iSCSI and fibre-channel devices within the network.
>
> For more information about the specifications of *isns-utils* in
> this release, refer to http://tools.ietf.org/html/rfc4171. For
> usage instructions, refer to
> |/usr/share/docs/isns-utils-/|[version]|//README| and
> |/usr/share/docs/isns-utils-/|[version]|//README.redhat.setup|.
>
> rsyslog
>
> *rsyslog* is an enhanced multi-threaded *syslogd* daemon that
> supports the following (among others):
>
> *
>
> MySQL
>
> *
>
> syslog/tcp
>
> *
>
> RFC 3195
>
> *
>
> permitted sender lists
>
> *
>
> filtering on any message part
>
> *
>
> more granular output format control
>
> *rsyslog* is compatible with the stock *sysklogd*, and can be used
> as a replacement in most cases. Its advanced features make it
> suitable for enterprise-class, encrypted *syslog* relay chains; at
> the same time, its user-friendly interface is designed to make
> setup easy for the novice user.
>
> For more information about *rsyslog*, refer to
> http://www.rsyslog.com/.
>
> OpenSwan
>
> /OpenSwan/ is a free implementation of /Internet Protocol
> Security/ (IPSEC) and IKE for Linux. IPSEC uses strong
> cryptography to provide authentication and encryption services.
> These services allow you to build secure tunnels through untrusted
> networks. Everything passing through the untrusted network is
> encrypted by the IPSEC gateway machine and decrypted by the
> gateway at the other end of the tunnel. The resulting tunnel is a
> virtual private network (VPN).
>
> This release of OpenSwan also contains an IKE2 daemon that
> conforms to IETF RFCs. For more information about OpenSwan, refer
> to http://www.openswan.org/.
>
> Evolution
>
> The Evolution update for this release now features the following
> enhancements (among others):
>
> *
>
> Bogofilter compatibility for filtering junk mail.
>
> *
>
> An option to receive pop-up notifications for new mail.
>
> *
>
> Improved performance for downloading messages from a
> Microsoft Exchange^(TM) server.
>
> *
>
> A setup assistant to guide you through the process of
> backing up and restoring data/settings.
>
> Password Hashing Using SHA-256/SHA-512
>
> Password hashing using the SHA-256 and SHA-512 hash functions is
> now supported.
>
> To switch to SHA-256 or SHA-512 on an installed system, run
> *authconfig --passalgo=sha256 --update* or *authconfig
> --passalgo=sha512 --update*. To configure the hashing method
> through a GUI, use *authconfig-gtk*. Existing user accounts will
> not be affected until their passwords are changed.
>
> For newly installed systems, using SHA-256 or SHA-512 can be
> configured only for kickstart installations. To do so, use the
> *--passalgo=sha256* or *--passalgo=sha512* options of the
> kickstart command *auth*; also, remove the *--enablemd5* option if
> present.
>
> If your installation does not use kickstart, use *authconfig* as
> described above, then change all passwords (including root)
> created after installation.
>
> Appropriate options were also added to *libuser*, *pam*, and
> *shadow-utils* to support these password hashing algorithms.
> *authconfig* configures necessary options automatically, so it is
> usually not necessary to modify them manually:
>
> *
>
> New values of the *crypt_style* option and new options for
> both *hash_rounds_min* and *hash_rounds_max* are now
> supported in the *[defaults]* section of
> |/etc/libuser.conf|. For more information, refer to *man
> libuser.conf*.
>
> *
>
> New options *sha256*, *sha512*, and *rounds* are now
> supported by the |pam_unix| PAM module. For more
> information, refer to |/usr/share/doc/pam-/|[pam
> version]|//txts/README.pam_unix|.
>
> *
>
> The following new options in |/etc/login.defs| are now
> supported by *shadow-utils*:
>
> o
>
> *ENCRYPT_METHOD* --- Specifies the encryption methos
> to be used. Valid values are *DES*, *MD5*, *SHA256*,
> *SHA512*. If this option is defined, *MD5_CRYPT_ENAB*
> is ignored.
>
> o
>
> *SHA_CRYPT_MIN_ROUNDS* and *SHA_CRYPT_MAX_ROUNDS* ---
> Specifies the number of hashing rounds to use if
> *ENCRYPT_METHOD* is set to *SHA256* or *SHA512*. If
> neither option is set, a default value is chosen by
> *glibc*. If only one option is set, the encryption
> method specifies the number of rounds.
>
> If both options are used, they specify an inclusive
> interval from which the number of rounds is chosen
> randomly. The selected number of rounds is limited to
> the inclusive interval [1000, 999999999].
>
> nfsroot
>
> *nfsroot* is fully supported in this update. This allows users to
> run Red Hat Enterprise Linux 5.2 with its root file system (|/|)
> mounted via NFS.
>
> *nfsroot* was originally introduced in Red Hat Enterprise Linux 5
> as a subset of the Technology Preview feature /Stateless Linux/.
> The full implementation of Stateless Linux remains a Technology
> Preview.
>
> At present, *nfsroot* has the following restrictions:
>
> *
>
> Writable directories that hold system files (for example,
> |/tmp|, |/var|, and |/etc|) must be replicated for each
> client and mounted independently with no sharing between
> clients. To do so, perform the following steps:
>
> 1.
>
> Configure the client's root file system to boot in
> read-only mode. To do so, replace *READONLY* with
> *yes* in |/etc/sysconfig/readonly-root|.
>
> 2.
>
> Run *cat /etc/rwtab* to view a default list of
> directories and files mounted by each client in the
> format */|[type] [path]|/*.
>
> */|[type]|/* can be either *empty* (an empty path),
> *dirs* (a directory tree that is copied, but is
> empty), or *files* (a file or directory tree copied
> intact).
>
> 3.
>
> If any other files or directories need to writable but
> are not in |/etc/rwtab|, list them in the same format
> (i.e. */|[type] [path]|/*) in a file under
> |/etc/rwtab.d/|.
>
> *
>
> SWAP is not supported over NFS.
>
> *
>
> SELinux cannot be enabled on *nfsroot* clients. In general,
> Red Hat does not recommend disabling SELinux. As such,
> customers must carefully consider the security implications
> of this action.
>
> OFED in comps.xml
>
> The group *OpenFabrics Enterprise Distribution* is now included in
> |comps.xml|. This group contains components used for
> high-performance networking and clustering (for example,
> InfiniBand and Remote Direct Memory Access).
>
> Further, the *Workstation* group has been removed from |comps.xml|
> in the Red Hat Enterprise Linux 5.2 Client version. This group
> only contained the |openib| package, which is now part of the
> *OpenFabrics Enterprise Distribution* group.
>
> Frysk
>
> The goal of the *frysk* project is to create an intelligent,
> distributed, always-on system monitoring and debugging tool that
> allows developers and system administrators to:
>
> *
>
> monitor running processes and threads (including creation
> and destruction events)
>
> *
>
> monitor the use of locking primitives
>
> *
>
> expose deadlocks
>
> *
>
> gather data
>
> *
>
> debug any given process by choosing it from a list or
> allowing *frysk* to open a source code (or other) window on
> a process that is crashing or misbehaving
>
> This updated version of *frysk* includes the following new utilities:
>
> *
>
> *fauxv*
>
> *
>
> *fdebuginfo*
>
> *
>
> *fdebugrpm*
>
> *
>
> *ferror*
>
> *
>
> *fexe*
>
> *
>
> *fmaps*
>
> In addition to this, *ftrace* can now perform signal and function
> symbol tracing. In previous releases, *ftrace* could only perform
> system call tracing.
>
> *frysk* was introduced in Red Hat Enterprise Linux 5, and is still
> included in this release as a Technology Preview. For more
> information about *frysk*, refer to http://sources.redhat.com/frysk/.
>
>
> Driver Updates
>
> General Driver/Platform Updates
>
> *
>
> The driver that allows hot docking/undocking of laptops is
> now updated to eliminate specific panic situations (for
> example, when a laptop fails to initialize correctly). This
> update also adds new *sysfs* entries, most notably:
>
> o
>
> |/sys/devices/platform/dock.0/docked| --- read-only;
> indicates whether the laptop is docked on a docking
> station.
>
> o
>
> |/sys/devices/platform/dock.0/undock| --- write-only;
> writing to this file initiates an "undock" request to
> the firmware.
>
> o
>
> |/sys/devices/platform/dock.0/uid| --- displays the
> unique ID (UID) of the docking station.
>
> *
>
> Added the necessary PCI IDs to support the /Intel E7221/
> Graphic Controller.
>
> *
>
> Added the necessary sub-device IDs to support the
> /PCI-Express icom WAN/ adapter.
>
> *
>
> |i2c-piix4| kernel module is now enabled to support the /AMD
> SBX00 SMBus/.
>
> *
>
> The following kernel configuration flags are now enabled to
> enhance kernel panic handling for /Intelligent Platform
> Management Interface/ (IPMI):
>
> o
>
> *CONFIG_IPMI_PANIC_EVENT* --- when a panic occurs, the
> IPMI message handler generates an IPMI event
> describing the panic to each interface registered with
> the message handler.
>
> o
>
> *CONFIG_IPMI_PANIC_STRING* --- when a panic occurs,
> OEM events containing the panic string are generated.
>
> In addition to this, IPMI now supports the /IBM Bladecenter
> QS21/ and /QS22/.
>
> *
>
> The |tlclk| driver is now included to support the /Intel
> MPCBL0050/ systems.
>
> *
>
> All PCI-X configuration registers (up to 4096 bytes) are now
> accessible.
>
> *
>
> The maximum length of the kernel command line is now 2,048
> bytes. To use this increased maximum length, upgrade the
> |grub| package.
>
> *
>
> /Dynamic acceleration/ is now supported. This allows a core
> to run at a higher-than-normal frequency when all CPUs (as a
> whole) are operating below maximum power.
>
> Graphics/Audio
>
> *
>
> /High-Definition Multimedia Interface/ (HDMI) audio is now
> supported on /AMD ATI/ integrated chipsets.
>
> *
>
> The /Intel/ Xorg driver now provides enhanced support for
> /i915/ (and later) chips. This driver is also the default
> driver now for such chips.
>
> Basic runtime multi-head support is provided by the |intel|
> Xorg driver. Selecting a resolution with the System =>
> Preferences => Screen Resolution tool
> (*gnome-display-properties*) will set that resolution on all
> connected outputs.
>
> *
>
> The /Sony/Philips Digital Interconnect Format/ (S/PDIF) port
> on the /Dell D/Dock Expansion Station/ is now supported by
> the /Dell M4300/ and /M6300 Precision Workstations/. This
> allows digital audio output through the S/PDIF port on the
> /Dell D/Dock Expansion Station/ when either the /M4300/ or
> /M6300/ is docked.
>
> Network
>
> *
>
> |bnx2x|: driver added to provide support for /bcm5710/ hardware.
>
> *
>
> |tg3|: updated to version 3.86. This update enables support
> for /BroadCom 5761/ and /5784/ devices.
>
> Storage
>
> *
>
> |lpfc|: updated to version 8.2.0.22. This update applies
> several *devloss* fixes, and enables support for the following:
>
> o
>
> 1, 2, 4, and 8GB auto-rate negotiation.
>
> o
>
> FC-SP DH-CHAP Authentication.
>
> o
>
> The latest /HBAnyware/ configuration utility, which is
> also part of the driver master kit. This enables
> GUI-based driver configuration (including fibre
> channel and TCP/IP remote storage area network
> management), diagnostics (loopback and diagnostics
> dump) and FC-SP/Authentication Diffie-Hellman CHAP
> (DH-CHAP).
>
> o
>
> LPe1250, LPe1252, LPe12000 and LPe12002 (2, 4, and 8Gb
> capable HBAs).
>
> o
>
> NPIV virtual ports.
>
> *
>
> |megaraid_sas|: updated to version 3.15. This applies
> several upstream changes, most notably:
>
> o
>
> Added the following module parameters:
>
> +
>
> *fast_load*: enables the driver to load faster
> by skipping physical device check.
>
> +
>
> *cmd_per_lun*: sets the maximum number of
> commands per logical unit.
>
> +
>
> *max_sectors*: sets the maximum number of
> sectors per I/O command.
>
> +
>
> *poll_mode_io*: enables support for polling
> (i.e. reduced interrupt operations). When
> *poll_mode_io* is set, commands will also be
> completed from the I/O path.
>
> o
>
> Added support for hibernation.
>
> o
>
> *SYNCHRONIZE_CACHE* is now blocked by the driver.
>
> *
>
> |aacraid|: updated to version 1.1.5-2453. This applies
> several upstream changes, most notably:
>
> o
>
> Fixed a bug that caused |aacraid| to use an incorrect
> *dma* mapping mask during firmware assert recovery.
>
> o
>
> Added the capability to issue a hardware reset to the
> adapter via *sysfs*. In line with this, the following
> check features were also added:
>
> +
>
> *check_interval* --- for checking adapter health
>
> +
>
> *update_interval* --- for revising time
> intervals used by adapter
>
> +
>
> *check_reset* --- for blocking adapter checks/resets
>
> o
>
> Added a *SYNCHRONIZE_CACHE* call to implement a more
> effective cache flushing schedule. This helps reduce
> application stalls resulting from multiple
> applications issuing I/O commands to the storage device.
>
> o
>
> Replaced all *if/else* packet formations with platform
> function calls.
>
> o
>
> VPD inquiry pages are now supported. This ensures that
> when an array is created, the metadata stored on the
> physical device is issued a unique serial number. This
> serial number remains constant throughout array
> morphing or migration to other controllers.
>
> *
>
> |qla2xxx|: updated to version 8.02.00-k5. This update to
> |qla2xxx| adds support for the following:
>
> o
>
> EHAFT, a QLogic host bus adapter mechanism that
> provides activity information about fibre channel devices.
>
> o
>
> /N_Port ID Virtualization/ (NPIV), which allows
> multiple N_Port IDs to share a single physical N_Port.
> This allows you to tie virtualized guests to
> fibre-channel identifiers, allowing those guests to
> migrate between hosts while retaining their access in
> the storage area network.
>
> o
>
> 8GB fibre-channel devices.
>
> o
>
> PCI EE error handling.
>
> This update also applies several improvements provided from
> upstream.
>
> *
>
> |mpt fusion|: updated to version 3.04.05. This update
> provides several changes, most notably:
>
> o
>
> /On-the-fly logging/ (via the *sysfs* *shost*
> attribute) is now supported.
>
> o
>
> Added new *sysfs* *shost* attributes that provide the
> following:
>
> +
>
> *board_name*
>
> +
>
> *board_assembly*
>
> +
>
> *board_tracer*
>
> +
>
> *unique_id*
>
> +
>
> *version_bios*
>
> +
>
> *version_fw*
>
> +
>
> *version_product*
>
> +
>
> *version_mpi*
>
> +
>
> *version_nvdata_default*
>
> +
>
> *version_nvdata_persistent*
>
> +
>
> *debug_level*
>
> +
>
> *io_delay*
>
> +
>
> *device_delay*
>
> o
>
> *task_abort* calls are no longer sent to hidden RAID
> components and volumes.
>
> o
>
> Changes related to fibre channel:
>
> +
>
> /Brocade/, a rebranded FC949E fibre channel
> controller, is now supported.
>
> +
>
> Link speeds are now displayed when the driver is
> loaded and whenever the link speed changes.
>
> +
>
> /High-priority request/ queueing is now used
> instead of the handshake/doorbell system when
> sending management requests for SAS or fibre
> channel.
>
> o
>
> Changes related to parallel SCSI:
>
> +
>
> /ATTO UL4D/, a rebranded SPI 1030 controller, is
> now supported.
>
> +
>
> *mptspi_target_destroy* is now declared as static.
>
>
> Kernel-Related Updates
>
> This release applies following kernel bug fixes:
>
> *
>
> Executing binaries with more than 2GB of debug information no
> longer fails.
>
> *
>
> When shutting down a database, all allocated hugepages are now
> released upon shutdown.
>
> *
>
> *invalidate_mapping_pages()* calls no longer cause soft lockups.
>
> *
>
> A bug that delayed *oomkill* from launching in a timely fashion
> (on systems with large memory) is now fixed.
>
> *
>
> A bug that caused soft lockup warnings when allocating memory on
> a system with large memory is now fixed.
>
> *
>
> 32-bit NFS clients can now correctly process 64-bit inode numbers.
>
> *
>
> The kernel now asserts /Data Terminal Ready/ (DTR) signals
> before printing to serial ports during boot time. DTR assertion
> is required by some devices. Kernel boot messages are now
> printed to serial consoles on such devices.
>
> *
>
> The kernel parameter *ide0=noprobe* no longer causes a kernel panic.
>
> This kernel update also features the following enhancements:
>
> *
>
> Added a new kernel parameter: |/proc/sys/vm/flush_mmap_pages|.
> This parameter specifies whether or not memory-mapped file pages
> should be flushed to disk by *kupdate* while the memory map is
> active. Valid values for this parameter are *1* (enable memory
> mapping by *kupdate*) and *0* (disable memory mapping by
> *kupdate*). The default value for this parameter is *1*.
>
> To configure this parameter, use *echo /|[1 or 0]|/
> /proc/sys/vm/flush_mmap_pages*. Setting this parameter to *0*
> does the following:
>
> o
>
> *kupdate* will not flush dirty memory-mapped file pages as
> long as the memory map is active.
>
> o
>
> All dirty file pages will be asynchronously flushed to
> disk only as soon as the memory map is deactivated.
>
> If you set |/proc/sys/vm/flush_mmap_pages| to *0*, it is
> advisable that you use another application to manually sync
> memory-mapped pages to disk.
>
> *
>
> Added a new kernel parameter:
> |/proc/sys/kernel/sched_interactivity|. This parameter allows
> you to tune the CPU scheduler's interactivity estimator. The
> interactivity estimator allows interactive processes to acquire
> more CPU time without causing CPU starvation in other processes.
>
> To configure this parameter, use *echo /|[interactivity_level]|/
> > /proc/sys/kernel/sched_interactivity*, where
> */|[interactivity_level]|/* can be any of the following:
>
> o
>
> *2* --- interactivity estimator is fully activated.
>
> o
>
> *1* --- provides a weaker affinity to interactive
> processes than *2*, but avoids CPU starvation under
> certain scheduling patterns.
>
> o
>
> *0* --- any bias or affinity towards interactive processes
> is disabled.
>
> *
>
> *kprobe* now supports *kretprobe_blacklist[]*.
>
> *
>
> /Core dump masking/ is now supported. This allows a core dump
> process to skip the shared memory segments of a process when
> creating a core dump file. This feature also allows you to
> select whether or not to dump anonymous shared memory for each
> process.
>
> When a process is dumped, all anonymous memory is written to a
> core file as long as the size of the core file isn't limited. In
> some cases, you may want to prevent some memory segments (such
> as huge shared memory) from being dumped. Conversely, you may
> also want to save file-backed memory segments into a core file,
> in addition to individual files.
>
> For these purposes, you can use
> |/proc//|[pid]|//coredump_filter| to specify which memory
> segments of the *[pid]* process is dumped. |coredump_filter| is
> a bitmask of memory types. If a bitmask is set, memory segments
> of the corresponding memory type are dumped.
>
> The following memory types are supported:
>
> o
>
> *0x0* --- anonymous private memory
>
> o
>
> *0x1* --- anonymous shared memory
>
> o
>
> *0x2* --- file-backed private memory
>
> o
>
> *0x3* --- file-backed shared memory
>
> To set a bitmask for *[pid]*, simply *echo* the corresponding
> bitmask to |/proc//|[pid]|//coredump_filter|. For example, to
> prevent a dump of all shared memory segments attached to process
> 1111, use:
>
> *echo 0x1 > /proc/1111/coredump_filter*
>
> The default value of |coredump_filter| is *0x3*, which specifies
> that all anonymous memory segments are dumped. Also, note that
> regardless of the bitmask status, MMIO pages (such as frame
> buffers) are never dumped and vDSO pages are always dumped
>
> When a new process is created, the process inherits the bitmask
> status from its parent. As such, it is recommended that you set
> up |coredump_filter| before the program runs. To do so, *echo*
> the desired bitmask to |/proc/self/coredump_filter| before
> running the program.
>
> *
>
> *audit* can now trace and display per-session user activity.
>
> *
>
> REV UDF file sizes larger than 1GB are now supported.
>
> *
>
> /Lock contention tracing/ and *lockdep* are now supported. These
> features provide in-depth information about spinlocks held in
> the kernel, which in turn help developers in driver debugging.
>
> In addition to these, this release also features the following kernel
> updates:
>
> *
>
> The enumeration order of PCI devices has changed on several
> platforms to have NICs appear in the order they are labeled on
> the chassis and how the BIOS numbers them. The affected
> platforms are as follows:
>
> o
>
> /Dell PowerEdge R900/
>
> o
>
> /HP ProLiant DL385 G2/
>
> o
>
> /HP ProLiant DL585 G2/
>
> o
>
> /HP Proliant DL580 G5/
>
> Note that this change affects new installations only. If you
> prefer the old enumeration order, use the kernel parameter
> *pci=nobfsort*.
>
> *
>
> You can now determine the resource limit (*rlimit*) of a
> process. To do so, run *cat /proc//|[pid]|//limits*.
>
> *
>
> The maximum soft lockup timeout is now increased from 60 seconds
> to 300 seconds for systems that have a large number of CPUs. A
> soft lockup occurs when a CPU reports a memory starvation while
> it is unable to access a memory node accessed by other CPUs.
>
> In this release, you can also adjust the trigger limit for soft
> lockup warnings. To do so, use the following command (as root):
>
> *echo /|[time]|/ > /proc/sys/kernel/softlockup_thresh*
>
> Replace */|[time]|/* with the desired number of seconds before a
> soft lockup warning should be triggered. By default, this value
> is set to 10 (seconds).
>
> *
>
> *show_mem()* output now includes the total number of pagecache
> pages.
>
> *
>
> MSI-X is no longer enabled by default. To enable MSI-X, use the
> kernel module parameter *ql2xenablemsix*.
>
>
> Virtualization
>
> This section contains information about updates made to Red Hat
> Enterprise Linux suite of Virtualization tools.
>
> Enhancements/Updates
>
> *
>
> When entering the second stage of a Windows^(TM) Server 2003
> installation, you no longer need to manually edit
> |/etc/xen//|[name of guest machine]|/| to continue. The
> current user interface now allows you to change media on
> CD-ROMs attached to the guest.
>
> *
>
> The Virtual Machine Manager (*virt-manager*) included in
> this release now allows users to specify kernel boot
> parameters to the paravirtualized guest installer.
>
> *
>
> A wrong address translation (which can lead to a crashed
> guest) no longer occurs if a guest is running a PAE kernel
> with more than 3,840MB of RAM. As such, you no longer need
> to use the 64-bit kernel if you intend to run guests with
> more than 4GB of physical RAM under Rapid Virtualization
> Indexing (RVI).
>
> *
>
> During the lifetime of *dom0*, you can now create guests
> (i.e. *xm create*) more than 32,750 times.
>
> *
>
> When using *virt-manager* to add disks to an existing guest,
> duplicate entries are no longer created in the guest's
> |/etc/xen//|[domain name]|/| configuration file.
>
> Known Issues
>
> *
>
> Migrating paravirtualized guests through *xm migrate
> /|[domain]|/ /|[dom0 IP address]|/* does not work.
>
> *
>
> Repeated live migration of paravirtualized guests between
> two hosts may cause one host to panic. If a host is rebooted
> after migrating a guest out of the system and before
> migrating the same guest back, the panic will not occur.
>
> *
>
> Running 16 cores or more using /AMD Rev F/ processors may
> result in system resets when performing fully-virtualized
> guest installations.
>
> *
>
> When installing Red Hat Enterprise Linux 5 on a fully
> virtualized SMP guest, the installation may freeze. This can
> occur when the host (*dom0*) is running Red Hat Enterprise
> Linux 5.2.
>
> To prevent this, set the guest to use a single processor
> using the install. You can do this by using the *--vcpus=1*
> option in *virt-install*. Once the installation is
> completed, you can set the guest to SMP by modifying the
> allocated *vcpus* in virt-manager.
>
>
> Technology Previews
>
> /Technology Preview/ features are currently /not/ supported under Red
> Hat Enterprise Linux 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.
>
> ALUA Mode on /EMC Clariion/
>
> Explicit active-passive failover (ALUA) mode using *dm-multipath*
> on /EMC Clariion/ storage is now available. This mode is provided
> as per T10 specifications, but is provided in this release only as
> a technology preview.
>
> For more information about T10, refer to http://www.t10.org.
>
> radeon_tp
>
> The |radeon_tp| driver is now included in this release as a
> Technology Preview. This driver enables the /ATI R500/R600/ chipsets.
>
> This driver also features the following capabilities:
>
> *
>
> Modesetting on /R500/R600/ chipsets
>
> *
>
> 2D acceleration on /R500/ chipsets
>
> *
>
> Shadow framebuffer acceleration on /R600/ chipsets
>
> FreeIPMI
>
> /FreeIPMI/ is now included in this update as a Technology Preview.
> FreeIPMI is a collection of Intelligent Platform Management IPMI
> system software. It provides in-band and out-of-band software,
> along with a development library conforming to the Intelligent
> Platform Management Interface (IPMI v1.5 and v2.0) standards.
>
> For more information about FreeIPMI, refer to
> http://www.gnu.org/software/freeipmi/
>
> TrouSerS and tpm-tools
>
> /TrouSerS/ and *tpm-tools* are included in this release to enable
> use of /Trusted Platform Module/ (TPM) hardware.TPM hardware
> features include (among others):
>
> *
>
> Creation, storage, and use of RSA keys securely (without
> being exposed in memory)
>
> *
>
> Verification of a platform's software state using
> cryptographic hashes
>
> /TrouSerS/ is an implementation of the Trusted Computing Group's
> Software Stack (TSS) specification. You can use TrouSerS to write
> applications that make use of TPM hardware. *tpm-tools* is a suite
> of tools used to manage and utilize TPM hardware.
>
> For more information about TrouSerS, refer to
> http://trousers.sourceforge.net/.
>
> eCryptfs
>
> |eCryptfs| is a stacked cryptographic file system for Linux. It
> mounts on individual directories in existing mounted lower file
> systems such as EXT3; there is no need to change existing
> partitions or file systems in order to start using |eCryptfs|.
>
> |eCryptfs| stores cryptographic metadata in the header of each
> file written to the lower file system. This enables you to copy
> encrypted files between hosts or directly onto backup media. Files
> encrypted and copied in this manner can be decrypted with the
> proper key.
>
> This release's version of |eCryptfs| provides several key
> management options, including protection based on passphrases and
> public keys. Below is a list of other fully functional features:
>
> *
>
> Interactive and non-interactive mounting.
>
> *
>
> Compatibility with SELinux.
>
> *
>
> Cryptographic metadata storage in both *xattrs* and file
> headers.
>
> At present, the following issues still exist with |eCryptfs|:
>
> *
>
> *direct_IO* is not implemented.
>
> *
>
> Complex I/O patterns within the *mmap* implementation in
> |eCryptfs| may cause data corruption in some cases.
>
> *
>
> |eCryptfs| cannot be used for root file systems.
>
> For more information about |eCryptfs|, refer to
> http://ecryptfs.sf.net. You can also refer to
> http://ecryptfs.sourceforge.net/README and
> http://ecryptfs.sourceforge.net/ecryptfs-faq.html for basic setup
> information.
>
> GFS2
>
> /GFS2/ is an incremental advancement of GFS. This update applies
> several significant improvements that require a change to the
> on-disk file system format. GFS file systems can be converted to
> GFS2 using the utility *gfs2_convert*, which updates the metadata
> of a GFS file system accordingly.
>
> While much improved since its introduction in Red Hat Enterprise
> Linux 5, GFS2 remains a Technology Preview. Benchmark tests
> indicate faster performance on the following:
>
> *
>
> heavy usage in a single directory and faster directory scans
> (Postmark benchmark)
>
> *
>
> synchronous I/O operations (*fstest* benchmark test
> indicates improved performance for messaging applications
> like TIBCO)
>
> *
>
> cached reads, as there is no longer any locking overhead
>
> *
>
> direct I/O to preallocated files
>
> *
>
> NFS file handle lookups
>
> *
>
> *df*, as allocation information is now cached
>
> In addition, GFS2 also features the following changes:
>
> *
>
> journals are now plain (though hidden) files instead of
> metadata. Journals can now be dynamically added as
> additional servers mount a file system.
>
> *
>
> quotas are now enabled and disabled by the mount option
> *quota=/|<on|off|account>|/*
>
> *
>
> *quiesce* is no longer needed on a cluster to replay
> journals for failure recovery
>
> *
>
> nanosecond timestamps are now supported
>
> *
>
> similar to ext3, GFS2 now supports the *data=ordered* mode
>
> *
>
> attribute settings *lsattr()* and *chattr()* are now
> supported via standard *ioctl()*
>
> *
>
> file system sizes above 16TB are now supported
>
> *
>
> GFS2 is a standard file system, and can be used in
> non-clustered configurations
>
> Stateless Linux
>
> Stateless Linux is a new way of thinking about how a system should
> be run and managed, designed to simplify provisioning and
> management of large numbers of systems by making them easily
> replaceable. This is accomplished primarily by establishing
> prepared system images which get replicated and managed across a
> large number of stateless systems, running the operating system in
> a read-only manner (refer to |/etc/sysconfig/readonly-root| for
> more details).
>
> In its current state of development, the Stateless features are
> subsets of the intended goals. As such, the capability remains as
> Technology Preview.
>
> It is highly recommended that those interested in testing
> stateless code read the HOWTO at
> http://fedoraproject.org/wiki/StatelessLinux/HOWTO and join
> [log in to unmask] <mailto:[log in to unmask]>.
>
> The enabling infrastructure pieces for Stateless Linux were
> originally introduced in Red Hat Enterprise Linux 5.
>
> AIGLX
>
> /AIGLX/ is a Technology Preview feature of the otherwise fully
> supported X server. It aims to enable GL-accelerated effects on a
> standard desktop. The project consists of the following:
>
> *
>
> A lightly modified X server.
>
> *
>
> An updated Mesa package that adds new protocol support.
>
> By installing these components, you can have GL-accelerated
> effects on your desktop with very few changes, as well as the
> ability to enable and disable them at will without replacing your
> X server. AIGLX also enables remote GLX applications to take
> advantage of hardware GLX acceleration.
>
> mac80211 802.11a/b/g WiFi protocol stack (mac80211)
>
> The /mac80211/ stack (formerly known as the /devicescape/d80211/
> stack) enables the |iwlwifi 4965GN| wireless driver for /Intel/
> Wifi Link 4965 hardware. This stack allows certain wireless
> devices to connect to any Wi-Fi network.
>
> Although the stack is already accepted upstream, the stability of
> this stack is yet to be verified through testing. As such, this
> stack is included in this release as a Technology Preview.
>
> FS-Cache
>
> /FS-Cache/ is a local caching facility for remote file systems
> that allows users to cache NFS data on a locally mounted disk. To
> set up the FS-Cache facility, install the |cachefilesd| RPM and
> refer to the instructions in
> |/usr/share/doc/cachefilesd-/|[version]|//README|.
>
> Replace /|[version]|/ with the corresponding version of the
> |cachefilesd| package installed.
>
> iSCSI Target
>
> The Linux target (tgt) framework allows a system to serve
> block-level SCSI storage to other systems that have a SCSI
> initiator. This capability is being initially deployed as a Linux
> iSCSI target, serving storage over a network to any iSCSI initiator.
>
> To set up the iSCSI target, install the |scsi-target-utils| RPM
> and refer to the instructions in:
>
> *
>
> |/usr/share/doc/scsi-target-utils-/|[version]|//README|
>
> *
>
> |/usr/share/doc/scsi-target-utils-/|[version]|//README.iscsi|
>
> Replace |/|[version]|/| with the corresponding version of the
> package installed.
>
> For more information, refer to *man tgtadm*.
>
> FireWire
>
> The |firewire-sbp2| module is still included in this update as a
> Technology Preview. This module enables connectivity with FireWire
> storage devices and scanners.
>
> At present, FireWire does not support the following:
>
> *
>
> IPv4
>
> *
>
> /pcilynx/ host controllers
>
> *
>
> multi-LUN storage devices
>
> *
>
> non-exclusive access to storage devices
>
> In addition, the following issues still exist in FireWire:
>
> *
>
> a memory leak in the |SBP2| driver may cause the machine to
> become unresponsive.
>
> *
>
> a code in this version does not work properly in big-endian
> machines. This could lead to unexpected behavior in PowerPC.
>
>
> Resolved Issues
>
> *
>
> /Netapp/ devices can now complete failback (after a
> previously-failed path is restored) within a reasonable time
> with the default *dm-multipath* configuration.
>
> *
>
> *system-config-kickstart* now supports package selection through
> the Red Hat Network plugin.
>
> *
>
> *kudzu* can now properly parse |ifcfg-/|*|/| files that contain
> quotes around the *HWADDR* or *SUBCHANNELS* parameters. In
> addition, *kudzu* no longer modifies network configurations on
> device change if the device's *HWADDR* is not specified.
>
> *
>
> Running *netstat* with the *-A inet* or *-A inet6* option (on a
> system where |sctp| was not added to the kernel) no longer
> terminates abnormally. Note, however, that *netstat* will
> display the following warning message when invoked with the *-s*
> option:
>
> netstat: no support for `AF INET (sctp)' on this system.
>
> *
>
> The *nohide* export option is no longer required on referral
> exports (i.e. exports that specify a referral server). For more
> information on bound mounts, refer to *man 5 exports*.
>
> *
>
> The priority callouts of *dm-multipath* are now statically
> compiled. This fixes a problem that occurs when running
> *dm-multipath* on devices containing the root file system, which
> caused such devices to freeze during fibre-channel path faults.
>
> *
>
> *parted* can now understand and correctly print out Xen Virtual
> Device (XVD) partition labels. This enables paravirtualized
> guests to now use the *parted* utility. As such, you no longer
> need to use *parted* within *dom0* to configure disk partitions
> on paravirtualized guests.
>
> *
>
> When upgrading to Red Hat Enterprise Linux 5.2 via Red Hat
> Network, you no longer need to manually import the redhat-beta
> key prior to upgrading.
>
> *
>
> It is no longer necessary to use the kernel parameter
> *pci=nommconf* for systems that use the /AMD 8132/ or /HT 1000/
> chipsets.
>
> Note that the system will still restrict such bridges to using
> the /PortIO CF8/CFC/ mechanism. However, bridges (including
> those on the same platform) that respond correctly to *MMCONFIG*
> cycles will use *MMCONFIG*, provided that the platform's BIOS
> correctly supports *MMCONFIG*.
>
> *
>
> Previous versions of Red Hat Enterprise Linux 5 on /HP BL860c/
> blade systems could hang during the IP information request stage
> of installation. When this occurred, you were required to reboot
> and perform the installation with Ethernet autonegotiation disabled.
>
> This issue is now fixed in this update.
>
> *
>
> /Gemalto 64K/ smart cards now use readers compliant with
> Chip/Smart Card Interface Devices (CCID). Previously, this smart
> card used the built-in e-gate reader, which essentially meant
> that the card and reader were being inserted at the same time.
> As a result, *coolkey* did not consistently recognize /Gemalto
> 64K/ smart cards.
>
> In this update, *coolkey* now works correctly with /Gemalto 64k/
> smart cards.
>
>
> Known Issues
>
> *
>
> A bug in the updated |/etc/udev/rules.d/50-udev.rules| file
> prevents the creation of persistent names for tape devices with
> numbers higher than 9 in their names. For example, a persistent
> name will not be created for a tape device with a name of |nst12|.
>
> To work around this, add an asterisk (*) after each occurrence
> of the string *nst[0-9]* in |/etc/udev/rules.d/50-udev.rules|.
>
> *
>
> /Nested paging/ can only translate 32-bit guest virtual
> addresses. This is because of a hardware feature that exists
> only in 32-bit physical address extensions (PAE).
>
> Also, note that on an /AMD NPT/ system used as a PAE host,
> guests cannot have more than 4GB of memory.
>
> *
>
> The *smartctl* tool cannot properly read SMART parameters from
> SATA devices.
>
> *
>
> When using *dm-multipath*, if *features "1 queue_if_no_path"* is
> specified in |/etc/multipath.conf| then any process that issues
> I/O will hang until one or more paths are restored.
>
> To avoid this, set *no_path_retry /|[N]|/* in
> |/etc/multipath.conf| (where */|[N]|/* is the number of times
> the system should retry a path). When you do, remove the
> *features "1 queue_if_no_path"* option from
> |/etc/multipath.conf| as well.
>
> *
>
> Enabling multiple installed versions of the same kernel module
> is not supported. In addition to this, a bug in the way kernel
> module versions are parsed can sometimes result in enabling an
> older version of the same kernel module.
>
> It is recommended that when you install a newer version of an
> installed kernel module, you should delete the older one first.
>
> *
>
> Executing *kdump* on an /IBM Bladecenter QS21/ or /QS22/
> configured with NFS root will fail. To avoid this, specify an
> NFS dump target in |/etc/kdump.conf|.
>
> *
>
> /IBM T60/ laptops will power off completely when suspended and
> plugged into a docking station. To avoid this, boot the system
> with the argument *acpi_sleep=s3_bios*.
>
> *
>
> The /QLogic iSCSI Expansion Card/ for the /IBM Bladecenter/
> provides both ethernet and iSCSI functions. Some parts on the
> card are shared by both functions. However, the current
> |qla3xxx| and |qla4xxx| drivers support ethernet and iSCSI
> functions individually. Both drivers do not support the use of
> ethernet and iSCSI functions simultaneously.
>
> Because of this limitation, successive resets (via consecutive
> *ifdown*/*ifup* commands) may hang the device. To avoid this,
> allow a 10-second interval after an *ifup* before issuing an
> *ifdown*. Also, allow the same 10-second interval after an
> *ifdown* before issuing an *ifup*. This interval allows ample
> time to stabilize and re-initialize all functions when an *ifup*
> is issued.
>
> *
>
> Laptops equipped with the /Cisco Aironet MPI-350/ wireless may
> hang trying to get a DHCP address during any network-based
> installation using the wired ethernet port.
>
> To work around this, use local media for your installation.
> Alternatively, you can disable the wireless card in the laptop
> BIOS prior to installation (you can re-enable the wireless card
> after completing the installation).
>
> *
>
> Boot-time logging to |/var/log/boot.log| is not available in Red
> Hat Enterprise Linux 5.2.
>
> *
>
> The system may not successfully reboot into a *kexec*/*kdump*
> kernel if X is running and using a driver other than /vesa/.
> This problem only exists with /ATI Rage XL/ graphics chipsets.
>
> If X is running on a system equipped with /ATI Rage XL/, ensure
> that it is using the /vesa/ driver in order to successfully
> reboot into a *kexec*/*kdump* kernel.
>
> *
>
> When using Red Hat Enterprise Linux 5.2 on a machine with an
> /nVidia CK804/ chipset installed, the following kernel messages
> may appear:
>
> kernel: assign_interrupt_mode Found MSI capability
> kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
>
>
> These messages indicate that certain PCI-E ports are not
> requesting IRQs. Further, these messages do not, in any way,
> affect the operation of the machine.
>
> *
>
> Removable storage devices (such as CDs and DVDs) do not
> automatically mount when you are logged in as root. As such, you
> will need to manually mount the device through the graphical
> file manager.
>
> Alternatively, you can run the following command to mount a
> device to |/media|:
>
> mount /dev//|[device name]|/ /media
>
> *
>
> The /IBM System z/ does not provide a traditional Unix-style
> physical console. As such, Red Hat Enterprise Linux 5.2 for the
> /IBM System z/ does not support the /firstboot/ functionality
> during initial program load.
>
> To properly initialize setup for Red Hat Enterprise Linux 5.2 on
> the /IBM System z/, run the following commands after installation:
>
> o
>
> */usr/bin/setup* --- provided by the |setuptool| package.
>
> o
>
> */usr/bin/rhn_register* --- provided by the |rhn-setup|
> package.
>
> *
>
> 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
> lrwxrwxrwx 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
>
> *
>
> Running the *multipath* command with the *-ll* option can cause
> the command to hang if one of the paths is on a blocking device.
> Note that the driver does not fail a request after some time if
> the device does not respond.
>
> This is caused by the cleanup code, which waits until the path
> checker request either completes or fails. To display the
> current *multipath* state without hanging the command, use
> *multipath -l* instead.
>
> *
>
> The system may not successfully reboot into a *kexec*/*kdump*
> kernel if X is running and using a driver other than /vesa/.
> This problem only exists with /ATI Rage XL/ graphics chipsets.
>
> If X is running on a system equipped with /ATI Rage XL/, ensure
> that it is using the /vesa/ driver in order to successfully
> reboot into a *kexec*/*kdump* kernel.
>
> *
>
> When running the bare-metal (non-Virtualized) kernel, the X
> server may not be able to retrieve *EDID* information from the
> monitor. When this occurs, the graphics driver will be unable to
> display resolutions highers than 800x600.
>
> To work around this, add the following line to the
> *ServerLayout* section of |/etc/X11/xorg.conf|:
>
> Option "Int10Backend" "x86emu"
>
> *
>
> Upgrading |pm-utils| from a Red Hat Enterprise Linux 5.2 Beta
> version of |pm-utils| will fail, resulting in the following error:
>
> error: unpacking of archive failed on file /etc/pm/sleep.d: cpio: rename
>
>
> To prevent this from occurring, delete the |/etc/pm/sleep.d/|
> directory prior to upgrading. If |/etc/pm/sleep.d| contains any
> files, move those files to |/etc/pm/hooks/|.
>
> *
>
> 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.
>
> *
>
> When upgrading from Red Hat Enterprise Linux 4.6 to Red Hat
> Enterprise Linux 5.1 (or later), a warning error will appear
> stating that the kernel module |mptscsi| was not found. To
> prevent this, edit |/etc/modprobe.conf| by changing *mptscsi* to
> *mptscsih* before upgrading.
>
> ( /x86/ )
>
|