diff --git a/en/releases/4.1.1R/announce.sgml b/en/releases/4.1.1R/announce.sgml index a109bda198..e3d1fa3326 100644 --- a/en/releases/4.1.1R/announce.sgml +++ b/en/releases/4.1.1R/announce.sgml @@ -1,83 +1,87 @@ - + + %navincludes; %includes; ]> &header;

Date: Wed, 27 Sep 2000 00:07:50 -070
From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
To: announce@FreeBSD.org
Subject: 4.1.1-RELEASE now available from ftp.freebsd.org

As always, I'm pleased to announce the availability of FreeBSD 4.1.1-RELEASE, a point release update for 4.1-RELEASE and, of course, the very latest in 4.x-STABLE branch technology.

Since 4.1-RELEASE was produced in August 2000, RSA released their code into the public domain and a number of other security enhancements were made possible through the FreeBSD project's permission to export cryptographic code from the United States. These changes are fully reflected in 4.1.1-RELEASE, making it one of the most secure "out of the box" releases of FreeBSD we've ever done.

We also took the opportunity to include support for new features like IDE ATA100 support, drivers for additional Gigabit ethernet cards and hardware watchpoints in gdb. Please see the release notes for more information.

The 4.1.1-RELEASE is available right now for the i386 architecture (alpha to follow in several days) in "FTP installable" and ISO image form. For the appropriate bits, please see:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.1.1-RELEASE/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.1.1-install.iso

When the Alpha release follows in several days, it will be available from:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.1.1-RELEASE/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.1.1-install.iso

Please watch the alpha@freebsd.org mailing list for an announcement.

IMPORTANT NOTE: This is a network only point release and will not be made generally available for sale on CDROM, at least not from BSDi or anyone else we currently have knowledge of. The next official CD release will be FreeBSD 4.2-RELEASE, still scheduled for mid-November 2000.

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

Before trying the central FTP site, please check your regional mirror(s) first by going to:

   ftp://ftp.<yourdomain>.freebsd.org/pub/FreeBSD
- +

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Thanks! - Jordan + +&footer; + diff --git a/en/releases/4.10R/announce.sgml b/en/releases/4.10R/announce.sgml index 86fed545ed..e1d4905e2c 100644 --- a/en/releases/4.10R/announce.sgml +++ b/en/releases/4.10R/announce.sgml @@ -1,210 +1,213 @@ - + + %navincludes; %includes; ]> &header;

Date: Thu, 27 May 2004 01:35:03 -0400
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD &local.rel;-RELEASE is now available

I am happy to announce the availability of FreeBSD &local.rel;-RELEASE, the latest release of the FreeBSD -STABLE development branch. Since FreeBSD 4.9-RELEASE in October 2003 we have made conservative updates to a number of software programs in the base system, dealt with known security issues, and made many bugfixes.

For a complete list of new features, known problems, and late-breaking news, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/&local.rel;R/relnotes.html

http://www.FreeBSD.org/releases/&local.rel;R/errata.html

FreeBSD &local.rel; will become the first "Errata Branch". Release branches for previous versions of FreeBSD would only have critical security fixes applied. With FreeBSD &local.rel; the scope of fixes will be expanded to include local Denial of Service fixes as well as other significant and well-tested fixes that may not represent security issues.

The current plans are for one more FreeBSD 4.X release which will be FreeBSD 4.11-RELEASE. It is expected the upcoming FreeBSD 5.3 release will have reached the maturity level most users will be able to migrate to 5.X. Most developer resources continue to be devoted to the 5.X branch.

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Availability

FreeBSD &local.rel;-RELEASE supports the i386 and alpha architectures and can be installed directly over the net, using bootable media, or copied to a local NFS/FTP server. Distributions for both architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD &local.rel; based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemon News http://www.bsdmall.com/freebsd1.html

If you can not afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can not promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 checksums for the release images are included at the bottom of this message.

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Canada, China, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland, Ireland, Italy, Japan, Korea, Lithuania, Netherlands, Norway, Poland, Portugal, Romania, Russia, Saudi Arabia, Singapore, Slovak Republic, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Turkey, Ukraine, United Kingdom, and the United States.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD &local.rel; including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for &local.rel;-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, Alpha Release Building
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Release Engineering, I386 Release Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer

CD Image Checksums

For i386:

MD5 (4.10-RELEASE-i386-disc1.iso) = acdfe766794b0b5fbb2e5997af6e78dd
MD5 (4.10-RELEASE-i386-disc2.iso) = 502c14e2e2d62c15d302da51ea36c199
MD5 (4.10-RELEASE-i386-miniinst.iso) = 3214c17137439ad422f53606d5626cad

For Alpha:

MD5 (4.10-RELEASE-alpha-disc1.iso) = 529fe8669a3fb5e127b5affc48b4c669
MD5 (4.10-RELEASE-alpha-disc2.iso) = b0d0293bfa7e6764800cb29dd22ebf45
MD5 (4.10-RELEASE-alpha-miniinst.iso) = c7c5d3149e32f88cfaef0759dfee2c55

-ken

+ + &footer; diff --git a/en/releases/4.10R/hardware.sgml b/en/releases/4.10R/hardware.sgml index 2dbc24f37d..e36454dcb5 100644 --- a/en/releases/4.10R/hardware.sgml +++ b/en/releases/4.10R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.10-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.10R/installation.sgml b/en/releases/4.10R/installation.sgml index 469057e7e4..3b8cf24968 100644 --- a/en/releases/4.10R/installation.sgml +++ b/en/releases/4.10R/installation.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 4.10-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.10R/qa.sgml b/en/releases/4.10R/qa.sgml index 5d6e319c60..aaed44d3b0 100644 --- a/en/releases/4.10R/qa.sgml +++ b/en/releases/4.10R/qa.sgml @@ -1,57 +1,58 @@ - + + %navincludes; %includes; ]> &header;

Goals

As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in &rel; that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:

To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.

Features to explore carefully:

The release notes will always be a good place to look for things to test.

Known Issues

&footer; diff --git a/en/releases/4.10R/relnotes.sgml b/en/releases/4.10R/relnotes.sgml index f44183d02a..d774efde77 100644 --- a/en/releases/4.10R/relnotes.sgml +++ b/en/releases/4.10R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.10-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.10R/schedule.sgml b/en/releases/4.10R/schedule.sgml index e82d9c4e5c..c8c343b1b8 100644 --- a/en/releases/4.10R/schedule.sgml +++ b/en/releases/4.10R/schedule.sgml @@ -1,319 +1,320 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
ActionExpectedActualDescription
Reminder announcement 30 Mar 2004 30 Mar 2004 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD &local.rel; release.
&local.rel;-BETA Testing Guide published 30 Mar 2004 30 Mar 2004 A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period.
Announce the Ports Freeze 03 Apr 2004 03 Apr 2004 Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree.
&local.rel;-BETA 7 Apr 2004 10 Apr 2004 newvers.sh, and release.ent updated.
Code freeze begins 7 Apr 2004 7 Apr 2004 After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers@, stable@ and qa@ lists.
RELENG_&local.rel.tag; branch 20 Apr 2004 21 Apr 2004 The release branch is created.
Unfreeze the tree 20 Apr 2004 22 Apr 2004 Announcement to developers@ explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_&local.rel.tag; branch.
&local.rel;-RC 20 Apr 2004 24 Apr 2004 newvers.sh and release.ent updated.
First release candidate 21 Apr 2004 22 Apr 2004 The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks.
Heads up to -stable 21 Apr 2004 23 Apr 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate 27 Apr 2004 2 May 2004 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable 28 Apr 2004 3 May 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded.
Third release candidate -- 17 May 2004 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable -- 17 May 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Ports tree frozen 20 Apr 2004 20 Apr 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush -- 12 Apr 2004 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush 17 Apr 2004 17 Apr 2004 Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
Ports tree tagged 27 Apr 2004 28 Apr 2004 RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen 27 Apr 2004 28 Apr 2004 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts -- -- The ports cluster and bento build final packages.
doc/ tree tagged. 24 Apr 2004 24 Apr 2004 Version number bumps for doc/ subtree. RELEASE_&local.rel.tag;_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped. 4 May 2004
22 May 2004		 24 May 2004 The files listed here are updated to reflect the fact that this is FreeBSD &local.rel;.
Update man.cgi on the website. 4 May 2004
22 May 2004		 25 May 2004 Make sure the &local.rel; manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
src tree tagged. 4 May 2004
22 May 2004		 25 May 2004 RELENG_&local.rel.tag;_0_RELEASE tag for src/.
Final builds. 4 May 2004
22 May 2004		 26 May 2004 Final builds for x86 and Alpha in a pristine environment.
Warn mirror-announce@FreeBSD.org 4 May 2004
23 May 2004		 25 May 2004 Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master. 4 May 2004
23 May 2004		 26 May 2004 Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long)
Announcement 5 May 2004
24 May 2004		 27 May 2004 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam -- 3 June 2004 RELENG_&local.rel.tag; branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information

&footer; diff --git a/en/releases/4.10R/todo.sgml b/en/releases/4.10R/todo.sgml index ae9e1e728d..0a342b0b94 100644 --- a/en/releases/4.10R/todo.sgml +++ b/en/releases/4.10R/todo.sgml @@ -1,105 +1,106 @@ - + + %navincludes; %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD &local.rel;. If you have any updates for this list, please e-mail re@FreeBSD.org.

As many of these open issues involve merging bus_dma driver changes from -CURRENT, the busdma project page is also useful.

Must Resolve Issues for &local.rel;-RC3

- +
IssueStatusResponsibleDescription

Must Resolve Issues for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription

Desired Features for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription

Documentation items that must be resolved for &local.rel;

- +
IssueStatusResponsibleDescription

Testing focuses for &local.rel;

- +
IssueStatusResponsibleDescription
twe(4) stability problem &status.untested; -- The twe(4) driver has a stability problem when a lot of rapid sequential small file inserts into a new directory tree. A set of patches for the problem has been committed just before 4.10-RC3.
vmspace leak &status.untested; -- Copying vm_exitingcnt to the new vmspace in vmspace_exec() can make it very high values and never drop to 0 and be freed. This can cause a system crash. A patch for the problem has been committed just before 4.10-RC3.
twa(4) fails in sysinstall &status.untested; -- When a twa(4) device in a system with no SCSI controller is detected, sysinstall in 4.10-RC2 does not recognize the disks attached. It seems that this problem may involve inconsistency between the CAM device rescanning and the kernel module loading. A patch for the problem has been committed just before 4.10-RC3.
&footer; diff --git a/en/releases/4.11R/announce.sgml b/en/releases/4.11R/announce.sgml index c6b360a375..c13a9bb7b2 100644 --- a/en/releases/4.11R/announce.sgml +++ b/en/releases/4.11R/announce.sgml @@ -1,243 +1,247 @@ - + + %navincludes; %includes; ]> &header;

Date: Tue, 25 Jan 2005 12:02:10 -0500
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD &local.rel;-RELEASE is now available

The Release Engineering Team is happy to announce the availability of FreeBSD 4.11-RELEASE, the latest release of the FreeBSD Legacy development branch. Since FreeBSD 4.10-RELEASE in May 2004 we have made conservative updates to a number of software programs in the base system, dealt with known security issues, and made many bugfixes.

For a complete list of new features, known problems, and late-breaking news, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/&local.rel;R/relnotes.html

http://www.FreeBSD.org/releases/&local.rel;R/errata.html

FreeBSD &local.rel; will become an "Errata Branch". In addition to Security fixes other well-tested fixes to basic functionality will be committed to the RELENG_4_11 branch after the release. Both Security Advisories and Errata Notices are announced on the freebsd-announce@freebsd.org mailing list.

This is expected to be the last release from the RELENG_4 branch. Most of the Developers are now focused on the RELENG_5 branch, or on the cutting edge development in HEAD.

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Availability

FreeBSD &local.rel;-RELEASE supports the i386 and alpha architectures and can be installed directly over the net, using bootable media, or copied to a local NFS/FTP server. Distributions for both architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD &local.rel; based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemon News http://www.bsdmall.com/freebsd1.html

If you can not afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can not promise that all the mirror sites will carry the larger ISO images. At the time of this announcement they are available from the following sites. MD5 checksums for the release images are included at the bottom of this message.

Bittorrent

As with the 5.3 release we are experimenting with Bittorrent. A collection of trackers for the release ISO images is available at

http://people.freebsd.org/~kensmith/4.11-torrent/

FTP

FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Austria, Brazil, Canada, China, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland, Indonesia, Ireland, Italy, Japan, Korea, Lithuania, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russia, Saudi Arabia, Singapore, Slovak Republic, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Turkey, Ukraine, United Kingdom, and the United States.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites and the current list of all active mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for &local.rel; including The FreeBSD Mall, Hewlett Packard, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for &local.rel;-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Release Engineering, I386 Release Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Wilko Bulte <wilko@FreeBSD.org> Alpha Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer
Paul Saab <ps@FreeBSD.org> Bittorrent Coordination

A few people put in more than their fair share of last-minute work. This includes Alexander Leidinger <netchild@FreeBSD.org> who did a lot of work on the linux_base-8 package integration, and Kris Kennaway <kris@FreeBSD.org> who did a lot of package rebuilding thanks to a few recent security issues in some key packages.

CD Image Checksums

For Alpha:

MD5 (4.11-RELEASE-alpha-disc1-gnome.iso) = 3f0f49a9c7067f398ca0b47fd21234eb
MD5 (4.11-RELEASE-alpha-disc1-kde.iso) = b4c83df8e979741c7972f379154360aa
MD5 (4.11-RELEASE-alpha-disc2.iso) = 8fd241bab99fed226ef71184ed0b0b38
MD5 (4.11-RELEASE-alpha-miniinst.iso) = 3280b9e34fd26db7ce0dd24f1a05e7b4

For i386:

MD5 (4.11-RELEASE-i386-disc1-gnome.iso) = 80c6b06b83432efc6cbe1cff3ebd893f
MD5 (4.11-RELEASE-i386-disc1-kde.iso) = 84921fe6b6b4bfd3f7011788985d34e2
MD5 (4.11-RELEASE-i386-disc2.iso) = 73553999f9f8e2e49222ba14e8ecbde5
MD5 (4.11-RELEASE-i386-miniinst.iso) = 28b006bcdf5df8b8b7e8f1831085cdae

-ken

+ + &footer; + diff --git a/en/releases/4.11R/errata_policy.sgml b/en/releases/4.11R/errata_policy.sgml index 3cf92588de..a00968bfba 100644 --- a/en/releases/4.11R/errata_policy.sgml +++ b/en/releases/4.11R/errata_policy.sgml @@ -1,57 +1,58 @@ - + + %navincludes; %includes; ]> &header;

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD &local.rel;.

Procedures

The Errata fixes will be applied by a member of the Release Engineering Team, coordinating the fix with the Security Officer who owns the branch. An Errata Notice will also be issued. The Release Engineering Team may choose to handle several Errata with one Errata Notice if several are being processed at roughly the same time.

Policy

Errata Candidates

The classification of things that are Errata candidates are things that are severe service-disrupting bugs for which there is no known work-around. Things like bugs in device drivers that impair their expected functionality, things that can cause kernel panics, etc.

Initial Patch

During the initial phases the fix for Errata should be handled exactly like any other fix. It should initially be committed to HEAD if possible and go through the normal testing period there. The fix should then be MFCed as usual. Since HEAD and RELENG_5 have become dramatically different from RELENG_4 in many areas this may not be possible, and the initial commit may need to be applied straight to RELENG_4. At this point if you feel a fix is an Errata Notice candidate please contact the Release Engineering Team to make them aware of it.

The fix should then sit in RELENG_4 for one to two weeks. During this period please try to have the fix reviewed by another senior Developer familiar with the section of the code you are working with. You should also get confirmation that the fix solves the problem from someone who had reported the problem. Assuming no problems come up during this testing period then send in the formal request to re@FreeBSD.org. Please include the patch that will need to be applied to &local.rel; and who has reviewed the fix.

&footer; diff --git a/en/releases/4.11R/hardware.sgml b/en/releases/4.11R/hardware.sgml index 8509f0280c..81a8696ffa 100644 --- a/en/releases/4.11R/hardware.sgml +++ b/en/releases/4.11R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.11-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.11R/installation.sgml b/en/releases/4.11R/installation.sgml index 7ca9340e18..2b010723bd 100644 --- a/en/releases/4.11R/installation.sgml +++ b/en/releases/4.11R/installation.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 4.11-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.11R/relnotes.sgml b/en/releases/4.11R/relnotes.sgml index 4511d2cc34..b83f84ea21 100644 --- a/en/releases/4.11R/relnotes.sgml +++ b/en/releases/4.11R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.11-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.11R/schedule.sgml b/en/releases/4.11R/schedule.sgml index 1f07dd58cf..bd783e37e6 100644 --- a/en/releases/4.11R/schedule.sgml +++ b/en/releases/4.11R/schedule.sgml @@ -1,304 +1,305 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
ActionExpectedActualDescription
Reminder announcement 30 Nov 2004 30 Nov 2004 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD &local.rel; release.
&local.rel;-BETA Testing Guide published -- -- A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period.
Announce the Ports Freeze -- 18 Dec 2004 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
&local.rel;-PRERELEASE 6 Dec 2004 6 Dec 2004 newvers.sh updated.
Code freeze begins 13 Dec 2004 13 Dec 2004 After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers, as well as stable@ and qa@ lists.
RELENG_&local.rel.tag; branch 17 Dec 2004 17 Dec 2004 The release branch is created. Update newvers.sh and release.ent on various branches involved.
Unfreeze the tree 17 Dec 2004 17 Dec 2004 Announcement to developers explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_&local.rel.tag; branch.
&local.rel;-RC 17 Dec 2004 17 Dec 2004 newvers.sh and release.ent updated.
First release candidate 20 Dec 2004 18 Dec 2004 The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks.
Heads up to -stable 20 Dec 2004 18 Dec 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate 3 Jan 2005 3 Jan 2005 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable 3 Jan 2005 3 Jan 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded.
Third release candidate 17 Jan 2005 17 Jan 2005 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable 17 Jan 2005 17 Jan 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Ports tree frozen 30 Dec 2004 31 Dec 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush 27 Dec 2004 29 Dec 2004 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush 14 Jan 2005 15 Jan 2005 Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
Ports tree tagged 6 Jan 2005 8 Jan 2005 RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen 7 Jan 2005 8 Jan 2005 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts 6 Jan 2005 -- The ports cluster and pointyhat build final packages.
doc/ tree tagged. 18 Jan 2005 -- Version number bumps for doc/ subtree. RELEASE_&local.rel.tag;_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped. 20 Jan 2005 21 Jan 2005 The files listed here are updated to reflect the fact that this is FreeBSD &local.rel;.
src tree tagged. 20 Jan 2005 21 Jan 2005 RELENG_&local.rel.tag;_0_RELEASE tag for src/.
Final builds. 20 Jan 2005 21 Jan 2005 Final builds for x86 and Alpha in a pristine environment.
Warn mirror-announce@FreeBSD.org 21 Jan 2005 24 Jan 2005 Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master. 22 Jan 2005 24 Jan 2005 Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long)
Update man.cgi on the website. 24 Jan 2005 25 Jan 2005 Make sure the &local.rel; manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
Announcement 24 Jan 2005 25 Jan 2005 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam 2 Feb 2005 1 Feb 2005 RELENG_&local.rel.tag; branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information

