[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Red Hat Enterprise Linux 4 Update 1 *Beta* Availability Announcement



Red Hat is pleased to announce the availability of the *beta*
release of Update 1 for the Red Hat Enterprise Linux 4 family 
of products, including:

 - Red Hat Enterprise Linux AS (v. 4) for x86, AMD64/EM64T, Itanium, 
    POWER, S/390 and zSeries
 - Red Hat Enterprise Linux ES (v. 4) for x86, AMD64/EM64T, Itanium
 - Red Hat Enterprise Linux WS (v. 4) for x86, AMD64/EM64T, Itanium
 - Red Hat Desktop (v. 4) for x86 and AMD64/EM64T

This update beta includes the following enhancements:
  
 - Availability of a full set of updated installable CD ISO 
    images via Red Hat Network, with OS package updates and 
    install-time support for new hardware.

 - Availability of updated Extras ISO images via Red Hat 
    Network, with third party package updates.

 - Dual core support for AMD64 Opteron and Intel EM64T ICH7 
   systems.

 - Support for ICH7, including Glenwood and Lakeport chipsets.

 - Improved disk dump capability (including SATA and 
   megaraid support).

 - Updated Intel IA32 Execution Layer for the Itanium2 
   architecture.

 - Driver updates including lpfc, megaraid, e100, e1000, 
   and SATA.

 - Updated Intel Centrino ipw2100/ipw2200 wireless drivers.

 - Many platform hardware support updates and bug fixes.

 - Security updates, bug fixes, and feature enhancements to
    numerous system packages.

Packages updated or added in this beta release include:
 anaconda, anaconda-product, apr, authconfig, autofs, binutils,
 bootparamd, chkconfig, compat-libcom_err, comps, coreutils, crash,
 dbus, device-mapper, diskdumputils, dmraid, dovecot, e2fsprogs,
 elinks, evolution, evolution-connector, evolution-data-server, 
 fonts-xorg, gcc, gdb, gdm, glibc, gsl, gtk2, hotplug, httpd, 
 hwbrowser, hwdata, ia32el, im-sdk, initscripts, 
 java-1.4.2-gcj-compat, kernel, kernel-utils, krb5, kudzu, 
 libtool, lsof, lvm2, man-pages-ja, mod_auth_mysql, mysql, 
 netdump, net-tools, NetworkManager, nss_ldap, openCryptoki, 
 openoffice.org, openssh, pam, pango, pciutils, pcmcia-cs, 
 policycoreutils, postgresql, postgresql-odbc, procps, psacct, 
 redhat-lsb, redhat-release, rpm, rpmdb-redhat, rsh, 
 selinux-policy-targeted, strace, sysreport, 
 system-config-kickstart, system-config-lvm, tcpdump, telnet, 
 tzdata, up2date, xinetd, and xorg-x11

The beta update packages and CD images are intended for testing 
purposes only, and will be followed up with official, supported 
update packages delivered as official product errata when testing 
is complete.  Red Hat may, at any time, change the contents of 
any or all of these beta updates.  The beta testing period is 
scheduled to continue through May 18, 2005.

Please remember that this beta software is not supported and 
is not intended for production environments!  Please do not publish
any benchmark or performance results based on this beta release.  
Upgrades will *not* be supported from the beta update to the 
subsequent official update; a fresh base install will be 
required.

This message includes details on obtaining the early access software, 
reporting bugs, and communicating with Red Hat and other testers via 
mailing lists during the early access period.

A draft of the beta release notes for this update is attached.

For specific package change logs and version levels, consult the
architecture-specific channel package lists on Red Hat Network.

Accessing the Software
----------------------

The beta update packages are available via Red Hat Network
(https://rhn.redhat.com) to all current Red Hat Enterprise Linux
subscribers.  The updates are available via two methods:
 
(a) Install from new ISO images

Once you have logged in to RHN, click on the "Software" tab and choose
the appropriate child channel entitled "<product name> Beta".  
Click on the 'Downloads' sub-tab, and follow the directions 
provided to download installable ISO images for your platform and
release.  

For Red Hat Enterprise Linux 4 Update 1 Beta, a completely
new installable ISO image set is provided.

(b) Update existing test installation using RHN beta channel

Once you have logged in to RHN, click on the "Software" tab and choose
the appropriate child channel entitled "<product name> Beta".  
Click on the "Target Systems" subtab, and select all of the 
non-production, test systems you wish to run in the beta errata 
program.  Click on the "subscribe" button to apply the 
selection(s).

Once the beta channel has been subscribed, run the following command 
from a shell prompt on each target system to update any packages for
which new versions exist:

  up2date

You will see a list of packages that are available to be installed.
Select all packages and step through the instructions.  Note: you will
optionally be able to skip installation of the kernel.  Do not skip the
kernel!  Be sure to select it as well for installation.

For more information, Red Hat Network user guides and FAQs are 
available on the RHN website at https://rhn.redhat.com.

* Note: Systems that are updated with the beta update will not be 
upgradeable to the official update.  A fresh install will be 
required to ensure support! *

Bug Reporting
-------------

Red Hat customers with active support contracts should report their
bugs through Red Hat support at:
  http://www.redhat.com/support

Red Hat partners with Issue Tracker accounts should report their
bugs through the Issue Tracker interface at:
  https://enterprise.redhat.com/issue-tracker/

All other testers should report bugs directly via the public 
bugzilla tool at:
  http://bugzilla.redhat.com

If you do not have a bugzilla account, please visit this URL and 
create one.
 
If you already have a bugzilla account:
 
1.  On bugzilla's home page at http://bugzilla.redhat.com, choose the
"New" tab at the top of the web page.  Proceed to Step 3, Choosing 
Your Product by clicking that button at the bottom of the web page.
 
2.  Choose "Red Hat Enterprise Linux Public Beta".  Proceed to Step 4, 
Choosing Component by clicking that button at the bottom of the 
web page.
 
3.  Choose the component against which you want to report a problem,
such as kernel, glibc, etc.

4.  Scroll the page to Step 5, Choosing Version and Architecture.  In
the Version field, choose 'rhel4-update'.  Choose the appropriate
architecture.  Proceed to Step 6, Additional Info, by clicking that 
button at the bottom of the web page.
 
5.  Provide the information about the problem you're reporting by
entering information in the appropriate fields. Then click the "Open
Bugzilla Entry Form" button. In the summary of the bug, and in the
text describing your problem, please state clearly that you are using 
a *BETA* package and provide the full package versions of any components 
you are experiencing problems with (as beta packages may be updated 
during the beta period).  Check to make sure that all information is 
accurate and click the Commit button to submit your problem report.

Mailing Lists
-------------

Red Hat has created a public mailing list for communication during 
this and all future Red Hat Enterprise Linux 4 beta programs. 

* rhelv4-announce redhat com

  A low-volume, moderated, announcement-only mailing list.  Red Hat 
  will use this list to communicate one-way information about RHEL 4
  beta programs, such as notifications when updates are 
  available or solicitations for beta feedback.  Subscribe at:
    https://www.redhat.com/mailman/listinfo/rhelv4-announce

* nahant-beta-list redhat com

  A public general discussion mailing list for beta testers of 
  Red Hat Enterprise Linux 4 updates.  Subscribe at:
    https://www.redhat.com/mailman/listinfo/nahant-beta-list

Thank you for participating in the Red Hat Enterprise Linux 4
Update 1 beta program. 

Sincerely,

The Red Hat Enterprise Linux Team
              Red Hat Enterprise Linux 4 Update 1 Release Notes

   Copyright (c) 2005 Red Hat, Inc.

     ----------------------------------------------------------------------

Introduction

   The following topics are covered in this document:

     o Changes to the Red Hat Enterprise Linux installation program
       (Anaconda)

     o General information

     o Changes to drivers and hardware support

Changes to the Red Hat Enterprise Linux Installation Program (Anaconda)

   The following section includes information specific to the Red Hat
   Enterprise Linux installation program, Anaconda.

  Note

   In order to upgrade an already-installed Red Hat Enterprise Linux 4 system
   to Update 1, you must use Red Hat Network to update those packages that
   have changed.

   You may use Anaconda to perform a fresh installation of Red Hat Enterprise
   Linux 4 Update 1 or to perform an upgrade from the latest updated version
   of Red Hat Enterprise Linux 3 to Red Hat Enterprise Linux 4.

     o If you are copying the contents of the Red Hat Enterprise Linux 4
       Update 1 CD-ROMs (in preparation for a network-based installation, for
       example) be sure you copy the CD-ROMs for the operating system only.
       Do not copy the Extras CD-ROM, or any of the layered product CD-ROMs,
       as this will overwrite files necessary for Anaconda's proper
       operation.

       These CD-ROMs must be installed after Red Hat Enterprise Linux has
       been installed.

General Information

   This section contains general information not specific to any other
   section of this document.

     o Red Hat Enterprise Linux 4 Update 1 now includes the diskdump
       facility,which can serve as an alternative to (or be used in
       conjunction with) the Red Hat netdump facility.

       The diskdump facility for i386 systems currently support the aic7xxx,
       aic79xx, mpt fusion, megaraid, and SATA devices. On ia64 systems, the
       aic7xxx, aic79xx, mpt fusion, and SATA devices are supported. On AMD64
       and Intel(R) EM64T systems, the aic7xxx, aic79xx, mpt fusion,
       megaraid, and SATA 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 Red Hat
       Enterprise Linux 4 Update 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 Red Hat Enterprise Linux 4 kernel. The
       associated user-space diskdump package is named diskdumputils-1.0.0,
       and like netdump, is installed by default.

       The available and 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.0/README

       Further information can be found in the diskdumpfmt(8),
       diskdumpctl(8), and savecore(8) man pages.

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
   Red Hat Enterprise Linux update is applied, because in most cases only one
   older-revision driver will be preserved for each update.

   ( x86 )

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]