java-1.4.2-ibm bug fix update

Updated java-1.4.2-ibm packages that fix a packaging issue are now
available.

The following packages comprise IBM's 1.4.2 Java release:

java-1.4.2-ibm
java-1.4.2-ibm-devel
java-1.4.2-ibm-src
java-1.4.2-ibm-demo
java-1.4.2-ibm-plugin

These packages include the IBM Java 2 Runtime Environment and the IBM Java
2 Software Development Kit.

The Java 2 Runtime Environment (JRE) consists of the Java virtual machine,
the Java platform core classes and supporting files, and includes a Web
browser plug-in for running Java applets. It is the runtime section of the
Java 2 SDK, but without the development tools such as compilers and debuggers.

The Java 2 Software Development Kit (SDK) is a development environment for
building applications, applets, and components that can be deployed on the
Java platform. The Java 2 SDK software includes tools useful for
developing and testing programs written in the Java programming language.
The Java 2 SDK software also includes a JDBC/ODBC bridge for Java
applications that need to communicate with a database.

These updated packages resolve a packaging issue. The plugin sub-package
no longer takes ownership of the /usr/lib/mozilla/plugins directory.

All users of java-1.4.2-ibm should upgrade to these updated packages, which
resolve these issues.

Note for AMD64 users: If you have been using the i386 packages on an AMD64
RHEL3 installation, it is important that you remove the i386 packages
before installing these new AMD64 packages. There is an RPM bug which
breaks alternatives symlinks if two packages of the same name, but for
different architectures, are installed on the same machine. See this bug
report for details: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127359

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains the
desired RPMs.

Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.

136378 - wrong /etc/mailcap entries for javaws (jnlp)
137236 - java-1.4.2-ibm should provide an rt.jar symlink to core.jar
142151 - JVMs hang on RHEL 3 Update 3 when booted in SMP kernel
150219 - LTC14314- PrivilegedExceptionAction failure on x86-64
150242 - LTC14305- strange results from log2up
163649 - java-1.4.2-ibm-plugin should not own /usr/lib/mozilla/plugins directory