&footer; diff --git a/en/releases/4.11R/todo.sgml b/en/releases/4.11R/todo.sgml index 0fb5cb1f6e..5ec01f7311 100644 --- a/en/releases/4.11R/todo.sgml +++ b/en/releases/4.11R/todo.sgml @@ -1,63 +1,64 @@ - + + %navincludes; %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD &local.rel;. If you have any updates for this list, please e-mail re@FreeBSD.org.

Must Resolve Issues for &local.rel;-RC3

- +
IssueStatusResponsibleDescription

Must Resolve Issues for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription

Desired Features for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription

Documentation items that must be resolved for &local.rel;

- +
IssueStatusResponsibleDescription

Testing focuses for &local.rel;

- +
IssueStatusResponsibleDescription
&footer; diff --git a/en/releases/4.3R/announce.sgml b/en/releases/4.3R/announce.sgml index c73d4aa894..5a43694e5d 100644 --- a/en/releases/4.3R/announce.sgml +++ b/en/releases/4.3R/announce.sgml @@ -1,89 +1,93 @@ - + + %navincludes; %includes; ]> &header;

Date: Friday, 20 Apr 2001 21:00:00 -0800
From: "Jordan K. Hubbard" <jkh@freebsd.org>
To: announce@FreeBSD.org
Subject: 4.3-RELEASE is now available

It gives me great pleasure to announce what is probably the finest release produced from the 4.x-STABLE branch to date, FreeBSD 4.3-RELEASE. Following the release of FreeBSD 4.2 in November, 2000, many bugs were fixed, important security issues dealt with, and a reasonable number of new features added. Please see the release notes for more information.

4.3-RELEASE is available for the i386 and alpha architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/ftp server.

ISO (CD) Images
---------------

We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.3-install.iso
and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3-install.iso

If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.3-RELEASE can be ordered as a 4 CD set from The FreeBSD Mall from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at:

   BSDi
   4041 Pike Lane, #F
   Concord CA, 94520 USA
   Phone: +1 925 674-0783
   Fax: +1 925 674-0821
   Tech Support: +1 925 603-1234
   Email: orders@wccdrom.com
   WWW: http://www.freebsdmall.com/

Note: Despite the recent acquisition of BSDi's software assets by Wind River, the above information still holds true for the forseeable future and will not change for at least the life-cycle of the FreeBSD 4.3 product. Any changes in the FreeBSD product sales infrastructure will be announced if and as they occur.

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom, among others.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

- +

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Thanks! - Jordan + +&footer; + diff --git a/en/releases/4.4R/hardware.sgml b/en/releases/4.4R/hardware.sgml index 45b0e64b5c..7152ef1f3b 100644 --- a/en/releases/4.4R/hardware.sgml +++ b/en/releases/4.4R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.4 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+&footer; + + diff --git a/en/releases/4.4R/notes.sgml b/en/releases/4.4R/notes.sgml index 8dc859da33..e868772cae 100644 --- a/en/releases/4.4R/notes.sgml +++ b/en/releases/4.4R/notes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.4 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.5R/hardware.sgml b/en/releases/4.5R/hardware.sgml index 34f9959ce5..9d9e59a35c 100644 --- a/en/releases/4.5R/hardware.sgml +++ b/en/releases/4.5R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.5 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.5R/notes.sgml b/en/releases/4.5R/notes.sgml index c07ee637b7..067c3a82cf 100644 --- a/en/releases/4.5R/notes.sgml +++ b/en/releases/4.5R/notes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.5 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6.2R/announce.sgml b/en/releases/4.6.2R/announce.sgml index 5c45ff2205..3cd8dd543d 100644 --- a/en/releases/4.6.2R/announce.sgml +++ b/en/releases/4.6.2R/announce.sgml @@ -1,174 +1,177 @@ - + + %navincludes; %includes; ]> &header;

Date: Thu, 15 Aug 2002 14:08:02 -0700
From: "Murray Stokely" <murray@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 4.6.2-RELEASE is now available

I am happy to announce the availability of FreeBSD 4.6.2-RELEASE, a maintenance release of the FreeBSD 4.6-STABLE branch. Since FreeBSD 4.6-RELEASE in June 2002, we have resolved several ATA-related problems, updated the system OpenSSL and OpenSSH components, and addressed several security issues.

For a list of new features and known problems, please see the release notes and errata list, available here:

For more information about FreeBSD release engineering activities (including information about the upcoming FreeBSD 4.7), please see:

Availability

FreeBSD 4.6.2-RELEASE supports the i386 and alpha architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for the i386 are available now. As of this writing, the final builds for the alpha architecture are in progress and will be made available shortly.

We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images, otherwise please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 4.6.2 based products:

Daemon News http://www.bsdmall.com/freebsd1.html
FreeBSD Mall, Inc. http://www.freebsdmall.com/
FreeBSD Services Ltd. http://www.freebsd-services.com/

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 4.6.2, including Compaq, Yahoo!, Sentex Communications, NTT/Verio, and The FreeBSD Mall.

In addition to myself, the release engineering team for 4.6.2-RELEASE includes:

Bruce A. Mah<bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Brian Somers <brian@FreeBSD.org> Release Engineering
Steve Price <steve@FreeBSD.org> Package Splits
Will Andrews <will@FreeBSD.org> Package Splits
Kris Kennaway <kris@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer

Please join me in thanking them for all the hard work which went into making this release. Many thanks are also due to the FreeBSD committers (committers@FreeBSD.org), without whom there would be nothing to release, and thousands of FreeBSD users world-wide who have contributed bug fixes, features, and suggestions.

Enjoy!

Murray Stokely
(For the FreeBSD Release Engineering Team)

+&footer; + diff --git a/en/releases/4.6.2R/hardware.sgml b/en/releases/4.6.2R/hardware.sgml index 9d26896aa2..d22265a34a 100644 --- a/en/releases/4.6.2R/hardware.sgml +++ b/en/releases/4.6.2R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.6.2-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6.2R/relnotes.sgml b/en/releases/4.6.2R/relnotes.sgml index 8567627d62..1e0650a901 100644 --- a/en/releases/4.6.2R/relnotes.sgml +++ b/en/releases/4.6.2R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.6.2-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6R/contents.sgml b/en/releases/4.6R/contents.sgml index 62675e37f5..379fa7355e 100644 --- a/en/releases/4.6R/contents.sgml +++ b/en/releases/4.6R/contents.sgml @@ -1,48 +1,49 @@ - + + %navincludes; %includes; ]> &header;

Contents of the FreeBSD Official 4-CDROM set.

The FreeBSD Project now releases the full 4-CDROM set formerly produced by Walnut Creek CDROM / BSDi. This CDROM set may be replicated by vendors wishing to sell "Official" copies of FreeBSD.

Contents of Disc 1

4.6-disc1.iso - This is a bootable CDROM image that contains the base system, XFree86 4.2.0, a 'tools' directory of software for users performing an installation from other operating systems, and 2,131 third-party software packages. [ file listing ]

Contents of Disc 2

4.6-disc2.iso - This is a bootable CDROM that may be used as a live filesystem disc. This disc also contains a compressed copy of the CVS repository in the CVS-REPO directory, and some commercial software demos for FreeBSD in the commerce directory. [ file listing ]

Contents of Discs #3 and #4

4.6-disc3.iso, 4.6-disc4.iso - The remaining two discs contain the most popular third-party software package that users have requested. They contain 2,399 and 550 packages, respectively.[ Disc 3 listing ] [ Disc 4 listing ]

&footer; diff --git a/en/releases/4.6R/hardware.sgml b/en/releases/4.6R/hardware.sgml index 025c3424e2..3e69371236 100644 --- a/en/releases/4.6R/hardware.sgml +++ b/en/releases/4.6R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.6-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6R/installation.sgml b/en/releases/4.6R/installation.sgml index 5562c55e4f..969a7d8e81 100644 --- a/en/releases/4.6R/installation.sgml +++ b/en/releases/4.6R/installation.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 4.6-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6R/qa.sgml b/en/releases/4.6R/qa.sgml index bc3463aba9..25f398be90 100644 --- a/en/releases/4.6R/qa.sgml +++ b/en/releases/4.6R/qa.sgml @@ -1,112 +1,113 @@ - + + %navincludes; %includes; ]> &header;

Goals

As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.6-PRERELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:

To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.

Features to explore carefully:

The release notes will always be a good place to look for things to test.

Known Issues

&footer; diff --git a/en/releases/4.6R/relnotes.sgml b/en/releases/4.6R/relnotes.sgml index c52b304d47..9ad64d8cf6 100644 --- a/en/releases/4.6R/relnotes.sgml +++ b/en/releases/4.6R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.6-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.6R/schedule.sgml b/en/releases/4.6R/schedule.sgml index cfc99d425c..ae27fffa3d 100644 --- a/en/releases/4.6R/schedule.sgml +++ b/en/releases/4.6R/schedule.sgml @@ -1,290 +1,291 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD 4.6. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public FreeBSD-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
- +
Action Expected Actual Description
Reminder announcement 01 Apr 2002 09 Apr 2002 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.6 release.
4.6-PRERELEASE Testing Guide published Ongoing -- A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period.
4.6-PRERELEASE 01 May 2002 01 May 2002 newvers.sh, and release.ent updated.
FTP site updated 01 May 2002 18 May 2002 pkg_add -r works for 4.6-PRERELEASE machines.
Code freeze begins 01 May 2002 01 May 2002 After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers@, stable@ and qa@ lists.
Commercial software demos updated. 15 May 2002 -- The second disc contains commercial software demos, these demos should be updated to contain the latest versions.
4.6-RC 15 May 2002 15 May 2002 newvers.sh and release.ent updated.
Announce the Ports Freeze 15 May 2002 19 May 2002 Someone from portmgr should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree.
Heads up to hubs 28 May 2002 -- A message should be sent to freebsd-hubs@FreeBSD.org before the release is uploaded. The site administrators have frequently requested advance notice for new ISOs.
First release candidate 16 May 2002 17 May 2002 The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ and XF86336/ directories may be symlinked to save space, as long as you're sure to use relative symlinks.
Heads up to -stable 17 May 2002 17 May 2002 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded.
Package split posted 17 May 2002 -- The proposed package split (which packages go on which disc of the 4 CD set) should be posted to qa@FreeBSD.org, ports@FreeBSD.org, and stable@FreeBSD.org.
Second release candidate ?? May 2002 18 May 2002 Note: the release date of this candidate depends on the user experience with RC1.
Third release candidate -- -- There will be no 4.6 RC3 snapshot.
Ports tree frozen. 24 May 2002 25 May 2002 CVSROOT/avail locks out everyone but the person who does the tagging. It will take approximately 2 hours to tag the entire ports tree with the RELEASE_4_6_0 tag. After this time, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.6-RELEASE.
Final package build starts 25 May 2002 -- The ports cluster and bento build final packages.
Package split 26 May 2002 -- The packages must be split so that packages with similar dependencies appear on each of the four discs, with the most popular packages appearing on the first disc.
doc/ tree tagged. 27 May 2002 27 May 2002 RELEASE_4_6_0 tag for docs.
Fourth release candidate 3 June 2002 6 June 2002 4.6 RC4 for the x86 and Alpha architectures will be made available from ftp.FreeBSD.org and the mirrors.
RELENG_4_6 branch 5 June 2002 6 June 2002 The release branch is created.
Note to freebsd-stable@ 5 June 2002 6 June 2002 A note should be sent to the freebsd-stable@ to let over-anxious users know that the tags have been created but the release still isn't ready. Tags may be slid before the announcement goes out. Point users to freebsd-qa@ for details.
Version numbers bumped. 5 June 2002 8 June 2002 The files listed here are updated to reflect the fact that this is FreeBSD 4.6.
Update man.cgi on the website. 6 June 2002 3 June 2002 Make sure the 4.6 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
src tree tagged. 10 June 2002 10 June 2002 RELENG_4_6_0_RELEASE tag for src.
Final builds. 10 June 2002 -- Final builds for x86 and Alpha in a pristine environment.
Warn hubs@FreeBSD.org 10 June 2002 11 June 2002 Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come.
Upload to ftp-master. 10 June 2002 14 June 2002 release and packages uploaded to ftp-master.FreeBSD.org
Announcement 10 Jun 2002 15 June 2002 Announcement sent out after a majority of the mirrors have received the bits.
Unfreeze the tree 10 June 2002 16 June Announcement to developers@ explaining that the release is out, and commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_6 branch.
&footer; diff --git a/en/releases/4.8R/announce.sgml b/en/releases/4.8R/announce.sgml index 2adc401ff3..08c7b3d8a7 100644 --- a/en/releases/4.8R/announce.sgml +++ b/en/releases/4.8R/announce.sgml @@ -1,194 +1,197 @@ - + + %navincludes; %includes; ]> &header;

Date: Thu, 3 Apr 2003 21:43:09 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD &local.rel;-RELEASE is now available

I am happy to announce the availability of FreeBSD &local.rel;-RELEASE, the latest release of the FreeBSD -STABLE development branch. Since FreeBSD 4.7-RELEASE in October 2002, we have made conservative updates to a number of software programs in the base system, added initial support for Firewire and other new hardware technologies, and dealt with known security issues.

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/&local.rel;R/relnotes.html

http://www.FreeBSD.org/releases/&local.rel;R/errata.html

This release does not include all of the new technologies that were introduced with FreeBSD 5.0 in January. FreeBSD 4.X releases offer a more conservative platform than FreeBSD 5.0 at this time. For more information about the distinctions between FreeBSD 4.X and 5.0, or for general information about the FreeBSD release engineering activities, please see :

http://www.FreeBSD.org/releng/

Availability

FreeBSD &local.rel;-RELEASE supports the i386 and alpha architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for the i386 are available now. As of this writing, the final builds for the alpha architecture are in progress and will be made available shortly.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies have contributed substantially to the development of FreeBSD:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemon News http://www.bsdmall.com/freebsd1.html

Each CD or DVD set contains the FreeBSD installation and application package bits for the i386 ("PC") architecture. For a set of distfiles used to build ports in the ports collection, please see the FreeBSD Toolkit, a 6 CD set containing extra bits which no longer fit on the 4 CD set, or the DVD distribution.

If you can't afford FreeBSD on media, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD &local.rel; including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

In addition to myself, the release engineering team for &local.rel;-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Bruce Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Wilko Bulte <wilko@FreeBSD.org> Release Engineering, alpha builds
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Ruslan Ermilov <ru@FreeBSD.org> Release Engineering
Kris Kennaway <kris@FreeBSD.org> Package Building
Will Andrews <will@FreeBSD.org> Package Building, KDE
Joe Marcus Clarke <marcus@FreeBSD.org> GNOME Integration
Julian Elischer <julian@FreeBSD.org> Release Testing

Please join me in thanking them for all the hard work which went into making this release. Many thanks are also due to the FreeBSD committers (committers@FreeBSD.org), without whom there would be nothing to release, and thousands of FreeBSD users world-wide who have contributed bug fixes, features, and suggestions.

Enjoy!

Murray Stokely
(For the FreeBSD Release Engineering Team)

+&footer; + diff --git a/en/releases/4.8R/hardware.sgml b/en/releases/4.8R/hardware.sgml index 5a8536172f..bc6426328f 100644 --- a/en/releases/4.8R/hardware.sgml +++ b/en/releases/4.8R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.8-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.8R/installation.sgml b/en/releases/4.8R/installation.sgml index 53842e0e72..cd85bdf11c 100644 --- a/en/releases/4.8R/installation.sgml +++ b/en/releases/4.8R/installation.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 4.8-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.8R/qa.sgml b/en/releases/4.8R/qa.sgml index 5a26eebd68..52a0c79227 100644 --- a/en/releases/4.8R/qa.sgml +++ b/en/releases/4.8R/qa.sgml @@ -1,91 +1,92 @@ - + + %navincludes; %includes; ]> &header;

Goals

As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in &rel; that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:

To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.

Features to explore carefully:

The release notes will always be a good place to look for things to test.

Known Issues

