[Fwd: Red Hat Enterprise Linux 3 Update 4 *Beta* Availability Announcement]
[email protected] Fri, 22 Oct 2004 15:31:22 -0400
| Newsgroups | gmane.linux.redhat.taroon |
|---|---|
| Message-ID | <[email protected]> |
--=-iwNH2+fZruXzp0FuV1hy Content-Type: text/plain Content-Transfer-Encoding: 7bit --=-iwNH2+fZruXzp0FuV1hy Content-Disposition: inline Content-Description: Attached message - Red Hat Enterprise Linux 3 Update 4 *Beta* Availability Announcement Content-Type: message/rfc822 Return-Path: <[email protected]> Received: from mail.boston.redhat.com ([unix socket]) by mail.boston.redhat.com (Cyrus v2.1.12) with LMTP; Fri, 22 Oct 2004 15:28:51 -0400 X-Sieve: CMU Sieve 2.2 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id i9MJSpPd024425; Fri, 22 Oct 2004 15:28:51 -0400 Received: from mx1.util.phx.redhat.com (mx1.util.phx.redhat.com [10.8.4.92]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9MJSnr06212; Fri, 22 Oct 2004 15:28:49 -0400 Received: from hormel.redhat.com (hormel.util.phx.redhat.com [10.8.4.111]) by mx1.util.phx.redhat.com (8.11.6/8.11.6) with ESMTP id i9MJSnx25853; Fri, 22 Oct 2004 15:28:49 -0400 Received: from listman.util.phx.redhat.com (listman.util.phx.redhat.com [10.8.4.110]) by hormel.redhat.com (Postfix) with ESMTP id 362C772EAC; Fri, 22 Oct 2004 15:28:52 -0400 (EDT) Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.util.phx.redhat.com (8.12.11/8.12.10) with ESMTP id i9MJS5OM023121 for <taroon-list-LDDX7aEP/i07/[email protected]>; Fri, 22 Oct 2004 15:28:05 -0400 Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9MJS5r05833 for <[email protected]>; Fri, 22 Oct 2004 15:28:05 -0400 Received: from [172.16.80.60] (maniac.boston.redhat.com [172.16.80.60]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id i9MJS3Pd024365 for <[email protected]>; Fri, 22 Oct 2004 15:28:03 -0400 To: [email protected] Content-Type: multipart/mixed; boundary="=-F7D+YA+371osL3neyAUT" Date: Fri, 22 Oct 2004 15:28:23 -0400 Message-Id: <1098473304.4161.83.camel-ZxiUL3e3WckEMMbVNdFDoACJwEvxM/[email protected]> Mime-Version: 1.0 X-Mailer: Evolution 1.5.94.1 (1.5.94.1-1) X-loop: [email protected] X-Mailman-Approved-At: Fri, 22 Oct 2004 15:28:47 -0400 From: [email protected] Subject: Red Hat Enterprise Linux 3 Update 4 *Beta* Availability Announcement X-BeenThere: [email protected] X-Mailman-Version: 2.1.5 Precedence: junk Reply-To: [email protected] List-Id: "Discussion of Red Hat Enterprise Linux 3 \(Taroon\)" <taroon-list.redhat.com> List-Unsubscribe: <http://www.redhat.com/mailman/listinfo/taroon-list>, <mailto:[email protected]?subject=unsubscribe> List-Archive: </archives/taroon-list> List-Post: <mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help> List-Subscribe: <http://www.redhat.com/mailman/listinfo/taroon-list>, <mailto:[email protected]?subject=subscribe> Sender: [email protected] Errors-To: [email protected] X-Evolution-Source: imap://[email protected]/ --=-F7D+YA+371osL3neyAUT Content-Type: text/plain Content-Transfer-Encoding: 7bit Red Hat is pleased to announce the availability of the *beta* release of Update 4 for the Red Hat Enterprise Linux 3 family of products, including: - Red Hat Enterprise Linux AS (v. 3 for x86) - Red Hat Enterprise Linux AS (v. 3 for Itanium) - Red Hat Enterprise Linux AS (v. 3 for AMD64 and Intel(r) EM64T) - Red Hat Enterprise Linux AS (v. 3 for iSeries and pSeries) - Red Hat Enterprise Linux AS (v. 3 for S/390) - Red Hat Enterprise Linux AS (v. 3 for zSeries) - Red Hat Enterprise Linux ES (v. 3 for x86) - Red Hat Enterprise Linux ES (v. 3 for Itanium) - Red Hat Enterprise Linux ES (v. 3 for AMD64 and Intel(r) EM64T) - Red Hat Enterprise Linux WS (v. 3 for x86) - Red Hat Enterprise Linux WS (v. 3 for Itanium) - Red Hat Enterprise Linux WS (v. 3 for AMD64 and Intel(r) EM64T) - Red Hat Desktop (v. 3 for x86, AMD64 and Intel(r) 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. - Expanded runtime compatibility library coverage for multi-arch platforms, including AMD64/Intel(r) EM64T, Itanium2, IBM iSeries/pSeries, and IBM zSeries. - Updated Intel IA32 Execution Layer for the Itanium2 architecture. - iSCSI software initiator support, and a new package iscsi-initiator-tools with supporting daemon and utilities. - Local disk kernel crashdump support for AMD64 and Intel(r) EM64T platforms. - Driver updates including Adaptec RAID (aacraid), LSI Logic RAID (megaraid), IBM ServeRAID (ips), LSI Logic MPT Fusion (mpt*), Compaq SA53xx Controllers (cciss), QLogic Fibre Channel (qla2xxx), Intel PRO/1000 (e1000), Intel PRO/100 (e100), Broadcom Tigon3 (tg3), Network Bonding (bonding), Emulex (lpfc), i810 Audio, PCNet32, FCP adapter for zSeries (zfcp), and Serial ATA (libata). - Security updates, bug fixes, and feature enhancements to numerous system packages. Packages updated or added in this beta release include: amtu, anaconda, at, autofs, bind, bonobo-activation, busybox, caching-nameserver, devlabel, dhcp, eal3-certification, esound, evolution, firstboot, freeradius, gaim, gcc, gdb, gimp-print, glibc, gnome-desktop, gtk2, guile, httpd, hwdata, ia32el, initscripts, ipsec-tools, iputils, iscsi-initiator-tools, kernel, krb5, kudzu, laus, libsvg2, libtiff, lvm, mailman, man-pages, metacity, modutils, mysql, nedit, net-snmp, net-snmp, net-tools, nfs-utils, openssh, pam, php, piranha, procps, psacct, pump, quotactl, redhat-config-date, redhat-config-netboot, redhat-config-services, redhat-config-users, rhn-applet, rh-postgresql, rpm, rusers, shadow-utils, sysreport, sysstat, tcsh, tftp, tzdata, up2date, usermode, util-linux, vim, vnc, vsftpd, vte, xchat, xscreensaver, ypbind, ypserv, yp-tools 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 November 17, 2004. 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 3 Update 4 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 ------------- To ensure accurate tracking and follow-up, all bugs should be reported using Bugzilla 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 'rhel3-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 3 beta programs. * [email protected] A public general discussion mailing list for beta testers of Red Hat Enterprise Linux 3 updates. Subscribe at: https://www.redhat.com/mailman/listinfo/taroon-beta-list Thank you for participating in the Red Hat Enterprise Linux 3 Update 4 beta program. Sincerely, The Red Hat Enterprise Linux Team --=-F7D+YA+371osL3neyAUT Content-Disposition: attachment; filename=RELEASE-NOTES-U4-en Content-Type: text/plain; name=RELEASE-NOTES-U4-en; charset=UTF-8 Content-Transfer-Encoding: 7bit Red Hat Enterprise Linux AS 3 Update 4 *Beta* Release Notes Copyright (c) 2004 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 Kernel-related information 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 3 system to Update 4, you must use Red Hat Network to update those packages that have changed. The use of Anaconda to upgrade to Update 4 is not supported. Use Anaconda only to perform a fresh install of Red Hat Enterprise Linux 3 Update 4. o If you are copying the contents of the Red Hat Enterprise Linux 3 Update 4 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 3 Update 4 now includes Mailman, an electronic mail discussion and e-newsletter lists system. Mailman is integrated with the Web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, spam filters, and more. Kernel-Related Information This section contains information related to the Red Hat Enterprise Linux 3 Update 4 kernel. o The Open Sound System (OSS) AC97 plugin infrastructure has been backported to the Red Hat Enterprise Linux 3 Update 4 kernel. This allows registering modules to modify the behavior of the OSS subsystem depending on the AC97 CODEC(s) in use. Note Because the OSS subsystem is not supported in the hugemem kernel, the AC97 plugin infrastructure is unavailable in the hugemem kernel. o The release notes for Red Hat Enterprise Linux 3 Update 3 contained information related to Exec-Shield. This information was not entirely accurate; the corrected information appears below. The Red Hat Enterprise Linux 3 Update 4 kernel includes a new security feature known as Exec-Shield. Exec-Shield is a security-enhancing modification to the Linux kernel that makes large parts of specially-marked programs -- including their stack -- not executable. This can reduce the potential damage of some security holes, such as buffer overflow exploits. Exec-Shield can also randomize the virtual memory addresses at which certain binaries are loaded. This randomized VM mapping makes it more difficult for a malicious application to improperly access code or data based on knowledge of the code or data's virtual address. Exec-Shield's behavior can be controlled via the proc file system. Two files are used: o /proc/sys/kernel/exec-shield o /proc/sys/kernel/exec-shield-randomize The /proc/sys/kernel/exec-shield file controls overall Exec-Shield functionality, and can be manipulated using the following command: echo <value> > /proc/sys/kernel/exec-shield Where <value> is one of the following: o 0 -- Exec-Shield (including randomized VM mapping) is disabled for all binaries, marked or not o 1 -- Exec-Shield is enabled for all marked binaries The default value for /proc/sys/kernel/exec-shield is 1. The /proc/sys/kernel/exec-shield-randomize file controls whether Exec-Shield randomizes VM mapping, and can be manipulated using the following command: echo <value> > /proc/sys/kernel/exec-shield-randomize Where <value> is one of the following: o 0 -- Randomized VM mapping is disabled o 1 -- Randomized VM mapping is enabled The default value for /proc/sys/kernel/exec-shield-randomize is 1. It is also possible to configure Exec-Shield by including one (or both) of the following lines in the /etc/sysctl.conf file: kernel.exec-shield=<value> kernel.exec-shield-randomize=<value> (Where <value> is as previously described.) Exec-Shield can also be disabled at a system level by means of a kernel boot option. Appending the following parameter to the "kernel" line(s) in the /etc/grub.conf file will disable Exec-Shield: exec-shield=0 Note Exec-Shield functionality is available only to binaries that have been built (and marked) using the toolchain (compiler, assembler, linker) available with Red Hat Enterprise Linux 3. Binaries that have been built using a different version of the toolchain can still be used, but since they will not be marked, they will not take advantage of Exec-Shield. Application developers should keep in mind that, in the majority of cases, GCC correctly marks its generated code as being capable of using Exec-Shield. In the few instances (usually caused by inline assembler or other nonportable code) where GCC non-optimally (or, more rarely, incorrectly) marks generated code, it is possible to pass GCC options to obtain the desired result. The options controlling binary marking at the assembler level are: -Wa,--execstack -Wa,--noexecstack The options controlling binary marking at the linker level are: -Wl,-z,execstack -Wl,-z,noexecstack It is also possible to exert more fine-grained control by explicitly disabling Exec-Shield for a specific binary at run time. This is done using the setarch command: setarch i386 <binary> (Where <binary> represents the binary to be run.) The binary is then run without Exec-Shield functionality. The proc file /proc/self/maps can be used to observe Exec-Shield's effects. By using cat to display the current process's VM mapping, you can see Exec-Shield at work. Similarly, you can use setarch in conjunction with cat to see how normal VM mapping differs from Exec-Shield's mapping. ( x86 ) --=-F7D+YA+371osL3neyAUT Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit -- Taroon-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/taroon-list --=-F7D+YA+371osL3neyAUT-- --=-iwNH2+fZruXzp0FuV1hy Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Taroon-beta-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/taroon-beta-list --=-iwNH2+fZruXzp0FuV1hy--