I have included the Upstream Vendor release notes. This includes both the
original and Update 1 notes.
-Connie Sieh
-Jarek Polok
----------------------------------------------------------------------------
Scientific Linux 4.1 for ia64 August 08 , 2005
It may be possible to upgrade to this release from Scientific Linux 3.0.5
ia64 if the anaconda installer is used. Yum is known to NOT work.
*This includes Update 1.
See SL.documentation/ for the vendor release notes.
See 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
/contrib
SRPMS
HARDWARE REQUIREMENTS
LIMITATIONS
INFO
ERRATA
_____________________________________________________________________________
DOWNLOAD INFO
_____________________________________________________________________________
ftp://ftp.scientificlinux.org/linux/scientific/41/ia64/
ftp://ftp.scientificlinux.org/linux/scientific/41/iso/ia64/
rsync access available upon request.
-------------------------------------------------------------------------
ADDED compared to vendor
-------------------------------------------------------------------------
APT
apt-0.5.15cnc6-9.SL.ia64.rpm
apt-devel-0.5.15cnc6-9.SL.ia64.rpm
apt-sourceslist-40-1.SL.ia64.rpm
* apt-autoupdate-1-5.SL.noarch.rpm
* apt-firstboot-1-5.SL.noarch.rpm
* apt-scripts-1-5.SL.noarch.rpm
*Cluster Suite
*
* ccs-1.0.0-0.ia64.rpm
* ccs-devel-1.0.0-0.ia64.rpm
* cman-1.0.0-0.ia64.rpm
* cman-kernel-2.6.9-36.0.ia64.rpm
* cman-kernel-smp-2.6.9-36.0.ia64.rpm
* cman-kernheaders-2.6.9-36.0.ia64.rpm
* dlm-1.0.0-0.ia64.rpm
* dlm-devel-1.0.0-0.ia64.rpm
* dlm-kernel-2.6.9-34.0.ia64.rpm
* dlm-kernel-smp-2.6.9-34.0.ia64.rpm
* dlm-kernheaders-2.6.9-34.0.ia64.rpm
* fence-1.32.1-0.ia64.rpm
* gulm-1.0.0-0.ia64.rpm
* gulm-devel-1.0.0-0.ia64.rpm
* iddev-2.0.0-0.ia64.rpm
* iddev-devel-2.0.0-0.ia64.rpm
* ipvsadm-1.24-6.ia64.rpm
* magma-1.0.0-0.ia64.rpm
* magma-devel-1.0.0-0.ia64.rpm
* magma-plugins-1.0.0-0.ia64.rpm
* perl-Net-Telnet-3.03-3.noarch.rpm
* piranha-0.8.0-1.ia64.rpm
* rgmanager-1.9.34-1.ia64.rpm
* system-config-cluster-1.0.12-1.0.noarch.rpm
*GFS
*
* GFS-6.1.0-0.ia64.rpm
* GFS-kernel-2.6.9-35.5.ia64.rpm
* GFS-kernel-smp-2.6.9-35.5.ia64.rpm
* GFS-kernheaders-2.6.9-35.5.ia64.rpm
* gnbd-1.0.0-0.ia64.rpm
* gnbd-kernel-2.6.9-8.27.ia64.rpm
* gnbd-kernel-smp-2.6.9-8.27.ia64.rpm
* gnbd-kernheaders-2.6.9-8.27.ia64.rpm
* lvm2-cluster-2.01.09-5.0.RHEL4.ia64.rpm
icewm
A lightweight window manager for the X Window System.
icewm-1.2.20-2.ia64.rpm
icewm-l10n-1.2.20-2.ia64.rpm
OpenAFS
* As of Scientific Linux 4.1 OpenAFS is working on all architectures. Some
* architectures may work better or faster than others, but all work.
*
* openafs-1.3.82-3.SL.ia64.rpm
* openafs-client-1.3.82-3.SL.ia64.rpm
* openafs-compat-1.3.82-3.SL.ia64.rpm
* openafs-debug-1.3.82-3.SL.ia64.rpm
* openafs-devel-1.3.82-3.SL.ia64.rpm
openafs-firstboot-1.2.11-5.SL.noarch.rpm
* openafs-kernel-source-1.3.82-3.SL.ia64.rpm
* openafs-kpasswd-1.3.82-3.SL.ia64.rpm
* openafs-krb5-1.3.82-3.SL.ia64.rpm
* openafs-server-1.3.82-3.SL.ia64.rpm
* kernel-module-openafs-2.6.9-11.EL-1.3.82-3.SL.ia64.rpm
* kernel-module-openafs-2.6.9-11.ELsmp-1.3.82-3.SL.ia64.rpm
These perl modules have been added as they are useful. They came from CERN
perl-BSD-Resource-1.24-1.ia64.rpm
perl-Compress-Zlib-1.16-12.ia64.rpm
perl-MailTools-1.62-1.noarch.rpm
perl-Parse-RecDescent-1.94-1.noarch.rpm
perl-Proc-ProcessTable-0.39-1.ia64.rpm
perl-SQL-Statement-1.06-1.noarch.rpm
perl-TermReadKey-2.20-12.ia64.rpm
perl-Text-CSV_XS-0.23-1.ia64.rpm
perl-Text-Template-1.44-1.noarch.rpm
perl-TimeDate-2.22-1.noarch.rpm
perl-Tk-804.027-1.ia64.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.
Release 4 has everything setup correctly
SL_disable_print_notification-1.0-4.noarch.rpm
Removes eggcups notification. Not installed by default.
SL_enable_serialconsole-3.1-3.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_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_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
SL_no_colorls-1.0-2.noarch.rpm
Turns off "color" of ls. Not installed by default.
SL_rpm_show_arch-1.0-1.noarch.rpm
Adds arch to "rpm -qa" listing.
SL_sendmail_accept-1.1-1.noarch.rpm
Changes Sendmail config so that it allows incomming mail.
Not installed by default.
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-40-2 has the check of 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.
* yum-conf-4.1-2.SL has a new bugfix repo in it
* 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-2.2.2-1.SL.noarch.rpm
* yum-conf-41-4.SL.noarch.rpm
createrepo-0.4.2-1.noarch.rpm
* yum-conf-41-2.SL has a new bugfix repo in it
MISC
Added these rpms because they are important but RedHat removed them.
gv-3.5.8-29.ia64.rpm from Fedora Core 3
jpilot-0.99.7-2.ia64.rpm from Fedora Core 3
ncurses4-5.0-12.ia64.rpm from Scientific Linux 3.0.x
pine-4.62-1.SL.ia64.rpm from Dag's Repository
readline41-4.1-17.ia64.rpm from Scientific Linux 3.0.x
*Documentation
*
* rhd-dg-en-4-2.SL1.noarch.rpm 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
-------------------------------------------------------------------------
Installer(anaconda)
Added support for sites
Updated icons
Added support for installation of openafs for smp on smp systems
* Updated to Update 1
* Fixes for cd disk swapping for sites
* anaconda-10.1.1.19-1SL.ia64.rpm
* anaconda-runtime-10.1.1.19-1SL.ia64.rpm
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.
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, not suggested
for use
indexhtml-4-2.SL.1.noarch.rpm
redhat-artwork-0.120-1.SL.5.ia64.rpm
redhat-logos-1.1.25-1.SL.8.noarch.rpm
* sl-release-4.1-4.noarch.rpm
These rpm's are not required to be changed by the vendor, we made minor customizations
desktop-backgrounds-basic-2.0-26.2.3SL.noarch.rpm
desktop-backgrounds-extra-2.0-26.2.3SL.noarch.rpm
-----------------------------------------------------------------------------
/contrib
-----------------------------------------------------------------------------
RPMS provided by users that either cannot go in main release or are
in testing .
/contrib/RPMS/
/contrib/SRPMS/
---------------------------------------------------------------------------
/../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
-----------------------------------------------------------------------------
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.
openafs
see above info in the AFS section
-----------------------------------------------------------------------------
INFO
-----------------------------------------------------------------------------
Web Site
https://www.scientificlinux.org
FTP
ftp://ftp.scientificlinux.org/linux/scientific/41/
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 errata
-----------------------------------------------------------------------------
ERRATA rebuilt from SRPMS
-----------------------------------------------------------------------------
* fetchmail-6.2.5-6.el4.2.ia64.rpm
* httpd-2.0.52-12.1.ent.ia64.rpm
* httpd-l-6.2.5-6.el4.2.ia64.rpm
* httpd-2.0.52-12.1.ent.ia64.rpm
* httpd-devel-2.0.52-12.1.ent.ia64.rpm
* httpd-manual-2.0.52-12.1.ent.ia64.rpm
* httpd-suexec-2.0.52-12.1.ent.ia64.rpm
* kdelibs-3.3.1-3.11.ia64.rpm
* kdelibs-3.3.1-3.11.i386.rpm
* kdelibs-devel-3.3.1-3.11.ia64.rpm
* mod_ssl-2.0.52-12.1.ent.ia64.rpmdevel-2.0.52-12.1.ent.x86_64.rpm
* httpd-manual-2.0.52-12.1.ent.ia64.rpm
* httpd-suexec-2.0.52-12.1.ent.ia64.rpm
* kdelibs-3.3.1-3.11.ia64.rpm
* kdelibs-3.3.1-3.11.i386.rpm
* kdelibs-devel-3.3.1-3.11.ia64.rpm
* mod_ssl-2.0.52-12.1.ent.ia64.rpm
* cpio-2.5-8.RHEL4.ia64.rpm
* devhelp-0.9.2-2.4.6.SL4.ia64.rpm
* devhelp-devel-0.9.2-2.4.6.SL4.ia64.rpm
* firefox-1.0.6-1.4.1.ia64.rpm
* kdenetwork-3.3.1-2.3.ia64.rpm
* kdenetwork-devel-3.3.1-2.3.ia64.rpm
* kdenetwork-nowlistening-3.3.1-2.3.ia64.rpm
* mozilla-1.7.10-1.4.1.ia64.rpm
* mozilla-chat-1.7.10-1.4.1.ia64.rpm
* mozilla-devel-1.7.10-1.4.1.ia64.rpm
* mozilla-dom-inspector-1.7.10-1.4.1.ia64.rpm
* mozilla-js-debugger-1.7.10-1.4.1.ia64.rpm
* mozilla-mail-1.7.10-1.4.1.ia64.rpm
* mozilla-nspr-1.7.10-1.4.1.ia64.rpm
* mozilla-nspr-1.7.10-1.4.1.i386.rpm
* mozilla-nspr-devel-1.7.10-1.4.1.ia64.rpm
* mozilla-nss-1.7.10-1.4.1.ia64.rpm
* mozilla-nss-1.7.10-1.4.1.i386.rpm
* mozilla-nss-devel-1.7.10-1.4.1.ia64.rpm
* thunderbird-1.0.6-1.4.1.ia64.rpm
* zlib-1.2.1.2-1.2.ia64.rpm
* zlib-1.2.1.2-1.2.i386.rpm
* zlib-devel-1.2.1.2-1.2.ia64.rpm
* zlib-devel-1.2.1.2-1.2.i386.rpm
firefox-1.0.3-1.4.1.ia64.rpm
HelixPlayer-1.0.4-1.1.EL4.2.i386.rpm
kernel-2.6.9-5.0.5.EL.ia64.rpm
kernel-devel-2.6.9-5.0.5.EL.ia64.rpm
kernel-doc-2.6.9-5.0.5.EL.noarch.rpm
kernel-smp-2.6.9-5.0.5.EL.ia64.rpm
kernel-smp-devel-2.6.9-5.0.5.EL.ia64.rpm
xloadimage-4.1-34.RHEL4.ia64.rpm
gaim-1.2.1-4.el4.ia64.rpm
curl-7.12.1-5.rhel4.i386.rpm
curl-7.12.1-5.rhel4.ia64.rpm
curl-devel-7.12.1-5.rhel4.ia64.rpm
gdk-pixbuf-0.22.0-16.el4.i386.rpm
gdk-pixbuf-0.22.0-16.el4.ia64.rpm
gdk-pixbuf-devel-0.22.0-16.el4.ia64.rpm
mysql-4.1.10a-1.RHEL4.1.i386.rpm
mysql-4.1.10a-1.RHEL4.1.ia64.rpm
mysql-bench-4.1.10a-1.RHEL4.1.ia64.rpm
mysql-devel-4.1.10a-1.RHEL4.1.ia64.rpm
mysql-server-4.1.10a-1.RHEL4.1.ia64.rpm
telnet-0.17-31.EL4.2.ia64.rpm
telnet-server-0.17-31.EL4.2.ia64.rpm
evolution-2.0.2-14.ia64.rpm
evolution-devel-2.0.2-14.ia64.rpm
devhelp-0.9.2-2.4.3.ia64.rpm
devhelp-devel-0.9.2-2.4.3.ia64.rpm
ethereal-0.10.10-1.EL4.1.ia64.rpm
ethereal-gnome-0.10.10-1.EL4.1.ia64.rpm
firefox-1.0.2-1.4.1.ia64.rpm
ImageMagick-6.0.7.1-10.ia64.rpm
ImageMagick-c++-6.0.7.1-10.ia64.rpm
ImageMagick-c++-devel-6.0.7.1-10.ia64.rpm
ImageMagick-devel-6.0.7.1-10.ia64.rpm
ImageMagick-perl-6.0.7.1-10.ia64.rpm
ipsec-tools-0.3.3-6.ia64.rpm
kdelibs-devel-3.3.1-3.6.ia64.rpm
kdelibs-3.3.1-3.6.i386.rpm
kdelibs-3.3.1-3.6.ia64.rpm
libexif-0.5.12-5.1.i386.rpm
libexif-0.5.12-5.1.ia64.rpm
libexif-devel-0.5.12-5.1.ia64.rpm
mailman-2.1.5-33.rhel4.ia64.rpm
mozilla-1.7.6-1.4.1.ia64.rpm
mozilla-chat-1.7.6-1.4.1.ia64.rpm
mozilla-devel-1.7.6-1.4.1.ia64.rpm
mozilla-dom-inspector-1.7.6-1.4.1.ia64.rpm
mozilla-js-debugger-1.7.6-1.4.1.ia64.rpm
mozilla-mail-1.7.6-1.4.1.ia64.rpm
mozilla-nspr-1.7.6-1.4.1.ia64.rpm
mozilla-nspr-devel-1.7.6-1.4.1.ia64.rpm
mozilla-nss-1.7.6-1.4.1.ia64.rpm
mozilla-nss-devel-1.7.6-1.4.1.ia64.rpm
thunderbird-1.0.2-1.4.2.ia64.rpm
postfix-2.1.5-4.2.RHEL4.ia64.rpm
postfix-pflogsumm-2.1.5-4.2.RHEL4.ia64.rpm
squid-2.5.STABLE6-3.4E.5.ia64.rpm
tetex-2.0.2-22.EL4.4.ia64.rpm
tetex-afm-2.0.2-22.EL4.4.ia64.rpm
tetex-doc-2.0.2-22.EL4.4.ia64.rpm
tetex-dvips-2.0.2-22.EL4.4.ia64.rpm
tetex-fonts-2.0.2-22.EL4.4.ia64.rpm
tetex-latex-2.0.2-22.EL4.4.ia64.rpm
tetex-xdvi-2.0.2-22.EL4.4.ia64.rpm
gaim-1.1.4-1.EL4.ia64.rpm
libaio-0.3.103-3.ia64.rpm
libaio-devel-0.3.103-3.ia64.rpm
mozilla-1.7.3-19.EL4.ia64.rpm
mozilla-chat-1.7.3-19.EL4.ia64.rpm
mozilla-devel-1.7.3-19.EL4.ia64.rpm
mozilla-dom-inspector-1.7.3-19.EL4.ia64.rpm
mozilla-js-debugger-1.7.3-19.EL4.ia64.rpm
mozilla-mail-1.7.3-19.EL4.ia64.rpm
mozilla-nspr-1.7.3-19.EL4.ia64.rpm
mozilla-nspr-devel-1.7.3-19.EL4.ia64.rpm
mozilla-nss-1.7.3-19.EL4.ia64.rpm
mozilla-nss-devel-1.7.3-19.EL4.ia64.rpm
HelixPlayer-1.0.3-1.i386.rpm
firefox-1.0.1-1.4.3.ia64.rpm
cups-1.1.22-0.rc1.9.6.ia64.rpm
cups-devel-1.1.22-0.rc1.9.6.ia64.rpm
cups-libs-1.1.22-0.rc1.9.6.ia64.rpm
emacs-21.3-19.EL.1.ia64.rpm
emacs-common-21.3-19.EL.1.ia64.rpm
emacs-el-21.3-19.EL.1.ia64.rpm
emacs-leim-21.3-19.EL.1.ia64.rpm
emacs-nox-21.3-19.EL.1.ia64.rpm
enscript-1.6.1-28.3.ia64.rpm
ethereal-0.10.9-1.EL4.1.ia64.rpm
ethereal-gnome-0.10.9-1.EL4.1.ia64.rpm
exim-4.43-1.RHEL4.3.ia64.rpm
exim-doc-4.43-1.RHEL4.3.ia64.rpm
exim-mon-4.43-1.RHEL4.3.ia64.rpm
exim-sa-4.43-1.RHEL4.3.ia64.rpm
gpdf-2.8.2-4.3.ia64.rpm
htdig-3.2.0b6-3.40.1.ia64.rpm
htdig-web-3.2.0b6-3.40.1.ia64.rpm
ImageMagick-6.0.7.1-6.ia64.rpm
ImageMagick-c++-6.0.7.1-6.ia64.rpm
ImageMagick-c++-devel-6.0.7.1-6.ia64.rpm
ImageMagick-devel-6.0.7.1-6.ia64.rpm
ImageMagick-perl-6.0.7.1-6.ia64.rpm
kdegraphics-3.3.1-3.3.ia64.rpm
kdegraphics-devel-3.3.1-3.3.ia64.rpm
kdelibs-3.3.1-3.3.ia64.rpm
kdelibs-devel-3.3.1-3.3.ia64.rpm
kernel-2.6.9-5.0.3.EL.ia64.rpm
kernel-devel-2.6.9-5.0.3.EL.ia64.rpm
kernel-smp-2.6.9-5.0.3.EL.ia64.rpm
kernel-smp-devel-2.6.9-5.0.3.EL.ia64.rpm
krb5-devel-1.3.4-10.ia64.rpm
krb5-libs-1.3.4-10.ia64.rpm
krb5-server-1.3.4-10.ia64.rpm
krb5-workstation-1.3.4-10.ia64.rpm
libtiff-3.6.1-8.ia64.rpm
libtiff-devel-3.6.1-8.ia64.rpm
mailman-2.1.5-31.rhel4.ia64.rpm
mod_python-3.1.3-5.1.ia64.rpm
perl-5.8.5-12.1.ia64.rpm
perl-DBI-1.40-8.ia64.rpm
perl-suidperl-5.8.5-12.1.1.ia64.rpm
php-4.3.9-3.2.ia64.rpm
php-devel-4.3.9-3.2.ia64.rpm
php-domxml-4.3.9-3.2.ia64.rpm
php-gd-4.3.9-3.2.ia64.rpm
php-imap-4.3.9-3.2.ia64.rpm
php-ldap-4.3.9-3.2.ia64.rpm
php-mbstring-4.3.9-3.2.ia64.rpm
php-mysql-4.3.9-3.2.ia64.rpm
php-ncurses-4.3.9-3.2.ia64.rpm
php-odbc-4.3.9-3.2.ia64.rpm
php-pear-4.3.9-3.2.ia64.rpm
php-pgsql-4.3.9-3.2.ia64.rpm
php-snmp-4.3.9-3.2.ia64.rpm
php-xmlrpc-4.3.9-3.2.ia64.rpm
postgresql-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-contrib-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-devel-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-docs-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-jdbc-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-libs-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-pl-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-python-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-server-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-tcl-7.4.7-2.RHEL4.1.ia64.rpm
postgresql-test-7.4.7-2.RHEL4.1.ia64.rpm
python-2.3.4-14.1.ia64.rpm
python-devel-2.3.4-14.1.ia64.rpm
python-docs-2.3.4-14.1.ia64.rpm
python-tools-2.3.4-14.1.ia64.rpm
squid-2.5.STABLE6-3.4E.3.ia64.rpm
squirrelmail-1.4.3a-9.EL4.noarch.rpm
thunderbird-1.0-1.1.EL4.ia64.rpm
tkinter-2.3.4-14.1.ia64.rpm
vim-common-6.3.046-0.40E.4.ia64.rpm
vim-enhanced-6.3.046-0.40E.4.ia64.rpm
vim-minimal-6.3.046-0.40E.4.ia64.rpm
vim-X11-6.3.046-0.40E.4.ia64.rpm
xpdf-3.00-11.5.ia64.rpm
From [log in to unmask] Wed Aug 10 17:23:41 2005
Date: Wed, 10 Aug 2005 17:20:51 -0500
From: root <[log in to unmask]>
To: [log in to unmask]
Scientific Linux 4.1 Release Notes
---------------------------------------------------------------------------
Introduction
The following topics are covered in this document:
o Changes to the Scientific Linux installation program (Anaconda)
o General information
o Changes to drivers and hardware support
o Changes to packages
Installation Related Notes
The following section includes information specific to installation of
Scientific Linux and the Anaconda installation program.
Note
In order to upgrade an already-installed Scientific Linux 4.x system
to 4.1, you must use yum or apt to update those packages that
have changed.
You may use Anaconda to perform a fresh installation of Scientific
Linux 4.1 or to perform an upgrade from the latest updated version
of Scientific Linux 3.0.x to Scientific Linux 4.x.
General Information
This section contains general information not specific to any other
section of this document.
o The openssh-3.9p1 package included in Scientific Linux 4.x
introduced two different modes of X11 forwarding: trusted and
untrusted. In the default Scientific Linux 4.x configuration,
passing the -X flag to /usr/bin/ssh (or using the "ForwardX11 on"
configuration option) enables untrusted X11 forwarding. This mode
restricts the X11 protocol to prevent a malicious application using a
forwarded SSH connection from compromising the security of the local
X11 server (for example, by performing keystroke monitoring); but few
X11 applications are usable in this mode.
In Scientific Linux 4.1, the default configuration of
the openssh client has been changed such that passing the -X flag
enables trusted X11 forwarding. The trusted forwarding mode allows all
X applications to work correctly when forwarded over an SSH
connection; but, as with previous releases of Scientific
Linux, it should only be used when invoking trusted applications.
Important
X11 forwarding is disabled by default in Scientific Linux 4.x,
which differs from previous Scientific Linux 3.0.x releases such
that attempting to run a malicious X11 application over an ssh
connection cannot compromise the local X11 server. You should only use
X11 forwarding when connecting to trusted servers.
o Scientific Linux 4.1 now includes the diskdump
facility,which can serve as an alternative to (or be used in
conjunction with) the netdump facility.
The diskdump facility for i386 systems currently support the aic7xxx,
aic79xx, mpt fusion, megaraid, ata_piix, and sata_promise devices. On
ia64 systems, the aic7xxx, aic79xx, mpt fusion, and sata_promise
devices are supported. On AMD64 and Intel(R) EM64T systems, the
aic7xxx, aic79xx, mpt fusion, megaraid, sata_promise, and ata_piix
devices are supported. Finally, on PPC64 systems, the ipr and
sym53c8xx_2 devices are supported.
Note
The megaraid and SATA devices are newly supported in
Scientific Linux 4.1.
Usage of the diskdump facility requires a dedicated disk device or
disk partitions that are large enough to contain all physical system
memory. In the event of a system crash, memory will be written to the
configured disk location. Upon subsequent reboot, the data will be
copied from the configured disk location and formatted into a vmcore
file, identical in functionality to that created by the netdump
facility, and stored in the unique subdirectory /var/crash/. The
vmcore file may be analyzed using the crash(8) utility.
Important
The diskdump facility may fail to write a dump file if cluster mode is
enabled on megaraid adapters. You can disable cluster mode on megaraid
adapters using the device's WebBIOS utility. Consult your manufacturer
documentation for more information on using WebBIOS.
The kernel modules required for the diskdump facility are
automatically included in the Scientific Linux 4.x kernel. The
associated user-space diskdump package is named diskdumputils-1.0.1-5,
and like netdump, is installed by default.
The appropriate disk location must first be configured and then
preformatted for use. After formatting, the diskdump facility may be
turned on with chkconfig(8), and then the service must be started.
Detailed documentation concerning configuration and user tasks is
included with the diskdumputils at the following:
/usr/share/doc/diskdumputils-1.0.1-5/README
Further information can be found in the diskdumpfmt(8),
diskdumpctl(8), and savecore(8) man pages.
Kernel Notes
This section contains notes relating to the Scientific Linux 4.1 kernel.
o An issue that causes USB mice to stop responding after a few hours of
use has been discovered on certain systems. A BIOS setting that
enables USB emulation causes 2.6 kernel mouse driving to freeze, which
necessitates either changing to a virtual console using Ctrl-Alt-Fx
then switching back to the graphical desktop or unplugging and
re-plugging the mouse in order to regain functionality.
To prevent the freezing of USB mice, it is recommended to disable USB
Emulation support (also called USB Legacy Support) in the system's
BIOS. Refer to your system manufacturer documentation for more
information about finding and disabling this BIOS setting.
o The Scientific Linux 4.1 kernel automatically disables
NUMA optimizations (numa=off) by default on systems using the AMD64
dual core processor. This ensures stable operation across multiple
systems where each has a different system BIOS implementation for
reporting dual core processors.
Users have the ability to safely override this default for a system
where the manufacturer has stated conformance with the reporting of
dual core processors as expected by Scientific Linux 4.1 kernel.
Users can override the numa=off default by specifying numa=on on the
Linux boot prompt or on the active kernel line in the grub.conf file.
If the system fails to boot after enabling this function, remove the
override and retry it. This limitation is expected to be removed in a
future Scientific Linux 4.x update.
Changes to Drivers and Hardware Support
This update includes bug fixes for a number of drivers. The more
significant driver updates are listed below. In some cases, the original
driver has been preserved under a different name, and is available as a
non-default alternative for organizations that wish to migrate their
driver configuration to the latest versions at a later time.
Note
The migration to the latest drivers should be completed before the next
Scientific Linux update is applied, because in most cases only one
older-revision driver will be preserved for each update.
The following device drivers are updated in Scientific Linux 4.1:
o Emulex LightPulse Fibre Channel HBA (lpfc driver)
o LSI Logic MegaRAID Controller family (megaraid_mbox driver)
o Intel(R) PRO/Wireless 2100/2200 adapters (ieee80211/ipw2100/ipw2200
drivers)
o Broadcom Tigon3 (tg3 driver)
o Intel(R) Pro/100 Adapter family (e100 driver)
o Intel(R) PRO/1000 Adapters (e1000 driver)
o Serial ATA (SATA) devices (sata driver)
o Neterion 10GB Ethernet adapter (s2io driver)
o The kernel shipped with Scientific Linux 4.1 includes
the new megaraid_mbox driver from LSI Logic, which replaces the
megaraid driver. The megaraid_mbox driver has an improved design, is
compatible with the 2.6 kernel, and includes support for the latest
hardware. However, megaraid_mbox does not support some of the older
hardware that was supported by the megaraid driver.
Adapters with the following PCI vendor ID and device ID pairs are not
supported by the megaraid_mbox driver:
vendor, device
0x101E, 0x9010
0x101E, 0x9060
0x8086, 0x1960
The lspci -n command can be used to display the IDs for adapters
installed in a particular machine. Products with these IDs are known
by (but not limited to) the following model names:
o Broadcom 5820
o Dell PERC (dual-channel fast/wide SCSI) RAID controller
o Dell PERC2/SC (single-channel Ultra SCSI) RAID controller
o Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller
o Dell CERC (four-channel ATA/100) RAID controller
o DRAC 1
o MegaRAID 428
o MegaRAID 466
o MegaRAID Express 500
o HP NetRAID 3Si and 1M
Note
Both Dell and LSI Logic have indicated that they no longer support these
models in the 2.6 kernel. As a result, these adapters are no longer
supported in Scientific Linux 4.1.
o Scientific Linux 4.1 provides support for disk devices
that are larger than 2 terabytes (TB). Although there is limited
support for this feature in the Scientific Linux 4.0 release,
4.1 contains many improvements (both in user space programs and
in the kernel). In general, 4.1 is considered a requirement for
support of disk devices larger than 2 TB.
Please note the following guidelines and restrictions related to large
device support:
. Typical disk devices are addressed in units of 512 byte blocks. The
size of the address in the SCSI command determines the maximum device
size. The SCSI command set includes commands that have 16-bit block
addresses (device size is limited to 2 GB), 32-bit block addresses
(limited to addressing 2 TB), and 64-bit block addresses. The SCSI
subsystem in the 2.6 kernel has support for commands with 64-bit block
addresses. To support disks larger then 2 TB, the Host Bus Adapter
(HBA), the HBA driver, and the storage device must also support 64-bit
block address. We have tested the QLogic qla2300 driver and the
Emulex lpfc driver, included in Scientific Linux 4.1,
on an 8 TB logical unit on a Winchester Systems FX400 (rev. 3.42B and
above is required).
. The commonly-used MS-DOS partition table format can not be used on
devices larger than 2 TB. For devices larger than 2 TB, the GPT
partition table format must be used. The parted utility must be used
for the creation and management of GPT partitions. To create a GPT
partition, use the parted command mklabel gpt.
Scientific Linux requires that all block devices be initialized with a valid
partition table, even if there is a single partition encompassing the
entire device. This requirement exists to prevent potential problems
caused by erroneous or unintended partition tables on the device.
. The Anaconda installer currently only supports GPT partition tables
on the Itanium(TM) architecture. As a result, it is not possible to
install or format devices that are larger that 2 TB with Anaconda,
except on Itanium(TM) platforms.
. The / and /boot directories must be located on devices that are 2 TB
in size or less.
. Various issues with LVM2 on large devices are fixed in
Scientific Linux 4.1. Do not use LVM2 on devices larger than 2
TB prior to installing 4.1.
As noted above, Scientific Linux requires that a partition table be written to
the block device, even when it is used as part of an LVM2 Volume
Group. In this case, you may create a single partition that spans the
entire device. Then, be sure to specify the full partition name (for
example, /dev/sda1, not /dev/sda), when you use the pvcreate and
vgcreate commands.
. The maximum size disk that can be a member of an md software RAID
set is 2 TB. The md RAID device itself can be larger than 2 TB.
Devices have been tested up to 8 TB.
. Various issues with e2fsprogs that occur on devices larger than 4 TB
are addressed in Scientific Linux 4.1. Prior to 4.1,
these issues can be worked around by specifying mke2fs -b 4096 when
making an ext2 or ext3 filesystem. The workaround is not necessary in
4.1.
The ext2 and ext3 filesystems have an internal limit of 8 TB. Devices
up to this limit have been tested.
You may want to use the mke2fs -T largefile4 command to speed up the
creation of large filesystems.
. The GFS filesystem is limited to 16 TB on 32-bit systems, and 8
exabytes (EB) with 64-bit systems. GFS filesystem
sizes up to 8 TB have been tested.
. NFS partitions greater than 2 TB have been tested and are supported.
. Scientific Linux 4.1 user space tools are compiled
for large file support. However, it is not possible to test every
program in this mode. Please file a problem report if issues arise
when using the tools for large file support.
. The inn program does not function correctly with devices larger than
2 TB. This will be addressed in a future release of Scientific Linux.
Changes to Packages
This section contains listings of packages that have been updated or added
to Scientific Linux 4.x as part of 4.1.
The following packages have been updated from the original release of
Scientific Linux 4.0:
o ImageMagick
o ImageMagick-c++
o ImageMagick-c++-devel
o ImageMagick-devel
o ImageMagick-perl
o alsa-lib
o alsa-lib-devel
o anaconda
o anaconda-product
o anaconda-runtime
o apr
o apr-devel
o arpwatch
o authconfig
o authconfig-gtk
o autofs
o binutils
o bootparamd
o chkconfig
o comps-4AS
o coreutils
o cpio
o cpp
o crash
o cups
o cups-devel
o cups-libs
o curl
o curl-devel
o dbus
o dbus-devel
o dbus-glib
o dbus-python
o dbus-x11
o device-mapper
o e2fsprogs
o e2fsprogs-devel
o elinks
o emacs
o emacs-common
o emacs-el
o emacs-leim
o emacs-nox
o enscript
o ethereal
o ethereal-gnome
o evolution
o evolution-connector
o evolution-data-server
o evolution-data-server-devel
o evolution-devel
o exim
o exim-doc
o exim-mon
o exim-sa
o firefox
o fonts-xorg-100dpi
o fonts-xorg-75dpi
o fonts-xorg-ISO8859-14-100dpi
o fonts-xorg-ISO8859-14-75dpi
o fonts-xorg-ISO8859-15-100dpi
o fonts-xorg-ISO8859-15-75dpi
o fonts-xorg-ISO8859-2-100dpi
o fonts-xorg-ISO8859-2-75dpi
o fonts-xorg-ISO8859-9-100dpi
o fonts-xorg-ISO8859-9-75dpi
o fonts-xorg-base
o fonts-xorg-cyrillic
o fonts-xorg-syriac
o fonts-xorg-truetype
o gaim
o gcc
o gcc-c++
o gcc-g77
o gcc-java
o gcc-objc
o gdb
o gdk-pixbuf
o gdk-pixbuf-devel
o gdm
o glibc
o glibc-common
o glibc-devel
o glibc-headers
o glibc-profile
o glibc-utils
o gpdf
o gsl
o gsl-devel
o gtk2
o gtk2-devel
o hotplug
o htdig
o htdig-web
o httpd
o httpd-devel
o httpd-manual
o httpd-suexec
o hwbrowser
o hwdata
o iiimf-csconv
o iiimf-docs
o iiimf-emacs
o iiimf-gnome-im-switcher
o iiimf-gtk
o iiimf-le-canna
o iiimf-le-hangul
o iiimf-le-sun-thai
o iiimf-le-unit
o iiimf-libs
o iiimf-libs-devel
o iiimf-server
o iiimf
o initscripts
o ipsec-tools
o java-1.4.2-gcj-compat
o java-1.4.2-gcj-compat-devel
o kdegraphics
o kdegraphics-devel
o kdelibs
o kdelibs-devel
o kernel
o kernel-devel
o kernel-doc
o kernel-utils
o krb5-devel
o krb5-libs
o krb5-server
o krb5-workstation
o kudzu
o kudzu-devel
o libaio
o libaio-devel
o libexif
o libexif-devel
o libf2c
o libgcc
o libgcj
o libgcj-devel
o libobjc
o libpcapk
o libstdc++
o libstdc++-devel
o libtiff
o libtiff-devel
o libtool
o libtool-libs
o lsof
o lvm2
o mailman
o man-pages-ja
o mod_auth_mysql
o mod_python
o mod_ssl
o mozilla
o mozilla-chat
o mozilla-devel
o mozilla-dom-inspector
o mozilla-js-debugger
o mozilla-mail
o mozilla-nspr
o mozilla-nspr-devel
o mozilla-nss
o mozilla-nss-devel
o mysql
o mysql-bench
o mysql-devel
o mysql-server
o net-tools
o netdump
o netdump-server
o nptl-devel
o nscd
o nss_ldap
o ntsysv
o openssh
o openssh-askpass
o openssh-askpass-gnome
o openssh-clients
o openssh-server
o pam
o pam-devel
o pango
o pango-devel
o pciutils
o pciutils-devel
o perl
o perl-DBI
o perl-suidperl
o php
o php-devel
o php-domxml
o php-gd
o php-imap
o php-ldap
o php-mbstring
o php-mysql
o php-ncurses
o php-odbc
o php-pear
o php-pgsql
o php-snmp
o php-xmlrpc
o policycoreutils
o popt
o postfix
o postfix-pflogsumm
o postgresql
o postgresql-contrib
o postgresql-devel
o postgresql-docs
o postgresql-jdbc
o postgresql-libs
o postgresql-odbc
o postgresql-pl
o postgresql-python
o postgresql-server
o postgresql-tcl
o postgresql-test
o procps
o psacct
o python
o python-devel
o python-docs
o python-tools
o redhat-lsb
o redhat-release
o rpm
o rpm-build
o rpm-devel
o rpm-libs
o rpm-python
o rpmdb-redhat
o rsh
o rsh-server
o selinux-policy-targeted
o selinux-policy-targeted-sources
o squid
o squirrelmail
o strace
o system-config-kickstart
o system-config-lvm
o tcpdump
o telnet
o telnet-server
o tetex
o tetex-afm
o tetex-doc
o tetex-dvips
o tetex-fonts
o tetex-latex
o tetex-xdvi
o thunderbird
o tkinter
o ttfonts-ja
o tzdata
o up2date
o up2date-gnome
o vim-X11
o vim-common
o vim-enhanced
o vim-minimal
o xemacs
o xemacs-common
o xemacs-el
o xemacs-info
o xemacs-nox
o xloadimage
o xorg-x11
o xorg-x11-Mesa-libGL
o xorg-x11-Mesa-libGLU
o xorg-x11-Xdmx
o xorg-x11-Xnest
o xorg-x11-Xvfb
o xorg-x11-deprecated-libs
o xorg-x11-deprecated-libs-devel
o xorg-x11-devel
o xorg-x11-font-utils
o xorg-x11-libs
o xorg-x11-tools
o xorg-x11-twm
o xorg-x11-xauth
o xorg-x11-xdm
o xorg-x11-xfs
o xpdf
The following new packages have been added to Scientific Linux 4.1:
o compat-libcom_err-1.0-5
The following packages have been removed from Scientific Linux 4.1:
o No packages have been removed.
( ia64 )
From [log in to unmask] Wed Aug 10 17:23:47 2005
Date: Wed, 10 Aug 2005 17:20:46 -0500
From: root <[log in to unmask]>
To: [log in to unmask]
Scientific Linux 4.0 Release Notes
---------------------------------------------------------------------------
Introduction
The following topics related to Scientific Linux 4.0 are covered in
this document:
o Introduction (this section)
o Overview of this release
o Installation-related notes
o Package-specific notes
o Packages added/removed/deprecated
Overview of This Release
The following list includes brief summaries of some of the more
significant aspects of Scientific Linux 4.0:
o Scientific Linux 4.0 includes an implementation of SELinux.
SELinux represents a major shift in the way users, programs, and
processes interact. By default, SELinux is installed and enabled in
this release.
Note
During the installation you have the option of disabling SELinux,
setting it to log warning messages only, or to use its targeted
policy, which confines the following daemons only:
o dhcpd
o httpd
o mysqld
o named
o nscd
o ntpd
o portmap
o postgres
o snmpd
o squid
o syslogd
The targeted policy is active by default.
Warning
Scientific Linux 4.0 support for SELinux uses Extended
Attributes on ext2/ext3 file systems. This means that, when a file is
written to a default-mounted ext2/ext3 file system, an extended
attribute will also be written.
This will cause problems on systems that dual boot between Scientific
Linux 4.x and much older linux distributions. The older kernels do not
support extended attributes, and can crash when encountering them.
Scientific Linux 3.0.x's kernel does support these extended attributes.
o The mount command has been changed to do the following on NFS mounts:
. TCP is now the default transport on NFS mounts. This means that a
mount command that does not explicitly specify UDP as the desired
protocol (for example, mount foo:/bar /mnt) now uses TCP to
communicate with the server, instead of UDP.
. Using the verbose (-v) option now causes RPC error messages to be
written to standard output.
o Scientific Linux 4.0 supports UTF-8 encoding by default for
Chinese, Japanese, and Korean locales.
o Scientific Linux 4.0 now uses IIIMF for input of Chinese,
Japanese, and Korean by default.
o Scientific Linux 4.0 supports 5 Indian (Indic) languages:
Bengali, Gujarati, Hindi, Punjabi, and Tamil. In addition, the
high-quality Lohit font family for the supported languages has been
included.
o Subversion 1.1 is now included in Scientific Linux; the
Subversion version control system is designed to be a replacement for
CVS and features truly atomic commits, versioning of files,
directories and metadata, along with most current features of CVS.
o Scientific Linux 3.0.x introduced the Native POSIX Thread Library
(NPTL) -- an implementation of POSIX threading support that greatly
improved performance, scalability, semantic correctness, and standards
compliance over the LinuxThreads implementation used previously.
While most threaded applications were not impacted by the introduction
of NPTL, applications that relied on those semantics of LinuxThreads
that were contrary to the POSIX specification would not operate
correctly. As noted at the time of NPTL's introduction, we
recommended that such applications be updated so that they complied
with POSIX (and could therefore use NPTL.)
While support for LinuxThreads still exists for Scientific
Linux 4.x, this statement serves as advance notice that Scientific
Linux 5.x will no longer include support for LinuxThreads.
Therefore, applications that require LinuxThreads support must be
updated before they will be able to work properly on a Scientific
Linux 5.x system.
Note
Several workarounds exist that permit applications requiring the use
of LinuxThreads to continue operation under Scientific Linux 3.0.x
and 4.x. These workarounds include:
o Using the LD_ASSUME_KERNEL environment variable to select
LinuxThreads instead of NPTL at runtime
o Using an explicit rpath to /lib/i686/ or /lib/ to select
LinuxThreads instead of NPTL at runtime
o Statically linking the application to use LinuxThreads instead of
NPTL (strongly discouraged)
In order to determine whether an application is using NPTL or
LinuxThreads, add following two environment variables to the
application's environment:
LD_DEBUG=libs
LD_DEBUG_OUTPUT=<filename>
(Where <filename> is the name to be given to each debug output log
file. More than one file can be generated if the program forks other
processes; all debug output log filenames include the PID of process
generating the file.)
Then start the application and use it as you normally would.
If no debug output log file was produced, the application is
statically linked. The application will not be affected by the missing
LinuxThreads DSO but, as with all statically linked applications, no
guarantees for compatibility are given if the application dynamically
loads any code (directly via dlopen() or indirectly via NSS.)
If one or more debug output log files were produced, review each one
for any references to libpthread -- in particular, a line also
containing the string "calling init". The grep utility can do this
easily:
grep "calling init.*libpthread" <filename>.*
(Where <filename> refers to the name used in the LD_DEBUG_OUTPUT
environment variable.)
If the path preceding libpthread is /lib/tls/, the application is
using NPTL, and no further action needs to be taken. Any other path
means that LinuxThreads is being used, and the application must be
updated and rebuilt to support NPTL.
o Scientific Linux 4.0 now includes support for Advanced
Configuration and Power Interface (ACPI), a power management
specification commonly supported by most newer hardware.
Due to differences in the order in which hardware is probed in system
environments with and without ACPI support, the potential for device
name changes exists. This means, for example, that a network interface
card identified as eth1 under a prior version of Scientific
Linux may now appear as eth0.
Installation-Related Notes
This section outlines those issues that are related to Anaconda (the
Scientific Linux installation program) and installing Scientific
Linux 4.x in general.
o During the Scientific Linux 4.0 installation, it can be
challenging to identify individual storage devices in system
configurations that include multiple storage adapters. This is
particulary true for systems containing Fibre Channel adapters,
because in many instances it is desirable to install Scientific
Linux on local storage.
The Scientific Linux 4.x installation program addresses this
issue by delaying the loading of the following modules until after all
other SCSI devices have been loaded:
o lpfc
o qla2100
o qla2200
o qla2300
o qla2322
o qla6312
o qla6322
This results in any locally-attached SCSI device names starting with
/dev/sda, /dev/sdb, and so on, with the FC-attached storage following.
Package-Specific Notes
The following sections contain information regarding packages that have
undergone significant changes for Scientific Linux 4.0. For easier
access, they are organized using the same groups used in Anaconda.
Base
This section contains information related to basic system components.
openssh
Scientific Linux 4.0 contains OpenSSH 3.9, which includes strict
permission and ownership checks for the ~/.ssh/config file. These checks
mean that ssh will exit if this file does not have appropriate ownership
and permissions.
Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and
that its permissions are set to mode 600.
Core
This section contains the most elemental components of Scientific
Linux, including the kernel.
e2fsprogs
The ext2online utility has been added for online growing of existing ext3
file systems.
Note
It is important to keep in mind that ext2online does not grow the
underlying block device itself -- there must be sufficient unused space
already present on the device. The easiest way to ensure this is to use
LVM volumes and to run lvresize or lvextend to extend the device.
In addition, file systems must be specially prepared in order to be
resized past a certain point. The preparation involves reserving a small
amount of space into which on-disk tables can grow. For newly-created file
systems, mke2fs reserves such space automatically; the space reserved is
sufficient to grow the file system by a factor of 1000. The creation of
this reserved space can be disabled by the following command:
mke2fs -O ^resize_inode
Future releases of Scientific Linux will allow the creation of
this reserved space on existing file systems.
glibc
o The version of glibc provided with Scientific Linux 4.0 performs
additional internal sanity checks to prevent and detect data
corruption as early as possible. By default, should corruption be
detected, a message similar to the following will be displayed on
standard error (or logged via syslog if stderr is not open):
*** glibc detected *** double free or corruption: 0x0937d008 ***
By default, the program that generated this error will also be killed;
however, this (and whether or not an error message is generated) can
be controlled via the MALLOC_CHECK_ environment variable. The
following settings are supported:
o 0 -- Do not generate an error message, and do not kill the
program
o 1 -- Generate an error message, but do not kill the program
o 2 -- Do not generate an error message, but kill the program
o 3 -- Generate an error message and kill the program
Note
If MALLOC_CHECK_ is explicitly set a value other than 0, this causes
glibc to perform more tests that are more extensive than the default,
and may impact performance.
Should you have a program from a third party ISV that triggers these
corruption checks and displays a message, you should file a defect
report with the application's vendor, since this indicates a serious
bug.
kernel
This section contains notes relating to the Scientific Linux 4.0
kernel.
o Although Scientific Linux 4.0 includes support for rawio, it is
now a deprecated interface. If your application performs device access
using this interface, we encourages you to modify your
application to open the block device with the O_DIRECT flag. The rawio
interface will exist for the life of Scientific Linux 4.x, but
is a candidate for removal from future releases.
Asynchronous I/O (AIO) on file systems is currently only supported in
O_DIRECT, or non-buffered mode. Also note that the asynchronous poll
interface is no longer present, and that AIO on pipes is no longer
supported.
o The sound subsystem is now based on ALSA; the OSS modules are no
longer available.
o System environments using the kernel's "hugepage" functionality should
be aware that the name of the /proc/ entry controlling this feature
changed between Scientific Linux 3.0.x and Scientific Linux 4.x:
o Scientific Linux 3.0.x used /proc/sys/vm/hugetlb_pool and
specified the desired size in megabytes
o Scientific Linux 4.x uses /proc/sys/vm/nr_hugepages and
specifies the size by the desired number of pages (refer to
/proc/meminfo for the size of hugepages on your system)
o The initial release of Scientific Linux 4.0 does not support USB
hard disk drives. However, other USB storage devices, such as flash
media, CD-ROM and DVD-ROM devices are currently supported.
o The kernel shipped with Scientific Linux 4.0 includes the new
megaraid_mbox driver from LSI Logic, which replaces the megaraid
driver. The megaraid_mbox driver has an improved design, is compatible
with the 2.6 kernel, and includes support for the latest hardware.
However, megaraid_mbox does not support some of the older hardware
that was supported by the megaraid driver.
Adapters with the following PCI vendor ID and device ID pairs are not
supported by the megaraid_mbox driver:
vendor, device
0x101E, 0x9010
0x101E, 0x9060
0x8086, 0x1960
The lspci -n command can be used to display the IDs for adapters
installed in a particular machine. Products with these IDs are known
by (but not limited to) the following model names:
o Dell PERC (dual-channel fast/wide SCSI) RAID controller
o Dell PERC2/SC (single-channel Ultra SCSI) RAID controller
o Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller
o Dell CERC (four-channel ATA/100) RAID controller
o MegaRAID 428
o MegaRAID 466
o MegaRAID Express 500
o HP NetRAID 3Si and 1M
Both Dell and LSI Logic have indicated that they no longer support
these models in the 2.6 kernel. As a result, these adapters are not
supported in Scientific Linux 4.0.
o The initial release of Scientific Linux 4.0 does not include
iSCSI software initiator or target support. Support for iSCSI is being
evaluated for addition in a future update to Scientific Linux 4.x.
o The Emulex LightPulse Fibre Channel driver (lpfc) is currently
undergoing public review for possible inclusion in the Linux 2.6
kernel. It is included in Scientific Linux 4.0 for testing
purposes. Changes to the driver are expected. If there are problems
with the driver or, if for some reason it is no longer on-track for
inclusion in the Linux 2.6 kernel, the driver may be removed from the
final Scientific Linux release.
The lpfc driver currently has the following known issues:
o The driver does not insulate the system from short-duration cable
pulls, switch reboots, or device disappearances. Therefore, the
system may prematurely determine that a device is non-existent
and take it offline. In such cases, manual intervention will be
required to reinstate the device with the system.
o There is a known panic if Ctrl-C is pressed while the driver is
being inserted with insmod.
o There is a known panic if rmmod is executed while insmod is still
executing.
o New device insertion requires manual scanning in order for the
SCSI subsystem to detect the new device.
o In the past, the process of updating the kernel did not change the
default kernel in the system's boot loader configuration.
Scientific Linux 4.0 changes this behavior to set
newly-installed kernels as the default. This behavior applies to all
installation methods (including rpm -i).
This behavior is controlled by two lines in the /etc/sysconfig/kernel
file:
o UPGRADEDEFAULT -- Controls whether new kernels will be booted by
default (default value: yes)
o DEFAULTKERNEL -- kernel RPMs whose names match this value will be
booted by default (default value: depends on hardware
configuration)
o In order to eliminate the redundancy inherent in providing a separate
package for the kernel source code when that source code already
exists in the kernel's .src.rpm file, Scientific Linux 4.x no
longer includes the kernel-source package. Users that require access
to the kernel sources can find them in the kernel .src.rpm file. To
create an exploded source tree from this file, perform the following
steps (note that <version> refers to the version specification for
your currently-running kernel):
1. Obtain the kernel-<version>.src.rpm file from one of the
following sources:
o The SRPMS directory on the appropriate "SRPMS" CD iso image
o The FTP site where you got the kernel package
2. Install kernel-<version>.src.rpm (given the default RPM
configuration, the files this package contains will be written to
/usr/src/redhat/)
3. Change directory to /usr/src/redhat/SPECS/, and issue the
following command:
rpmbuild -bp --target=<arch> kernel.spec
(Where <arch> is the desired target architecture.)
On a default RPM configuration, the kernel tree will be located
in /usr/src/redhat/BUILD/.
4. In resulting tree, the configurations for the specific kernels
shipped in Scientific Linux 4.x are in the /configs/
directory. For example, the i686 SMP configuration file is named
/configs/kernel-<version>-i686-smp.config. Issue the following
command to place the desired configuration file in the proper
place for building:
cp <desired-file> ./.config
5. Issue the following command:
make oldconfig
You can then proceed as usual.
Note
An exploded source tree is not required to build kernel modules
against the currently in-use kernel.
For example, to build the foo.ko module, create the following file
(named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
Issue the make command to build the foo.ko module.
sysklogd
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
DNS Name Server
This section contains information related to the DNS name server.
bind
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
Graphical Internet
This section includes packages that help you access the Internet,
including graphical email, Web browser, and chat clients.
evolution
o Scientific Linux 4.0 includes an updated version of the
Evolution graphical email client. This version adds a number of new
features, including:
o Evolution now includes spam filters that can be trained to more
accurately distinguish between spam and non-spam email. When you
get spam, click on the Junk button. Check your Junk Mail folder
periodically to see if anything is being filtered improperly. If
you find an improperly-filtered email, mark it as Not Junk; in
this way, the filter becomes more effective over time.
o The Evolution Connector makes it possible to connect to Microsoft
Exchange 2000 and 2003 servers.
o The user interface has been modified so that each operation
(email, calendaring, tasks, and contacts) is treated separately,
replacing the previous server-centric model.
o Evolution now includes enhanced support for encryption and
cryptographic signatures, including the use of S/MIME.
o The directory used by Evolution to store its settings has been
hidden from end-users by renaming it from ~/evolution/ to
~/.evolution/.
Graphics
This section includes packages that help you manipulate and scan images.
gimp
o The gimp-perl package has been removed from Scientific Linux 4.0
because GIMP was updated to 2.0 and the Perl bindings were neither
ready nor part of the main package anymore.
Users of Perl scripts in GIMP should install the Gimp Perl module from
[4]http://www.gimp.org/downloads/.
Language Support
This section includes information related to the support of various
languages under Scientific Linux.
UTF-8 Support for Chinese, Japanese, and Korean
When upgrading a system from Scientific Linux 3.0.x to
Scientific Linux 4.0, system locale settings are preserved. Because
Scientific Linux 4.0 supports Chinese, Japanese, and Korean in UTF-8
encoding by default, we recommends that you change to UTF-8 locale by
editing the following file:
/etc/sysconfig/i18n
Modify the locale settings by making the following changes:
o ja_JP.eucJP becomes ja_JP.UTF-8
o ko_KR.eucKR becomes ko_KR.UTF-8
o zh_CN.GB18030 becomes zh_CN.UTF-8
o zh_TW.Big5 becomes zh_TW.UTF-8
Users with locale settings in ~/.i18n should also update to use UTF-8
encoding by default.
To convert a text file in native encoding (for example eucJP, eucKR, Big5,
or GB18030) to UTF-8, you can use the iconv utility:
iconv -f <native encoding> -t UTF-8 <filename> -o <newfilename>
Refer to the iconv man page for more information.
IIIMF
The default Input Method (IM) for Chinese (Simplified and Traditional),
Japanese, and Korean has been changed to IIIMF -- the Internet/Intranet
Input Method Framework. IIIMF is used by default for input of Indian
languages also. IIIMF is supported natively through a GTK2 IM module, and
also through XIM using the httx client. IIIMF supports the use of multiple
Language Engines (LEs) at the same time; using the GNOME Input Method
Language Engine Tool (GIMLET -- an applet) it is possible to switch
between LEs of different languages inside GTK2 applications.
IIIMF currently defaults to using Ctrl-Space or Shift-Space for toggling
the input method on and off (Emacs users can use Ctrl-@ instead of
Ctrl-Space to set the mark).
Depending on your choice of language support during installation, one or
more IIIMF Language Engines may have been installed:
o Indian languages -- iiimf-le-unit
o Japanese -- iiimf-le-canna
o Korean -- iiimf-le-hangul
o Simplified Chinese -- iiimf-le-chinput
o Traditional Chinese -- iiimf-le-xcin
For these languages IIIMF is installed and enabled by default.
New users get the GIMLET applet (part of the iiimf-gnome-im-switcher
package) automatically added to their GNOME panel, if the GNOME Desktop is
installed and the default system language is one of the above.
GIMLET is an applet for switching between the different LEs that are
installed on your system. Using different Language Engines allows you to
enter text in different languages. You can add GIMLET manually to your
GNOME panel by right-clicking on the panel, selecting Add to panel... and
choosing the InputMethod Switcher applet.
If you are upgrading and have any legacy XIM input methods installed,
Anaconda will automatically install appropriate Language Engines onto your
system:
o ami causes iiimf-le-hangul to be installed
o kinput2 causes iiimf-le-canna to be installed
o miniChinput causes iiimf-le-chinput to be installed
o xcin causes iiimf-le-xcin to be installed
For users that do not need IIIMF input all the time there is a LE called
"Latin default" which does nothing for normal input. This can be used to
temporarily disable another LE.
The following are some keybindings particular to each of the Language
Engines:
iiimf-le-canna -- Home (show the menu, including the utilities for Canna)
iiimf-le-unit -- F5 (switch between languages), F6 (switch to different
input styles, if available)
iiimf-le-xcin -- Ctrl-Shift (switch to different input styles),
Shift-punctuation (input wide punctuation marks), Cursor keys (change
pages in candidate window)
iiimf-le-chinput -- Ctrl-Shift (switch to different input styles), < or >
(change pages in candidate window)
iiimf-le-hangul -- F9 (convert Hangul to Chinese characters)
Input Method Configuration
Should you wish to switch between IIIMF and the legacy input method
framework XIM, you can use the system-switch-im application. There is also
the command-line tool im-switch for changing the user and system
configuration.
Scientific Linux 4.0 uses an alternatives-based system of files in
/etc/X11/xinit/xinput.d/ and ~/.xinput.d/ to configure the input methods
used for different locales. Users of locales for which input methods are
not used by default (for example, en_US.UTF-8) that wish to input Asian
text must execute the following commands from a shell prompt:
mkdir -p ~/.xinput.d/
ln -s /etc/X11/xinit/xinput.d/iiimf ~/.xinput.d/en_US
This overrides the system default and enables the use of IIIMF for
American English. To configure the input method for an different locale,
replace en_US with your locale name (without the charset suffix). To set
the input method to be used for all locale use the word default instead of
en_US.
Users upgrading from Scientific Linux 3.0.x should note that
/etc/sysconfig/i18n and ~/.i18n can no longer be used for input method
configuration; any custom configuration still needed should be moved as
appropriate to /etc/X11/xinit/xinput.d/ or ~/.xinput.d/.
After changing the input method configuration your changes will be
reflected next time you start a X Window System session.
Mail Server
This section contains information related to the mail transport agents
included with Scientific Linux 4.0.
mailman
Earlier mailman RPMs installed all files under the /var/mailman/
directory. Unfortunately, this did not conform to the Filesystem Hierarchy
Standard (FHS) and also created security violations when SELinux was
enabled.
If you previously had mailman installed and had edited files in
/var/mailman/ (such as mm_cfg.py) you must move those changes to their new
location, as documented in the following file:
/usr/share/doc/mailman-*/INSTALL.REDHAT
sendmail
o By default, the Sendmail mail transport agent (MTA) does not accept
network connections from any host other than the local computer. If
you want to configure Sendmail as a server for other clients, you must
edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also
listen on network devices (or comment out this option entirely using
the dnl comment delimiter). You must then regenerate
/etc/mail/sendmail.cf by running the following command (as root):
make -C /etc/mail
Note that you must have the sendmail-cf package installed for this to
work.
Note
Be aware that it is possible to inadvertently configure Sendmail to
act as an open-relay SMTP server.
MySQL Database
MySQL, the multi-user and multi-threaded client/server database, has been
updated from version 3.23.x (which shipped with Scientific Linux 3.0.x)
to version 4.1.x. This new version of MySQL features improvements in
speed, functionality, and usability, including:
o subquery support
o BTREE indexing for non-structured queries
o Secure database replication over SSL connections
o Unicode support via utf-8 and ucs-2 character sets
Users should note that there may be compatibility issues when migrating
applications or databases from version 3.23.x to 4.1.x of MySQL. A known
issue is that the default timestamp format has changed. To address these
various issues, the mysqlclient10 package is included to provide the
3.23.x client library (libmysqlclient.so.10) for binary compatibility with
applications linked against this legacy library.
Note
While the mysqlclient10 package provides compatibility support with the
MySQL 4.1.x server, it does not support the new password encryption method
introduced in version 4.1. To enable compatibility with legacy MySQL
3.x-based clients, the old_passwords parameter is enabled by default in
the /etc/my.cnf configuration file. If compatibility with old clients is
not required, this parameter can be disabled to allow use of the improved
password encryption method.
mysql-server
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
Network Servers
This section contains information related to various network-based
servers.
dhcp
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
Server Configuration Tools
This section contains information related to various server configuration
tools.
system-config-lvm
Scientific Linux 4.0 includes system-config-lvm, a graphical tool
for configuring Logical Volume Manager (LVM). system-config-lvm allows
users to create volume groups from physical disk drives and disk
partitions on a local machine, creating flexible and extensible logical
volumes that are treated as normal physical disk space by the system.
system-config-lvm uses graphical representations of system disks and
volumes, which assists users in visualizing storage use and providing an
interface for addressing volume management tasks.
system-config-securitylevel
The firewall constructed by the system-config-securitylevel configuration
tool now allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the
present time, these services cannot be disabled by
system-config-securitylevel.
Web Server
This section contains information related to software used as part of a
Web server environment.
httpd
o Under the default SELinux security configuration, httpd is covered by
the targeted policy. This increases security and Web server stability
by specifically granting or denying httpd access to system objects.
However, because this has the potential to cause previously-working
configurations (such as those that use PHP) to no longer function, you
must understand how SELinux works in order to ensure that your
configuration is both secure and functional.
For example, a Boolean can be set to give specific permission to httpd
to read objects in ~/public_html/ as long as they are labeled with the
security context httpd_sys_content_t. The Apache daemon cannot access
objects (files, applications, devices, and other processes) that have
a security context not specifically granted access by SELinux to
httpd.
By allowing Apache access to only what it needs to do its function,
the system is protected from compromised or misconfigured httpd
daemons.
Because of the need for both standard Linux directory and file
permissions as well as SELinux file context labels, adminstrators and
users will need to know about relabeling files. Examples of relabeling
include the following commands (one for recursively relabeling the
contents of a directory, and one for relabeling a single file):
chcon -R -h -t httpd_sys_content_t public_html
chcon -t httpd_sys_content_t public_html/index.html
A file or directory which is not labeled with a context on the list of
Apache's allowable types will generate a 403 Forbidden error.
You can configure Boolean values or selectively disable targeted
policy coverage for just Apache (or any of the covered daemons) using
system-config-securitylevel. Under the SELinux tab, within the Modify
SELinux Policy area, you can modify the Boolean values for Apache. If
you wish, you can select to Disable SELinux protection for httpd
daemon, which disables the transition from unconfined_t (the default
type that acts transparently like standard Linux security without
SELinux) to the specific daemon type, i.e., httpd_t. Disabling this
transition effectively turns off SELinux coverage for that daemon,
returning it to standard Linux security only.
o By default, the httpd daemon is now started using the C locale, rather
than using the configured system locale setting. This behavior can be
changed by setting the HTTPD_LANG variable in the /etc/sysconfig/httpd
file.
php
o The default /etc/php.ini configuration file has been changed to use
the "production" defaults rather than "development" defaults; notable
differences are:
o display_errors is now Off
o log_errors is now On
o magic_quotes_gpc is now Off
The package now uses the "apache2handler" SAPI for integration with
Apache httpd 2.0 rather than the "apache2filter" SAPI. If upgrading
from previous releases, the SetOutputFilter directives should be
removed from the /etc/httpd/conf.d/php.conf file.
o The following changes have been made to the packaging of PHP extension
modules:
o The gd, mbstring, and ncurses extensions have been moved to the
php-gd, php-mbstring, and php-ncurses packages, respectively.
Note that you will need to install these packages manually (if
required) when upgrading from an earlier release.
o The domxml, snmp, and xmlrpc extensions are now available in
php-domxml, php-snmp, and php-xmlrpc packages, respectively.
squid
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
X Window System
This section contains information related to the X Window System
implementation provided with Scientific Linux 4.0.
xorg-x11
o Scientific Linux 4.0 includes the new xorg-x11-deprecated-libs
package. This package contains X11-related libraries that are
deprecated, and may be removed from future versions of Scientific
Linux. By packaging deprecated libraries in this manner,
binary compatibility with existing applications is maintained while
allowing 3rd-party software providers time to transition their
applications away from these libraries.
Currently, this package contains the Xprint library (libXp). This
library should not be used in new application development.
Applications that currently use this library should begin migrating to
the supported libgnomeprint/libgnomeprintui printing APIs.
o There has been some confusion regarding font-related issues under the
X Window System. At the present time, there are
two font subsystems, each with different characteristics:
- The original (15+ year old) subsystem is referred to as the "core X
font subsystem". Fonts rendered by this subsystem are not
anti-aliased, are handled by the X server, and have names like:
-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
The newer font subsystem is known as "fontconfig", and allows
applications direct access to the font files. Fontconfig is often used
along with the "Xft" library, which allows applications to render
fontconfig fonts to the screen with antialiasing. Fontconfig uses more
human-friendly names like:
Luxi Sans-10
Over time, fontconfig/Xft will replace the core X font subsystem. At
the present time, applications using the Qt 3 or GTK 2 toolkits (which
would include KDE and GNOME applications) use the fontconfig and Xft
font subsystem; most everything else uses the core X fonts.
In the future, Scientific Linux may support only
fontconfig/Xft in place of the XFS font server as the default local
font access method.
NOTE: An exception to the font subsystem usage outlined above is
OpenOffice.org (which uses its own font rendering technology).
If you wish to add new fonts to your Scientific Linux 4.x
system, you must be aware that the steps necessary depend on which
font subsystem is to use the new fonts. For the core X font subsystem,
you must:
1. Create the /usr/share/fonts/local/ directory (if it doesn't already
exist):
mkdir /usr/share/fonts/local/
2. Copy the new font file into /usr/share/fonts/local/
3. Update the font information by issuing the following commands (note
that, due to formatting restrictions, the following commands may
appear on more than one line; in use, each command should be entered
on a single line):
ttmkfdir -d /usr/share/fonts/local/ -o
/usr/share/fonts/local/fonts.scale
mkfontdir /usr/share/fonts/local/
4. If you had to create /usr/share/fonts/local/, you must then add it
to the X font server (xfs) path:
chkfontpath --add /usr/share/fonts/local/
Adding new fonts to the fontconfig font subsystem is more
straightforward; the new font file only needs to be copied into the
/usr/share/fonts/ directory (individual users can modify their
personal font configuration by copying the font file into the
~/.fonts/ directory).
After the new font has been copied, use fc-cache to update the font
information cache:
fc-cache <directory>
(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
directories.)
Individual users may also install fonts graphically, by browsing
fonts:/// in Nautilus, and dragging the new font files there.
NOTE: If the font filename ends with ".gz", it has been compressed
with gzip, and must be decompressed (with the gunzip command) before
the fontconfig font subsystem can use the font.
o Due to the transition to the new font system based on fontconfig/Xft,
GTK+ 1.2 applications are not affected by any changes made via the
Font Preferences dialog. For these applications, a font can be
configured by adding the following lines to the file ~/.gtkrc.mine:
style "user-font" {
fontset = "<font-specification>"
}
widget_class "*" style "user-font"
(Where <font-specification> represents a font specification in the
style used by traditional X applications, such as
"-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
Miscellaneous Notes
This section contains information related to packages that do not fit in
any of the proceeding categories.
compat-db
C++ and TCL bindings are no longer contained in the compat-db package.
Applications requiring these bindings must be ported to the
currently-shipping DB library.
lvm2
This section contains information related to the lvm2 package.
o The full set of LVM2 commands is now installed in /usr/sbin/. In boot
environments where /usr/ is not available, it is necessary to prefix
each command with /sbin/lvm.static (/sbin/lvm.static vgchange -ay, for
example).
In environments where /usr/ is available, it is no longer necessary to
prefix each command with lvm (/usr/sbin/lvm vgchange -ay becomes
/usr/sbin/vgchange -ay, for example).
o The new LVM2 commands (such as /usr/sbin/vgchange -ay and
/sbin/lvm.static vgchange -ay) detect if you are running a 2.4 kernel,
and transparently invoke the old LVM1 commands if appropriate. The
LVM1 commands have been renamed to end with ".lvm1" (for example,
/sbin/vgchange.lvm1 -ay).
Note
LVM1 commands work only with 2.4 kernels. It is not possible to use
LVM1 commands while running a 2.6 kernel.
Refer to /usr/share/doc/lvm2*/WHATS_NEW for more information on LVM2.
net-snmp
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
nscd
o The nscd name service cache daemon may now maintain a persistent cache
across restarts or system reboots. Each database (user, group, and
host, respectively) can be made selected to be persistent by setting
the appropriate line in /etc/nscd.conf to "yes". Entries are not
removed from the cache until they are proven to be no longer of
interest. All entries whose time-to-live expires but are otherwise
interesting are automatically reloaded, which helps in situations
where the directory and name services become temporarily unavailable.
o Under the default SELinux security configuration, this daemon is
covered by the targeted policy. This increases security by
specifically granting or denying access to system objects that that
the daemon normally uses. However, because this has the potential to
cause previously-working configurations to no longer function, you
must understand how SELinux works in order to ensure that your
configuration is both secure and functional.
ntp
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
portmap
Under the default SELinux security configuration, this daemon is covered
by the targeted policy. This increases security by specifically granting
or denying access to system objects that that the daemon normally uses.
However, because this has the potential to cause previously-working
configurations to no longer function, you must understand how SELinux
works in order to ensure that your configuration is both secure and
functional.
udev
Scientific Linux 4.0 has switched from a static /dev/ directory to
one that is dynamically managed via udev. This allows device nodes to be
created on demand as drivers are loaded.
For more information on udev, refer to the udev(8) man page.
Additional rules for udev should be placed in a separate file in the
/etc/udev/rules.d/ directory.
Additional permission rules for udev should be placed in a separate file
in the /etc/udev/permissions.d/ directory.
Systems upgraded to Scientific Linux 4.0 using Anaconda will
automatically be reconfigured to use udev. However (although NOT
recommended) it is possible to perform a "live" upgrade to udev using the
following steps:
1. Ensure that you are running a 2.6 kernel
2. Ensure that /sys/ is mounted
3. Install the initscripts RPM supplied with Scientific Linux 4.0
4. Install the new udev RPM supplied with Scientific Linux 4.0
5. Execute /sbin/start_udev
6. Install the new mkinitrd RPM supplied with Scientific Linux 4.0
7. Perform one of the following steps:
. Install the new kernel RPM supplied with Scientific Linux 4.0
OR:
. Re-run mkinitrd for your existing kernel(s)
Warning
Improperly performing these steps can result in a system configuration
that will not boot properly.
Packages Added/Removed/Deprecated
This section contains lists of packages that fit into the following
categories:
o Packages that have been added to Scientific Linux 4.0
o Packages that have been removed from Scientific Linux 4.0
o Packages that have been deprecated, and may be removed from a future
release of Scientific Linux
Packages Added
The following packages have been added to Scientific Linux 4.0:
o Canna-devel
o FreeWnn-devel
o ImageMagick-c++
o ImageMagick-c++-devel
o ImageMagick-devel
o ImageMagick-perl
o NetworkManager
o NetworkManager-gnome
o PyQt
o PyQt-devel
o PyQt-examples
o Pyrex
o VFlib2-VFjfm
o VFlib2-conf-ja
o VFlib2-devel
o Xaw3d-devel
o alchemist-devel
o alsa-lib
o alsa-lib-devel
o alsa-utils
o amanda-devel
o anaconda-product (noarch)
o anacron
o apel
o apr
o apr-devel
o apr-util
o apr-util-devel
o arpwatch
o aspell-ca
o aspell-cs
o aspell-cy
o aspell-el
o aspell-en
o aspell-pl
o audit
o authd
o automake16
o automake17
o beecrypt-devel
o beecrypt-python
o bind-chroot
o bind-devel
o bind-libs
o bitstream-vera-fonts
o bluez-bluefw
o bluez-hcidump
o bluez-libs
o bluez-libs-devel
o bluez-pin
o bluez-utils
o bluez-utils-cups
o bogl-devel
o boost
o boost-devel
o bootparamd
o bridge-utils-devel
o busybox
o cadaver
o cdda2wav
o cdparanoia-devel
o cdrecord-devel
o checkpolicy
o compat-gcc-32
o compat-gcc-32-c++
o compat-libgcc-296
o compat-libstdc++-296
o compat-libstdc++-33
o compat-openldap
o comps (ia64)
o cryptsetup
o cscope
o cyrus-imapd
o cyrus-imapd-devel
o cyrus-imapd-murder
o cyrus-imapd-nntp
o cyrus-imapd-utils
o cyrus-sasl-ntlm
o cyrus-sasl-sql
o dasher
o db4-java
o db4-tcl
o dbus
o dbus-devel
o dbus-glib
o dbus-python
o dbus-x11
o device-mapper
o dhcp-devel
o dhcpv6
o dhcpv6_client
o dia
o dmalloc
o docbook-simple
o docbook-slides
o dovecot
o doxygen-doxywizard
o elfutils-libelf-devel
o emacs-common
o emacs-nox
o evolution-connector
o evolution-data-server
o evolution-data-server-devel
o evolution-devel
o evolution-webcal
o exim
o exim-doc
o exim-mon
o exim-sa
o expect-devel
o expectk
o finger-server
o firefox
o flac
o flac-devel
o fonts-arabic
o fonts-bengali
o fonts-xorg-100dpi
o fonts-xorg-75dpi
o fonts-xorg-ISO8859-14-100dpi
o fonts-xorg-ISO8859-14-75dpi
o fonts-xorg-ISO8859-15-100dpi
o fonts-xorg-ISO8859-15-75dpi
o fonts-xorg-ISO8859-2-100dpi
o fonts-xorg-ISO8859-2-75dpi
o fonts-xorg-ISO8859-9-100dpi
o fonts-xorg-ISO8859-9-75dpi
o fonts-xorg-base
o fonts-xorg-cyrillic
o fonts-xorg-syriac
o fonts-xorg-truetype
o freeglut
o freeglut-devel
o freeradius-mysql
o freeradius-postgresql
o freeradius-unixODBC
o freetype-demos
o freetype-utils
o fribidi
o fribidi-devel
o fsh
o gamin
o gamin-devel
o gd-progs
o gedit-devel
o gettext-devel
o ghostscript-devel
o ghostscript-gtk
o gimp-devel
o gimp-gap
o gimp-help
o gimp-print-devel
o gnome-audio-extra
o gnome-kerberos
o gnome-keyring
o gnome-keyring-devel
o gnome-keyring-manager
o gnome-mag
o gnome-mag-devel
o gnome-netstatus
o gnome-nettool
o gnome-panel-devel
o gnome-pilot-conduits
o gnome-pilot-devel
o gnome-python2-applet
o gnome-python2-gconf
o gnome-python2-gnomeprint
o gnome-python2-gnomevfs
o gnome-python2-nautilus
o gnome-speech
o gnome-speech-devel
o gnome-vfs2-smb
o gnome-volume-manager
o gnopernicus
o gnu-efi
o gnumeric
o gnumeric-devel
o gnuplot-emacs
o gnutls
o gnutls-devel
o gok
o gok-devel
o gpdf
o gphoto2-devel
o groff-gxditview
o groff-perl
o gsl
o gsl-devel
o gstreamer-devel
o gstreamer-plugins-devel
o gthumb
o gtkhtml3-devel
o gtksourceview
o gtksourceview-devel
o gtkspell
o gtkspell-devel
o guile-devel
o hal
o hal-cups-utils
o hal-devel
o hal-gnome
o hicolor-icon-theme
o howl
o howl-devel
o howl-libs
o hpoj-devel
o htdig-web
o httpd-manual
o httpd-suexec
o icon-slicer
o iiimf-csconv
o iiimf-docs
o iiimf-emacs
o iiimf-gnome-im-switcher
o iiimf-gtk
o iiimf-le-canna
o iiimf-le-chinput
o iiimf-le-hangul
o iiimf-le-sun-thai
o iiimf-le-unit
o iiimf-le-xcin
o iiimf-libs
o iiimf-libs-devel
o iiimf-server
o iiimf-x
o inn-devel
o iptables-devel
o iptraf
o iptstate
o irb
o isdn4k-utils-devel
o isdn4k-utils-vboxgetty
o joe
o jpackage-utils
o k3b
o kdbg
o kde-i18n-Bengali
o kde-i18n-Bulgarian
o kde-i18n-Hindi
o kde-i18n-Punjabi
o kde-i18n-Tamil
o kdeaddons-atlantikdesigner
o kdeaddons-xmms
o kdeadmin
o kdeartwork-icons
o kdegames-devel
o kdemultimedia-devel
o kdenetwork-nowlistening
o kernel-devel
o kernel-doc
o kinput2
o krb5-auth-dialog
o libavc1394
o libavc1394-devel
o libc-client
o libc-client-devel
o libcroco
o libcroco-devel
o libdbi-dbd-pgsql
o libdbi-devel
o libdv
o libdv-devel
o libdv-tools
o libexif
o libexif-devel
o libgal2-devel
o libgcrypt
o libgcrypt-devel
o libghttp-devel
o libgnomecups
o libgnomecups-devel
o libgpg-error
o libgpg-error-devel
o libgsf-devel
o libgtop2-devel
o libidn
o libidn-devel
o libieee1284
o libieee1284-devel
o libmng-static
o libmusicbrainz
o libmusicbrainz-devel
o libpfm
o libpfm-devel
o libpng10-devel
o libraw1394-devel
o libsane-hpoj
o libselinux
o libselinux-devel
o libsepol
o libsepol-devel
o libsilc
o libsilc-devel
o libsilc-doc
o libsoup-devel
o libtabe-devel
o libtheora
o libtheora-devel
o libungif-progs
o libunwind
o libwmf
o libwmf-devel
o libwnck-devel
o libwvstreams-devel
o libxklavier
o libxklavier-devel
o libxml-devel
o libxslt-python
o linuxwacom
o linuxwacom-devel
o lrzsz
o lvm2
o lynx
o mailman
o mc
o mgetty-sendfax
o mgetty-viewfax
o mgetty-voice
o mikmod-devel
o mod_auth_kerb
o mod_dav_svn
o mod_perl-devel
o module-init-tools
o mozilla-devel
o mozilla-nspr-devel
o mozilla-nss-devel
o mtr-gtk
o mtx
o mysql-server
o nabi
o nasm
o nasm-doc
o nasm-rdoff
o nautilus-cd-burner-devel
o neon
o neon-devel
o net-snmp-libs
o net-snmp-perl
o nmap-frontend
o nss_db
o numactl
o octave-devel
o openh323-devel
o openjade-devel
o openldap-servers-sql
o openssl-perl
o pam_ccreds
o pam_passwdqc
o parted-devel
o pcmcia-cs
o perl-Bit-Vector
o perl-Convert-ASN1
o perl-Crypt-SSLeay
o perl-Cyrus
o perl-Date-Calc
o perl-LDAP
o perl-Net-DNS
o perl-XML-LibXML
o perl-XML-LibXML-Common
o perl-XML-NamespaceSupport
o perl-XML-SAX
o perl-suidperl
o pfmon
o php-devel
o php-domxml
o php-gd
o php-mbstring
o php-ncurses
o php-pear
o php-snmp
o php-xmlrpc
o planner
o pmake
o policycoreutils
o postfix-pflogsumm
o postgresql
o postgresql-contrib
o postgresql-devel
o postgresql-docs
o postgresql-jdbc
o postgresql-libs
o postgresql-pl
o postgresql-python
o postgresql-server
o postgresql-tcl
o postgresql-test
o pump-devel
o pvm-gui
o pwlib-devel
o pyorbit-devel
o pyparted
o python-docs
o python-ldap
o python-tools
o qt-ODBC
o qt-PostgreSQL
o qt-config
o quagga-contrib
o quagga-devel
o redhat-release (ia64)
o rhgb
o rhythmbox
o rpm-libs
o ruby-docs
o ruby-tcltk
o samba-swat
o selinux-doc
o selinux-policy-targeted
o selinux-policy-targeted-sources
o sendmail-devel
o sendmail-doc
o setools
o setools-gui
o sg3_utils
o shared-mime-info
o skkdic
o sound-juicer
o sox-devel
o speex
o speex-devel
o statserial
o subversion
o subversion-devel
o subversion-perl
o switchdesk
o switchdesk-gui
o sysfsutils
o sysfsutils-devel
o system-config-date
o system-config-display
o system-config-httpd
o system-config-keyboard
o system-config-kickstart
o system-config-language
o system-config-lvm
o system-config-mouse
o system-config-network
o system-config-network-tui
o system-config-nfs
o system-config-packages
o system-config-printer
o system-config-printer-gui
o system-config-rootpassword
o system-config-samba
o system-config-securitylevel
o system-config-securitylevel-tui
o system-config-services
o system-config-soundcard
o system-config-users
o system-logviewer
o system-switch-im
o system-switch-mail
o system-switch-mail-gnome
o talk-server
o tcl-devel
o tcl-html
o tclx
o tclx-devel
o tclx-doc
o tetex-doc
o theora-tools
o thunderbird
o tix-devel
o tix-doc
o tk-devel
o tn5250-devel
o ttfonts-bn
o ttfonts-gu
o ttfonts-hi
o ttfonts-pa
o ttfonts-ta
o udev
o unixODBC-devel
o vim-X11
o vino
o w3c-libwww-apps
o w3c-libwww-devel
o xcdroast
o xdelta-devel
o xemacs-common
o xemacs-nox
o xemacs-sumo
o xemacs-sumo-el
o xemacs-sumo-info
o xisdnload
o xmlsec1
o xmlsec1-devel
o xmlsec1-openssl
o xmlsec1-openssl-devel
o xmms-devel
o xmms-flac
o xmms-skins
o xojpanel
o xorg-x11
o xorg-x11-Mesa-libGL
o xorg-x11-Mesa-libGLU
o xorg-x11-Xdmx
o xorg-x11-Xnest
o xorg-x11-Xvfb
o xorg-x11-deprecated-libs
o xorg-x11-deprecated-libs-devel
o xorg-x11-devel
o xorg-x11-doc
o xorg-x11-font-utils
o xorg-x11-libs
o xorg-x11-sdk
o xorg-x11-tools
o xorg-x11-twm
o xorg-x11-xauth
o xorg-x11-xdm
o xorg-x11-xfs
o xrestop
o zisofs-tools
o zsh-html
Packages Removed
The following packages have been removed from Scientific Linux 4.0:
o FreeWnn-common
o Wnn6-SDK
o Wnn6-SDK-devel
o XFree86
o XFree86-100dpi-fonts
o XFree86-75dpi-fonts
o XFree86-ISO8859-14-100dpi-fonts
o XFree86-ISO8859-14-75dpi-fonts
o XFree86-ISO8859-15-100dpi-fonts
o XFree86-ISO8859-15-75dpi-fonts
o XFree86-ISO8859-2-100dpi-fonts
o XFree86-ISO8859-2-75dpi-fonts
o XFree86-ISO8859-9-100dpi-fonts
o XFree86-ISO8859-9-75dpi-fonts
o XFree86-Mesa-libGL (i386)
o XFree86-Mesa-libGL (ia64)
o XFree86-Mesa-libGLU
o XFree86-Xnest
o XFree86-Xvfb
o XFree86-base-fonts
o XFree86-cyrillic-fonts
o XFree86-devel
o XFree86-doc
o XFree86-font-utils
o XFree86-libs (i386)
o XFree86-libs (ia64)
o XFree86-libs-data
o XFree86-syriac-fonts
o XFree86-tools
o XFree86-truetype-fonts
o XFree86-twm
o XFree86-xauth
o XFree86-xdm
o XFree86-xfs
o ami
o anaconda-images
o ant
o ant-libs
o aspell-en-ca
o aspell-en-gb
o aspell-pt_BR
o bcel
o bonobo-activation
o bonobo-activation-devel
o cipe
o commons-beanutils
o commons-collections
o commons-digester
o commons-logging
o commons-modeler
o compat-gcc
o compat-gcc-c++
o compat-glibc
o compat-libstdc++
o compat-libstdc++-devel
o compat-pwdb
o compat-slang
o cup
o db4 (i386)
o dev
o devlabel
o dvdrecord
o expat (i386)
o fam
o fam-devel
o fontconfig (i386)
o fontilus
o freetype (i386)
o gcc-c++-ssa
o gcc-g77-ssa
o gcc-gnat
o gcc-java-ssa
o gcc-objc-ssa
o gcc-ssa
o gdk-pixbuf-gnome
o glibc (i686)
o gnome-libs
o gnome-libs-devel
o gnome-vfs2-extras
o gpm (i386)
o gtkam
o gtkam-gimp
o im-sdk
o imap
o itcl
o jakarta-regexp
o jfsutils
o kde-i18n-Afrikaans
o kde-i18n-Korean
o kdoc
o kernel-source
o kernel-unsupported
o kinput2-canna-wnn6
o krb5-libs (i386)
o libgcc (i386)
o libgcc-ssa
o libgcj (i386)
o libgcj-ssa
o libgcj-ssa-devel
o libgnat
o libmrproject
o libmudflap
o libmudflap-devel
o libole2
o libole2-devel
o libstdc++ (i386)
o libstdc++-ssa
o libstdc++-ssa-devel
o linc
o linc-devel
o losetup
o lvm
o magicdev
o modutils
o modutils-devel
o mount
o mozilla-psm
o mrproject
o mx4j
o ncurses (i386)
o openssl (i686)
o perl-CGI
o perl-CPAN
o perl-DB_File
o perl-Net-DNS
o printman
o pspell
o pspell-devel
o python-optik
o raidtools
o rarpd
o redhat-config-bind
o redhat-config-date
o redhat-config-httpd
o redhat-config-keyboard
o redhat-config-kickstart
o redhat-config-language
o redhat-config-mouse
o redhat-config-network
o redhat-config-network-tui
o redhat-config-nfs
o redhat-config-packages
o redhat-config-printer
o redhat-config-printer-gui
o redhat-config-proc
o redhat-config-rootpassword
o redhat-config-samba
o redhat-config-securitylevel
o redhat-config-securitylevel-tui
o redhat-config-services
o redhat-config-soundcard
o redhat-config-users
o redhat-config-xfree86
o redhat-java-rpm-scripts
o redhat-logviewer
o redhat-switch-mail
o redhat-switch-mail-gnome
o rh-postgresql
o rh-postgresql-contrib
o rh-postgresql-devel
o rh-postgresql-docs
o rh-postgresql-jdbc
o rh-postgresql-libs
o rh-postgresql-python
o rh-postgresql-tcl
o shapecfg
o switchdesk
o switchdesk-gnome
o switchdesk-kde
o xalan-j
o xerces-j
o zlib (i386)
Packages Deprecated
We seek to preserve functionality across major releases, but
reserves the right to change the specific implementation and packaging of
components between major releases.
The following packages are included in Scientific Linux 4.0, but may
be removed from future releases. Developers and users are advised to
migrate away from these packages.
o 4Suite -- Only used by system-config-* tools
o FreeWnn -- IIIMF is the recommended input method
o FreeWnn-devel -- IIIMF is the recommended input method
o FreeWnn-libs -- IIIMF is the recommended input method
o alchemist -- Only used by system-config-* tools
o alchemist-devel -- Only used by system-config-* tools
o aumix -- Redundant with other volume control tools
o autoconf213 -- Backwards compatibility dev tool
o automake14 -- Backwards compatibility dev tool
o automake15 -- Backwards compatibility dev tool
o automake16 -- Backwards compatibility dev tool
o automake17 -- Backwards compatibility dev tool
o compat-db -- Backwards compatibility library
o compat-gcc-32 -- Backwards compatibility library/tool
o compat-gcc-32-c++ -- Backwards compatibility library/tool
o compat-glibc -- Backwards compatibility library/tool
o compat-libgcc-296 -- Backwards compatibility library/tool
o compat-libstdc++-296 -- Backwards compatibility library/tool
o compat-libstdc++-33 -- Backwards compatibility library/tool
o compat-openldap -- Backwards compatibility library/tool
o dbskkd-cdb -- IIIMF is the recommended input method
o dev86 -- Required only for lilo
o dietlibc -- Only supported for installer use
o eog -- Integrated support in Nautilus
o gftp -- Integrated FTP in Firefox and Nautilus
o gnome-libs -- Replaced by libgnome
o imlib -- Replaced by gdk-pixbuf
o imlib-devel -- Replaced by gdk-pixbuf
o kinput2 -- IIIMF is the recommended input method
o libghttp -- Deprecated library
o libghttp-devel -- Deprecated library
o mikmod -- Deprecated sound format
o mikmod-devel -- Deprecated sound format
o miniChinput -- IIIMF is the recommended input method
o mozilla -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-chat -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-devel -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-dom-inspector -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-js-debugger -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-mail -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-nspr -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-nspr-devel -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-nss -- Replaced by Firefox/Thunderbird/Evolution
o mozilla-nss-devel -- Replaced by Firefox/Thunderbird/Evolution
o nabi -- IIIMF is the recommended input method
o newt-perl -- Only required by crypto-utils
o openmotif21 -- Backwards compatibility library
o openssl096b -- Backwards compatibility library
o skkdic -- IIIMF is the recommended input method
o skkinput -- IIIMF is the recommended input method
o xcin -- IIIMF is the recommended input method
o xmms -- Replaced by rhythmbox, Helix Player
o xmms-devel -- Replaced by rhythmbox, Helix Player
o xmms-flac -- Replaced by rhythmbox, Helix Player
o xmms-skins -- Replaced by rhythmbox, Helix Player
( ia64 )
|