&footer; diff --git a/en/releases/4.8R/relnotes.sgml b/en/releases/4.8R/relnotes.sgml index 5c401d16ec..5bc6fe6dc6 100644 --- a/en/releases/4.8R/relnotes.sgml +++ b/en/releases/4.8R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.8-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.8R/schedule.sgml b/en/releases/4.8R/schedule.sgml index 830abbf09d..ad7145cc0c 100644 --- a/en/releases/4.8R/schedule.sgml +++ b/en/releases/4.8R/schedule.sgml @@ -1,292 +1,293 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
ActionExpectedActualDescription
Reminder announcement 16 Jan 2003 16 Jan 2003 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD &local.rel; release.
Another Reminder announcement 7 Feb 2003 10 Feb 2003 1 week reminder.
Another Reminder announcement 14 Feb 2003 14 Feb 2003 Final reminder, with exact time that freeze begins.
&local.rel;-PRERELEASE Testing Guide published15 Feb 20032 Mar 2003 A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period.
&local.rel;-PRERELEASE 15 Feb 2003 15 Feb 2003 newvers.sh, and release.ent updated.
FTP site updated 15 Feb 2003 unnecessary pkg_add -r works for &local.rel;-PRERELEASE machines.
Code freeze begins 15 Feb 2003 15 Feb 2003 After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers@, stable@ and qa@ lists.
&local.rel;-RC 1 Mar 2003 2 Mar 2003 newvers.sh and release.ent updated.
Announce the Ports Freeze 1 Mar 2003 1 Mar 2003 Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree.
First release candidate 1 Mar 2003 3 Mar 2003 The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article.
Heads up to -stable 2 Mar 2003 3 Mar 2003 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded.
Second release candidate 16 Mar 2003 17 Mar 2003 Note: the release date of this candidate depends on the user experience with RC1.
Third release candidate -- --
Ports tree frozen 5 Mar 2003 6 Mar 2003 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush 6 Mar 2003 7 Mar 2003 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush 10 Mar 2003 10 Mar 2003 Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
Ports tree tagged 13 Mar 2003 -- RELEASE_4_8_0 tag for ports/.
Ports tree unfrozen 22 Mar 2003 22 Mar 2003 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts 20 Mar 2003 -- The ports cluster and bento build final packages.
doc/ tree tagged. 19 Mar 2003 22 Mar 2003 Version number bumps for doc/ subtree. RELEASE_4_8_0 tag for doc/. doc/ slush ends at this time.
RELENG_4_8 branch 22 Mar 2003 23 Mar 2003 The release branch is created.
Note to freebsd-stable@ 22 Mar 2003 -- A note should be sent to the freebsd-stable@ list to let over-anxious users know that the tags have been created but the release still isn't ready. Tags may be slid before the announcement goes out. Point users to freebsd-qa@ for details.
Version numbers bumped. 23 Mar 2003 -- The files listed here are updated to reflect the fact that this is FreeBSD &local.rel;.
Update man.cgi on the website. 23 Mar 2003 28 Mar 2003 Make sure the &local.rel; manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
src tree tagged. 29 Mar 2003 -- RELENG_4_8_0_RELEASE tag for src/.
Final builds. 29 Mar 2003 -- Final builds for x86 and Alpha in a pristine environment.
Warn hubs@FreeBSD.org 29 Mar 2003 -- Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master. 29 Mar 2003 -- Release and packages uploaded to ftp-master.FreeBSD.org
Announcement 30 Mar 2003 -- Announcement sent out after a majority of the mirrors have received the bits.
Unfreeze the tree 30 Mar 2003 -- Announcement to developers@ explaining that the release is out, and commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_8 branch.
&footer; diff --git a/en/releases/4.9R/announce.sgml b/en/releases/4.9R/announce.sgml index 226750c621..4b960698c8 100644 --- a/en/releases/4.9R/announce.sgml +++ b/en/releases/4.9R/announce.sgml @@ -1,210 +1,213 @@ - + + %navincludes; %includes; ]> &header;

Date: Tue, 28 Oct 2003 23:19:08 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD &local.rel;-RELEASE is now available

I am happy to announce the availability of FreeBSD 4.9-RELEASE, the latest release of the FreeBSD -STABLE development branch. Since FreeBSD 4.8-RELEASE in April 2003, we have made conservative updates to a number of software programs in the base system, dealt with known security issues, and merged support for large memory i386 machines with Page Address Extensions (PAE) from 5.1.

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/&local.rel;R/relnotes.html

http://www.FreeBSD.org/releases/&local.rel;R/errata.html

This release does not include all of the new technologies that were introduced with FreeBSD 5.1 in June. Most developer resources are focused on improving the FreeBSD 5.X branch, and this may very well be the last major release of FreeBSD 4.X. The security officer team will continue to actively support the 4.X branch according to the normal policy. Additional 4.9.X releases may be made available when necessitated by security vulnerabilities or high-impact bugfixes.

We encourage all our users to evaluate FreeBSD 5.1 and the upcoming 5.2. Because PAE support has only been a feature in 4.X for a few months, it has not received wide-spread testing, and our most conservative users may wish to stay with FreeBSD 4.8 until they choose to migrate to 5.X.

For more information about the distinctions between FreeBSD 4.X and 5.X, or for general information about the FreeBSD release engineering activities, please see :

http://www.FreeBSD.org/releng/

Availability

FreeBSD &local.rel;-RELEASE supports the i386 and alpha architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies have contributed substantially to the development of FreeBSD:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemon News http://www.bsdmall.com/freebsd1.html

Each CD or DVD set contains the FreeBSD installation and application package bits for the i386 ("PC") architecture. For a set of distfiles used to build ports in the ports collection, please see the FreeBSD Toolkit, a 6 CD set containing extra bits which no longer fit on the 4 CD set, or the DVD distribution.

If you can't afford FreeBSD on media, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD &local.rel; including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

In addition to myself, the release engineering team for &local.rel;-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Bruce Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Wilko Bulte <wilko@FreeBSD.org> Release Engineering, alpha builds
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Mike Silbersack <silby@silby.com> PAE Testing
Luoqi Chen <luoqi@freebsd.org> PAE Merge
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building, GNOME
Kris Kennaway <kris@FreeBSD.org> Package Building
Will Andrews <will@FreeBSD.org> Package Building, KDE

Please join me in thanking them for all the hard work which went into making this release. Many thanks are also due to the FreeBSD committers (committers@FreeBSD.org), without whom there would be nothing to release, and thousands of FreeBSD users world-wide who have contributed bug fixes, features, and suggestions.

Enjoy!

Murray Stokely
(For the FreeBSD Release Engineering Team)

MD5 (4.9-i386-disc1.iso) = 9195be15a4c8c54a6a6a23272ddacaae
MD5 (4.9-i386-disc2.iso) = 51d28c35308cc916b9a9bfcacb3146b8
MD5 (4.9-RELEASE-alpha-miniinst.iso) = 51e189a32a5f1bb058adc7627b673ae6
MD5 (4.9-RELEASE-alpha-disc2.iso) = ec316dcfb33ca76ba2a240e50d7c9fce
 +&footer; + diff --git a/en/releases/4.9R/hardware.sgml b/en/releases/4.9R/hardware.sgml index 5e5e08ffea..c23d5227d6 100644 --- a/en/releases/4.9R/hardware.sgml +++ b/en/releases/4.9R/hardware.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.9-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.9R/installation.sgml b/en/releases/4.9R/installation.sgml index 5643c64190..c9c78ebd72 100644 --- a/en/releases/4.9R/installation.sgml +++ b/en/releases/4.9R/installation.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 4.9-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.9R/qa.sgml b/en/releases/4.9R/qa.sgml index a129cf874d..49f3446945 100644 --- a/en/releases/4.9R/qa.sgml +++ b/en/releases/4.9R/qa.sgml @@ -1,75 +1,76 @@ - + + %navincludes; %includes; ]> &header;

Goals

As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in &rel; that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:

To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.

Features to explore carefully:

The release notes will always be a good place to look for things to test.

Known Issues

&footer; diff --git a/en/releases/4.9R/relnotes.sgml b/en/releases/4.9R/relnotes.sgml index 32a7de363f..804a6fcf7c 100644 --- a/en/releases/4.9R/relnotes.sgml +++ b/en/releases/4.9R/relnotes.sgml @@ -1,26 +1,30 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.9-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/4.9R/schedule.sgml b/en/releases/4.9R/schedule.sgml index 88a840be1a..2088174116 100644 --- a/en/releases/4.9R/schedule.sgml +++ b/en/releases/4.9R/schedule.sgml @@ -1,305 +1,306 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
ActionExpectedActualDescription
Reminder announcement 28 Jul 2003 28 Jul 2003 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD &local.rel; release.
Another Reminder announcement 18 Aug 2003 18 Aug 2003 1 week reminder.
Another Reminder announcement 24 Aug 2003 24 Aug 2003 Final reminder, with exact time (GMT) that freeze begins.
&local.rel;-PRERELEASE Testing Guide published25 Aug 2003-- A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period.
&local.rel;-PRERELEASE 25 Aug 2003 25 Aug 2003 newvers.sh, and release.ent updated.
FTP site updated 25 Aug 2003 25 Aug 2003 pkg_add -r works for &local.rel;-PRERELEASE machines.
Code freeze begins 25 Aug 2003 25 Aug 2003 After this date, all commits to the RELENG_4 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers@, stable@ and qa@ lists.
&local.rel;-RC 12 Sep 2003 28 Sep 2003 newvers.sh and release.ent updated.
Announce the Ports Freeze 19 Aug 2003 19 Aug 2003 Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree.
First release candidate 12 Sep 2003 28 Sep 2003 The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. Send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks.
Heads up to -stable 12 Sep 2003 28 Sep 2003 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded.
Second release candidate 17 Sep 2003 8 Oct 2003 Note: the release date of this candidate depends on the user experience with RC1.
Third release candidate 17 Oct 2003 18 Oct 2003
Ports tree frozen 10 Sep 2003 10 Sep 2003 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush 17 Oct 2003 18 Oct 2003 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush 18 Oct 2003 18 Oct 2003 Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
Ports tree tagged 23 Sep 2003 24 Sep 2003 RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen -- -- After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts 19 Sep 2003 10 Oct 2003 The ports cluster and bento build final packages.
doc/ tree tagged. 20 Oct 2003 21 Oct 2003 Version number bumps for doc/ subtree. RELEASE_&local.rel.tag;_0 tag for doc/. doc/ slush ends at this time.
RELENG_&local.rel.tag; branch 18 Oct 2003 22 Oct 2003 The release branch is created.
Note to freebsd-stable@ 18 Oct 2003 23 Oct 2003 A note should be sent to the freebsd-stable@ list to let over-anxious users know that the tags have been created but the release still isn't ready. Tags may be slid before the announcement goes out. Point users to freebsd-qa@ for details.
Version numbers bumped. 18 Oct 2003 -- The files listed here are updated to reflect the fact that this is FreeBSD &local.rel;.
Update man.cgi on the website. 18 Oct 2003 19 Oct 2003 Make sure the &local.rel; manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
src tree tagged. 21 Oct 2003 -- RELENG_&local.rel.tag;_0_RELEASE tag for src/.
Final builds. 21 Oct 2003 -- Final builds for x86 and Alpha in a pristine environment.
Warn mirror-announce@FreeBSD.org 21 Oct 2003 -- Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master. 21 Oct 2003 -- Release (and packages?) uploaded to ftp-master.FreeBSD.org
Announcement 23 Oct 2003 -- Announcement sent out after a majority of the mirrors have received the bits.
Unfreeze the tree 23 Oct 2003 -- Announcement to developers@ explaining that the release is out, and commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_&local.rel.tag; branch.

Additional Information

&footer; diff --git a/en/releases/4.9R/todo.sgml b/en/releases/4.9R/todo.sgml index bb8342d402..6af7a0ebbe 100644 --- a/en/releases/4.9R/todo.sgml +++ b/en/releases/4.9R/todo.sgml @@ -1,157 +1,158 @@ - + + %navincludes; %includes; %developers; ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD &local.rel;. If you have any updates for this list, please e-mail re@FreeBSD.org.

As many of these open issues involve merging bus_dma driver changes from -CURRENT, the busdma project page is also useful.

Must Resolve Issues for &local.rel;-RC3

- +
IssueStatusResponsibleDescription
FireWire load failure bug. Done matusita@ Reported on stable@. Did this ever work after the initial firewire commit to drivers.conf in April? If not, is there any reason to not just back out that commit and not have firewire supported during the install?

Must Resolve Issues for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription
if_dc tested/merged to work with PAE in 4.x -- luoqi
busdma infrastructure merges -- scottl It's unclear if further bus_dma infrastructure changes need to be merged?
if_xl Done silby
RAID drivers tested/merged to work with PAE in 4.x -- scottl
ACPI merged as optional component In progress &a.jhb; ACPI will be provided as an optional component, turned off by default.

Desired Features for &local.rel;-RELEASE

- +
IssueStatusResponsibleDescription
USB updated to work with PAE In progress jmg, joe, luoqi USB does not currently work with PAE enabled.
twe updated for bus_dma/PAE -- ps The 3ware twe driver needs to be updated for use with PAE in 4.X.
ciss updated for bus_dma/PAE -- ps The ciss driver needs to be updated for use with PAE in 4.X.

Documentation items that must be resolved for &local.rel;

- +
IssueStatusResponsibleDescription
ACPI Done Murray Handbook should be updated to note that ACPI can be enabled on 4.9 systems.
PAE Done Murray Handbook should be updated to explain the basic PAE functionality.

Testing focuses for &local.rel;

- +
IssueStatusResponsibleDescription
PAE testing -- More testing should be done with PAE systems to test device compatibility and performance. In particular, active systems with 12 gig of ram or more should be thoroughly tested to make sure the various memory allocation algorithms in the kernel still scale properly. There were reports of users running out of KVA space in -CURRENT with large memory machines.
&footer; diff --git a/en/releases/5.0R/DP1/announce.sgml b/en/releases/5.0R/DP1/announce.sgml index 647b14e18d..1c53ab58a6 100644 --- a/en/releases/5.0R/DP1/announce.sgml +++ b/en/releases/5.0R/DP1/announce.sgml @@ -1,165 +1,168 @@ - + + %navincludes; %includes; ]> &header;

Date: Monday, 8 Apr 2002 15:00:00 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: announce@FreeBSD.org
Subject: FreeBSD 5.0 Developer Preview #1 Now Available

A Developer Preview release of FreeBSD 5.0-CURRENT is now available for widespread testing. This preview is a significant milestone towards the eventual release of FreeBSD 5.0 in late 2002. Some of the many new features that are available in this snapshot are listed below:

WARNING

This is a development snapshot, and may include serious software bugs. Do not install this on a machine where important data may be put at risk. In addition, a number of debugging options are turned on by default, so the poor performance of this snapshot should not set expectations for the final release of 5.0.

That said, we have done our best to provide a stable system for developers and power-users to help test the new functionality in 5.0. For a complete list of new features and known problems, please see the release notes and errata list.

Availability

5.0-DP1 is available for the i386, alpha, and sparc64 architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server.

If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please continue to support the FreeBSD project by purchasing media from one of our supporting vendors. This Developer Preview release is available on CD-ROM from the FreeBSD Mall.

http://www.FreeBSDMall.com/

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Lithuania, Latvia, the Netherlands, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, the Ukraine, the United Kingdom, and the United States.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

See the FreeBSD Handbook for additional information about FreeBSD mirror sites.

Acknowledgments

Finally, we would like to thank the developers, users, and companies that continue to make FreeBSD releases possible.

Many companies donated equipment, network access, or man-hours to finance our ongoing release engineering activities, including Compaq, Yahoo!, and The FreeBSD Mall.

I couldn't possibly list all of the people that have helped make 5.0 DP1 a reality, but the following people deserve to be singled out. Will Andrews, Kris Kennaway, Steve Price, and the rest of the Ports team did an incredible job fixing hundreds of third-party packages. Robert Watson and Bruce A. Mah did an excellent job writing up the errata file, helping to decide what changes should be made specifically for this DP release, and much more. Jake Burkholder acted not only as lead developer for the sparc64 port, but also as package builder and release engineer! David O'Brien helped integrate XFree86 4.2 into this snapshot.

Please join me in thanking them for all the hard work that went into polishing the FreeBSD -CURRENT development branch over the past month. I would also like to thank the FreeBSD Committers (committers@FreeBSD.org), without whom there would be nothing to release, and the many thousands of FreeBSD users world-wide who contributed bug fixes, features and suggestions.

Above all else, remember that this is a work in progress. Please help us find bugs now, so that 5.0-RELEASE will be that much better.

Thanks!

- Murray

+&footer; + diff --git a/en/releases/5.0R/DP1/hardware.sgml b/en/releases/5.0R/DP1/hardware.sgml index acea1c2a2c..32942c759b 100644 --- a/en/releases/5.0R/DP1/hardware.sgml +++ b/en/releases/5.0R/DP1/hardware.sgml @@ -1,27 +1,31 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 5.0-DP1 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/DP1/installation.sgml b/en/releases/5.0R/DP1/installation.sgml index 93cc79ad07..3ce45e9e92 100644 --- a/en/releases/5.0R/DP1/installation.sgml +++ b/en/releases/5.0R/DP1/installation.sgml @@ -1,27 +1,31 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Installation notes for FreeBSD 5.0-DP1 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/DP1/relnotes.sgml b/en/releases/5.0R/DP1/relnotes.sgml index 49bd88eb58..c4efee2d68 100644 --- a/en/releases/5.0R/DP1/relnotes.sgml +++ b/en/releases/5.0R/DP1/relnotes.sgml @@ -1,27 +1,31 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.0-DP1 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/DP2/announce.sgml b/en/releases/5.0R/DP2/announce.sgml index 8fa9da18be..0d00166abd 100644 --- a/en/releases/5.0R/DP2/announce.sgml +++ b/en/releases/5.0R/DP2/announce.sgml @@ -1,184 +1,187 @@ - + + %navincludes; %includes; ]> &header;

Date: Monday, 18 Nov 2002 16:39:13 -0800
From: bmah@FreeBSD.org (Bruce A. Mah)
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 5.0 Developer Preview #2 Now Available

The FreeBSD Project is proud to announce the availability of the second Developer Preview snapshot of FreeBSD 5.0 (5.0-DP2). This snapshot, intended for widespread testing purposes, is the latest milestone towards the eventual release of FreeBSD 5.0-RELEASE, currently scheduled for mid-December 2002.

Since the release of 5.0-DP1, a number of new features have been added on the CURRENT development branch. A few of these include:

Much more information can be found in the release documentation, as described below.

WARNING

This snapshot is not a supported release, and has not undergone any of the usual quality assurance checking that is a part of normal FreeBSD releases. It may include serious software bugs. Do not install this software on a machine where important data may be put at risk.

The purpose of this snapshot is to get wider exposure to FreeBSD 5.0's new features, in advance of the release. As such, we expect that testers of 5.0-DP2 will follow the technical discussions on the freebsd-current@ mailing list.

AVAILABILITY

FreeBSD 5.0-DP2 is being released for the alpha, ia64, i386, pc98, and sparc64 architectures. As of this writing, 5.0-DP2/i386 is available, with other architectures to follow soon.

The checksums for the two i386 ISO images are as follows:

MD5 (5.0-DP2-disc1.iso) = 997ef9ed5aa3e0721678f5482d2fc664
MD5 (5.0-DP2-disc2.iso) = 425718dbf1b771c8317556b7a13842c6

Before trying the central FTP site, we strongly recommend that you check FTP mirror sites in your country or region, such as:

ftp://ftp.<yourcountry>.FreeBSD.org/pub/FreeBSD/

Any additional mirror sites will be named ftp2, ftp3, and so forth. Appendix A of the FreeBSD Handbook has additional information about FreeBSD mirror sites; it is available on-line at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

Some of the mirror sites known to carry 5.0-DP2 (in alphabetical order by country code) are:

Release documentation is available in the distributions, as well as on the FreeBSD Web site:

LATE-BREAKING NEWS

-

Certain parts of the KDE and GNOME desktop environments did not make +

Certain parts of the KDE and GNOME desktop environments did not make it to the package sets in the i386 ISO images.

The sparc64 and ia64 snapshots may or may not have package sets associated with them.

ACKNOWLEDGEMENTS

The FreeBSD Project wishes to thank the companies, developers, and users who continue to make FreeBSD releases possible.

Many companies donated equipment, network access, or person-hours to finance our ongoing release engineering activities, including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, NTT/Verio, and Packet Design. We greatly appreciate their contributions.

The release engineering team for 5.0-DP2 includes:

Murray Stokely <murray@FreeBSD.org> Release Engineering Team Lead
John Baldwin <jhb@FreeBSD.org> Release Engineering, alpha and sparc64 Builds
Scott Long <scottl@FreeBSD.org> Developer Communications
Bruce A. Mah <bmah@FreeBSD.org> Release Documentation, i386 Build
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Marcel Moolenaar <marcel@FreeBSD.org> ia64 Build
TAKAHASHI Yoshihiro <nyan@FreeBSD.org> pc98 Build
Kris Kennaway <kris@FreeBSD.org> i386 and alpha Package Builds

FreeBSD 5.0-DP2 is, as with every release, a cooperative effort of all of the FreeBSD committers <committers@FreeBSD.org>, as well as FreeBSD users all over the world who have submitted new features, bug fixes, and suggestions. Please join us in thanking everyone for their hard work in polishing and improving the state of the FreeBSD -CURRENT development branch.

We'd like to emphasize once again that this snapshot represents a work-in-progress. Please help us by testing it now, so that we can make FreeBSD 5.0-RELEASE as stable and useful as possible.

Thanks!

Bruce A. Mah
(For the FreeBSD Release Engineering Team)

+&footer; + diff --git a/en/releases/5.0R/DP2/hardware.sgml b/en/releases/5.0R/DP2/hardware.sgml index c9384cfc96..a03b6ecfdf 100644 --- a/en/releases/5.0R/DP2/hardware.sgml +++ b/en/releases/5.0R/DP2/hardware.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 5.0-DP2 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/DP2/installation.sgml b/en/releases/5.0R/DP2/installation.sgml index b788b149a0..57d1482dea 100644 --- a/en/releases/5.0R/DP2/installation.sgml +++ b/en/releases/5.0R/DP2/installation.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Installation notes for FreeBSD 5.0-DP2 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/DP2/relnotes.sgml b/en/releases/5.0R/DP2/relnotes.sgml index 784da0f0df..11b2558846 100644 --- a/en/releases/5.0R/DP2/relnotes.sgml +++ b/en/releases/5.0R/DP2/relnotes.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.0-DP2 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/announce.sgml b/en/releases/5.0R/announce.sgml index 76e318b429..0a4cc5bf35 100644 --- a/en/releases/5.0R/announce.sgml +++ b/en/releases/5.0R/announce.sgml @@ -1,194 +1,197 @@ - + + %navincludes; %includes; ]> &header;

Date: Sun, 19 Jan 2003 10:03:42 -0700
From: scottl@FreeBSD.org (Scott Long)
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 5.0 Release Available

It is my privilege and pleasure to announce the availability of FreeBSD 5.0-RELEASE. The culmination of nearly three years of work, this release starts FreeBSD on the path of advanced multiprocessor and application thread support and introduces support for the sparc64 and ia64 platforms. Among the long list of new and improved features:

-

Although FreeBSD 5.0 contains a number of new and exciting features, it -may not be suitable for all users. More conservative users may prefer -to continue using FreeBSD 4.X. Information on the various trade-offs -involved, as well as some notes on future plans for both FreeBSD 4.X +

Although FreeBSD 5.0 contains a number of new and exciting features, it +may not be suitable for all users. More conservative users may prefer +to continue using FreeBSD 4.X. Information on the various trade-offs +involved, as well as some notes on future plans for both FreeBSD 4.X and 5.X, can be found in the Early Adopter's Guide, available here:

http://www.FreeBSD.org/releases/5.0R/early-adopter.html

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/5.0R/relnotes.html

http://www.FreeBSD.org/releases/5.0R/errata.html

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Availability

FreeBSD 5.0-RELEASE supports the i386, pc98, alpha, sparc64, and ia64 architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for all architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.0 based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.0 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 5.0-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering and Building
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org> IA64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer
+&footer; + diff --git a/en/releases/5.0R/hardware.sgml b/en/releases/5.0R/hardware.sgml index fdeee59407..8cf328540a 100644 --- a/en/releases/5.0R/hardware.sgml +++ b/en/releases/5.0R/hardware.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.0-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/installation.sgml b/en/releases/5.0R/installation.sgml index 730de67df9..43e4212f83 100644 --- a/en/releases/5.0R/installation.sgml +++ b/en/releases/5.0R/installation.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.0-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/relnotes.sgml b/en/releases/5.0R/relnotes.sgml index f654521ff6..ead67a159f 100644 --- a/en/releases/5.0R/relnotes.sgml +++ b/en/releases/5.0R/relnotes.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.0-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.0R/schedule.sgml b/en/releases/5.0R/schedule.sgml index c599cd8813..e4f0595880 100644 --- a/en/releases/5.0R/schedule.sgml +++ b/en/releases/5.0R/schedule.sgml @@ -1,213 +1,214 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD 5.0. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

One of the major new features of FreeBSD 5.0 will be completely re-worked SMP support. For specific information about the progress towards 5.0-RELEASE in this area, please see the SMP Project page.

The current release engineering TODO list is also available. This list is updated periodically through the release cycle.

Schedule

- +
ActionExpectedActualDescription
releng_5_dp1 branch (Perforce)15 Mar 200215 Mar 2002Branch created, commits require re@ approval. The branch will be used to allow us time to QA the release, synchronize the release notes with the translation teams, synchronize sysinstall and the package set, etc without disrupting the normal flow of development on -CURRENT.
Ports Freeze2 Apr 20022 Apr 2002The ports tree is frozen and tagged for the developer preview.
Final i386 package build completes3 Apr 20024 Apr 2002The final package build for the i386 architecture is complete.
Final Alpha package build completes3 Apr 20025 Apr 2002The final package build for the Alpha architecture is complete.
Final sparc64 package build completes3 Apr 20027 Apr 2002The final package build for the sparc64 architecture is complete.
Package Split3 Apr 20027 Apr 2002The packages for the installation CDROM are selected from the results of the final package build.
FreeBSD 5.0 Developer Preview 15 Apr 20028 Apr 2002A full release for the i386, Alpha, and sparc64 architectures. The i386 and Alpha releases at least will contain a full package set and a disc1 ISO image will be made available.
5.0 Feature List finalized16 Jun 2002--At the FreeBSD Developer Summit at Usenix, we will need to finalize the list of features that will be included with FreeBSD 5.0. Some features will just have to wait for 5.1 to give us ample time to QA the many features that are ready.
RELENG_5_0_DP2 branch17 Jul 200217 Aug 2002Branch created in Perforce, commits require re@ approval.
FreeBSD 5.0 Developer Preview 225 Jul 200218 Nov 2002A full release for the i386, Alpha, and sparc64 architectures.
-CURRENT feature freeze1 Oct 200216 Oct 2002After this date, significant new features should be discussed with re@ before consideration for 5.0-RELEASE.
-CURRENT code freeze20 Oct 200218 Nov 2002The code freeze for 5.0. Commits to HEAD require re@ approval.
First release candidate2 Dec 20029 Dec 2002 x86, alpha, sparc64, and ia64 images released and uploaded to ftp-master.FreeBSD.org.
RELENG_5_0 branched12 Dec 200212 Dec 2002 Branch from HEAD for the release. Note: no branch for RELENG_5 will happen a this time.
src unfrozen12 Dec 200212 Dec 2002 Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE.
Second release candidate17 Dec 200221 Dec 2002 --
Ports tree tagged3 Jan 20031 Jan 2003 Tentative date of RELEASE_5_0_0 tag for ports.
Start RC3 builds7 Jan 20039 Jan 2003 Set timestamp and start i386, pc98, sparc64, alpha, and ia64 builds.
Third release candidate released10 Jan 2003 12 Jan 2003--
Version numbers bumped15 Jan 200315 Jan 2003 The files listed here are updated to reflect FreeBSD 5.0.
src tree tagged15 Jan 200316 Jan 2003 Tag the RELENG_5_0 branch with RELENG_5_0_0_RELEASE
doc tree tagged15 Jan 200315 Jan 2003 Tag the doc/ branch with RELEASE_5_0_0
Final builds15 Jan 200316 Jan 2003 Start x86, alpha, sparc64, ia64, and pc98 builds.
Warn hubs@FreeBSD.org15 Jan 200317 Jan 2003 Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master17 Jan 200317 Jan 2003 Release and packages uploaded to ftp-master.FreeBSD.org
FreeBSD 5.0 Released19 Jan 200319 Jan 2003 FreeBSD 5.0 is announced to the mailing lists.
FreeBSD 5.0 Press Release19 Jan 2003-- A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications.
&footer; diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml index b9fcba55ad..5bb63f5cf7 100644 --- a/en/releases/5.0R/todo.sgml +++ b/en/releases/5.0R/todo.sgml @@ -1,168 +1,169 @@ - + + %navincludes; %includes; %developers; ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.0. If you have any updates for this list, please e-mail re@FreeBSD.org.

Must Resolve Issues for 5.0-RELEASE

- +
IssueStatusResponsibleDescription
None at this time.

Desired Features for 5.0-RELEASE

- +
IssueStatusResponsibleDescription
a.out toolchain port -- -- A.out support in the base system was reduced; the removed build chain components should be made into a port.
NETNCP and nwfs broken -- -- NETNCP and nwfs appear to be as-yet unadapted for KSE, and hence not working. The build needs fixing (probably not all that hard) and then it needs to be tested (harder: few people appear to have Netware servers).
No docs for FAST IPSEC -- -- The new "fast ipsec" implementation has insufficient documentation (man pages, release notes), and this would be highly desirable to have before 5.0-RELEASE.
Race conditions in truss Errata candidate &a.robert; Truss appears to contain a race condition during the start-up of debugging, which can result in truss failing to attach to the process before it exits. The symptom is that truss reports that it cannot open the procfs node supporting the process being debugged. A bug also appears to exist where in truss will hang if execve() returns ENOENT. A further race appears to exist in which truss will return "PIOCWAIT: Input/output error" occasionally on startup. The fix for this sufficiently changes process execution handling that we will defer the fix to post-5.0 and consider this errata.
Documentation rottage: S/Key -- -- We now use OPIE instead of S/Key. The handbook doesn't know that yet.
Documentation wanted: gdbe -- &a.chris; 5.0 includes GDBE, supporting encryption of swap and storage. It would be nice if that was documented in the handbook.
iir driver fails to probe disks -- -- During the install, the iir controller appears to correctly probe, but finds no disk devices. The card in question is an Intel srcu32 RAID controller with 32Mb RAM, Firmware revision 2.33.01. Direct access to real iir hardware for SCSI developers would be very helpful in resolving this problem.
mly driver hangs during install -- &a.scottl;, &a.jeff; Hangs have been reported during the 5.0 snapshot install when installing to mly supported RAID arrays. The same array appears to work fine with 4.7-RELEASE. The card in question is a Mylex AcceleRAID 170, 32 Mb RAM, Firmware revision 7.01-00. This is believed to be the same problem as described in PR 45383.

Areas requiring immediate testing due to 5.0 changes

- +
IssueStatusResponsibleDescription
if_ie, if_le, if_wl network device drivers -- &a.sam; Changes made to the ethernet driver interfaces required sweeping API changes across all ethernet device drivers. While these changes are largely mechanical, they were not tested for three less frequently used interface drivers: if_ie, if_le, and if_wl. They each require testing (and probably fixing) prior to 5.0-RELEASE. If you have access to devices that use these drivers, please perform local testing and provide feedback to Sam Leffler.
No console (term) if smbus is enable in the kernel -- -- There are reports that kernels build with smbus, viapm, and smb devices may not properly probe and support the system console following boot.

Known Issues with 5.0R-RC1 / i386

- +
IssueStatusResponsibleDescription
KDE does not install from ISO In Progress &a.murray; The kde meta-package is not included on the ISO, but many of the component kde packages are, so sysinstall gets confused and installs kde-icontheme instead (more correct behavior would be to fall back to kdebase if kde package is not present).
&footer; diff --git a/en/releases/5.1R/announce.sgml b/en/releases/5.1R/announce.sgml index 29e7f63438..314022a855 100644 --- a/en/releases/5.1R/announce.sgml +++ b/en/releases/5.1R/announce.sgml @@ -1,236 +1,239 @@ - + + %navincludes; %includes; ]> &header;

Date: Mon, 9 Jun 2003 09:36:57 -0700 (PDT)
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] ]FreeBSD 5.1 Released!

It is my great privilege and pleasure to announce the availability of FreeBSD 5.1-RELEASE. This release continues FreeBSD on the path of advanced multiprocessor and application thread support and includes many improved and widely-sought features:

Although stability is greatly improved and many bugs have been fixed, FreeBSD 5.1 might not be suitable for all users. More conservative users may prefer to continue using FreeBSD 4.X. Information on the various trade-offs involved, as well as some notes on future plans for both FreeBSD 4.X and 5.X, can be found in the Early Adopter's Guide, available here:

http://www.FreeBSD.org/releases/5.1R/early-adopter.html

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/5.1R/relnotes.html

http://www.FreeBSD.org/releases/5.1R/errata.html

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

This release is dedicated to the memory of Alan Eldridge. Alan was a talented and dedicated member of the KDE On FreeBSD team and the FreeBSD community, and his passing is mourned by all of us. For more information, -please see +please see http://freebsd.kde.org/memoriam/alane.php.

Availability

FreeBSD 5.1-RELEASE supports the i386, pc98, alpha, sparc64, and ia64 architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for all architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.1 based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Saraville, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.1 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 5.1-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, IA32 and Alpha Release Building
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Bill Fenner <fenner@FreeBSD.org> Sparc64 Release Building
Marcel Moolenaar <marcel@FreeBSD.org> IA64 Release Building
Peter Wemm <peter@FreeBSD.org> AMD64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer
+&footer; + diff --git a/en/releases/5.1R/hardware.sgml b/en/releases/5.1R/hardware.sgml index e4d3705ef3..c1bc3b75f2 100644 --- a/en/releases/5.1R/hardware.sgml +++ b/en/releases/5.1R/hardware.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.1R/installation.sgml b/en/releases/5.1R/installation.sgml index b1c7fe75bf..97973f4bc4 100644 --- a/en/releases/5.1R/installation.sgml +++ b/en/releases/5.1R/installation.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.1R/relnotes.sgml b/en/releases/5.1R/relnotes.sgml index 56380f19bd..a6bb244c54 100644 --- a/en/releases/5.1R/relnotes.sgml +++ b/en/releases/5.1R/relnotes.sgml @@ -1,29 +1,33 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.1R/schedule.sgml b/en/releases/5.1R/schedule.sgml index 65c29ece21..372d2185b7 100644 --- a/en/releases/5.1R/schedule.sgml +++ b/en/releases/5.1R/schedule.sgml @@ -1,181 +1,182 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD 5.1. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public FreeBSD-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

One of the major features of FreeBSD 5.1 will be further refinement of the re-worked SMP support introduced in FreeBSD 5.0. For specific information about the progress towards 5.1-RELEASE in this area, please see the SMP Project page.

FreeBSD 5.1 will continue to be released from the 5-CURRENT development stream. For more details about the milestones for reaching 5-STABLE, see the 5-STABLE Roadmap page.

The current release engineering TODO list is also available. This list is updated periodically through the release cycle.

Schedule

- +
Action Expected Actual Description
-CURRENT code freeze 5 May 2003 5 May 2003 The src/ code freeze for 5.1. Commits to HEAD require re@FreeBSD.org approval.
5.1-BETA 5 May 2003 15 May 2003 5.1-BETA release of x86, alpha, sparc64, and ia64.
5.1-BETA2 19 May 2003 22 May 2003 Second 5.1-BETA release of x86, alpha, sparc64, and ia64.
RELENG_5_1 branched 30 May 2003 31 May 2003 Branch of src/ from HEAD for the release. Note: no branch for RELENG_5 will happen at this time.
Turn off debugging for RELENG_5_1 30 May 2003 31 May 2003 Turn off WITNESS, INVARIANTS, and malloc debugging options similar to what was done for 5.0.
First release candidate 30 May 2003 1 June 2003 x86, alpha, sparc64, and ia64 images released and uploaded to ftp-master.FreeBSD.org.
src/ unfrozen 30 May 2003 31 May 2003 Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE.
Ports tree tagged 30 May 2003 27 May 2003 Tentative date of RELEASE_5_1_0 tag for ports.
Version numbers bumped 2 June 2003 3 June 2003 The files listed here are updated to reflect FreeBSD 5.1.
src/ tree tagged 2 June 2003 4 June 2003 Tag the RELENG_5_1 branch with RELENG_5_1_0_RELEASE.
doc/ tree tagged 2 June 2003 30 May 2003 Tag the doc/ tree with RELEASE_5_1_0.
Final builds 2 June 2003 4 June 2003 Start x86, alpha, sparc64, ia64, and pc98 builds.
Warn hubs@FreeBSD.org 5 June 2003 5 June 2003 Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master 5 June 2003 8 June 2003 Release and packages uploaded to ftp-master.FreeBSD.org.
FreeBSD 5.1 Released 9 June 2003 9 June 2003 FreeBSD 5.1 is announced to the mailing lists.
FreeBSD 5.1 Press Release 9 June 2003 9 June 2003 A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications.
&footer; diff --git a/en/releases/5.1R/todo.sgml b/en/releases/5.1R/todo.sgml index 23760f46af..f420d8fe17 100644 --- a/en/releases/5.1R/todo.sgml +++ b/en/releases/5.1R/todo.sgml @@ -1,111 +1,112 @@ - + + %navincludes; %includes; %developers; ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.1. If you have any updates for this list, please e-mail re@FreeBSD.org.

Must Resolve Issues for 5.1-RELEASE

- +
IssueStatusResponsibleDescription

Desired Features for 5.1-RELEASE

- +
IssueStatusResponsibleDescription

Documentation items that must be resolved for 5.1

- +
IssueStatusResponsibleDescription

Areas requiring immediate testing

- +
- +
IssueStatusResponsibleDescription
Fresh ACPI-CA import -- -- The 20030228 vendor sources have been imported. Further testing is appreciated.
PAE support for i386 -- -- PAE support allows the use of up to 64GB of RAM on Pentium Pro and above systems. Virtual addresses are still constrained to 32-bits.
if_wi problems on Lucent hardware -- -- The recently upgraded if_wi driver is more tuned to Prism hardware than to Lucent hardware, resulting in system lockups and poor performance when using Lucent hardware. These problems are believed to be fixed but more testing is welcome.
UFS2 as installation, newfs default -- &a.rwatson; For 5.1-RELEASE, the default file system type for newly created file systems is UFS2 rather than UFS1. newfs(8) and sysinstall(8) have been updated to use this new default. Testing to make sure all goes well after the change (committed on April 20, 2003) is vital.
NSSwitch support -- &a.nectar; Support for pluggable directory services using NSS, including adaptations of current directory services (local databases, NIS), and support for new services (LDAP, Active Directory, etc). This change has been committed, and requires broader testing.
Spurious alpha panics -- -- &a.kris; reports that he has seen several unique panics on the alpha machines, but since gdb -k doesn't work on alpha I haven't been able to get more than a DDB traceback. No-one has looked into them.
&footer; diff --git a/en/releases/5.2.1R/announce.sgml b/en/releases/5.2.1R/announce.sgml index 6f865eb766..4e0db55c64 100644 --- a/en/releases/5.2.1R/announce.sgml +++ b/en/releases/5.2.1R/announce.sgml @@ -1,269 +1,272 @@ - + + %navincludes; %includes; ]> &header;

Date: Wed, 25 Feb 2004 20:31:31 -0700 (MST)
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 5.2.1 Released!

It is once again my great privilege and pleasure to announce the availability of FreeBSD 5.2.1-RELEASE. This is a 'point release' and is intended to address several bugs and vulnerabilities discovered in the FreeBSD 5.2 release. These include:

FreeBSD 5.2.1 also contains a number of other significant stability and security improvements over FreeBSD 5.2. However, it is still considered a 'New Technology' release and might not be suitable for all users. Those with more conservative needs may prefer to continue using FreeBSD 4.X. Information on the various trade-offs involved, as well as some notes on future plans for both FreeBSD 4.X and 5.X, can be found in the Early Adopter's Guide, available here:

http://www.FreeBSD.org/releases/5.2.1R/early-adopter.html

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/5.2.1R/relnotes.html

http://www.FreeBSD.org/releases/5.2.1R/errata.html

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Availability

FreeBSD 5.2.1-RELEASE supports the i386, pc98, alpha, sparc64, amd64, and ia64 architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for all architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.2.1 based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.2.1 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 5.2.1-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, I386 and Alpha Release Building
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Sparc64 Release Building, Mirror Site Coordination
Marcel Moolenaar <marcel@FreeBSD.org> IA64 Release Building
David O'Brien <obrien@FreeBSD.org> AMD64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer

CD Image Checksums

 MD5 (5.2.1-RELEASE-alpha-bootonly.iso) = 44136b68eb96d0b0776fcbca3648b020
 MD5 (5.2.1-RELEASE-alpha-disc1.iso) = ff5a9ebff52dba2db2e5afdfc996cfe4
 MD5 (5.2.1-RELEASE-alpha-disc2.iso) = bace8bceb3186b5bdeccccdc1c2b26cb
 MD5 (5.2.1-RELEASE-alpha-miniinst.iso) = 2a30597f5306a539963e826f1f29fb91
 
 MD5 (5.2.1-RELEASE-amd64-bootonly.iso) = 60a590202b07b264d33e30a40f745ba6
 MD5 (5.2.1-RELEASE-amd64-disc1.iso) = 7fdc18683561f58df0a2bc6327a6552b
 MD5 (5.2.1-RELEASE-amd64-disc2.iso) = fce7b8a76e85772c9d572b84ba1107af
 MD5 (5.2.1-RELEASE-amd64-miniinst.iso) = ff4d14fffaa8c4864e167f7df57189ee
 
 MD5 (5.2.1-RELEASE-i386-bootonly.iso) = 5035853dd92a0807645dc1674a2ee028
 MD5 (5.2.1-RELEASE-i386-disc1.iso) = 9a1c764680504f5b7d2fb8c2d07de8e0
 MD5 (5.2.1-RELEASE-i386-disc2.iso) = 86b96a834fdda87f7436373c53ff3662
 MD5 (5.2.1-RELEASE-i386-miniinst.iso) = 6f035aef6598c0307cf53a896ccfa12f
 
 MD5 (5.2.1-RELEASE-ia64-bootonly.iso) = dcdb3bc8fc5ae29fa7deeb836debc0a7
 MD5 (5.2.1-RELEASE-ia64-disc2.iso) = 59349f53622559263f77a6d599ebb74e
 MD5 (5.2.1-RELEASE-ia64-miniinst.iso) = 80148ffa7420828e28ce53ccfe3f1b8b
 
 MD5 (5.2.1-RELEASE-pc98-disc2.iso) = 06243edad4243fbdfa45f34965c13e5d
 MD5 (5.2.1-RELEASE-pc98-miniinst.iso) = 513c50b09da1cf1d8afda8df3599e754
 
 MD5 (5.2.1-RELEASE-sparc64-bootonly.iso) = e9b3e29c6c78aeb5f9176f8c04b9de93
 MD5 (5.2.1-RELEASE-sparc64-disc1.iso) = f9d463ccd832a3157603c68ddb9126ae
 MD5 (5.2.1-RELEASE-sparc64-disc2.iso) = 8a2c544ce9d9a6c632c8a5120ee99bc7
 MD5 (5.2.1-RELEASE-sparc64-miniinst.iso) = 069784739bd4c2244077f8423d97fda6
+&footer; + diff --git a/en/releases/5.2.1R/hardware.sgml b/en/releases/5.2.1R/hardware.sgml index 13b4e90446..de768cb391 100644 --- a/en/releases/5.2.1R/hardware.sgml +++ b/en/releases/5.2.1R/hardware.sgml @@ -1,31 +1,35 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2.1R/installation.sgml b/en/releases/5.2.1R/installation.sgml index fa127461d4..07aa371547 100644 --- a/en/releases/5.2.1R/installation.sgml +++ b/en/releases/5.2.1R/installation.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2.1R/relnotes.sgml b/en/releases/5.2.1R/relnotes.sgml index b9ac132f97..b6df4bbef2 100644 --- a/en/releases/5.2.1R/relnotes.sgml +++ b/en/releases/5.2.1R/relnotes.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2R/announce.sgml b/en/releases/5.2R/announce.sgml index 149e8421d9..400be72cf5 100644 --- a/en/releases/5.2R/announce.sgml +++ b/en/releases/5.2R/announce.sgml @@ -1,271 +1,274 @@ - + + %navincludes; %includes; ]> &header;

Date: Mon, 12 Jan 2004 13:25:30 -0700 (MST)
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 5.2 Released!

It is once again my great privilege and pleasure to announce the availability of FreeBSD 5.2-RELEASE. Building upon the success of FreeBSD 5.1, this release includes:

FreeBSD 5.2 also contains a number of significant stability and performance improvements over FreeBSD 5.1. However, it is still considered a 'New Technology' release and might not be suitable for all users. Users with more conservative needs may prefer to continue using FreeBSD 4.X. Information on the various trade-offs involved, as well as some notes on future plans for both FreeBSD 4.X and 5.X, can be found in the Early Adopter's Guide, available here:

http://www.FreeBSD.org/releases/5.2R/early-adopter.html

For a complete list of new features and known problems, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/5.2R/relnotes.html

http://www.FreeBSD.org/releases/5.2R/errata.html

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Availability

FreeBSD 5.2-RELEASE supports the i386, pc98, alpha, sparc64, amd64, and ia64 architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server. Distributions for all architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.2 based products:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.2 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 5.2-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, IA32 and Alpha Release Building
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Sparc64 Release Building, Mirror Site Coordinator
Marcel Moolenaar <marcel@FreeBSD.org> IA64 Release Building
David O'Brien <obrien@FreeBSD.org> AMD64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer

CD Image Checksums

 MD5 (5.2-RELEASE-i386-bootonly.iso) = 3adbf5641c35ce2fb4f60295a9131794
 MD5 (5.2-RELEASE-i386-disc1.iso) = cc2c9f647850df2bf96a478f0cbf18b6
 MD5 (5.2-RELEASE-i386-disc2.iso) = ae5e15ee38e3f4f2a05c9355fa0a1aed
 MD5 (5.2-RELEASE-i386-miniinst.iso) = 40c9a789d7d8e472914f9bc1e34ea04f
 
 MD5 (5.2-RELEASE-alpha-bootonly.iso) = 75f19aa7c24ac91af9bc21376a1d980b
 MD5 (5.2-RELEASE-alpha-disc1.iso) = 727785cb6485828db5e7f6b75217ed55
 MD5 (5.2-RELEASE-alpha-disc2.iso) = b83e38a9cd698051fc05915932b03b82
 MD5 (5.2-RELEASE-alpha-miniinst.iso) = 87042a14d0de3979667bb9d41bd84d45
 
 MD5 (5.2-RELEASE-sparc64-bootonly.iso) = e08fe8cf77549c7404acf7ee03eeeb0e
 MD5 (5.2-RELEASE-sparc64-disc1.iso) = 2373f5bd491a15cfc8fa856fe92b75b9
 MD5 (5.2-RELEASE-sparc64-disc2.iso) = 2fb598c20873f79fcf1afc112de06641
 MD5 (5.2-RELEASE-sparc64-miniinst.iso) = f6f064e3785367f1b2d673502f59565a
 
 MD5 (5.2-RELEASE-ia64-bootonly.iso) = b8ac4103a1703df9dba00f14a7c7557c
 MD5 (5.2-RELEASE-ia64-disc1.iso) = d473c7fc79f8e40b3e331300ead5b90e
 MD5 (5.2-RELEASE-ia64-disc2.iso) = c2a59d77bac522e7f8dee0460423cc2a
 MD5 (5.2-RELEASE-ia64-miniinst.iso) = a545b3974d18f0fd7796bff84b50825f
 
 MD5 (5.2-RELEASE-amd64-bootonly.iso) = 4cefddd4dd3f1b67e9f78380a058de81
 MD5 (5.2-RELEASE-amd64-disc1.iso) = 308af2fa0e96a394d445e8e89c1cbece
 MD5 (5.2-RELEASE-amd64-disc2.iso) = b00834c97fbab12d3ea4b159134a8f63
 MD5 (5.2-RELEASE-amd64-miniinst.iso) = 06f19271f985ca1acbd45fe9a6b13204
 
 MD5 (5.2-RELEASE-pc98-disc2.iso) = b167880c4e644f16f7377b715ccbf7c6
 MD5 (5.2-RELEASE-pc98-miniinst.iso) = 3b6ca2637d41e7052c028a41a1cefc6d
+&footer; + diff --git a/en/releases/5.2R/hardware.sgml b/en/releases/5.2R/hardware.sgml index 74a49c1c80..ff090d420d 100644 --- a/en/releases/5.2R/hardware.sgml +++ b/en/releases/5.2R/hardware.sgml @@ -1,31 +1,35 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.2-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2R/installation.sgml b/en/releases/5.2R/installation.sgml index b9bd6fd27c..5fdcac28cf 100644 --- a/en/releases/5.2R/installation.sgml +++ b/en/releases/5.2R/installation.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.2-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2R/relnotes.sgml b/en/releases/5.2R/relnotes.sgml index 4c8cdaf309..9204f11f39 100644 --- a/en/releases/5.2R/relnotes.sgml +++ b/en/releases/5.2R/relnotes.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.2-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.2R/schedule.sgml b/en/releases/5.2R/schedule.sgml index da9b22174f..ad246676df 100644 --- a/en/releases/5.2R/schedule.sgml +++ b/en/releases/5.2R/schedule.sgml @@ -1,217 +1,218 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD 5.2. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public FreeBSD-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

FreeBSD 5.2 will continue to be released from the 5-CURRENT development stream. For more details about the milestones for reaching 5-STABLE, see the 5-STABLE Roadmap page.

The current release engineering TODO list is also available. This list is updated periodically through the release cycle.

Schedule

- +
Action Expected Actual Description
src/ tree frozen 17 Nov 2003 18 Nov 2003 Announce the src/ code freeze for 5.2 on the HEAD branch. Commits to HEAD require re@FreeBSD.org approval.
ports/ tree frozen 17 Nov 2003 19 Nov 2003 Announce the ports/ code freeze for 5.2. Commits to ports/ require portmgr@FreeBSD.org approval.
Begin 5.2-BETA builds 17 Nov 2003 24 Nov 2003 Begin building 5.2-BETA disc1 and disc2 for all Tier-1 platforms.
Release 5.2-BETA 19 Nov 2003 26 Nov 2003 5.2-BETA tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
RELENG_5_2 branched 1 Dec 2003 6 Dec 2003 Branch of src/ from HEAD for the release. Note: no branch for RELENG_5 will happen at this time.
Turn off debugging for RELENG_5_2 1 Dec 2003 6 Dec 2003 Turn off WITNESS, INVARIANTS, and malloc debugging options similar to what was done for 5.1.
Begin 5.2-RC1 builds 1 Dec 2003 7 Dec 2003 Begin building 5.2-RC1 disc1 and disc2 for all Tier-1 platforms.
src/ unfrozen 1 Dec 2003 6 Dec 2003 Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE.
Release 5.2-RC1 3 Dec 2003 10 Dec 2003 5.2-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged 3 Dec 2003 3 Dec 2003 Tentative date of RELEASE_5_2_0 tag for ports.
doc/ tree slush 8 Dec 2003 9 Dec 2003 Announce the doc/ slush for 5.2. From this time until the tagging of the doc/ tree, non-critical changes should be postponed to allow translation teams time to finish their work for the release.
Begin 5.2-RC2 builds 19 Dec 2003 21 Dec 2003 Begin building 5.2-RC2 disc1 and disc2 for all Tier-1 platforms.
Release 5.2-RC2 21 Dec 2003 23 Dec 2003 5.2-RC2 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged 12 Dec 2003 12 Dec 2003 Tag the doc/ tree with RELEASE_5_2_0.
Version numbers bumped Jan 2004 Jan 11 2004 The files listed here are updated to reflect FreeBSD 5.2.
src/ tree tagged Jan 2004 Jan 11 2004 Tag the RELENG_5_2 branch with RELENG_5_2_0_RELEASE.
Begin 5.2-RELEASE builds Jan 2004 Jan 11 2004 Start 5.2-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org Jan 2004 Jan 11 2004 Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master Jan 2004 Jan 11 2004 Release and packages uploaded to ftp-master.FreeBSD.org.
FreeBSD 5.2 Announced Jan 2004 Jan 12 2004 FreeBSD 5.2 is announced to the mailing lists.
FreeBSD 5.2 Press Release Jan 2004 Jan 12 2004 A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications.
&footer; diff --git a/en/releases/5.2R/todo.sgml b/en/releases/5.2R/todo.sgml index 815111c96f..356e5b4df4 100644 --- a/en/releases/5.2R/todo.sgml +++ b/en/releases/5.2R/todo.sgml @@ -1,271 +1,272 @@ - + + %navincludes; %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail re@FreeBSD.org.

Show stopper defects for 5.2-RELEASE

- +
IssueStatusResponsibleDescription

Required features for 5.2-RELEASE

- +
IssueStatusResponsibleDescription
Fine-grained network stack locking without Giant &status.wip; &a.sam; Significant parts of the network stack (especially IPv4 and IPv6) now have fine-grained locking of their data structures. However, it is not yet possible for the netisr threads to run without Giant, due to dependencies on sockets, routing, etc. A 5.2-RELEASE goal is to have the forwarding path in the network stack able to run without Giant, which should substantially improve performance of the stack, as well as other system components by reducing contention on Giant. For stability reasons, this will be disabled by default in 5.2.

Desired features for 5.2-RELEASE

- +
IssueStatusResponsibleDescription
KAME Synchronization &status.wip; &a.ume; The FreeBSD KAME IPv6 code is now substantially dated with respect to the KAME vendor source. The FreeBSD Project needs to take initiative in driving the merge of new bug fixes, features, et al.
Light-weight interrupt threads, context switches &status.new; -- Currently, there are two classes of interrupt handlers in 5.x: fast interrupt handlers which run entirely in interrupt context, and heavy-weight handlers which execute in a full-weight kernel interrupt thread. It is possible to optimize interrupt thread context management such that a light-weight context switch is performed to begin execution of the interrupt thread in the handler context, and only when a full-weight context is required (such as sleeping on a lock) is that cost required. This optimization should substantially improve interrupt latency. There are also additional kernel thread context switch optimizations that can be made to improve the performance of thread workers in the kernel, such as found in the network stack, crypto worker threads, and GEOM. &a.bmilekic; has done substantial prototyping work, and should be coordinated with.
Run-time autoconfiguration of GBDE and related transforms &status.new; -- Currently, gbde must be manually configured at run-time each time an encrypted disk device is mounted. This prevents easy integration into /etc/fstab and easy automated deployment. Improved integration with the configuration, mounting, and boot process is required to make this feature more easily accessible.
gdb -k support for alpha &status.new; &a.mp; gdb -k doesn't work on alpha

Documentation items desired for 5.2

- +
IssueStatusResponsibleDescription
Revise EAG &status.done; &a.bmah; The Early Adopters Guide needs to be revised, hopefully for the last time, to reflect the state of 5.2.
Trim Hardware Notes &status.wip; &a.bmah; Ongoing project to remove redundancy in documentation by removing lists of specific devices from the hardware notes and pointing readers to driver manpages.

Testing focuses for 5.2-RELEASE

- +
IssueStatusResponsibleDescription
PCM locking and performance issues &status.untested; -- The PCM audio framework and device drivers have been locked and free of Giant for quite a while, but LOR problems persist along with reports of poor audio performance under load. These problems are believed to have been corrected, but more testing is desired.
ATA driver structural improvements, MPsafety &status.untested; &a.sos; New ATA model has arrived, supporting fine-grained locking, and more. Much testing is needed to ensure no regressions.
GPT support for sysinstall &status.untested; &a.marcel; Sysinstall and libdisk has been overhauled to support the GPT partition scheme used on ia64.
Complete the APIC PCI interrupt routing support &status.untested; &a.jhb Interrupt routing on ia32 has been completely re-written to support ACPI hints for PCI interrupt routing, along with ACPI hints for CPU enumeration. There have been reports of interrupt storms or a failure for interrupts to deliver, possibly a result of bad ACPI information. These problems need to be tracked down and resolved.
ATAng crashdump causes disk corruption &status.untested; &a.sos;, &a.tegge; Performing a crashdump on an ATA device can result in a corrupted MBR record. Tor has a possible patch for this.
SMP users report acpi_cpu panic during shutdown &status.untested; &a.njl; The ACPI code registers eventhandlers that are not unregistered when ACPI shuts down during system shutdown. The result can be a panic during shutdown. Nate is circulating a patch that is believed to correct this problem.
random_harvest panic &status.untested; &a.markm; There are reports of witness panics in random_harvest_internal() due to last minute changes in interrupt entropy harvesting code. Systems running with INVARIANTS will rapidly panic. Update: a workaround has been committed, but the original change must either be backed out or revised before we can cut the first beta.
Vinum data corruption and memory allocation problems &status.untested; &a.grog; In the last week, reports of two new (and possibly related) Vinum failures have come to light: a warning message of vinum: exiting with malloc table inconsistency at 0xc2053c00 from vinumio.c:755 has been experienced when Vinum auto-configuration fails. Also, even simple test cases for Vinum I/O appear to result in incorrect data being returned from disk, rendering Vinum unusable in several reproduceable configurations.
ACPI kernel module &status.untested; &a.jhb; The new i386 inpterrupt code should work whether the acpi driver is compiled into the kernel or loaded as a module. The loader should automatically load the module if it's not already compiled in.
Reported NFS failures &status.unknown;   There have been a number of reports of NFS clients and server hangs. Unfortunately, these are difficult to reproduce, and have not yet been traced back to a particular change or reliable reproduction scenario.
Turnstile assertion failure &status.unknown &a.jhb; panic: Assertion td->td_turnstile != NULL failed at ../../../kern/subr_turnstile.c:427 has been affecting several users on multiple platforms. This has hopefully been fixed now, but more testinig is needed.
fsync panic while installing with softupdates enabled &status.untested; &a.dwhite;, &a.jeff; There is a repeatable panic happening for many people while installing 5.2-RC1 when softupdates are enabled on the root partition. This was being triggered by sysinstall doing a forced unmount of devfs while node where still active. VFS has been fixed to deal with this better, and sysinstall has bee fixed to not do the forced unmount.
&footer; diff --git a/en/releases/5.3R/announce.sgml b/en/releases/5.3R/announce.sgml index c044fdf2f5..ae3e98d7e0 100644 --- a/en/releases/5.3R/announce.sgml +++ b/en/releases/5.3R/announce.sgml @@ -1,257 +1,260 @@ - + + %navincludes; %includes; ]> &header;

Date: Sat, 06 Nov 2004 16:19:57 -0700
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 5.3-RELEASE Announcement

It is my great pleasure and privilege to announce the availability of FreeBSD 5.3-RELEASE. This release marks a milestone in the FreeBSD 5.x series and the beginning of the 5-STABLE branch of releases. Some of the many changes since 5.2.1 include:

There has also been a significant focus on testing and bug-fixing with this release, as well as the freezing of most kernel and userland APIs. Users and vendors are encouraged to consider transitioning to it as FreeBSD 5.x is no longer considered a 'New Technology' release series. Information on migrating from FreeBSD 4.x to 5.x can be found at

http://www.FreeBSD.org/releases/5.3R/migration-guide.html

For a complete list of new features and known problems, please see the release notes and errata list, available at:

http://www.FreeBSD.org/releases/5.3R/relnotes.html
http://www.FreeBSD.org/releases/5.3R/errata.html

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng

Availability

FreeBSD 5.3-RELEASE supports the i386, pc98, alpha, sparc64, amd64, and ia64 architectures and can be installed directly over the net using bootable media or copied to a local NFS/FTP server. Distributions for all architectures are available now.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.3 based products:

If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 checksums for the release images are included at the bottom of this message.

Bittorrent

Bittorrent distribution is being tested on an experimental basis. A collection of trackers for the release ISO images is available at

http://people.freebsd.org/~scottl/5.3-torrent

FTP

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.3 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, Sandvine, Inc., FreeBSD Systems, Inc, and NTT/Verio.

The release engineering team for 5.3-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, I386 and AMD64 Release Building
Ken Smith <kensmith@FreeBSD.org> I386 and Sparc64 Release, Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation and Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org> IA64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Wilko Bulte <wilko@FreeBSD.org> Alpha Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer

CD Image Checksums

For Alpha:

MD5 (5.3-RELEASE-alpha-bootonly.iso) = 82fd65e9cfdb6431934d0f1c1b6a15a3
 MD5 (5.3-RELEASE-alpha-disc1.iso) = f7d2267e623be6e7409c119b46982061
 MD5 (5.3-RELEASE-alpha-disc2.iso) = 26ab899510752a05bf0019529b3ae09e
 MD5 (5.3-RELEASE-alpha-miniinst.iso) = 3cc9b2881ea519027fbec6f95ab2ea84

For amd64:

MD5 (5.3-RELEASE-amd64-bootonly.iso) = 3b13650ee101461d55233d2648402cfd
 MD5 (5.3-RELEASE-amd64-disc2.iso) = f35d3c6f46499ffab755ccf9b63cd558
 MD5 (5.3-RELEASE-amd64-miniinst.iso) = 1efce73bf26984feb6128518b225ad7e
 MD5 (5.3-RELEASE-amd64-disc1.iso) = 22894ae0c26f03537608d06815700148

For i386:

MD5 (5.3-RELEASE-i386-bootonly.iso) = e370ae39bb34f0789c638b6ad50038a2
 MD5 (5.3-RELEASE-i386-disc1.iso) = fbcbfdff31f27de396f257e0a37a78b8
 MD5 (5.3-RELEASE-i386-disc2.iso) = 21874a5663022768336e4cc73d1dd30d
 MD5 (5.3-RELEASE-i386-miniinst.iso) = 96124b2608ba481693e04d364d485e3c

For ia64:

MD5 (5.3-RELEASE-ia64-bootonly.iso) = 2e5dfceb79b2975885cab6b318c965b8
 MD5 (5.3-RELEASE-ia64-disc1.iso) = 61b5bc276bf2b75aed0908802ea12926
 MD5 (5.3-RELEASE-ia64-disc2.iso) = 02613e71ea7e04c43f75a8feccb0bdfa
 MD5 (5.3-RELEASE-ia64-miniinst.iso) = 709233fd711756966f298e31bcab4e45

For pc98:

MD5 (5.3-RELEASE-pc98-disc2.iso) = 373ddc67857b90b34190ad07a23e5298
 MD5 (5.3-RELEASE-pc98-miniinst.iso) = 01735af51f7b7f6ce37314e5ec49a842

For sparc64:

MD5 (5.3-RELEASE-sparc64-bootonly.iso)= db98df3d41cb20d6cdac668125736880
 MD5 (5.3-RELEASE-sparc64-disc1.iso) = cd960f33a4e4ae33628b28580900932a
 MD5 (5.3-RELEASE-sparc64-disc2.iso) = 058c9fce47fec044e6be91773532293a
 MD5 (5.3-RELEASE-sparc64-miniinst.iso)= 05eb044da17fda978f88716a8203be3d
+&footer; + diff --git a/en/releases/5.3R/errata_policy.sgml b/en/releases/5.3R/errata_policy.sgml index 7936ed9601..261190270b 100644 --- a/en/releases/5.3R/errata_policy.sgml +++ b/en/releases/5.3R/errata_policy.sgml @@ -1,54 +1,55 @@ - + + %navincludes; %includes; ]> &header;

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD &local.rel;.

Procedures

The Errata fixes will be applied by a member of the Release Engineering Team, coordinating the fix with the Security Officer who owns the branch. An Errata Notice will also be issued. The Release Engineering Team may choose to handle several Errata with one Errata Notice if several are being processed at roughly the same time.

Policy

Errata Candidates

The classification of things that are Errata candidates are things that are severe service-disrupting bugs for which there is no known work-around. Things like bugs in device drivers that impair their expected functionality, things that can cause kernel panics, etc.

Initial Patch

During the initial phases the fix for Errata should be handled exactly like any other fix. It should initially be committed to HEAD and go through the normal testing period there. The fix should then be MFCed as usual. At this point if you feel a fix is an Errata Notice candidate please contact the Release Engineering Team to make them aware of it.

The fix should then sit in RELENG_5 for one to two weeks. During this period please try to have the fix reviewed by another senior Developer familiar with the section of the code you are working with. You should also get confirmation that the fix solves the problem from someone who had reported the problem. Assuming no problems come up during this testing period then send in the formal request to re@FreeBSD.org. Please include the patch that will need to be applied to &local.rel; and who has reviewed the fix.

&footer; diff --git a/en/releases/5.3R/hardware.sgml b/en/releases/5.3R/hardware.sgml index d2f3b9bf7e..84de377466 100644 --- a/en/releases/5.3R/hardware.sgml +++ b/en/releases/5.3R/hardware.sgml @@ -1,31 +1,35 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.3R/installation.sgml b/en/releases/5.3R/installation.sgml index be0a7fab59..64aaea4771 100644 --- a/en/releases/5.3R/installation.sgml +++ b/en/releases/5.3R/installation.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.3R/policy.sgml b/en/releases/5.3R/policy.sgml index d51bf1e69b..55d8d6575a 100644 --- a/en/releases/5.3R/policy.sgml +++ b/en/releases/5.3R/policy.sgml @@ -1,146 +1,147 @@ - + + %navincludes; %includes; ]> &header;

Introduction

The following is the general policy for submitting and granting approvals for committing during the code freeze for FreeBSD &local.rel;. Flexibility will be granted when deemed appropriate by the Release Engineering Team. The ultimate purpose of this policy, however, is to minimize risks to the release process and help encourage good release engineering practices.

This policy applies to the BETA1 - BETA4, RC1 - RC2, and RELEASE release engineering cycles for the RELENG_5 and RELENG_5_3 branches. During the BETA cycle, the RELENG_5 branch will be frozen and under strict control of the Release Engineering team. The HEAD branch will be used to validate changes that are intended for this branch. Once the RELENG_5_3 branch is created, the RELENG_5 branch will become unfrozen and will be the validation ground for RELENG_5_3 changes. Changes should be committed to all branches in sequence as appropriate.

Procedures

When a branch is frozen by the release engineering team, all commits to it must be approved by the team. This applies also to release engineering team members as well as the rest of the developer community. In other words, approval is mandatory. This largely applies to the src/ tree, as ports/, doc/ and www/ tree management is handled separately by the ports and docs teams as appropriate.

To apply for a commit approval, a message must be sent to re@FreeBSD.org with the description of exactly what files need to change and why. Including a diff is encouraged, as is sending a copy of the commit message from the parent branch if appropriate. A response should usually be expected within 24 hours for less. Once approval is granted, the commit should be done as soon as possible. Approved commits may be canceled or overridden by the release engineering team if needed.

Blanket approvals are a special case that can be requested and granted in certain circumstances. With a blanket approval, the release engineering team is granting an individual the permission to do commits without specific approval in a well defined and controlled area of the tree. They are typically granted to those who are working on tier-2 and tier-3 platforms or on features that are not fully integrated into the tree. Blanket approvals are completely at the discretion of the release engineering team and may be revoked or suspended as needed.

Policy

Build fixes

These are defined as changes that fix source files, makefiles, or other build components so that the system can be compiled. This does not include bug fixes to tools or compilers except in rare circumstances. Build fixes must be committed to the parent branch first, if applicable, and be tested in all default build configurations. For kernel sources, this means testing on both GENERIC and LINT kernels. For userland sources, this means completing and installing the build of the 'world' target. For both userland and kernel sources, compiling on both 32-bit and 64-bit platforms is mandatory for machine-independent code. There is no minimum wait period for these fixes once testing is complete.

Bug fixes

These are defined as changes that fix incorrect behavior in an existing piece of code or subsystem in the src/ tree. All bugs must have a PR number, a review by a senior member of the project, and be vetted through the parent branch for at least 3 full days. We are often pressured to skirt the rules and put high-priority fixes in early, but we must resist that and rely on other tools like Perforce and diff/patch to get early testing before committing to the tree.

Documentation fixes

These are defined as changes to existing documentation in manual pages, release notes, and doc articles and books. This does not generally include comments in source files. Documentation fixes are classified into trivial and content fixes. Trivial fixes are defined as changes which do not need a technical review such as fixing a typo, wording, markup error, and so on. Content fixes are defined as ones which need a technical review, such as changes to the contents of documentation and build infrastructure.

Documentation fixes for the src/ tree

All changes must be committed to the parent branch first, vetted through that branch for 2 days. Content fixes must be sent with a PR number when the changes are large or involve one of the TODO items (these are periodically posted to the freebsd-doc@ mailing list during the release cycle, and should also be filed as PRs). When the changes are self-explaining, send them to re@ as an MFC request. Changes that are widespread or cover significant technical information should be reviewed without exception.

Documentation fixes for the doc/ tree

Similar policy is applied to the doc/ tree, but since doc/ is not branched and is not frozen, trivial fixes are allowed to be committed without explicit approval before BETA4. Content fixes must be committed with a PR number when the changes are large or involve one of the TODO items (these are periodically posted to the freebsd-doc@ mailing list during the release cycle, and should also be filed as PRs). When the changes are self-explaining, you can commit them into the doc/ tree. When you are not sure if committing your patch without approval is reasonable or not, please ask doceng@. Documentation Engineering Team reserves the right to reject and back out your change. After BETA4, doc/ slush begins and non-critical changes to English documents are discouraged.

Translations

The above two policies also apply to translations, but all changes are considered as trivial changes during the period before the doc/ slush is over.

Feature additions and modifications

These are defined as changes that add new features to the system or significantly change or improve existing features and behaviors, but are not strictly bug fixes. These will only be considered for inclusion if prior notice is given to the re@ and arch@ mail aliases and the work is publically available in either patch form or in the FreeBSD Perforce repository. We reserve the right to reject feature requests based on risk to stability and risk to the published release schedule. Those that are allowed need at least 7 days in the parent branch and a thorough review by at least two parties. Mitigation of risk is highly important here, so developers are highly encouraged to make their work be modular and able to be removed or turned off to restore previous behavior. Feature additions will not be allowed after BETA4.

Performance improvements

These are defined as changes that are designed to optimize performance in a measurable way. Any proposal here must be accompanied by documented performance and regression testing on all affected arches. On arches with a clear runtime distinction between UP and SMP, the testing must include both. Thorough review by two or more senior people is also a firm requirement. Performance improvements will not be allowed after BETA3.

&footer; diff --git a/en/releases/5.3R/relnotes.sgml b/en/releases/5.3R/relnotes.sgml index 1ab60ec6b7..161d3c12af 100644 --- a/en/releases/5.3R/relnotes.sgml +++ b/en/releases/5.3R/relnotes.sgml @@ -1,30 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.3-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ &footer; + + diff --git a/en/releases/5.3R/schedule.sgml b/en/releases/5.3R/schedule.sgml index 69a12393ee..d9d5824ff1 100644 --- a/en/releases/5.3R/schedule.sgml +++ b/en/releases/5.3R/schedule.sgml @@ -1,286 +1,287 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public FreeBSD-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

FreeBSD &local.rel; will be the first release from the RELENG_5 branch and thus will also be the first 5-STABLE release.

The current release engineering TODO list is also available. This list is updated periodically through the release cycle.

Schedule

- +
Action Expected Actual Description
Announce the Ports Freeze 15 Aug 2004 15 Aug 2004 Someone from portmgr@ should email for the two week long ports freeze and tagging of the ports tree.
src/ tree frozen 16 Aug 2004 16 Aug 2004 Announce the src/ code freeze for &local.rel;. Commits to the HEAD branch will be locked until the RELENG_5 branch is created.
RELENG_5 branch creation 16 Aug 2004 17 Aug 2004 Create the RELENG_5 branch. Commits to this branch will require Release Engineering approval until the RELENG_&local.rel.tag; branch is created.
Begin &local.rel;-BETA1 builds 16 Aug 2004 20 Aug 2004 Begin building &local.rel;-BETA1 disc1 and disc2 for all Tier-1 platforms. The first built typically requires several days to resolve latent problems on all platforms, so it will be started early.
Release &local.rel;-BETA1 20 Aug 2004 22 Aug 2004 &local.rel;-BETA1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Build and release &local.rel;-BETA2 27 Aug 2004 29 Aug 2004 &local.rel;-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Build and release &local.rel;-BETA3 3 Sep 2004 5 Sep 2004 &local.rel;-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree frozen 3 Sep 2004 3 Sep 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Build and release &local.rel;-BETA4 10 Sep 2004 12 Sep 2004 &local.rel;-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Build and release &local.rel;-BETA5 17 Sep 2004 20 Sep 2004 &local.rel;-BETA5 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged 17 Sep 2004 11 Oct 2004 RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen 17 Sep 2004 11 Oct 2004 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts 17 Sep 2004 11 Oct 2004 The ports cluster and pointyhat build final packages.
Turn off debugging for RELENG_5 17 Sep 2004 7 Sep 2004 Turn off WITNESS, INVARIANTS, and malloc debugging options. This will be the default for all RELENG_5 releases.
doc/ tree slush 17 Sep 2004 17 Sep 2004 Announce the doc/ slush for &local.rel;. From this time until the tagging of the doc/ tree, non-critical changes should be postponed to allow translation teams time to finish their work for the release. If we can resolve problems before this expected date, doc/ slush could start earlier. At this point, we are considering on 10 Sep at earliest, and on 17 Sep at latest.
Build and release &local.rel;-BETA6 24 Sep 2004 26 Sep 2004 &local.rel;-BETA6 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged 24 Sep 2004 26 Sep 2004 Tag the doc/ tree with RELEASE_&local.rel.tag;_0.
Build and release &local.rel;-BETA7 1 Oct 2004 3 Oct 2004 &local.rel;-BETA7 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
RELENG_&local.rel.tag; branched 8 Oct 2004 16 Oct 2004 Branch of src/ from RELENG_5 for the release.
src/ unfrozen 8 Oct 2004 16 Oct 2004 Unfreeze RELENG_5 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Build and release &local.rel;-RC1 17 Oct 2004 19 Oct 2004 &local.rel;-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Version numbers bumped 22 Oct 2004 24 Oct 2004 The files listed here are updated to reflect FreeBSD &local.rel;.
src/ tree tagged 22 Oct 2004 24 Oct 2004 Tag the RELENG_&local.rel.tag; branch with RELENG_&local.rel.tag;_0_RELEASE.
Begin &local.rel;-RELEASE builds 5 Nov 2004 4 Nov 2004 Start &local.rel;-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org 5 Nov 2004 5 Nov 2004 Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master 5 Nov 2004 6 Nov 2004 Release and packages uploaded to ftp-master.FreeBSD.org.
FreeBSD &local.rel; Announced 5 Nov 2004 6 Nov 2004 FreeBSD &local.rel; is announced to the mailing lists.
FreeBSD &local.rel; Press Release 5 Nov 2004 6 Nov 2004 A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications.
&footer; diff --git a/en/releases/5.3R/todo.sgml b/en/releases/5.3R/todo.sgml index 97a1a99b0f..c724fb2a0c 100644 --- a/en/releases/5.3R/todo.sgml +++ b/en/releases/5.3R/todo.sgml @@ -1,637 +1,638 @@ - + + %navincludes; %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 5.3. If you have any updates for this list, please e-mail re@FreeBSD.org.

Issues that require investigation

- +
IssueStatusResponsibleDescription

Show stopper defects for 5.3-RELEASE

- +
IssueStatusResponsibleDescription

Required features for 5.3-RELEASE

- +
IssueStatusResponsibleDescription

Desired features and bugfixes for 5.3-RELEASE

- +
IssueStatusResponsibleDescription
Reports of poor performance with the if_re driver (re ethernet interfaces) &status.wip; &a.jmg; There have been reports that specific gigabit ethernet cards supported by the if_re driver are experiencing poor performance; a patch has been posted that corrects timer and interrupt problems with the driver, and is believed to correct the performace problems. The patch will be merged to 6.x and 5.x shortly.
GDB thread support &status.wip; &a.davidxu;, &a.marcel; With improved support for threading primitives, support is now required to ease debugging of threaded applications. Ideally, this support will work for both libthr and libkse threading models.
KSE support for sparc64 &status.wip; &a.kensmith; Kernel bits implemented, userland not implemented.
truss support for ptrace -- -- Almost all process debugging tools have been updated to use non-procfs kernel primitives, with the exception of truss(1). As procfs is considered deprecated due to its inherent security risks, it is highly desirable to update truss to operate in a post-procfs world. &a.des; had prototype patches; &a.robert; is developing and testing patches now. Support for system call tracing has been added to ptrace().
FAST_IPSEC and KAME compatibility &status.new; -- FAST_IPSEC currently cannot be used directly with the KAME IPv6 implementation, requiring an additional level of IP tunnel indirection to protect IPv6 packets when using hardware crypto acceleration. This issue must be resolved so that the two services may more easily be used together. Among other things, this will require a careful review of the handling of mbuf header copying and m_tag support in the KAME IPv6 code.
rpc.lockd(8) stability -- -- A process cannot be interrupted while waiting on a lock. Fixing this requires that the RPC code be taught how to deal with lock cancellation and interruption events.
Revised kld build infrastructure &status.new; &a.peter; Kernel modules are currently built independently from a kernel configuration, and independently from one another, resulting in substantially redundant compilation of objects, as well as the inability to easily manage compile-time options for kernel objects (such as MAC, PAE, etc) that may require conditional compilation in the kernel modules. In order to improve build performance and better support options of this sort, the KLD build infrastructure needs to be revamped. &a.peter; has done some initial prototyping, and should be contacted before starting on this work.
Race conditions in truss Errata candidate &a.robert; Truss appears to contain a race condition during the start-up of debugging, which can result in truss failing to attach to the process before it exits. The symptom is that truss reports that it cannot open the procfs node supporting the process being debugged. A bug also appears to exist where in truss will hang if execve() returns ENOENT. A further race appears to exist in which truss will return "PIOCWAIT: Input/output error" occasionally on startup. The fix for this sufficiently changes process execution handling that we will defer the fix to post-5.0 and consider this errata.
filedesc LOR &status.new; -- The LOR reported in PR kern/55175 needs to be fixed. Filedesc locking needs to be heavily reviewed in general.
KSE support for alpha &status.wip; &a.marcel; Userland bits implemented, kernel bits not implemented.
CAM locking &status.wip; &a.scottl;, &a.gibbs; For kernel API/ABI compatibility reasons, it would be desirable to have the CAM locking strategy determined and loosely implemented for 5.3.
syscons not working on Sparc64 Ultra-30 &status.new; -- When running syscons on an Ultra-30 with Creator-3D typing characters on the keyboard produces garbage. Problem reported by &a.kris;. Debugging difficult due to lack of this particular configuration among developers and problem isn't present on similar hardware (e.g. no problem on Ultra-60 w/Creator-3D).

Documentation items that must be resolved for 5.3

- +
IssueStatusResponsibleDescription
i386 Floppy Installation Docs &status.done; Gavin Atkinson, &a.bmah; The installation documentation doesn't take into account the new floppy images (with a full kernel split across multiple disks). This should be updated.
References:
docs/70485 (closed)
Finish hardware notes trimming &status.done; &a.simon;, &a.brueffer; Finish removing mention of individual devices in the hardware notes and use auto-generated lists, based on driver manual pages, instead.
sound(4) related manual pages &status.done; &a.simon; The snd(4) and pcm(4) drivers have been renamed but their manual pages are still outdated. sound(4) has to be added and pcm(4), csa(4), gusc(4), sbc(4), and uaudio(4) should be revised. Other manual pages which refer to pcm(4) (if any) should possibly be revised, too. In addition, supported cards list needs to be updated.
References:
Manpage for snd_solo on -doc@
[PATCH] sound(4) related manpages 5.3 TODO item on -doc@
src/share/man/man4/Makefile rev.1.279
Sound section in the Handbook &status.done; &a.blackend; This section is outdated, some rewrites are needed for 5.3-RELEASE.
References:
doc/en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml rev.1.94
FDP documentations related pcm(4) &status.new; -- With the snd(4) and pcm(4) drivers changes, documentations (FAQ) regarding the use of these drivers need an update.
Early Adopter's Guide &status.done; &a.bmah;, &a.trhodes; Xin LI pointed out that FreeBSD 5.3-RELEASE is the first stable release on 5.X and it is (hopefully) not for early adopters. Early Adopter's Guide is still useful, but contains a bit old information. Some parts of this guide need a rewrite, and this document should be published as "4.X to 5.X Migration Guide", which focuses difference between 4.X and 5.X.
References:
Draft for review
discussion on -doc@ and -current@
Installation Notes &status.new; &a.trhodes; Some parts are outdated. doc/70485 has been committed, but more work is needed to reflect the realities. bmah@ pointed out that we should have "quick-start" installation guide for each platform instead of the current ones because they become too long and difficult to be maintained.
References:
doc/70485 (closed)
Xorg &status.done; Ken Tom, &a.blackend; Update the X11 chapter of the Handbook for X.Org's X11 server.
References:
books/handbook/config/chapter.sgml rev.1.147
rc.d scripts &status.done; &a.trhodes; Ch.11.4 and 11.5 of the Handbook must be updated to mention the new rc.d scripts and some ports use /etc/rc.conf for their configuration.
References:
books/handbook/config/chapter.sgml rev.1.170
books/handbook/config/chapter.sgml rev.1.172
Handbook's kernel configuration chapter &status.done; &a.ceri; Chapter 8 must be updated to match 5.3-RELEASE.
References:
docs/70674 (closed)
books/handbook/kernelconfig/chapter.sgml rev.1.135
Handbook's IPsec section &status.new; -- Some parts of Section 14.10 are outdated and are not correct for 5.X systems.
References:
ipsec on -doc@
Problem with IPSEC in handbook on -doc@
Handbook's Vinum chapter &status.new; -- Vinum chapter needs to be revised for 5.X systems.

Testing focuses for 5.3-RELEASE

- +
IssueStatusResponsibleDescription
KSE as the default threads library &status.untested; &a.davidxu;, &a.deischen; KSE has matured to the point of being more stable and POSIX-compliant than the traditional libc_r. All Tier-1 platforms MUST have stable KSE support for 5.3 in order to support a consistent transition. Additionally, all ports that depend on the pthreads API must be modified to properly detect and support the default threading library.
Updated binutils for all platforms &status.untested; &a.obrien; Binutils needs updating in order to support new platforms, newer GDB versions, and Thread Local Storage.
gcc 3.3 floating point alignment regression &status.untested;   The previous GCC 3.3 snapshot included regressions in alignment of floating point arguments, resulting in a substantial performance degradation. The recent GCC 3.4.2 import should fix this, but more testing is needed.
in6_pcbnotify() panic with TCP &status.done; &a.rwatson; &a.kuriyama; has reported a failed locking assertion with IPv6 TCP notifications. This problem is believed to be corrected.
Per-platform Thread-Local Storage &status.untested; &a.dfr;, &a.marcel; To complete support for thread-local storage on FreeBSD, per-architecture changes must be made. Currently pending platforms are amd64, alpha, ia64, i386, sparc64, and powerpc.
SMP instability under load &status.untested; &a.dwhite;, &a.alc; High load on SMP systems appears to result in a hard hang related to VM IPI. &a.dwhite; has prepared a candidate patch that appears to resolve this instability, which is currently in testing for merge to the CVS HEAD.
Fine-grained network stack locking without Giant &status.untested; &a.rwatson; Significant parts of the network stack (especially IPv4, UNIX domain IPC, and sockets) now have fine-grained locking of their data structures. It's possible to run many common network subsystems and services without the Giant lock. However, a number of device drivers and less mainstream network subsystems are currently not MPSAFE. 5.3 betas have shipped with Giant-free networking by default, with some bug reports and fixes in later betas and release candidates. Please report any problems to the current@ mailing list.
kld support for amd64 &status.untested; &a.obrien;, &a.iedowse; KLDs work when loaded from userland, but not from the loader. kldxref and loader support has been committed to HEAD and RELENG_5 and needs final testing.
ATA panics under sparc64 &status.untested; &a.sos;, &a.scottl; Recent changes to the ATA driver trigger a bug on sparc64 that causes a panic on boot. This was caused by bugs in busdma that have been hopefully fixed.
ifconf() sleep warning &status.done; &a.brooks; The ifconf() ioctl for listing network interfaces performs a copyout() while holding the global ifnet list mutex. This generates a witness warning in the event that copyout() generates a page fault, and risks more serious problems. This problem is believed to be corrected.
poll()/select() application wedge reports with debug.mpsafenet=1 &status.done; &a.rwatson; There are reports of applications wedging in poll() and select() while running the network stack without the Giant lock. A recent sleepq change appears to have caused some of the observed problems to go away (others are difficult to test for due to recent SMP instability). This problem appears to be corrected.
if_em wedging under high pps &status.done; &a.mlaier; There have been several reports of if_em cards "wedging" under high packets-per-second load. This problem appears to have been corrected.
Panic on USB detach &status.untested &a.imp;, &a.scottl; A recent regression in the USB code is causing panics when a USB device detaches, especially USB hubs. A fix is in RELENG_5 now.
KAME IPSEC "ENOBUFS" problem with racoon and mbuma &status.done; &a.rwatson;, &a.sam; There are reports that racoon is unable to complete IKE negotiation due to a send to the pfkey socket returning ENOBUFS. This appears to be a result of an incorrect assumption about mbuf data size due to a change resulting from mbuma. This problem appears to have been corrected.
BIND9 import into 5-CURRENT &status.done; &a.dougb;, &a.des;, &a.trhodes; BIND9 is now in RELENG_5 and HEAD. Testing is needed of basic functionality, migration from 8.x, and 3rd party packages in the ports tree.
Synaptics touchpad problems &status.untested; &a.philip; Synaptics updates to the psm(4) driver have resulted in poor interactivity for taps and button press events for some users. Support is now disabled by default but work will procede to fix the underlying problems.
Scheduler-related hangs involving threads &status.untested; &a.scottl;, &a.julian; Significant work has happened in the scheduler to fix stability problems. More testing for UP and SMP under heavily load is needed.
NFS over IPv6 problems &status.done; &a.dwhite; &a.kuriyama; has reported problems with NFS over IPv6 not functioning correctly as of the improved NFS support for disconnection changes. &a.dwhite; has tracked down the source of the problem (EMSGSIZE being returned by IPv6 UDP send routine due to fragmentation), and is currently exploring possible fixes. This problem appears to have been corrected.
Reports of socket buffer corruption in tcp_output() &status.done; &a.rwatson; There have been reports of occasional corruption of socket buffers. This may have been the result of missing socket buffer locking in tcp_output(), which has now been corrected in 6.x and 5.x; this problem is believed to be fixed.
Reports of hangs using i4b (isdn4bsd) &status.done; &a.rwatson; There have been reports of system hangs while using ISDN with the i4b ISDN framework on SMP systems. These likely result from insufficient synchronization in the i4b implementation when runnning without the Giant lock over the network stack. The workaround until this is fixed is to re-assert the Giant lock over the stack when i4b is compiled into the kernel; this has been committed to 6.x and and 5.x. This problem appears to have been corrected.
Problems with multicast and setuid binaries/daemons &status.done; &a.rwatson;, &a.csjp; There have been reports that multicast socket options on raw sockets no longer work properly with daemons changing privilege or setuid binaries. These symptoms have been tracked down to bugs relating to permitting limited use of raw sockets in jail(). A patch correcting these problems has been merged to 6.x and 5.x. This problem appears to have been corrected.
Reports of sodealloc() panic under heavy load &status.done; &a.rwatson;, &a.green; There have been reports of a so_count invariant violation in sofree(), which may relate to race conditions in sofree() against accept(), which were recently corrected in 6.x, and has been merged to 5.x. This problem appears to have been corrected.
Merge of Darwin msdosfs, other fixes &status.done; -- Apple's Darwin operating system has fairly extensive improvements to msdosfs and other kernel services; these fixes must be reviewed and merged to the FreeBSD tree.
Reports of poor performance of the if_de driver (de ethernet interfaces) &status.done; &a.rwatson;, &a.jmg; There have been reports that if_de ethernet cds behave poorly when running with debug.mpsafenet=1, even though the driver is marked to run all portions with the Giant lock. This suggests a race condition specific to this drive, which is currently being debugged. A patch has been committed to the 6.x and 5.x branches, and appears to correct the problem.
Threaded application get stuck in an unkillable state when touched by GDB &status.done; &a.davidxu; Attaching GDB to a threaded process will leave the process in an unkillable state. Rebooting the machine is the only way to recover from this. This is easily triggered when a KDE app crashes and KDE automatically attaches GDB to it to extract a stack trace. A candidate fix is in 6-CURRENT. More testing and review is needed.
More truss problems &status.done; &a.alfred; Truss appears to have another problem. It is repeatable by running "truss -f fsck -p /", suspending it with ^Z, and then killing truss. It will leave behind the fsck processes which will be unkillable.
Reports of TCP-related instability under extremely high load; possibly related to SACK &status.untested; &a.gnn;, &a.rwatson;, &a.scottl There have been reports that, under extremely high load, the tcp_output() routine may appear to run for extended periods, resulting in the appearance of a hang for an extended period (up to 30 minutes), followed by recovery. A fix for SACK was developed and committed that hopefully corrects this problem.
&footer; diff --git a/en/releases/5.4R/announce.sgml b/en/releases/5.4R/announce.sgml index 160296f350..694842eecb 100644 --- a/en/releases/5.4R/announce.sgml +++ b/en/releases/5.4R/announce.sgml @@ -1,269 +1,272 @@ - + + %navincludes; %includes; ]> &header;

Date: Mon, 9 May 2005 17:01:58 -0400
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 5.4-RELEASE Announcement

The Release Engineering Team is happy to announce the availability of FreeBSD 5.4-RELEASE, the latest release of the FreeBSD Stable development branch. Since FreeBSD 5.3-RELEASE in November 2004 we have made many improvements in functionality, stability, performance, and device driver support for some hardware, as well as dealt with known security issues and made many bugfixes.

For a complete list of new features, known problems, and late-breaking news, please see the release notes and errata list, available here:

http://www.FreeBSD.org/releases/5.4R/relnotes.html

http://www.FreeBSD.org/releases/5.4R/errata.html

FreeBSD 5.4 will become an "Errata Branch". In addition to Security fixes other well-tested fixes to basic functionality will be committed to the RELENG_5_4 branch after the release. Both Security Advisories and Errata Notices are announced on the freebsd-announce@freebsd.org mailing list.

It is expected there will be at least one more release from the RELENG_5 branch, most likely two. The current plans are for the RELENG_6 branch to be created within the next few months, and an initial 6.0-RELEASE will be made a few months afterwards. There will be a 5.5-RELEASE following a few months after the 6.0-RELEASE.

For more information about FreeBSD release engineering activities, please see:

http://www.FreeBSD.org/releng/

Dedication

The FreeBSD 5.4 Release is dedicated to the memory of Cameron Grant. Cameron was an active FreeBSD Developer and principal architect of the sound driver subsystem despite his physical handicap. His is a superb example of human spirit dominating over adversity. Cameron was an inspiration to those who met him; he will be fondly remembered and sorely missed.

Availability

FreeBSD 5.4-RELEASE supports the i386, amd64, ia64, pc98, sparc64, and alpha architectures and can be installed directly over the net, using bootable media, or copied to a local NFS/FTP server. Distributions for all architectures except alpha are available now. The distribution for alpha should become available within the next day or two.

Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.4 based products:

If you can not afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can not promise that all the mirror sites will carry the larger ISO images. At the time of this announcement they are available from the following sites. MD5 checksums for the release images are included at the bottom of this message.

Bittorrent

As with the 5.3 release we are experimenting with Bittorrent. A collection of trackers for the release ISO images is available at

http://people.freebsd.org/~kensmith/5.4-torrent/

FTP

At the time of this announcement the following FTP sites have FreeBSD 5.4-RELEASE available.

FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Austria, Brazil, Canada, China, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland, Indonesia, Ireland, Italy, Japan, Korea, Lithuania, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russia, Saudi Arabia, Singapore, Slovak Republic, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Turkey, Ukraine, United Kingdom, and the United States.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Acknowledgments

The FreeBSD Developers deserve the most thanks. Without their efforts FreeBSD would not exist.

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.4 including The FreeBSD Mall, Hewlett Packard, Yahoo!, Sentex Communications, Sandvine, Inc., FreeBSD Systems, Inc, and NTT/Verio.

The release engineering team for 5.4-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Doug White <dwhite@FreeBSD.org> Release Engineering
Murray Stokely <murray@FreeBSD.org> Release Engineering, Documentation
Wilko Bulte <wilko@FreeBSD.org> Alpha Release Building
Marcel Moolenaar <marcel@FreeBSD.org> ia64 Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org> pc98 Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Jacques A. Vidrine <nectar@FreeBSD.org> Security Officer
Paul Saab <ps@FreeBSD.org> Bittorrent Coordination

CD Image Checksums

   MD5 (5.4-RELEASE-amd64-bootonly.iso) = 6882dd5ce59cda1ba4a66ef45f017597
   MD5 (5.4-RELEASE-amd64-disc1.iso) = 26bca75d799c0a1690c6ae0bf0886234
   MD5 (5.4-RELEASE-amd64-disc2.iso) = 3da9debeae15a49158b01b1d92843fbc
 
   MD5 (5.4-RELEASE-i386-bootonly.iso) = 2afe65af7e7b994c3ce87cefda27352e
   MD5 (5.4-RELEASE-i386-disc1.iso) = 3dbb37485535e129354bc099e24aed99
   MD5 (5.4-RELEASE-i386-disc2.iso) = e4b748415ca783fce64cfafd6bd56f57
 
   MD5 (5.4-RELEASE-ia64-bootonly.iso) = 45b032bf952e7ea8b2c42f94c3fa4997
   MD5 (5.4-RELEASE-ia64-disc1.iso) = 2b1ad22da2ea0fe86345c99590049ebd
   MD5 (5.4-RELEASE-ia64-disc2.iso) = 62e589928628453f1813db7402b4f3ad
   MD5 (5.4-RELEASE-ia64-livefs.iso) = 6c05d71c36d84179923668faddf58e43
 
   MD5 (5.4-RELEASE-pc98-disc1.iso) = 003dee8647e9b2cbca7df0d92011800f
 
   MD5 (5.4-RELEASE-sparc64-bootonly.iso) = 91cb2304c2ecbcce0b312738649ba88d
   MD5 (5.4-RELEASE-sparc64-disc1.iso) = 5f77c9a20e09d5ef66fad9c60e17c2ac
   MD5 (5.4-RELEASE-sparc64-disc2.iso) = 7da34a32ca8196a34732548fe92d71e6
+&footer; + diff --git a/en/releases/5.4R/errata_policy.sgml b/en/releases/5.4R/errata_policy.sgml index 7c34520e11..d9081894e5 100644 --- a/en/releases/5.4R/errata_policy.sgml +++ b/en/releases/5.4R/errata_policy.sgml @@ -1,54 +1,55 @@ - + + %navincludes; %includes; ]> &header;

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD &local.rel;.

Procedures

The Errata fixes will be applied by a member of the Release Engineering Team, coordinating the fix with the Security Officer who owns the branch. An Errata Notice will also be issued. The Release Engineering Team may choose to handle several Errata with one Errata Notice if several are being processed at roughly the same time.

Policy

Errata Candidates

The classification of things that are Errata candidates are things that are severe service-disrupting bugs for which there is no known work-around. Things like bugs in device drivers that impair their expected functionality, things that can cause kernel panics, etc.

Initial Patch

During the initial phases the fix for Errata should be handled exactly like any other fix. It should initially be committed to HEAD and go through the normal testing period there. The fix should then be MFCed as usual. At this point if you feel a fix is an Errata Notice candidate please contact the Release Engineering Team to make them aware of it.

The fix should then sit in RELENG_5 for one to two weeks. During this period please try to have the fix reviewed by another senior Developer familiar with the section of the code you are working with. You should also get confirmation that the fix solves the problem from someone who had reported the problem. Assuming no problems come up during this testing period then send in the formal request to re@FreeBSD.org. Please include the patch that will need to be applied to &local.rel; and who has reviewed the fix.

&footer; diff --git a/en/releases/5.4R/hardware.sgml b/en/releases/5.4R/hardware.sgml index 305b624756..096811371f 100644 --- a/en/releases/5.4R/hardware.sgml +++ b/en/releases/5.4R/hardware.sgml @@ -1,30 +1,35 @@ - + + %navincludes; %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.

Hardware notes for FreeBSD 5.4-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ + &footer; + + diff --git a/en/releases/5.4R/installation.sgml b/en/releases/5.4R/installation.sgml index 2cfe1fa7f6..309891cebe 100644 --- a/en/releases/5.4R/installation.sgml +++ b/en/releases/5.4R/installation.sgml @@ -1,29 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.

Installation notes for FreeBSD 5.4-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ + &footer; + + diff --git a/en/releases/5.4R/relnotes.sgml b/en/releases/5.4R/relnotes.sgml index b57b64fb78..fcd80748de 100644 --- a/en/releases/5.4R/relnotes.sgml +++ b/en/releases/5.4R/relnotes.sgml @@ -1,29 +1,34 @@ - + + %navincludes; %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 5.4-RELEASE are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

+ + &footer; + + diff --git a/en/releases/5.4R/schedule.sgml b/en/releases/5.4R/schedule.sgml index 4a13d0947b..fe2c4cfb99 100644 --- a/en/releases/5.4R/schedule.sgml +++ b/en/releases/5.4R/schedule.sgml @@ -1,333 +1,334 @@ - + + %navincludes; %includes; ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. For more general information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- +
Action Expected Actual Description
Reminder announcement 31 Jan 2005 31 Jan 2005 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD &local.rel; release.
Announce the Ports Freeze 24 Feb 2005 24 Feb 2005 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
&local.rel;-PRERELEASE 23 Feb 2005 24 Feb 2005 newvers.sh updated.
Code freeze begins 2 Mar 2005 3 Mar 2005 After this date, all commits to the RELENG_5 branch must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers, as well as stable@ and qa@ lists.
&local.rel;-PRERELEASE
&local.rel;-BETA1		 4 Mar 2005 20 Mar 2005 First public test release build. Note that the release build name is &local.rel;-BETA1 but newvers.sh RELEASE name remains &local.rel;-PRERELEASE. This is because the name BETA often confuses the users who are using the STABLE branch.
Announce doc/ tree slush 14 Mar 2005 25 Mar 2005 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen 21 Mar 2005 21 Mar 2005 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush 24 Mar 2005
2 Apr 2005		 2 Apr 2005
Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
doc/ tree tagged. 28 Mar 2005
11 Apr 2005		 12 Apr 2005 Version number bumps for doc/ subtree. RELEASE_&local.rel.tag;_0 tag for doc/. doc/ slush ends at this time.
RELENG_&local.rel.tag; branch 31 Mar 2005 3 Apr 2005 The release branch is created. Update newvers.sh and release.ent on various branches involved.
Unfreeze the tree 31 Mar 2005 3 Apr 2005 Announcement to developers explaining that commits to RELENG_5 no longer require approval. Also note the policy for commits to the RELENG_&local.rel.tag; branch.
&local.rel;-RC1 31 Mar 2005 3 Apr 2005 newvers.sh and release.ent updated.
Ports tree tagged 31 Mar 2005 2 Apr 2005 RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen 31 Mar 2005 2 Apr 2005 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts 31 Mar 2005 -- The ports cluster and pointyhat build final packages.
First release candidate 2 Apr 2005 5 Apr 2005 The first release candidate for the each architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks.
Heads up to -stable 2 Apr 2005 5 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate 9 Apr 2005 9 Apr 2005 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable 9 Apr 2005 11 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded.
Third release candidate 16 Apr 2005 16 Apr 2005 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable 16 Apr 2005 18 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Fourth release candidate 30 Apr 2005 2 May 2005 Note: This is the final release candidate.
Heads up to -stable 1 May 2005 2 May 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the fourth snapshot is uploaded.
Version numbers bumped. 6 May 2005 6 May 2005 The files listed here are updated to reflect the fact that this is FreeBSD &local.rel;.
src tree tagged. 6 May 2005 6 May 2005 RELENG_&local.rel.tag;_0_RELEASE tag for src/.
Final builds. 6 May 2005 6 May 2005 Final builds for all architectures in a pristine environment.
Warn mirror-announce@FreeBSD.org 6 May 2005 6 May 2005 Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs.
Upload to ftp-master. 7 May 2005 -- Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long)
Update man.cgi on the website. 9 May 2005 -- Make sure the &local.rel; manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.sgml.
Announcement 9 May 2005 -- Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam 17 May 2005 -- RELENG_&local.rel.tag; branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information

&footer; diff --git a/en/releases/5.4R/todo.sgml b/en/releases/5.4R/todo.sgml index aa4dcc4dca..6c4924b3a9 100644 --- a/en/releases/5.4R/todo.sgml +++ b/en/releases/5.4R/todo.sgml @@ -1,260 +1,261 @@ - + + %navincludes; %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is the beginning of a list of open issues that need to be worked on or resolved for FreeBSD 5.4. If you have any updates for this list, please e-mail re@FreeBSD.org. The feature list for 5.4 is still a work in progress, so items may be added, removed, or modified before we're done.

Show stopper defects for 5.4-RELEASE

- +
Issue Status Responsible Description

Required features for 5.4-RELEASE

- +
Issue Status Responsible Description

Desired features for 5.4-RELEASE

- +
Issue Status Responsible Description
KAME IPSEC without the Giant Lock &status.wip; &a.gnn; Currently, the KAME IPSEC implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with the KAME IPSEC implementation (not FAST_IPSEC) to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for KAME IPSEC so that it can run without the Giant lock.
All Network Interface Drivers MPSAFE &status.wip; -- Currently, some network interface drivers are not safe without the Giant lock due to missing synchronization. These drivers are protected by running non-INTR_MPSAFE and with the IFF_NEEDSGIANT flag set, which cause interrupt threads to acquire the Giant lock before executing the driver's interrupt handler, and to perform if_start (interface transmit start) asynchronously once the Giant lock can be acquired. This results in these drivers performing less well due to increased lock contention, decreased ability to preempt, and latency associated with asynchronous launching of latency-critical events. For 5.4, all network drivers should be able to operate without the Giant lock.
NetIPX without the Giant Lock &status.wip; &a.rwatson; Currently, the IPX/SPX (netipx) implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with IPX support to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for IPX so that it can run without the Giant lock.
Fix regression in file(1) -- -- The new version of file(1) does not cross-build properly. If sparc64 executables are built on i386 the compiled magic numbers file that gets installed is wrong and file(1) doesn't work properly.
SIGABRT under load &status.wip; &a.alc; Under very high load (Kris sees this on the package builders) a limitation of 16 sumultaneous exec's may be hit in exec_map(). A workaround has been implemented with a fix planned for 5.5.
DDB_UNATTENDED may not work &status.new; -- There are reports of problems getting dumps after panics.
fix for ttywakeup panic &status.wip; &a.dwhite; There appears to be a race condition opening/closing ttys.

Documentation items that must be resolved for 5.4

- +
Issue Status Responsible Description

Testing focuses for 5.4-RELEASE

- +
Issue Status Responsible Description
File descriptor locking &status.done; &a.jeff; File descriptor locking needs to be merged back from HEAD.
IPFilter mpsafe fixes &status.done; &a.rwatson; IPFilter is currently not mpsafe but doesn't run with Giant.
Update sysinstall to handle separate packages CD &status.done; &a.jhb; Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11
busdma fixes &status.done; &a.scottl; More work is needed on busdma to fix bounce buffer problems.
AMR driver MPSAFE &status.done; &a.scottl; Making the AMR driver MPSAFE will greatly increase its performance.
CARP support &status.done; &a.glebius; Common Address Redundancy Protocol allows multiple hosts on the same local network to share a set of IP addresses.
kstack overflows in softupdates &status.done; -- There had been reports of kernel stack overflows in softupdates code that caused filesystem problems on reboot. This was fixed during the early stage of code freeze but should be tested.
ATAPI CDROMs in PIO mode during install &status.done; &a.kensmith; People are having difficulties with various ATAPI CDROMs on various architectures. We need to either do all installs in PIO mode or provide a boot menu method of selecting it.
truss not working &status.done; &a.jeff; See PR kern/78664.
Deadlock under heavy interrupt load on MP Opteron systems &status.done; &a.dwhite; A deadlock related to delivering IPIs on AMD 64-bit processors has been identified.
SCHED_ULE update &status.done; &a.jeff; Many improvements have been made to the ULE scheduler in 6-CURRENT. These should be merged back to 5.4. The merging is done but ULE is still known to cause panics for some people, especially on SMP systems. Try it with extreme caution.
&footer;