diff --git a/website/content/en/releases/4.10R/announce.html b/website/content/en/releases/4.10R/announce.html index 6d46844725..13832c55a6 100644 --- a/website/content/en/releases/4.10R/announce.html +++ b/website/content/en/releases/4.10R/announce.html @@ -1,458 +1,458 @@ FreeBSD 4.10-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10-RELEASE Announcement

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

I am happy to announce the availability of FreeBSD 4.10-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/4.10R/relnotes.html

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

FreeBSD 4.10 will become the first "Errata Branch". Release branches for previous versions of FreeBSD would only have critical security fixes applied. With FreeBSD 4.10 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 4.10-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 4.10 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 4.10 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 4.10-RELEASE includes:

- - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + +
Scott Long <scottl@FreeBSD.org>Release Engineering, Alpha Release BuildingScott Long <scottl@FreeBSD.org>Release Engineering, Alpha Release Building
Bruce A. Mah <bmah@FreeBSD.org>Release Engineering, DocumentationBruce A. Mah <bmah@FreeBSD.org>Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org>Release Engineering, SecurityRobert Watson <rwatson@FreeBSD.org>Release Engineering, Security
John Baldwin <jhb@FreeBSD.org>Release EngineeringJohn Baldwin <jhb@FreeBSD.org>Release Engineering
Murray Stokely <murray@FreeBSD.org>Release EngineeringMurray Stokely <murray@FreeBSD.org>Release Engineering
Ken Smith <kensmith@FreeBSD.org>Release Engineering, I386 Release Building, Mirror Site CoordinationKen Smith <kensmith@FreeBSD.org>Release Engineering, I386 Release Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org>Release Engineering, DocumentationHiroki Sato <hrs@FreeBSD.org>Release Engineering, Documentation
Kris Kennaway <kris@FreeBSD.org>Package BuildingKris Kennaway <kris@FreeBSD.org>Package Building
Joe Marcus Clarke <marcus@FreeBSD.org>Package BuildingJoe Marcus Clarke <marcus@FreeBSD.org>Package Building
Jacques A. Vidrine <nectar@FreeBSD.org>Security OfficerJacques 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


diff --git a/website/content/en/releases/4.10R/hardware.html b/website/content/en/releases/4.10R/hardware.html index f2710613fd..6f55eb9ff5 100644 --- a/website/content/en/releases/4.10R/hardware.html +++ b/website/content/en/releases/4.10R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.10-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.10R/installation.html b/website/content/en/releases/4.10R/installation.html index 0baddd9179..69fb4fe3eb 100644 --- a/website/content/en/releases/4.10R/installation.html +++ b/website/content/en/releases/4.10R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.10-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/4.10R/qa.html b/website/content/en/releases/4.10R/qa.html index 62a83648bf..af29f991b0 100644 --- a/website/content/en/releases/4.10R/qa.html +++ b/website/content/en/releases/4.10R/qa.html @@ -1,302 +1,302 @@ Testing Guide for 4.10-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.10-RELEASE

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.10-RELEASE 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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • There was a large merge of the USB code from RELENG_5 into RELENG_4. This requires as much testing as possible to make sure that no devices have regressed in stability or functionality.

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

Known Issues

  • No known issues at this time.

diff --git a/website/content/en/releases/4.10R/relnotes.html b/website/content/en/releases/4.10R/relnotes.html index f44c8bc943..4566a07129 100644 --- a/website/content/en/releases/4.10R/relnotes.html +++ b/website/content/en/releases/4.10R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.10-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.10R/schedule.html b/website/content/en/releases/4.10R/schedule.html index 7b21d21999..7a2cbd446a 100644 --- a/website/content/en/releases/4.10R/schedule.html +++ b/website/content/en/releases/4.10R/schedule.html @@ -1,556 +1,556 @@ FreeBSD 4.10 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 4.10. 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

- - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - + - + - - + + - + - - + + - - + + - - + + - - + + - - + 22 May 2004 + - - + 22 May 2004 + - - + 22 May 2004 + - - + 22 May 2004 + - - + 23 May 2004 + - - + 23 May 2004 + - - + 24 May 2004 + - +
ActionExpectedActualDescription
Reminder announcement30 Mar 200430 Mar 200430 Mar 200430 Mar 2004 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.10 release.
4.10-BETA Testing Guide published30 Mar 200430 Mar 200430 Mar 200430 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 Freeze03 Apr 200403 Apr 200403 Apr 200403 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.
4.10-BETA7 Apr 200410 Apr 20047 Apr 200410 Apr 2004 newvers.sh, and release.ent updated.
Code freeze begins7 Apr 20047 Apr 20047 Apr 20047 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_4_10 branch20 Apr 200421 Apr 200420 Apr 200421 Apr 2004 The release branch is created.
Unfreeze the tree20 Apr 200422 Apr 200420 Apr 200422 Apr 2004 Announcement to developers@ explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_10 branch.
4.10-RC20 Apr 200424 Apr 200420 Apr 200424 Apr 2004 newvers.sh and release.ent updated.
First release candidate21 Apr 200422 Apr 200421 Apr 200422 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 -stable21 Apr 200423 Apr 200421 Apr 200423 Apr 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate27 Apr 20042 May 200427 Apr 20042 May 2004 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable28 Apr 20043 May 200428 Apr 20043 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 200417 May 2004 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable --17 May 200417 May 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Ports tree frozen20 Apr 200420 Apr 200420 Apr 200420 Apr 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush --12 Apr 200412 Apr 2004 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush17 Apr 200417 Apr 200417 Apr 200417 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 tagged27 Apr 200428 Apr 200427 Apr 200428 Apr 2004 RELEASE_4_10_0 tag for ports/.
Ports tree unfrozen27 Apr 200428 Apr 200427 Apr 200428 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 4.10-RELEASE.
Final package build starts -- -- The ports cluster and bento build final packages.
doc/ tree tagged.24 Apr 200424 Apr 200424 Apr 200424 Apr 2004 Version number bumps for doc/ subtree. RELEASE_4_10_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped.4 May 2004 + 4 May 2004
- 22 May 2004		24 May 200424 May 2004 The files listed here are updated to reflect the fact that this is FreeBSD 4.10.
Update man.cgi on the website.4 May 2004 + 4 May 2004
- 22 May 2004		25 May 200425 May 2004 Make sure the 4.10 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
src tree tagged.4 May 2004 + 4 May 2004
- 22 May 2004		25 May 200425 May 2004 RELENG_4_10_0_RELEASE tag for src/.
Final builds.4 May 2004 + 4 May 2004
- 22 May 2004		26 May 200426 May 2004 Final builds for x86 and Alpha in a pristine environment.
Warn mirror-announce@FreeBSD.org4 May 2004 + 4 May 2004
- 23 May 2004		25 May 200425 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 + 4 May 2004
- 23 May 2004		26 May 200426 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)
Announcement5 May 2004 + 5 May 2004
- 24 May 2004		27 May 200427 May 2004 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam --3 June 20043 June 2004 RELENG_4_10 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/4.10R/todo.html b/website/content/en/releases/4.10R/todo.html index 521a5e86df..aa3a584a25 100644 --- a/website/content/en/releases/4.10R/todo.html +++ b/website/content/en/releases/4.10R/todo.html @@ -1,341 +1,341 @@ FreeBSD 4.10 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.10 Open Issues

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 4.10. 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 4.10-RC3

IssueStatusResponsibleDescription

Must Resolve Issues for 4.10-RELEASE

IssueStatusResponsibleDescription

Desired Features for 4.10-RELEASE

IssueStatusResponsibleDescription

Documentation items that must be resolved for 4.10

IssueStatusResponsibleDescription

Testing focuses for 4.10

- + - + - +
IssueStatusResponsibleDescription
twe(4) stability problemNeeds testingNeeds testing -- 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 leakNeeds testingNeeds testing -- 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 sysinstallNeeds testingNeeds testing -- 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.

diff --git a/website/content/en/releases/4.11R/announce.html b/website/content/en/releases/4.11R/announce.html index 410e166e75..68b9fdadc4 100644 --- a/website/content/en/releases/4.11R/announce.html +++ b/website/content/en/releases/4.11R/announce.html @@ -1,492 +1,492 @@ FreeBSD 4.11-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11-RELEASE Announcement

Date: Tue, 25 Jan 2005 12:02:10 -0500
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 4.11-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/4.11R/relnotes.html

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

FreeBSD 4.11 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 4.11-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 4.11 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 4.11 including The FreeBSD Mall, Hewlett Packard, Yahoo!, Sentex Communications, and NTT/Verio.

The release engineering team for 4.11-RELEASE includes:

- - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + +
Scott Long <scottl@FreeBSD.org>Release EngineeringScott Long <scottl@FreeBSD.org>Release Engineering
Robert Watson <rwatson@FreeBSD.org>Release Engineering, SecurityRobert Watson <rwatson@FreeBSD.org>Release Engineering, Security
John Baldwin <jhb@FreeBSD.org>Release EngineeringJohn Baldwin <jhb@FreeBSD.org>Release Engineering
Ken Smith <kensmith@FreeBSD.org>Release Engineering, I386 Release Building, Mirror Site CoordinationKen Smith <kensmith@FreeBSD.org>Release Engineering, I386 Release Building, Mirror Site Coordination
Hiroki Sato <hrs@FreeBSD.org>Release Engineering, DocumentationHiroki Sato <hrs@FreeBSD.org>Release Engineering, Documentation
Wilko Bulte <wilko@FreeBSD.org>Alpha Release BuildingWilko Bulte <wilko@FreeBSD.org>Alpha Release Building
Kris Kennaway <kris@FreeBSD.org>Package BuildingKris Kennaway <kris@FreeBSD.org>Package Building
Joe Marcus Clarke <marcus@FreeBSD.org>Package BuildingJoe Marcus Clarke <marcus@FreeBSD.org>Package Building
Jacques A. Vidrine <nectar@FreeBSD.org>Security OfficerJacques A. Vidrine <nectar@FreeBSD.org>Security Officer
Paul Saab <ps@FreeBSD.org>Bittorrent CoordinationPaul 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


diff --git a/website/content/en/releases/4.11R/errata_policy.html b/website/content/en/releases/4.11R/errata_policy.html index 30d6a88975..75e7f0a4cf 100644 --- a/website/content/en/releases/4.11R/errata_policy.html +++ b/website/content/en/releases/4.11R/errata_policy.html @@ -1,300 +1,300 @@ FreeBSD 4.11 Errata Processing Policy
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11 Errata Processing Policy

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD 4.11.

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 4.11 and who has reviewed the fix.


diff --git a/website/content/en/releases/4.11R/hardware.html b/website/content/en/releases/4.11R/hardware.html index fd3f6f232b..dc4d8d42e6 100644 --- a/website/content/en/releases/4.11R/hardware.html +++ b/website/content/en/releases/4.11R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.11-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.11R/installation.html b/website/content/en/releases/4.11R/installation.html index 63d99fac53..801f0c1900 100644 --- a/website/content/en/releases/4.11R/installation.html +++ b/website/content/en/releases/4.11R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.11-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/4.11R/relnotes.html b/website/content/en/releases/4.11R/relnotes.html index ba2d91c695..e82686afbf 100644 --- a/website/content/en/releases/4.11R/relnotes.html +++ b/website/content/en/releases/4.11R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.11-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.11R/schedule.html b/website/content/en/releases/4.11R/schedule.html index 5609da8bfd..2c344ab3ed 100644 --- a/website/content/en/releases/4.11R/schedule.html +++ b/website/content/en/releases/4.11R/schedule.html @@ -1,541 +1,541 @@ FreeBSD 4.11 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 4.11. 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 announcement30 Nov 200430 Nov 200430 Nov 200430 Nov 2004 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 4.11 release.
4.11-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 200418 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.
4.11-PRERELEASE6 Dec 20046 Dec 20046 Dec 20046 Dec 2004 newvers.sh updated.
Code freeze begins13 Dec 200413 Dec 200413 Dec 200413 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_4_11 branch17 Dec 200417 Dec 200417 Dec 200417 Dec 2004 The release branch is created. Update newvers.sh and release.ent on various branches involved.
Unfreeze the tree17 Dec 200417 Dec 200417 Dec 200417 Dec 2004 Announcement to developers explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_11 branch.
4.11-RC17 Dec 200417 Dec 200417 Dec 200417 Dec 2004 newvers.sh and release.ent updated.
First release candidate20 Dec 200418 Dec 200420 Dec 200418 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 -stable20 Dec 200418 Dec 200420 Dec 200418 Dec 2004 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate3 Jan 20053 Jan 20053 Jan 20053 Jan 2005 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable3 Jan 20053 Jan 20053 Jan 20053 Jan 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded.
Third release candidate17 Jan 200517 Jan 200517 Jan 200517 Jan 2005 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable17 Jan 200517 Jan 200517 Jan 200517 Jan 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Ports tree frozen30 Dec 200431 Dec 200430 Dec 200431 Dec 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Announce doc/ tree slush27 Dec 200429 Dec 200427 Dec 200429 Dec 2004 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush14 Jan 200515 Jan 200514 Jan 200515 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 tagged6 Jan 20058 Jan 20056 Jan 20058 Jan 2005 RELEASE_4_11_0 tag for ports/.
Ports tree unfrozen7 Jan 20058 Jan 20057 Jan 20058 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 4.11-RELEASE.
Final package build starts6 Jan 20056 Jan 2005 -- The ports cluster and pointyhat build final packages.
doc/ tree tagged.18 Jan 200518 Jan 2005 -- Version number bumps for doc/ subtree. RELEASE_4_11_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped.20 Jan 200521 Jan 200520 Jan 200521 Jan 2005 The files listed here are updated to reflect the fact that this is FreeBSD 4.11.
src tree tagged.20 Jan 200521 Jan 200520 Jan 200521 Jan 2005 RELENG_4_11_0_RELEASE tag for src/.
Final builds.20 Jan 200521 Jan 200520 Jan 200521 Jan 2005 Final builds for x86 and Alpha in a pristine environment.
Warn mirror-announce@FreeBSD.org21 Jan 200524 Jan 200521 Jan 200524 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 200524 Jan 200522 Jan 200524 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 200525 Jan 200524 Jan 200525 Jan 2005 Make sure the 4.11 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
Announcement24 Jan 200525 Jan 200524 Jan 200525 Jan 2005 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam2 Feb 20051 Feb 20052 Feb 20051 Feb 2005 RELENG_4_11 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/4.11R/todo.html b/website/content/en/releases/4.11R/todo.html index 42aa1acffd..5d292267e9 100644 --- a/website/content/en/releases/4.11R/todo.html +++ b/website/content/en/releases/4.11R/todo.html @@ -1,300 +1,300 @@ FreeBSD 4.11 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.11 Open Issues

Open Issues

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

Must Resolve Issues for 4.11-RC3

IssueStatusResponsibleDescription

Must Resolve Issues for 4.11-RELEASE

IssueStatusResponsibleDescription

Desired Features for 4.11-RELEASE

IssueStatusResponsibleDescription

Documentation items that must be resolved for 4.11

IssueStatusResponsibleDescription

Testing focuses for 4.11

IssueStatusResponsibleDescription

diff --git a/website/content/en/releases/4.4R/announce.html b/website/content/en/releases/4.4R/announce.html index f8dea700e5..a478555df2 100644 --- a/website/content/en/releases/4.4R/announce.html +++ b/website/content/en/releases/4.4R/announce.html @@ -1,349 +1,349 @@ FreeBSD 4.4 Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.4 Announcement

Date: Thursday, 20 Sep 2001 18:00:00 -0800
From: "Jordan K. Hubbard" <jkh@freebsd.org>
To: announce@FreeBSD.org
Subject: 4.4-RELEASE is now available

I am very pleased to announce the availability of FreeBSD 4.4-RELEASE, the very very latest in 4.x-STABLE branch technology. Since FreeBSD 4.3 was released in April 2001, we have made hundreds of fixes, updated many different components and addressed a wide variety of security issues. We have also substantially revamped the documentation and provided much more comprehensive release notes. Please see the various HTML (or, at your option, text) files in the release directory for more information.

4.4-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.4/
and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.4/

Where ${arch} is currently "i386" or "alpha". 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 The FreeBSD Mall. Each CD sets contains the FreeBSD installation and application package bits for the x86 ("PC") architecture. 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 can no longer fit on the 4 ISO set.

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, Mordor, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, 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.

Most releases prior to 4.4-RELEASE have been team efforts, only possible at all due to the collaboration of many different people. It still bears noting, however, that 4.4-RELEASE was done completely by a "release engineering team" rather than "a release engineer" and I think it's fair to say that with 4.4-RELEASE, we've completed the transition from having one primary person worry about releases to having many primary people (re@FreeBSD.org) worry about them. This is a distinct improvement from any point of view and, I think, an important milestone in FreeBSD's progress.

In addition to myself, the release engineering team for 4.4-RELEASE has been:

Murray Stokely <murray@freebsd.org> : Release Engineering
Steve Price <steve@FreeBSD.org> : Package collection
Satoshi Asami <asami@FreeBSD.org> : Package collection
Bruce A. Mah <bmah@FreeBSD.org> : Release notes

Please join me in thanking them for all the hard work which went into making this release. I would also like to thank the FreeBSD Committers <committers@FreeBSD.org>, without which there would be nothing to release, and the many thousands of FreeBSD users world-wide who contributed bug fixes, features and suggestions.

Thanks!

- Jordan

diff --git a/website/content/en/releases/4.4R/hardware.html b/website/content/en/releases/4.4R/hardware.html index 9dbcc73d8f..85f43c1e61 100644 --- a/website/content/en/releases/4.4R/hardware.html +++ b/website/content/en/releases/4.4R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.4 Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.4 Hardware Notes

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.


diff --git a/website/content/en/releases/4.4R/notes.html b/website/content/en/releases/4.4R/notes.html index cb925f8fa7..a7fc9eb16e 100644 --- a/website/content/en/releases/4.4R/notes.html +++ b/website/content/en/releases/4.4R/notes.html @@ -1,276 +1,276 @@ FreeBSD 4.4 Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.4 Release Notes

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.


diff --git a/website/content/en/releases/4.5R/announce.html b/website/content/en/releases/4.5R/announce.html index dca7967325..c74ff82983 100644 --- a/website/content/en/releases/4.5R/announce.html +++ b/website/content/en/releases/4.5R/announce.html @@ -1,392 +1,392 @@ FreeBSD 4.5 Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.5 Announcement

Date: Tuesday, 29 Jan 2002 20:00:00 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: announce@FreeBSD.org
Subject: 4.5-RELEASE is now available

I am very pleased to announce the availability of FreeBSD 4.5-RELEASE, the very latest release on the FreeBSD -STABLE branch of development. Since FreeBSD 4.4 was released in September 2001, we have made hundreds of fixes, updated many system components, made several substantial performance improvements, and addressed a wide variety of security issues.

In particular, there have been significant enhancements in the areas of network communications and filesystems. FreeBSD 4.5 contains improvements to the TCP stack to provide better throughput. In addition, TCP performance is aided by larger default buffer sizes. Finally, FreeBSD 4.5 contains new mechanisms to mitigate the effects of TCP Denial of Service attacks.

The FFS filesystem benefits from a new directory layout strategy that has demonstrated significantly better performance for operations traversing large directory structures. Various bugs were located and fixed in the FFS and NFS code with the help of a filesystem exercising program originally developed at Apple Computer, Inc.

Those users doing fresh installations of FreeBSD should note some changes for newly created filesystems, intended to improve the "out of the box" performance of FreeBSD. In particular, sysinstall(8) now enables Soft Updates (a strategy for improving both performance and reliability of on-disk data structures) for new filesystems it creates and the newfs(8) program will now, by default, create filesystems with larger block sizes.

For more information about the most significant changes with this release of FreeBSD, please see the release section of our web site:

http://www.FreeBSD.org/releases/

There you will find Release Notes, Hardware Notes, and a list of Errata.

Availability

4.5-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.

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 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. The following companies have contributed substantially to the development of FreeBSD :

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

Each CD 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.

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 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.

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

The FreeBSD installation instructions have recently been significantly enhanced. Chapter 2 of The FreeBSD Handbook, available online, provides a complete installation walk-through for users new to FreeBSD.

Acknowledgments

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

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

Robert Watson <rwatson@FreeBSD.org>Release Engineering
John Baldwin <jhb@FreeBSD.org>Release Engineering
Bruce A. Mah <bmah@FreeBSD.org>Release Documentation
Steve Price <steve@FreeBSD.org>Package Building
Wilko Bulte <wilko@FreeBSD.org>Alpha Platform Release Engineering
Peter Wemm <peter@FreeBSD.org>Ports Cluster System Administration

Please join me in thanking them for all the hard work which went into making this release. 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.

Thanks!

- Murray


diff --git a/website/content/en/releases/4.5R/contents.html b/website/content/en/releases/4.5R/contents.html index 455837fcb6..e9841a2ac0 100644 --- a/website/content/en/releases/4.5R/contents.html +++ b/website/content/en/releases/4.5R/contents.html @@ -1,290 +1,290 @@ FreeBSD 4.5 Contents
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.5 Contents

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.5-install.iso - This is a bootable CDROM image that contains the base system, XFree86 3.3.6, a 'tools' directory of software for users performing an installation from other operating systems, and 2,210 third-party software packages. [ file listing ]

Contents of Disc 2

4.5-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.5-disc3.iso, 4.5-disc4.iso - The remaining two discs contain the most popular third-party software package that users have requested. [ Disc 3 listing ] [ Disc 4 listing ]


diff --git a/website/content/en/releases/4.5R/hardware.html b/website/content/en/releases/4.5R/hardware.html index ec0204c513..c6437dcf9c 100644 --- a/website/content/en/releases/4.5R/hardware.html +++ b/website/content/en/releases/4.5R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.5 Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.5 Hardware Notes

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.


diff --git a/website/content/en/releases/4.5R/notes.html b/website/content/en/releases/4.5R/notes.html index 2f742b7945..1541c855b2 100644 --- a/website/content/en/releases/4.5R/notes.html +++ b/website/content/en/releases/4.5R/notes.html @@ -1,276 +1,276 @@ FreeBSD 4.5 Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.5 Release Notes

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.


diff --git a/website/content/en/releases/4.5R/qa.html b/website/content/en/releases/4.5R/qa.html index bf40f179a0..e6552594b0 100644 --- a/website/content/en/releases/4.5R/qa.html +++ b/website/content/en/releases/4.5R/qa.html @@ -1,377 +1,377 @@ Testing Guide for 4.5-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.5-RELEASE

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.5-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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • Recent TCP changes, especially relating to the delayed ACK fix, congestion response, syncache, syncookies, increased socket buffer sizes, et al. We're interested in testing interoperability with as many platforms as possible, demonstrating continued strong (and better) scalability and performance, and watching out for quirks (connection stalls, ...), not to mention crashes. Jonathan Lemon was responding to a panic report on freebsd-current earlier today regarding a PCB call, which is something we should keep an eye on. On the other hand, Yahoo! is now deploying this code, and that should help test it a great deal.

  • VFS/VM/NFS fixes. We need to continue to test performance, correctness, and interoperability. In particular, I'd like to see a lot of inter-platform performance testing (FreeBSD->Solaris, vice versa, etc). We'd also like careful investigation of low-memory situations.

  • FFS fixes. We had some reports of deadlocks in FFS; it sounds like Matt Dillon has caught most of them, but combinations I'd particular like to see tested involve Quotas, Chroot, and NFS, under load, and involving memory mapping and heavy directory operations.

  • NTP 4.1. This is probably reasonable safe, but it doesn't hurt to do interop testing, especially on the Alpha platform.

  • SMBfs. We need stability testing, mostly, I suspect. Performance is probably not a large focus. While SMBfs support has been available on -STABLE through a port previously, determining that the integration with the base system (especially the boot process) was done correctly is important. Attempting to use SMBfs in /etc/fstab in a diskless environment might be one thing to explore, for example.

  • Once the man page change goes in (which I think it should) we'll want some basic testing of the man command. Update: This change proved too controversial for introduction this late in the release cycle, and so it will not be included with FreeBSD 4.5.

  • cdboot. Late in the release cycle, a new implementation of the CD-based boot loader was introduced. This should generally improve support for booting or installing from CD, but this change requires testing on a variety of architectures and devices. Update: Thanks to everyone who helped test this functionality. A number of users reported problems booting with this new loader, so this will not be used for FreeBSD 4.5.

  • Sysinstall module loading. In order to make room for more devices on the boot floppy, a number of wireless Ethernet device drivers were moved over to the MFSROOT floppy in the form of loadable kernel modules. We would like to see this functionality tested thoroughly before the final release.

  • ATA code. The ATA driver has been updated to support 48bit addressing and has been tested to work with at least one 160GB IDE drive. Further testing with very large IDE drives is necessary.

  • XFree86. There was at least one problem report with XFree86 4.x sent to the qa@FreeBSD.org mailing list. Please help us test this important third party software package to ensure it works well with FreeBSD 4.5. The FreeBSD Handbook may need to be updated to describe the recommended procedure for installing XFree86 4.x during a new installation.
  • Linux Compatibility. There was a small change in the Ethernet device enumeration of the Linux compatibility layer. All Linux applications should be tested under the new environment. In particular, those applications that deal with network interfaces should be tested carefully.

The release notes will always be a good place to look for things to test. There are a number of new drivers, including if_em, which would probably benefit from more exposure. Please report bugs to the qa@FreeBSD.org list, and/or via send-pr with a heads up to the qa list.

Known Issues

4.5 Release Candidate 3 was released on January 23. There will be one final release candidate before the final release. Please see the postings to qa@FreeBSD.org and stable@FreeBSD.org for more information.


diff --git a/website/content/en/releases/4.5R/schedule.html b/website/content/en/releases/4.5R/schedule.html index 668ca294a9..f11aeacdad 100644 --- a/website/content/en/releases/4.5R/schedule.html +++ b/website/content/en/releases/4.5R/schedule.html @@ -1,506 +1,506 @@ FreeBSD 4.5 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.5 Release Process

Introduction

The release engineering team (re@FreeBSD.org) for FreeBSD 4.5 consists of Murray Stokely, Steve Price, Robert Watson, and John Baldwin.

The x86 build team consists of Murray Stokely and John Baldwin.

The Alpha build team consists of David O'Brien, Wilko Bulte, John Baldwin, and Murray Stokely.

The third-party packages are handled by Steve Price and the Ports managers (portmgr@FreeBSD.org).

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.

For an overview of the entire release engineering process, please see this document.

Schedule

ActionExpectedActualDescription
Reminder announcement01 Dec 200103 Dec 2001 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.5 release.
4.5-PRERELEASE 20 Dec 2001 20 Dec 2001 newvers.sh, param.h, and release.ent updated.
FTP site updated 20 Dec 2001 20 Dec 2001 pkg_add -r works for 4.5-PRERELEASE machines.
Code freeze begins 20 Dec 2001 20 Dec 2001 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. 05 Jan 2002 24 Jan 2002 The second disc contains commercial software demos, these demos should be updated to contain the latest versions.
4.5-RC 09 Jan 2002 09 Jan 2002 newvers.sh and release.ent updated.
Announce the Ports Freeze 09 Jan 2002 09 Jan 2002 Someone from portmgr should email freebsd-ports@ and CC: developers@ to set a date for the tagging of the ports tree. Will set this date at January 22nd.
Heads up to hubs 09 Jan 2002 09 Jan 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 09 Jan 2002 09 Jan 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 09 Jan 2002 09 Jan 2002 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the release is uploaded.
Second release candidate ?? Jan 2002 18 Jan 2002 Note: the release date of this candidate depends on the user experience with RC1.
Third release candidate 23 Jan 2002 24 Jan 2002 4.5 RC3 for the x86 and Alpha architectures will be made available from ftp.FreeBSD.org and the mirrors.
Ports tree frozen. 22 Jan 2002 22 Jan 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_5_0 tag. After this time, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.5-RELEASE.
Final package build starts 22 Jan 2002 22 Jan 2002 The ports cluster and bento build final packages.
Package split 23 Jan 2002 29 Jan 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. 24 Jan 2002 24 Jan 2002 RELEASE_4_5_0 tag for docs.
RELENG_4_5 branch 25 Jan 2002 26 Jan 2002 The release branch is created.
Note to freebsd-stable@ 25 Jan 2002 26 Jan 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. 25 Jan 2002 25 Jan 2002 The files listed here are updated to reflect the fact that this is FreeBSD 4.5.
src tree tagged. 27 Jan 2002 27 Jan 2002 RELEASE_4_5_0_RELEASE tag for src.
Update man.cgi on the website. 25 Jan 2002 -- Make sure the 4.5 manual pages are being displayed by default for the man->web gateway.
Archive the errata for FreeBSD 4.4. 25 Jan 2002 25 Jan 2002 The new RELNOTESng errata file should be setup, and the old errata file archived.
Final builds. 28 Jan 2002 28 Jan 2002 Final builds for x86 and Alpha in a pristine environment.
Warn hubs@FreeBSD.org 28 Jan 2002 28 Jan 2002 Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come.
Upload to ftp-master. 28 Jan 2002 28 Jan 2002 release and packages uploaded to ftp-master.FreeBSD.org
Announcement 28 Jan 2002 29 Jan 2002 Announcement sent out after a majority of the mirrors have received the bits.

It's been pointed out that this table is rather boring. Bruce Mah gave a slightly more interesting rendition of the 12 days of Code-Freeze.


diff --git a/website/content/en/releases/4.6.2R/announce.html b/website/content/en/releases/4.6.2R/announce.html index 71caba5c6e..8fb0e79ce6 100644 --- a/website/content/en/releases/4.6.2R/announce.html +++ b/website/content/en/releases/4.6.2R/announce.html @@ -1,422 +1,422 @@ FreeBSD 4.6.2-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6.2-RELEASE Announcement

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)


diff --git a/website/content/en/releases/4.6.2R/hardware.html b/website/content/en/releases/4.6.2R/hardware.html index 8f0168dd99..4ded1b1c23 100644 --- a/website/content/en/releases/4.6.2R/hardware.html +++ b/website/content/en/releases/4.6.2R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.6.2-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6.2-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.6.2R/relnotes.html b/website/content/en/releases/4.6.2R/relnotes.html index bede2969db..a054b2e988 100644 --- a/website/content/en/releases/4.6.2R/relnotes.html +++ b/website/content/en/releases/4.6.2R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.6.2-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6.2-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.6R/announce.html b/website/content/en/releases/4.6R/announce.html index a192f9e919..74b9fe118f 100644 --- a/website/content/en/releases/4.6R/announce.html +++ b/website/content/en/releases/4.6R/announce.html @@ -1,450 +1,450 @@ FreeBSD 4.6-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6-RELEASE Announcement

Date: Sat, 15 Jun 2002 16:34:26 -0700
From: "Bruce A. Mah" <bmah@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 4.6-RELEASE is now available

I am happy to announce the availability of FreeBSD 4.6-RELEASE, the very latest release on the FreeBSD -STABLE development branch. Since FreeBSD 4.5-RELEASE in January 2002, we have made hundreds of fixes, updated many system components, and addressed a wide variety of security issues.

One of the most significant changes in FreeBSD 4.6 is the adoption of XFree86 4.2.0 as the default version of the X Windows System. We encourage users (particularly those upgrading from older installations of XFree86) to consult the relevant section of the FreeBSD Handbook for information on installing and configuring XFree86 4.2.0. This information can be found on-line at:

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

On systems with the doc distribution installed, it can also be found at:

/usr/share/doc/en_US.ISO8859-1/books/handbook/x11.html

A number of enhancements to network device drivers have been made, as well as updates to the ATA storage subsystem.

Some contributed programs have been updated, such as sendmail (updated to 8.12.3) and the ISC DHCP client (updated to 3.0.1RC8).

For more information about the most significant changes with this release of FreeBSD, please see the release notes:

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

It is also useful to peruse the errata file, as it contains late-breaking news about the release:

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

For more information about FreeBSD release engineering activities (including a schedule of upcoming releases), please see:

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

Availability

FreeBSD 4.6-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 have contributed substantially to the development of FreeBSD:

FreeBSD Mall, Inc. http://www.freebsdmall.com/
FreeBSD Services Ltd. http://www.freebsd-services.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 from FreeBSD Services Ltd.

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, Trantor, 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, including Compaq, Yahoo!, and The FreeBSD Mall.

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

Murray Stokely <murray@FreeBSD.org> Release Engineering Lead, i386 Builds
Robert Watson <rwatson@FreeBSD.org> Release Engineering
John Baldwin <jhb@FreeBSD.org> Release Engineering, alpha Builds
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
David O'Brien <obrien@FreeBSD.org> XFree86 Integration

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!

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


diff --git a/website/content/en/releases/4.6R/contents.html b/website/content/en/releases/4.6R/contents.html index 747b1d26a5..701ed1f86e 100644 --- a/website/content/en/releases/4.6R/contents.html +++ b/website/content/en/releases/4.6R/contents.html @@ -1,291 +1,291 @@ FreeBSD 4.6-RELEASE Contents
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6-RELEASE Contents

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 ]


diff --git a/website/content/en/releases/4.6R/hardware.html b/website/content/en/releases/4.6R/hardware.html index b1f149fecc..07da3986b6 100644 --- a/website/content/en/releases/4.6R/hardware.html +++ b/website/content/en/releases/4.6R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.6-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.6R/installation.html b/website/content/en/releases/4.6R/installation.html index 1a2d720cf8..44d01d8c1f 100644 --- a/website/content/en/releases/4.6R/installation.html +++ b/website/content/en/releases/4.6R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.6-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/4.6R/qa.html b/website/content/en/releases/4.6R/qa.html index f51124ed9e..8a05bb01f4 100644 --- a/website/content/en/releases/4.6R/qa.html +++ b/website/content/en/releases/4.6R/qa.html @@ -1,358 +1,358 @@ Testing Guide for 4.6-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.6-RELEASE

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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • DHCP client support. This release will feature a major update of the ISC DHCP client (v3.0.1 RC8). The common cases have been well tested, but testing in more demanding or unusual environments would be beneficial. In particular, the new dynamic DNS update functionality has not been well tested.
  • sppp(4) upgrade. The ISDN project (i4b) once maintained an off-spring version of the SyncPPP driver, with a number of enhancements and bug-fixes made to it by people contributing to the i4b project. On the other hand, other improvements and bug-fixes of the regular tree's sppp driver didn't make it back to that version, so eventually two different SyncPPP drivers developed. The i4b version has been merged back in FreeBSD-current a few months ago, and these changes have now been folded into FreeBSD-stable as well, thus eliminating i4b's separate version. sppp users (of both flavours) should carefully test the new version. Users who previously used the i4b version should find all those improvements still being present (most notably, VJ header compression). Users who use sppp on hardware (HDLC) devices (like ar(4) or sr(4)) should see no breakage, but might notice that the negotiation of VJ header compression is now enabled by default. Use spppcontrol(8) to modify the default behaviour. Please report any breakage or oddity you observe to <joerg@FreeBSD.org>.
  • XFree86 4.2.0. sysinstall now installs XFree86 4.2.0 instead of XFree86 3.3.6; the XFree86 installation now uses ``normal'' binary packages instead of the special tarballs in past releases. The ports infrastructure now uses the XFree86 version 4 as the default version for satisfying dependencies.

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

Known Issues

  • Due to a buffer truncation in sysinstall, the GNOME meta-port (x11/gnome) in 4.6-RC1 does not install correctly. This has been fixed and is functional for 4.6-RC2 (and any later release candidate snapshots).
  • nslookup(1) had some bugs in 4.6-RC1 and 4.6-RC2. These have been been corrected and should function correctly beginning with 4.6-RC3.
  • Some users have reported stability issues with tagged queueing and the ata(4) driver. These problems have only been observed when using tags on motherboard-based ATA channels.
  • Potential problems with the TCP default window size (see kern/34801). The default window size has been reduced from 65536 to 57344 for 4.6-RELEASE. (Errata item needed.)
  • Some of the XFree86 configuration utilities write their generated configuration files in places where sysinstall isn't looking for them, thus complicating XFree86 installs that are initiated from within sysinstall. These have been changed to /etc/X11/XF86Config for 4.6-RELEASE. (Errata item needed.)
  • Some filenames in the ports tree are too long, thus resulting in odd /usr/@LongLink files after a sysinstall. These filenames have been shortened for 4.6-RELEASE.
  • Under some circumstances, dhclient can go into an infinite loop.

diff --git a/website/content/en/releases/4.6R/relnotes.html b/website/content/en/releases/4.6R/relnotes.html index b49f3c53bc..929336ec8b 100644 --- a/website/content/en/releases/4.6R/relnotes.html +++ b/website/content/en/releases/4.6R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.6-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.6R/schedule.html b/website/content/en/releases/4.6R/schedule.html index f002b58bb3..ade13458d1 100644 --- a/website/content/en/releases/4.6R/schedule.html +++ b/website/content/en/releases/4.6R/schedule.html @@ -1,529 +1,529 @@ FreeBSD 4.6 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.6 Release Process

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.xml.
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.

diff --git a/website/content/en/releases/4.7R/announce.html b/website/content/en/releases/4.7R/announce.html index 7a8acf9920..80c0df4391 100644 --- a/website/content/en/releases/4.7R/announce.html +++ b/website/content/en/releases/4.7R/announce.html @@ -1,429 +1,429 @@ FreeBSD 4.7-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.7-RELEASE Announcement

Date: Thu, 10 Oct 2002 07:47:54 -0700
From: "Murray Stokely" <murray@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 4.7-RELEASE is now available

I am happy to announce the availability of FreeBSD 4.7-RELEASE, the latest release of the FreeBSD -STABLE development branch. Since FreeBSD 4.6-RELEASE in June 2002, we have updated a number of software programs in the base system, such as GCC and sendmail. Several new drivers have been added for USB devices and disk controllers. We have also incorporated updates for XFree86 and our Linux emulation libraries.

FreeBSD 4.7 also incorporates all of the security and bug fixes from 4.6.2 (released in August 2002), including several ATA-related bugfixes, updates for OpenSSL and OpenSSH, and fixes to address several security advisories.

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/4.7R/relnotes.html

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

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

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

Availability

FreeBSD 4.7-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 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.

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 4.7 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

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

Bruce Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
John Baldwin <jhb@FreeBSD.org> Release Engineering, alpha Builds
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

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)


diff --git a/website/content/en/releases/4.7R/hardware.html b/website/content/en/releases/4.7R/hardware.html index 8fef565039..191c8698ec 100644 --- a/website/content/en/releases/4.7R/hardware.html +++ b/website/content/en/releases/4.7R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.7-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.7-RELEASE Hardware Notes

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.7-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/4.7R/installation.html b/website/content/en/releases/4.7R/installation.html index 89711e378a..5539b15e31 100644 --- a/website/content/en/releases/4.7R/installation.html +++ b/website/content/en/releases/4.7R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.7-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.7-RELEASE Installation Notes

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.7-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/4.7R/qa.html b/website/content/en/releases/4.7R/qa.html index eb0e6e44cb..4ee618016f 100644 --- a/website/content/en/releases/4.7R/qa.html +++ b/website/content/en/releases/4.7R/qa.html @@ -1,371 +1,371 @@ Testing Guide for 4.7-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.7-RELEASE

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.7-RELEASE 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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • PPP. A number of significant PPP changes were merged to -STABLE before the code freeze. In particular, the following changes were made:

    • IPv6 support
    • Better RADIUS support (including MS-CHAP)
    • Improved handling of bad negotiation options
    • Improved negotiation diagnostics
    • Improved sockaddr (RTAX) parsing
    • More consistent compile time options (NOXXX to compile something out)
    • More available macros
    • Firewall punching
    • Improved ``proxy'' and ``proxyall'' handling
    • Handle connected UDP sockets on descriptor 0 in -direct mode
    • Fix a load of typos
    • Update to internal version 3.1
  • IPFilter has recently been updated to version 3.4.29 and has not yet been thoroughly tested in -STABLE.
  • ahc and ahd Adaptec SCSI drivers: There has been a major update to the ahc and ahd device drivers. These drivers have not yet been thoroughly tested in -STABLE.
  • ATA. There were some problems with tagged queuing and some CDROM read operations with the ATA stack in FreeBSD 4.6. These problems were fixed in 4.6.2, but more testing on different hardware is still needed.
  • Sendmail has been updated to 8.12.6. This should be a very stable bugfix release, but sendmail users are encouraged to help test this before 4.7 is released.
  • XFree86 has been updated to 4.2.1. This release fixes some security issues and other bugs in 4.2.0, but should have almost identical functionality.
  • Heimdal (Kerberos 5 support) has been updated. Kerberos 5 users are encouraged to test this before 4.7 is released.

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

Known Issues

  • The 4.7-RC1 snapshots were built without packages due to some problems (which only recently came to light) in the bzip2 package support. Resolution: The RE team decided to return to gzip packages for 4.7-RC2 (as well as any subsequent RC snapshots and the final release), thus allowing this snapshot to have its normal package set.
  • Partially as a result of the above package problems, the ports tree on the 4.7-RC1/i386 ISO image is not exactly the same as the 4.7-RC1/i386 FTP directory. Both will be eventually updated for subsequent RC snapshots and the final release. Resolution: Not a factor for subsequent snapshots.
  • Loading kernel modules on 4.7-RC1/alpha is broken. Resolution: A fix has been committed and will be present in 4.7-RC2/alpha.
  • When booting from the install media (e.g. a CDROM), sysinstall tries to load a set of modules from the mfsroot image. For some reason, sysinstall cannot load the module containing the aac driver; this results in an error dialog when starting sysinstall. Access to aac devices from within sysinstall is, understandably, broken by this error. This appears to be due to a dependency on the linux module. Resolution: The aac driver was brought back into the install kernels, and other modules were moved to modules.

diff --git a/website/content/en/releases/4.7R/relnotes.html b/website/content/en/releases/4.7R/relnotes.html index 3a80f8f28e..287c881051 100644 --- a/website/content/en/releases/4.7R/relnotes.html +++ b/website/content/en/releases/4.7R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.7-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.7-RELEASE Release Notes

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.7-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/4.7R/schedule.html b/website/content/en/releases/4.7R/schedule.html index ffde3d7dd0..18007f16c3 100644 --- a/website/content/en/releases/4.7R/schedule.html +++ b/website/content/en/releases/4.7R/schedule.html @@ -1,518 +1,518 @@ FreeBSD 4.7 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.7 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 4.7. 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 announcement06 Aug 200206 Aug 2002Reminder announcement06 Aug 200206 Aug 2002 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.7 release.
4.7-PRERELEASE Testing Guide publishedOngoing02 Sep 2002 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.7-PRERELEASE01 Sep 200202 Sep 200201 Sep 200202 Sep 2002 newvers.sh, and release.ent updated.
FTP site updated 01 Sep 2002 02 Sep 2002 pkg_add -r works for 4.7-PRERELEASE machines.
Code freeze begins 01 Sep 2002 01 Sep 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. -- -- The second disc contains commercial software demos, these demos should be updated to contain the latest versions.
4.7-RC 15 Sep 2002 16 Sep 2002 newvers.sh and release.ent updated.
Announce the Ports Freeze 15 Sep 2002 16 Sep 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.
First release candidate 15 Sep 2002 18 Sep 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 directory should be a relative symlink, as described in the releng article.
Heads up to -stable 17 Sep 2002 18 Sep 2002 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded.
Package split posted 17 Sep 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 -- 27 Sep 2002 Note: the release date of this candidate depends on the user experience with RC1.
Third release candidate -- 07 Oct 2002
Ports tree frozen 20 Sep 2002 21 Sep 2002 Only approved commits will be permitted to the ports/ tree during the freeze.
Ports tree tagged 24 Sep 2002 01 Oct 2002 RELEASE_4_7_0 tag for ports/.
Ports tree unfrozen 24 Sep 2002 05 Oct 2002 After the ports tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.7-RELEASE.
Final package build starts 25 Sep 2002 05 Oct 2002 The ports cluster and bento build final packages.
Package split 26 Sep 2002 08 Oct 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 Sep 2002 01 Oct 2002 RELEASE_4_7_0 tag for docs.
RELENG_4_7 branch 28 Sep 2002 06 Oct 2002 The release branch is created.
Note to freebsd-stable@ 28 Sep 2002 06 Oct 2002 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. 29 Sep 2002 07 Oct 2002 The files listed here are updated to reflect the fact that this is FreeBSD 4.7.
Update man.cgi on the website. 29 Sep 2002 06 Oct 2002 Make sure the 4.7 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
src tree tagged. 29 Sep 2002 06 Oct 2002 RELENG_4_7_0_RELEASE tag for src.
Final builds. 08 Oct 2002 08 Oct 2002 Final builds for x86 and Alpha in a pristine environment.
Warn hubs@FreeBSD.org 30 Sep 2002 09 Oct 2002 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. 08 Oct 2002 09 Oct 2002 release and packages uploaded to ftp-master.FreeBSD.org
Announcement 08 Oct 2002 10 Oct 2002 Announcement sent out after a majority of the mirrors have received the bits.
Unfreeze the tree 08 Oct 2002 10 Oct 2002 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_7 branch.

diff --git a/website/content/en/releases/4.8R/announce.html b/website/content/en/releases/4.8R/announce.html index 0a95a6a6b8..21eed6406d 100644 --- a/website/content/en/releases/4.8R/announce.html +++ b/website/content/en/releases/4.8R/announce.html @@ -1,437 +1,437 @@ FreeBSD 4.8-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.8-RELEASE Announcement

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

I am happy to announce the availability of FreeBSD 4.8-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/4.8R/relnotes.html

http://www.FreeBSD.org/releases/4.8R/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 4.8-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 4.8 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

In addition to myself, the release engineering team for 4.8-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)


diff --git a/website/content/en/releases/4.8R/hardware.html b/website/content/en/releases/4.8R/hardware.html index eacefe2ead..0200ef93bf 100644 --- a/website/content/en/releases/4.8R/hardware.html +++ b/website/content/en/releases/4.8R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.8-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.8-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.8R/installation.html b/website/content/en/releases/4.8R/installation.html index 37df415d6b..716f86ae72 100644 --- a/website/content/en/releases/4.8R/installation.html +++ b/website/content/en/releases/4.8R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.8-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.8-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/4.8R/qa.html b/website/content/en/releases/4.8R/qa.html index b4dd879765..1e3962d4cf 100644 --- a/website/content/en/releases/4.8R/qa.html +++ b/website/content/en/releases/4.8R/qa.html @@ -1,336 +1,336 @@ Testing Guide for 4.8-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.8-RELEASE

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.8-RELEASE 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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • OpenSSL. OpenSSL was updated to 0.9.7a. Please test any SSL consumers on your system to make sure there have been no regressions in functionality.

  • IPFilter has recently been updated to version 3.4.31 and has not yet been thoroughly tested in -STABLE.

  • Firewire

  • libc_r - A change has been made to fix libc_r in the case when a non-standard value of KVA_PAGES is used in the kernel. libc_r in general could use testing with real applications.

  • dlinfo() added - test your shared-library heavy ports to make sure there are no build problems.

  • ISC DHCP 3.0.1 RC11 has recently been added to 4.8RC. This version of the ISC DHCP client was used in 5.0-RELEASE, and should be well tested, but it was only recently made available to 4.X-STABLE users so it has not received much testing to date in that environment.

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

Known Issues

  • Disks attached to a Mylex controller are not seen by sysinstall. There is a problem because this module is loaded from the mfsroot floppy and the equivalent of a "camcontrol rescan" is not performed to discover disks after the module has loaded. Found by Julian. Fixed by scottl Mar 28.

  • GNOME2 does not work until the user manually runs 'fc-cache -f'. marcus@ has committed a fix to the port, murray@ has manually hacked some packages to test the proposed fixes, and kris@ will rebuild 150+ GNOME ports


diff --git a/website/content/en/releases/4.8R/relnotes.html b/website/content/en/releases/4.8R/relnotes.html index 7d760fe111..b5c2bd1b87 100644 --- a/website/content/en/releases/4.8R/relnotes.html +++ b/website/content/en/releases/4.8R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.8-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.8-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.8R/schedule.html b/website/content/en/releases/4.8R/schedule.html index c2e266a90c..97eee0cc0a 100644 --- a/website/content/en/releases/4.8R/schedule.html +++ b/website/content/en/releases/4.8R/schedule.html @@ -1,530 +1,530 @@ FreeBSD 4.8 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.8 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 4.8. 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 announcement16 Jan 200316 Jan 200316 Jan 200316 Jan 2003 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.8 release.
Another Reminder announcement7 Feb 20037 Feb 2003 10 Feb 2003 1 week reminder.
Another Reminder announcement14 Feb 200314 Feb 200314 Feb 200314 Feb 2003 Final reminder, with exact time that freeze begins.
4.8-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.
4.8-PRERELEASE15 Feb 200315 Feb 200315 Feb 200315 Feb 2003 newvers.sh, and release.ent updated.
FTP site updated 15 Feb 2003 unnecessary pkg_add -r works for 4.8-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.
4.8-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 4.8-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 4.8.
Update man.cgi on the website. 23 Mar 2003 28 Mar 2003 Make sure the 4.8 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
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.

diff --git a/website/content/en/releases/4.9R/announce.html b/website/content/en/releases/4.9R/announce.html index 390268d201..6e537a5d4b 100644 --- a/website/content/en/releases/4.9R/announce.html +++ b/website/content/en/releases/4.9R/announce.html @@ -1,452 +1,452 @@ FreeBSD 4.9-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9-RELEASE Announcement

Date: Tue, 28 Oct 2003 23:19:08 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: FreeBSD 4.9-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/4.9R/relnotes.html

http://www.FreeBSD.org/releases/4.9R/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 4.9-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 4.9 including The FreeBSD Mall, Compaq, Yahoo!, Sentex Communications, and NTT/Verio.

In addition to myself, the release engineering team for 4.9-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

diff --git a/website/content/en/releases/4.9R/hardware.html b/website/content/en/releases/4.9R/hardware.html index c88777ac30..a9f1a97c7a 100644 --- a/website/content/en/releases/4.9R/hardware.html +++ b/website/content/en/releases/4.9R/hardware.html @@ -1,276 +1,276 @@ FreeBSD 4.9-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/4.9R/installation.html b/website/content/en/releases/4.9R/installation.html index 9a22f2eb06..6f584efe4f 100644 --- a/website/content/en/releases/4.9R/installation.html +++ b/website/content/en/releases/4.9R/installation.html @@ -1,276 +1,276 @@ FreeBSD 4.9-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/4.9R/qa.html b/website/content/en/releases/4.9R/qa.html index bfff83b3f3..9ed4df286a 100644 --- a/website/content/en/releases/4.9R/qa.html +++ b/website/content/en/releases/4.9R/qa.html @@ -1,320 +1,320 @@ Testing Guide for 4.9-RELEASE
Skip site navigation (1) Skip section navigation (2)

Section Navigation

Testing Guide for 4.9-RELEASE

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.9-RELEASE 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:

  • The system has not regressed with respects to stability, correctness, interoperability, or performance of features present in prior releases.

  • New features result in the desired improvement in stability, correctness, interoperability, or performance.

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:

  • A bug affecting IPFW2 "limit" rules was fixed very late in the release cycle; other ipfw2 features should not be affected. We are interested in hearing any feedback about IFPW2 in 4.9-RC3.

  • The sysinstall(8) utility was updated to support multiple mail transfer agents (MTAs). As such, the familiar Network Services menu was modified to expose a new option entitled Mail.

  • The xl driver has recently been updated with full busdma support among other improvements. This driver will now work with large memory systems with PAE enabled.

  • Users with large memory configurations (>4G) should explore the recently added PAE support in 4.9-RELEASE.

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

Known Issues

  • The kernel hangs solidly during device configuration when certain SATA controllers are installed on the system. (patch)
  • 4.9-PRE panics reproducibly on a heavily loaded ata(4)-system. PR

diff --git a/website/content/en/releases/4.9R/relnotes.html b/website/content/en/releases/4.9R/relnotes.html index 57fb02b13b..b5da20bef2 100644 --- a/website/content/en/releases/4.9R/relnotes.html +++ b/website/content/en/releases/4.9R/relnotes.html @@ -1,276 +1,276 @@ FreeBSD 4.9-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/4.9R/schedule.html b/website/content/en/releases/4.9R/schedule.html index 90061337c3..34e0334201 100644 --- a/website/content/en/releases/4.9R/schedule.html +++ b/website/content/en/releases/4.9R/schedule.html @@ -1,542 +1,542 @@ FreeBSD 4.9 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 4.9. 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 announcement28 Jul 200328 Jul 200328 Jul 200328 Jul 2003 Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.9 release.
Another Reminder announcement18 Aug 200318 Aug 200318 Aug 200318 Aug 2003 1 week reminder.
Another Reminder announcement24 Aug 200324 Aug 200324 Aug 200324 Aug 2003 Final reminder, with exact time (GMT) that freeze begins.
4.9-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.
4.9-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 4.9-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.
4.9-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_4_9_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 4.9-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_4_9_0 tag for doc/. doc/ slush ends at this time.
RELENG_4_9 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 4.9.
Update man.cgi on the website. 18 Oct 2003 19 Oct 2003 Make sure the 4.9 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
src tree tagged. 21 Oct 2003 -- RELENG_4_9_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_4_9 branch.

Additional Information


diff --git a/website/content/en/releases/4.9R/todo.html b/website/content/en/releases/4.9R/todo.html index 855c6c4404..642fb46433 100644 --- a/website/content/en/releases/4.9R/todo.html +++ b/website/content/en/releases/4.9R/todo.html @@ -1,399 +1,399 @@ FreeBSD 4.9 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 4.9 Open Issues

Open Issues

This is a list of open issues that need to be resolved for FreeBSD 4.9. 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 4.9-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 4.9-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 John Baldwin ACPI will be provided as an optional component, turned off by default.

Desired Features for 4.9-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 4.9

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 4.9

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.

diff --git a/website/content/en/releases/5.0R/announce.html b/website/content/en/releases/5.0R/announce.html index fa4d9a7450..d86fc3ccd8 100644 --- a/website/content/en/releases/5.0R/announce.html +++ b/website/content/en/releases/5.0R/announce.html @@ -1,443 +1,443 @@ FreeBSD 5.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0-RELEASE Announcement

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:

  • UFS2, the second generation UFS filesystem, shatters the current 1TB filesystem barrier.
  • Background filesystem checking (bgfsck) and filesystem snapshots eliminate the need for downtime to do filesystem repair and backup tasks.
  • Experimental support for Mandatory Access Controls (MAC) provide an extensible and flexible means for administrators to define system security policies.
  • Fine-grained locking in the kernel paves the road for much higher efficiency of multi-processor systems.
  • Support for Bluetooth, ACPI, CardBus, IEEE 1394, and experimental hardware crypto acceleration keeps FreeBSD at the forefront of new technology.
  • The GCC 3.2.1 compiler provides the latest installment of the ever-improving GNU Compiler Collection.
  • GEOM, the extensible and flexible storage framework, and DEVFS, the device virtual filesystem, simplify storage and device management while opening the door for new enterprise storage technologies.
  • Support for the sparc64 and ia64 platforms expands FreeBSD's support of advanced 64-bit computing platforms.

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

diff --git a/website/content/en/releases/5.0R/hardware.html b/website/content/en/releases/5.0R/hardware.html index a666da43fa..50ebc73ed8 100644 --- a/website/content/en/releases/5.0R/hardware.html +++ b/website/content/en/releases/5.0R/hardware.html @@ -1,280 +1,280 @@ FreeBSD 5.0-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.0R/installation.html b/website/content/en/releases/5.0R/installation.html index 4d01f37b04..e3c2fbe199 100644 --- a/website/content/en/releases/5.0R/installation.html +++ b/website/content/en/releases/5.0R/installation.html @@ -1,279 +1,279 @@ FreeBSD 5.0-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.0R/relnotes.html b/website/content/en/releases/5.0R/relnotes.html index 33567871d4..cfce1e065e 100644 --- a/website/content/en/releases/5.0R/relnotes.html +++ b/website/content/en/releases/5.0R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 5.0-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.0R/schedule.html b/website/content/en/releases/5.0R/schedule.html index 6a7b5bfe36..41f947a1c4 100644 --- a/website/content/en/releases/5.0R/schedule.html +++ b/website/content/en/releases/5.0R/schedule.html @@ -1,451 +1,451 @@ FreeBSD 5.0 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0 Release Process

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.

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.

diff --git a/website/content/en/releases/5.0R/todo.html b/website/content/en/releases/5.0R/todo.html index 05cf48005b..7277891042 100644 --- a/website/content/en/releases/5.0R/todo.html +++ b/website/content/en/releases/5.0R/todo.html @@ -1,412 +1,412 @@ FreeBSD 5.0 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.0 Open Issues

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 Robert Drehmel 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 -- Chris Costello 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 -- Scott Long, Jeff Roberson 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 -- Sam Leffler 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 Murray Stokely 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).

diff --git a/website/content/en/releases/5.1R/announce.html b/website/content/en/releases/5.1R/announce.html index 5f0e22dd20..c4ea47afbf 100644 --- a/website/content/en/releases/5.1R/announce.html +++ b/website/content/en/releases/5.1R/announce.html @@ -1,485 +1,485 @@ FreeBSD 5.1-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1-RELEASE Announcement

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:

  • Experimental 1:1 and M:N thread libraries provide kernel support for efficient application multithreading.
  • Support for Physical Address Extensions enables Pentium Pro and higher CPUs to access up to 64GB of RAM.
  • Experimental Name Service Switch infrastructure allows enterprises to seamlessly integrate with LDAP and Active Directory services.
  • Enhanced "jail" management, allowing one server to provide many different "virtual machines" with reduced administrator workload.
  • New device drivers include support for IBM/Adaptec ServeRAID controllers, expanded support for USB 2.0 and USB Ethernet adapters, and Promise Serial ATA controllers.
  • Experimental support for the amd64 platform allows FreeBSD to run on single processor AMD Opteron systems.

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 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

diff --git a/website/content/en/releases/5.1R/hardware.html b/website/content/en/releases/5.1R/hardware.html index 184c97ec4b..64398b2db6 100644 --- a/website/content/en/releases/5.1R/hardware.html +++ b/website/content/en/releases/5.1R/hardware.html @@ -1,280 +1,280 @@ FreeBSD 5.1-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.1R/installation.html b/website/content/en/releases/5.1R/installation.html index ef390da6a2..71dd9ba839 100644 --- a/website/content/en/releases/5.1R/installation.html +++ b/website/content/en/releases/5.1R/installation.html @@ -1,279 +1,279 @@ FreeBSD 5.1-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.1R/relnotes.html b/website/content/en/releases/5.1R/relnotes.html index 45baa88ca6..8dc6e8a6ac 100644 --- a/website/content/en/releases/5.1R/relnotes.html +++ b/website/content/en/releases/5.1R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 5.1-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.1R/schedule.html b/website/content/en/releases/5.1R/schedule.html index 5b80889098..edbc4219c1 100644 --- a/website/content/en/releases/5.1R/schedule.html +++ b/website/content/en/releases/5.1R/schedule.html @@ -1,419 +1,419 @@ FreeBSD 5.1 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1 Release Process

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.

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 freeze5 May 20035 May 20035 May 20035 May 2003 The src/ code freeze for 5.1. Commits to HEAD require re@FreeBSD.org approval.
5.1-BETA5 May 200315 May 20035 May 200315 May 2003 5.1-BETA release of x86, alpha, sparc64, and ia64.
5.1-BETA219 May 200322 May 200319 May 200322 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 candidate30 May 20031 June 200330 May 20031 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-master5 June 20035 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.

diff --git a/website/content/en/releases/5.1R/todo.html b/website/content/en/releases/5.1R/todo.html index 03694abd16..dad1a4056c 100644 --- a/website/content/en/releases/5.1R/todo.html +++ b/website/content/en/releases/5.1R/todo.html @@ -1,355 +1,355 @@ FreeBSD 5.1 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.1 Open Issues

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 -- Robert Watson 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 -- Jacques Vidrine 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 -- -- Kris Kennaway 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.

diff --git a/website/content/en/releases/5.2.1R/announce.html b/website/content/en/releases/5.2.1R/announce.html index cd10472c09..5cc95e4b58 100644 --- a/website/content/en/releases/5.2.1R/announce.html +++ b/website/content/en/releases/5.2.1R/announce.html @@ -1,518 +1,518 @@ FreeBSD 5.2.1-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2.1-RELEASE Announcement

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:

  • Significantly improved ATA/IDE and SATA handling. Problems with timeouts, error recovery, and certain master/slave configurations have been largely addressed.
  • The kdeadmin3 package has been updated to fix the password database corruption found with the KUser tool.
  • Third-party NSS modules can now support groups with many users.
  • Multicast and promiscuous modes have been fixed in the 'sk' Ethernet driver, allowing it to operate in a DHCP environment.
  • Latest updates to the XFree86 4.3 server to protect against several published security vulnerabilities.

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

diff --git a/website/content/en/releases/5.2.1R/hardware.html b/website/content/en/releases/5.2.1R/hardware.html index 1b51425132..17218012c8 100644 --- a/website/content/en/releases/5.2.1R/hardware.html +++ b/website/content/en/releases/5.2.1R/hardware.html @@ -1,281 +1,281 @@ FreeBSD 5.2.1-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2.1-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.2.1R/installation.html b/website/content/en/releases/5.2.1R/installation.html index a4e51520a6..4e41f86eac 100644 --- a/website/content/en/releases/5.2.1R/installation.html +++ b/website/content/en/releases/5.2.1R/installation.html @@ -1,280 +1,280 @@ FreeBSD 5.2.1-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2.1-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.2.1R/relnotes.html b/website/content/en/releases/5.2.1R/relnotes.html index 5cea276fee..9972c70285 100644 --- a/website/content/en/releases/5.2.1R/relnotes.html +++ b/website/content/en/releases/5.2.1R/relnotes.html @@ -1,280 +1,280 @@ FreeBSD 5.2.1-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2.1-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.2R/announce.html b/website/content/en/releases/5.2R/announce.html index 7fd14e35e6..6593390ed2 100644 --- a/website/content/en/releases/5.2R/announce.html +++ b/website/content/en/releases/5.2R/announce.html @@ -1,520 +1,520 @@ FreeBSD 5.2-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2-RELEASE Announcement

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:

  • Full Tier-1 support for single and multiprocessor AMD Athlon64 and Opteron systems.
  • Dynamically linked root partition for a smaller installation footprint and better integration with the Name Service Switch subsystem.
  • New and improved driver support for IDE, SATA, and 802.11a/b/g devices, and significantly better integration with the ACPI power management subsystem.
  • Client support for the Network File System version 4 protocol.
  • Experimental first-stage support for multithreaded filtering and forwarding of IP traffic. This also provides the foundation for a fully multi-threaded network stack in the next release of FreeBSD.
  • In-box support for the latest Gnome 2.4 and KDE 3.1 desktops.

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

diff --git a/website/content/en/releases/5.2R/hardware.html b/website/content/en/releases/5.2R/hardware.html index ca6fc303de..0d8d9175db 100644 --- a/website/content/en/releases/5.2R/hardware.html +++ b/website/content/en/releases/5.2R/hardware.html @@ -1,281 +1,281 @@ FreeBSD 5.2-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.2R/installation.html b/website/content/en/releases/5.2R/installation.html index c3bcccd0d0..5e1e5c4090 100644 --- a/website/content/en/releases/5.2R/installation.html +++ b/website/content/en/releases/5.2R/installation.html @@ -1,280 +1,280 @@ FreeBSD 5.2-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.2R/relnotes.html b/website/content/en/releases/5.2R/relnotes.html index 95848274bb..d3584fff11 100644 --- a/website/content/en/releases/5.2R/relnotes.html +++ b/website/content/en/releases/5.2R/relnotes.html @@ -1,280 +1,280 @@ FreeBSD 5.2-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.2R/schedule.html b/website/content/en/releases/5.2R/schedule.html index 698fff166a..b1d5694eb5 100644 --- a/website/content/en/releases/5.2R/schedule.html +++ b/website/content/en/releases/5.2R/schedule.html @@ -1,457 +1,457 @@ FreeBSD 5.2 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2 Release Process

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 frozen17 Nov 200318 Nov 200317 Nov 200318 Nov 2003 Announce the src/ code freeze for 5.2 on the HEAD branch. Commits to HEAD require re@FreeBSD.org approval.
ports/ tree frozen17 Nov 200319 Nov 200317 Nov 200319 Nov 2003 Announce the ports/ code freeze for 5.2. Commits to ports/ require portmgr@FreeBSD.org approval.
Begin 5.2-BETA builds17 Nov 200324 Nov 200317 Nov 200324 Nov 2003 Begin building 5.2-BETA disc1 and disc2 for all Tier-1 platforms.
Release 5.2-BETA19 Nov 200326 Nov 200319 Nov 200326 Nov 2003 5.2-BETA tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
RELENG_5_2 branched1 Dec 20036 Dec 20031 Dec 20036 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_21 Dec 20036 Dec 20031 Dec 20036 Dec 2003 Turn off WITNESS, INVARIANTS, and malloc debugging options similar to what was done for 5.1.
Begin 5.2-RC1 builds1 Dec 20037 Dec 20031 Dec 20037 Dec 2003 Begin building 5.2-RC1 disc1 and disc2 for all Tier-1 platforms.
src/ unfrozen1 Dec 20036 Dec 20031 Dec 20036 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-RC13 Dec 200310 Dec 20033 Dec 200310 Dec 2003 5.2-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged3 Dec 20033 Dec 20033 Dec 20033 Dec 2003 Tentative date of RELEASE_5_2_0 tag for ports.
doc/ tree slush8 Dec 20039 Dec 20038 Dec 20039 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 builds19 Dec 200321 Dec 200319 Dec 200321 Dec 2003 Begin building 5.2-RC2 disc1 and disc2 for all Tier-1 platforms.
Release 5.2-RC221 Dec 200323 Dec 200321 Dec 200323 Dec 2003 5.2-RC2 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged12 Dec 200312 Dec 200312 Dec 200312 Dec 2003 Tag the doc/ tree with RELEASE_5_2_0.
Version numbers bumpedJan 2004Jan 11 2004Jan 2004Jan 11 2004 The files listed here are updated to reflect FreeBSD 5.2.
src/ tree taggedJan 2004Jan 11 2004Jan 2004Jan 11 2004 Tag the RELENG_5_2 branch with RELENG_5_2_0_RELEASE.
Begin 5.2-RELEASE buildsJan 2004Jan 11 2004Jan 2004Jan 11 2004 Start 5.2-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.orgJan 2004Jan 11 2004Jan 2004Jan 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-masterJan 2004Jan 11 2004Jan 2004Jan 11 2004 Release and packages uploaded to ftp-master.FreeBSD.org.
FreeBSD 5.2 AnnouncedJan 2004Jan 12 2004Jan 2004Jan 12 2004 FreeBSD 5.2 is announced to the mailing lists.
FreeBSD 5.2 Press ReleaseJan 2004Jan 12 2004Jan 2004Jan 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.

diff --git a/website/content/en/releases/5.2R/todo.html b/website/content/en/releases/5.2R/todo.html index 15ad0671d7..3613e62abb 100644 --- a/website/content/en/releases/5.2R/todo.html +++ b/website/content/en/releases/5.2R/todo.html @@ -1,508 +1,508 @@ FreeBSD 5.2 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.2 Open Issues

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 GiantIn progressIn progress Sam Leffler 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 SynchronizationIn progressIn progress Hajimu UMEMOTO 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 switchesNot doneNot done -- 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. Bosko Milekic has done substantial prototyping work, and should be coordinated with.
Run-time autoconfiguration of GBDE and related transformsNot doneNot done -- 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 alphaNot doneNot done Mark Peek gdb -k doesn't work on alpha

Documentation items desired for 5.2

- +
IssueStatusResponsibleDescription
Revise EAG Done Bruce A. Mah The Early Adopters Guide needs to be revised, hopefully for the last time, to reflect the state of 5.2.
Trim Hardware NotesIn progressIn progress Bruce A. Mah 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 issuesNeeds testingNeeds testing -- 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, MPsafetyNeeds testingNeeds testing Søren Schmidt New ATA model has arrived, supporting fine-grained locking, and more. Much testing is needed to ensure no regressions.
GPT support for sysinstallNeeds testingNeeds testing Marcel Moolenaar Sysinstall and libdisk has been overhauled to support the GPT partition scheme used on ia64.
Complete the APIC PCI interrupt routing supportNeeds testingNeeds testing John Baldwin 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 corruptionNeeds testingNeeds testing Søren Schmidt, Tor Egge 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 shutdownNeeds testingNeeds testing Nate Lawson 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 panicNeeds testingNeeds testing Mark Murray 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 problemsNeeds testingNeeds testing Greg Lehey 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 moduleNeeds testingNeeds testing John Baldwin 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 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 Unknown John Baldwin 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 enabledNeeds testingNeeds testing Doug White, Jeff Roberson 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.

diff --git a/website/content/en/releases/5.3R/announce.html b/website/content/en/releases/5.3R/announce.html index a9dd1d1501..2b128d4be6 100644 --- a/website/content/en/releases/5.3R/announce.html +++ b/website/content/en/releases/5.3R/announce.html @@ -1,506 +1,506 @@ FreeBSD 5.3-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3-RELEASE Announcement

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:

  • A binary compatibility interface has been introduced for the i386 platform that allows running Microsoft Windows NDIS network drivers natively in the kernel.

  • The network and socket subsystems are now multi-threaded and reentrant. This allows for much better use of SMP parallelism when processing and forwarding local and remote network traffic.

  • The development environment has been updated to GCC 3.4.2, Binutils 2.15, and GDB 6.1

  • The choices for graphical environments have been updated to include X.org 6.7, Gnome 2.6.2 and KDE 3.3.0.

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

diff --git a/website/content/en/releases/5.3R/errata_policy.html b/website/content/en/releases/5.3R/errata_policy.html index 641960fcc6..e7ad3cd361 100644 --- a/website/content/en/releases/5.3R/errata_policy.html +++ b/website/content/en/releases/5.3R/errata_policy.html @@ -1,297 +1,297 @@ FreeBSD 5.3 Errata Processing Policy
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3 Errata Processing Policy

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD 5.3.

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 5.3 and who has reviewed the fix.


diff --git a/website/content/en/releases/5.3R/hardware.html b/website/content/en/releases/5.3R/hardware.html index 4fb57ed9ce..dc61bee474 100644 --- a/website/content/en/releases/5.3R/hardware.html +++ b/website/content/en/releases/5.3R/hardware.html @@ -1,281 +1,281 @@ FreeBSD 5.3-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.3R/installation.html b/website/content/en/releases/5.3R/installation.html index c73d5c2867..fdddf509c9 100644 --- a/website/content/en/releases/5.3R/installation.html +++ b/website/content/en/releases/5.3R/installation.html @@ -1,280 +1,280 @@ FreeBSD 5.3-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.3R/policy.html b/website/content/en/releases/5.3R/policy.html index 5279c09fee..ec83135706 100644 --- a/website/content/en/releases/5.3R/policy.html +++ b/website/content/en/releases/5.3R/policy.html @@ -1,389 +1,389 @@ FreeBSD 5.3 Code Freeze Policy
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3 Code Freeze Policy

Introduction

The following is the general policy for submitting and granting approvals for committing during the code freeze for FreeBSD 5.3. 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.


diff --git a/website/content/en/releases/5.3R/relnotes.html b/website/content/en/releases/5.3R/relnotes.html index 400575874b..c3997b93b3 100644 --- a/website/content/en/releases/5.3R/relnotes.html +++ b/website/content/en/releases/5.3R/relnotes.html @@ -1,280 +1,280 @@ FreeBSD 5.3-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.3R/schedule.html b/website/content/en/releases/5.3R/schedule.html index a1339cefc6..f3c99f6ee2 100644 --- a/website/content/en/releases/5.3R/schedule.html +++ b/website/content/en/releases/5.3R/schedule.html @@ -1,523 +1,523 @@ FreeBSD 5.3 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 5.3. 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.3 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 Freeze15 Aug 200415 Aug 200415 Aug 200415 Aug 2004 Someone from portmgr@ should email for the two week long ports freeze and tagging of the ports tree.
src/ tree frozen16 Aug 200416 Aug 200416 Aug 200416 Aug 2004 Announce the src/ code freeze for 5.3. Commits to the HEAD branch will be locked until the RELENG_5 branch is created.
RELENG_5 branch creation16 Aug 200417 Aug 200416 Aug 200417 Aug 2004 Create the RELENG_5 branch. Commits to this branch will require Release Engineering approval until the RELENG_5_3 branch is created.
Begin 5.3-BETA1 builds16 Aug 200420 Aug 200416 Aug 200420 Aug 2004 Begin building 5.3-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 5.3-BETA120 Aug 200422 Aug 200420 Aug 200422 Aug 2004 5.3-BETA1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Build and release 5.3-BETA227 Aug 200429 Aug 200427 Aug 200429 Aug 2004 5.3-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Build and release 5.3-BETA33 Sep 20045 Sep 20043 Sep 20045 Sep 2004 5.3-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree frozen3 Sep 20043 Sep 20043 Sep 20043 Sep 2004 Only approved commits will be permitted to the ports/ tree during the freeze.
Build and release 5.3-BETA410 Sep 200412 Sep 200410 Sep 200412 Sep 2004 5.3-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Build and release 5.3-BETA517 Sep 200420 Sep 200417 Sep 200420 Sep 2004 5.3-BETA5 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged17 Sep 200411 Oct 200417 Sep 200411 Oct 2004 RELEASE_5_3_0 tag for ports/.
Ports tree unfrozen17 Sep 200411 Oct 200417 Sep 200411 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 5.3-RELEASE.
Final package build starts17 Sep 200411 Oct 200417 Sep 200411 Oct 2004 The ports cluster and pointyhat build final packages.
Turn off debugging for RELENG_517 Sep 20047 Sep 200417 Sep 20047 Sep 2004 Turn off WITNESS, INVARIANTS, and malloc debugging options. This will be the default for all RELENG_5 releases.
doc/ tree slush17 Sep 200417 Sep 200417 Sep 200417 Sep 2004 Announce the doc/ slush for 5.3. 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 5.3-BETA624 Sep 200426 Sep 200424 Sep 200426 Sep 2004 5.3-BETA6 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged24 Sep 200426 Sep 200424 Sep 200426 Sep 2004 Tag the doc/ tree with RELEASE_5_3_0.
Build and release 5.3-BETA71 Oct 20043 Oct 20041 Oct 20043 Oct 2004 5.3-BETA7 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
RELENG_5_3 branched8 Oct 200416 Oct 20048 Oct 200416 Oct 2004 Branch of src/ from RELENG_5 for the release.
src/ unfrozen8 Oct 200416 Oct 20048 Oct 200416 Oct 2004 Unfreeze RELENG_5 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Build and release 5.3-RC117 Oct 200419 Oct 200417 Oct 200419 Oct 2004 5.3-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Version numbers bumped22 Oct 200424 Oct 200422 Oct 200424 Oct 2004 The files listed here are updated to reflect FreeBSD 5.3.
src/ tree tagged22 Oct 200424 Oct 200422 Oct 200424 Oct 2004 Tag the RELENG_5_3 branch with RELENG_5_3_0_RELEASE.
Begin 5.3-RELEASE builds5 Nov 20044 Nov 20045 Nov 20044 Nov 2004 Start 5.3-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org5 Nov 20045 Nov 20045 Nov 20045 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-master5 Nov 20046 Nov 20045 Nov 20046 Nov 2004 Release and packages uploaded to ftp-master.FreeBSD.org.
FreeBSD 5.3 Announced5 Nov 20046 Nov 20045 Nov 20046 Nov 2004 FreeBSD 5.3 is announced to the mailing lists.
FreeBSD 5.3 Press Release5 Nov 20046 Nov 20045 Nov 20046 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.

diff --git a/website/content/en/releases/5.3R/todo.html b/website/content/en/releases/5.3R/todo.html index 974d90ccc9..273a7c06b0 100644 --- a/website/content/en/releases/5.3R/todo.html +++ b/website/content/en/releases/5.3R/todo.html @@ -1,860 +1,860 @@ FreeBSD 5.3 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.3 Open Issues

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)In progressIn progress John-Mark Gurney 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 supportIn progressIn progress David Xu, Marcel Moolenaar 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 sparc64In progressIn progress Ken Smith 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. Dag-Erling Smørgrav had prototype patches; Robert Drehmel is developing and testing patches now. Support for system call tracing has been added to ptrace().
FAST_IPSEC and KAME compatibilityNot doneNot done -- 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 infrastructureNot doneNot done Peter Wemm 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. Peter Wemm has done some initial prototyping, and should be contacted before starting on this work.
Race conditions in truss Errata candidate Robert Drehmel 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 LORNot doneNot done -- The LOR reported in PR kern/55175 needs to be fixed. Filedesc locking needs to be heavily reviewed in general.
KSE support for alphaIn progressIn progress Marcel Moolenaar Userland bits implemented, kernel bits not implemented.
CAM lockingIn progressIn progress Scott Long, Justin T. 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-30Not doneNot done -- When running syscons on an Ultra-30 with Creator-3D typing characters on the keyboard produces garbage. Problem reported by Kris Kennaway. 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 Done Gavin Atkinson, Bruce A. Mah 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 Done Simon L. B. Nielsen, Christian 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 Done Simon L. B. Nielsen 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 Done Marc Fonvieille This section is outdated, some rewrites are needed for 5.3-RELEASE.
References:
doc/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml rev.1.94
FDP documentations related pcm(4)Not doneNot done -- With the snd(4) and pcm(4) drivers changes, documentations (FAQ) regarding the use of these drivers need an update.
Early Adopter's Guide Done Bruce A. Mah, Tom Rhodes 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 NotesNot doneNot done Tom Rhodes 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 Done Ken Tom, Marc Fonvieille Update the X11 chapter of the Handbook for X.Org's X11 server.
References:
books/handbook/config/chapter.xml rev.1.147
rc.d scripts Done Tom Rhodes 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.xml rev.1.170
books/handbook/config/chapter.xml rev.1.172
Handbook's kernel configuration chapter Done Ceri Davies Chapter 8 must be updated to match 5.3-RELEASE.
References:
docs/70674 (closed)
books/handbook/kernelconfig/chapter.xml rev.1.135
Handbook's IPsec sectionNot doneNot done -- 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 chapterNot doneNot done -- Vinum chapter needs to be revised for 5.X systems.

Testing focuses for 5.3-RELEASE

- + - + - - + + - + - + - + - + - + - + - + - + - +
IssueStatusResponsibleDescription
KSE as the default threads libraryNeeds testingNeeds testing David Xu, Daniel Eischen 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 platformsNeeds testingNeeds testing David O'Brien Binutils needs updating in order to support new platforms, newer GDB versions, and Thread Local Storage.
gcc 3.3 floating point alignment regressionNeeds testing Needs testing  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 Done Robert Watson Jun Kuriyama has reported a failed locking assertion with IPv6 TCP notifications. This problem is believed to be corrected.
Per-platform Thread-Local StorageNeeds testingNeeds testing Doug Rabson, Marcel Moolenaar 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 loadNeeds testingNeeds testing Doug White, Alan L. Cox High load on SMP systems appears to result in a hard hang related to VM IPI. Doug White 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 GiantNeeds testingNeeds testing Robert Watson 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 amd64Needs testingNeeds testing David O'Brien, Ian Dowse 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 sparc64Needs testingNeeds testing Søren Schmidt, Scott Long 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 Done Brooks Davis 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" Done Robert Watson 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 Done Max Laier 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 detachNeeds testingNeeds testing Warner Losh, Scott Long 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 Done Robert Watson, Sam Leffler 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 Done Doug Barton, Dag-Erling Smørgrav, Tom Rhodes 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 problemsNeeds testingNeeds testing Philip Paeps 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 threadsNeeds testingNeeds testing Scott Long, Julian Elischer 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 Done Doug White Jun Kuriyama has reported problems with NFS over IPv6 not functioning correctly as of the improved NFS support for disconnection changes. Doug White 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() Done Robert Watson 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) Done Robert Watson 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 Done Robert Watson, Christian S.J. Peron 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 Done Robert Watson, Brian F. Feldman 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 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) Done Robert Watson, John-Mark Gurney 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 Done David Xu 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 Done Alfred Perlstein 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 SACKNeeds testingNeeds testing George V. Neville-Neil, Robert Watson, Scott Long 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.

diff --git a/website/content/en/releases/5.4R/announce.html b/website/content/en/releases/5.4R/announce.html index 68973e2f57..a8f7d77783 100644 --- a/website/content/en/releases/5.4R/announce.html +++ b/website/content/en/releases/5.4R/announce.html @@ -1,516 +1,516 @@ FreeBSD 5.4-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4-RELEASE Announcement

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

diff --git a/website/content/en/releases/5.4R/errata_policy.html b/website/content/en/releases/5.4R/errata_policy.html index 26d278e663..05fd788d61 100644 --- a/website/content/en/releases/5.4R/errata_policy.html +++ b/website/content/en/releases/5.4R/errata_policy.html @@ -1,297 +1,297 @@ FreeBSD 5.4 Errata Processing Policy
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4 Errata Processing Policy

Introduction

The following is the general policy for submitting requests to have Errata Fixes applied to FreeBSD 5.4.

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 5.4 and who has reviewed the fix.


diff --git a/website/content/en/releases/5.4R/hardware.html b/website/content/en/releases/5.4R/hardware.html index 7cbca8b125..d1123ddeb3 100644 --- a/website/content/en/releases/5.4R/hardware.html +++ b/website/content/en/releases/5.4R/hardware.html @@ -1,281 +1,281 @@ FreeBSD 5.4-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4-RELEASE Hardware Notes

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.


diff --git a/website/content/en/releases/5.4R/installation.html b/website/content/en/releases/5.4R/installation.html index e34969c063..83119f8631 100644 --- a/website/content/en/releases/5.4R/installation.html +++ b/website/content/en/releases/5.4R/installation.html @@ -1,280 +1,280 @@ FreeBSD 5.4-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4-RELEASE Installation Notes

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.


diff --git a/website/content/en/releases/5.4R/relnotes.html b/website/content/en/releases/5.4R/relnotes.html index 5014e516e6..23ad18b68d 100644 --- a/website/content/en/releases/5.4R/relnotes.html +++ b/website/content/en/releases/5.4R/relnotes.html @@ -1,280 +1,280 @@ FreeBSD 5.4-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4-RELEASE Release Notes

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.


diff --git a/website/content/en/releases/5.4R/schedule.html b/website/content/en/releases/5.4R/schedule.html index 6f956093bb..a485771837 100644 --- a/website/content/en/releases/5.4R/schedule.html +++ b/website/content/en/releases/5.4R/schedule.html @@ -1,570 +1,570 @@ FreeBSD 5.4 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 5.4. 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 announcement31 Jan 200531 Jan 200531 Jan 200531 Jan 2005 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 5.4 release.
Announce the Ports Freeze24 Feb 200524 Feb 200524 Feb 200524 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.
5.4-PRERELEASE23 Feb 200524 Feb 200523 Feb 200524 Feb 2005 newvers.sh updated.
Code freeze begins2 Mar 20053 Mar 20052 Mar 20053 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.
5.4-PRERELEASE
5.4-BETA1		4 Mar 200520 Mar 20054 Mar 200520 Mar 2005 First public test release build. Note that the release build name is 5.4-BETA1 but newvers.sh RELEASE name remains 5.4-PRERELEASE. This is because the name BETA often confuses the users who are using the STABLE branch.
Announce doc/ tree slush14 Mar 200525 Mar 200514 Mar 200525 Mar 2005 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen21 Mar 200521 Mar 200521 Mar 200521 Mar 2005 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush24 Mar 2005
- 2 Apr 2005		2 Apr 2005
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 200528 Mar 2005
+ 11 Apr 2005		12 Apr 2005 Version number bumps for doc/ subtree. RELEASE_5_4_0 tag for doc/. doc/ slush ends at this time.
RELENG_5_4 branch31 Mar 20053 Apr 200531 Mar 20053 Apr 2005 The release branch is created. Update newvers.sh and release.ent on various branches involved.
Unfreeze the tree31 Mar 20053 Apr 200531 Mar 20053 Apr 2005 Announcement to developers explaining that commits to RELENG_5 no longer require approval. Also note the policy for commits to the RELENG_5_4 branch.
5.4-RC131 Mar 20053 Apr 200531 Mar 20053 Apr 2005 newvers.sh and release.ent updated.
Ports tree tagged31 Mar 20052 Apr 200531 Mar 20052 Apr 2005 RELEASE_5_4_0 tag for ports/.
Ports tree unfrozen31 Mar 20052 Apr 200531 Mar 20052 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 5.4-RELEASE.
Final package build starts31 Mar 200531 Mar 2005 -- The ports cluster and pointyhat build final packages.
First release candidate2 Apr 20055 Apr 20052 Apr 20055 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 -stable2 Apr 20055 Apr 20052 Apr 20055 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded.
Second release candidate9 Apr 20059 Apr 20059 Apr 20059 Apr 2005 Note: the release date of this candidate depends on the user experience with RC1.
Heads up to -stable9 Apr 200511 Apr 20059 Apr 200511 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded.
Third release candidate16 Apr 200516 Apr 200516 Apr 200516 Apr 2005 Note: the release date of this candidate depends on the user experience with RC2.
Heads up to -stable16 Apr 200518 Apr 200516 Apr 200518 Apr 2005 A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded.
Fourth release candidate30 Apr 20052 May 200530 Apr 20052 May 2005 Note: This is the final release candidate.
Heads up to -stable1 May 20052 May 20051 May 20052 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 20056 May 20056 May 20056 May 2005 The files listed here are updated to reflect the fact that this is FreeBSD 5.4.
src tree tagged.6 May 20056 May 20056 May 20056 May 2005 RELENG_5_4_0_RELEASE tag for src/.
Final builds.6 May 20056 May 20056 May 20056 May 2005 Final builds for all architectures in a pristine environment.
Warn mirror-announce@FreeBSD.org6 May 20056 May 20056 May 20056 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 20057 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 20059 May 2005 -- Make sure the 5.4 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml.
Announcement9 May 20059 May 2005 -- Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam17 May 200517 May 2005 -- RELENG_5_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/5.4R/todo.html b/website/content/en/releases/5.4R/todo.html index b254b1aef0..afdad535ce 100644 --- a/website/content/en/releases/5.4R/todo.html +++ b/website/content/en/releases/5.4R/todo.html @@ -1,484 +1,484 @@ FreeBSD 5.4 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.4 Open Issues

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 LockIn progressIn progress George V. Neville-Neil 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 MPSAFEIn progressIn progress -- 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 LockIn progressIn progress Robert Watson 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 loadIn progressIn progress Alan L. Cox 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 workNot doneNot done -- There are reports of problems getting dumps after panics.
fix for ttywakeup panicIn progressIn progress Doug White 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 Done Jeff Roberson File descriptor locking needs to be merged back from HEAD.
IPFilter mpsafe fixes Done Robert Watson IPFilter is currently not mpsafe but doesn't run with Giant.
Update sysinstall to handle separate packages CD Done John Baldwin Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11
busdma fixes Done Scott Long More work is needed on busdma to fix bounce buffer problems.
AMR driver MPSAFE Done Scott Long Making the AMR driver MPSAFE will greatly increase its performance.
CARP support Done Gleb Smirnoff Common Address Redundancy Protocol allows multiple hosts on the same local network to share a set of IP addresses.
kstack overflows in softupdates 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 Done Ken Smith 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 Done Jeff Roberson See PR kern/78664.
Deadlock under heavy interrupt load on MP Opteron systems Done Doug White A deadlock related to delivering IPIs on AMD 64-bit processors has been identified.
SCHED_ULE update Done Jeff Roberson 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.

diff --git a/website/content/en/releases/5.5R/announce.html b/website/content/en/releases/5.5R/announce.html index a3d0388a4b..72d884ea86 100644 --- a/website/content/en/releases/5.5R/announce.html +++ b/website/content/en/releases/5.5R/announce.html @@ -1,495 +1,495 @@ FreeBSD 5.5-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5-RELEASE Announcement

Date: Thu, 25 May 2006 14:00:13 -0400
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 5.5 Released

It is my great pleasure and privilege to announce the availability of FreeBSD 5.5-RELEASE. Work done between the 5.4-RELEASE and this release has mostly been bugfixes. Some ``vendor supplied'' software has also been updated, mostly due to security concerns (specifically BIND and sendmail).

This is the last planned release on the 5-STABLE branch. The FreeBSD development community is currently focusing its efforts on the 6-STABLE and CURRENT codelines. No new major features are planned for the 5-STABLE branch, although minor updates and bugfixes may be merged at the discretion of individual developers. The FreeBSD security team will support the FreeBSD 5.5-RELEASE-based security branch with advisories and security patches until the end-of-life date documented at http://security.freebsd.org/ (as of this writing, May 31, 2008).

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

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

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

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

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

Availability

FreeBSD 5.5-RELEASE supports the amd64, i386, pc98, alpha, and sparc64 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.5 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 and SHA256 checksums for the release images are included at the bottom of this message.

BitTorrent

5.5-RELEASE ISOs are not available via BitTorrent at this time. They may be made available in the future on an on-demand basis.

FTP

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

FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, 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.5 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Sentex Communications, and Copan Systems.

The release engineering team for 5.5-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Doug White <dwhite@FreeBSD.org> Release Engineering
Maxime Henrion <mux@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org> Documentation
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
Kiril Ponomarew <krion@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org> Security Officer

CD Image Checksums

MD5 (5.5-RELEASE-alpha-bootonly.iso) = 4de66e8aeb7d3842f36dcbd93834acaa
 MD5 (5.5-RELEASE-alpha-disc1.iso) = 618fc2622d1e41f7b75a38b06eb6a8ae
 MD5 (5.5-RELEASE-alpha-disc2.iso) = d169bbcb7870de8c54dbcdb39b0a3967
 
 MD5 (5.5-RELEASE-amd64-bootonly.iso) = 2d79d5b7cd032b004305c0a8d6d72ce3
 MD5 (5.5-RELEASE-amd64-disc1.iso) = dcaa38041be2735c2c9e8159640045b2
 MD5 (5.5-RELEASE-amd64-disc2.iso) = 38d5ff06cb1dea9761cdd6f6fa39138f
 
 MD5 (5.5-RELEASE-i386-bootonly.iso) = 331e1aa238f595cc913c697ce71fc4f3
 MD5 (5.5-RELEASE-i386-disc1.iso) = c66d2ff89d8177b31417f8752eadf6a8
 MD5 (5.5-RELEASE-i386-disc2.iso) = 91508e819b4efcfda9b900f57aace472
 
 MD5 (5.5-RELEASE-pc98-disc1.iso) = 7e14250d9cf44a9964fe45c1cca8b782
 
 MD5 (5.5-RELEASE-sparc64-bootonly.iso) = 7eaa9db570cde6b36f6d6734520fdd3a
 MD5 (5.5-RELEASE-sparc64-disc1.iso) = 59be492e648d56f9c046459776303108
 MD5 (5.5-RELEASE-sparc64-disc2.iso) = 35c393b4129b09fc16adc66a7180a23c
 
 SHA256 (5.5-RELEASE-amd64-bootonly.iso) = 36826ae8e1c2bdfe011b1b9597f5f2406f3d6bdc7e5fdfa4ec75a12652a1a51d
 SHA256 (5.5-RELEASE-amd64-disc1.iso) = f71eedf18ab24d973c938b473ca127018eb87ab1d1b4c96a5d8d1e9cd8f261d3
 SHA256 (5.5-RELEASE-amd64-disc2.iso) = 60daae915430e60a02d577ad0f409de6f011d4ac102ea6f2c332e2c24fad9340
 
 SHA256 (5.5-RELEASE-i386-bootonly.iso) = b9f052d2f0d2f3a9924354c0ad16c3ffda286562dbe29a28ce74a75c7b4c710c
 SHA256 (5.5-RELEASE-i386-disc1.iso) = 40d41ec7b567e7952d0f85729f340d409911368808256dae123ff1b97155c1ae
 SHA256 (5.5-RELEASE-i386-disc2.iso) = f561695f7c6bf673a1b84d0f8480d181aa3eac73cd2a14ce3d99d51f580eb42e
 
 SHA256 (5.5-RELEASE-pc98-disc1.iso) = 44526391702a21332bb5844ef2d6cf85b08447eec00dde62f930b032ee29b42d
 
 SHA256 (5.5-RELEASE-sparc64-bootonly.iso) = 7157e8ad27d8c285addf784589ed69043c4c10bff808f7a7ce6a81073c89c37f
 SHA256 (5.5-RELEASE-sparc64-disc1.iso) = 4d14d0547fc2bdf92c5def07f81351693c85039e5b4b05a5da89d1ca73cb577a
 SHA256 (5.5-RELEASE-sparc64-disc2.iso) = d4d3322d333d439e2f87cfc6476af45d8869ec9d2b5bc377bd8c89e7d43b2b4c

diff --git a/website/content/en/releases/5.5R/approvals.html b/website/content/en/releases/5.5R/approvals.html index 3cb710882c..a06192aa6d 100644 --- a/website/content/en/releases/5.5R/approvals.html +++ b/website/content/en/releases/5.5R/approvals.html @@ -1,293 +1,293 @@ FreeBSD 5.5 Commit Approvals
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5 Commit Approvals

Introduction

The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.

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.

Approval List

Committer Area Expiration

Additional Information


diff --git a/website/content/en/releases/5.5R/hardware.html b/website/content/en/releases/5.5R/hardware.html index d8bc6d94fb..a683a65ce1 100644 --- a/website/content/en/releases/5.5R/hardware.html +++ b/website/content/en/releases/5.5R/hardware.html @@ -1,280 +1,280 @@ FreeBSD 5.5-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5-RELEASE Hardware Notes

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.5-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/5.5R/installation.html b/website/content/en/releases/5.5R/installation.html index 2248271a67..53b94afdd5 100644 --- a/website/content/en/releases/5.5R/installation.html +++ b/website/content/en/releases/5.5R/installation.html @@ -1,279 +1,279 @@ FreeBSD 5.5-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5-RELEASE Installation Notes

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.5-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/5.5R/relnotes.html b/website/content/en/releases/5.5R/relnotes.html index 1e07f2d904..4c0f7aee09 100644 --- a/website/content/en/releases/5.5R/relnotes.html +++ b/website/content/en/releases/5.5R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 5.5-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5-RELEASE Release Notes

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.5-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/5.5R/schedule.html b/website/content/en/releases/5.5R/schedule.html index 06d0edccae..ca7dc0f013 100644 --- a/website/content/en/releases/5.5R/schedule.html +++ b/website/content/en/releases/5.5R/schedule.html @@ -1,549 +1,549 @@ FreeBSD 5.5 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 5.5. 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 --25 January 200625 January 2006 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 5.5 release.
Code freeze begins31 January 200631 January 200631 January 200631 January 2006 After this date, all commits to HEAD 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.
Announce the Ports Freeze --5 February 20065 February 2006 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Begin 5.5-BETA1 builds5 February 20065 February 20065 February 20065 February 2006 Begin building the first public test release build for all Tier-1 platforms.
Release 5.5-BETA15 February 20065 February 20065 February 20065 February 2006 5.5-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 5.5-BETA2 builds19 February 200616 February 200619 February 200616 February 2006 Begin building the second public test release build for all Tier-1 platforms.
Release 5.5-BETA219 February 200620 February 200619 February 200620 February 2006 5.5-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree frozen20 February 200623 February 200620 February 200623 February 2006 Only approved commits will be permitted to the ports/ tree during the freeze.
Begin 5.5-BETA3 builds5 March 20061 March 20065 March 20061 March 2006 Begin building the third public test release build for all Tier-1 platforms.
Release 5.5-BETA35 March 20065 March 20065 March 20065 March 2006 5.5-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Announce doc/ tree slush6 March 20066 March 20066 March 20066 March 2006 Notification of the impending doc/ tree slush should be sent to doc@.
Begin 5.5-BETA4 builds --14 March 200614 March 2006 Begin building the fourth public test release build for all Tier-1 platforms.
Release 5.5-BETA4 --14 March 200614 March 2006 5.5-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged6 March 200614 March 20066 March 200614 March 2006 RELEASE_5_5_0 tag for ports/.
Ports tree unfrozen6 March 200614 March 20066 March 200614 March 2006 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 5.5-RELEASE.
Final package build starts TBD -- The ports cluster and pointyhat build final packages.
doc/ tree slush10 March 20067 April 200610 March 20067 April 2006 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.13 March 200621 May 200613 March 200621 May 2006 Version number bumps for doc/ subtree. RELEASE_5_5_0 tag for doc/. doc/ slush ends at this time.
RELENG_5_5 branch19 March 2006
- 12 May 2006		12 May 200619 March 2006
+ 12 May 2006		12 May 2006 The new major version branch is created. Update newvers.sh and release.ent on various branches involved.
src/ unfrozen TBD -- Unfreeze RELENG_5 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Build 5.5-RC119 March 2006
- 14 May 2006		13 May 200619 March 2006
+ 14 May 2006		13 May 2006 Begin building the first release candidate build for all Tier-1 platforms.
Release 5.5-RC119 March 2006
- 14 May 2006		16 May 200619 March 2006
+ 14 May 2006		16 May 2006 5.5-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org.
Version numbers bumped31 March 2006
- 20 May 2006		12 May 200631 March 2006
+ 20 May 2006		12 May 2006 The files listed here are updated to reflect FreeBSD 5.5.
src/ tree tagged31 March 2006
- 20 May 2006		22 May 200631 March 2006
+ 20 May 2006		22 May 2006 Tag the RELENG_5_5 branch with RELENG_5_5_0_RELEASE.
Begin 5.5-RELEASE builds31 March 2006
- 20 May 2006		22 May 200631 March 2006
+ 20 May 2006		22 May 2006 Start 5.5-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org31 March 2006
- 20 May 2006		23 May 200631 March 2006
+ 20 May 2006		23 May 2006 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-master2 April 2006
- 21 May 2006		24 May 20062 April 2006
+ 21 May 2006		24 May 2006 Release and packages uploaded to ftp-master.FreeBSD.org.
Announcement3 April 2006
- 22 May 2006		25 May 20063 April 2006
+ 22 May 2006		25 May 2006 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD31 May 200631 May 2006 RELENG_5_5 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/5.5R/todo.html b/website/content/en/releases/5.5R/todo.html index aa8b5f9ea7..399a44c0bf 100644 --- a/website/content/en/releases/5.5R/todo.html +++ b/website/content/en/releases/5.5R/todo.html @@ -1,338 +1,338 @@ FreeBSD 5.5 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 5.5 Open Issues

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

Show stopper defects for 5.5-RELEASE

Issue Status Responsible Description

Required features for 5.5-RELEASE

Issue Status Responsible Description

Desired features for 5.5-RELEASE

Issue Status Responsible Description

Documentation items that must be resolved for 5.5

Issue Status Responsible Description

Testing foci for 5.5-RELEASE

Issue Status Responsible Description

diff --git a/website/content/en/releases/6.0R/announce.html b/website/content/en/releases/6.0R/announce.html index 3f27bc88b8..f53c52b1ef 100644 --- a/website/content/en/releases/6.0R/announce.html +++ b/website/content/en/releases/6.0R/announce.html @@ -1,529 +1,529 @@ FreeBSD 6.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0-RELEASE Announcement

Date: Fri, 04 Nov 2005 08:40:04 -0700
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 6.0 Released

It is my great pleasure and privilege to announce the availability of FreeBSD 6.0-RELEASE. This release is the next step in delivering the high performance and enterprise features that have been under development in the FreeBSD 5.x series for that last several years. Some of the many changes since 5.4 include:

  • Significant performance improvements to the filesystem and direct disk access layers of the OS. The filesystem is now multithreaded and can take full advantage of multiple CPU systems.

  • Expanded support for wireless networking adapters and new support for the WPA wireless security protocol.

  • Experimental support for the PowerPC platform.

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/6.0R/relnotes.html
http://www.FreeBSD.org/releases/6.0R/errata.html

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

http://www.FreeBSD.org/releng

Availability

FreeBSD 6.0-RELEASE supports the i386, pc98, alpha, sparc64, amd64, powerpc, 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 6.0 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 and SHA256 checksums for the release images are included at the bottom of this message.

Bittorrent

The FreeBSD project encourages the use of BitTorrent for distributing the release ISO images. A collection of torrent files to download the images is available at:

ftp://ftp.freebsd.org/pub/FreeBSD/torrents/6.0-RELEASE

FTP

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

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 6.0 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Sentex Communications, and SPARTA.

The release engineering team for 6.0-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering, I386 and AMD64 Release Building
Ken Smith <kensmith@FreeBSD.org> Sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Doug White <dwhite@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
Peter Grehan <grehan@FreeBSD.org> PowerPC Release Building
Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org> Security Officer

CD Image Checksums

For Alpha:

MD5 (6.0-RELEASE-alpha-bootonly.iso) = 98499535a511e85ae5afe4542b6fd7f3
 MD5 (6.0-RELEASE-alpha-disc1.iso) = c8f316202b221035086a08709bc011a6
 SHA256 (6.0-RELEASE-alpha-bootonly.iso) = 2fcc391dc123baaeaba34f4f925a22223f209d63260d9283d6ba77227bb23dbd
 SHA256 (6.0-RELEASE-alpha-disc1.iso) = c71d06359a0dc0c6efb3aa9b40c80df62e359716454aaaf672556638b81b498a

For amd64:

MD5 (6.0-RELEASE-amd64-bootonly.iso) = 4328c66c900ef6e6ddc1daf9dd8b731f
 MD5 (6.0-RELEASE-amd64-disc1.iso) = a4e427adaa2bfef868e2bc62d57fbf8d
 MD5 (6.0-RELEASE-amd64-disc2.iso) = 2f46d344681c1a82b146b3ed1df68e61
 SHA256 (6.0-RELEASE-amd64-bootonly.iso) = afa6eb02845185d1968cce02e752614394f8b9c09fc519ae1b61356c583d6df0
 SHA256 (6.0-RELEASE-amd64-disc1.iso) = 449b08c98acc73508219e2a19de0787334fd9237123346b2c7949c3009540170
 SHA256 (6.0-RELEASE-amd64-disc2.iso) = 25c3e3da1f2e0a0ecb8a23dd78f35f969cc17eba6072db6a41edab3ecfc2e2d4

For i386:

MD5 (6.0-RELEASE-i386-bootonly.iso) = d71afd22be9ea7fe28e026575cbbb878
 MD5 (6.0-RELEASE-i386-disc1.iso) = cfe3c1a2b4991edd6a294ca9b422b9d5
 MD5 (6.0-RELEASE-i386-disc2.iso) = 1003806d98cd60ba4b672f4ca546ced3
 SHA256 (6.0-RELEASE-i386-bootonly.iso) = 97ee1c1ffc2774c1c2cdc63ed8820fd3aedf7f0b5bb6273b87e40a05e00b2d1f
 SHA256 (6.0-RELEASE-i386-disc1.iso) = 0ad601dae704e941beb7d4617bf96b04055849a24835275c716f518eee7a12f1
 SHA256 (6.0-RELEASE-i386-disc2.iso) = 1a82de4ff6733ee782da8df80cf66cf47266eefdb9f76cd19bf08063539c1aa0

For ia64:

MD5 (6.0-RELEASE-ia64-bootonly.iso) = 3246ae501dac0067d4085e216fcf376a
 MD5 (6.0-RELEASE-ia64-disc1.iso) = e2fbb0e3b19a26e0b2e72bb8c13a57e9
 MD5 (6.0-RELEASE-ia64-disc2.iso) = 2f5bbe94ec1438ecaa0b08915500d605
 MD5 (6.0-RELEASE-ia64-livefs.iso) = cb227ea0e1db6873dbcb56249bf45418
 SHA256 (6.0-RELEASE-ia64-bootonly.iso) = 9e6d502f32b5dc2cfc3d2af69d1512eb0476e6320851b3ecb5918977780c3cda
 SHA256 (6.0-RELEASE-ia64-disc1.iso) = fd9aaee8417a1701ebc72db6cd86d15f23738e743149f8a8cb9f6547ab5f336d
 SHA256 (6.0-RELEASE-ia64-disc2.iso) = 65618e4547ef7f5238a4987622d34e3f05200b4d6d9c0affbca8931b317197d1
 SHA256 (6.0-RELEASE-ia64-livefs.iso) = 3e2e689318f05e9946ad24f443019256e73459bb2000be6b9aaf96c7ec1eaae8

For pc98:

MD5 (6.0-RELEASE-pc98-disc1.iso) = 5ec7737af58ed3a2618523721dc17cec

For powerpc:

MD5 (6.0-RELEASE-powerpc-bootonly.iso) = 09219f4db3d3b94528413901757d2e49
 MD5 (6.0-RELEASE-powerpc-disc1.iso) = 2ad675f7e4010c51f173e6c636b18b76
 SHA256 (6.0-RELEASE-powerpc-bootonly.iso) = 530db1240a5fc4ae4e91b589630ad74c04eab9113b752c0d101f8dc9d14236ba
 SHA256 (6.0-RELEASE-powerpc-disc1.iso) = a7242065cca689d95c0c3611b1d8fdc38bb1c8b5207bc985289c46bcf75e7e00

For sparc64:

MD5 (6.0-RELEASE-sparc64-bootonly.iso) = cf6423fe3c344827fc4a0fb179e0e375
 MD5 (6.0-RELEASE-sparc64-disc1.iso) = 5ef7031b720f18bad2e216fb373c8da7
 MD5 (6.0-RELEASE-sparc64-disc2.iso) = 31045ae89c097003fe06f77d0ee97227
 SHA256 (6.0-RELEASE-sparc64-bootonly.iso) = 17f1849d89bc98107bddc2b86c5b18f33dbc33351e388ea7003efadda6c575b4
 SHA256 (6.0-RELEASE-sparc64-disc1.iso) = a212e35e8d016908ec9bc431c66c393ca7e43823aeb7b3333266420ef1b7380c
 SHA256 (6.0-RELEASE-sparc64-disc2.iso) = 66ed27a2cb202b4249e00bad73609bfc4ffea4fcae8f941a30eb4b90bc0e43a9

diff --git a/website/content/en/releases/6.0R/approvals.html b/website/content/en/releases/6.0R/approvals.html index 5b63983e2f..4e08119fd5 100644 --- a/website/content/en/releases/6.0R/approvals.html +++ b/website/content/en/releases/6.0R/approvals.html @@ -1,360 +1,360 @@ FreeBSD 6.0 Commit Approvals
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0 Commit Approvals

Introduction

The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.

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.

Approval List

- + - + - + - + - + - + - + - + - + - + - +
Committer Area Expiration
Ruslan Ermilov manual pages1 July 20051 July 2005
Joseph Koshy Performance measurement toolset work: sys/dev/hwpmc, usr.sbin/pmcstat, etc.1 July 20051 July 2005
Max Laier IP6FW removal, contrib/pf PR bugfixes, if_bridge cleanup.1 July 20051 July 2005
Jeff Roberson VFS stability fixes.1 July 20051 July 2005
Brooks Davis ifnet restructuring fixes.1 July 20051 July 2005
Christian Brueffer manual pages and release documentation1 July 20051 July 2005
Bruce A. Mah release documentation1 July 20051 July 2005
Wilko Bulte Alpha release documentation1 July 20051 July 2005
Peter Wemm i386 / amd64 syncing1 July 20051 July 2005
Robert Watson minor manual page tweaks1 July 20051 July 2005
Denis Peplin ru_RU.KOI8-R translation of release documentation1 July 20051 July 2005

Additional Information


diff --git a/website/content/en/releases/6.0R/hardware.html b/website/content/en/releases/6.0R/hardware.html index 59b2197e45..2a97dc49ef 100644 --- a/website/content/en/releases/6.0R/hardware.html +++ b/website/content/en/releases/6.0R/hardware.html @@ -1,279 +1,279 @@ FreeBSD 6.0-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0-RELEASE Hardware Notes

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 6.0-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.0R/installation.html b/website/content/en/releases/6.0R/installation.html index db99cf3947..45137acebe 100644 --- a/website/content/en/releases/6.0R/installation.html +++ b/website/content/en/releases/6.0R/installation.html @@ -1,279 +1,279 @@ FreeBSD 6.0-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0-RELEASE Installation Notes

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 6.0-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.0R/relnotes.html b/website/content/en/releases/6.0R/relnotes.html index 8c918a53aa..7bd66523bd 100644 --- a/website/content/en/releases/6.0R/relnotes.html +++ b/website/content/en/releases/6.0R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 6.0-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0-RELEASE Release Notes

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 6.0-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.0R/schedule.html b/website/content/en/releases/6.0R/schedule.html index 7af954e7e8..99bd34c002 100644 --- a/website/content/en/releases/6.0R/schedule.html +++ b/website/content/en/releases/6.0R/schedule.html @@ -1,569 +1,569 @@ FreeBSD 6.0 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 6.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.

Schedule

- - + + - - + + - - + + - + - - + + - - + + - - + + - - + + - + - + - + - + - - + + - - + + - + - + - + - + - - + - - + + - - + + - - + + - - + + - + -
Action Expected Actual Description
Reminder announcement3 June 20053 June 20053 June 20053 June 2005 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.0 release.
Announce the Ports Freeze22 July 200522 July 200522 July 200522 July 2005 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins10 June 200510 June 200510 June 200510 June 2005 After this date, all commits to HEAD 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.
Announce doc/ tree slush --2 October 20052 October 2005 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen1 August 20051 August 20051 August 20051 August 2005 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush5 October 20055 October 20055 October 20055 October 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.10 October 200512 October 200510 October 200512 October 2005 Version number bumps for doc/ subtree. RELEASE_6_0_0 tag for doc/. doc/ slush ends at this time.
RELENG_6 branch10 July 200511 July 200510 July 200511 July 2005 The new major version branch is created. Update newvers.sh and release.ent on various branches involved.
Begin 6.0-BETA1 builds --11 July 200511 July 2005 Begin building the first public test release build for all Tier-1 platforms.
Release 6.0-BETA1 --15 July 200515 July 2005 6.0-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.0-BETA2 builds --1 August 20051 August 2005 Begin building the second public test release build for all Tier-1 platforms.
Release 6.0-BETA2 --5 August 20055 August 2005 6.0-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.0-BETA3 builds20 August 200525 August 200520 August 200525 August 2005 Begin building the third public test release build for all Tier-1 platforms.
Release 6.0-BETA322 August 200529 August 200522 August 200529 August 2005 6.0-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.0-BETA4 builds --3 September 20053 September 2005 Begin building the fourth public test release build for all Tier-1 platforms.
Release 6.0-BETA4 --7 September 20057 September 2005 6.0-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.0-BETA5 builds --17 September 200517 September 2005 Begin building the fifth public test release build for all Tier-1 platforms.
Release 6.0-BETA5 --30 September 200530 September 2005 6.0-BETA5 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
RELENG_6_0 branch1 August 2005
+ 		1 August 2005
TBD		9 October 20059 October 2005 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
src/ unfrozen TBD -- Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Ports tree tagged15 August 2005
- 28 August 2005		28 August 200515 August 2005
+ 28 August 2005		28 August 2005 RELEASE_6_0_0 tag for ports/.
Ports tree unfrozen15 August 2005
- 28 August 2005		28 August 200515 August 2005
+ 28 August 2005		28 August 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 6.0-RELEASE.
Final package build starts15 August 2005
- 28 August 2005		28 August 200515 August 2005
+ 28 August 2005		28 August 2005 The ports cluster and pointyhat build final packages.
Build 6.0-RC15 October 20059 October 20055 October 20059 October 2005 Begin building the first release candidate build for all Tier-1 platforms.
Release 6.0-RC1 TBD11 October 200511 October 2005 6.0-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org.
Version numbers bumped TBD -- The files listed here are updated to reflect FreeBSD 6.0.
src/ tree tagged TBD -- Tag the RELENG_6_0 branch with RELENG_6_0_0_RELEASE.
Begin 6.0-RELEASE builds TBD -- Start 6.0-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org TBD -- 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 TBD -- Release and packages uploaded to ftp-master.FreeBSD.org.
Announcement15 August 2005 + 15 August 2005
TBD		 -- Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD -- RELENG_6_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/6.0R/todo.html b/website/content/en/releases/6.0R/todo.html index a0009f19bd..13d525d6cb 100644 --- a/website/content/en/releases/6.0R/todo.html +++ b/website/content/en/releases/6.0R/todo.html @@ -1,637 +1,637 @@ FreeBSD 6.0 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.0 Open Issues

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

Show stopper defects for 6.0-RELEASE

Issue Status Responsible Description

Required features for 6.0-RELEASE

Issue Status Responsible Description

Desired features for 6.0-RELEASE

- - + + - - + + - - + + - - + + - - + + - +
Issue Status Responsible Description
devfs umount panicNot done Not done  There is a race condition between device removal and devfs umounts that causes "Memory modified after free" panics. Can be reproduced by doing 'mdconfig -u' concurrently with unmounting a devfs instance.
/dev/kmem panicNot done Not done  Kris has noticed panics on SMP machines when there was ABI breakage of libkvm and world was not rebuilt and utilities like fstat were used. This suggests panics can be caused by incorrect accesses to /dev/kmem.
KLDs on sparc64Not done Not done  On sparc64 machines with more than 4Gb memory KLDs are not usable and will panic the system. The problem is reportedly with how the KLDs are compiled, it only works if the code ends up below 4G.
Max RAM on sparc64Not done Not done  Maximum RAM on sparc64 appears to be limited to 16Gb.
make -jNNot done Not done  Doing 'make -jN', then suspending/resuming it may result in make reporting it lost child process(es).
OpenBSM Deferred for future release Robert Watson The integration of OpenBSM is waiting on some final licensing hurdles. Once those are cleared, it will be a very desirable feature for 6.0.
update sysinstall disk labelingIn progressIn progress Craig Rodrigues Sysinstall could use the same fixes recently made to fdisk so it plays nice with GEOM and disk labeling. This does not cause problems during install because nothing on the disk is mounted when its label is being manipulated but it can cause problems if sysinstall gets used on a live system to adjust labels on existing disks which sys-admins tend to do.

Documentation items that must be resolved for 6.0

- + - +
Issue Status Responsible Description
dhclientNot doneNot done freebsd-doc The ISC DHCP client v3.x has been removed in favor of the OpenBSD DHCP client which was based on ISC DHCP v2.X. Minimal updates to the FreeBSD Handbook may be required.
WPA / hostapIn progressIn progress loader@freebsdmall.com, Sam Leffler, Murray Stokely Significant new wireless functionality will be available with FreeBSD 6.0. The wireless section of the FreeBSD Handbook should be updated to describe how to connect to networks with WPA keys, setup host access points, etc. A howto in progress is available here.

Testing foci for 6.0-RELEASE

- + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - +
Issue Status Responsible Description
New dhclientNeeds testingNeeds testing Brooks Davis The ISC DHCP client v3.x has been removed in favor of the OpenBSD DHCP client which was based on ISC DHCP v2.X. More testing is needed to make sure there are no major regressions in functionality. We are particularly interested in tests involving non-standard environments.
WPA / hostapNeeds testingNeeds testing Sam Leffler Significant new wireless functionality is available in FreeBSD 6.0. As this functionality is rather new, further testing would be appreciated.
if_bridgeNeeds testing Needs testing  A new bridge implementation has been added from NetBSD. As this has not seen a wider audience yet, further testing would be appreciated. See if_bridge(4) for configuration details.
sysinstall dhclient problemsNeeds testingNeeds testing Scott Long, Sam Leffler sysinstall has been updated to deal with the new DHCP client in 6.0, more testing is needed.
ULENeeds testingNeeds testing David Xu The ULE scheduler has been fixed on both HEAD and RELENG_6. More testing is needed.
aac(4) regressionNeeds testingNeeds testing Scott Long There had been a regression in the aac device driver on Dell 2550 machines. This should be fixed but more testing would be good.
vnode_pager_init nswbuf initialization bugNeeds testingNeeds testing Alexander Kabaev There had been a serious performance regression due to a very low bound on the number of swap buffers per vnode (1). This should be fixed but more testing would be good.
fdisk & boot0cfgNeeds testingNeeds testing Poul-Henning Kamp The boot0cfg and fdisk utilities need to be updated to use the proper GEOM model for updating the boot sector of a mounted disk.
Alarming devfs shutdown error needs to be quenched Done Robert Watson During system shutdown, devfs generates a spurious error message due to /dev being non-unmountable: "unmount of /dev failed (BUSY)". While this is not a product of serious breakage, it is a potentially alarming error, whose source should either be fixed, or the message should be forceably quenched, in order to avoid many false positive bug reports and user concern.
page fault at if_ethersubr.c: 284 Done Gleb Smirnoff Found by stress tests at http://www.holm.cc/stress/log/cons141.html.
LivelockNeeds testingNeeds testing Tor Egge Found by stress tests at http://www.holm.cc/stress/log/cons139.html. This is the second most frequent panic reported by Peter Holm.
panic: softdep_setup_inomapdep: found inodeNeeds testingNeeds testing Tor Egge Found by stress tests at http://www.holm.cc/stress/log/cons138.html.
M_SAVEDINONeeds testingNeeds testing Tor Egge A 'memory modified after free' bug affecting M_SAVEDINO. Possibly a softupdates bug.
kgdbNeeds testingNeeds testing Marcel Moolenaar kgdb has been modified to handle trap frames on all tier 1 and 2 architectures. This allows tracebacks to provide useful info.
panic: wrong b_bufobjNeeds testingNeeds testing Tor Egge Found by stress tests at http://www.holm.cc/stress/log/cons140.html. This is high priority and can be provoked within minutes of testing!
Panic when filesystem fills Done Robert Watson Inadequate locking causes panics when calling kernel printf functions. This is most often seen when a filesystem fills up and uprintf() is called to report it to the console, but it can happen in many other places also. Properly locking the upper and lower parts of the tty subsystem likely cannot happen for 6.0, but temporary fixes must be developed and committed. A patch has now been committed that is believed to fix this problem by acquiring Giant in uprintf() and tprintf(), as well as a regression test. This work-around has now been merged to RELENG_6 and is ready for wide-spread testing.
panic on multicast socket close after interface removal Done Robert Watson Due to the addition of multicast locking, a long-present memory corruption bug now generates an immediate panic if an interface is removed while a multicast group is in use on the interface. This can manifest if running routed and using vlans. A regression test has now been committed as msocket_ifnet_remove. A short-term fix will be to GC references to the interface in the IPv4/IPv6 multicast socket options hung off of the inpcb; a long term solution will require determining the correct application semantics for interface removal as relates to multicast sockets. This problem is described in detail in PR kern/77665. A fix has now been committed to 7-CURRENT in the CVS HEAD, and merged to RELENG_6.
panic: handle_written_inodeblock: live inodedepNeeds testingNeeds testing Don “Truck” Lewis, Tor Egge Found by stress tests at http://www.holm.cc/stress/log/cons142.html.
"snaplk" livelockNeeds testingNeeds testing Don “Truck” Lewis Found by stress tests at http://www.holm.cc/stress/log/cons143.html.
fpudna: fpcurthread == curthread 1 timesNeeds testingNeeds testing Stephan Uphoff This warning is appearing sporadically on a dual AMD64 system. It appears to be warning against a legitimate problem, and thus should be investigated and fixed.
race condition in POSIX named fifos Done Robert Watson There have been multiple reports of panics when running with make -j on SMP systems, which appear to be associated with a race condition in the POSIX named fifo support. A number of regression tests have been written to confirm that any fix does not break fifos, and a number of other unrelated bugs were fixed in the process. The cause of the symptoms has been identified, and a workaround has been committed to 7-CURRENT for testing; it has been merged to RELENG_6 for testing.
UFS_EXTATTR_AUTOSTART Done Robert Watson Changes in VFS locking as part of the SMPng work have resulted in a new panic during the auto-starting of UFS1 extended attributes. A patch to fix this has been committed (ufs_extattr.c:1.82), and now requires further testing before it is merged to RELENG_6 and RELENG_6_0.

Stress Test Panics

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. The following issues have recently been discovered from this test suite.


diff --git a/website/content/en/releases/6.1R/announce.html b/website/content/en/releases/6.1R/announce.html index 8ea9a419cb..48e81b4c79 100644 --- a/website/content/en/releases/6.1R/announce.html +++ b/website/content/en/releases/6.1R/announce.html @@ -1,521 +1,521 @@ FreeBSD 6.1-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1-RELEASE Announcement

Date: Mon, 08 May 2006 18:40:04 -0700
From: Scott Long <scottl@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 6.1 Released

It is my great pleasure and privilege to announce the availability of FreeBSD 6.1-RELEASE. This release is the next step in the development of the 6.X branch, delivering several performance improvements, many bugfixes, and a few new features. These include:

  • Addition of a keyboard multiplexer. This allows USB and PS/2 keyboards to coexist without any special options at boot.

  • Many fixes for filesystem stability. High load stress tests are now run successfully on a regular basis as part of the normal FreeBSD QA process.

  • Automatic configuration for many Bluetooth devices, as well as automatic support for running WiFi access points.

  • Addition of drivers for new ethernet and SAS and SATA RAID controllers.

  • BIND updated to 9.3.2

  • sendmail updated to 8.13.6

NOTE: It was discovered at the last minute that the errata notes that got packaged with the release are out of date. For a complete list of known problems, please see the online errata list, available at:

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

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

http://www.FreeBSD.org/releng

Availability

FreeBSD 6.1-RELEASE supports the i386, pc98, alpha, sparc64, amd64, powerpc, 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 6.1 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 and SHA256 checksums for the release images are included at the bottom of this message.

Bittorrent

The FreeBSD project encourages the use of BitTorrent for distributing the release ISO images. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP

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

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, 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 6.1 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Sentex Communications, and Copan Systems.

The release engineering team for 6.1-RELEASE includes:

Scott Long <scottl@FreeBSD.org> Release Engineering
Ken Smith <kensmith@FreeBSD.org> I386, AMD64, Sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Doug White <dwhite@FreeBSD.org> Release Engineering
Maxime Henrion <mux@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
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
Kiril Ponomarew <krion@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org> Security Officer

CD Image Checksums

 MD5 (6.1-RELEASE-amd64-bootonly.iso) = b73e8dc202f64aa56606f6e3399bc83f
 MD5 (6.1-RELEASE-amd64-disc1.iso) = 2d6fc98a4cd11468f62ea0c7332affff
 MD5 (6.1-RELEASE-amd64-disc2.iso) = 6b48c41b5dc774ae727f3f0a8a91c96f
 
 MD5 (6.1-RELEASE-i386-bootonly.iso) = 11bb7fb4d2a781238008945f6bf65a4e
 MD5 (6.1-RELEASE-i386-disc1.iso) = cf1ce4ba48d664ce3977108a18ced6b8
 MD5 (6.1-RELEASE-i386-disc2.iso) = bc0f4a32a64e00c7cbfb839e6d5772f3
 
 MD5 (6.1-RELEASE-ia64-bootonly.iso) = 94e83e6ba0281b58bd5af4a1004f8079
 MD5 (6.1-RELEASE-ia64-disc1.iso) = b3f957ef581f4267fdd2b0400ff492dd
 MD5 (6.1-RELEASE-ia64-disc2.iso) = e46c08dd1e46c825048ce5105497f900
 MD5 (6.1-RELEASE-ia64-livefs.iso) = 75f70e7c1f5bc295bc00841b19c00b63
 
 MD5 (6.1-RELEASE-pc98-disc1.iso) = 923e86a2307d1dce7dfb3379a67885f4
 
 MD5 (6.1-RELEASE-sparc64-bootonly.iso) = f8e11c6a952f4be8435dc8d56c5bfc8e
 MD5 (6.1-RELEASE-sparc64-disc1.iso) = c206054f9cecf629211f6fc2b068e9ff
 MD5 (6.1-RELEASE-sparc64-disc2.iso) = b7b4db45c998f682ba57fef62f2b8fdc
 
 SHA256 (6.1-RELEASE-amd64-bootonly.iso) = da885951bfa1b322bad9780766338e9b22f8b1e71c59316c0f182e27522409a9
 SHA256 (6.1-RELEASE-amd64-disc1.iso) = 99f596f65f7860f2f7d1be7b926faab7c3a3561d8659527127ca39760afb0e00
 SHA256 (6.1-RELEASE-amd64-disc2.iso) = 4359419420b459a256b2d45ee8d5ba4e13373f9a986ceeadfe6778448d72b01d
 
 SHA256 (6.1-RELEASE-i386-bootonly.iso) = cb7ad11198358e2123dc139d7fbab26727524e973c6c02906cc6aca944b064c9
 SHA256 (6.1-RELEASE-i386-disc1.iso) = cbc6f9389c85f3130baff5270316ece18d5e324e82f8aa167c61ab49174dd4d1
 SHA256 (6.1-RELEASE-i386-disc2.iso) = 7c3a056d18be9e2dccf1f4e7dba22a4760d6288165eb87fe9894abc8c7741ffb
 
 SHA256 (6.1-RELEASE-ia64-bootonly.iso) =  2d1f921f9195f5f1525b437f3bee67e0c02bbfa195a8f9950fba4d471434e837
 SHA256 (6.1-RELEASE-ia64-disc1.iso) =  584870eed63617f27a0fc5dc908195504e69f35125d7cf6ef9e6752d14f85c59
 SHA256 (6.1-RELEASE-ia64-disc2.iso) =  6076b7c988625cc044c75e3e580542b23ec0acdac3472d61944736731bc263fe
 SHA256 (6.1-RELEASE-ia64-livefs.iso) =  6fbdd5f0dc63743e05ff11a688aa6a5de2dcb34a469874c85dd3797de99e97ce
 
 SHA256 (6.1-RELEASE-pc98-disc1.iso) = 859d6978f06d9354713fe76b8ea05268650da943fb9a03e05de3c69426ebbee7
 
 SHA256 (6.1-RELEASE-sparc64-bootonly.iso) = a700069cdcc2d0df71e7023afdbba2b4e2e2b66c23348ac6386c46f5b2ce798e
 SHA256 (6.1-RELEASE-sparc64-disc1.iso) = a8e8cf6d82cb8bebe3fa85fe8b2f0c5b6eff866e9314611d36194c01c489474d
 SHA256 (6.1-RELEASE-sparc64-disc2.iso) = 062f5e1d0ec254dbd924ed43f44de6f068646edf459ed0e36b98e2ca3f257774

diff --git a/website/content/en/releases/6.1R/approvals.html b/website/content/en/releases/6.1R/approvals.html index 411742661e..6d9d0a0464 100644 --- a/website/content/en/releases/6.1R/approvals.html +++ b/website/content/en/releases/6.1R/approvals.html @@ -1,293 +1,293 @@ FreeBSD 6.1 Commit Approvals
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1 Commit Approvals

Introduction

The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.

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.

Approval List

Committer Area Expiration

Additional Information


diff --git a/website/content/en/releases/6.1R/hardware.html b/website/content/en/releases/6.1R/hardware.html index f4f92bfc25..80dcf5bff7 100644 --- a/website/content/en/releases/6.1R/hardware.html +++ b/website/content/en/releases/6.1R/hardware.html @@ -1,279 +1,279 @@ FreeBSD 6.1-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1-RELEASE Hardware Notes

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 6.1-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.1R/installation.html b/website/content/en/releases/6.1R/installation.html index 113df7d55c..98e258d587 100644 --- a/website/content/en/releases/6.1R/installation.html +++ b/website/content/en/releases/6.1R/installation.html @@ -1,279 +1,279 @@ FreeBSD 6.1-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1-RELEASE Installation Notes

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 6.1-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.1R/relnotes.html b/website/content/en/releases/6.1R/relnotes.html index 0a5d75008f..f57d62da80 100644 --- a/website/content/en/releases/6.1R/relnotes.html +++ b/website/content/en/releases/6.1R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 6.1-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1-RELEASE Release Notes

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 6.1-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.1R/schedule.html b/website/content/en/releases/6.1R/schedule.html index 7ab06efa85..b73f37509c 100644 --- a/website/content/en/releases/6.1R/schedule.html +++ b/website/content/en/releases/6.1R/schedule.html @@ -1,570 +1,570 @@ FreeBSD 6.1 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 6.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.

Schedule

- + - - + + - + - - + + - - + + - - + + - - + + - - + + - + - + - - + + - + - - + + - - + + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - + - - + + - - + + - + - - + + - - + +
Action Expected Actual Description
Reminder announcement --25 January 200625 January 2006 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.1 release.
Code freeze begins31 January 200631 January 200631 January 200631 January 2006 After this date, all commits to HEAD 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.
Announce the Ports Freeze --5 February 20065 February 2006 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Begin 6.1-BETA1 builds5 February 20065 February 20065 February 20065 February 2006 Begin building the first public test release build for all Tier-1 platforms.
Release 6.1-BETA15 February 20065 February 20065 February 20065 February 2006 6.1-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.1-BETA2 builds19 February 200616 February 200619 February 200616 February 2006 Begin building the second public test release build for all Tier-1 platforms.
Release 6.1-BETA219 February 200620 February 200619 February 200620 February 2006 6.1-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree frozen20 February 200623 February 200620 February 200623 February 2006 Only approved commits will be permitted to the ports/ tree during the freeze.
Begin 6.1-BETA3 builds --1 March 20061 March 2006 Begin building the third public test release build for all Tier-1 platforms.
Release 6.1-BETA3 --3 March 20063 March 2006 6.1-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.1-BETA4 builds12 March 200613 March 200612 March 200613 March 2006 Begin building the fourth public test release build for all Tier-1 platforms.
Release 6.1-BETA4 --14 March 200614 March 2006 6.1-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
RELENG_6_1 branch5 March 2006
- 5 April 2006		5 April 20065 March 2006
+ 5 April 2006		5 April 2006 The new major version branch is created. Update newvers.sh and release.ent on various branches involved.
src/ unfrozen TBD -- Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Build 6.1-RC15 March 2006
- 5 April 2006		5 April 20065 March 2006
+ 5 April 2006		5 April 2006 Begin building the first release candidate build for all Tier-1 platforms.
Release 6.1-RC15 March 2006
- 10 April 2006		5 March 2006
+ 10 April 2006		 -- 6.1-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged6 March 200614 March 20066 March 200614 March 2006 RELEASE_6_1_0 tag for ports/.
Ports tree unfrozen6 March 200614 March 20066 March 200614 March 2006 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.1-RELEASE.
Final package build starts TBD -- The ports cluster and pointyhat build final packages.
Announce doc/ tree slush6 March 20066 March 20066 March 20066 March 2006 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush10 March 2006
- 7 April 2006		7 April 200610 March 2006
+ 7 April 2006		7 April 2006 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.
Build 6.1-RC212 March 2006
- 30 April 2006		30 April 200612 March 2006
+ 30 April 2006		30 April 2006 Begin building the second release candidate build for all Tier-1 platforms.
Release 6.1-RC212 March 2006
- 2 May 2006		2 May 200612 March 2006
+ 2 May 2006		2 May 2006 6.1-RC2 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged.13 March 2006
- 10 April 2006		17 April 200613 March 2006
+ 10 April 2006		17 April 2006 Version number bumps for doc/ subtree. RELEASE_6_1_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped17 March 2006
- 7 May 2006		17 March 2006
+ 7 May 2006		 -- The files listed here are updated to reflect FreeBSD 6.1.
src/ tree tagged17 March 2006
- 7 May 2006		7 May 200617 March 2006
+ 7 May 2006		7 May 2006 Tag the RELENG_6_1 branch with RELENG_6_1_0_RELEASE.
Begin 6.1-RELEASE builds17 March 2006
- 7 May 2006		7 May 200617 March 2006
+ 7 May 2006		7 May 2006 Start 6.1-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org17 March 2006
- 7 May 2006		17 March 2006
+ 7 May 2006		 -- 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-master19 March 2006
- 8 May 2006		8 May 200619 March 2006
+ 8 May 2006		8 May 2006 Release and packages uploaded to ftp-master.FreeBSD.org.
Announcement20 March 2006
- 8 May 2006		8 May 200620 March 2006
+ 8 May 2006		8 May 2006 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD -- RELENG_6_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/6.1R/todo.html b/website/content/en/releases/6.1R/todo.html index ee8f81f5ea..4b9f851243 100644 --- a/website/content/en/releases/6.1R/todo.html +++ b/website/content/en/releases/6.1R/todo.html @@ -1,694 +1,694 @@ FreeBSD 6.1 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.1 Open Issues

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

Show stopper defects for 6.1-RELEASE

Issue Status Responsible Description
No pending issue.

Required features for 6.1-RELEASE

Issue Status Responsible Description
No pending issue.

Desired features for 6.1-RELEASE

- + - + - + - + - + - - + + - - + + - +
Issue Status Responsible Description
devfs locking problemIn progressIn progress Jeff Roberson It is trivial to deadlock it on an SMP system, and there are other panics with device removal.
pty leakIn progressIn progress Olivier Houchard Since 6.x has a hard-coded limit, once all ptys are leaked things like ssh and login no longer work. This seems devfs-related, and occurs only under extreme stress testing, not normal use.
swap_pager warnings Unknown Don “Truck” Lewis? When swapfiles are in use, there are often warnings printed: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 889347, size: 8192. There is also the possibility of deadlock.
unmount pending errorIn progressIn progress Suleiman Souhlal When unmounting filesystems Kris Kennaway reports seeing this warning: /c: unmount pending error: blocks -68512 files 0. This dates back at least to 5.3. It might be associated with filesystem corruption reported by many users in which the 'used' space on a filesystem is negative; fsck -f is needed to correct this.
"calcru: runtime went backwards" problem for threaded program Unknown   stress2 thr1 test can trigger "calcru: runtime went backwards" problem and there are also many similar reports on -stable and -current. Poul-Henning Kamp committed a possible fix (src/sys/kern/kern_tc.c rev.1.169) to update the calibration code to be more precise on 2 March.
NFS data corruption between two 7.0 machinesIn progressIn progress Mohan Srinivasan Running fsx between a 7.0 NFS client and server detects data corruption. This problem can also be reproduced by using 6.1 NFS server. The problem seems to be avoidable by turning off the attribute cache on the NFS client.
sort(1) does not work with some localesNot done Not done  sort(1) can cause a coredump with some locales. See also gnu/93629.
unreliable serial console Unknown At the manual 'root mount' prompt, the serial console is very unreliable and drops most characters. This appears to be caused by cngetc() polling the sio driver for input, and the sio driver resetting the chip on every poll iteration. That results in a very small window for it to accept input. Fixing this requires a large review of the operation of the sio driver. The uart driver looks to handle this better and might be a suitable replacement.
fix ntpdate(1) bogus output on amd64. Unknown Ollivier Robert
make -jNNot done Not done  Doing 'make -jN', then suspending/resuming it may result in make reporting it lost child process(es).
update sysinstall disk labelingIn progressIn progress Craig Rodrigues Sysinstall could use the same fixes recently made to fdisk so it plays nice with GEOM and disk labeling. This does not cause problems during install because nothing on the disk is mounted when its label is being manipulated but it can cause problems if sysinstall gets used on a live system to adjust labels on existing disks which sys-admins tend to do.
i386 deadlocks with >16GB swap Deferred for future release Alan L. Cox i386 deadlocks if more than 16GB of swap is in use. Increasing the kern.maxswzone tunable would be a workaround this. Although a patch from Alan L. Cox is needed to allow this variable to be increased, this is not suitable for 6.1R. This limitation should be documented in the Release Notes.
panic in bpf Deferred for future release Sam Leffler killing tcpdump (e.g. with ^C) can cause panics in bpf. To fix this problem, some architectural changes are needed.
OpenBSM Deferred for future release Robert Watson The integration of OpenBSM is waiting on some final licensing hurdles. It is expected to be available in the next release.

Documentation items that must be resolved for 6.1

Issue Status Responsible Description
No pending issue.

Testing foci for 6.1-RELEASE

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Issue Status Responsible Description
manual root mount lockmgr panicsNeeds testingNeeds testing Suleiman Souhlal Specifying a manual root mount location causes lockmgr panics. Suleiman Souhlal has committed a patch for this.
dhclient causes ipv6 panics.Needs testingNeeds testing Doug Barton Doug Barton has more details about this.
amd64 panics in ipv6 with date(1)Needs testingNeeds testing Hajimu UMEMOTO amd64 panics in ipv6 when the date is changed using date(1) or ntpdate(1). This may be a MI issue.
grep(1) -w does not work with multibyte localesNeeds testingNeeds testing Tim J. Robbins grep(1) -w generates wrong results with non-UTF-8 multibyte locales. Tim J. Robbins has committed a patch to -HEAD. See also gnu/91909.
Improve kbdmuxNeeds testingNeeds testing Maksim Yevmenkin From the ideas page. We need this for the growing number of systems that assume that USB is the primary keyboard. Current status appears to be that the kbdmux driver breaks very easily. We need this working well enough where it can be enabled by default, and all attached keyboards Just Work. Maksim Yevmenkin commit kbdmux and rc.d/syscons patches in HEAD and RELENG_6. It is not yet enabled by default. See kbdmux(4) and contact Maksim Yevmenkin if you have problems.
umount -f panicsNeeds testingNeeds testing Jeff Roberson, Suleiman Souhlal panics from race conditions. A patch from Jeff Roberson seems to fix some of them.
quota deadlocksNeeds testingNeeds testing Jeff Roberson Quota support is not locked properly and causes deadlocks. A patch from Jeff Roberson seems to fix some of them.
ifconfig regression on 6.xNeeds testingNeeds testing Yar Tikhiy ifconfig cannot handle vlan and mtu parameters at the same time after rev.1.7.2.3 of sbin/ifconfig/ifvlan.c commit. For more information and a proposed patch, see bin/94028.
SMP kernels for installNeeds testingNeeds testing Sam Leffler From the ideas page. Right now we only install a UP kernel, for performance reasons. We should be able to package both a UP and SMP kernel into the release bits, and have sysinstall install both. It should also select the correct one for the target system and make that the default on boot. The easiest way to do this would be to have sysinstall boot an SMP kernel and then look at the hw.ncpu sysctl. The only problem is being able to have sysinstall fall back to booting a UP kernel for itself if the SMP one fails. This can probably be 'faked' by setting one of the SMP-disabling variables in the loader. But in any case, the point is to make the process Just Work for the user, without the user needing to know arcane loader/sysctl knobs. SMP laptops are here, and we should be ready to support SMP out-of-the-box.
dup(2) regression on 6.xNeeds testingNeeds testing Christian S.J. Peron Simple "close(0); dup(fd)" does not return descriptor "0" in some cases. This problem has been reported in kern/87208, and there is a proposed patch in the PR, too. Christian S.J. Peron has committed a fix for this.
cpu_ipi_selected() can cause a trap on FreeBSD/sparc64Needs testingNeeds testing Marius Strobl On sparc64, cpu_ipi_selected() can cause a trap (which is bad since it appears in the trap code path).
UFS deadlocks on amd64Needs testingNeeds testing Tor Egge Seen by Kris Kennaway. This problem seems MI.
UFS deadlocksNeeds testingNeeds testing Tor Egge Seen by Peter Jeremy.
panic in fxp driverNeeds testingNeeds testing Andre Oppermann See http://people.freebsd.org/~pho/stress/log/cons186.html.
exec_map depletionNeeds testingNeeds testing Stephan Uphoff The exec_map is regularly running out of space on machines running 7.0. Stephan Uphoff has a committed a patch that seems to fix this problem.
/dev/mem instabilityNeeds testingNeeds testing Marius Strobl, Stephan Uphoff Instability when accessing /dev/mem. A fix was committed for i386. amd64 does not seem to have the problem. A sparc64 fix is still in progress.
deadlock in vn_start_write() consumersNeeds testingNeeds testing Tor Egge Many potential deadlocks have been fixed.

Stress Test Panics

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. The following issues have recently been discovered from this test suite.

sparc64 problems

These are problems that range in severity for FreeBSD/sparc64. They will not hold up the release, but they will still be tracked for future releases.

- + - + - - + + - - + +
Issue Status Responsible Description
sparc64 frequent hangsIn progressIn progress Marius Strobl Some of the more serious hangs on sparc64 have been fixed, but more remain.
serious sparc64 IPv6 panicIn progressIn progress George V. Neville-Neil Triggered by just ping6'ing the box. It may even be a MI issue, the reporter of this bug only uses IPv6 with sparc64. This problem seems to be triggered even when debug.mpsafenet="0".
swap panic on sparc64 Unknown Kris Kennaway has panic info Kris Kennaway reports configuring a 74GB swap-backed md on sparc64 that caused a panic after a week or two of load (during which time swap was slowly filling as more of the md was dirtied).
KLDs on sparc64Not done Not done  On sparc64 machines with more than 4Gb memory KLDs are not usable and will panic the system. The problem is reportedly with how the KLDs are compiled, it only works if the code ends up below 4G.
Max RAM on sparc64Not done Not done  Maximum RAM on sparc64 appears to be limited to 16Gb.

diff --git a/website/content/en/releases/6.2R/announce.html b/website/content/en/releases/6.2R/announce.html index 32c9f56511..a78d1ba580 100644 --- a/website/content/en/releases/6.2R/announce.html +++ b/website/content/en/releases/6.2R/announce.html @@ -1,542 +1,542 @@ FreeBSD 6.2-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2-RELEASE Announcement

Date: Mon, 15 Jan 2007 00:29:19 -0500
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 6.2 Released

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.2-RELEASE. This release continues the development of the 6-STABLE branch providing performance and stability improvements, many bug fixes and new features. Some of the highlights:

  • freebsd-update(8) provides officially supported binary updates for security fixes and errata patches

  • Experimental support for CAPP security event auditing

  • OpenBSM audit command line tool suite and library

  • KDE updated to 3.5.4, GNOME updated to 2.16.1

  • csup(1) integrated cvsup client now included

  • Disk integrity protection and authentication added to geli(8)

  • New amdsmb(4), enc(4) ipmi(4), nfsmb(4), stge(4) drivers

  • IPFW(4) packet tagging

  • Linux emulation support for sysfs

  • BIND updated to 9.3.3

  • Many driver updates including em(4), arcmsr(4), ath(4), bce(4), ata(4), and iwi(4)

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

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

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

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

Availability

FreeBSD 6.2-RELEASE is now available for the alpha, amd64, i386, ia64, pc98, powerpc, and sparc64 architectures. It can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The contents of the ISO images provided as part of the release has changed for most of the architectures. Using the i386 architecture as an example, there are ISO images named ``bootonly'', ``disc1'', ``disc2'', and ``docs''. The ``bootonly'' image is suitable for booting a machine to do a network based installation using FTP or NFS. The ``disc1'' and ``disc2'' images are used to do a full installation that includes a basic set of packages and does not require network access to an FTP or NFS server during the installation. In addition, ``disc1'' supports booting into a ``live CD-based filesystem'' and system rescue mode. The ``docs'' image has all of the documentation for all supported languages. Most people will find that ``disc1'' and ``disc2'' are all that are needed.

FreeBSD 6.2-RELEASE can also be purchased on CD-ROM from several vendors. Two of the vendors that will be offering FreeBSD 6.2-based products are:

Bittorrent

6.2-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP

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

FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, 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

FreeBSD Update

The freebsd-update(8) utility, which is the client half of the FreeBSD Update binary update system, is now included in the FreeBSD base system and supported by the FreeBSD Security Team, which will be building binary security and errata updates for the i386 and amd64 platforms.

In addition, an experimental version of the freebsd-update(8) utility is available which supports upgrading systems between FreeBSD releases. Administrators of FreeBSD 6.1 systems are encouraged to test this and report any problems encountered on the freebsd-stable mailing list. For more information, see:

http://www.daemonology.net/blog/2006-11-26-freebsd-6.1-to-6.2-binary-upgrade.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 6.2 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, Sentex Communications, and Copan Systems.

The release engineering team for 6.2-RELEASE includes:

Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386 sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Doug White <dwhite@FreeBSD.org> Release Engineering
Maxime Henrion <mux@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc 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
Colin Percival <cperciva@FreeBSD.org> Security Officer

ISO Image Checksums

 MD5 (6.2-RELEASE-alpha-bootonly.iso) = e8e29790cb6e621c7dfbe3ab4b5a30f5
 MD5 (6.2-RELEASE-alpha-disc1.iso) = 8c80f84e59aff027eab3dcebac87c823
 MD5 (6.2-RELEASE-alpha-docs.iso) = 9de4213a490341738cd06f0e943cabfd
 
 MD5 (6.2-RELEASE-amd64-bootonly.iso) = da90d52b86f956c8eb0980ca77d06fd7
 MD5 (6.2-RELEASE-amd64-disc1.iso) = bf42599b11b7d8fb468160bd8168e053
 MD5 (6.2-RELEASE-amd64-disc2.iso) = 703435e3e34c1c7729cab8a98378d6df
 MD5 (6.2-RELEASE-amd64-docs.iso) = 0c826df4dd7280738392cb04188cb183
 
 MD5 (6.2-RELEASE-i386-bootonly.iso) = 4e8701ac951bc4537f8420fdac7efbb5
 MD5 (6.2-RELEASE-i386-disc1.iso) = 3d27214700687c0b5390e8b6dd3706e3
 MD5 (6.2-RELEASE-i386-disc2.iso) = fd30bfc65ef8adaa67aeffd07c72bf21
 MD5 (6.2-RELEASE-i386-docs.iso) = e3512834982a9beebc3670499c7f3817
 
 MD5 (6.2-RELEASE-ia64-bootonly.iso) = a678f17e66b306c9ceabf17d2e820cfc
 MD5 (6.2-RELEASE-ia64-disc1.iso) = 30ea0bbef1d6400f8d9c30e2d7cea764
 MD5 (6.2-RELEASE-ia64-disc2.iso) = fd0d68530582208fab0377c419500153
 MD5 (6.2-RELEASE-ia64-docs.iso) = 4abb963dec5d4f957a3185cebd8534e8
 MD5 (6.2-RELEASE-ia64-livefs.iso) = d5325d0084f59b6dbbca4706da7c78e6
 
 MD5 (6.2-RELEASE-pc98-bootonly.iso) = da1bdf4c43dd6e8adcf5bd610a0aa3ad
 MD5 (6.2-RELEASE-pc98-disc1.iso) = 31b56ea419c7d1071cbd68f8a1fa2628
 
 MD5 (6.2-RELEASE-powerpc-bootonly.iso) = 3d5ecb6c20a692be9554ba9959e34519
 MD5 (6.2-RELEASE-powerpc-disc1.iso) = 53f47b625ef4a6e2ab9ef51e415333d0
 
 MD5 (6.2-RELEASE-sparc64-bootonly.iso) = 40d2e78c023284722478e82f16f77963
 MD5 (6.2-RELEASE-sparc64-disc1.iso) = d9830e979013d9e4ac67eab4565aecde
 MD5 (6.2-RELEASE-sparc64-disc2.iso) = 9f93f1cf2cb07e40b78b1217b52242c2
 MD5 (6.2-RELEASE-sparc64-docs.iso) = 7226efa1edb55a6ee0b8286ee2fe3be6
 
 SHA256 (6.2-RELEASE-alpha-bootonly.iso) = ce8d9183b8c15a9b1fe6ebbf2a72f9797baa5fe3a80e726041eea23efe027b59
 SHA256 (6.2-RELEASE-alpha-disc1.iso) = 6ecb22ddd1b400699707c7584bef4fc90ea53852b23859a95aa2b4d659c6baf4
 SHA256 (6.2-RELEASE-alpha-docs.iso) = 086b58bda8f89ca942f9f46af77de0ee95cf5a5aa15045b7bbe043ea0d220ae7
 
 SHA256 (6.2-RELEASE-amd64-bootonly.iso) = 29b3c796fffbe758913e45787f2467f2d21f9e2074ff642b3f1b092f59888960
 SHA256 (6.2-RELEASE-amd64-disc1.iso) = 60d2d13a23c0e6ecac5547c5e83c53c378c37ae40a04ef4f5f0964c79955cc6f
 SHA256 (6.2-RELEASE-amd64-disc2.iso) = b4e9d7e396d60c0b1311853a3f67e8edbbe882ce1ed65b885eaf91e1f553c171
 SHA256 (6.2-RELEASE-amd64-docs.iso) = 5c9a5c1ff8d8b588485cfbedf0d7482e3c70841d53f4750ab33e4efdccd67911
 
 SHA256 (6.2-RELEASE-i386-bootonly.iso) = f338404690ebca656c6c15b20a8f82d10fb3f37c237808a3ce7d786509123378
 SHA256 (6.2-RELEASE-i386-disc1.iso) = 2099715d561df721833322bc56a4fa8b02c2b77713a1e0bc17fc4b2dded20212
 SHA256 (6.2-RELEASE-i386-disc2.iso) = 7399fa52298a76eebedd70436361f0de980412a2d88679054ed5338b7c30a4bf
 SHA256 (6.2-RELEASE-i386-docs.iso) = 3962be41cbdf8341e5ed38c8a7ceb762d3b1feb275f961fe21d74e5312e43377
 
 SHA256 (6.2-RELEASE-ia64-bootonly.iso) = 950bdbd9c46aef3e55e98b429813bd7812e2300bbea4c31304282930e04ae25e
 SHA256 (6.2-RELEASE-ia64-disc1.iso) = eaf3fe8ffb1458fc0629453ffe58b44f161d4a915dba1fca7f055b4b8209db24
 SHA256 (6.2-RELEASE-ia64-disc2.iso) = e43e1360984dae64b9f917118fab8e9e6f0428b9533e11996190f894b035b3ad
 SHA256 (6.2-RELEASE-ia64-docs.iso) = f69c57f47fb289da1bee1a812c17f209b48fb7dd1b28cbc7d9ae9719d12f5755
 SHA256 (6.2-RELEASE-ia64-livefs.iso) = 0af88079c7451169b09d3765a85042bdc33e1334df5dd5c8a1fbff33e8d16170
 
 SHA256 (6.2-RELEASE-pc98-bootonly.iso) = ee73ce2ab7a7f37adb5d71eb054e6e0ca3d986d2f7b6d80273139bba029cb091
 SHA256 (6.2-RELEASE-pc98-disc1.iso) = 22ffa26aecbfad9efafd115ec6b4a74ce75bc920b0b63d159ee5c4bb35d79d1d
 
 SHA256 (6.2-RELEASE-powerpc-bootonly.iso) = 7abc11e7bc9c80e11bcd87e8c85016ca3a6affbc986bbd9b4e02aec4dea17958
 SHA256 (6.2-RELEASE-powerpc-disc1.iso) = 0c4533f474f6b79b37bfd3bf3297ef6fc044d82e2b8a64829900924685d2d1db
 
 SHA256 (6.2-RELEASE-sparc64-bootonly.iso) = 902509d63d4beef190c0260ea570901769cb87e30904f7144e45583a5d81913b
 SHA256 (6.2-RELEASE-sparc64-disc1.iso) = 9a864e017d652e584a959335088aa36be85d3c78568546afddf2c743e74111c1
 SHA256 (6.2-RELEASE-sparc64-disc2.iso) = b5c34512fbc2edc1920ab1f7d811b06be0f79cd27f58ca9c8b93c5d5ebd041d7
 SHA256 (6.2-RELEASE-sparc64-docs.iso) = 9d974edf7f100512b2c67fd1b8c0124e370e7b687120f5284e5cc8979e0e18d2

diff --git a/website/content/en/releases/6.2R/approvals.html b/website/content/en/releases/6.2R/approvals.html index afc7ea1570..16bc34935d 100644 --- a/website/content/en/releases/6.2R/approvals.html +++ b/website/content/en/releases/6.2R/approvals.html @@ -1,312 +1,312 @@ FreeBSD 6.2 Commit Approvals
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2 Commit Approvals

Introduction

The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.

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.

Approval List

Committer Area Expiration
obrien ARM-related toolchain 6.2-RC1
delphij src/release/doc/zh_CN.GB2312/ (Simplified Chinese release documentation) 6.2-RC1
ru Manual pages 6.2-BETA3

Additional Information


diff --git a/website/content/en/releases/6.2R/hardware.html b/website/content/en/releases/6.2R/hardware.html index 2192924e86..ac14172b89 100644 --- a/website/content/en/releases/6.2R/hardware.html +++ b/website/content/en/releases/6.2R/hardware.html @@ -1,279 +1,279 @@ FreeBSD 6.2-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2-RELEASE Hardware Notes

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 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.


diff --git a/website/content/en/releases/6.2R/installation.html b/website/content/en/releases/6.2R/installation.html index ca497db2e2..66fdae60d4 100644 --- a/website/content/en/releases/6.2R/installation.html +++ b/website/content/en/releases/6.2R/installation.html @@ -1,279 +1,279 @@ FreeBSD 6.2-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2-RELEASE Installation Notes

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 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.


diff --git a/website/content/en/releases/6.2R/relnotes.html b/website/content/en/releases/6.2R/relnotes.html index b959b85587..f57f011d70 100644 --- a/website/content/en/releases/6.2R/relnotes.html +++ b/website/content/en/releases/6.2R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 6.2-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2-RELEASE Release Notes

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 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.


diff --git a/website/content/en/releases/6.2R/schedule.html b/website/content/en/releases/6.2R/schedule.html index 499ec89896..34db964acc 100644 --- a/website/content/en/releases/6.2R/schedule.html +++ b/website/content/en/releases/6.2R/schedule.html @@ -1,549 +1,549 @@ FreeBSD 6.2 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 6.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.

Schedule

- - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - + - + - - + + - - + + - - + + - - + + - - + + - - + + - + - - + + - - + + - +
Action Expected Actual Description
Reminder announcement8 September 20068 September 20068 September 20068 September 2006 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.2 release.
Code freeze begins10 September 200610 September 200610 September 200610 September 2006 After this date, all commits to RELENG_6 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.
Announce the Ports Freeze17 September 200617 September 200617 September 200617 September 2006 portmgr@ sends email to freebsd-ports@ to announce the dates for the week long ports freeze and tagging of the ports tree.
Begin 6.2-BETA1 builds16 September 200616 September 200616 September 200616 September 2006 Begin building the first public test release build for all Tier-1 platforms.
Release 6.2-BETA117 September 200620 September 200617 September 200620 September 2006 6.2-BETA1 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Begin 6.2-BETA2 builds30 September 20061 October 200630 September 20061 October 2006 Begin building the second public test release build for all Tier-1 platforms.
Release 6.2-BETA21 October 20065 October 20061 October 20065 October 2006 6.2-BETA2 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
Ports tree frozen10 October 200610 October 200610 October 200610 October 2006 Only approved commits will be permitted to the ports/ tree during the freeze.
Begin 6.2-BETA3 builds30 October 200630 October 200630 October 200630 October 2006 Begin building the third public test release build for all Tier-1 platforms.
Release 6.2-BETA31 November 200631 October 20061 November 200631 October 2006 6.2-BETA3 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org.
RELENG_6_2 branch12 October 200615 November 200612 October 200615 November 2006 The release branch is created. Update newvers.sh and release.ent on various branches involved.
src/ unfrozen14 October 200618 November 200614 October 200618 November 2006 Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final.
Build 6.2-RC114 October 200615 November 200614 October 200615 November 2006 Begin building the first release candidate build for all Tier-1 platforms.
Release 6.2-RC115 October 200617 November 200615 October 200617 November 2006 6.2-RC1 Tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
Ports tree tagged24 October 200630 October 200624 October 200630 October 2006 RELEASE_6_2_0 tag for ports/.
Ports tree slush24 October 200630 October 200624 October 200630 October 2006 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.2-RELEASE. Also, wide sweeping commits are only allowed after explicit approval from portmgr@. The ports tree will be fully unfrozen after the release announcement.
Final package build starts24 October 200620 November 200624 October 200620 November 2006 The ports cluster and pointyhat build final packages.
Announce doc/ tree slush8 October 20068 October 2006 -- Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush23 October 200623 October 2006 -- 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.
Build 6.2-RC228 October 2006
- 25 November 2006		24 December 200628 October 2006
+ 25 November 2006		24 December 2006 Begin building the second release candidate build for all Tier-1 platforms.
Release 6.2-RC229 October 2006
- 27 November 2006		27 December 200629 October 2006
+ 27 November 2006		27 December 2006 6.2-RC2 Tier-1 platform images released and uploaded to ftp-master.FreeBSD.org.
doc/ tree tagged.29 October 20068 December 200629 October 20068 December 2006 Version number bumps for doc/ subtree. RELEASE_6_2_0 tag for doc/. doc/ slush ends at this time.
Version numbers bumped9 November 2006
- 8 January 2007		11 January 20079 November 2006
+ 8 January 2007		11 January 2007 The files listed here are updated to reflect FreeBSD 6.2.
src/ tree tagged9 November 2006
- 8 January 2007		11 January 20079 November 2006
+ 8 January 2007		11 January 2007 Tag the RELENG_6_2 branch with RELENG_6_2_0_RELEASE.
Begin 6.2-RELEASE builds9 November 2006
- 8 January 2007		11 January 20079 November 2006
+ 8 January 2007		11 January 2007 Start 6.2-RELEASE Tier-1 builds.
Warn mirror-announce@FreeBSD.org9 November 2006
- 8 January 2007		9 November 2006
+ 8 January 2007		 -- 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-master10 November 2006
- 8 January 2007		13 January 200710 November 2006
+ 8 January 2007		13 January 2007 Release and packages uploaded to ftp-master.FreeBSD.org.
Announcement13 November 2006
- 10 January 2007		15 January 200713 November 2006
+ 10 January 2007		15 January 2007 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to so@ TBD22 January 200722 January 2007 Control of the RELENG_6_2 branch is handed over to the FreeBSD Security Officer Team one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/6.2R/todo.html b/website/content/en/releases/6.2R/todo.html index 8923ca20da..97788c8b21 100644 --- a/website/content/en/releases/6.2R/todo.html +++ b/website/content/en/releases/6.2R/todo.html @@ -1,360 +1,360 @@ FreeBSD 6.2 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.2 Open Issues

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

Major issues for 6.2-RELEASE

Issue Status Responsible Description
No pending major issues.

Testing foci for 6.2-RELEASE

- + - + - + - + - + - +
Issue Status Responsible Description
bce(4) stability fixesNeeds testingNeeds testing Scott Long Several stability fixes for bce(4) were merged from HEAD to RELENG_6 around 20061024. Initial testing results have been promising, but more testing reports would be useful.
em(4) stability fixesNeeds testingNeeds testing Scott Long, Jack F. Vogel, Gleb Smirnoff, Kris Kennaway Several difficult-to-diagnose stability issues have been observed in the em(4) driver since August. As of 20061027, a newer driver provided by Intel (version 6.2.9) has been committed to RELENG_6 for testing. UPDATE: Additional changes committed 20061110 fix some other observed stability problems and restore missing jumbo frame functionality.
sysinstall(8) kernel selection fixNeeds testingNeeds testing Erwin Lansing A bug in sysinstall(8) could result in it failing to install a kernel on a new disk if the user did not choose a distribution from the distribution menu. This is believed to have been fixed as of 20061029, but could use more testing.
ggated(8)Needs testingNeeds testing Paweł Jakub Dawidek A recently-committed patch to ggated(8) is believed to fix some fairly serious problems, as reported in PR kern/104829.
devfs(5) fixesNeeds testingNeeds testing Konstantin Belousov Several deadlocks and locking bugs have been fixed in devfs(5).
tty(4) fixesNeeds testingNeeds testing Martin Blapp Several workarounds have been committed for known problems in the tty(4) layer.

Stress Test Panics

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. The following issues have recently been discovered from this test suite.


diff --git a/website/content/en/releases/6.3R/announce.html b/website/content/en/releases/6.3R/announce.html index e2bc367014..b50d97d90c 100644 --- a/website/content/en/releases/6.3R/announce.html +++ b/website/content/en/releases/6.3R/announce.html @@ -1,561 +1,561 @@ FreeBSD 6.3-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.3-RELEASE Announcement

Date: Fri, 18 Jan 2008 14:00:11 -0500
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 6.3 Released

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.3-RELEASE. This release continues the development of the 6-STABLE branch providing performance and stability improvements, many bug fixes and new features. Some of the highlights:

  • KDE updated to 3.5.8, GNOME updated to 2.20.1, Xorg updated to 7.3

  • BIND updated to 9.3.4

  • sendmail updated to 8.14.2

  • lagg(4) driver ported from OpenBSD/NetBSD

  • unionfs file system re-implemented

  • freebsd-update(8) now supports an upgrade command

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

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

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

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

The FreeBSD Security Team intends to support 6.3-RELEASE until January 31st, 2010.

Dedication

FreeBSD 6.3-RELEASE is dedicated to the memory of Dr. Jun-ichiro Hagino, known throughout the Internet community as itojun, for his visionary work on the IPv6 protocol and his many other contributions to the Internet and BSD communities.

Availability

FreeBSD 6.3-RELEASE is now available for the alpha, amd64, i386, pc98, and sparc64 architectures. It can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The contents of the ISO images provided as part of the release has changed for most of the architectures. Using the i386 architecture as an example, there are ISO images named ``bootonly'', ``disc1'', ``disc2'', ``disc3'', and ``docs''. The ``bootonly'' image is suitable for booting a machine to do a network based installation using FTP or NFS. The ``disc1'', ``disc2'', and ``disc3'' images are used to do a full installation that includes a basic set of packages and does not require network access to an FTP or NFS server during the installation. In addition, ``disc1'' supports booting into a live CD-based filesystem and system rescue mode. The ``docs'' image has all of the documentation for all supported languages. Most people will find that ``disc1'', ``disc2'' and ``disc3'' are all that are needed. If you intend to install ports from source instead of using the pre-built packages included with the release only ``disc1'' is needed.

FreeBSD 6.3-RELEASE can also be purchased on CD-ROM from several vendors. One of the vendors that will be offering FreeBSD 6.3-based products is:

Bittorrent

6.3-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP

The primary mirror site is:

ftp://ftp.freebsd.org/pub/FreeBSD/

However, 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

FreeBSD Update

Starting with FreeBSD 6.3, the freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems systems running earlier FreeBSD releases, release candidates, and betas. Users upgrading to FreeBSD 6.3 from older releases (in particular, older than 6.3-RC1) will need to download an updated version of freebsd-update(8) that supports upgrading to a new release.

# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz

Downloading and verifying the digital signature for the tarball (signed by the FreeBSD Security Officer's PGP key) is highly recommended.

# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc

# gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz

The new freebsd-update(8) can then be extracted and run as follows:

# tar -xf freebsd-update-upgrade.tgz

# sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade

# sh freebsd-update.sh -f freebsd-update.conf install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

Finally, freebsd-update.sh needs to be run one more time to install the new userland components, and the system needs to be rebooted one last time:

# sh freebsd-update.sh -f freebsd-update.conf install

# shutdown -r now

For more information, see:

http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 6.3 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, and Sentex Communications.

The release engineering team for 6.3-RELEASE includes:

Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386 sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Maxime Henrion <mux@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org> Release Engineering
Wilko Bulte <wilko@FreeBSD.org> Alpha 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
Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org> Security Officer
Peter Wemm <peter@FreeBSD.org> Bittorrent Coordination

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

 MD5 (6.3-RELEASE-alpha-bootonly.iso) = b9a479f20d84758202006b0fc446f52c
 MD5 (6.3-RELEASE-alpha-disc1.iso) = 4a5fd2fd27f966b3b65717ee79d0bf09
 MD5 (6.3-RELEASE-alpha-disc2.iso) = c1d05f366160f1a7b760cd92b2368158
 MD5 (6.3-RELEASE-alpha-disc3.iso) = aa3884eec1b62fba1c2f407ed5568d52
 MD5 (6.3-RELEASE-alpha-docs.iso) = c8f663a537e62668e7f26d4ba262d879
 
 MD5 (6.3-RELEASE-amd64-bootonly.iso) = 5ded1d6f91da4d872aef8c2ddba24dde
 MD5 (6.3-RELEASE-amd64-disc1.iso) = a8d41ea26769919db6c0c672fa8f8c4f
 MD5 (6.3-RELEASE-amd64-disc2.iso) = a243076fb99b011d9b0771a6f7f9a977
 MD5 (6.3-RELEASE-amd64-disc3.iso) = 92831414b34b4b06cfb7140ddfe69cfe
 MD5 (6.3-RELEASE-amd64-docs.iso) = d3662411f91a19df195df81fd23afdcc
 
 MD5 (6.3-RELEASE-i386-bootonly.iso) = ab1db0ae643e8c12ddbe855f533b8fae
 MD5 (6.3-RELEASE-i386-disc1.iso) = cdb0dfa4b2db3e4c9cc19138f4fb2ada
 MD5 (6.3-RELEASE-i386-disc2.iso) = e73a3d9cf5f3bfbf07384ef0a93ae5d5
 MD5 (6.3-RELEASE-i386-disc3.iso) = 123840107a5578ce22875c440d41f453
 MD5 (6.3-RELEASE-i386-docs.iso) = 17aa87ccfb01f4453d8ce078874029ab
 
 MD5 (6.3-RELEASE-pc98-bootonly.iso) = fc9921a841735b778164b3efed8fdd2c
 MD5 (6.3-RELEASE-pc98-disc1.iso) = df93a3981a866edeb76c47c84cf6db6d
 
 MD5 (6.3-RELEASE-sparc64-bootonly.iso) = 1726741e8c3406b103578509fc02cd37
 MD5 (6.3-RELEASE-sparc64-disc1.iso) = ebbc2252425b27491cee2eac88c523b5
 MD5 (6.3-RELEASE-sparc64-disc2.iso) = 3ed441f5478d0aba15d759d861ceee65
 MD5 (6.3-RELEASE-sparc64-disc3.iso) = cf6f35f7331904711a3fe9245e0c0be5
 MD5 (6.3-RELEASE-sparc64-docs.iso) = 11e0e61f4c39a418f0395e6980a880ee
 
 SHA256 (6.3-RELEASE-alpha-bootonly.iso) = 9798fd8c99b60b8b265d494447e12722bc330bf212cc5c668995684dc7532675
 SHA256 (6.3-RELEASE-alpha-disc1.iso) = f2df3edb20d00f5ec89cd23e11c5a304feb00444f67d3affcece1f5ce633e3e2
 SHA256 (6.3-RELEASE-alpha-disc2.iso) = 84882ca5b4370b6f23000eb7b806cd125958fbf42f61e14a9a991a258410793c
 SHA256 (6.3-RELEASE-alpha-disc3.iso) = 559cfe5025bddfdb8a6cfbf315874332149ed1cf73b64f63f6227c3c32d37d86
 SHA256 (6.3-RELEASE-alpha-docs.iso) = c913b3b65c093dfb830104c8153f06bf32c3bec49d3ded99abafeb7039f6f305
 
 SHA256 (6.3-RELEASE-amd64-bootonly.iso) = 8cdf4a486066943eb5fa8e36609bfb3c2da0d0128b699864eb95ca90007cea96
 SHA256 (6.3-RELEASE-amd64-disc1.iso) = 6ee1c2f00f8a1bc9d38b04b058b0549df9904ded52ddd19bae9dad070a5868e3
 SHA256 (6.3-RELEASE-amd64-disc2.iso) = f69e3ab103f4be34fea7b9dde4a34d5279948b4539dfe88c53e6b371d7962301
 SHA256 (6.3-RELEASE-amd64-disc3.iso) = cf6820b81eb1a1705d6294eb0bfa884bb6bad88c3be0e94c895283235c675abd
 SHA256 (6.3-RELEASE-amd64-docs.iso) = 1b7d78bb94902f15609c60332d4cfc534479ade5f5f72b9e52fc61ce48410cc4
 
 SHA256 (6.3-RELEASE-i386-bootonly.iso) = 124c340c1c54dc3f29c8d77e321205d47eec682bc147384dabe3fa2ae9e148f2
 SHA256 (6.3-RELEASE-i386-disc1.iso) = 15081a56d184a18c7cc3a5c3cd0d7d5b7d9304c9cc1d5fc40d875b0fd3047721
 SHA256 (6.3-RELEASE-i386-disc2.iso) = 7aabc815455f4ab80121071c5eb17c41dc355c2e45444b42a06158de4f9e482a
 SHA256 (6.3-RELEASE-i386-disc3.iso) = d606a1700c58074c606a6145e4ab713473ff4277ec2b81a82d33eff843711a2b
 SHA256 (6.3-RELEASE-i386-docs.iso) = 84a04e4478e92b9eb777900eba15b5f5ba0464cbba9caf49c19df2a1f28250f6
 
 SHA256 (6.3-RELEASE-pc98-bootonly.iso) = dd9d764189a0fc2d35bb78f07e169e4ec39561d018ffbaaa80da0c636fdb2800
 SHA256 (6.3-RELEASE-pc98-disc1.iso) = 641e98c9467ab7bc21767a054a6c7c9ff705f6295c58c32899e18daf597cc79c
 
 SHA256 (6.3-RELEASE-sparc64-bootonly.iso) = c9bdca8e894d37534da7ba823dda4ba38493ccfac709d615f4f5ec99b001c3d8
 SHA256 (6.3-RELEASE-sparc64-disc1.iso) = 5e7b155a7204c24117f50d330da979548eb7edded2669369575ed471812d8233
 SHA256 (6.3-RELEASE-sparc64-disc2.iso) = c54cd4a9760a30169c9daee27f4bb59281c7e5298db8ad7a0a66b094988aa298
 SHA256 (6.3-RELEASE-sparc64-disc3.iso) = 1c780cc51ff2231acd7179b2296cfac83b28e4ee32c34cc569744ae26556e97a
 SHA256 (6.3-RELEASE-sparc64-docs.iso) = 51201e31aaf7ebbdb4b6aecf2eebf97770347716e1ee9eb75cf807a0f14f6085

diff --git a/website/content/en/releases/6.3R/hardware.html b/website/content/en/releases/6.3R/hardware.html index f95f165722..2013fea25f 100644 --- a/website/content/en/releases/6.3R/hardware.html +++ b/website/content/en/releases/6.3R/hardware.html @@ -1,279 +1,279 @@ FreeBSD 6.3-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.3-RELEASE Hardware Notes

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 6.3-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.3R/installation.html b/website/content/en/releases/6.3R/installation.html index b5579ee6a6..3d1cd2a0f7 100644 --- a/website/content/en/releases/6.3R/installation.html +++ b/website/content/en/releases/6.3R/installation.html @@ -1,279 +1,279 @@ FreeBSD 6.3-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.3-RELEASE Installation Notes

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 6.3-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.3R/relnotes.html b/website/content/en/releases/6.3R/relnotes.html index 657865863f..85d30d54ea 100644 --- a/website/content/en/releases/6.3R/relnotes.html +++ b/website/content/en/releases/6.3R/relnotes.html @@ -1,279 +1,279 @@ FreeBSD 6.3-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.3-RELEASE Release Notes

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 6.3-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.3R/schedule.html b/website/content/en/releases/6.3R/schedule.html index d978e7ddd8..2cc13606b4 100644 --- a/website/content/en/releases/6.3R/schedule.html +++ b/website/content/en/releases/6.3R/schedule.html @@ -1,445 +1,445 @@ FreeBSD 6.3 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.3 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 6.3. 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 TBD15 Oct 200715 Oct 2007 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.3 release.
Announce the Ports Freeze23 Oct 200723 Oct 200723 Oct 200723 Oct 2007 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins18 Nov 200718 Nov 200718 Nov 200718 Nov 2007 After this date, all commits to RELENG_6 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.
Announce doc/ tree slush TBD19 Nov 200719 Nov 2007 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen30 Oct 200730 Oct 200730 Oct 200730 Oct 2007 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush25 Nov 200725 Nov 200725 Nov 200725 Nov 2007 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.5 Dec 20075 Dec 20075 Dec 20075 Dec 2007 Version number bumps for doc/ subtree. RELEASE_6_3_0 tag for doc/. doc/ slush ends at this time.
BETA1 builds24 Oct 20071 Nov 200724 Oct 20071 Nov 2007 Begin BETA1 builds.
BETA2 builds7 Nov 20079 Nov 20077 Nov 20079 Nov 2007 Begin BETA2 builds.
RELENG_6_3 branch21 Nov 200725 Nov 200721 Nov 200725 Nov 2007 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds21 Nov 200726 Nov 200721 Nov 200726 Nov 2007 Begin RC1 builds.
RC2 builds5 Dec 200722 Dec 20075 Dec 200722 Dec 2007 Begin RC2 builds.
Ports tree tagged14 Dec 200711 Dec 200714 Dec 200711 Dec 2007 RELEASE_6_3_0 tag for ports/.
Ports tree unfrozen14 Dec 200711 Dec 200714 Dec 200711 Dec 2007 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.3-RELEASE.
Final package build starts14 Dec 200712 Dec 200714 Dec 200712 Dec 2007 The ports cluster and pointyhat build final packages.
RELEASE builds19 Dec 200715 Jan 200819 Dec 200715 Jan 2008 Begin RELEASE builds.
Announcement23 Dec 200718 Jan 200823 Dec 200718 Jan 2008 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD28 Jan 200828 Jan 2008 RELENG_6_3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/6.4R/announce.html b/website/content/en/releases/6.4R/announce.html index f9fef850d6..29ccb124ea 100644 --- a/website/content/en/releases/6.4R/announce.html +++ b/website/content/en/releases/6.4R/announce.html @@ -1,575 +1,575 @@ FreeBSD 6.4-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.4-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.4-RELEASE. At this time 6.4-RELEASE is expected to be the last of the 6-STABLE releases. Some of the highlights:

  • New and much-improved NFS Lock Manager (NLM) client

  • Support for the Camellia cipher

  • boot loader changes allow, among other things, booting from USB devices and booting from GPT-labeled devices with GPT-enabled BIOSes

  • DVD install ISO images for amd64/i386

  • KDE updated to 3.5.10, GNOME updated to 2.22.3

  • Updates for BIND, sendmail, OpenPAM, and others

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

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

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

The FreeBSD Security Team intends to support 6.4-RELEASE until November 30th, 2010.

Availability

FreeBSD 6.4-RELEASE is now available for the amd64, i386, pc98, and sparc64 architectures. The builds for the alpha architecture have not completed yet and will be announced later. FreeBSD 6.4-RELEASE can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The contents of the ISO images provided as part of the release has changed for most of the architectures. Using the i386 architecture as an example, there are ISO images named "bootonly", "disc1", "disc2", "disc3", "docs", and "dvd1". The "bootonly" image is suitable for booting a machine to do a network based installation using FTP or NFS. The "disc1", "disc2", and "disc3" images are CDROM-sized (700MB media) and are used to do a full installation that includes a basic set of packages and does not require network access to an FTP or NFS server during the installation. In addition, "disc1" supports booting into a "live CD-based filesystem" and system rescue mode. The "docs" image has all of the documentation for all supported languages. The "dvd1" image is DVD-sized and includes everything that is on the CDROM discs. So "dvd1" can be used to do a full installation that includes a basic set of packages, it has all of the documentation for all supported languages, and it can be used for booting into a "live CD-based filesystem" and system rescue mode. Most people will find that "disc1", "disc2" and "disc3" are all that are needed if their machine does not have a DVD-capable drive. For people with machines that do have a DVD-capable drive "dvd1" should be all that is required. If you intend to install ports from source instead of using the pre-built packages included with the release only "disc1" is needed.

FreeBSD 6.4-RELEASE can also be purchased on CD-ROM from several vendors. One of the vendors that will be offering FreeBSD 6.4-based products is:

BitTorrent

6.4-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080

FTP

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

However before trying these sites you may want to 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

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 6.3-RELEASE, 6.4-BETA, 6.4-RC1, or 6.4-RC2 can upgrade as follows:

# freebsd-update upgrade -r 6.4-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install

# shutdown -r now

Note that FreeBSD Update stores downloaded upgrades in /var/db/freebsd-update, so at least 400MB should be free in /var before running freebsd-update; if the /var partition is too small, the -d option to freebsd-update can be used to indicate that the upgrades should be stored in a different directory.

For more information, see:

http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 6.4 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, and Sentex Communications.

The release engineering team for 6.4-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Maxime Henrion <mux@FreeBSD.org>Maxime Henrion <mux@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org>Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org>George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org>Murray Stokely <murray@FreeBSD.org> Release Engineering
Wilko Bulte <wilko@FreeBSD.org>Wilko Bulte <wilko@FreeBSD.org> Alpha Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org>Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer
Peter Wemm <peter@FreeBSD.org>Peter Wemm <peter@FreeBSD.org> Bittorrent Coordination

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (6.4-RELEASE-amd64-bootonly.iso) = 922fa2b990b3fd58bc558e08707dec47
 MD5 (6.4-RELEASE-amd64-disc1.iso) = 33e9801d546a9bd379d97c4dc9bf833f
 MD5 (6.4-RELEASE-amd64-disc2.iso) = 10e4a74cd4e80b52845adbabeb017532
 MD5 (6.4-RELEASE-amd64-disc3.iso) = 986d99df8a44cb3e8647b53e1551a56b
 MD5 (6.4-RELEASE-amd64-docs.iso) = be48876a37812fa19fb67aebe0c847de
 MD5 (6.4-RELEASE-amd64-dvd1.iso) = efd0dd71c5b13b8464d8a7fce8a90cbc
 
 MD5 (6.4-RELEASE-i386-bootonly.iso) = d3704b309b224fadeba29423511fbcff
 MD5 (6.4-RELEASE-i386-disc1.iso) = 3bf0054bf0d650c1c7289e3076f2a24f
 MD5 (6.4-RELEASE-i386-disc2.iso) = 2e5c68f0e8e82907e28394248973f2f6
 MD5 (6.4-RELEASE-i386-disc3.iso) = 75c4b9ed4bfc836471ca6aad7ff071db
 MD5 (6.4-RELEASE-i386-docs.iso) = a7e89a2006b34d5904ce74c907932918
 MD5 (6.4-RELEASE-i386-dvd1.iso) = 01d1b4445bbb70e643e7a096562ca4a3
 
 MD5 (6.4-RELEASE-pc98-bootonly.iso) = 6137dac091894d4eb620b02a94e3ddb6
 MD5 (6.4-RELEASE-pc98-disc1.iso) = 1ac648575affdb79e6f345b1210fee1b
 
 MD5 (6.4-RELEASE-sparc64-bootonly.iso) = 060cdc6c4fbcc96dcc13a88c09005079
 MD5 (6.4-RELEASE-sparc64-disc1.iso) = 2e2f264f9cdbfd73c531943631174dac
 MD5 (6.4-RELEASE-sparc64-docs.iso) = 33187d3f0459dbb2d1145aa8a4731497
 
 SHA256 (6.4-RELEASE-amd64-bootonly.iso) = 228cfe8b5d06bdf3131a656972d94919b594371464e5f1c68e068af17b88f382
 SHA256 (6.4-RELEASE-amd64-disc1.iso) = 6e8f24e153d78518268129db62e5efd3cd7b75e428a3c22bddf89eb901efa79e
 SHA256 (6.4-RELEASE-amd64-disc2.iso) = 33697f3290e9754baada1feeb560f5797a8794f80ea36ecc8b0305c0ab32f07a
 SHA256 (6.4-RELEASE-amd64-disc3.iso) = 59905ac81bc49be620e6a1465aba667be78b9276d999d820cca30357b073c263
 SHA256 (6.4-RELEASE-amd64-docs.iso) = 1bf1445e2cf19c108adfa973cab26891c3c9ee19664de3650f38fc11c67d9f9e
 SHA256 (6.4-RELEASE-amd64-dvd1.iso) = 88a0bd7818ecc2c26a6d304bffa9257f9bd192d6fb3b51ab1b538a5ef0e78130
 
 SHA256 (6.4-RELEASE-i386-bootonly.iso) = 82377be5c922610e7613f70066919da6d39c1e3fc753b6b925eae9bdd22ac946
 SHA256 (6.4-RELEASE-i386-disc1.iso) = c4f688013a27632e97caefc71296f59c9597abdb4e724385130d72dbd9abd218
 SHA256 (6.4-RELEASE-i386-disc2.iso) = 4936aaede7c55c29f1acb07724a86690ae220f53ba2f67b441f15fa0a4b282e8
 SHA256 (6.4-RELEASE-i386-disc3.iso) = 0c0ea48e2a07f2fc78c7d9448ad7cc24ffd224bbe4a9c1f7731358d7ce00d377
 SHA256 (6.4-RELEASE-i386-docs.iso) = 13ef3a3fe8799b71130ac2041e63156b30751d292d9d2df68f2b4a4318cbcc98
 SHA256 (6.4-RELEASE-i386-dvd1.iso) = 40b70eb8b36a5a13ef012592335d8e53cb9dea129a8b59971a999e84659ec6a8
 
 SHA256 (6.4-RELEASE-pc98-bootonly.iso) = 2d0fc39c377c8bf6e3ff1ab61b8ecd9b94231e3331bc442be7f26b37ed4cf59d
 SHA256 (6.4-RELEASE-pc98-disc1.iso) = dd2679fe503f7936fd4f7a6f5aa30e9c699d7eb78d382bef46eb9106dd0ab892
 
 SHA256 (6.4-RELEASE-sparc64-bootonly.iso) = eeabf33aa11cc764f41ea9bb50ae9109817953a60d22ed4af8c6bf61885ed648
 SHA256 (6.4-RELEASE-sparc64-disc1.iso) = c20f0a43732d72071cfdc17d788f3e04c1ac33e5ba122ce82fbd705ade482860
 SHA256 (6.4-RELEASE-sparc64-docs.iso) = 1728658de8be72e62afbc10bc50243cf07c532b8b4cf7426c5f74f09dc5b8243

diff --git a/website/content/en/releases/6.4R/hardware.html b/website/content/en/releases/6.4R/hardware.html index 3938f28503..12033f29b3 100644 --- a/website/content/en/releases/6.4R/hardware.html +++ b/website/content/en/releases/6.4R/hardware.html @@ -1,279 +1,279 @@ FreeBSD 6.4-RELEASE Hardware Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.4-RELEASE Hardware Notes

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 6.4-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.4R/installation.html b/website/content/en/releases/6.4R/installation.html index f2c3653eaa..d38b92d209 100644 --- a/website/content/en/releases/6.4R/installation.html +++ b/website/content/en/releases/6.4R/installation.html @@ -1,279 +1,279 @@ FreeBSD 6.4-RELEASE Installation Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.4-RELEASE Installation Notes

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 6.4-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.4R/relnotes.html b/website/content/en/releases/6.4R/relnotes.html index fce19914ea..40c2343a48 100644 --- a/website/content/en/releases/6.4R/relnotes.html +++ b/website/content/en/releases/6.4R/relnotes.html @@ -1,303 +1,303 @@ FreeBSD 6.4-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.4-RELEASE Release Notes

Release Highlights

The highlights in the 6.4-RELEASE are the following:

  • New and much-improved NFS Lock Manager (NLM) client

  • Support for the Camellia cipher

  • Boot loader changes allow, among other things, booting from USB devices and booting from GPT-labeled devices with GPT-enabled BIOSes

  • DVD install ISO images for amd64/i386

  • KDE updated to 3.5.10, GNOME updated to 2.22.3

  • Updates for BIND, sendmail, OpenPAM, and others

For more details, please see the Release Notes below.

Detailed Release Notes

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 6.4-RELEASE are available for the following platforms:

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


diff --git a/website/content/en/releases/6.4R/schedule.html b/website/content/en/releases/6.4R/schedule.html index 86f5bcbc48..c68bac1685 100644 --- a/website/content/en/releases/6.4R/schedule.html +++ b/website/content/en/releases/6.4R/schedule.html @@ -1,442 +1,442 @@ FreeBSD 6.4 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 6.4 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 6.4. 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 --22 August 200822 August 2008 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.4 release.
Announce the Ports Freeze --22 August 200822 August 2008 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins29 August 20082 September 200829 August 20082 September 2008 After this date, all commits to HEAD 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.
Announce doc/ tree slush TBD -- Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen8 September 20088 September 20088 September 20088 September 2008 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush8 September 20088 September 20088 September 20088 September 2008 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.15 September 200816 September 200815 September 200816 September 2008 Version number bumps for doc/ subtree. RELEASE_6_4_0 tag for doc/. doc/ slush ends at this time.
BETA1 builds1 September 20085 September 20081 September 20085 September 2008 Begin BETA1 builds.
RELENG_6_4 branch6 September 20082 October 20086 September 20082 October 2008 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds8 September 20085 October 20088 September 20085 October 2008 Begin RC1 builds.
Ports tree tagged15 September 200822 September 200815 September 200822 September 2008 RELEASE_6_4_0 tag for ports/.
Ports tree unfrozen15 September 200822 September 200815 September 200822 September 2008 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.4-RELEASE.
Final package build starts15 September 200822 September 200815 September 200822 September 2008 The ports cluster and pointyhat build final packages.
RC2 builds22 September 20082 November 200822 September 20082 November 2008 Begin RC2 builds.
RELEASE builds12 November 200826 November 200812 November 200826 November 2008 Begin RELEASE builds.
Announcement6 October 200828 November 20086 October 200828 November 2008 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD12 December 200812 December 2008 RELENG_6_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/7.0R/announce.html b/website/content/en/releases/7.0R/announce.html index fbe9912ed2..0f747e5762 100644 --- a/website/content/en/releases/7.0R/announce.html +++ b/website/content/en/releases/7.0R/announce.html @@ -1,645 +1,645 @@ FreeBSD 7.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.0-RELEASE Announcement

Date: Wed, 27 Feb 2008 17:19:52 -0500
From: Ken Smith <kensmith@FreeBSD.org>
To: freebsd-announce@FreeBSD.org
Subject: [FreeBSD-Announce] FreeBSD 7.0-RELEASE Available

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.0-RELEASE. This is the first release from the 7-STABLE branch which introduces many new features along with many improvements to functionality present in the earlier branches. Some of the highlights:

  • Dramatic improvements in performance and SMP scalability shown by various database and other benchmarks, in some cases showing peak performance improvements as high as 350% over FreeBSD 6.X under normal loads and 1500% at high loads. When compared with the best performing Linux kernel (2.6.22 or 2.6.24) performance is 15% better. Results are from benchmarks used to analyze and improve system performance, results with your specific work load may vary. Some of the changes that contribute to this improvement are:

    • The 1:1 libthr threading model is now the default.

    • Finer-grained IPC, networking, and scheduler locking.

    • A major focus on optimizing the SMP architecture that was put in place during the 5.x and 6.x branches.

    Some benchmarks show linear scaling up to 8 CPUs. Many workloads see a significant performance improvement with multicore systems.

  • The ULE scheduler is vastly improved, providing improved performance and interactive response (the 4BSD scheduler is still the default for 7.0 but ULE may become the default for 7.1).

  • Experimental support for Sun's ZFS filesystem.

  • gjournal can be used to set up journaled filesystems, gvirstor can be used as a virtualized storage provider.

  • Read-only support for the XFS filesystem.

  • The unionfs filesystem has been fixed.

  • iSCSI initiator.

  • TSO and LRO support for some network drivers.

  • Experimental SCTP (Stream Control Transmission Protocol) support (FreeBSD's being the reference implementation).

  • Much improved wireless (802.11) support.

  • Network link aggregation/trunking (lagg(4)) imported from OpenBSD.

  • JIT compilation to turn BPF into native code, improving packet capture performance.

  • Much improved support for embedded system development for boards based on the ARM architecture.

  • jemalloc, a new and highly scalable user-level memory allocator.

  • freebsd-update(8) provides officially supported binary upgrades to new releases in addition to security fixes and errata patches.

  • X.Org 7.3, KDE 3.5.8, GNOME 2.20.2.

  • GNU C compiler 4.2.1.

  • BIND 9.4.2.

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

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

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

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

Availability

FreeBSD 7.0-RELEASE is now available for the amd64, i386, ia64, pc98, and powerpc architectures. The version for the sparc64 architecture will become available in a few days. Some of the package builds are still in progress.

FreeBSD 7.0 can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The contents of the ISO images provided as part of the release has changed for most of the architectures. Using the i386 architecture as an example, there are ISO images named ``bootonly'', ``disc1'', ``disc2'', ``disc3'', ``livefs'', and ``docs''. The ``bootonly'' image is suitable for booting a machine to do a network based installation using FTP or NFS. The ``disc1'', ``disc2'', and ``disc3'' images are used to do a full installation that includes a basic set of packages and does not require network access to an FTP or NFS server during the installation. To boot into a ``live CD-based filesystem'' and system rescue mode ``disc1'' and ``livefs'' are needed. The ``docs'' image has all of the documentation for all supported languages. Most people will find that ``disc1'', ``disc2'' and ``disc3'' are all that are needed if you want to install some packages during the initial install, and just ``disc1'' if you prefer to install packages after the initial install is completed.

FreeBSD 7.0-RELEASE can also be purchased on CD-ROM from several vendors. One of the vendors that will be offering FreeBSD 7.0-based products is:

Bittorrent

7.0-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP

The primary mirror site is:

ftp://ftp.freebsd.org/pub/FreeBSD/

However, 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

Updating Existing Systems

An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes a major version upgrade, so no matter which method you use to update an older system you should reinstall any ports you have installed on the machine. This will avoid binaries becoming linked to inconsistent sets of libraries when future port upgrades rebuild one port but not others that link to it. This can be done with:

# portupgrade -faP

after updating your system. Note some of the tools to help with this or the instructions below for FreeBSD Update are not installed by default (e.g. portupgrade, gpg, or similar tools like portmaster).

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

The branch tag to use for updating the source is RELENG_7_0.

FreeBSD Update

Starting with FreeBSD 6.3, the freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems systems running earlier FreeBSD releases, release candidates, and betas. Users upgrading to FreeBSD 7.0 from older releases (in particular, older than 7.0-RC1) will need to download an updated version of freebsd-update(8) that supports upgrading to a new release.

# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz

Downloading and verifying the digital signature for the tarball (signed by the FreeBSD Security Officer's PGP key) is highly recommended.

# fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc

# gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz

The new freebsd-update(8) can then be extracted and run as follows:

# tar -xf freebsd-update-upgrade.tgz

# sh freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade

# sh freebsd-update.sh -f freebsd-update.conf install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

Next, freebsd-update.sh needs to be run again to install the new userland components, after which all ports should be recompiled to link to new libraries:

# sh freebsd-update.sh -f freebsd-update.conf install

# portupgrade -faP

Finally, freebsd-update.sh needs to be run one last time to remove old system libraries, after which the system should be rebooted in order that the updated userland and ports will be running:

# sh freebsd-update.sh -f freebsd-update.conf install

# shutdown -r now

For more information, see:

http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html

Support

The FreeBSD Security Team currently plans to support FreeBSD 7.0 until February 28th, 2009. For more information on the Security Team and their support of the various FreeBSD branches see:

http://www.freebsd.org/security/

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.0 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, and Sentex Communications.

The release engineering team for 7.0-RELEASE includes:

Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386 sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Maxime Henrion <mux@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc 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
Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org> Security Officer
Simon Nielsen <simon@FreeBSD.org> Deputy Security Officer
Peter Wemm <peter@FreeBSD.org> Bittorrent Coordination

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

 MD5 (7.0-RELEASE-amd64-bootonly.iso) = 60ff91f3a0851077a2c335f830e1e028
 MD5 (7.0-RELEASE-amd64-disc1.iso) = 0232f1b6ffde0e3e76034c9f10791acd
 MD5 (7.0-RELEASE-amd64-disc2.iso) = 17be33da3bdddfce3b32e697724e021e
 MD5 (7.0-RELEASE-amd64-disc3.iso) = 3d001985149acc50a5857626f20ddb93
 MD5 (7.0-RELEASE-amd64-docs.iso) = b0877e52f08aecd2e70ce86bd1ceb554
 MD5 (7.0-RELEASE-amd64-livefs.iso) = 6fea83a3679e8ac785c685f0e446788b
 
 MD5 (7.0-RELEASE-i386-bootonly.iso) = cb4f8d05d07aa74f2038050e53673455
 MD5 (7.0-RELEASE-i386-disc1.iso) = 5f185a688ef2e0db59105e8f439c8620
 MD5 (7.0-RELEASE-i386-disc2.iso) = bb59156b4fc1f9c148095b8c239c827a
 MD5 (7.0-RELEASE-i386-disc3.iso) = 44de27d5f6bcdbf14e3db38c84f12348
 MD5 (7.0-RELEASE-i386-docs.iso) = bcf16778ecc73975024a8e6450ee4ba4
 MD5 (7.0-RELEASE-i386-livefs.iso) = abe6773601feda1dc56dade0022fca59
 
 MD5 (7.0-RELEASE-ia64-bootonly.iso) = 0acd75c4c191609bd5d39428c556f59c
 MD5 (7.0-RELEASE-ia64-disc1.iso) = f79c20fcf15d084d1b1bc47023678ecf
 MD5 (7.0-RELEASE-ia64-disc2.iso) = 517ae3572002f7deba02f5f35799bcee
 MD5 (7.0-RELEASE-ia64-disc3.iso) = 2d6c64c4f3e166e8e329977c94c6ea72
 MD5 (7.0-RELEASE-ia64-docs.iso) = 262a7dda8a7e0747807f1c32c293eb4b
 MD5 (7.0-RELEASE-ia64-livefs.iso) = 1b4daa26d5a89130f7e45e85fd1501a7
 
 MD5 (7.0-RELEASE-pc98-bootonly.iso) = 0359f519b7185b1747524d3a3a433f52
 MD5 (7.0-RELEASE-pc98-disc1.iso) = 90889420c8afc72d8a3dbce45c21c716
 MD5 (7.0-RELEASE-pc98-livefs.iso) = 583e4d51629a0c644495e56eb899b917
 
 MD5 (7.0-RELEASE-powerpc-bootonly.iso) = ba968855e8ccfcdfce0657cf591307fa
 MD5 (7.0-RELEASE-powerpc-disc1.iso) = b553330bd7ccc1683559a6507ab0e304
 MD5 (7.0-RELEASE-powerpc-disc2.iso) = bb58530a5b623fad5f55d17cc382cc2d
 MD5 (7.0-RELEASE-powerpc-disc3.iso) = d1dd0645b24f16aa01e2e3f6c88f189a
 MD5 (7.0-RELEASE-powerpc-docs.iso) = 84a164f4795894b9bb247ea16c97c645
 
 SHA256 (7.0-RELEASE-amd64-bootonly.iso) = 596bc89d0926fd15ae16d8f3c4c5735289c7553bdac8062284940830c26d2555
 SHA256 (7.0-RELEASE-amd64-disc1.iso) = d3b206eb74df7559041dd9054de7352b9a67d4f350e75f433c7fb001bf4b5c6f
 SHA256 (7.0-RELEASE-amd64-disc2.iso) = 296e02387794b06992c294450b4c6c07cc6a5530f415901492dcd721809d96b5
 SHA256 (7.0-RELEASE-amd64-disc3.iso) = 683545d8768a3f7fa1ae5a2c0f2586e88a09b43b9b1f57da384c30339fd889e5
 SHA256 (7.0-RELEASE-amd64-docs.iso) = 6d69c5c27a4e5891fed9a88e5825af803558c14281257bc3b325b00a2a62a966
 SHA256 (7.0-RELEASE-amd64-livefs.iso) = 596b5f69d7f2c4e17f66e0fd1306a192cc03a700b0dce3532e95abffd5e5344a
 
 SHA256 (7.0-RELEASE-i386-bootonly.iso) = 3184674f1833c7abdc687672188e1189f61d5f7239ba48df584787b8e1d0273b
 SHA256 (7.0-RELEASE-i386-disc1.iso) = 7480c74dda9a78805ab0d647b23eb71cac43f4afce83ff65ad9f2019423583af
 SHA256 (7.0-RELEASE-i386-disc2.iso) = 55c12b9c7239ee22e84594e07736c4b73e5788a6330cd76a199c1b99bd4bea51
 SHA256 (7.0-RELEASE-i386-disc3.iso) = 2812afd48559c5b38338eee0697c33b25d9127f60b03eb04c77799ac6523dde0
 SHA256 (7.0-RELEASE-i386-docs.iso) = 428fc1d0fc820326be04c673bd8c228fbccd0761d59e50b11dfd8e508820a661
 SHA256 (7.0-RELEASE-i386-livefs.iso) = 6ca035fa860f6942b983de628fc1df829c22e7c55a7ab4d0bb342a5c53792f94
 
 SHA256 (7.0-RELEASE-ia64-bootonly.iso) = a133c1acf597dc7a36ec0239cb4aa93ca08e85a95f47f3bad8e9eed4f494928e
 SHA256 (7.0-RELEASE-ia64-disc1.iso) = 1d2c1de094705f095adf5ffc76e34da3ed8a881409766e5450b22a33a3c8626e
 SHA256 (7.0-RELEASE-ia64-disc2.iso) = c628e4abfac5f87ea6a0ba899db023b21115ce817620d2a48a261e2af6daae56
 SHA256 (7.0-RELEASE-ia64-disc3.iso) = 22b7192b52f7765a5f42fff284fe58eaaad068f2021ddcecbf11b9bd02a3db49
 SHA256 (7.0-RELEASE-ia64-docs.iso) = a103f78ab620120c0fc945ad7b07b85c4a182f8e045b17dcfc8ba5faf9d21a88
 SHA256 (7.0-RELEASE-ia64-livefs.iso) = 3adcd9e3afd3b52f75b1f4b0c0a02dbb6af4bcbc016b3837bd527a01702af847
 
 SHA256 (7.0-RELEASE-pc98-bootonly.iso) = 8e6ee4327af57ed6ddb3c890c5cc8e8b051bbc51cfa7a1c7cd53bd4685dbc01d
 SHA256 (7.0-RELEASE-pc98-disc1.iso) = c4ec9b975f68ea7f278462fff0db8f6138d57effa462e3b20035994155e93c4b
 SHA256 (7.0-RELEASE-pc98-livefs.iso) = 20f6cc867590798c79716e771abf4c6880452defd5dcd0aed21161d54ab3d40e
 
 SHA256 (7.0-RELEASE-powerpc-bootonly.iso) = 86a6398f34e9f933adfd717024dd3eefd4e209f940cc3487c047cb979ec8dbfa
 SHA256 (7.0-RELEASE-powerpc-disc1.iso) = b75e61be2f3daac9898e61c7e00086fcc039bf894211800bd40335424e5afc7d
 SHA256 (7.0-RELEASE-powerpc-disc2.iso) = 69ffdea7850aa2ebd609851ca22dfe2c92d1d7606ac621e99de3b6e2998be553
 SHA256 (7.0-RELEASE-powerpc-disc3.iso) = 1f1cacb35e647e3480c120ba19e8b3b55b8d02f98b7672784a5e729ced840a48
 SHA256 (7.0-RELEASE-powerpc-docs.iso) = e6c2965dbced365738c7816dfaf47ab2eec450aff2dd8d9ae4ee10d015458785

diff --git a/website/content/en/releases/7.0R/approvals.html b/website/content/en/releases/7.0R/approvals.html index 9354aa17d7..c086c5d6e3 100644 --- a/website/content/en/releases/7.0R/approvals.html +++ b/website/content/en/releases/7.0R/approvals.html @@ -1,294 +1,294 @@ FreeBSD 7.0 Commit Approvals
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.0 Commit Approvals

Introduction

The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.

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.

Approval List

Committer Area Expiration
No approval granted yet.

Additional Information


diff --git a/website/content/en/releases/7.0R/schedule.html b/website/content/en/releases/7.0R/schedule.html index c95d8e1eec..9970873b97 100644 --- a/website/content/en/releases/7.0R/schedule.html +++ b/website/content/en/releases/7.0R/schedule.html @@ -1,469 +1,469 @@ FreeBSD 7.0 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.0 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 7.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.

Schedule

- + - - + + - - + + - + - - + + - - + + - - + + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - +
Action Expected Actual Description
Reminder announcement TBD15 Oct 200715 Oct 2007 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.0 release.
Announce the Ports Freeze23 Oct 200723 Oct 200723 Oct 200723 Oct 2007 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins18 June 200719 June 200718 June 200719 June 2007 After this date, all commits to HEAD 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.
Announce doc/ tree slush TBD19 Nov 200719 Nov 2007 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen30 Oct 200730 Oct 200730 Oct 200730 Oct 2007 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush25 Nov 200725 Nov 200725 Nov 200725 Nov 2007 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.5 Dec 20075 Dec 20075 Dec 20075 Dec 2007 Version number bumps for doc/ subtree. RELEASE_7_0_0 tag for doc/. doc/ slush ends at this time.
RELENG_7 branch --11 Oct 200711 Oct 2007 The new major version branch is created. Update newvers.sh and release.ent on various branches involved.
BETA1 builds17 Oct 200719 Oct 200717 Oct 200719 Oct 2007 Begin BETA1 builds.
BETA2 builds31 Oct 200731 Oct 200731 Oct 200731 Oct 2007 Begin BETA2 builds.
BETA3 builds14 Nov 200716 Nov 200714 Nov 200716 Nov 2007 Begin BETA3 builds.
BETA4 builds28 Nov 20072 Dec 200728 Nov 20072 Dec 2007 Begin BETA4 builds.
RELENG_7_0 branch12 Dec 200722 Dec 200712 Dec 200722 Dec 2007 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds12 Dec 200722 Dec 200712 Dec 200722 Dec 2007 Begin RC1 builds.
RC2 builds28 Jan 20087 Feb 200828 Jan 20087 Feb 2008 Begin RC2 builds.
Ports tree tagged14 Dec 200711 Dec 200714 Dec 200711 Dec 2007 RELEASE_7_0_0 tag for ports/.
Ports tree unfrozen14 Dec 200711 Dec 200714 Dec 200711 Dec 2007 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.0-RELEASE.
Final package build starts14 Dec 200712 Dec 200714 Dec 200712 Dec 2007 The ports cluster and pointyhat build final packages.
RELEASE builds11 Feb 200823 Feb 200811 Feb 200823 Feb 2008 Begin RELEASE builds.
Announcement26 Feb 200827 Feb 200826 Feb 200827 Feb 2008 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD5 Mar 20085 Mar 2008 RELENG_7_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/7.0R/todo.html b/website/content/en/releases/7.0R/todo.html index bb85cfc649..66fda10451 100644 --- a/website/content/en/releases/7.0R/todo.html +++ b/website/content/en/releases/7.0R/todo.html @@ -1,403 +1,403 @@ FreeBSD 7.0 Open Issues
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.0 Open Issues

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

Major issues for 7.0-RELEASE

Issue Status Responsible Description
routed not working Done Robert Watson Routed should have been updated because of updates made to the underlying network infrastructure. The old interface was added back in but marked as depreciated.
TCP accept race condition Done Gleb Smirnoff, Robert Watson A race in TCP will lead to very occasional returning of 0.0.0.0:0 rather than the correct IP address via the socket address returned by accept(). A patch has been merged to HEAD, RELENG_7 and RELENG_7_0.
sleepq race condition Done John Baldwin Races in the sleepq implementation will occasionally result in sleeps with timeouts failing to wake up, as well as other symptoms. A patch has been merged to HEAD, RELENG_7, and RELENG_7_0.
pty race condition Done Konstantin Belousov Multiple race conditions in the tty/pty code have lead to occasional panics. One set of problems has been fixed, but others are still being explored It is aniticipated that the remaining problems will be fixed for 7.0RC2.
amd64 minidump race condition Done Ruslan Ermilov A race condition during minidump generation on SMP amd64 could lead trashed file systems due to writing outside of the swap area. A patch has been merged to HEAD, RELENG_7, and RELENG_7_0.
libkse fork process wedge Done Julian Elischer, Daniel Eischen A bug in libkse could lead the processes hanging after fork if they fork while running multiple threads. A patch has been committed to HEAD that properly reinitializes internal thread library locks after fork; it has been merged to RELENG_7 and RELENG_7_0.

Minor issues for 7.0-RELEASE

Issue Status Responsible Description
sparc64 has a problem building OpenSP so it can't finish a release build with docs Done Marius Strobl Fixed.

Testing foci for 7.0-RELEASE

- +
Issue Status Responsible Description
TCP timersNeeds testingNeeds testing Mike Silbersack
MAC Framework Robert Watson A code sync with Mac OS X Leopard for the MAC framework was committed.
TCP issues Done Mike Silbersack Turned out to not be TCP issues after all, problems with signal handling in mountd.

Stress Test Panics

The system is continuously being subjected to Peter Holm's Kernel Stress Test Suite. The following issues have recently been discovered from this test suite.


diff --git a/website/content/en/releases/7.1R/announce.html b/website/content/en/releases/7.1R/announce.html index 8eb5540aa3..45ac6ef427 100644 --- a/website/content/en/releases/7.1R/announce.html +++ b/website/content/en/releases/7.1R/announce.html @@ -1,671 +1,671 @@ FreeBSD 7.1-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.1-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.1-RELEASE. This is the second release from the 7-STABLE branch which improves on the functionality of FreeBSD 7.0 and introduces some new features. Some of the highlights:

  • The ULE scheduler is now the default in GENERIC kernels for amd64 and i386 architectures. The ULE scheduler significantly improves performance on multicore systems for many workloads.

  • Support for using DTrace inside the kernel has been imported from OpenSolaris. DTrace is a comprehensive dynamic tracing framework.

  • A new and much-improved NFS Lock Manager (NLM) client.

  • Boot loader changes allow, among other things, booting from USB devices and booting from GPT-labeled devices.

  • The cpuset(2) system call and cpuset(1) command have been added, providing an API for thread to CPU binding and CPU resource grouping and assignment.

  • KDE updated to 3.5.10, GNOME updated to 2.22.3.

  • DVD-sized media for the amd64 and i386 architectures

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

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

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

Availability

FreeBSD 7.1-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.

FreeBSD 7.1 can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the ISO images provided as part of the release are as follows:

dvd1:

Contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, the documentation, and supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1, disc2, disc3, livefs, docs:

disc1 contains the base FreeBSD system and a few pre-built packages. disc2 and disc3 contain more pre-built packages. Those three can be burned to CDROM sized media and should be all you need to do a normal installation. livefs contains support for entering into a "livefs" based rescue mode but you need disc1 to do the initial boot first. docs contains the documentation.

bootonly:

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself, you would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

FreeBSD 7.1-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 7.1-based products is:

BitTorrent

7.1-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

http://torrents.freebsd.org:8080

FTP

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

However before trying these sites you may want to 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

Updating Existing Systems

NOTE: If updating from a 7.0 or earlier system due to a change in the Vendor's drivers certain Intel NICs will now come up as igb(4) instead of em(4). We normally try to avoid changes like that in stable branches but the vendor felt it necessary in order to support the new adapters. See the UPDATING entry dated 20080811 for details. There are only 3 PCI ID's that should have their name changed from em(4) to igb(4): 0x10A78086, 0x10A98086, and 0x10D68086. You should be able to determine if your card will change names by running the command "pciconf -l", and for the line representing your NIC (should be named em on older systems, e.g. em0 or em1, etc) check the fourth column. If that says "chip="0x10a78086"" (or one of the other two IDs given above) you will have the adapter's name change.

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_7_1.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-BETA, 7.1-BETA2, 7.1-RC1, or 7.1-RC2 can upgrade as follows:

# freebsd-update upgrade -r 7.1-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install

# shutdown -r now

Users of Intel network interfaces which are changing their name from "em" to "igb" should make necessary changes to configuration files BEFORE running freebsd-update, since otherwise the network interface will not be configured appropriately after rebooting for the first time.

Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.1, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x.

For more information, see:

http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html

Support

The FreeBSD Security Team currently plans to support FreeBSD 7.1 until January 31st 2011. For more information on the Security Team and their support of the various FreeBSD branches see:

http://www.freebsd.org/security/

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.1 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Network Appliances, and Sentex Communications.

The release engineering team for 7.1-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Maxime Henrion <mux@FreeBSD.org>Maxime Henrion <mux@FreeBSD.org> Release Engineering
Bruce A. Mah <bmah@FreeBSD.org>Bruce A. Mah <bmah@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org>George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Murray Stokely <murray@FreeBSD.org>Murray Stokely <murray@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org>Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer
Peter Wemm <peter@FreeBSD.org>Peter Wemm <peter@FreeBSD.org> Bittorrent Coordination

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (7.1-RELEASE-amd64-bootonly.iso) = f127de85eb1f3a945b56ef750fa610ae
 MD5 (7.1-RELEASE-amd64-disc1.iso) = ac88bfa3359aea242450d74c20347bde
 MD5 (7.1-RELEASE-amd64-disc2.iso) = 918d89e3ee330f5bd13535bc82def802
 MD5 (7.1-RELEASE-amd64-disc3.iso) = d01747e4de48acb052f827d723ef9672
 MD5 (7.1-RELEASE-amd64-docs.iso) = 4558db657d0b021849c2b1a802e1bea4
 MD5 (7.1-RELEASE-amd64-dvd1.iso) = df1a3604d4f99b7cf3511d42d33c550a
 MD5 (7.1-RELEASE-amd64-livefs.iso) = 83dd8e10ff27f8799c66bd4bd26ac5b3
 
 MD5 (7.1-RELEASE-i386-bootonly.iso) = 6988cd1662a03e5465cb38b1100a28eb
 MD5 (7.1-RELEASE-i386-disc1.iso) = ebdea2ebae35597bed323047cd70bcf2
 MD5 (7.1-RELEASE-i386-disc2.iso) = e20444a71dd709d92f3340323e58535c
 MD5 (7.1-RELEASE-i386-disc3.iso) = e64fab3db2917e1ba15bc72ab2af35f6
 MD5 (7.1-RELEASE-i386-docs.iso) = e04e8dc0261fc947efb699faf8852eb8
 MD5 (7.1-RELEASE-i386-dvd1.iso) = bbb47ab60bda55270ddd9ff4f73b9dc8
 MD5 (7.1-RELEASE-i386-livefs.iso) = 148b2aae58b4a9e27970ff77b5dd6f08
 
 MD5 (7.1-RELEASE-ia64-bootonly.iso) = 43c55b764bcc0b6c7ec07037cdca12a7
 MD5 (7.1-RELEASE-ia64-disc1.iso) = 47ffbdbdf8b258c6b1018e3a75b3cab3
 MD5 (7.1-RELEASE-ia64-disc2.iso) = e603d24d1c8e21dbc8e85e4bf30f0482
 MD5 (7.1-RELEASE-ia64-disc3.iso) = ef356f4e4efc7258899a9ead3fa834ea
 MD5 (7.1-RELEASE-ia64-docs.iso) = 7dba36505623251068e7fc1f06099634
 MD5 (7.1-RELEASE-ia64-livefs.iso) = d3f6f2d47b1bd2b46cb7db7180215385
 
 MD5 (7.1-RELEASE-pc98-bootonly.iso) = c46d9eed8fb421f294ffd6a6770dbd46
 MD5 (7.1-RELEASE-pc98-disc1.iso) = 90d8d8c24d8a14c166428df037addc68
 MD5 (7.1-RELEASE-pc98-livefs.iso) = 4c578bfe71d3dd7c2de4ba490fae04ee
 
 MD5 (7.1-RELEASE-powerpc-bootonly.iso) = c7f8b40c7b7194f4b40776b86864e257
 MD5 (7.1-RELEASE-powerpc-disc1.iso) = 228c53863c604298f66a86f0a1fd4f88
 MD5 (7.1-RELEASE-powerpc-disc2.iso) = a1d8c054fdfa420ac1965ca0795f6693
 MD5 (7.1-RELEASE-powerpc-disc3.iso) = 24aa15c263cebf28e1d2f66f7c6b9215
 MD5 (7.1-RELEASE-powerpc-docs.iso) = 3073516ccd548a979794ea0aaba7b732
 
 MD5 (7.1-RELEASE-sparc64-bootonly.iso) = 0fd076346a8d6d49601f4aaa2148edb1
 MD5 (7.1-RELEASE-sparc64-disc1.iso) = 715680a781ed8649271430c10f7907db
 MD5 (7.1-RELEASE-sparc64-disc2.iso) = 7179853c118549dbe780f94e74e90ddf
 MD5 (7.1-RELEASE-sparc64-disc3.iso) = f640b3a800c18020279158f444cf1643
 MD5 (7.1-RELEASE-sparc64-docs.iso) = 94d5661906826735b0a4264197a5f4b4
 
 SHA256 (7.1-RELEASE-amd64-bootonly.iso) = a633924d756812eb6916d0e9cc2821c20935daaf76eb741319bcabd246a2d4ab
 SHA256 (7.1-RELEASE-amd64-disc1.iso) = 4f7deebbd5e3211d144c6e630b808e918fcbb901ff4689b64087ed4c2d6e781d
 SHA256 (7.1-RELEASE-amd64-disc2.iso) = 2236148b61b896d62086889bc6fedaf36a24dbf327c1d1f30f79a6c1ff677b8d
 SHA256 (7.1-RELEASE-amd64-disc3.iso) = 19035ad37eae028bf27b060ea10ecff7a9cc9feae10f951d63907b6be852c458
 SHA256 (7.1-RELEASE-amd64-docs.iso) = ac17871f20b9438ce27ec6598c2441c8ad58f19b5696cacddc332976c2e24a4c
 SHA256 (7.1-RELEASE-amd64-dvd1.iso) = 1c148191e8c01191011d5fde4688aaa567a166838ed9722d1ae73451c4ef2b7d
 SHA256 (7.1-RELEASE-amd64-livefs.iso) = 1a30fca92c806b2f58c569c894bec221e7e2aad9c2937e6c09cd8e340bfb0903
 
 SHA256 (7.1-RELEASE-i386-bootonly.iso) = ad848e85c0a8e83fc5c26fad4f370eb6c34d2e3154966cd460788f56f734085c
 SHA256 (7.1-RELEASE-i386-disc1.iso) = 58e588c26d06b84d8c3c01d8507b2ffe2e237b167f72604c82d34011dc850a46
 SHA256 (7.1-RELEASE-i386-disc2.iso) = 6d0476f77e3a17863eddf59eadb41ecb52c4399614442a0df39f97c8e4c74b2e
 SHA256 (7.1-RELEASE-i386-disc3.iso) = b58d19c5bcb88e5651dce06ccf55bd9a309efaec2b2fe47a9277343a8f6646fe
 SHA256 (7.1-RELEASE-i386-docs.iso) = 521e45641f4e50168a74ea315720d13844e8a1220f28656302aca8281261ac5b
 SHA256 (7.1-RELEASE-i386-dvd1.iso) = 303be4ce844f0cb18aa38a41988dc5fba960427dbcc69263410308176cb5875f
 SHA256 (7.1-RELEASE-i386-livefs.iso) = db1609e72ad3f979b3f6d954ac2811588cc99c460c57e3035835cb604447dc0d
 
 SHA256 (7.1-RELEASE-ia64-bootonly.iso) = 059c82e3e4b535730795a52b939d3085c7cd891a37570a3567e47dee6a345787
 SHA256 (7.1-RELEASE-ia64-disc1.iso) = e97ad79b9f21e3554e47bd125a25dea5adac112608bbcba8c60d45aebc0b1837
 SHA256 (7.1-RELEASE-ia64-disc2.iso) = f1c91524eebe8d1933057669ad7ce1343f18aecbad092d1402652e6c0d69f7a9
 SHA256 (7.1-RELEASE-ia64-disc3.iso) = ed838b4c4801d6244f33cdd02abcca4c208b0dd2d89c6f0446a1913d95662096
 SHA256 (7.1-RELEASE-ia64-docs.iso) = dd7c1dc8fe4968bd32b2fef42b21460211bef5284ecf9be53490de595f4b6a8b
 SHA256 (7.1-RELEASE-ia64-livefs.iso) = 81a8cad96e8540e32a9197d4dcba587b1266a8d56ff75db3755381471793e90f
 
 SHA256 (7.1-RELEASE-pc98-bootonly.iso) = 8b4038d22b59464e7df7cc1273a1929bdf89be77bc8fecfa88faf4d81db049c9
 SHA256 (7.1-RELEASE-pc98-disc1.iso) = 43eae1bc95cc307f0b228cd8388c94cfad0db1402650e5b31262c8a2040ead7a
 SHA256 (7.1-RELEASE-pc98-livefs.iso) = ba4e744629fb5a7f40e288b15a39dc971c3a5108a38e9952ec00fd951292f677
 
 SHA256 (7.1-RELEASE-powerpc-bootonly.iso) = e1c0e47b3aa66604853e9a27ccad381d1abb3b6dbe49fc7a773ba91720dd5862
 SHA256 (7.1-RELEASE-powerpc-disc1.iso) = e672b975d10502677076014804d486c406e79cd7724353f76abc68b55dd5972e
 SHA256 (7.1-RELEASE-powerpc-disc2.iso) = 9f6aff26f127a229cdae1e73c4eb25d6d51b595380110bb99f9882b88c0a2a20
 SHA256 (7.1-RELEASE-powerpc-disc3.iso) = 0c0c3a012fad489b425d35e4df539f23be4c26cc46a950f5699b84da4a37bdb2
 SHA256 (7.1-RELEASE-powerpc-docs.iso) = 4fc75610e7bed8c05e474053266b4a8cce40c039707e39970ca2cf78ff99dee9
 
 SHA256 (7.1-RELEASE-sparc64-bootonly.iso) = d8259fa546988201cb629ce606a10f8928e7b93a6e317e4078abbe6804bd5068
 SHA256 (7.1-RELEASE-sparc64-disc1.iso) = 020030fff08be2a2e99dfa057096a27305c762ad5aebc4b880de84587dd3ef1a
 SHA256 (7.1-RELEASE-sparc64-disc2.iso) = 0d287b855a94317332d0dada8ac6ba2e216200f76551e463e94af30dc14cebdc
 SHA256 (7.1-RELEASE-sparc64-disc3.iso) = 246c73be0f35fcdc7437b346a796c6224a9de887325cdc99f3008fd961c47edb
 SHA256 (7.1-RELEASE-sparc64-docs.iso) = 30e298e8d36cdabcf6b48eea5d5fb784351c44f8cb97df29695037d9513843cc

diff --git a/website/content/en/releases/7.1R/schedule.html b/website/content/en/releases/7.1R/schedule.html index 1cc44960b3..f465e1f9ae 100644 --- a/website/content/en/releases/7.1R/schedule.html +++ b/website/content/en/releases/7.1R/schedule.html @@ -1,447 +1,447 @@ FreeBSD 7.1 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.1 Release Process

Introduction

This is a specific schedule for the release of FreeBSD 7.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.

Schedule

- + - + - - + + - + - - + + - - + + - - + + - - + + - + - - + + - - + + - - + + - - + + - - + + - - + + - + - - + +
Action Expected Actual Description
Reminder announcement --22 August 200822 August 2008 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.1 release.
Announce the Ports Freeze --22 August 200822 August 2008 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins29 August 20082 September 200829 August 20082 September 2008 After this date, all commits to RELENG_7 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.
Announce doc/ tree slush --2 September 20082 September 2008 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen8 September 20088 September 20088 September 20088 September 2008 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush8 September 20088 September 20088 September 20088 September 2008 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.15 September 200816 September 200815 September 200816 September 2008 Version number bumps for doc/ subtree. RELEASE_7_1_0 tag for doc/. doc/ slush ends at this time.
BETA1 builds1 September 20085 September 20081 September 20085 September 2008 Begin BETA1 builds.
BETA2 builds --19 October 200819 October 2008 Begin BETA2 builds.
RELENG_7_1 branch6 September 200825 November 20086 September 200825 November 2008 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds15 September 20088 December 200815 September 20088 December 2008 Begin RC1 builds.
Ports tree tagged15 September 200822 September 200815 September 200822 September 2008 RELEASE_7_1_0 tag for ports/.
Ports tree unfrozen15 September 200822 September 200815 September 200822 September 2008 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.1-RELEASE.
Final package build starts15 September 200822 September 200815 September 200822 September 2008 The ports cluster and pointyhat build final packages.
RC2 builds29 September 200822 December 200829 September 200822 December 2008 Begin RC2 builds.
RELEASE builds TBD1 January 20091 January 2009 Begin RELEASE builds.
Announcement13 October 20085 January 200913 October 20085 January 2009 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD -- RELENG_7_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/7.2R/announce.html b/website/content/en/releases/7.2R/announce.html index ac6b5a55db..7cf4ca5aff 100644 --- a/website/content/en/releases/7.2R/announce.html +++ b/website/content/en/releases/7.2R/announce.html @@ -1,649 +1,649 @@ FreeBSD 7.2-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.2-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.2-RELEASE. This is the third release from the 7-STABLE branch which improves on the functionality of FreeBSD 7.1 and introduces some new features. Some of the highlights:

  • support for fully transparent use of superpages for application memory

  • support for multiple IPv4 and IPv6 addresses for jails

  • csup(1) now supports CVSMode to fetch a complete CVS repository

  • Gnome updated to 2.26, KDE updated to 4.2.2

  • sparc64 now supports UltraSparc-III processors

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

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

Availability

FreeBSD 7.2-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.

FreeBSD 7.2 can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the ISO images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1, disc2, disc3, livefs, docs

disc1 contains the base FreeBSD operating system and a few pre-built packages. disc2 and disc3 contain more pre-built packages. Those three can be burned to CDROM sized media and should be all you need to do a normal installation. livefs contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. You would need to perform a network based install. docs contains the documentation.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

Note: late in the testing cycle it was discovered some machines do not recognize the i386 disc1 as bootable (they just fall through to booting off the next boot device). All affected machines did see the other discs as bootable. If you have a machine with that problem booting off either bootonly or livefs and then swapping in disc1 once sysinstall starts should work.

FreeBSD 7.2-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 7.2-based products is:

BitTorrent

7.2-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_7_2.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-BETA, 7.2-RC1, or 7.2-RC2 can upgrade as follows:

# freebsd-update upgrade -r 7.2-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install
 # shutdown -r now

Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.2, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x.

For more information about upgrading from FreeBSD 6.x using FreeBSD Update, see:

Support

The FreeBSD Security Team currently plans to support FreeBSD 7.2 until May 31st, 2010. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.2 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.

The release engineering team for 7.2-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org>George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Kris Kennaway <kris@FreeBSD.org>Kris Kennaway <kris@FreeBSD.org> Package Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (7.2-RELEASE-amd64-bootonly.iso) = d77d758684d03815be05f90c12085b2f
 MD5 (7.2-RELEASE-amd64-disc1.iso) = 3b281f75acef6f6a16d5e405ed003f36
 MD5 (7.2-RELEASE-amd64-disc2.iso) = e7d2497054a15906d0e4945d8c91e47f
 MD5 (7.2-RELEASE-amd64-disc3.iso) = ba4369f5d39fae3bd11ad537f4c52783
 MD5 (7.2-RELEASE-amd64-docs.iso) = 97db6efd21c531b2a325224d9897f287
 MD5 (7.2-RELEASE-amd64-dvd1.iso) = b3ac4c645aec087480ddefa827c8553c
 MD5 (7.2-RELEASE-amd64-livefs.iso) = 93c4ad283b66f6cb9d1eb1dcace92ce6
MD5 (7.2-RELEASE-i386-bootonly.iso) = aceb5cdbb14780c97924cb4a645d3258
 MD5 (7.2-RELEASE-i386-disc1.iso) = b2415294a55ab3e5c1931f4e0fe67e4e
 MD5 (7.2-RELEASE-i386-disc2.iso) = b4fd35adea684e6da3a0515b535ece39
 MD5 (7.2-RELEASE-i386-disc3.iso) = da2958a3eb6a3ce6237ed7194bdfdd13
 MD5 (7.2-RELEASE-i386-docs.iso) = fee5de7fbd8c21e5a7523a1c197c32ae
 MD5 (7.2-RELEASE-i386-dvd1.iso) = 1d129a999a1db6aefebc57c2f82cacc0
 MD5 (7.2-RELEASE-i386-livefs.iso) = decdd91479b8059e70eed6d8e4eb5c06
MD5 (7.2-RELEASE-ia64-bootonly.iso) = d0a84e0014b042f5369e1644a38c380c
 MD5 (7.2-RELEASE-ia64-disc1.iso) = 58eb2db0a7656a05cb6193aad68e150b
 MD5 (7.2-RELEASE-ia64-disc2.iso) = bf27c66277e9bea85d9656af154e94ca
 MD5 (7.2-RELEASE-ia64-disc3.iso) = 1ab4e7e08fa41b7b4e2370a8bde6dcfb
 MD5 (7.2-RELEASE-ia64-docs.iso) = 01de8413d2829c5b1cb6d495b51cf3a0
 MD5 (7.2-RELEASE-ia64-livefs.iso) = 02eadf879e203148610d823e7db515ba
MD5 (7.2-RELEASE-pc98-bootonly.iso) = a0eaf2126458fc88ee1ac6d82d1f1c3a
 MD5 (7.2-RELEASE-pc98-disc1.iso) = 6555c5c4a8606ee043b5a7fbb7759b32
 MD5 (7.2-RELEASE-pc98-livefs.iso) = 0a23c3c4fc94d2961be5d148003e9511
MD5 (7.2-RELEASE-powerpc-bootonly.iso) = 17ddd18ad20aa00dd5b4830e536eabad
 MD5 (7.2-RELEASE-powerpc-disc1.iso) = 015869f4f70124c0204ebd111d876142
 MD5 (7.2-RELEASE-powerpc-disc2.iso) = 2f6d5139b57e982039fb90f02cf3f508
 MD5 (7.2-RELEASE-powerpc-disc3.iso) = 0a6d3b4a5808374bb44f3f8583df38f7
 MD5 (7.2-RELEASE-powerpc-docs.iso) = bb30b266f3c0164b512b3b3317f8ab68
MD5 (7.2-RELEASE-sparc64-bootonly.iso) = e3246598de481f7c1b117c81b46acfaa
 MD5 (7.2-RELEASE-sparc64-disc1.iso) = 2e767c93f195b69ea83274a1dff4dd5c
 MD5 (7.2-RELEASE-sparc64-docs.iso) = 1b3d32f0c82c89e18b6f2a3eeca47ae5
SHA256 (7.2-RELEASE-amd64-bootonly.iso) = fb87f4c7ddf8870e8758191181ebf3730dd44534ecc3654069a66d85c56695d3
 SHA256 (7.2-RELEASE-amd64-disc1.iso) = 1ea1f6f652d7c5f5eab7ef9f8edbed50cb664b08ed761850f95f48e86cc71ef5
 SHA256 (7.2-RELEASE-amd64-disc2.iso) = 0a951c4eea8891b0d2bf3702eb933037dc6db3530b9a37e5b33d765ba9f67154
 SHA256 (7.2-RELEASE-amd64-disc3.iso) = 870eeb94b3f21d0ab603986bc6fecb6b3a4a7529f6220ba34aef6458fc43a8b4
 SHA256 (7.2-RELEASE-amd64-docs.iso) = 109b9d048b8ff58e392f002ef85f60e75b33ea72ef658edb610f9f50235508d4
 SHA256 (7.2-RELEASE-amd64-dvd1.iso) = 1e13d3b6dfa7034e86f17b9ba379fff56761ffad7e029a23a27e92e9dbde2788
 SHA256 (7.2-RELEASE-amd64-livefs.iso) = df3cc7f8795b9b260ada2facbd0d77114f0535c35b933a503ac3e56e05947e33
SHA256 (7.2-RELEASE-i386-bootonly.iso) = 6993e73ad5e012d1605c5cf085942b694ec4fa6fb4be114c7e752a012b8c3a5e
 SHA256 (7.2-RELEASE-i386-disc1.iso) = bf4d00102215b07f5a4c8acac80b9d9bd9bf8bd93ac554fe09b21302f0b41380
 SHA256 (7.2-RELEASE-i386-disc2.iso) = 573673db5acebd68dfdbca63f620b923a7e68421f1e946fb26a1381e3d7fd9f8
 SHA256 (7.2-RELEASE-i386-disc3.iso) = ec5c98c02849c181f405e63875f193e33e121cb087cec0bd2a3e10f533ffc8e7
 SHA256 (7.2-RELEASE-i386-docs.iso) = 77beb6e7a7905a2e9aba4adeb2722be5fbdb699bd44bd0a01e3780b4623d2ce9
 SHA256 (7.2-RELEASE-i386-dvd1.iso) = de395cc63cb7fa22a0bf116487c13d56aac71762787fc5581746bfb48e66f750
 SHA256 (7.2-RELEASE-i386-livefs.iso) = 4faa7b9d78d125f9b28521247e32e1f0bef3b0b0f21b654ba22c6e79ca3301ce
SHA256 (7.2-RELEASE-ia64-bootonly.iso) = 0a2f5fb514f14760b1237059d9ef381e0836fd45579c5264efc2eb49cc57fbb9
 SHA256 (7.2-RELEASE-ia64-disc1.iso) = 048850ab672ae6865225b4d3ca324753dd823d526ce93480adf15f602acd96bf
 SHA256 (7.2-RELEASE-ia64-disc2.iso) = 5fe326d21f2e7646c63a1b6fb5ae913971da99f1c660f0ffd148de19fc47fb11
 SHA256 (7.2-RELEASE-ia64-disc3.iso) = 58c0c94d12ca197593ec48cab2fc5ec619a87caa16ae5421958216773665086d
 SHA256 (7.2-RELEASE-ia64-docs.iso) = 106844d5135e56ed2232ecabe0e4dc8c78e54f7e9d43e92be0ee3f741009a2eb
 SHA256 (7.2-RELEASE-ia64-livefs.iso) = 70294d2d65e2f483af23d9a4c0d14e1af43da68c086b3e247af31e85050b1247
SHA256 (7.2-RELEASE-pc98-bootonly.iso) = 37f65bb079304353858da6f06936cf12d19cfcdd6f4127aecac91d2a23976db1
 SHA256 (7.2-RELEASE-pc98-disc1.iso) = 877845e4dcd3b617f1c23a47b62d27dbe3a5ff6d35075cb20cd038e2b749220f
 SHA256 (7.2-RELEASE-pc98-livefs.iso) = 3741eb5a178fa0b97a6f50b57dcc750ee7d9d2e1871a244740a4603b22289491
SHA256 (7.2-RELEASE-powerpc-bootonly.iso) = d933276ab67b6de04144ffb3a15e632f6ac6f0a82237654f9349214e0c0acb9b
 SHA256 (7.2-RELEASE-powerpc-disc1.iso) = b366319ce4cfdbff2ef394cca6f460159dd1e4949927da82904ff5c9baa3f4b8
 SHA256 (7.2-RELEASE-powerpc-disc2.iso) = 40e4d5e94c543018fd692efe7150bcca482f1a0a3ddc50330bbbd5a320d90d36
 SHA256 (7.2-RELEASE-powerpc-disc3.iso) = fc5ed9a503447c68a9e8392b60c4c35650208c42da982c9c6206e349ad327888
 SHA256 (7.2-RELEASE-powerpc-docs.iso) = 58e4f348b057608515bca359a713877964fddf638bca921d09000aada899477b
SHA256 (7.2-RELEASE-sparc64-bootonly.iso) = 98aa7492c195df441b4e4699984fd8f38af1db03e7e92cc8d1530089a4d50e11
 SHA256 (7.2-RELEASE-sparc64-disc1.iso) = ba7fa45c21d7ca43bacb78fe46c18ef15f73e480e7fe3e6c8ba8c575efe25888
 SHA256 (7.2-RELEASE-sparc64-docs.iso) = b67483a4e198e2aeb99bacf9cc826f36a3d9304482fb49c34d05590661d6da76

diff --git a/website/content/en/releases/7.2R/relnotes.html b/website/content/en/releases/7.2R/relnotes.html index 832a2bae98..c698e46391 100644 --- a/website/content/en/releases/7.2R/relnotes.html +++ b/website/content/en/releases/7.2R/relnotes.html @@ -1,388 +1,388 @@ FreeBSD 7.2-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.2-RELEASE Release Notes

Release Highlights

The highlights in the 7.2-RELEASE are the following:

  • [amd64, i386] The FreeBSD virtual memory subsystem now supports fully transparent use of superpages for application memory; application memory pages are dynamically promoted to or demoted from superpages without any modification to application code. This change offers the benefit of large page sizes such as improved virtual memory efficiency and reduced TLB (translation lookaside buffer) misses without downsides like application changes and virtual memory inflexibility. This is disabled by default and can be enabled by setting a loader tunable vm.pmap.pg_ps_enabled to 1.

  • [amd64] The FreeBSD kernel virtual address space has been increased to 6GB. This allows subsystems to use larger virtual memory space than before. For example, zfs(8) adaptive replacement cache (ARC) requires large kernel memory space to cache file system data, so it benefits from the increased address space. Note that the ceiling on the kernel map size is now 60% of the size rather than an absolute quantity.

  • [sparc64] The FreeBSD now supports Ultra SPARC III (Cheetah) processor family.

  • [i386] The boot(8) BTX loader has been improved. This fixes several boot issues on recent machines reported for 7.1-RELEASE and before.

  • A bug in the ciss(4) driver which caused low “max device openings” count and led to poor performance has been fixed.

  • The sdhci(4) driver has been added. This supports PCI devices with class 8 and subclass 5 according to the SD Host Controller Specification.

  • Various network interface drivers have been improved, including ae(4), ath_hal(4), axe(4), bce(4), cxgb(4), fxp(4), igb(4), jme(4), msk(4), mxge(4), nfe(4), re(4), rl(4), sis(4), and txp(4).

  • The btpand(8) daemon from NetBSD has been added. This daemon provides support for Bluetooth Network Access Point (NAP), Group Ad-hoc Network (GN) and Personal Area Network User (PANU) profiles.

  • The jail(8) subsystem has been updated. Changes include:

    • Multiple addresses of both IPv4 and IPv6 per jail has been supported. It is even possible to have jails without an IP address at all, which basically gives one a chrooted environment with restricted process view and no networking.

    • SCTP (sctp(4)) with IPv6 in jails has been implemented.

    • Specific CPU binding by using cpuset(1) has been implemented. Note that the current implementation allows the superuser inside of the jail to change the CPU bindings specified. This behavior will be fixed in the next release.

    • A jail(8) can start with a specific route FIB now.

    • A show jails subcommand in ddb(8) has been added.

    • Compatibility support which permits 32-bit jail binaries to be used on 64-bit systems to manage jails has been added.

    • Note that both version numbers of jail and prison in the jail(8) have been updated for the new features.

  • The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.22 to 2.26.

  • The supported version of the KDE desktop environment has been updated from 3.5.10 (x11/kde3) to 4.2.2 (x11/kde4).

For more details, please see the Detailed Release Notes.

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


diff --git a/website/content/en/releases/7.2R/schedule.html b/website/content/en/releases/7.2R/schedule.html index eea38a7d4a..5022046a5c 100644 --- a/website/content/en/releases/7.2R/schedule.html +++ b/website/content/en/releases/7.2R/schedule.html @@ -1,440 +1,440 @@ FreeBSD 7.2 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.2 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- - + + - - + + - - + + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + +
Action Expected Actual Description
Reminder announcement16 March 200917 March 200916 March 200917 March 2009 Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.2 release.
Announce the Ports Freeze3 April 20093 April 20093 April 20093 April 2009 Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins23 March 200923 March 200923 March 200923 March 2009 After this date, all commits to RELENG_7 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.
Announce doc/ tree slush --3 April 20093 April 2009 Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen13 April 200913 April 200913 April 200913 April 2009 Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush10 April 200910 April 200910 April 200910 April 2009 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.17 April 200917 April 200917 April 200917 April 2009 Version number bumps for doc/ subtree. RELEASE_7_2_0 tag for doc/. doc/ slush ends at this time.
BETA1 builds30 March 200931 March 200930 March 200931 March 2009 Begin BETA1 builds.
RELENG_7_2 branch10 April 200915 April 200910 April 200915 April 2009 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds13 April 200915 April 200913 April 200915 April 2009 Begin RC1 builds.
Ports tree tagged20 April 200921 April 200920 April 200921 April 2009 RELEASE_7_2_0 tag for ports/.
Ports tree unfrozen20 April 200921 April 200920 April 200921 April 2009 After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.2-RELEASE.
Final package build starts20 April 200921 April 200920 April 200921 April 2009 The ports cluster and pointyhat build final packages.
RC2 builds20 April 200923 April 200920 April 200923 April 2009 Begin RC2 builds.
RELEASE builds1 May 20091 May 20091 May 20091 May 2009 Begin RELEASE builds.
Announcement4 May 20094 May 20094 May 20094 May 2009 Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD -- RELENG_7_2 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information


diff --git a/website/content/en/releases/7.3R/announce.html b/website/content/en/releases/7.3R/announce.html index 4612357f7d..2efeaf5c21 100644 --- a/website/content/en/releases/7.3R/announce.html +++ b/website/content/en/releases/7.3R/announce.html @@ -1,618 +1,618 @@ FreeBSD 7.3-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.3-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.3-RELEASE. This is the fourth release from the 7-STABLE branch which improves on the functionality of FreeBSD 7.2 and introduces a few new features. There will be one more release from this branch to allow future improvements to be made available in the 7-STABLE branch but at this point most developers are focused on 8-STABLE.

Some of the highlights:

  • ZFS updated to version 13

  • new boot loader gptzfsboot supports GPT and ZFS

  • hwpmc(4) enhancements including support for Core2/i7 processor and pmcannotate(8)

  • new mfiutil and mptutil tools for widely used RAID controllers

  • NULL pointer vulnerability mitigation

  • bind updated to 9.4-ESV

  • Gnome updated to 2.28.2

  • KDE updated to 4.3.5

  • Perl updated to 5.10

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

For more information about FreeBSD release engineering activities please see:

Availability

FreeBSD 7.3-RELEASE is now available for the amd64, i386, pc98, and sparc64 architectures.

FreeBSD 7.3 can be installed from bootable ISO images or over the network. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the xorg packages for CDROM-sized media. There are no other packages on this image but there are more packages (mostly Gnome and KDE) on the disc2 and disc3 images. If you choose to install packages post-install you should just need disc1, you only need disc2/disc3 if you want to install Gnome or KDE during install.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

FreeBSD 7.3-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 7.3-based products is:

BitTorrent

7.3-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_7_3.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE, 7.3-BETA1, or 7.3-RC[12] can upgrade as follows:

# freebsd-update upgrade -r 7.3-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install
 # shutdown -r now

Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.3, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x.

Support

The FreeBSD Security Team currently plans to support FreeBSD 7.3 until March 31st 2012. Users of FreeBSD 7.2 are strongly encouraged to upgrade to either FreeBSD 7.3 or FreeBSD 8.0 before the FreeBSD 7.2 End of Life on June 30th 2010. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.3 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, iXsystems, and Sentex Communications.

The release engineering team for 7.3-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-7.3-RELEASE-amd64-bootonly.iso) = 759246c235869ee6d89e84910d1bab63
 MD5 (FreeBSD-7.3-RELEASE-amd64-disc1.iso) = 7c5049d15a95d9e0dd5eca013d1086b8
 MD5 (FreeBSD-7.3-RELEASE-amd64-disc2.iso) = 4c829f2d3b2c88d857fe600362aa4ea2
 MD5 (FreeBSD-7.3-RELEASE-amd64-disc3.iso) = 29b50df4507a0bdf0aea21324889205c
 MD5 (FreeBSD-7.3-RELEASE-amd64-docs.iso) = 3433f7ab2e204369b0965a2d857e5f97
 MD5 (FreeBSD-7.3-RELEASE-amd64-dvd1.iso) = 7b9c2e7766c5e7684d6b305cb05be7f8
 MD5 (FreeBSD-7.3-RELEASE-amd64-livefs.iso) = 73552eb142365c497ecc51bf5bcef131
MD5 (FreeBSD-7.3-RELEASE-i386-bootonly.iso) = 557e05b367cc84d672878e19a7a28a04
 MD5 (FreeBSD-7.3-RELEASE-i386-disc1.iso) = 310d3e4d6fd03608f6fbbbecc4f13d6d
 MD5 (FreeBSD-7.3-RELEASE-i386-disc2.iso) = ade3d0b064a934da1cbd0bcc4bde8159
 MD5 (FreeBSD-7.3-RELEASE-i386-disc3.iso) = b57b9bfe9c1856a54fa719d175987c57
 MD5 (FreeBSD-7.3-RELEASE-i386-docs.iso) = c496b49fb7c6e9acf084eb4148b6b942
 MD5 (FreeBSD-7.3-RELEASE-i386-dvd1.iso) = 8b940feb3174dab1703297d4b59ddaa4
 MD5 (FreeBSD-7.3-RELEASE-i386-livefs.iso) = 553d28df18560a2916bc9733e625e8fb
MD5 (FreeBSD-7.3-RELEASE-pc98-bootonly.iso) = 639defb907eb57c4902592092fa77869
 MD5 (FreeBSD-7.3-RELEASE-pc98-disc1.iso) = cde68c0b13b819528c157e493d74568b
 MD5 (FreeBSD-7.3-RELEASE-pc98-livefs.iso) = 504a42bae0b1948fbf45cb1e1ffda4d3
MD5 (FreeBSD-7.3-RELEASE-sparc64-bootonly.iso) = 719acf982a7994edc9922c28abb4ef49
 MD5 (FreeBSD-7.3-RELEASE-sparc64-disc1.iso) = 6af2258863aa30c1a8f0bb53f785a02c
 MD5 (FreeBSD-7.3-RELEASE-sparc64-disc2.iso) = f3040f02b198b695a36e31f72b23b0ee
 MD5 (FreeBSD-7.3-RELEASE-sparc64-disc3.iso) = 3191f0c8521a101ca510f80e4c0ba16a
 MD5 (FreeBSD-7.3-RELEASE-sparc64-docs.iso) = 9306d29be84e9677906ce971b370d3cc
SHA256 (FreeBSD-7.3-RELEASE-amd64-bootonly.iso) = 5a59fe1eb3012c42f77432141a62cc2e44e962c0e10b7b140cae5e2a4007e2a6
 SHA256 (FreeBSD-7.3-RELEASE-amd64-disc1.iso) = 7f5970e095774c0cdf802e9a15b4419d0166fa7641c2b65f1a1431429105b98b
 SHA256 (FreeBSD-7.3-RELEASE-amd64-disc2.iso) = 4b281e76e39fc573bfd07391c2ab3d788f2de3c7b48243b16d9159fc027a3a99
 SHA256 (FreeBSD-7.3-RELEASE-amd64-disc3.iso) = ed78f617800056c14cad15856f720f493742cbd5fbe454955579cb29cb778ef7
 SHA256 (FreeBSD-7.3-RELEASE-amd64-docs.iso) = b2224360926499df2bb535d202bddb790371434bec3abdc135afc35836bbe5b8
 SHA256 (FreeBSD-7.3-RELEASE-amd64-dvd1.iso) = 83ae9ca4e62713a5b0b76a208e898d404508f795e617c8292ed16ec0633aa3b8
 SHA256 (FreeBSD-7.3-RELEASE-amd64-livefs.iso) = cda760fffbde26e3908edd21286e349d31f49f53c2572a7fde739c908456534b
SHA256 (FreeBSD-7.3-RELEASE-i386-bootonly.iso) = 29066f9f3557a0b599b88e19e8cdd3248dd580dc627d9fc8aeee7c11317d5433
 SHA256 (FreeBSD-7.3-RELEASE-i386-disc1.iso) = e1623209b45df700e624ed37d8526b298fddc48af14e40fbe8a62c0b3801819b
 SHA256 (FreeBSD-7.3-RELEASE-i386-disc2.iso) = 0413cd6c64d2278044bca5a7c37b848f8ba16cc8429d358c12ba58ac02acbf54
 SHA256 (FreeBSD-7.3-RELEASE-i386-disc3.iso) = f621be0a0ba5225f528584a6b85d1936b2a291dcd849b2c7da6fd09d703f11c9
 SHA256 (FreeBSD-7.3-RELEASE-i386-docs.iso) = 107c642abb44d9ffde43f9da80564010c225fa7da37424a499a771a4a5d0f602
 SHA256 (FreeBSD-7.3-RELEASE-i386-dvd1.iso) = f2cb0b5cd01124a212819e7de87e2fc463ded07ab6c150f8b9c38fc7810f8194
 SHA256 (FreeBSD-7.3-RELEASE-i386-livefs.iso) = 22cf0423766057740fcdeff8fca72b602a3d9b0e4b037b704320f65cdea11bd0
SHA256 (FreeBSD-7.3-RELEASE-pc98-bootonly.iso) = 3bfd7b24ef6e7563df5878e1eca9223aab0e02eec89690730efb3a9bc7cee895
 SHA256 (FreeBSD-7.3-RELEASE-pc98-disc1.iso) = 5fde4d15c9144ac64ea354546c24079f5abc0976ed7a868edab4990657ece776
 SHA256 (FreeBSD-7.3-RELEASE-pc98-livefs.iso) = e564864d9568430574dddb97ae3c5741b2b981926b626dfc003620fb95ce9d1a
SHA256 (FreeBSD-7.3-RELEASE-sparc64-bootonly.iso) = f99a648aa04df5b9d9d8f66055f8a2789759a7305c03dc7b890abfec1869a341
 SHA256 (FreeBSD-7.3-RELEASE-sparc64-disc1.iso) = 5d659bd0c8e22244bc987a92efd34d3bb725e489a491635abd42888b89e802e8
 SHA256 (FreeBSD-7.3-RELEASE-sparc64-disc2.iso) = 0583bc6eda0e6e86bcd901773de759e55c34cadb17e5fcd00e428afe36fcce1e
 SHA256 (FreeBSD-7.3-RELEASE-sparc64-disc3.iso) = 987aad567c165094781af8d808c0ba5fc4f1ef12efcf6cae66d3cf5d6425ffc6
 SHA256 (FreeBSD-7.3-RELEASE-sparc64-docs.iso) = 8d5440c371637d5b5510a69ce0dec2461c045df7c9ae6e3fd74bc1f0998ceb35

diff --git a/website/content/en/releases/7.3R/relnotes.html b/website/content/en/releases/7.3R/relnotes.html index 0854af56a6..eb5616c7e8 100644 --- a/website/content/en/releases/7.3R/relnotes.html +++ b/website/content/en/releases/7.3R/relnotes.html @@ -1,358 +1,358 @@ FreeBSD 7.3-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.3-RELEASE Release Notes

Release Highlights

The highlights in the 7.3-RELEASE are the following:

  • The ZFS file system has been updated to version 13. The changes include ZFS operations by a regular user, L2ARC, ZFS Intent Log on separated disks (slog), sparse volumes, and so on.

  • A lock handling error has been fixed in interaction between malloc(3) implementation and threading library.

  • A deadlock in the sched_ule(4) scheduler has been fixed.

  • A new sysctl variable security.bsd.map_at_zero has been added and set to 1 (allow) by default. This controls whether FreeBSD allows to map an object at the address 0, which is part of the user-controlled portion of the virtual address space. Disabling this has some effect on preventing an attack which injects malicious code into that location and triggers a NULL pointer dereference in the kernel.

  • A new boot loader gptzfsboot, which supports GPT and ZFS has been added. zfsloader, the final boot loader similar to loader(8) which supports ZFS has been added.

  • [amd64, i386] CPU cache flushing has been optimized when changing caching attributes of pages by doing nothing for CPUs that support self-snooping and using CLFLUSH instead of a full cache invalidate when possible.

  • The amdsbwd(4) driver for AMD SB600/SB7xx watchdog timer has been added.

  • [amd64, i386] The hwpmc(4) driver for Hardware Performance Monitoring Counter support has been added.

  • DRM now supports Radeon HD 4200 (RS880), 4770 (RV740), and R6/7xx 3D, and Intel G41 chips.

  • The alc(4) driver for Atheros AR8131/AR8132 PCIe Ethernet controller has been added.

  • [sparc64] The cas(4) driver has been added to provide support for Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn Gigabit Ethernet devices.

  • A userland utility mfiutil(8) for the mfi(4) devices has been added.

  • A userland utility mptutil(8) for the mpt(4) devices has been added.

  • The yp(8) utilities now support shadow.byname and shadow.byuid maps. These requires privileged port access.

  • The service(8) command as an easy interface for the rc.d scripts has been added.

  • ISC BIND has been updated to version 9.4-ESV.

  • sendmail has been updated from version 8.14.3 to version 8.14.4.

  • The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.28.2.

  • The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.3.5.

  • FreeBSD release ISO images now have “FreeBSD-” at the beginning of the filenames.

For more details, please see the Detailed Release Notes.

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


diff --git a/website/content/en/releases/7.3R/schedule.html b/website/content/en/releases/7.3R/schedule.html index 8df0687dc8..fb2c3959c7 100644 --- a/website/content/en/releases/7.3R/schedule.html +++ b/website/content/en/releases/7.3R/schedule.html @@ -1,399 +1,399 @@ FreeBSD 7.3 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.3 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - - + + - - + + - + - - + + - - + + - - + + - + - - + + - - + + - + - + - - + +
Action Expected Actual Description
Release schedule announcement —23 January 201023 January 2010 Release Engineers send announcement email to freebsd-stable@ with a rough schedule for the FreeBSD 7.3 release.
Code freeze begins22 January 201023 January 201022 January 201023 January 2010 After this date, all commits to RELENG_7 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.
BETA1 builds25 January 201027 January 201025 January 201027 January 2010 Begin BETA1 builds.
Announce doc/ tree slush —31 January 201031 January 2010 Notification of the impending doc/ tree slush should be sent to doc@.
doc/ tree slush5 February 20105 February 20105 February 20105 February 2010 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.10 February 201010 February 201010 February 201010 February 2010 Version number bumps for doc/ subtree. RELEASE_7_3_0 tag for doc/. doc/ slush ends at this time.
Ports tree feature freeze8 February 201015 February 20108 February 201015 February 2010 Only feature safe commits will be permitted to the ports/ tree during the freeze.
RELENG_7_3 branch —10 February 201010 February 2010 The new release branch is created. Update newvers.sh and release.ent on various branches involved.
RC1 builds8 February 201010 February 20108 February 201010 February 2010 Begin RC1 builds.
RC2 builds22 February 20101 March 201022 February 20101 March 2010 Begin RC2 builds.
RELENG_7_3_0_RELEASE tagged —21 March 201021 March 2010 The release tag for 7.3-RELEASE is set on RELENG_7_3 branch.
RELEASE builds —21 March 201021 March 2010 Begin RELEASE builds.
Announcement1 March 2010
23 March 2010		23 March 20101 March 2010
23 March 2010		23 March 2010 Announcement sent out after a majority of the mirrors have received the bits.

Additional Information


diff --git a/website/content/en/releases/7.4R/announce.html b/website/content/en/releases/7.4R/announce.html index d0785ffb0b..35b0f5fbe4 100644 --- a/website/content/en/releases/7.4R/announce.html +++ b/website/content/en/releases/7.4R/announce.html @@ -1,627 +1,627 @@ FreeBSD 7.4-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.4-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 7.4-RELEASE. This will be the last release from the 7-STABLE branch.

Some of the highlights:

  • Gnome updated to 2.32.1

  • KDE updated to 4.5.5

  • Many misc. improvements and bugfixes

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

For more information about FreeBSD release engineering activities please see:

Availability

FreeBSD 7.4-RELEASE is now available for the amd64, i386, ia64, pc98, and sparc64 architectures.

FreeBSD 7.4 can be installed from bootable ISO images or over the network. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the xorg packages for CDROM-sized media. There are no other packages on this image but there are more packages (mostly Gnome and KDE) on the disc2 and disc3 images. If you choose to install packages post-install you should just need disc1, you only need disc2/disc3 if you want to install Gnome or KDE during install.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

FreeBSD 7.4-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 7.4-based products is:

BitTorrent

7.4-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_7_4 for CVS. For SVN use releng/7.4.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[0123]-RELEASE, 7.4-BETA1, or 7.4-RC[123] can upgrade as follows:

# freebsd-update upgrade -r 7.4-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install
 # shutdown -r now

Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.4, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x.

Support

The FreeBSD Security Team currently plans to support FreeBSD 7.4 until February 28th 2013. Users of FreeBSD 7.3 are strongly encouraged to upgrade to either FreeBSD 7.4 or FreeBSD 8.X before the FreeBSD 7.3 End of Life on March 31st 2012. Also note support for FreeBSD 7.1 ends February 28th, 2011. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 7.4 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.

The release engineering team for 7.4-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Josh Paetzel <jpaetzel@FreeBSD.org>Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-7.4-RELEASE-amd64-bootonly.iso) = d63b110b10e99520258609f3d28bf0b0
 MD5 (FreeBSD-7.4-RELEASE-amd64-disc1.iso) = ea00c6902424af499360e19339656601
 MD5 (FreeBSD-7.4-RELEASE-amd64-disc2.iso) = 023fe1aec66972f43cda98b97a3c9117
 MD5 (FreeBSD-7.4-RELEASE-amd64-disc3.iso) = 0d7017e106a4ea51cbbc1d7ec5dcd6f8
 MD5 (FreeBSD-7.4-RELEASE-amd64-docs.iso) = bafb94c26d48ed5d2c4f8923b0003b43
 MD5 (FreeBSD-7.4-RELEASE-amd64-dvd1.iso) = fe454e503b9aeab68cff5d8f56ffa73c
 MD5 (FreeBSD-7.4-RELEASE-amd64-livefs.iso) = b8da626af31016c3b860fd093b562ecf
 MD5 (FreeBSD-7.4-RELEASE-amd64-dvd1.iso.gz) = e195b51e86f207d14d12bff9c5de81c6
MD5 (FreeBSD-7.4-RELEASE-i386-bootonly.iso) = 30165c3342ef3508b535313f32a2d0b4
 MD5 (FreeBSD-7.4-RELEASE-i386-disc1.iso) = 746d6908bdac5f96ba3002ae1627aa4c
 MD5 (FreeBSD-7.4-RELEASE-i386-disc2.iso) = c0dbb71dec89341635714d861cca66cf
 MD5 (FreeBSD-7.4-RELEASE-i386-disc3.iso) = 9ad3cfeae844d6db7c385fd743027cb7
 MD5 (FreeBSD-7.4-RELEASE-i386-docs.iso) = a2709e830ee3cc2d12d735750e72ad79
 MD5 (FreeBSD-7.4-RELEASE-i386-dvd1.iso) = 105fc5e9bf7ff0d1eb3ab8f6003ae51f
 MD5 (FreeBSD-7.4-RELEASE-i386-livefs.iso) = 4bd1dea8735dba4347aaac04f7009fc1
 MD5 (FreeBSD-7.4-RELEASE-i386-dvd1.iso.gz) = f3d05347a929e988063bdd176d761734
MD5 (FreeBSD-7.4-RELEASE-pc98-bootonly.iso) = 0901c7c2b10af1f019da231ec57c1baf
 MD5 (FreeBSD-7.4-RELEASE-pc98-disc1.iso) = 90f9e2d1a95e4475cae021607d7d7a0e
 MD5 (FreeBSD-7.4-RELEASE-pc98-livefs.iso) = 2159dd1f7c991e0d2c39e481b7ed128d
MD5 (FreeBSD-7.4-RELEASE-sparc64-bootonly.iso) = 090ff3bf77bb4a8e5c8aac022f41987c
 MD5 (FreeBSD-7.4-RELEASE-sparc64-disc1.iso) = 09bf9f7d7ff62050dc3ea8addc028453
 MD5 (FreeBSD-7.4-RELEASE-sparc64-disc2.iso) = c6db8de5536af23bf5d8a63347261dae
 MD5 (FreeBSD-7.4-RELEASE-sparc64-disc3.iso) = ebcc690de2b0dcbc9d530dcd71943db3
 MD5 (FreeBSD-7.4-RELEASE-sparc64-docs.iso) = 093865a606b4c9e583b82321cb1f5dca
SHA256 (FreeBSD-7.4-RELEASE-amd64-bootonly.iso) = 71c7a0fb224a435a2d482b783af80ff478973a52aaa9e398b77903bf14d6e425
 SHA256 (FreeBSD-7.4-RELEASE-amd64-disc1.iso) = c6d560a010808929570818c6e5947ff4e488085de690dd2d8489d393cf59ddd2
 SHA256 (FreeBSD-7.4-RELEASE-amd64-disc2.iso) = 9f51f6ee4636a9c0f12116539dad2e49c610e113b44cc01790b7167db5ad9500
 SHA256 (FreeBSD-7.4-RELEASE-amd64-disc3.iso) = d80ec0f695312658d2dac7c47ae2bb16a6f68661146b9b7a80fc2a49601e2097
 SHA256 (FreeBSD-7.4-RELEASE-amd64-docs.iso) = 6bdf555fb4a5882af65fea9f418d16cebc2443d72ed9a0af406d714170bf689a
 SHA256 (FreeBSD-7.4-RELEASE-amd64-dvd1.iso) = fcb7f2b97d67b08c4a72144c2d6428442417b671e367c3960b4bd0f27d006388
 SHA256 (FreeBSD-7.4-RELEASE-amd64-livefs.iso) = 7461a584b93fffbc9ca3f363e63913d2eaed2be3c947cb5366fc2f4bc5165e50
 SHA256 (FreeBSD-7.4-RELEASE-amd64-dvd1.iso.gz) = 5b81738635a997b5cd73b92131e2dd1c492a0cd1b7cd95330d75f7a2bada9097
SHA256 (FreeBSD-7.4-RELEASE-i386-bootonly.iso) = 015cbe8fd94d7af971030ff3d9570b4e2a76941b8d9b9c9baba34451dd6e2a65
 SHA256 (FreeBSD-7.4-RELEASE-i386-disc1.iso) = 3a4437fbd10a516f365d169457f9413fe1e8cbc28792935edd83145bd4d20f9d
 SHA256 (FreeBSD-7.4-RELEASE-i386-disc2.iso) = d919293fe6e7fef5e30290f6d5814235f2c1ea8ac7080da8608d84e51da7dbca
 SHA256 (FreeBSD-7.4-RELEASE-i386-disc3.iso) = d69e755ae01bb82efc29b4aaa7f144690a5491506975548666791752662486cb
 SHA256 (FreeBSD-7.4-RELEASE-i386-docs.iso) = 743f5bd8f7e3ee065bf44821eaa026e9ac741c1e8ed1ad0ef4b93cf7d7aa5507
 SHA256 (FreeBSD-7.4-RELEASE-i386-dvd1.iso) = 2511f0f26acc184ec433a6729b54018c6582cf184ca5255cef6884dd2323cfbd
 SHA256 (FreeBSD-7.4-RELEASE-i386-livefs.iso) = b2fc72d782fc2c04afa6fa2ba76197b625436b11e77e18410c11023f68d1f2bd
 SHA256 (FreeBSD-7.4-RELEASE-i386-dvd1.iso.gz) = edfc816c589864d67b4e10500252789e44473cbd79775b8caf35cfa5ec488908
SHA256 (FreeBSD-7.4-RELEASE-pc98-bootonly.iso) = 7420b7155d9e2c479cb18d6743a37f8f778027b400ecd7ac57f113c4f10af340
 SHA256 (FreeBSD-7.4-RELEASE-pc98-disc1.iso) = 9f6ceb3fc95b7c19ff1813ce4c27624f1c168373b02b8970d316c92e396fbb8f
 SHA256 (FreeBSD-7.4-RELEASE-pc98-livefs.iso) = ecd0996a62e7486614987037c47882729ef9c2a2b8b85b39064acfde840a060a
SHA256 (FreeBSD-7.4-RELEASE-sparc64-bootonly.iso) = 0b7c2b29b99a5f39a8702717f7ae62b5dccd16457f208d954d0b99c30296332c
 SHA256 (FreeBSD-7.4-RELEASE-sparc64-disc1.iso) = 984ae17ec236bbaf0af2954fedda9054607a016c8a0e494930f37bf1c842109f
 SHA256 (FreeBSD-7.4-RELEASE-sparc64-disc2.iso) = 4ec37668a8732c77eef91f865da95d8f751784efee6fc3c7222d4a0810f557a6
 SHA256 (FreeBSD-7.4-RELEASE-sparc64-disc3.iso) = 987c44323e9c8e91adca0e5fdbf37cea46a835ff84f6d4bc13f36bd6202ad3c8
 SHA256 (FreeBSD-7.4-RELEASE-sparc64-docs.iso) = 6f21ca0637727a372234f7e57314cf532aabb78b9352c6a9de3867793318682e

diff --git a/website/content/en/releases/7.4R/schedule.html b/website/content/en/releases/7.4R/schedule.html index 5616e1d7e6..918ade1d19 100644 --- a/website/content/en/releases/7.4R/schedule.html +++ b/website/content/en/releases/7.4R/schedule.html @@ -1,381 +1,381 @@ FreeBSD 7.4 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 7.4 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - - + + - - + + - - + + - - + + - - + + - - + + - + - + - +
Action Expected Actual Description
Initial release schedule announcement -08 October 201008 October 2010 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder - Weekly Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code freeze begins28 November 201029 November 201028 November 201029 November 2010 Release Engineers announce that all further commits to the stable/7 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA103 December 201010 December 201003 December 201010 December 2010 First beta test snapshot.
releng/7.4 branch15 December 201021 December 201015 December 201021 December 2010 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
RC117 December 201026 December 201017 December 201026 December 2010 First release candidate.
RC207 January 201122 January 201107 January 201122 January 2011 Second release candidate.
RC328 January 201103 February 201128 January 201103 February 2011 Third release candidate.
RELEASE build21 January 201121 January 2011 - 7.4-RELEASE built.
RELEASE announcement24 January 201124 January 2011 - 7.4-RELEASE press release.
Turn over to the secteam31 January 201131 January 2011 - RELENG_7_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Status / TODO

http://wiki.freebsd.org/Releng/7.4TODO

Additional Information


diff --git a/website/content/en/releases/8.0R/announce.html b/website/content/en/releases/8.0R/announce.html index 41067f8d03..473a2bf577 100644 --- a/website/content/en/releases/8.0R/announce.html +++ b/website/content/en/releases/8.0R/announce.html @@ -1,686 +1,686 @@ FreeBSD 8.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.0-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.0-RELEASE. This release starts off the new 8-STABLE branch which improves on the functionality of FreeBSD 7.X and introduces many new features. Some of the highlights:

  • Xen Dom-U, VirtualBox guest and host, hierarchical jails.

  • NFSv3 GSSAPI support, experimental NFSv4 client and server.

  • 802.11s D3.03 wireless mesh networking and Virtual Access Point support.

  • ZFS is no longer in experimental status.

  • Ground-up rewrite of USB, including USB target support.

  • Continued SMP scalability improvements in many areas, especially VFS.

  • Revised network link layer subsystem.

  • Experimental MIPS architecture support.

The press release contains more information on this release.

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

For more information about FreeBSD release engineering activities please see:

Dedication

The FreeBSD Project dedicates this release to the memories of Jean-Marc Zucconi (jmz@) and John Birrell (jb@) who passed away in May and November of 2009 respectively. Jean-Marc and John were both FreeBSD committers since the mid-1990s and made extensive contributions to the operating system. They will be missed.

Availability

FreeBSD 8.0-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.

FreeBSD 8.0 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO and memory stick images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the documentation packages for CDROM-sized media. There are no other packages.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if="8".0-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.0-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.0-based products is:

BitTorrent

8.0-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_8_0.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE, 8.0-BETA[1234], or 8.0-RC[123] can upgrade as follows:

# freebsd-update upgrade -r 8.0-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See:

for more details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:

# freebsd-update install

Finally, reboot into 8.0-RELEASE:

# shutdown -r now

Support

The FreeBSD Security Team currently plans to support FreeBSD 8.0 until November 30th, 2010. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.0 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.

The release engineering team for 8.0-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
George Neville-Neil <gnn@FreeBSD.org>George Neville-Neil <gnn@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (8.0-RELEASE-amd64-bootonly.iso) = 49ccdac2e01b33c943ae89233c465ef1
 MD5 (8.0-RELEASE-amd64-disc1.iso) = eba84fbd08133cbc8c9ed67be27ee0c8
 MD5 (8.0-RELEASE-amd64-dvd1.iso) = 44c016ae8812a266f710d1845722366d
 MD5 (8.0-RELEASE-amd64-livefs.iso) = 8db54cfc97b2afa97fb13dbccace4bfa
 MD5 (8.0-RELEASE-amd64-memstick.img) = b4558fa30d13776988d86477e9631887
MD5 (8.0-RELEASE-i386-bootonly.iso) = aede8888c250b648bf799d508bc9bf9d
 MD5 (8.0-RELEASE-i386-disc1.iso) = ace0afedfa7c6e0ad12c77b6652b02ab
 MD5 (8.0-RELEASE-i386-dvd1.iso) = 5336cd827991e4d4cff6d73c4a5ca105
 MD5 (8.0-RELEASE-i386-livefs.iso) = 7f4f0ab014f853c8a99c053c2dc12641
 MD5 (8.0-RELEASE-i386-memstick.img) = 0a769af739a92f5f495d1a6842e8150b
MD5 (8.0-RELEASE-ia64-bootonly.iso) = be9dcfc2f638d5f86e21b0b344bec91b
 MD5 (8.0-RELEASE-ia64-disc1.iso) = e982547f376432d09be603b117f4da54
 MD5 (8.0-RELEASE-ia64-disc2.iso) = 5bc7616212e6977c4f054a84ef538615
 MD5 (8.0-RELEASE-ia64-disc3.iso) = cefe2fd4694f5065e55778f879dc5852
 MD5 (8.0-RELEASE-ia64-dvd1.iso) = 6b8df7fb34d5960ecf91a291926a1e6f
 MD5 (8.0-RELEASE-ia64-livefs.iso) = fe7933f2c1ddc2f4a90d5dfc48c38995
MD5 (8.0-RELEASE-pc98-bootonly.iso) = 16a29c2e31025c02997de21aac5041bb
 MD5 (8.0-RELEASE-pc98-disc1.iso) = 58e423d5a0a69a72016ebbecde265abd
 MD5 (8.0-RELEASE-pc98-livefs.iso) = 6ad13607eb305338edd9501310e6699c
MD5 (8.0-RELEASE-powerpc-bootonly.iso) = f60f73d55100f664c635c6848f00c6d8
 MD5 (8.0-RELEASE-powerpc-disc1.iso) = 1323203ffeb317f47219ed8927449980
 MD5 (8.0-RELEASE-powerpc-disc2.iso) = 5967750bf681428d59070a133b272bfd
 MD5 (8.0-RELEASE-powerpc-disc3.iso) = 43e4846683ce43fa8d6158c703767635
MD5 (8.0-RELEASE-sparc64-bootonly.iso) = 75b2f04c29e6b81058944e42055fe604
 MD5 (8.0-RELEASE-sparc64-disc1.iso) = f4aa61db620c97089641a0c63531225a
 MD5 (8.0-RELEASE-sparc64-dvd1.iso) = 85307705213a86a383e21941ee34d8e2
 MD5 (8.0-RELEASE-sparc64-livefs.iso) = 1ff6d6a449975dcc829f328b866f8128
SHA256 (8.0-RELEASE-amd64-bootonly.iso) = b0e07e8f92303b61220cba18691e86ab50d67c7df974bb62a6f1d4ffb94a1ee6
 SHA256 (8.0-RELEASE-amd64-disc1.iso) = 7d4583c20c651093b208170a7fd4ed5f38ee5af0cbe19fb742f67175a9fee10f
 SHA256 (8.0-RELEASE-amd64-dvd1.iso) = 408f7fdf3226d72564f2476fff365e4fd071bd48ddae26cd34755d808ad54b8b
 SHA256 (8.0-RELEASE-amd64-livefs.iso) = ae939a96b3b3691df84227a33de5d5f4a76d469379dca27114c3557ed443a8f3
 SHA256 (8.0-RELEASE-amd64-memstick.img) = b6cd7b0644f636f2099820ad1250940975fa3bfc19f74a0a94f69e75cc2be4c2
SHA256 (8.0-RELEASE-i386-bootonly.iso) = 12e32cea29b2f7bf873df43321a1a93d45b48a6fbb37c8e1c7f3003d5ce82e5d
 SHA256 (8.0-RELEASE-i386-disc1.iso) = d7ef47a76a20a716c006a635b476ed3515830b8442ded2702ed015f0bde32bcf
 SHA256 (8.0-RELEASE-i386-dvd1.iso) = 8b7bc67599fffc443ebc08efae8a49dd4a0fed7512cfb02b963b9a218e7c286c
 SHA256 (8.0-RELEASE-i386-livefs.iso) = feb8998bf2b9dbd6ae86f24feb9ab3c25983dc62c9f4a27f6a5314c3a4a7b59a
 SHA256 (8.0-RELEASE-i386-memstick.img) = 7e9b9cd2fd7af0fa0715b826a034b83b0f732a544a51cac7539ead5522a08806
SHA256 (8.0-RELEASE-ia64-bootonly.iso) = c594debd1cb629bf4c906da79c4a6d47b24cf4836d7690f18bc42ee9e31b6b92
 SHA256 (8.0-RELEASE-ia64-disc1.iso) = c7f4bd197ff9996ead66f4c77d077e115d18a2822e006bdfdc86a5824dcef37e
 SHA256 (8.0-RELEASE-ia64-disc2.iso) = bfcd99680bc15e1b66329a0e71eaf6b38b44d1909a3fb43ba5485238e6807dfd
 SHA256 (8.0-RELEASE-ia64-disc3.iso) = 8e8edea7117239af60c07c7e724567ea276fa32d8634f04dd30312e72b35df9a
 SHA256 (8.0-RELEASE-ia64-dvd1.iso) = bd1c9a3e8a6a287ee7bef62b3e15646d76a97dec3108177a7c606706a7ee9952
 SHA256 (8.0-RELEASE-ia64-livefs.iso) = 60a9a7738ad94765cad45dbc4f62913dd728b335d22bb4e5b065c0cae40a99db
SHA256 (8.0-RELEASE-pc98-bootonly.iso) = 7df38839c8da226bca8ef18b00f0b680074267b8333a393c3431f9b620f0ab9f
 SHA256 (8.0-RELEASE-pc98-disc1.iso) = b41fb185b1e057ee36ae6e080021f309a379c3fdf5d45a0a40461092d31e052a
 SHA256 (8.0-RELEASE-pc98-livefs.iso) = 1313ec3d5a28af8a85c181cd702b2adb91c783db7e2ad2021d311686ce5e0c2d
SHA256 (8.0-RELEASE-powerpc-bootonly.iso) = 78e18d76c24c9636b87f1946f2020a0a58fc70b80bcb925c27fa497b3c9e5bb4
 SHA256 (8.0-RELEASE-powerpc-disc1.iso) = 80f5c024b61629b77a73fd396917c68b4d0215019a5e5aaf5882cf14144764a2
 SHA256 (8.0-RELEASE-powerpc-disc2.iso) = 28c8e62c10b42fe5fb1e7a2235a6decbddbbfece0535ea42174c7ac937735068
 SHA256 (8.0-RELEASE-powerpc-disc3.iso) = e36db6e05b434a0256e977cab9e3eedb5984b2c45c400a14d7c69bbf4dda9065
SHA256 (8.0-RELEASE-sparc64-bootonly.iso) = 941b5e76a67960045040c268894b8666f5b7a8cbd2e9f98186f2618abb5bf431
 SHA256 (8.0-RELEASE-sparc64-disc1.iso) = 2d0a74cf867fa34c5a073777cf2d8e2469906425c9a54068892bd2d58ac9c3c5
 SHA256 (8.0-RELEASE-sparc64-dvd1.iso) = 482447b382fa50ffdc80e02a0cfd774e0eecf7d009e5b06864e8a4f828536876
 SHA256 (8.0-RELEASE-sparc64-livefs.iso) = 7499ca1af16de7b3d431741b1551a4b59f277fda997d57cf2615155992beaef7

diff --git a/website/content/en/releases/8.0R/pressrelease.html b/website/content/en/releases/8.0R/pressrelease.html index b67f53a3b1..500044ec46 100644 --- a/website/content/en/releases/8.0R/pressrelease.html +++ b/website/content/en/releases/8.0R/pressrelease.html @@ -1,365 +1,365 @@ FreeBSD 8.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.0-RELEASE Announcement

FreeBSD Project Announces Release of FreeBSD Version 8.0

Release includes enhanced virtualization support, NFSv4, and 802.11s D3.03 wireless mesh networking

San Jose, CA (PRWEB) November 25, 2009 -- The FreeBSD Project has announced the release of FreeBSD Version 8.0. This next major release branch of FreeBSD delivers a large number of new technologies into the hands of an ever-increasing number of users. Key release focuses include wireless networking, virtualization, and storage technology.

802.11 wireless networking has been overhauled to add Virtual Access Points (VAP) support, which allows multiple wireless networks to be hosted from a single access point. Draft 802.11 mesh networking support allows FreeBSD-based devices to dynamically link together to create a larger wireless network. Also added are TDMA extensions to 802.11, targeted at long-haul WiFi networks.

FreeBSD 8.0's network stack also offers multiprocessing optimizations: a revised link layer subsystem, per-CPU flow cache, multiqueue transmit support, and significant UDP and TCP protocol scalability improvements. Zero-copy buffer extensions to BPF improve high volume packet capture performance.

In FreeBSD 8.0, virtual machine administrators in FreeBSD's ground-breaking lightweight "Jails" can now create their own nested jails. FreeBSD now supports host and guest modes in VirtualBox, and can run as a 32-bit Xen DomU guest.

The Network File System (NFS) implementation has been enhanced with GSSAPI encryption, and also experimental NFSv4 client and server support. In addition to ZFS moving from experimental to production status, FreeBSD 8.0 introduces GPT boot support.

Other notable updates in FreeBSD Version 8.0 include:

  • Experimental MIPS support based on a contribution from Juniper Networks.
  • Countless SMP scalability improvements significantly aid performance on 16-core systems.
  • File system scalability improvements as a result of reimplemented VFS locking.
  • Improved exploit mitigation for buffer overflows and kernel NULL pointer vulnerabilities.
  • The extensible kernel security framework (MAC Framework) is now available out-of-the-box.
  • A ground-up rewrite of the USB stack improving performance, device support, and adding USB target mode.

"FreeBSD 8.0's wireless network stack is the industry leader, and makes FreeBSD the platform of choice for a future generation of networking products," said FreeBSD Core Team member Robert Watson. "Enterprise consumers will appreciate 8.0's improved virtualization, storage, and multiprocessor scalability."

About The FreeBSD Project:

FreeBSD is an advanced operating system for modern server, desktop, and embedded computer platforms. FreeBSD's code base has undergone over thirty years of continuous development, improvement, and optimization. It is developed and maintained by a large team of individuals. FreeBSD provides advanced networking, impressive security features, and world class performance and is used by some of the world's busiest web sites and most pervasive embedded networking and storage devices. The FreeBSD Project's web site is at http://www.FreeBSD.org

About The FreeBSD Foundation

The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting the FreeBSD Project. The Foundation gratefully accepts donations from individuals and businesses, using them to fund projects, which further the development of the FreeBSD operating system. In addition, the Foundation represents the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. The FreeBSD Foundation is entirely supported by donations. More information about the FreeBSD Foundation is available on the web at http://www.FreeBSDFoundation.org/.


diff --git a/website/content/en/releases/8.0R/relnotes.html b/website/content/en/releases/8.0R/relnotes.html index 76f90b9ec6..3414235f29 100644 --- a/website/content/en/releases/8.0R/relnotes.html +++ b/website/content/en/releases/8.0R/relnotes.html @@ -1,354 +1,354 @@ FreeBSD 8.0-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.0-RELEASE Release Notes

Release Highlights

The highlights in the 8.0-RELEASE are the following:

  • A new virtualization container named “vimage” has been implemented. This is a jail with a virtualized instance of the FreeBSD network stack and can be created by using jail(8) command.

  • The FreeBSD netisr framework has been reimplemented for parallel threading support. This is a kernel network dispatch interface which allows device drivers (and other packet sources) to direct packets to protocols for directly dispatched or deferred processing. The new implementation supports up to one netisr thread per CPU, and several benchmarks on SMP machines show substantial performance improvement over the previous version.

  • The FreeBSD TTY layer has been replaced with a new one which has better support for SMP and robust resource handling. A tty now has own mutex and it is expected to improve scalability when compared to the old implementation based on the Giant lock.

  • [amd64, i386] The FreeBSD Linux emulation layer has been updated to version 2.6.16 and the default Linux infrastructure port is now emulators/linux_base-f10 (Fedora 10).

  • The FreeBSD GENERIC kernel now includes Trusted BSD MAC (Mandatory Access Control) support. No MAC policy module is loaded by default.

  • The FreeBSD USB subsystem has been reimplemented to support modern devices and better SMP scalability. The new implementation includes Giant-lock-free device drivers, a Linux compatibility layer, usbconfig(8) utility, full support for split transaction and isochronous transaction, and so on.

  • The FreeBSD CAM SCSI subsystem ( cam(4)) now includes experimental support for ATA/SATA/AHCI-compliant devices.

  • The shared vnode locking for pathname lookups in the VFS(9) subsystem has been improved.

  • The ZFS file system has been updated to version 13. The changes include ZFS operations by a regular user, L2ARC, ZFS Intent Log on separated disks (slog), sparse volumes, and so on.

  • The FreeBSD NFS subsystem now supports RPCSEC_GSS authentication on both the client and server.

  • The FreeBSD NFS subsystem now includes a new, experimental implementation with support for NFSv2, NFSv3, and NFSv4.

  • The wireless network support layer (net80211) now supports multiple BSS instances on the supported network devices.

  • The FreeBSD L2 address translation table has been reimplemented to reduce lock contention on parallel processing and simplify the routing logic.

  • The IGMPv3 and SSM (Source-Specific Multicast) including IPv6 SSM and MLDv2 have been added.

  • The ipsec(4) subsystem now supports NAT-Traversal (RFC 3948).

  • The GCC stack protection (also known as ProPolice) has been enabled in the FreeBSD base system.

  • The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.26.3.

  • The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.3.1.

For more details, please see the Detailed Release Notes.

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


diff --git a/website/content/en/releases/8.0R/schedule.html b/website/content/en/releases/8.0R/schedule.html index 6ee6f6b3b0..7c558e5c01 100644 --- a/website/content/en/releases/8.0R/schedule.html +++ b/website/content/en/releases/8.0R/schedule.html @@ -1,413 +1,413 @@ FreeBSD 8.0 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.0 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-current mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - + - - + + - - + + - - + + - - + + - + - - + + - - + + - - + + - - + + - + - - + + - + - +
Action Expected Actual Description
Initial release schedule announcement -29 March 200929 March 2009 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder -5 May 20095 May 2009 Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code slush1 June 20091 June 20091 June 20091 June 2009 Release Engineers announce a slowdown in feature development for the release -- developers are requested to coordinate any non-refinement changes or late-arriving features with the release engineering team.
Code freeze begins25 June 200927 June 200925 June 200927 June 2009 Release Engineers announce that all further commits to the head (and forthcoming RELENG_8 branch) will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvmeents, etc.
BETA129 June 20096 July 200929 June 20096 July 2009 First beta test snapshot.
BETA26 July 200917 July 20096 July 200917 July 2009 Second beta test snapshot.
RELENG_8 branch -3 August 2009 - in progress3 August 2009 - in progress Subversion branch created, propagated to CVS and Perforce; future release engineering proceeds on this branch although code freeze/ slush continue for some time on head.
BETA313 July 200924 August 200913 July 200924 August 2009 Third beta test snapshot.
BETA45 September 20097 September 20095 September 20097 September 2009 Begin BETA4 builds.
RC114 September 200921 September 200914 September 200921 September 2009 First release candidate.
RC221 September 200928 October 200921 September 200928 October 2009 Second release candidate.
RC3 -12 November 200912 November 2009 Third release candidate.
RELEASE build28 September 200922 November 200928 September 200922 November 2009 8.0-RELEASE built.
RELEASE announcement TBD25 November 200925 November 2009 8.0-RELEASE press release.
Turn over to the secteam TBD01 December 200901 December 2009 RELENG_8_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Status / TODO

http://wiki.freebsd.org/8.0TODO

Additional Information


diff --git a/website/content/en/releases/8.1R/announce.html b/website/content/en/releases/8.1R/announce.html index 809426080d..f1ce81fdb1 100644 --- a/website/content/en/releases/8.1R/announce.html +++ b/website/content/en/releases/8.1R/announce.html @@ -1,657 +1,657 @@ FreeBSD 8.1-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.1-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.1-RELEASE. This is the second release from the 8-STABLE branch which improves on the functionality of FreeBSD 8.0 and introduces some new features. Some of the highlights:

  • zfsloader added

  • zpool version of ZFS subsystem updated to version 14

  • NFSv4 ACL support in UFS and ZFS; support added to cp(1), find(1), getfacl(1), mv(1), and setfacl(1) utilities

  • UltraSPARC IV/IV+, SPARC64 V support

  • SMP support in PowerPC G5

  • BIND 9.6.2-P2

  • sendmail updated to 8.14.4

  • OpenSSH updated to 5.4p1

  • GNOME 2.30.1, KDE 4.4.5

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

For more information about FreeBSD release engineering activities please see:

Availability

FreeBSD 8.1-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.

FreeBSD 8.1 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the documentation packages for CDROM-sized media. There are no other packages.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if="8".1-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.1-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.1-based products is:

BitTorrent

8.1-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_8_1 for CVS. For SVN use releng/8.1.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[0123]-RELEASE, 8.0-RELEASE, 8.1-BETA1, or 8.1-RC[12] can upgrade as follows:

# freebsd-update upgrade -r 8.1-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 7.3-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries.

After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:

# freebsd-update install

Finally, reboot into 8.1-RELEASE:

# shutdown -r now

Support

The FreeBSD Security Team has designated FreeBSD 8.1 an "Extended" support release and currently plans to support FreeBSD 8.1 until July 31, 2012. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.1 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.

The release engineering team for 8.1-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-8.1-RELEASE-amd64-bootonly.iso) = e522b6f4af801e40f52d402d937f1886
 MD5 (FreeBSD-8.1-RELEASE-amd64-disc1.iso) = 644ded0765f68984f2c2d8159e16acd1
 MD5 (FreeBSD-8.1-RELEASE-amd64-dvd1.iso) = 3dc2f3131c390f3d8312349cd945aa24
 MD5 (FreeBSD-8.1-RELEASE-amd64-livefs.iso) = 05ef3fb0e60cc0b263f2889f3a31c6c5
 MD5 (FreeBSD-8.1-RELEASE-amd64-memstick.img) = 2769c3a606d786fa3840bb2937ac75c1
MD5 (FreeBSD-8.1-RELEASE-i386-bootonly.iso) = 7266163259fe288f08e3749503c58f73
 MD5 (FreeBSD-8.1-RELEASE-i386-disc1.iso) = 4ead632b2655ca3bd5fc11f8d0c91a53
 MD5 (FreeBSD-8.1-RELEASE-i386-dvd1.iso) = 75eb10e7586de1adf793e897ae344eb1
 MD5 (FreeBSD-8.1-RELEASE-i386-livefs.iso) = 2f245b65923ff37fe5b760515072d8a9
 MD5 (FreeBSD-8.1-RELEASE-i386-memstick.img) = db63bb7c02fad1cf0d1f2f5c24530c45
MD5 (FreeBSD-8.1-RELEASE-ia64-bootonly.iso) = 86ab91535a04cef25dcbe9d8a3f28944
 MD5 (FreeBSD-8.1-RELEASE-ia64-disc1.iso) = d878a85d9fa3ed50e441222c5ffdbd3d
 MD5 (FreeBSD-8.1-RELEASE-ia64-disc2.iso) = 206a5b1f00cc640aa7267ab25a8e37e8
 MD5 (FreeBSD-8.1-RELEASE-ia64-disc3.iso) = c9f36660ad87ff71c95a3a14c4a36683
 MD5 (FreeBSD-8.1-RELEASE-ia64-dvd1.iso) = 95c32e513c84a54d6b1e741943bb34b3
 MD5 (FreeBSD-8.1-RELEASE-ia64-livefs.iso) = 76fb856ca73a6ad2b2d683cdbc46f6eb
MD5 (FreeBSD-8.1-RELEASE-pc98-bootonly.iso) = 3a8d1d854a389588a6344494ddc7f73c
 MD5 (FreeBSD-8.1-RELEASE-pc98-disc1.iso) = 647399d13fb24753071b2c1e2c21198b
 MD5 (FreeBSD-8.1-RELEASE-pc98-livefs.iso) = f7ee871bc4682e54cd365934f16dbd1a
MD5 (FreeBSD-8.1-RELEASE-powerpc-bootonly.iso) = 5a1a6ba5034fb6cc387f5ee39abd27fa
 MD5 (FreeBSD-8.1-RELEASE-powerpc-disc1.iso) = d4cebf352ddd75b8ae288444f1931cd8
 MD5 (FreeBSD-8.1-RELEASE-powerpc-disc2.iso) = 38a81b33fc22092d8ba851bd1b27ca78
 MD5 (FreeBSD-8.1-RELEASE-powerpc-disc3.iso) = dc6074506bf4d26a8ae1dd6406883891
MD5 (FreeBSD-8.1-RELEASE-sparc64-bootonly.iso) = 7b44be3d8532b76ef1546b432e2af624
 MD5 (FreeBSD-8.1-RELEASE-sparc64-disc1.iso) = 6a11b5a9bfff83e3833eefe1cac79d69
 MD5 (FreeBSD-8.1-RELEASE-sparc64-dvd1.iso) = 3432fdb346e2cc00e26a025dbd7a7799
 MD5 (FreeBSD-8.1-RELEASE-sparc64-livefs.iso) = 5b97fd1d08bb3d0699dc0a054a6a22f8
SHA256 (FreeBSD-8.1-RELEASE-amd64-bootonly.iso) = e24c270e1351d259b49a540647beaca88de3a5163371aa41e866fb0bf47ec572
 SHA256 (FreeBSD-8.1-RELEASE-amd64-disc1.iso) = 2b87563d876cfe6095d1a7fef164d0eb0d63a6a889320b4bb91f138dc29e01e1
 SHA256 (FreeBSD-8.1-RELEASE-amd64-dvd1.iso) = 5a7f23188bc20c8fbcc3a8d0eb630f2aa445c72d5bf1483c6bc83b17e590b397
 SHA256 (FreeBSD-8.1-RELEASE-amd64-livefs.iso) = 9e40d4f72c82d8ab47a110ea73a3835f908fc0d5aefdb0dd89bf52775804a6d7
 SHA256 (FreeBSD-8.1-RELEASE-amd64-memstick.img) = 44400547769fd8d3d4ab8eed09bfb1c0b8a4f4bc403bd2f848ec58963212cb37
SHA256 (FreeBSD-8.1-RELEASE-i386-bootonly.iso) = 8e0b4c877c3ae7714656d9ffacbf1b23710f71fe60255e81b902505af29e5ea9
 SHA256 (FreeBSD-8.1-RELEASE-i386-disc1.iso) = 7b80c34ad0cb49ace8def6261561ab22ab9346c58b69e79a82c148682a62bdc1
 SHA256 (FreeBSD-8.1-RELEASE-i386-dvd1.iso) = e273a66c370c519fe83711ee20b9a07165c2c3acd24dc3105efd6609ecb0b24f
 SHA256 (FreeBSD-8.1-RELEASE-i386-livefs.iso) = a446f5572cd711ee3907f17149b5cae4552ba9d4a676a29ee0d8a557304fb787
 SHA256 (FreeBSD-8.1-RELEASE-i386-memstick.img) = 549800209a67e6b6cfbe93b0cd1289ee7801a53c30ca229e82be14617b2ffa17
SHA256 (FreeBSD-8.1-RELEASE-ia64-bootonly.iso) = de4a56a9d02669285e1fdd3fbf4024a3fca427df24acd0663c840ed0d2b6e3aa
 SHA256 (FreeBSD-8.1-RELEASE-ia64-disc1.iso) = 89747ee7f04fc3949da5ccac71b2cababb3d3be65842e46f1d545e0e6f6f9f94
 SHA256 (FreeBSD-8.1-RELEASE-ia64-disc2.iso) = b3564cf59e4181ea9a7323f8f372a13a713615d444ccec90dac42d28bc46488a
 SHA256 (FreeBSD-8.1-RELEASE-ia64-disc3.iso) = 084851c14850ad98bf52e00e49e9c4db90b420c52f6abbd015d7ab478f93ca9c
 SHA256 (FreeBSD-8.1-RELEASE-ia64-dvd1.iso) = e7a8d16240b1890c24a8e46f5c03a4dec10ebc2ff585e9c2dcceb8bbfe099dc9
 SHA256 (FreeBSD-8.1-RELEASE-ia64-livefs.iso) = 84910d35b37d03c4ff593de25fe6f0a7a2a5c34ee34d66d0d7d59015d87a19ce
SHA256 (FreeBSD-8.1-RELEASE-pc98-bootonly.iso) = 25e345c38d6a606a4363110c58ad5b21ecc8c0d03d1349b13772761d5d2a99be
 SHA256 (FreeBSD-8.1-RELEASE-pc98-disc1.iso) = b7183eafec116954e5b729878eaa8b9f31af16c84651f9900dfd686f3ceae994
 SHA256 (FreeBSD-8.1-RELEASE-pc98-livefs.iso) = 436981209a3d34a522f57e73340e9a74d4e28191df743ec2b55b7051d78de04a
SHA256 (FreeBSD-8.1-RELEASE-powerpc-bootonly.iso) = 44b3b08f225b863c0e8f5dcd3d54b64ce2a664fee1893377ef504a54b8677e40
 SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc1.iso) = 0a27021d6c8bad5cd185bbd694a9dcc46eac71b12eb98180cd9d6875323a34d0
 SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc2.iso) = 8c135cccbfbf260fef62fa2722fa7bbec823aaf76447f90108a4be02a10c79a8
 SHA256 (FreeBSD-8.1-RELEASE-powerpc-disc3.iso) = de7277e1ad23c8f9a5f2bb979becfb71602ceda89eb7c0dde8838a0f87e07e20
SHA256 (FreeBSD-8.1-RELEASE-sparc64-bootonly.iso) = c33ae727ef70ff351fdd09a37afbe1beb5065a10536444af93136993943e1d8c
 SHA256 (FreeBSD-8.1-RELEASE-sparc64-disc1.iso) = 7f6b9a6bbfd01866dd0a7f305198a38cf66a2a2db5e071557ad45fc1bd77b561
 SHA256 (FreeBSD-8.1-RELEASE-sparc64-dvd1.iso) = e741cbad4d7c72a6e15bdd84c8e7fcf08767ee269b6f1ae6a036a237fef9ff23
 SHA256 (FreeBSD-8.1-RELEASE-sparc64-livefs.iso) = ef5254aad4b1376fd7b0dcc242498aac67d11a9ef32c0d9c2df256e59f370e03

diff --git a/website/content/en/releases/8.1R/relnotes.html b/website/content/en/releases/8.1R/relnotes.html index e3d43b5023..06c48ac075 100644 --- a/website/content/en/releases/8.1R/relnotes.html +++ b/website/content/en/releases/8.1R/relnotes.html @@ -1,408 +1,408 @@ FreeBSD 8.1-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.1-RELEASE Release Notes

Release Highlights

The highlights in the 8.1-RELEASE are the following:

  • [powerpc] FreeBSD now supports SMP in PowerPC G5 systems. Note that SMP support on FreeBSD/powerpc is disabled by default in GENERIC kernel.

  • [sparc64] FreeBSD now supports UltraSPARC IV, IV+, and SPARC64 V CPUs.

  • The ZFS zpool version has been updated to 14. The zfsloader has been added. This is a separate zfs(8) enabled loader. Note that a ZFS bootcode (zfsboot or gptzfsboot) need to be installed to use this new loader.

  • The bwn(4) driver for Broadcom BCM43xx chipsets has been added.

  • The run(4) driver for Ralink RT2700U/RT2800U/RT3000U USB 802.11agn devices has been added.

  • The sge(4) driver for Silicon Integrated Systems SiS190/191 Fast/Gigabit Ethernet has been added. This supports TSO and TSO over VLAN.

  • The uhso(4) driver for Option HSDPA USB devices has been added. A new uhsoctl(1) userland utility can be used to initiate and close the WAN connection.

  • The urtw(4) driver has been improved and now supports RTL8187B-based devices.

  • The ipfw(4) subsystem including dummynet(4) has been improved.

  • The pfil(9) framework for packet filtering in FreeBSD kernel now supports separate packet filtering instances like ipfw(4) for each VIMAGE jail.

  • The vlan(4) pseudo interface now supports TSO (TCP Segmentation Offloading). The capability flag is named as IFCAP_VLAN_HWTSO and it is separated from IFCAP_VLAN_HWTAGGING. The age(4), alc(4), ale(4), bce(4), bge(4), cxgb(4), jme(4), re(4), and mxge(4) driver support this feature.

  • The vlan(4) pseudo interface for IEEE 802.1Q VLAN now ignore renaming of the parent's interface name. The configured VLAN interfaces continue to work with the new name while previously the configurations were removed as the renaming happens.

  • The HAST (Highly Available STorage) framework has been added. This is a framework to allow transparently storing data on two physically separated machines connected over the TCP/IP network. HAST works in Primary-Secondary (Master-Backup, Master-Slave) configuration, which means that only one of the cluster nodes can be active at any given time. Only Primary node is able to handle I/O requests to HAST-managed devices. Currently HAST is limited to two cluster nodes in total.

  • FreeBSD cam(3) SCSI framework has been improved and a new kernel option option ATA_CAM has been added. This turns ata(4) controller drivers into cam(4) interface modules. When enabled, this option deprecates all ata(4) peripheral drivers and interfaces such as ad and acd, and allows cam(4) drivers ada, and cd and interfaces to be natively used instead. Note that this is not enabled by default in the GENERIC kernel.

  • The mvs(4) CAM ATA driver for Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA controllers has been added. This driver supports same hardware as the ata(4) driver does, but provides many additional features, such as NCQ and PMP.

  • The liblzma library for LZMA2 lossless data compression algorithm and the userland utilities xz(1), xzdec(1), lzma(1), and lzmainfo(1). has been imported.

  • The ACPI-CA has been updated to 20100304.

  • ISC BIND has been updated to version 9.6.2-P2.

  • OpenSSH has been updated from version 5.1p1 to version 5.4p1.

  • OpenSSL has been updated to version 0.9.8n.

  • sendmail has been updated to version 8.14.4.

  • The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.28.2.

  • The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.4.3.

For more details, please see the Detailed Release Notes.

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


diff --git a/website/content/en/releases/8.1R/schedule.html b/website/content/en/releases/8.1R/schedule.html index 626e21005d..35e523c6c4 100644 --- a/website/content/en/releases/8.1R/schedule.html +++ b/website/content/en/releases/8.1R/schedule.html @@ -1,374 +1,374 @@ FreeBSD 8.1 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.1 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-current mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - - + + - - + + - - + + - - + + - - + + - - + + - + - +
Action Expected Actual Description
Initial release schedule announcement -01 April 201001 April 2010 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder - Weekly Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code freeze begins24 May 201025 May 201024 May 201025 May 2010 Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA128 May 201027 May 201028 May 201027 May 2010 First beta test snapshot.
releng/8.1 branch10 June 201014 June 201010 June 201014 June 2010 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
RC111 June 201014 June 201011 June 201014 June 2010 First release candidate.
RC225 June 201026 June 201025 June 201026 June 2010 Second release candidate.
RELEASE build09 July 201017 July 201009 July 201017 July 2010 8.1-RELEASE built.
RELEASE announcement TBD23 July 201023 July 2010 8.1-RELEASE press release.
Turn over to the secteam TBD30 July 201030 July 2010 RELENG_8_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Status / TODO

http://wiki.freebsd.org/Releng/8.1TODO

Additional Information


diff --git a/website/content/en/releases/8.2R/announce.html b/website/content/en/releases/8.2R/announce.html index 7769002635..10072ac460 100644 --- a/website/content/en/releases/8.2R/announce.html +++ b/website/content/en/releases/8.2R/announce.html @@ -1,672 +1,672 @@ FreeBSD 8.2-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.2-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.2-RELEASE. This is the third release from the 8-STABLE branch which improves on the functionality of FreeBSD 8.1 and introduces some new features. Some of the highlights:

  • Xen HVM support in FreeBSD/amd64 and Xen PV support in FreeBSD/i386 improved

  • ZFS on-disk format updated to version 15

  • aesni(4) driver for Intel AESNI crypto instruction set

  • BIND and OpenSSL updates

  • Gnome updated to 2.32.1

  • KDE updated to 4.5.5

  • Many misc. improvements and bugfixes

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

For more information about FreeBSD release engineering activities please see:

Availability

FreeBSD 8.2-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.

FreeBSD 8.2 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the documentation packages for CDROM-sized media. There are no other packages.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if="FreeBSD"-8.2-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.2-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.2-based products is:

BitTorrent

8.2-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

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:

Updates from Source

The procedure for doing a source code based update is described in the FreeBSD Handbook:

The branch tag to use for updating the source is RELENG_8_2 for CVS. For SVN use releng/8.2.

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[01234]-RELEASE, 8.[01]-RELEASE, 8.2-BETA1, or 8.2-RC[123] can upgrade as follows:

# freebsd-update upgrade -r 8.2-RELEASE

During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new userland components:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 7.4-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries.

After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:

# freebsd-update install

Finally, reboot into 8.2-RELEASE:

# shutdown -r now

Support

The FreeBSD Security Team currently plans to support FreeBSD 8.2 until February 29th, 2012. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.2 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.

The release engineering team for 8.2-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Josh Paetzel <jpaetzel@FreeBSD.org>Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-8.2-RELEASE-amd64-bootonly.iso) = 2587cb3d466ed19a7dc77624540b0f72
 MD5 (FreeBSD-8.2-RELEASE-amd64-disc1.iso) = 8f4e41c9957b22413a94507f0ab36b50
 MD5 (FreeBSD-8.2-RELEASE-amd64-disc2.iso) = 833194b58ce0f1732b5611c4acbd0705
 MD5 (FreeBSD-8.2-RELEASE-amd64-disc3.iso) = d8a0eef926610db639a896142e63d515
 MD5 (FreeBSD-8.2-RELEASE-amd64-dvd1.iso) = 287242976c6593f31049ea454c1a82e9
 MD5 (FreeBSD-8.2-RELEASE-amd64-livefs.iso) = 5b9f2715b770521fff4d06fa2cd1670e
 MD5 (FreeBSD-8.2-RELEASE-amd64-memstick.img) = a080100906400182eaea808873d1d952
 MD5 (FreeBSD-8.2-RELEASE-amd64-dvd1.iso.xz) = 9ae527283ba94ef1f437115425bb5410
MD5 (FreeBSD-8.2-RELEASE-i386-bootonly.iso) = 722edaa1b47b5537a0552cdda3666769
 MD5 (FreeBSD-8.2-RELEASE-i386-disc1.iso) = ac6b2485e0e8a9e3c5f3a51803a5af32
 MD5 (FreeBSD-8.2-RELEASE-i386-disc2.iso) = 7ca69d1302a9219028faee5abeed923c
 MD5 (FreeBSD-8.2-RELEASE-i386-disc3.iso) = 849d4d61ed2a74b6eaa290e593267704
 MD5 (FreeBSD-8.2-RELEASE-i386-dvd1.iso) = c48054ce994e41de5a60b51aa8b1fed1
 MD5 (FreeBSD-8.2-RELEASE-i386-livefs.iso) = ad5ea10cbfdbdf839502ed5ef4abe4d9
 MD5 (FreeBSD-8.2-RELEASE-i386-memstick.img) = 79fbbd5155400aa3e1792267853b2c4a
 MD5 (FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz) = f5f6d71e3a5dcc53407c73306f915d9b
MD5 (FreeBSD-8.2-RELEASE-ia64-bootonly.iso) = 0d797d07deccf065c32e3e9245c3975b
 MD5 (FreeBSD-8.2-RELEASE-ia64-disc1.iso) = 655f58f0c1dd5baeb69e0df454835f73
 MD5 (FreeBSD-8.2-RELEASE-ia64-dvd1.iso) = 87f16857b6c26986543a76a57bc2462f
 MD5 (FreeBSD-8.2-RELEASE-ia64-livefs.iso) = eb5a7157d4201055678e5ae2b19e8919
MD5 (FreeBSD-8.2-RELEASE-pc98-bootonly.iso) = 09c3181da67394298f9fd0b967958993
 MD5 (FreeBSD-8.2-RELEASE-pc98-disc1.iso) = ba57179f881404a0ded74acae6db59f8
 MD5 (FreeBSD-8.2-RELEASE-pc98-livefs.iso) = 7fbc438dbbd2ddb97ce19fe25df167da
MD5 (FreeBSD-8.2-RELEASE-powerpc-bootonly.iso) = 2a26a95337693498d39a6ded219e4786
 MD5 (FreeBSD-8.2-RELEASE-powerpc-disc1.iso) = 055fa88e2f6e8442dc5d19202abbbe89
 MD5 (FreeBSD-8.2-RELEASE-powerpc-livefs.iso) = 52f57bdf6a80a58c762f3579b5acdcaf
MD5 (FreeBSD-8.2-RELEASE-sparc64-bootonly.iso) = e30c932affe6ef7fd94caa5d77850f48
 MD5 (FreeBSD-8.2-RELEASE-sparc64-disc1.iso) = 1957a06bc3dacc2d6c9c7eb7136dbb3e
 MD5 (FreeBSD-8.2-RELEASE-sparc64-disc2.iso) = 224219b31c9d1743bfe7033b6b2de60e
 MD5 (FreeBSD-8.2-RELEASE-sparc64-disc3.iso) = 3c22ed14f8f934832d0e3a881124bcaa
 MD5 (FreeBSD-8.2-RELEASE-sparc64-dvd1.iso) = 2fedb6f5fb8e3958e1e0c55e8ed04875
 MD5 (FreeBSD-8.2-RELEASE-sparc64-livefs.iso) = 7c1e8a56a7aff8e3ba21fad794c41978
SHA256 (FreeBSD-8.2-RELEASE-amd64-bootonly.iso) = 60f18defd7775efacb8f8461f321bb1f03c970bc16465530e196532ce50d8aae
 SHA256 (FreeBSD-8.2-RELEASE-amd64-disc1.iso) = 009938b49e9b989277fe93aae474b054918acaca5f5919fbabdfcb0b04cd8c60
 SHA256 (FreeBSD-8.2-RELEASE-amd64-disc2.iso) = 8bacf3839bb6bdec958c493eea7ce28f195b0ab9f4106d53beac887423b77c6c
 SHA256 (FreeBSD-8.2-RELEASE-amd64-disc3.iso) = 3aebb842a84d323017d1224203f674de1340064fe38a191dc4578a422a078ccb
 SHA256 (FreeBSD-8.2-RELEASE-amd64-dvd1.iso) = 4e2d31e7aa9ce20fd263dec0388469c0d4ae7cdf54508a466637abeef5081c91
 SHA256 (FreeBSD-8.2-RELEASE-amd64-livefs.iso) = f72ff7e9043f200651ca6dff3a4b71ec9447319c6efc419a2f6922a921bdfc68
 SHA256 (FreeBSD-8.2-RELEASE-amd64-memstick.img) = 684bccb533067a22fe8b20ef77bd897a100fe109d1189367fa085d2b0cdebcfd
 SHA256 (FreeBSD-8.2-RELEASE-amd64-dvd1.iso.xz) = 9925e5c1d9b9dd42bba3104526248a2d6fd8ad20b0700da2c95f050e7bc5613e
SHA256 (FreeBSD-8.2-RELEASE-i386-bootonly.iso) = d2945b63a095dafc38f0816e1d795d0b75648d57542eeb4c490058ec31e6f125
 SHA256 (FreeBSD-8.2-RELEASE-i386-disc1.iso) = fbfc3950674b3845a6cf0b74bd175b9ba19475b97bdc8bef23b50344bc33866c
 SHA256 (FreeBSD-8.2-RELEASE-i386-disc2.iso) = 20856ca93e9c15242b04b77fbb71de5d9f468705ea4431b22ca083704c26b8af
 SHA256 (FreeBSD-8.2-RELEASE-i386-disc3.iso) = be98218cf793ec04f2bf849a13ab9ace00be51dd928d06f7e84158cdb1880349
 SHA256 (FreeBSD-8.2-RELEASE-i386-dvd1.iso) = d5f03fef978936adf899d3b049dbf2e7122c053f99b235f53ce7585db0a16e3f
 SHA256 (FreeBSD-8.2-RELEASE-i386-livefs.iso) = 7caf4a5ea4ddc0add657e015002be9ba628bf8e1e44d37a1a407942b89f92684
 SHA256 (FreeBSD-8.2-RELEASE-i386-memstick.img) = 5b00ad9912379f0b71f7093bb82c9bcc260e6edb8cf4bf7dc68c3d7668836fe6
 SHA256 (FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz) = 1e65788cab1f5092842cdbebebfd54d81abad5b8af4064086c9a8420fcf2b1ea
SHA256 (FreeBSD-8.2-RELEASE-ia64-bootonly.iso) = 0aea181141923b6b9931940ae5061386f050366e07336b0271a0a7722c34da2f
 SHA256 (FreeBSD-8.2-RELEASE-ia64-disc1.iso) = 6bb36b59cd496f8e2df73a08de88a709f78c1da320c2e478895eba1abade80ef
 SHA256 (FreeBSD-8.2-RELEASE-ia64-dvd1.iso) = f8185a786aae30e5b5bed2f0175718795ebdaf792e31117786a8953de7c43f16
 SHA256 (FreeBSD-8.2-RELEASE-ia64-livefs.iso) = c6c5002071aa670ca18324a625fcece5b6b71581bc9dc7aed67a6bc971442bcd
SHA256 (FreeBSD-8.2-RELEASE-pc98-bootonly.iso) = 726cbad0107d1deaa26d2d6fd36ad49b4c15181d629c7fc37c32f9bfe4ab6706
 SHA256 (FreeBSD-8.2-RELEASE-pc98-disc1.iso) = 9cdcf94cd8ac9a331ae0871daa28d89d471a9f80f4c1a5f9662738bc14102f55
 SHA256 (FreeBSD-8.2-RELEASE-pc98-livefs.iso) = a1ffc9d23e686124d89890707513f890716e255690fccf55dd8f007cf6814c6e
SHA256 (FreeBSD-8.2-RELEASE-powerpc-bootonly.iso) = 171ac42483e8ab170f3bfa44f1dea82e50d4ccc5e411743990d5e1b7581fa3a7
 SHA256 (FreeBSD-8.2-RELEASE-powerpc-disc1.iso) = 0f1c74e25b81acdaea9f592abcd97dff76f7323c4a7a781f1da048b4676dbe1f
 SHA256 (FreeBSD-8.2-RELEASE-powerpc-livefs.iso) = d02f65048502ed3a37a36cc7c856f557c25534c486ff17c7644f9e0135c4f0ba
SHA256 (FreeBSD-8.2-RELEASE-sparc64-bootonly.iso) = 0a02b8895f0d8dec7668442742df0a9093cbc2634c6f3acd6dd6b93f19b4e732
 SHA256 (FreeBSD-8.2-RELEASE-sparc64-disc1.iso) = 7ccc7dd1a8cc5580757e916ef7887bc9cdb8b47c28de2d24d03f8a57437561d0
 SHA256 (FreeBSD-8.2-RELEASE-sparc64-disc2.iso) = 17eeb491fd0614168ad2cc11098de30d06c45da7cbeba08eec06c84938178294
 SHA256 (FreeBSD-8.2-RELEASE-sparc64-disc3.iso) = a4dfdad471288f2d85dfa7eca265954d3e28ada4c3d6a2e064aea4c51ddcee6e
 SHA256 (FreeBSD-8.2-RELEASE-sparc64-dvd1.iso) = 526754704252d1e2e681bf758d86edee152c16d8e454f080a20bccccbf39238f
 SHA256 (FreeBSD-8.2-RELEASE-sparc64-livefs.iso) = d590dfbabb0007fb037d14082f0d7418d7fc6e37e97e8ed402831feedc20119a

diff --git a/website/content/en/releases/8.2R/relnotes.html b/website/content/en/releases/8.2R/relnotes.html index bca75131b8..e3668f5855 100644 --- a/website/content/en/releases/8.2R/relnotes.html +++ b/website/content/en/releases/8.2R/relnotes.html @@ -1,460 +1,460 @@ FreeBSD 8.2-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.2-RELEASE Release Notes

Release Highlights

The highlights in the 8.2-RELEASE are the following:

  • [amd64] FreeBSD/amd64 now always sets the KVA space as equal to or larger than physical memory size. This change would help to prevent a “kmem_map too small” panic which often occurs when using ZFS.[r214620]

  • The FreeBSD GENERIC kernel is now compiled with KDB and KDB_TRACE options. From 8.2-RELEASE the kernel supports displaying a stack trace on panic by using stack(9) facility with no debugger backend like ddb(8). Note that this does not change the default behaviors of the GENERIC kernel on panic.[r214326]

  • The FreeBSD crypto(4) framework (opencrypto) now supports XTS-AES (XEX-TCB-CTS, or XEX-based Tweaked Code Book mode with CipherText Stealing), which is defined in IEEE Std. 1619-2007.[r214254]

  • [amd64] Xen HVM support in FreeBSD/amd64 kernel has been improved. For more details, see xen(4) manual page.[r215788]

  • FreeBSD now fully supports GPT (GUID Partition Table). Checksums of primary header and primary partition table are verified properly now.[r213994]

  • [amd64, i386] The aesni(4) driver has been added. This supports AES accelerator on Intel CPUs and accelerates AES operations for crypto(4).[r215633]

  • [amd64, i386] The aibs(4) driver has been added. This supports the hardware sensors in ASUS motherboards and replaces the acpi_aiboost(4) driver.[r210476]

  • The tpm(4) driver, which supports Trusted Platform Module has been added.[r215036]

  • The xhci(4) driver, which supports Extensible Host Controller Interface (xHCI) and USB 3.0, has been added.[r215944]

  • The FreeBSD Linux emulation subsystem now supports the video4linux API. This requires native video4linux hardware drivers such as the ones provided by multimedia/pwcbsd and multimedia/webcamd.

  • The miibus(4) has been rewritten for the generic IEEE 802.3 annex 31B full duplex flow control support. The alc(4), bge(4), bce(4), cas(4), fxp(4), gem(4), jme(4), msk(4), nfe(4), re(4), stge(4), and xl(4) drivers along with atphy(4), bmtphy(4), brgphy(4), e1000phy(4), gentbi(4), inphy(4), ip1000phy(4), jmphy(4), nsgphy(4), nsphyter(4), and rgephy(4) have been updated to support flow control via this facility.[r211379, r215881, r215890, r2105894, r216002, r216023, r216029, r216031, r216033]

  • A new netgraph(4) node ng_patch(4) has been added. This performs data modification of packets passing through. Modifications are restricted to a subset of C language operations on unsigned integers of 8, 16, 32 or 64-bit size.[r209843]

  • The FreeBSD TCP reassembly implementation has been improved. A long-standing accounting bug affecting SMP systems has been fixed and the net.inet.tcp.reass.maxqlen sysctl(8) variable has been retired in favor of a per-connection dynamic limit based on the receive socket buffer size. FreeBSD receivers now handle packet loss (particularly losses caused by queue overflows) significantly better than before which improves connection throughput.[r214865, r214866]

  • The siftr(4), Statistical Information For TCP Research (SIFTR) kernel module has been added. This is a facility that logs a range of statistics on active TCP connections to a log file. It provides the ability to make highly granular measurements of TCP connection state, aimed at system administrators, developers and researchers.[r214859]

  • The geli(8) GEOM class now uses XTS-AES mode by default.[r214405]

  • The ZFS on-disk format has been updated to version 15 and various performance improvements for the ZFS have been imported from OpenSolaris.

  • Userland support for the dtrace(1) subsystem has been added. This allows inspection of userland software itself and its correlation with the kernel, thus allowing a much better picture of what exactly is going on behind the scenes. The dtruss(1) utility has been added and libproc has been updated to support the facility.[r214983]

  • The gpart(8) utility now supports a recover subcommand for GPT partition tables.

  • The gpart(8) utility now supports GPT_ENT_ATTR_BOOTME, GPT_ENT_ATTR_BOOTONCE, and GPT_ENT_ATTR_BOOTFAILED attributes in GPT. The attribute keywords in the command line are bootme, bootonce, and bootfailed respectively.[r213994]

  • The libarchive library and tar(1) utility now support LZMA (Lempel-Ziv-Markov chain-Algorithm) compression format.[r213667]

  • The newsyslog(8) utility now supports an -S pidfile option to override the default syslogd(8) PID file.[r211699]

  • The newsyslog(8) utility now supports a special log file name <include> for processing file inclusion. Globbing in the file name and circular dependency detection are supported. For more details, see the newsyslog.conf(5) manual page.[r215622]

  • The pmcstat(8) utility now supports a file and a network socket as a top source. This allows top monitoring over TCP on a system with no local symbols, for example.[r211098]

  • The tftp(1) and tftpd(8) utilities have been improved for better interoperability and they now support RFC 1350, 2347, 2348, 2349, and 3617.[r213036, r213038]

  • A periodic script for zfs scrub has been added. For more details, see the periodic.conf(5) manual page.

  • A periodic script which can be used to find installed ports' files with mismatched checksum has been added. For more details, see the periodic.conf(5) manual page.

  • The sysinstall(8) utility now uses the following numbers for default and minimum partition sizes: 1GB for /, 4GB for /var, and 1GB for /tmp.[r211007]

  • The ACPI-CA has been updated to 20101013.

  • The ee(1) program has been updated to version 1.5.2.[r214287]

  • ISC BIND has been updated to version 9.6-ESV-R3.

  • netcat has been updated to version 4.8.

  • OpenSSL has been updated to version 0.9.8q.

  • The timezone database has been updated to the tzdata2010o release.

  • The xz has been updated from snapshot as of 12 April 2010 to 5.0.0 release

  • The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.32.1.

  • The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.5.5.

For more details, please see the Detailed Release Notes.

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


diff --git a/website/content/en/releases/8.2R/schedule.html b/website/content/en/releases/8.2R/schedule.html index a76e5c301a..4d1906d5d8 100644 --- a/website/content/en/releases/8.2R/schedule.html +++ b/website/content/en/releases/8.2R/schedule.html @@ -1,381 +1,381 @@ FreeBSD 8.2 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.2 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - - + + - - + + - - + + - - + + - - + + - - + + - + - + - +
Action Expected Actual Description
Initial release schedule announcement -08 October 201008 October 2010 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder - Weekly Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code freeze begins28 November 201029 November 201028 November 201029 November 2010 Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA103 December 201010 December 201003 December 201010 December 2010 First beta test snapshot.
releng/8.2 branch15 December 201021 December 201015 December 201021 December 2010 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
RC117 December 201026 December 201017 December 201026 December 2010 First release candidate.
RC207 January 201116 January 201107 January 201116 January 2011 Second release candidate.
RC328 January 201103 February 201128 January 201103 February 2011 Third release candidate.
RELEASE build21 January 201121 January 2011 - 8.2-RELEASE built.
RELEASE announcement24 January 201124 January 2011 - 8.2-RELEASE press release.
Turn over to the secteam31 January 201131 January 2011 - RELENG_8_2 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Status / TODO

http://wiki.freebsd.org/Releng/8.2TODO

Additional Information


diff --git a/website/content/en/releases/8.3R/announce.html b/website/content/en/releases/8.3R/announce.html index f2b809b9dd..23dfc64f8b 100644 --- a/website/content/en/releases/8.3R/announce.html +++ b/website/content/en/releases/8.3R/announce.html @@ -1,575 +1,575 @@ FreeBSD 8.3-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.3-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.3-RELEASE. This is the fourth release from the 8-STABLE branch which improves on the functionality of FreeBSD 8.2 and introduces some new features. Some of the highlights:

  • usb(4) now supports the USB packet filter

  • TCP/IP stack now supports the mod_cc(9) pluggable congestion control framework

  • graid(8) GEOM class added to support various BIOS-based software RAID controllers (replacement for ataraid(4))

  • ZFS subsystem updated to SPA version 28

  • Gnome version 2.32.1, KDE version 4.7.4

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

For more information about FreeBSD release engineering activities please see:

Availability

FreeBSD 8.3-RELEASE is now available for the amd64, i386, pc98, and sparc64 architectures.

FreeBSD 8.3 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system and the English documentation package for CDROM-sized media. There are no other packages.

livefs

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if="FreeBSD"-8.3-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.3-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.3-based products is:

BitTorrent

8.3-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

For instructions on installing FreeBSD or updating an existing machine to 8.3-RELEASE please see:

Support

The FreeBSD Security Team currently plans to support FreeBSD 8.3 until April 30, 2014. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.3 including The FreeBSD Foundation, Yahoo!, NetApp, Internet Systems Consortium, Sentex Communications, New York Internet, Juniper Networks, and iXsystems.

The release engineering team for 8.3-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Josh Paetzel <jpaetzel@FreeBSD.org>Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building, Ports Security
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-8.3-RELEASE-amd64-bootonly.iso) = b1e776a82deabaf66a91293b04107277
 MD5 (FreeBSD-8.3-RELEASE-amd64-disc1.iso) = cf4edae9692f560e9cab89c8347886f5
 MD5 (FreeBSD-8.3-RELEASE-amd64-dvd1.iso) = 70089656058e74962cbedad1a2181daa
 MD5 (FreeBSD-8.3-RELEASE-amd64-livefs.iso) = 24e1a8d3c02c230fe415408179f90dbc
 MD5 (FreeBSD-8.3-RELEASE-amd64-memstick.img) = 013612ac4e080028b5f4e2c344250850
MD5 (FreeBSD-8.3-RELEASE-i386-bootonly.iso) = 2fa59569f572abe450fce6b5efddeb04
 MD5 (FreeBSD-8.3-RELEASE-i386-disc1.iso) = 00fac17d95d27950e30b22e521c45da9
 MD5 (FreeBSD-8.3-RELEASE-i386-dvd1.iso) = 2478c6a7477492c347e80aaf61f48cc1
 MD5 (FreeBSD-8.3-RELEASE-i386-livefs.iso) = 147db14848518808deddf3c0b03694c3
 MD5 (FreeBSD-8.3-RELEASE-i386-memstick.img) = 5cbbe6f41e53eb98471c3392eb1bb768
MD5 (FreeBSD-8.3-RELEASE-pc98-bootonly.iso) = 91843c5c9dbdf1d1be23eae30b0184b8
 MD5 (FreeBSD-8.3-RELEASE-pc98-disc1.iso) = e84f3d26d72a37ae332b617e8122bec4
 MD5 (FreeBSD-8.3-RELEASE-pc98-livefs.iso) = 4a441695c30c446308d7ee55d1ead1bc
MD5 (FreeBSD-8.3-RELEASE-sparc64-bootonly.iso) = b94f5c9b07fdc1870cd284e168b557d8
 MD5 (FreeBSD-8.3-RELEASE-sparc64-disc1.iso) = 8b748240afe7a3f80cdf531f7d8a1317
 MD5 (FreeBSD-8.3-RELEASE-sparc64-dvd1.iso) = 3ea38fd60444193c3d74d2b0beba14a4
 MD5 (FreeBSD-8.3-RELEASE-sparc64-livefs.iso) = 317325d88a8605ae5a48447f92c5f919
SHA256 (FreeBSD-8.3-RELEASE-amd64-bootonly.iso) = 2af20d98b02a26ebe9a3ddeb4785f317e2024f9494ca3a177edafdc8ef138b7d
 SHA256 (FreeBSD-8.3-RELEASE-amd64-disc1.iso) = 26d4870f3a310a95e488ed14dd8e36eb52e857878f2b238b3b91e65c101eee93
 SHA256 (FreeBSD-8.3-RELEASE-amd64-dvd1.iso) = acd9127364c759c4eb38fd02634f52bffe75b845a767a20f7dbf022a1626eed7
 SHA256 (FreeBSD-8.3-RELEASE-amd64-livefs.iso) = cb3dcd38ce4e3782059ea6d550a947a69c47bf167c6ae24f1cd58c5b4132697b
 SHA256 (FreeBSD-8.3-RELEASE-amd64-memstick.img) = eb598fa93b553744bd79e6b648b87b20f9054f7c131856c09ee2f88f29ccca6d
SHA256 (FreeBSD-8.3-RELEASE-i386-bootonly.iso) = e701dee1458888bee1a399937f1ec525022a225b8b097bd820ed4338e0bf300d
 SHA256 (FreeBSD-8.3-RELEASE-i386-disc1.iso) = a83919b5104d8ec4e905693a6bd6b90b88b1c30923029146d1dab62b62a038e9
 SHA256 (FreeBSD-8.3-RELEASE-i386-dvd1.iso) = 3f3334a1e4f3d3f62ef274861764d466b44e19cc14549e6cdfdbd555808d78e2
 SHA256 (FreeBSD-8.3-RELEASE-i386-livefs.iso) = d45352262d7f9d871d25d01fab3c9a946ef4488f5fbbd104e153f04ca58d5b24
 SHA256 (FreeBSD-8.3-RELEASE-i386-memstick.img) = 56f4fc14ebe66dad5691ca63fa846e5d003efb630e5cb0181921ffb8af5a4edd
SHA256 (FreeBSD-8.3-RELEASE-pc98-bootonly.iso) = 664b06c1a68352be8833b90ee455cbc31dfea531b7dd5f648d48659da60e386d
 SHA256 (FreeBSD-8.3-RELEASE-pc98-disc1.iso) = 1a54d5cbd6e72d740f7bf6372c58fb8caa5bb49d6c56358e18fe7433103bbb4f
 SHA256 (FreeBSD-8.3-RELEASE-pc98-livefs.iso) = 5b8887aee9c80914ece956452fd5e48eb759232d56cb4fff557e7cc60daab58b
SHA256 (FreeBSD-8.3-RELEASE-sparc64-bootonly.iso) = e7ba76bbecff1b92d00caed5e644443b596f6a0fee4d717046aae73c4c5248c2
 SHA256 (FreeBSD-8.3-RELEASE-sparc64-disc1.iso) = f5d4087a0a070a05ad2cd9032fdc3a49fff2f716b7485debc25ae6757e29ca90
 SHA256 (FreeBSD-8.3-RELEASE-sparc64-dvd1.iso) = a697afe3e47250fa707b54021b5114aa0e286f088a5c89dfb6e1b2f51dd7bb67
 SHA256 (FreeBSD-8.3-RELEASE-sparc64-livefs.iso) = a5af66e2ad1042676a157c94f3d63e118761435abd26d8b5dd66e99bdc830526

diff --git a/website/content/en/releases/8.3R/relnotes.html b/website/content/en/releases/8.3R/relnotes.html index a72913fcf2..31c5b2b671 100644 --- a/website/content/en/releases/8.3R/relnotes.html +++ b/website/content/en/releases/8.3R/relnotes.html @@ -1,290 +1,290 @@ FreeBSD 8.3-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.3-RELEASE Release Notes

Important: All users are encouraged to consult the release errata before installing FreeBSD or submitting a problem report. The errata document is updated with late-breaking information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 8.3-RELEASE can be found on the FreeBSD Web site.

Other Release Documentation for 8.3-RELEASE

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


diff --git a/website/content/en/releases/8.3R/schedule.html b/website/content/en/releases/8.3R/schedule.html index b0428be992..9d5b8c3110 100644 --- a/website/content/en/releases/8.3R/schedule.html +++ b/website/content/en/releases/8.3R/schedule.html @@ -1,355 +1,355 @@ FreeBSD 8.3 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.3 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list.

Schedule

- + - - + + - - + + - + - - + + - - + + - - + + - +
Action Expected Actual Description
Initial release schedule announcement -25 January 201225 January 2012 Release Engineers send announcement email to developers with a rough schedule.
Code freeze begins15 February 201215 February 201215 February 201215 February 2012 Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA117 February 201220 February 201217 February 201220 February 2012 First beta test snapshot.
releng/8.3 branch -3 March 20123 March 2012 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
RC102 March 201206 March 201202 March 201206 March 2012 First release candidate.
RC216 March 20122 April 201216 March 20122 April 2012 Second release candidate.
RELEASE build9 April 20129 April 20129 April 20129 April 2012 8.3-RELEASE build.
RELEASE announcement -18 April 201218 April 2012 8.3-RELEASE press release.
Turn over to the secteam - - releng/8.3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Internal Status / TODO

http://wiki.freebsd.org/Releng/8.3TODO

diff --git a/website/content/en/releases/8.4R/announce.html b/website/content/en/releases/8.4R/announce.html index e03bae1be5..0a27859e5c 100644 --- a/website/content/en/releases/8.4R/announce.html +++ b/website/content/en/releases/8.4R/announce.html @@ -1,578 +1,578 @@ FreeBSD 8.4-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.4-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.4-RELEASE. This is the fifth release from the 8-STABLE branch which improves on the functionality of FreeBSD 8.3 and introduces some new features. Some of the highlights:

  • Gnome version 2.32.1, KDE version 4.10.1

  • Feature flags 5000 version of the ZFS filesystem.

  • Support for all shipping LSI storage controllers.

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

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

FreeBSD 8.4-RELEASE is now available for the amd64 and i386 architectures. Images for the pc98 architecture should be available within the next 24 hours.

FreeBSD 8.4 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

SHA256 and MD5 hashes for the release ISO and memory stick images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1:

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1:

This contains the base FreeBSD operating system and the English documentation package for CDROM-sized media. There are no other packages.

livefs:

This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.

bootonly:

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick:

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if=FreeBSD-8.4-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.4-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.4-based products is:

FTP

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

However before trying these sites 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:

For instructions on installing FreeBSD or updating an existing machine to 8.4-RELEASE please see:

Support

The FreeBSD Security Team currently plans to support FreeBSD 8.4 until June 30, 2015. For more information on the Security Team and their support of the various FreeBSD branches see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.4 including The FreeBSD Foundation, Yahoo!, NetApp, Internet Systems Consortium, Sentex Communications, New York Internet, Juniper Networks, and iXsystems.

The release engineering team for 8.4-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Josh Paetzel <jpaetzel@FreeBSD.org>Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering, 8.4-RELEASE Release Engineer
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, Release Engineering Team Lead, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Marcus von Appen <mva@FreeBSD.org>Marcus von Appen <mva@FreeBSD.org> Release Engineering
Glen Barber <gjb@FreeBSD.org>Glen Barber <gjb@FreeBSD.org> Release Engineering
Joel Dahl <joel@FreeBSD.org>Joel Dahl <joel@FreeBSD.org> Release Engineering
Steven Kreuzer <skreuzer@FreeBSD.org>Steven Kreuzer <skreuzer@FreeBSD.org> Release Engineering
Xin Li <delphij@FreeBSD.org>Xin Li <delphij@FreeBSD.org> Release Engineering
Craig Rodrigues <rodrigc@FreeBSD.org>Craig Rodrigues <rodrigc@FreeBSD.org> Release Engineering
Gleb Smirnoff <glebius@FreeBSD.org>Gleb Smirnoff <glebius@FreeBSD.org> Release Engineering
Marius Strobl <marius@FreeBSD.org>Marius Strobl <marius@FreeBSD.org> Release Engineering
Takahashi Yoshihiro <nyan@FreeBSD.org>Takahashi Yoshihiro <nyan@FreeBSD.org> PC98 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building
Dag-Erling Smørgrav <des@FreeBSD.org>Dag-Erling Smørgrav <des@FreeBSD.org> Security Officer
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer Emeritus
Simon L. B. Nielsen <simon@FreeBSD.org>Simon L. B. Nielsen <simon@FreeBSD.org> Security Officer Emeritus

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

SHA256 (FreeBSD-8.4-RELEASE-amd64-bootonly.iso) = c167d11721c2e505c062ccec4d0923fe18839d56c49e99e0646ab0de04294338
 SHA256 (FreeBSD-8.4-RELEASE-amd64-disc1.iso) = 2fb17d77d4eba34736eb98c142c56546dd73a4e7ac38895bb6c8517949282438
 SHA256 (FreeBSD-8.4-RELEASE-amd64-dvd1.iso) = 0a1acf77dee7fca7f71864e39804414ef53ad0540f2205bf0bfb954150f171f2
 SHA256 (FreeBSD-8.4-RELEASE-amd64-livefs.iso) = 6c0e004556e931da711d48bd530aaf45c056e4336b15acc00495cde128d8337a
 SHA256 (FreeBSD-8.4-RELEASE-amd64-memstick.img) = fe6686ce9f1c9afd3d1ee41d6c842d2173cfc8fed700fb76954fa2e2bef149cd
MD5 (FreeBSD-8.4-RELEASE-amd64-bootonly.iso) = 6d0cb38073c803d5f76cdbd89e0a6f24
 MD5 (FreeBSD-8.4-RELEASE-amd64-disc1.iso) = 642aba9299a30f06aca521abe0abb102
 MD5 (FreeBSD-8.4-RELEASE-amd64-dvd1.iso) = c8dfd45a0b4d6afca1aa79b7374682fe
 MD5 (FreeBSD-8.4-RELEASE-amd64-livefs.iso) = 72631f6b8a494390393db9f7c7a877bf
 MD5 (FreeBSD-8.4-RELEASE-amd64-memstick.img) = 36823c5c2613220ebc304d2508874cf6
SHA256 (FreeBSD-8.4-RELEASE-i386-bootonly.iso) = 8a92bea891f2e9bb3a4c8613c3e075c72491a5f3904219abea00eadf3c8d4258
 SHA256 (FreeBSD-8.4-RELEASE-i386-disc1.iso) = 73ecc5ba0c36e7682c4862e7351d385e2e07bc97a09f9dff326d3cc1ec690cf8
 SHA256 (FreeBSD-8.4-RELEASE-i386-dvd1.iso) = 28fcba3954f5014b67748f9870b7db9a95797a88e68956523f39dea8824fa694
 SHA256 (FreeBSD-8.4-RELEASE-i386-livefs.iso) = 7ed52fd38bc399603ff2f69013df54032f44fb431bcf1cfb4e30230cd37e323b
 SHA256 (FreeBSD-8.4-RELEASE-i386-memstick.img) = 071d889db802fc144c977023a94aece94dbe5a9e4019e85f7449128153110031
MD5 (FreeBSD-8.4-RELEASE-i386-bootonly.iso) = aca12a59ee988cccd19e4835ef8e6291
 MD5 (FreeBSD-8.4-RELEASE-i386-disc1.iso) = 051bfda6a9521ca950548b5449c8c5ce
 MD5 (FreeBSD-8.4-RELEASE-i386-dvd1.iso) = ca3ae875d0880e6b966f8eee2b13da40
 MD5 (FreeBSD-8.4-RELEASE-i386-livefs.iso) = 13ca52edd45284fb64133ceef804f890
 MD5 (FreeBSD-8.4-RELEASE-i386-memstick.img) = 52affc47ba90c9fa8df823a8c8c046e0
SHA256 (FreeBSD-8.4-RELEASE-pc98-bootonly.iso) = f88c46c223ce26146c4b82cb636fae33ff6903641ae95969f2e1e412f4ad9005
 SHA256 (FreeBSD-8.4-RELEASE-pc98-disc1.iso) = 6b7a564bdf9ba3f9370df52b78a85fdbb8eb480c9baeb07dfbc6a0374a86db91
 SHA256 (FreeBSD-8.4-RELEASE-pc98-livefs.iso) = 3d90e8f1aea96c4922be3aef8d2fd4ab54f07f2a30d0ae46eb29673b9db61065
MD5 (FreeBSD-8.4-RELEASE-pc98-bootonly.iso) = 8303bbf3b80a90e82fcee3e9280d297a
 MD5 (FreeBSD-8.4-RELEASE-pc98-disc1.iso) = a95bd4331afa524fc57ca9606893a814
 MD5 (FreeBSD-8.4-RELEASE-pc98-livefs.iso) = af6e0c5fee2ca6cf1f5b849fe4a2abb2

diff --git a/website/content/en/releases/8.4R/errata.html b/website/content/en/releases/8.4R/errata.html index e962c966bd..c90c41ceae 100644 --- a/website/content/en/releases/8.4R/errata.html +++ b/website/content/en/releases/8.4R/errata.html @@ -1,158 +1,158 @@ FreeBSD 8.4-RELEASE Errata

FreeBSD 8.4-RELEASE Errata

The FreeBSD Project

Copyright © 2015 The FreeBSD Documentation Project

FreeBSD is a registered trademark of the FreeBSD Foundation.

Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

SPARC, SPARC64, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol.

Last modified on 2015-02-05 by gjb.
Abstract

This document lists errata items for FreeBSD 8.4-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. This information includes security advisories, as well as news relating to the software or documentation that could affect its operation or usability. An up-to-date version of this document should always be consulted before installing this version of FreeBSD.

This errata document for FreeBSD 8.4-RELEASE - will be maintained until the FreeBSD 8.4-RELEASE end of life.

Table of Contents
1. Introduction
2. Security Advisories
3. Errata Notices
4. Open Issues
5. Late-Breaking News and Corrections

1. Introduction

This errata document contains “late-breaking news” + will be maintained until the FreeBSD 8.4-RELEASE end of life.

Table of Contents
1. Introduction
2. Security Advisories
3. Errata Notices
4. Open Issues
5. Late-Breaking News and Corrections

1. Introduction

This errata document contains “late-breaking news” about FreeBSD 8.4-RELEASE Before installing this version, it is important to consult this document to learn about any post-release discoveries or problems that may already have been found and fixed.

Any version of this errata document actually distributed with the release (for example, on a CDROM distribution) will be out of date by definition, but other copies are kept updated on the Internet and should be consulted as the “current errata” for this release. These other copies of the errata are located at http://www.FreeBSD.org/releases/, plus any sites which keep up-to-date mirrors of this location.

Source and binary snapshots of FreeBSD 8.4-STABLE also contain up-to-date copies of this document (as of the time of - the snapshot).

For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

2. Security Advisories

Problems described in the following security advisories have + the snapshot).

For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

2. Security Advisories

Problems described in the following security advisories have been fixed in 8.4-RELEASE. For more information, consult the individual advisories available from - http://security.FreeBSD.org/.

AdvisoryDateTopic
FreeBSD-SA-13:07.bind26 July 2013

Denial of Service vulnerability in - named(8)

FreeBSD-SA-13:09.ip_multicast21 August 2013

Integer overflow in computing the size of + http://security.FreeBSD.org/.

AdvisoryDateTopic
FreeBSD-SA-13:07.bind26 July 2013

Denial of Service vulnerability in + named(8)

FreeBSD-SA-13:09.ip_multicast21 August 2013

Integer overflow in computing the size of a temporary buffer can result in a buffer which is too - small for the requested operation

FreeBSD-SA-13:10.sctp21 August 2013

Fix a bug that could lead to kernel memory - disclosure with SCTP state cookie

FreeBSD-SA-13:12.ifioctl10 September 2013

In IPv6 and NetATM, stop + small for the requested operation

FreeBSD-SA-13:10.sctp21 August 2013

Fix a bug that could lead to kernel memory + disclosure with SCTP state cookie

FreeBSD-SA-13:12.ifioctl10 September 2013

In IPv6 and NetATM, stop SIOCSIFADDR, SIOCSIFBRDADDR, SIOCSIFDSTADDR and SIOCSIFNETMASK at the socket layer rather than pass them on to the link layer without - validation or credential checks

FreeBSD-SA-13:13.nullfs10 September 2013

Prevent cross-mount hardlinks between different + validation or credential checks

FreeBSD-SA-13:13.nullfs10 September 2013

Prevent cross-mount hardlinks between different nullfs mounts of the same underlying - filesystem

FreeBSD-SA-14:01.bsnmpd14 January 2014

bsnmpd remote denial of service - vulnerability

FreeBSD-SA-14:02.ntpd14 January 2014

ntpd distributed reflection Denial of Service - vulnerability

FreeBSD-SA-14:04.bind14 January 2014

BIND remote denial of service - vulnerability

FreeBSD-SA-14:05.nfsserver8 April 2014

NFS deadlock vulnerability

FreeBSD-SA-14:06.openssl8 April 2014

ECDSA Cache Side-channel Attack in - OpenSSL

FreeBSD-SA-14:08.tcp30 April 2014

TCP reassembly vulnerability

FreeBSD-SA-14:11.sendmail5 June 2014

sendmail improper close-on-exec flag - handling

FreeBSD-SA-14:12.ktrace5 June 2014

ktrace memory disclosure

FreeBSD-SA-14:14.openssl5 June 2014

OpenSSL multiple vulnerabilities

FreeBSD-SA-14:16.file5 June 2014

Multiple vulnerabilities in file(1) and - libmagic(3)

FreeBSD-SA-14:17.kmem8 July 2014

kernel memory disclosure in control message and - SCTP notifications

FreeBSD-SA-14:18.openssl9 September 2014

Multiple vulnerabilities in - OpenSSL

FreeBSD-SA-14:19.tcp16 September 2014

Denial of Service in TCP packet - processing

FreeBSD-SA-14:21.routed21 October 2014

routed(8) denial of service - vulnerability

FreeBSD-SA-14:23.openssl21 October 2014

Multiple vulnerabilities in - OpenSSL

FreeBSD-SA-14:25.setlogin4 November 2014

kernel stack disclosure in setlogin(2) and - getlogin(2)

FreeBSD-SA-14:26.ftp4 November 2014

Remote command execution in - ftp(1)

FreeBSD-SA-14:28.file10 December 2014

Multiple vulnerabilities in file(1) and - libmagic(3)

FreeBSD-SA-14:29.bind10 December 2014

BIND remote denial of service - vulnerability

FreeBSD-SA-14:31.ntp23 December 2014

Multiple vulnerabilities in NTP - suite

FreeBSD-SA-15:01.ntp14 January 2015

Multiple vulnerabilities in - OpenSSL

FreeBSD-SA-15:02.kmem27 January 2015

Fix SCTP SCTP_SS_VALUE kernel memory corruption - and disclosure vulnerability

FreeBSD-SA-15:03.sctp27 January 2015

Fix SCTP stream reset - vulnerability

FreeBSD-SA-15:04.igmp25 February 2015

Integer overflow in IGMP protocol

FreeBSD-SA-15:05.igmp25 February 2015

Remote denial of service - vulnerability

FreeBSD-SA-15:06.openssl19 March 2015

Multiple vulnerabilities

FreeBSD-SA-15:07.ntp7 April 2015

Multiple vulnerabilities

FreeBSD-SA-15:09.ipv67 April 2015

Router advertisement Denial of - Service

FreeBSD-SA-15:10.openssl16 June 2015

Multiple vulnerabilities

FreeBSD-SA-15:11.bind7 July 2015

Resolver remote denial of service

FreeBSD-SA-15:13.tcp21 July 2015

resource exhaustion due to sessions stuck in - LAST_ACK state.

FreeBSD-SA-15:15.tcp28 July 2015

resource exhaustion in TCP - reassembly

FreeBSD-SA-15:16.openssh28 July 2015

Multiple vulnerabilities

FreeBSD-SA-15:17.bind28 July 2015

Remote denial of service - vulnerability

3. Errata Notices

ErrataDateTopic
FreeBSD-EN-13:01.fxp28 June 2013

Fixed a problem where dhclient(8) would - infinitely try to intialize fxp(4)

FreeBSD-EN-13:02.vtnet28 June 2013

Fixed a problem frames sent to additional MAC + filesystem

FreeBSD-SA-14:01.bsnmpd14 January 2014

bsnmpd remote denial of service + vulnerability

FreeBSD-SA-14:02.ntpd14 January 2014

ntpd distributed reflection Denial of Service + vulnerability

FreeBSD-SA-14:04.bind14 January 2014

BIND remote denial of service + vulnerability

FreeBSD-SA-14:05.nfsserver8 April 2014

NFS deadlock vulnerability

FreeBSD-SA-14:06.openssl8 April 2014

ECDSA Cache Side-channel Attack in + OpenSSL

FreeBSD-SA-14:08.tcp30 April 2014

TCP reassembly vulnerability

FreeBSD-SA-14:11.sendmail5 June 2014

sendmail improper close-on-exec flag + handling

FreeBSD-SA-14:12.ktrace5 June 2014

ktrace memory disclosure

FreeBSD-SA-14:14.openssl5 June 2014

OpenSSL multiple vulnerabilities

FreeBSD-SA-14:16.file5 June 2014

Multiple vulnerabilities in file(1) and + libmagic(3)

FreeBSD-SA-14:17.kmem8 July 2014

kernel memory disclosure in control message and + SCTP notifications

FreeBSD-SA-14:18.openssl9 September 2014

Multiple vulnerabilities in + OpenSSL

FreeBSD-SA-14:19.tcp16 September 2014

Denial of Service in TCP packet + processing

FreeBSD-SA-14:21.routed21 October 2014

routed(8) denial of service + vulnerability

FreeBSD-SA-14:23.openssl21 October 2014

Multiple vulnerabilities in + OpenSSL

FreeBSD-SA-14:25.setlogin4 November 2014

kernel stack disclosure in setlogin(2) and + getlogin(2)

FreeBSD-SA-14:26.ftp4 November 2014

Remote command execution in + ftp(1)

FreeBSD-SA-14:28.file10 December 2014

Multiple vulnerabilities in file(1) and + libmagic(3)

FreeBSD-SA-14:29.bind10 December 2014

BIND remote denial of service + vulnerability

FreeBSD-SA-14:31.ntp23 December 2014

Multiple vulnerabilities in NTP + suite

FreeBSD-SA-15:01.ntp14 January 2015

Multiple vulnerabilities in + OpenSSL

FreeBSD-SA-15:02.kmem27 January 2015

Fix SCTP SCTP_SS_VALUE kernel memory corruption + and disclosure vulnerability

FreeBSD-SA-15:03.sctp27 January 2015

Fix SCTP stream reset + vulnerability

FreeBSD-SA-15:04.igmp25 February 2015

Integer overflow in IGMP protocol

FreeBSD-SA-15:05.igmp25 February 2015

Remote denial of service + vulnerability

FreeBSD-SA-15:06.openssl19 March 2015

Multiple vulnerabilities

FreeBSD-SA-15:07.ntp7 April 2015

Multiple vulnerabilities

FreeBSD-SA-15:09.ipv67 April 2015

Router advertisement Denial of + Service

FreeBSD-SA-15:10.openssl16 June 2015

Multiple vulnerabilities

FreeBSD-SA-15:11.bind7 July 2015

Resolver remote denial of service

FreeBSD-SA-15:13.tcp21 July 2015

resource exhaustion due to sessions stuck in + LAST_ACK state.

FreeBSD-SA-15:15.tcp28 July 2015

resource exhaustion in TCP + reassembly

FreeBSD-SA-15:16.openssh28 July 2015

Multiple vulnerabilities

FreeBSD-SA-15:17.bind28 July 2015

Remote denial of service + vulnerability

3. Errata Notices

ErrataDateTopic
FreeBSD-EN-13:01.fxp28 June 2013

Fixed a problem where dhclient(8) would + infinitely try to intialize fxp(4)

FreeBSD-EN-13:02.vtnet28 June 2013

Fixed a problem frames sent to additional MAC addresses are not forwarded to the vtnet(4) - interface

FreeBSD-EN-13:04.freebsd-update26 October 2013

Multiple fixes

FreeBSD-EN-13:05.freebsd-update28 November 2013

Fix INDEX generation

FreeBSD-EN-14:01.random14 January 2014

Disable hardware RNGs by default

FreeBSD-EN-14:02.mmap14 January 2014

Fix incorrect coalescing of stack - entry

FreeBSD-EN-14:03.pkg15 May 2014

Add pkg bootstrapping, configuration and public - keys

FreeBSD-EN-14:04.kldxref15 May 2014

Improve build repeatability for - kldxref(8)

FreeBSD-EN-14:06.exec3 June 2014

Fix triple-fault when executing from a threaded - process

FreeBSD-EN-14:08.heimdal24 June 2014

Fix gss_pseudo_random() - interoperability issue

FreeBSD-EN-14:09.jail8 July 2014

Fix jail fails to start if - WITHOUT_INET/WITHOUT_INET6 is use

FreeBSD-EN-14:10.tzdata21 October 2014

Time zone data file update

FreeBSD-EN-14:12.zfs4 November 2014

Fix NFSv4 and ZFS cache consistency - issue

FreeBSD-EN-14:13.freebsd-update23 December 2014

Fix directory deletion issue

FreeBSD-EN-15:02.openssl25 February 2015

OpenSSL update

FreeBSD-EN-15:03.freebsd-update25 February 2015

freebsd-update(8) updates libraries in - suboptimal order

FreeBSD-EN-15:04.freebsd-update13 May 2015

freebsd-update(8) does not ensure the - previous upgrade has completed

FreeBSD-EN-15:06.file9 June 2015

Multiple denial of service issues

FreeBSD-EN-15:08.sendmail30 June 2015 (revised)

Sendmail TLS/DH interoperability improvement

4. Open Issues

[20130613] The vtnet(4) network interface driver + interface

FreeBSD-EN-13:04.freebsd-update26 October 2013

Multiple fixes

FreeBSD-EN-13:05.freebsd-update28 November 2013

Fix INDEX generation

FreeBSD-EN-14:01.random14 January 2014

Disable hardware RNGs by default

FreeBSD-EN-14:02.mmap14 January 2014

Fix incorrect coalescing of stack + entry

FreeBSD-EN-14:03.pkg15 May 2014

Add pkg bootstrapping, configuration and public + keys

FreeBSD-EN-14:04.kldxref15 May 2014

Improve build repeatability for + kldxref(8)

FreeBSD-EN-14:06.exec3 June 2014

Fix triple-fault when executing from a threaded + process

FreeBSD-EN-14:08.heimdal24 June 2014

Fix gss_pseudo_random() + interoperability issue

FreeBSD-EN-14:09.jail8 July 2014

Fix jail fails to start if + WITHOUT_INET/WITHOUT_INET6 is use

FreeBSD-EN-14:10.tzdata21 October 2014

Time zone data file update

FreeBSD-EN-14:12.zfs4 November 2014

Fix NFSv4 and ZFS cache consistency + issue

FreeBSD-EN-14:13.freebsd-update23 December 2014

Fix directory deletion issue

FreeBSD-EN-15:02.openssl25 February 2015

OpenSSL update

FreeBSD-EN-15:03.freebsd-update25 February 2015

freebsd-update(8) updates libraries in + suboptimal order

FreeBSD-EN-15:04.freebsd-update13 May 2015

freebsd-update(8) does not ensure the + previous upgrade has completed

FreeBSD-EN-15:06.file9 June 2015

Multiple denial of service issues

FreeBSD-EN-15:08.sendmail30 June 2015 (revised)

Sendmail TLS/DH interoperability improvement

4. Open Issues

[20130613] The vtnet(4) network interface driver displays the following message upon configuration when using QEMU 1.4.1 and later:

vtnet0: error setting host MAC filter table

This message is harmless when the interface has only one MAC address. The patch for this issue is filed to a PR kern/178955.

[20130609] There is incompatibility in jail(8) configuration because the jail(8) utility and rc.d/jail script has been changed. More specifically, the following sysctl(8) variables cannot be used to set the default parameters for jails:

security.jail.mount_zfs_allowed
 security.jail.mount_procfs_allowed
 security.jail.mount_nullfs_allowed
 security.jail.mount_devfs_allowed
 security.jail.mount_allowed
 security.jail.chflags_allowed
 security.jail.allow_raw_sockets
 security.jail.sysvipc_allowed
 security.jail.socket_unixiproute_only
 security.jail.set_hostname_allowed

These could be set by manually using sysctl(8) utility, the sysctl.conf(5) file, or for some of them the following variables in rc.conf(5):

jail_set_hostname_allow="yes"
 jail_socket_unixiproute_only="yes"
 jail_sysvipc_allow="yes"

These parameters must now be specified in jail_parameters (or jail_jailname_parameters for per-jail configuration) in rc.conf(5). For example:

jail_parameters="allow.sysvipc allow.raw_sockets"

The valid keywords are the following. For more detail, see jail(8) manual page.

allow.set_hostname
 allow.sysvipc
 allow.raw_sockets
 allow.chflags
 allow.mount
 allow.mount.devfs
 allow.mount.nullfs
 allow.mount.procfs
 allow.mount.zfs
 allow.quotas
 allow.socket_af

[20130608] FreeBSD 8.4-RELEASE no longer supports FreeBSD CVS repository. Some documents mistakenly refer to RELENG_8_4_0_RELEASE as CVS tag for the release and RELENG_8_4 as CVS branch tag for the 8.4-RELEASE security branch. However, FreeBSD Project no longer supports FreeBSD CVS repository and 8.4-RELEASE has been released by using FreeBSD subversion repository instead. RELENG_8_4 corresponds to svn://svn.FreeBSD.org/base/releng/8.4, and RELENG_8_4_0_RELEASE corresponds to svn://svn.FreeBSD.org/base/release/8.4.0. Please note that FreeBSD source tree for 8.4-RELEASE and its security branch cannot be updated by using official CVSup servers.

[20130607] (removed about a bge(4) network interface driver issue because it was incorrect)

[20130606] The fxp(4) network interface driver may not work well with the dhclient(8) utility. More specifically, if the /etc/rc.conf has the following line:

ifconfig_fxp0="DHCP"

to activate a DHCP client to configure the network interface, the following notification messages are displayed and the dhclient(8) utility keeps trying to initialize the network interface forever.

kernel: fxp0: link state changed to UP
 kernel: fxp0: link state changed to DOWN

A patch to fix this issue will be released as an Errata - Notice.

5. Late-Breaking News and Corrections

[20130606] As described in FreeBSD 8.4-RELEASE Release Notes, + Notice.

5. Late-Breaking News and Corrections

[20130606] As described in FreeBSD 8.4-RELEASE Release Notes, FreeBSD ZFS subsystem has been updated to support feature flags for ZFS pools. However, the default version number of a newly created ZFS pool is still 28.

This is because FreeBSD 9.0 and 9.1 do not support the feature flags. This means ZFS pools with feature flag support cannot be used on FreeBSD 9.0 and 9.1. An 8.X system with v28 ZFS pools can be upgraded to 9.X with no problem. Note that zfs(8) send and receive commands do not work between pools with different versions. Once a ZFS pool is upgraded from v28, there is no way to upgrade the system to FreeBSD 9.0 and 9.1. FreeBSD 9.2 and later will support ZFS pools with feature flags.

To create a ZFS pool with feature flag support, use the zpool(8) create command and then the zpool(8) upgrade command.

\ No newline at end of file diff --git a/website/content/en/releases/8.4R/hardware.html b/website/content/en/releases/8.4R/hardware.html index 8601ddc082..676c0d2f19 100644 --- a/website/content/en/releases/8.4R/hardware.html +++ b/website/content/en/releases/8.4R/hardware.html @@ -1,10608 +1,10608 @@ FreeBSD 8.4-RELEASE Hardware Notes

FreeBSD 8.4-RELEASE Hardware Notes

The FreeBSD Documentation Project

Copyright © 2013 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/hardware/article.xml 251256 2013-06-02 15:47:22Z hrs $

FreeBSD is a registered trademark of the FreeBSD Foundation.

AMD, Am486, Am5X86, AMD Athlon, AMD Duron, AMD Opteron, AMD-K6, Athlon, Élan, Opteron, and PCnet are trademarks of Advanced Micro Devices, Inc.

Fujitsu, the Fujitsu logo, LifeBook, Stylistic, PRIMEPOWER, PRIMEQUEST, PRIMECLUSTER, ETERNUS, TRIOLE, ESPRIMO, BioMedCAChe, CAChe, CELLINJECTOR, isS, Materials Explorer, SystemWalker, and Interstage are trademarks or registered trademarks of Fujitsu Limited in the United States and other countries.

IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

SPARC, SPARC64, SPARCengine, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer Pages, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, Sun Blade, Sun Enterprise, Sun Fire, SunOS, Ultra and VirtualBox are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol.

Table of Contents
1 Introduction
2 Supported Processors and System Boards
2.1 amd64
2.2 i386
2.3 ia64
2.4 pc98
2.5 powerpc
2.6 sparc64
3 Supported Devices
3.1 Disk Controllers
3.2 Ethernet Interfaces
3.3 FDDI Interfaces
3.4 ATM Interfaces
3.5 Wireless Network Interfaces
3.6 Miscellaneous Networks
3.7 Serial Interfaces
3.8 Sound Devices
3.9 Camera and Video Capture Devices
3.10 USB Devices
3.11 IEEE 1394 (Firewire) Devices
3.12 Bluetooth Devices
3.13 Cryptographic Accelerators
3.14 Miscellaneous

1 Introduction

This document contains the hardware compatibility notes for FreeBSD 8.4-RELEASE. It lists the hardware platforms supported by FreeBSD, as well as the various types of hardware devices (storage controllers, network interfaces, and so on), along with known working instances of these devices.

2 Supported Processors and System Boards

This section provides some architecture-specific information about the specific processors and systems that are supported by each architecture.

2.1 amd64

Since mid-2003 FreeBSD/amd64 has supported the AMD64 (“Hammer”) and Intel® EM64T architecture, and is now one of the Tier-1 platforms (fully supported architecture), which are expected to be Production Quality with respects to all aspects of the FreeBSD operating system, including installation and development environments.

Note that there are two names for this architecture, AMD64 (AMD) and Intel EM64T (Extended Memory 64-bit Technology). 64-bit mode of the two architectures are almost compatible with each other, and FreeBSD/amd64 should support them both.

As of this writing, the following processors are supported:

  • -

    AMD Athlon™64 (“Clawhammer”).

    +

    AMD Athlon™64 (“Clawhammer”).

  • -

    AMD Opteron™ (“Sledgehammer”).

    +

    AMD Opteron™ (“Sledgehammer”).

  • All multi-core Intel Xeon™ processors except Sossaman have EM64T support.

  • The single-core Intel Xeon processors “Nocona”, “Irwindale”, “Potomac”, and “Cranford” have EM64T support.

  • All Intel Core 2 (not Core Duo) and later processors

  • All Intel Pentium® D processors

  • Intel Pentium 4s and Celeron Ds using the “Cedar Mill” core have EM64T support.

  • Some Intel Pentium 4s and Celeron Ds using the “Prescott” core have EM64T support. See the Intel Processor Spec Finder for the definitive answer about EM64T support in Intel processors.

Intel EM64T is an extended version of IA-32 (x86) and different from Intel IA-64 (Itanium) architecture, which FreeBSD/ia64 supports. Some Intel's old documentation refers to Intel EM64T as “64-bit extension technology” or “IA-32e”.

Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are supported.

In many respects, FreeBSD/amd64 is similar to FreeBSD/i386, in terms of drivers supported. Generally, drivers that already function correctly on other 64-bit platforms should work.

2.2 i386

FreeBSD/i386 runs on a wide variety of “IBM PC compatible” machines. Due to the wide range of hardware available for this architecture, it is impossible to exhaustively list all combinations of equipment supported by FreeBSD. Nevertheless, some general guidelines are presented here.

Almost all i386™-compatible processors with a floating point unit are supported. All Intel processors beginning with the 80486 are supported, including the 80486, Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron® processors. All i386-compatible AMD processors are also supported, including the Am486®, Am5x86®, K5, AMD-K6® (and -variants), AMD Athlon (including Athlon-MP, +variants), AMD Athlon (including Athlon-MP, Athlon-XP, Athlon-4, and Athlon Thunderbird), and AMD Duron™ processors. The AMD Élan SC520 embedded +class="trademark">AMD Duron™ processors. The AMD Élan SC520 embedded processor is supported. The Transmeta Crusoe is recognized and supported, as are i386-compatible processors from Cyrix and NexGen.

There is a wide variety of motherboards available for this architecture. Motherboards using the ISA, VLB, EISA, AGP, and PCI expansion buses are well-supported. There is some limited support for the MCA (“MicroChannel”) expansion bus used in the IBM PS/2 line of PCs.

Symmetric multi-processor (SMP) systems are generally supported by FreeBSD, although in some cases, BIOS or motherboard bugs may generate some problems. Perusal of the archives of the FreeBSD symmetric multiprocessing mailing list may yield some clues.

FreeBSD will take advantage of SMT (Symmetric MultiThreading, also known as HyperThreading on Intel CPUs) on the supported CPUs. The GENERIC kernel which is installed by default will automatically detect the additional logical processors. The default FreeBSD scheduler recognizes processor topology on the system and selects logical and physical processors to obtain optimal performance. The smp(4) manual page has more details.

FreeBSD will take advantage of Physical Address Extensions (PAE) support on CPUs that support this feature. A kernel with the PAE feature enabled will detect memory above 4 gigabytes and allow it to be used by the system. This feature places constraints on the device drivers and other features of FreeBSD which may be used; consult the pae(4) manual page for more details.

FreeBSD will generally run on i386-based laptops, albeit with varying levels of support for certain hardware features such as sound, graphics, power management, and PCCARD expansion slots. These features tend to vary in idiosyncratic ways between machines, and frequently require special-case support in FreeBSD to work around hardware bugs or other oddities. When in doubt, a search of the archives of the FreeBSD laptop computer mailing list may be useful.

Most modern laptops (as well as many desktops) use the Advanced Configuration and Power Management (ACPI) standard. FreeBSD supports ACPI via the ACPI Component Architecture reference implementation from Intel, as described in the acpi(4) manual page. The use of ACPI causes instabilities on some machines and it may be necessary to disable the ACPI driver, which is normally loaded via a kernel module. This may be accomplished by adding the following line to /boot/device.hints:

 hint.acpi.0.disabled="1"

Users debugging ACPI-related problems may find it useful to disable portions of the ACPI functionality. The acpi(4) manual page has more information on how to do this via loader tunables.

ACPI depends on a Differentiated System Descriptor Table (DSDT) provided by each machine's BIOS. Some machines have bad or incomplete DSDTs, which prevents ACPI from functioning correctly. Replacement DSDTs for some machines can be found at the DSDT section of the ACPI4Linux project Web site. FreeBSD can use these DSDTs to override the DSDT provided by the BIOS; see the acpi(4) manual page for more information.

2.3 ia64

Currently supported processors are the Itanium® and the Itanium 2.

Supported chipsets include:

  • HP zx1

  • Intel 460GX

  • Intel E8870

Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) configurations are supported.

Most devices that can be found in or are compatible with ia64 machines are fully supported. The notable exception is the VGA console. The FreeBSD support for VGA consoles is at this time too much based on PC hardware and not all ia64 machines have chipsets that provide sufficient PC legacy support. As such syscons(4) can not be enabled and the use of a serial console is required.

2.4 pc98

NEC PC-9801/9821 series with almost all i386-compatible processors, including 80486, Pentium, Pentium Pro, Pentium II, and variants. All i386-compatible processors by AMD, Cyrix, IBM, and IDT are also supported.

NEC FC-9801/9821 series, and NEC SV-98 series (both of them are compatible with PC-9801/9821 series) should be supported.

EPSON PC-386/486/586 series, which are compatible with NEC PC-9801 series are supported.

High-resolution mode is not supported. NEC PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in normal (PC-9801 compatible) mode only.

Although there are some multi-processor systems (such as Rs20/B20), SMP-related features of FreeBSD are not supported yet.

PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE expansion bus (110pin), and PCI bus are supported. New Extend Standard Architecture (NESA) bus (used in PC-H98, SV-H98, and FC-H98 series) is not supported.

2.5 powerpc

The information for this paragraph has yet to be compiled.

2.6 sparc64

This section describes the systems currently known to be supported by FreeBSD on the Fujitsu SPARC64® and Sun UltraSPARC® platforms. For background information on the various hardware designs see the Sun System Handbook.

SMP is supported on all systems with more than 1 processor.

When using the GENERIC kernel, FreeBSD/sparc64 systems not equipped with a framebuffer supported by the creator(4) (Sun Creator, Sun Creator3D and Sun Elite3D) or machfb(4) (Sun PGX and Sun PGX64 as well as the ATI Mach64 chips found onboard in for example - Sun Blade™ 100, Sun Blade 150, Sun Ultra™ -5 and Sun Ultra 10) driver must use the serial + Sun Blade™ 100, Sun Blade 150, Sun Ultra™ +5 and Sun Ultra 10) driver must use the serial console.

If you have a system that is not listed here, it may not have been tested with FreeBSD 8.4-RELEASE. We encourage you to try it and send a note to the FreeBSD SPARC porting mailing list with your results, including which devices work and which do not.

The following systems are fully supported by FreeBSD:

  • Naturetech GENIALstation 777S

  • -

    Sun Blade 100

    +

    Sun Blade 100

  • -

    Sun Blade 150

    +

    Sun Blade 150

  • -

    Sun Enterprise™ 150

    +

    Sun Enterprise™ 150

  • -

    Sun Enterprise 220R

    +

    Sun Enterprise 220R

  • -

    Sun Enterprise 250

    +

    Sun Enterprise 250

  • -

    Sun Enterprise 420R

    +

    Sun Enterprise 420R

  • -

    Sun Enterprise 450

    +

    Sun Enterprise 450

  • -

    Sun Fire™ B100s (support for the on-board NICs +

    Sun Fire™ B100s (support for the on-board NICs first appeared in 8.1-RELEASE)

  • -

    Sun Fire V100

    +

    Sun Fire V100

  • -

    Sun Fire V120

    +

    Sun Fire V120

  • Sun Netra™ t1 100/105

  • Sun Netra T1 AC200/DC200

  • Sun Netra t 1100

  • Sun Netra t 1120

  • Sun Netra t 1125

  • Sun Netra t 1400/1405

  • Sun Netra 120

  • Sun Netra X1

  • Sun SPARCengine® Ultra AX1105

  • Sun SPARCengine Ultra AXe

  • Sun SPARCengine Ultra AXi

  • Sun SPARCengine Ultra AXmp

  • Sun SPARCengine CP1500

  • -

    Sun Ultra 1

    +

    Sun Ultra 1

  • -

    Sun Ultra 1E

    +

    Sun Ultra 1E

  • -

    Sun Ultra 2

    +

    Sun Ultra 2

  • -

    Sun Ultra 5

    +

    Sun Ultra 5

  • -

    Sun Ultra 10

    +

    Sun Ultra 10

  • -

    Sun Ultra 30

    +

    Sun Ultra 30

  • -

    Sun Ultra 60

    +

    Sun Ultra 60

  • -

    Sun Ultra 80

    +

    Sun Ultra 80

  • -

    Sun Ultra 450

    +

    Sun Ultra 450

The following systems are partially supported by FreeBSD. In particular the fiber channel controllers in SBus-based systems are not supported. However, it is possible to use these with a SCSI controller supported by the esp(4) driver (Sun ESP SCSI, Sun FAS Fast-SCSI and Sun FAS366 Fast-Wide SCSI controllers).

  • -

    Sun Enterprise 3500

    +

    Sun Enterprise 3500

  • -

    Sun Enterprise 4500

    +

    Sun Enterprise 4500

Starting with 7.2-RELEASE, sparc64 systems based on Sun UltraSPARC III and beyond are also supported by FreeBSD, which includes the following known working systems:

  • -

    Sun Blade 1000

    +

    Sun Blade 1000

  • -

    Sun Blade 1500

    +

    Sun Blade 1500

  • -

    Sun Blade 2000

    +

    Sun Blade 2000

  • -

    Sun Blade 2500

    +

    Sun Blade 2500

  • -

    Sun Fire 280R

    +

    Sun Fire 280R

  • -

    Sun Fire V210

    +

    Sun Fire V210

  • -

    Sun Fire V215 (support first appeared in 7.3-RELEASE +

    Sun Fire V215 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)

  • -

    Sun Fire V240

    +

    Sun Fire V240

  • -

    Sun Fire V245 (support first appeared in 7.3-RELEASE +

    Sun Fire V245 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)

  • -

    Sun Fire V250

    +

    Sun Fire V250

  • -

    Sun Fire V440 (support for the on-board NICs first +

    Sun Fire V440 (support for the on-board NICs first appeared in 7.3-RELEASE and 8.0-RELEASE)

  • -

    Sun Fire V480 (501-6780 and 501-6790 centerplanes only, +

    Sun Fire V480 (501-6780 and 501-6790 centerplanes only, for which support first appeared in 7.3-RELEASE and 8.1-RELEASE, other centerplanes might work beginning with 8.3-RELEASE and 9.0-RELEASE)

  • -

    Sun Fire V880

    +

    Sun Fire V880

  • -

    Sun Fire V890 (support first appeared in 7.4-RELEASE +

    Sun Fire V890 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, non-mixed UltraSPARC IV/IV+ CPU-configurations only)

  • Netra 20/Netra T4

The following Sun UltraSPARC systems are not tested but believed to be also supported by FreeBSD:

  • -

    Sun Fire V125

    +

    Sun Fire V125

  • -

    Sun Fire V490 (support first appeared in 7.4-RELEASE +

    Sun Fire V490 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, non-mixed UltraSPARC IV/IV+ CPU-configurations only)

Starting with 7.4-RELEASE and 8.1-RELEASE, sparc64 systems based on Fujitsu SPARC64 V are also supported by FreeBSD, which includes the following known working systems:

  • Fujitsu PRIMEPOWER® 250

The following Fujitsu PRIMEPOWER systems are not tested but believed to be also supported by FreeBSD:

  • Fujitsu PRIMEPOWER 450

  • Fujitsu PRIMEPOWER 650

  • Fujitsu PRIMEPOWER 850

3 Supported Devices

This section describes the devices currently known to be supported by FreeBSD. Other configurations may also work, but simply have not been tested yet. Feedback, updates, and corrections to this list are encouraged.

Where possible, the drivers applicable to each device or class of devices is listed. If the driver in question has a manual page in the FreeBSD base distribution (most should), it is referenced here. Information on specific models of supported devices, controllers, etc. can be found in the manual pages.

Note: The device lists in this document are being generated automatically from FreeBSD manual pages. This means that some devices, which are supported by multiple drivers, may appear multiple times.

3.1 Disk Controllers

[amd64, i386, ia64, pc98, sparc64] IDE/ATA controllers ( ata(4) driver)

[pc98] IDE/ATA controllers (wdc driver)

  • On-board IDE controller

[i386,ia64,amd64] Controllers supported by the aac(4) driver include:

  • Adaptec AAC-364

  • Adaptec RAID 2045

  • Adaptec RAID 2405

  • Adaptec RAID 2445

  • Adaptec RAID 2805

  • Adaptec RAID 3085

  • Adaptec RAID 31205

  • Adaptec RAID 31605

  • Adaptec RAID 5085

  • Adaptec RAID 51205

  • Adaptec RAID 51245

  • Adaptec RAID 51605

  • Adaptec RAID 51645

  • Adaptec RAID 52445

  • Adaptec RAID 5405

  • Adaptec RAID 5445

  • Adaptec RAID 5805

  • Adaptec SAS RAID 3405

  • Adaptec SAS RAID 3805

  • Adaptec SAS RAID 4000SAS

  • Adaptec SAS RAID 4005SAS

  • Adaptec SAS RAID 4800SAS

  • Adaptec SAS RAID 4805SAS

  • Adaptec SATA RAID 2020SA ZCR

  • Adaptec SATA RAID 2025SA ZCR

  • Adaptec SATA RAID 2026ZCR

  • Adaptec SATA RAID 2410SA

  • Adaptec SATA RAID 2420SA

  • Adaptec SATA RAID 2610SA

  • Adaptec SATA RAID 2620SA

  • Adaptec SATA RAID 2810SA

  • Adaptec SATA RAID 2820SA

  • Adaptec SATA RAID 21610SA

  • Adaptec SCSI RAID 2020ZCR

  • Adaptec SCSI RAID 2025ZCR

  • Adaptec SCSI RAID 2120S

  • Adaptec SCSI RAID 2130S

  • Adaptec SCSI RAID 2130SLP

  • Adaptec SCSI RAID 2230SLP

  • Adaptec SCSI RAID 2200S

  • Adaptec SCSI RAID 2240S

  • Adaptec SCSI RAID 3230S

  • Adaptec SCSI RAID 3240S

  • Adaptec SCSI RAID 5400S

  • Dell CERC SATA RAID 2

  • Dell PERC 2/Si

  • Dell PERC 2/QC

  • Dell PERC 3/Si

  • Dell PERC 3/Di

  • Dell PERC 320/DC

  • HP ML110 G2 (Adaptec SATA RAID 2610SA)

  • HP NetRAID 4M

  • IBM ServeRAID 8i

  • IBM ServeRAID 8k

  • IBM ServeRAID 8s

  • ICP RAID ICP5045BL

  • ICP RAID ICP5085BL

  • ICP RAID ICP5085SL

  • ICP RAID ICP5125BR

  • ICP RAID ICP5125SL

  • ICP RAID ICP5165BR

  • ICP RAID ICP5165SL

  • ICP RAID ICP5445SL

  • ICP RAID ICP5805BL

  • ICP RAID ICP5805SL

  • ICP ICP5085BR SAS RAID

  • ICP ICP9085LI SAS RAID

  • ICP ICP9047MA SATA RAID

  • ICP ICP9067MA SATA RAID

  • ICP ICP9087MA SATA RAID

  • ICP ICP9014RO SCSI RAID

  • ICP ICP9024RO SCSI RAID

  • Legend S220

  • Legend S230

  • Sun STK RAID REM

  • Sun STK RAID EM

  • SG-XPCIESAS-R-IN

  • SG-XPCIESAS-R-EX

  • AOC-USAS-S4i

  • AOC-USAS-S8i

  • AOC-USAS-S4iR

  • AOC-USAS-S8iR

  • AOC-USAS-S8i-LP

  • AOC-USAS-S8iR-LP

[i386,pc98,amd64] The adv(4) driver supports the following SCSI controllers:

  • AdvanSys ABP510/5150

  • AdvanSys ABP5140

  • AdvanSys ABP5142

  • AdvanSys ABP902/3902

  • AdvanSys ABP3905

  • AdvanSys ABP915

  • AdvanSys ABP920

  • AdvanSys ABP3922

  • AdvanSys ABP3925

  • AdvanSys ABP930, ABP930U, ABP930UA

  • AdvanSys ABP960, ABP960U

  • AdvanSys ABP542

  • AdvanSys ABP742

  • AdvanSys ABP842

  • AdvanSys ABP940

  • AdvanSys ABP940UA/3940UA

  • AdvanSys ABP940U

  • AdvanSys ABP3960UA

  • AdvanSys ABP970, ABP970U

  • AdvanSys ABP752

  • AdvanSys ABP852

  • AdvanSys ABP950

  • AdvanSys ABP980, ABP980U

  • AdvanSys ABP980UA/3980UA

  • MELCO IFC-USP (PC-98)

  • RATOC REX-PCI30 (PC-98)

  • @Nifty FNECHARD IFC-USUP-TX (PC-98)

[i386,pc98,amd64] The adw(4) driver supports SCSI controllers including:

  • AdvanSys ABP940UW/ABP3940UW

  • AdvanSys ABP950UW

  • AdvanSys ABP970UW

  • AdvanSys ABP3940U2W

  • AdvanSys ABP3950U2W

[i386] The aha(4) driver supports the following SCSI host adapters:

  • Adaptec AHA-154xB

  • Adaptec AHA-154xC

  • Adaptec AHA-154xCF

  • Adaptec AHA-154xCP

  • Adaptec AHA-1640

  • Adaptec AHA-174x in 154x emulation mode

  • DTC 3290 SCSI controller in 1542 emulation mode

  • Tekram SCSI controllers in 154x emulation mode

[i386] The ahb(4) driver supports the following SCSI host adapters:

  • Adaptec AHA-1740

  • Adaptec AHA-1742

  • Adaptec AHA-1740A

  • Adaptec AHA-1742A

The ahc(4) driver supports the following SCSI host adapter chips and SCSI controller cards:

  • Adaptec AIC7770 host adapter chip

  • Adaptec AIC7850 host adapter chip

  • Adaptec AIC7860 host adapter chip

  • Adaptec AIC7870 host adapter chip

  • Adaptec AIC7880 host adapter chip

  • Adaptec AIC7890 host adapter chip

  • Adaptec AIC7891 host adapter chip

  • Adaptec AIC7892 host adapter chip

  • Adaptec AIC7895 host adapter chip

  • Adaptec AIC7896 host adapter chip

  • Adaptec AIC7897 host adapter chip

  • Adaptec AIC7899 host adapter chip

  • Adaptec 274X(W)

  • Adaptec 274X(T)

  • Adaptec 284X

  • Adaptec 2910

  • Adaptec 2915

  • Adaptec 2920C

  • Adaptec 2930C

  • Adaptec 2930U2

  • Adaptec 2940

  • Adaptec 2940J

  • Adaptec 2940N

  • Adaptec 2940U

  • Adaptec 2940AU

  • Adaptec 2940UW

  • Adaptec 2940UW Dual

  • Adaptec 2940UW Pro

  • Adaptec 2940U2W

  • Adaptec 2940U2B

  • Adaptec 2950U2W

  • Adaptec 2950U2B

  • Adaptec 19160B

  • Adaptec 29160B

  • Adaptec 29160N

  • Adaptec 3940

  • Adaptec 3940U

  • Adaptec 3940AU

  • Adaptec 3940UW

  • Adaptec 3940AUW

  • Adaptec 3940U2W

  • Adaptec 3950U2

  • Adaptec 3960

  • Adaptec 39160

  • Adaptec 3985

  • Adaptec 4944UW

  • NEC PC-9821Xt13 (PC-98)

  • NEC RvII26 (PC-98)

  • NEC PC-9821X-B02L/B09 (PC-98)

  • NEC SV-98/2-B03 (PC-98)

  • Many motherboards with on-board SCSI support

[i386,sparc64,ia64,amd64] The ahd(4) driver supports the following:

  • Adaptec AIC7901 host adapter chip

  • Adaptec AIC7901A host adapter chip

  • Adaptec AIC7902 host adapter chip

  • Adaptec 29320 host adapter

  • Adaptec 39320 host adapter

  • Many motherboards with on-board SCSI support

[i386,pc98,amd64] The adapters supported by the aic(4) driver include:

  • Adaptec AHA-1505 (ISA)

  • Adaptec AHA-1510A, AHA-1510B (ISA)

  • Adaptec AHA-1520A, AHA-1520B (ISA)

  • Adaptec AHA-1522A, AHA-1522B (ISA)

  • Adaptec AHA-1535 (ISA)

  • Creative Labs SoundBlaster SCSI host adapter (ISA)

  • Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)

  • Adaptec AHA-1030B, AHA-1030P (PC98)

  • NEC PC-9801-100 (PC98)

[i386,pc98,amd64] Controllers supported by the amd(4) driver include:

  • MELCO IFC-DP (PC-98)

  • Tekram DC390

  • Tekram DC390T

Controllers supported by the amr(4) driver include:

  • MegaRAID SATA 150-4

  • MegaRAID SATA 150-6

  • MegaRAID SATA 300-4X

  • MegaRAID SATA 300-8X

  • MegaRAID SCSI 320-1E

  • MegaRAID SCSI 320-2E

  • MegaRAID SCSI 320-4E

  • MegaRAID SCSI 320-0X

  • MegaRAID SCSI 320-2X

  • MegaRAID SCSI 320-4X

  • MegaRAID SCSI 320-0

  • MegaRAID SCSI 320-1

  • MegaRAID SCSI 320-2

  • MegaRAID SCSI 320-4

  • MegaRAID Series 418

  • MegaRAID i4 133 RAID

  • MegaRAID Elite 1500 (Series 467)

  • MegaRAID Elite 1600 (Series 493)

  • MegaRAID Elite 1650 (Series 4xx)

  • MegaRAID Enterprise 1200 (Series 428)

  • MegaRAID Enterprise 1300 (Series 434)

  • MegaRAID Enterprise 1400 (Series 438)

  • MegaRAID Enterprise 1500 (Series 467)

  • MegaRAID Enterprise 1600 (Series 471)

  • MegaRAID Express 100 (Series 466WS)

  • MegaRAID Express 200 (Series 466)

  • MegaRAID Express 300 (Series 490)

  • MegaRAID Express 500 (Series 475)

  • Dell PERC

  • Dell PERC 2/SC

  • Dell PERC 2/DC

  • Dell PERC 3/DCL

  • Dell PERC 3/QC

  • Dell PERC 4/DC

  • Dell PERC 4/IM

  • Dell PERC 4/SC

  • Dell PERC 4/Di

  • Dell PERC 4e/DC

  • Dell PERC 4e/Di

  • Dell PERC 4e/Si

  • Dell PERC 4ei

  • HP NetRAID-1/Si

  • HP NetRAID-3/Si (D4943A)

  • HP Embedded NetRAID

  • Intel RAID Controller SRCS16

  • Intel RAID Controller SRCU42X

[i386,amd64] The arcmsr(4) driver supports the following cards:

  • ARC-1110

  • ARC-1120

  • ARC-1130

  • ARC-1160

  • ARC-1170

  • ARC-1110ML

  • ARC-1120ML

  • ARC-1130ML

  • ARC-1160ML

  • ARC-1200

  • ARC-1201

  • ARC-1210

  • ARC-1212

  • ARC-1213

  • ARC-1214

  • ARC-1220

  • ARC-1222

  • ARC-1223

  • ARC-1224

  • ARC-1230

  • ARC-1231

  • ARC-1260

  • ARC-1261

  • ARC-1270

  • ARC-1280

  • ARC-1210ML

  • ARC-1220ML

  • ARC-1231ML

  • ARC-1261ML

  • ARC-1280ML

  • ARC-1380

  • ARC-1381

  • ARC-1680

  • ARC-1681

  • ARC-1880

  • ARC-1882

[i386] The adapters currently supported by the asr(4) driver include the following:

  • Adaptec Zero-Channel SCSI RAID 2000S, 2005S, 2010S, 2015S

  • Adaptec SCSI RAID 2100S, 2110S

  • Adaptec ATA-100 RAID 2400A

  • Adaptec SCSI RAID 3200S, 3210S

  • Adaptec SCSI RAID 3400S, 3410S

  • Adaptec SmartRAID PM1554

  • Adaptec SmartRAID PM1564

  • Adaptec SmartRAID PM2554

  • Adaptec SmartRAID PM2564

  • Adaptec SmartRAID PM2664

  • Adaptec SmartRAID PM2754

  • Adaptec SmartRAID PM2865

  • Adaptec SmartRAID PM3754

  • Adaptec SmartRAID PM3755U2B / SmartRAID V Millennium

  • Adaptec SmartRAID PM3757

  • DEC KZPCC-AC (LVD 1-ch, 4MB or 16MB cache), DEC KZPCC-CE (LVD 3-ch, 64MB cache), DEC KZPCC-XC (LVD 1-ch, 16MB cache), DEC KZPCC-XE (LVD 3-ch, 64MB cache) -- rebadged SmartRAID V Millennium

[i386,amd64] The bt(4) driver supports the following BusLogic MultiMaster “W”, “C”, “S”, and “A” series and compatible SCSI host adapters:

  • BusLogic BT-445C

  • BusLogic BT-445S

  • BusLogic BT-540CF

  • BusLogic BT-542B

  • BusLogic BT-542B

  • BusLogic BT-542D

  • BusLogic BT-545C

  • BusLogic BT-545S

  • BusLogic/BusTek BT-640

  • BusLogic BT-742A

  • BusLogic BT-742A

  • BusLogic BT-747C

  • BusLogic BT-747D

  • BusLogic BT-747S

  • BusLogic BT-757C

  • BusLogic BT-757CD

  • BusLogic BT-757D

  • BusLogic BT-757S

  • BusLogic BT-946C

  • BusLogic BT-948

  • BusLogic BT-956C

  • BusLogic BT-956CD

  • BusLogic BT-958

  • BusLogic BT-958D

  • Storage Dimensions SDC3211B / SDC3211F

AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also supported by the bt(4) driver.

[i386,ia64,amd64] Controllers supported by the ciss(4) driver include:

  • Compaq Smart Array 5300

  • Compaq Smart Array 532

  • Compaq Smart Array 5i

  • HP Smart Array 5312

  • HP Smart Array 6i

  • HP Smart Array 641

  • HP Smart Array 642

  • HP Smart Array 6400

  • HP Smart Array 6400 EM

  • HP Smart Array E200

  • HP Smart Array E200i

  • HP Smart Array P212

  • HP Smart Array P220i

  • HP Smart Array P222

  • HP Smart Array P400

  • HP Smart Array P400i

  • HP Smart Array P410

  • HP Smart Array P410i

  • HP Smart Array P411

  • HP Smart Array P420

  • HP Smart Array P420i

  • HP Smart Array P421

  • HP Smart Array P600

  • HP Smart Array P721m

  • HP Smart Array P800

  • HP Smart Array P812

  • HP Modular Smart Array 20 (MSA20)

  • HP Modular Smart Array 500 (MSA500)

[pc98] The ct(4) driver supports the following adapters:

  • ELECOM bus-master SCSI adapters

  • I-O DATA SC-98II

  • ICM IF-2660, IF-2766, IF-2766ET, IF-2767 and IF-2769

  • Logitec LHA-N151 and LHA-20x series

  • Midori-Denshi MDC-554NA and MDC-926R

  • NEC PC-9801-55, 92 and compatibles

  • SMIT transfer type SCSI host adapters

  • TEXA HA-55BS2 and its later models

[i386,ia64,amd64] The dpt(4) driver provides support for the following RAID adapters:

  • DPT Smart Cache Plus

  • Smart Cache II (PM2?2?, PM2022 [EISA], PM2024/PM2124 [PCI]) (Gen2)

  • Smart RAID II (PM3?2?, PM3021, PM3222)

  • Smart Cache III (PM2?3?)

  • Smart RAID III (PM3?3?, PM3332 [EISA], PM3334UW [PCI]) (Gen3)

  • Smart Cache IV (PM2?4?, PM2042 [EISA], PM2044/PM2144 [PCI]) (Gen4)

  • Smart RAID IV

Note: [amd64, i386] Booting from these controllers is supported. EISA adapters are not supported.

[sparc64] Controllers supported by the esp(4) driver include:

  • MELCO IFC-DP (PC-98)

  • Sun ESP family

  • Sun FAS family

  • Tekram DC390

  • Tekram DC390T

[i386,amd64] The hpt27xx(4) driver supports the following SAS controllers:

  • HighPoint's RocketRAID 271x series

  • HighPoint's RocketRAID 272x series

  • HighPoint's RocketRAID 274x series

  • HighPoint's RocketRAID 276x series

  • HighPoint's RocketRAID 278x series

[i386,amd64] The hptiop(4) driver supports the following SAS and SATA RAID controllers:

  • HighPoint RocketRAID 4522

  • HighPoint RocketRAID 4520

  • HighPoint RocketRAID 4322

  • HighPoint RocketRAID 4321

  • HighPoint RocketRAID 4320

  • HighPoint RocketRAID 4311

  • HighPoint RocketRAID 4310

  • HighPoint RocketRAID 4211

  • HighPoint RocketRAID 4210

  • HighPoint RocketRAID 3560

  • HighPoint RocketRAID 3540

  • HighPoint RocketRAID 3530

  • HighPoint RocketRAID 3522

  • HighPoint RocketRAID 3521

  • HighPoint RocketRAID 3520

  • HighPoint RocketRAID 3511

  • HighPoint RocketRAID 3510

  • HighPoint RocketRAID 3410

  • HighPoint RocketRAID 3320

  • HighPoint RocketRAID 3220

  • HighPoint RocketRAID 3122

  • HighPoint RocketRAID 3120

  • HighPoint RocketRAID 3020

[i386,amd64] The hptmv(4) driver supports the following ATA RAID controllers:

  • HighPoint's RocketRAID 182x series

[i386,amd64] The hptrr(4) driver supports the following RAID controllers:

  • RocketRAID 172x series

  • RocketRAID 174x series

  • RocketRAID 2210

  • RocketRAID 222x series

  • RocketRAID 2240

  • RocketRAID 230x series

  • RocketRAID 231x series

  • RocketRAID 232x series

  • RocketRAID 2340

  • RocketRAID 2522

[i386] The following controllers are supported by the ida(4) driver:

  • Compaq SMART Array 221

  • Compaq Integrated SMART Array Controller

  • Compaq SMART Array 4200

  • Compaq SMART Array 4250ES

  • Compaq SMART 3200 Controller

  • Compaq SMART 3100ES Controller

  • Compaq SMART-2/DH Controller

  • Compaq SMART-2/SL Controller

  • Compaq SMART-2/P Controller

  • Compaq SMART-2/E Controller

  • Compaq SMART Controller

[i386,ia64,amd64] Controllers supported by the iir(4) driver include:

  • Intel RAID Controller SRCMR

  • Intel Server RAID Controller U3-l (SRCU31a)

  • Intel Server RAID Controller U3-1L (SRCU31La)

  • Intel Server RAID Controller U3-2 (SRCU32)

  • All past and future releases of Intel and ICP RAID Controllers.

  • Intel RAID Controller SRCU21 (discontinued)

  • Intel RAID Controller SRCU31 (older revision, not compatible)

  • Intel RAID Controller SRCU31L (older revision, not compatible)

The SRCU31 and SRCU31L can be updated via a firmware update available from Intel.

[i386,amd64] Controllers supported by the ips(4) driver include:

  • IBM ServeRAID 3H

  • ServeRAID 4L/4M/4H

  • ServeRAID Series 5

  • ServeRAID 6i/6M

  • ServeRAID 7t/7k/7M

[i386,amd64] The isci(4) driver provides support for Intel C600 SAS controllers.

Cards supported by the isp(4) driver include:

  • ISP1000

  • ISP1020

  • ISP1040

  • Qlogic 1240

  • Qlogic 1020

  • Qlogic 1040

  • Qlogic 1080

  • Qlogic 1280

  • Qlogic 12160

  • Qlogic 210X

  • Qlogic 220X

  • Qlogic 2300

  • Qlogic 2312

  • Qlogic 234X

  • Qlogic 2322

  • Qlogic 200

  • Qlogic 2422

  • Qlogic 2432

[i386,ia64,amd64] The mfi(4) driver supports the following hardware:

  • LSI MegaRAID SAS 1078

  • LSI MegaRAID SAS 8408E

  • LSI MegaRAID SAS 8480E

  • LSI MegaRAID SAS 9260

  • Dell PERC5

  • Dell PERC6

  • IBM ServeRAID M5015 SAS/SATA

  • IBM ServeRAID-MR10i

  • Intel RAID Controller SROMBSAS18E

[i386,ia64,amd64] Controllers supported by the mlx(4) driver include:

  • Mylex DAC960P

  • Mylex DAC960PD / DEC KZPSC (Fast Wide)

  • Mylex DAC960PDU

  • Mylex DAC960PL

  • Mylex DAC960PJ

  • Mylex DAC960PG

  • Mylex DAC960PU / DEC PZPAC (Ultra Wide)

  • Mylex AcceleRAID 150 (DAC960PRL)

  • Mylex AcceleRAID 250 (DAC960PTL1)

  • Mylex eXtremeRAID 1100 (DAC1164P)

  • RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA (3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)

All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is always advisable to upgrade to the most recent firmware available for the controller.

Compatible Mylex controllers not listed should work, but have not been verified.

Note: [amd64, i386] Booting from these controllers is supported. EISA adapters are not supported.

[i386,ia64,amd64] Controllers supported by the mly(4) driver include:

  • Mylex AcceleRAID 160

  • Mylex AcceleRAID 170

  • Mylex AcceleRAID 352

  • Mylex eXtremeRAID 2000

  • Mylex eXtremeRAID 3000

Compatible Mylex controllers not listed should work, but have not been verified.

The mps(4) driver supports the following controllers:

  • LSI Logic SAS2004 (4 Port SAS)

  • LSI Logic SAS2008 (8 Port SAS)

  • LSI Logic SAS2108 (8 Port SAS)

  • LSI Logic SAS2116 (16 Port SAS)

  • LSI Logic SAS2208 (8 Port SAS)

The following controllers are supported by the mpt(4) driver:

  • LSI Logic 53c1030, LSI Logic LSI2x320-X (Single and Dual Ultra320 SCSI)

  • LSI Logic AS1064, LSI Logic AS1068

  • LSI Logic FC909 (1Gb/s Fibre Channel)

  • LSI Logic FC909A (Dual 1Gb/s Fibre Channel)

  • LSI Logic FC919, LSI Logic 7102XP-LC (Single 2Gb/s Fibre Channel)

  • LSI Logic FC929, LSI Logic FC929X, LSI Logic 7202XP-LC (Dual 2Gb/s Fibre Channel)

  • LSI Logic FC949X (Dual 4Gb/s Fibre Channel)

  • LSI Logic FC949E, LSI Logic FC949ES (Dual 4Gb/s Fibre Channel PCI-Express)

The Ultra 320 SCSI controller chips supported by the mpt(4) driver can be found onboard on many systems including:

  • Dell PowerEdge 1750 thru 2850

  • IBM eServer xSeries 335

These systems also contain Integrated Raid Mirroring and Integrated Raid Mirroring Enhanced which this driver also supports.

The SAS controller chips are also present on many new AMD/Opteron based systems, like the Sun 4100. Note that this controller can drive both SAS and SATA drives or a mix of them at the same time. The Integrated Raid Mirroring available for these controllers is poorly supported at best.

The Fibre Channel controller chipset are supported by a broad variety of speeds and systems. The Apple Fibre Channel HBA is in fact the FC949ES card.

This driver also supports target mode for Fibre Channel cards. This support may be enabled by setting the desired role of the core via the LSI Logic firmware utility that establishes what roles the card can take on - no separate compilation is required.

The mvs(4) driver supports the following controllers:

Gen-I (SATA 1.5Gbps):

  • 88SX5040

  • 88SX5041

  • 88SX5080

  • 88SX5081

Gen-II (SATA 3Gbps, NCQ, PMP):

  • 88SX6040

  • 88SX6041 (including Adaptec 1420SA)

  • 88SX6080

  • 88SX6081

Gen-IIe (SATA 3Gbps, NCQ, PMP with FBS):

  • 88SX6042

  • 88SX7042 (including Adaptec 1430SA)

  • 88F5182 SoC

  • 88F6281 SoC

  • MV78100 SoC

Note, that this hardware supports command queueing and FIS-based switching only for ATA DMA commands. ATAPI and non-DMA ATA commands executed one by one for each port.

[i386,pc98,amd64] The ncr(4) driver provides support for the following NCR/Symbios SCSI controller chips:

  • 53C810

  • 53C810A

  • 53C815

  • 53C820

  • 53C825A

  • 53C860

  • 53C875

  • 53C875J

  • 53C885

  • 53C895

  • 53C895A

  • 53C896

  • 53C1510D

The following add-on boards are known to be supported:

  • I-O DATA SC-98/PCI (PC-98)

  • I-O DATA SC-PCI (PC-98)

[i386,pc98] The following devices are currently supported by the ncv(4) driver:

  • I-O DATA PCSC-DV

  • KME KXLC002 (TAXAN ICD-400PN, etc.), KXLC004, and UJDCD450

  • Macnica Miracle SCSI-II mPS110

  • Media Intelligent MSC-110, MSC-200

  • NEC PC-9801N-J03R

  • New Media Corporation BASICS SCSI

  • Qlogic Fast SCSI

  • RATOC REX-9530, REX-5572 (SCSI only)

[i386,pc98] Controllers supported by the nsp(4) driver include:

  • Alpha-Data AD-PCS201

  • I-O DATA CBSC16

[i386] The pst(4) driver supports the Promise Supertrak SX6000 ATA hardware RAID controller.

[i386,pc98] Controllers supported by the stg(4) driver include:

  • Adaptec 2920/A

  • Future Domain SCSI2GO

  • Future Domain TMC-18XX/3260

  • IBM SCSI PCMCIA Card

  • ICM PSC-2401 SCSI

  • MELCO IFC-SC

  • RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A

Note that the Adaptec 2920C is supported by the ahc(4) driver.

The sym(4) driver provides support for the following Symbios/LSI Logic PCI SCSI controllers:

  • 53C810

  • 53C810A

  • 53C815

  • 53C825

  • 53C825A

  • 53C860

  • 53C875

  • 53C876

  • 53C895

  • 53C895A

  • 53C896

  • 53C897

  • 53C1000

  • 53C1000R

  • 53C1010-33

  • 53C1010-66

  • 53C1510D

The SCSI controllers supported by sym(4) can be either embedded on a motherboard, or on one of the following add-on boards:

  • ASUS SC-200, SC-896

  • Data Technology DTC3130 (all variants)

  • DawiControl DC2976UW

  • Diamond FirePort (all)

  • I-O DATA SC-UPCI (PC-98)

  • Logitec LHA-521UA (PC-98)

  • NCR cards (all)

  • Symbios cards (all)

  • Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D, and 390U3W

  • Tyan S1365

[i386,amd64] SCSI controllers supported by the trm(4) driver include:

  • Tekram DC-315 PCI Ultra SCSI adapter without BIOS and internal SCSI connector

  • Tekram DC-315U PCI Ultra SCSI adapter without BIOS

  • Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI connector

  • Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS

  • Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS

  • Tekram DC-395U2W PCI Ultra2-Wide SCSI adapter with flash BIOS

For the Tekram DC-310/U and DC-390F/U/UW/U2B/U2W/U3W PCI SCSI host adapters, use the sym(4) driver.

[i386,amd64] The twa(4) driver supports the following SATA RAID controllers:

  • AMCC's 3ware 9500S-4LP

  • AMCC's 3ware 9500S-8

  • AMCC's 3ware 9500S-8MI

  • AMCC's 3ware 9500S-12

  • AMCC's 3ware 9500S-12MI

  • AMCC's 3ware 9500SX-4LP

  • AMCC's 3ware 9500SX-8LP

  • AMCC's 3ware 9500SX-12

  • AMCC's 3ware 9500SX-12MI

  • AMCC's 3ware 9500SX-16ML

  • AMCC's 3ware 9550SX-4LP

  • AMCC's 3ware 9550SX-8LP

  • AMCC's 3ware 9550SX-12

  • AMCC's 3ware 9550SX-12MI

  • AMCC's 3ware 9550SX-16ML

  • AMCC's 3ware 9650SE-2LP

  • AMCC's 3ware 9650SE-4LPML

  • AMCC's 3ware 9650SE-8LPML

  • AMCC's 3ware 9650SE-12ML

  • AMCC's 3ware 9650SE-16ML

  • AMCC's 3ware 9650SE-24M8

[i386,amd64] The twe(4) driver supports the following PATA/SATA RAID controllers:

  • AMCC's 3ware 5000 series

  • AMCC's 3ware 6000 series

  • AMCC's 3ware 7000-2

  • AMCC's 3ware 7006-2

  • AMCC's 3ware 7500-4LP

  • AMCC's 3ware 7500-8

  • AMCC's 3ware 7500-12

  • AMCC's 3ware 7506-4LP

  • AMCC's 3ware 7506-8

  • AMCC's 3ware 7506-12

  • AMCC's 3ware 8006-2LP

  • AMCC's 3ware 8500-4LP

  • AMCC's 3ware 8500-8

  • AMCC's 3ware 8500-12

  • AMCC's 3ware 8506-4LP

  • AMCC's 3ware 8506-8

  • AMCC's 3ware 8506-8MI

  • AMCC's 3ware 8506-12

  • AMCC's 3ware 8506-12MI

[i386] The vpo(4) driver supports the following parallel to SCSI interfaces:

  • Adaptec AIC-7110 Parallel to SCSI interface (built-in to Iomega ZIP drives)

  • Iomega Jaz Traveller interface

  • Iomega MatchMaker SCSI interface (built-in to Iomega ZIP+ drives)

[i386] The wds(4) driver supports the WD7000 SCSI controller.

With all supported SCSI controllers, full support is provided for SCSI-I, SCSI-II, and SCSI-III peripherals, including hard disks, optical disks, tape drives (including DAT, 8mm Exabyte, Mammoth, and DLT), medium changers, processor target devices and CD-ROM drives. WORM devices that support CD-ROM commands are supported for read-only access by the CD-ROM drivers (such as cd(4)). WORM/CD-R/CD-RW writing support is provided by cdrecord(1), which is a part of the sysutils/cdrtools port in the Ports Collection.

The following CD-ROM type systems are supported at this time:

  • SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (cd(4))

  • [i386] Sony proprietary interface (all models) ( scd(4))

  • ATAPI IDE interface ( acd(4))

[i386] The following device is unmaintained:

  • Mitsumi proprietary CD-ROM interface (all models) ( mcd(4))

3.2 Ethernet Interfaces

The ae(4) driver supports Attansic/Atheros L2 PCIe FastEthernet controllers, and is known to support the following hardware:

  • ASUS EeePC 701

  • ASUS EeePC 900

Other hardware may or may not work with this driver.

The age(4) driver provides support for LOMs based on Attansic/Atheros L1 Gigabit Ethernet controller chips, including:

  • ASUS M2N8-VMX

  • ASUS M2V

  • ASUS M3A

  • ASUS P2-M2A590G

  • ASUS P5B-E

  • ASUS P5B-MX/WIFI-AP

  • ASUS P5B-VMSE

  • ASUS P5K

  • ASUS P5KC

  • ASUS P5KPL-C

  • ASUS P5KPL-VM

  • ASUS P5K-SE

  • ASUS P5K-V

  • ASUS P5L-MX

  • ASUS P5DL2-VM

  • ASUS P5L-VM 1394

  • ASUS G2S

The ale(4) device driver provides support for the following Ethernet controllers:

  • Atheros AR8113 PCI Express Fast Ethernet controller

  • Atheros AR8114 PCI Express Fast Ethernet controller

  • Atheros AR8121 PCI Express Gigabit Ethernet controller

[i386,pc98,ia64,amd64,powerpc] Adapters supported by the aue(4) driver include:

  • Abocom UFE1000, DSB650TX_NA

  • Accton USB320-EC, SpeedStream

  • ADMtek AN986, AN8511

  • Billionton USB100, USB100LP, USB100EL, USBE100

  • Corega Ether FEther USB-T, FEther USB-TX, FEther USB-TXS

  • D-Link DSB-650, DSB-650TX, DSB-650TX-PNA

  • Elecom LD-USBL/TX

  • Elsa Microlink USB2Ethernet

  • HP hn210e

  • I-O Data USB ETTX

  • Kingston KNU101TX

  • LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, USB100TX, USB100H1

  • MELCO LUA-TX, LUA2-TX

  • Netgear FA101

  • Planex UE-200TX

  • Sandberg USB to Network Link (model number 133-06)

  • Siemens Speedstream

  • SmartBridges smartNIC

  • SMC 2202USB

  • SOHOware NUB100

[i386,pc98,amd64,powerpc] The axe(4) driver supports ASIX Electronics AX88172/AX88178/AX88772/AX88772A/AX88772B/AX88760 based USB Ethernet adapters including:

AX88172:

  • AboCom UF200

  • Acer Communications EP1427X2

  • ASIX AX88172

  • ATen UC210T

  • Billionton SnapPort

  • Billionton USB2AR

  • Buffalo (Melco Inc.) LUA-U2-KTX

  • Corega USB2_TX

  • D-Link DUBE100

  • Goodway GWUSB2E

  • JVC MP_PRX1

  • LinkSys USB200M

  • Netgear FA120

  • Sitecom LN-029

  • System TALKS Inc. SGC-X2UL

AX88178:

  • ASIX AX88178

  • Belkin F5D5055

  • Logitec LAN-GTJ/U2A

  • Buffalo (Melco Inc.) LUA3-U2-AGT

  • Planex Communications GU1000T

  • Sitecom Europe LN-028

AX88772:

  • ASIX AX88772

  • Buffalo (Melco Inc.) LUA3-U2-ATX

  • D-Link DUBE100B1

  • Planex UE-200TX-G

  • Planex UE-200TX-G2

AX88772A:

  • ASIX AX88772A

  • Cisco-Linksys USB200Mv2

AX88772B:

  • ASIX AX88772B

AX88760:

  • ASIX AX88760

[i386,amd64] The bce(4) driver provides support for various NICs based on the Broadcom NetXtreme II family of Gigabit Ethernet controllers, including the following:

  • Broadcom NetXtreme II BCM5706 1000Base-SX

  • Broadcom NetXtreme II BCM5706 1000Base-T

  • Broadcom NetXtreme II BCM5708 1000Base-SX

  • Broadcom NetXtreme II BCM5708 1000Base-T

  • Broadcom NetXtreme II BCM5709 1000Base-SX

  • Broadcom NetXtreme II BCM5709 1000Base-T

  • Broadcom NetXtreme II BCM5716 1000Base-T

  • Dell PowerEdge 1950 integrated BCM5708 NIC

  • Dell PowerEdge 2950 integrated BCM5708 NIC

  • Dell PowerEdge R710 integrated BCM5709 NIC

  • HP NC370F Multifunction Gigabit Server Adapter

  • HP NC370T Multifunction Gigabit Server Adapter

  • HP NC370i Multifunction Gigabit Server Adapter

  • HP NC371i Multifunction Gigabit Server Adapter

  • HP NC373F PCIe Multifunc Giga Server Adapter

  • HP NC373T PCIe Multifunction Gig Server Adapter

  • HP NC373i Multifunction Gigabit Server Adapter

  • HP NC373m Multifunction Gigabit Server Adapter

  • HP NC374m PCIe Multifunction Adapter

  • HP NC380T PCIe DP Multifunc Gig Server Adapter

  • HP NC382T PCIe DP Multifunction Gigabit Server Adapter

  • HP NC382i DP Multifunction Gigabit Server Adapter

  • HP NC382m DP 1GbE Multifunction BL-c Adapter

[amd64, i386] Broadcom BCM4401 based Fast Ethernet adapters ( bfe(4) driver)

[i386,pc98,sparc64,ia64,amd64] The bge(4) driver provides support for various NICs based on the Broadcom BCM570x family of Gigabit Ethernet controller chips, including the following:

  • 3Com 3c996-SX (1000baseSX)

  • 3Com 3c996-T (10/100/1000baseTX)

  • Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX)

  • Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX)

  • Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX)

  • Dell PowerEdge R200 integrated BCM5750 NIC (10/100/1000baseTX)

  • Dell PowerEdge R300 integrated BCM5722 NIC (10/100/1000baseTX)

  • IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX)

  • HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX)

  • HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseTX)

  • HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX)

  • Netgear GA302T (10/100/1000baseTX)

  • SysKonnect SK-9D21 (10/100/1000baseTX)

  • SysKonnect SK-9D41 (1000baseSX)

The chips supported by the cas(4) driver are:

  • National Semiconductor DP83065 Saturn Gigabit Ethernet

  • Sun Cassini Gigabit Ethernet

  • Sun Cassini+ Gigabit Ethernet

The following add-on cards are known to work with the cas(4) driver at this time:

  • Sun GigaSwift Ethernet 1.0 MMF (Cassini Kuheen) (part no. 501-5524)

  • Sun GigaSwift Ethernet 1.0 UTP (Cassini) (part no. 501-5902)

  • Sun GigaSwift Ethernet UTP (GCS) (part no. 501-6719)

  • Sun Quad GigaSwift Ethernet UTP (QGE) (part no. 501-6522)

  • Sun Quad GigaSwift Ethernet PCI-X (QGE-X) (part no. 501-6738)

[i386,pc98,ia64,amd64,powerpc] The following devices are supported by the cdce(4) driver:

  • Prolific PL-2501 Host-to-Host Bridge Controller

  • Sharp Zaurus PDA

  • Terayon TJ-715 DOCSIS Cable Modem

[amd64, i386] Crystal Semiconductor CS89x0-based NICs (cs(4) driver)

[i386,pc98,ia64,amd64,powerpc] The cue(4) driver supports CATC USB-EL1210A based USB Ethernet adapters including:

  • Belkin F5U011/F5U111

  • CATC Netmate

  • CATC Netmate II

  • SmartBridges SmartLink

[i386,amd64] The cxgb(4) driver supports 10 Gigabit and 1 Gigabit Ethernet adapters based on the T3 and T3B chipset:

  • Chelsio 10GBase-CX4

  • Chelsio 10GBase-LR

  • Chelsio 10GBase-SR

The dc(4) driver provides support for the following chipsets:

  • DEC/Intel 21143

  • ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II

  • ALi/ULi M5261 and M5263

  • ASIX Electronics AX88140A and AX88141

  • Conexant LANfinity RS7112 (miniPCI)

  • Davicom DM9009, DM9100, DM9102 and DM9102A

  • Lite-On 82c168 and 82c169 PNIC

  • Lite-On/Macronix 82c115 PNIC II

  • Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732

  • Xircom X3201 (cardbus only)

The following NICs are known to work with the dc(4) driver at this time:

  • 3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P)

  • Abocom FE2500

  • Accton EN1217 (98715A)

  • Accton EN2242 MiniPCI

  • Adico AE310TX (98715A)

  • Alfa Inc GFC2204 (ASIX AX88140A)

  • Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, non-MII)

  • Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, MII)

  • Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII)

  • CNet Pro110B (ASIX AX88140A)

  • CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715)

  • Compex RL100-TX (98713 or 98713A)

  • D-Link DFE-570TX (21143, MII, quad port)

  • Digital DE500-BA 10/100 (21143, non-MII)

  • ELECOM Laneed LD-CBL/TXA (ADMtek AN985)

  • Hawking CB102 CardBus

  • IBM EtherJet Cardbus Adapter

  • Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset)

  • Jaton XpressNet (Davicom DM9102)

  • Kingston KNE100TX (21143, MII)

  • Kingston KNE110TX (PNIC 82c169)

  • LinkSys LNE100TX (PNIC 82c168, 82c169)

  • LinkSys LNE100TX v2.0 (PNIC II 82c115)

  • LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P)

  • Matrox FastNIC 10/100 (PNIC 82c168, 82c169)

  • Melco LGY-PCI-TXL

  • Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C)

  • Microsoft MN-130 10/100 PCI (ADMTek Centaur-P)

  • NDC SOHOware SFA110A (98713A)

  • NDC SOHOware SFA110A Rev B4 (98715AEC-C)

  • NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169)

  • Netgear FA511

  • PlaneX FNW-3602-T (ADMtek AN985)

  • SMC EZ Card 10/100 1233A-TX (ADMtek AN985)

  • SVEC PN102-TX (98713)

  • Xircom Cardbus Realport

  • Xircom Cardbus Ethernet 10/100

  • Xircom Cardbus Ethernet II 10/100

[i386,pc98,ia64,amd64] Adapters supported by the de(4) driver include:

  • Adaptec ANA-6944/TX

  • Cogent EM100FX and EM440TX

  • Corega FastEther PCI-TX

  • D-Link DFE-500TX

  • DEC DE435, DEC DE450, and DEC DE500

  • ELECOM LD-PCI2T, LD-PCITS

  • I-O DATA LA2/T-PCI

  • SMC Etherpower 8432, 9332 and 9334

  • ZNYX ZX3xx

[i386,pc98] The ed(4) driver supports the following Ethernet NICs:

  • 3Com 3c503 Etherlink II

  • AR-P500 Ethernet

  • Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin) (flags 0xd00000)

  • Accton EN2212/EN2216/UE2216

  • Allied Telesis CentreCOM LA100-PCM_V2

  • Allied Telesis LA-98 (flags 0x000000) (PC-98)

  • Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98)

  • Allied Telesis SIU-98-D (flags 0x610000) (PC-98)

  • AmbiCom 10BaseT card

  • Bay Networks NETGEAR FA410TXC Fast Ethernet

  • Belkin F5D5020 PC Card Fast Ethernet

  • Billionton LM5LT-10B Ethernet/Modem PC Card

  • Bromax iPort 10/100 Ethernet PC Card

  • Bromax iPort 10 Ethernet PC Card

  • Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX PC Card

  • CNet BC40 adapter

  • Compex Net-A adapter

  • Compex RL2000

  • Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98)

  • Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98)

  • Corega Ether98-T (flags 0x000000) (PC-98)

  • Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD PCC-T/Fether II TXD

  • Corega LAPCCTXD (TC5299J)

  • CyQ've ELA-010

  • DEC EtherWorks DE305

  • Danpex EN-6200P2

  • D-Link DE-298, DE-298P (flags 0x500000) (PC-98)

  • D-Link DE-660, DE-660+

  • D-Link IC-CARD/IC-CARD+ Ethernet

  • ELECOM LD-98P (flags 0x500000) (PC-98)

  • ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98)

  • ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A)

  • Hawking PN652TX PC Card (AX88790)

  • HP PC Lan+ 27247B and 27252A

  • IBM Creditcard Ethernet I/II

  • ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin) (flags 0x500000) (PC-98)

  • I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98)

  • I-O DATA ET2/T-PCI

  • I-O DATA PCLATE

  • Kansai KLA-98C/T (flags 0x900000) (PC-98)

  • Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet

  • KTI ET32P2 PCI

  • Linksys EC2T/PCMPC100/PCM100, PCMLM56

  • Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2)

  • Logitec LAN-98T (flags 0xb00000) (PC-98)

  • MACNICA Ethernet ME1 for JEIDA

  • MACNICA ME98 (flags 0x900000) (PC-98)

  • MACNICA NE2098 (flags 0x400000) (PC-98)

  • MELCO EGY-98 (flags 0x300000) (PC-98)

  • MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98)

  • MELCO LGY-PCI-TR

  • MELCO LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX

  • NDC Ethernet Instant-Link

  • NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98)

  • NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98)

  • National Semiconductor InfoMover NE4100

  • NetGear FA-410TX

  • NetVin NV5000SC

  • Network Everywhere Ethernet 10BaseT PC Card

  • Networld 98X3 (flags 0xd00000) (PC-98)

  • Networld EC-98X, EP-98X (flags 0xd10000) (PC-98)

  • New Media LANSurfer 10+56 Ethernet/Modem

  • New Media LANSurfer

  • Novell NE1000/NE2000/NE2100

  • PLANEX ENW-8300-T

  • PLANEX EN-2298-C (flags 0x200000) (PC-98)

  • PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98)

  • PLANEX FNW-3600-T

  • Psion 10/100 LANGLOBAL Combine iT

  • RealTek 8019

  • RealTek 8029

  • Relia Combo-L/M-56k PC Card

  • SMC Elite 16 WD8013

  • SMC Elite Ultra

  • SMC EtherEZ98 (flags 0x000000) (PC-98)

  • SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones

  • SMC EZCard PC Card, 8040-TX, 8041-TX (AX88x90), 8041-TX V.2 (TC5299J)

  • Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF

  • Surecom EtherPerfect EP-427

  • Surecom NE-34

  • TDK 3000/3400/5670 Fast Ethernet/Modem

  • TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card

  • TDK DFL5610WS Ethernet/Modem PC Card

  • Telecom Device SuperSocket RE450T

  • Toshiba LANCT00A PC Card

  • VIA VT86C926

  • Winbond W89C940

  • Winbond W89C940F

C-Bus, ISA, PCI and PC Card devices are supported.

The ed(4) driver does not support the following Ethernet NICs:

  • Mitsubishi LAN Adapter B8895

The em(4) driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips:

  • Intel PRO/1000 CT Network Connection (82547)

  • Intel PRO/1000 F Server Adapter (82543)

  • Intel PRO/1000 Gigabit Server Adapter (82542)

  • Intel PRO/1000 GT Desktop Adapter (82541PI)

  • Intel PRO/1000 MF Dual Port Server Adapter (82546)

  • Intel PRO/1000 MF Server Adapter (82545)

  • Intel PRO/1000 MF Server Adapter (LX) (82545)

  • Intel PRO/1000 MT Desktop Adapter (82540)

  • Intel PRO/1000 MT Desktop Adapter (82541)

  • Intel PRO/1000 MT Dual Port Server Adapter (82546)

  • Intel PRO/1000 MT Quad Port Server Adapter (82546EB)

  • Intel PRO/1000 MT Server Adapter (82545)

  • Intel PRO/1000 PF Dual Port Server Adapter (82571)

  • Intel PRO/1000 PF Quad Port Server Adapter (82571)

  • Intel PRO/1000 PF Server Adapter (82572)

  • Intel PRO/1000 PT Desktop Adapter (82572)

  • Intel PRO/1000 PT Dual Port Server Adapter (82571)

  • Intel PRO/1000 PT Quad Port Server Adapter (82571)

  • Intel PRO/1000 PT Server Adapter (82572)

  • Intel PRO/1000 T Desktop Adapter (82544)

  • Intel PRO/1000 T Server Adapter (82543)

  • Intel PRO/1000 XF Server Adapter (82544)

  • Intel PRO/1000 XT Server Adapter (82544)

[i386,pc98,amd64] The ep(4) driver supports Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, including:

  • 3Com 3C1 CF

  • 3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA

  • 3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA

  • 3Com 3C529, 3C529-TP MCA

  • 3Com 3C562/3C563 PCMCIA

  • 3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS

  • 3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA

  • 3Com 3C579-TP, 3C579-BNC EISA

  • 3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA

  • 3Com 3CCFEM556B, 3CCFEM556BI PCMCIA

  • 3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA

  • 3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA

  • 3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA

  • Farallon EtherWave and EtherMac PC Card (P/n 595/895 with BLUE arrow)

[i386,amd64] The ex(4) driver supports the following Ethernet adapters:

  • Intel EtherExpress Pro/10 ISA

  • Intel EtherExpress Pro/10+ ISA

  • Olicom OC2220 Ethernet PC Card

  • Olicom OC2232 Ethernet/Modem PC Card

  • Silicom Ethernet LAN PC Card

  • Silicom EtherSerial LAN PC Card

[i386,pc98,amd64] Controllers and cards supported by the fe(4) driver include:

  • Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)

  • CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)

  • CONTEC C-NET(PC)C PC Card Ethernet

  • Eagle Tech NE200T

  • Eiger Labs EPX-10BT

  • Fujitsu FMV-J182, FMV-J182A

  • Fujitsu MB86960A, MB86965A

  • Fujitsu MBH10303, MBH10302 PC Card Ethernet

  • Fujitsu Towa LA501 Ethernet

  • HITACHI HT-4840-11 PC Card Ethernet

  • NextCom J Link NC5310

  • RATOC REX-5588, REX-9822, REX-4886, and REX-R280

  • RATOC REX-9880/9881/9882/9883

  • TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)

  • TDK LAK-CD011, LAK-CD021, LAK-CD021A, LAK-CD021BX

  • Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) (110-pin)

Adapters supported by the fxp(4) driver include:

  • Intel EtherExpress PRO/10

  • Intel InBusiness 10/100

  • Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter

  • Intel PRO/100+ Management Adapter

  • Intel PRO/100 VE Desktop Adapter

  • Intel PRO/100 VM Network Connection

  • Intel PRO/100 M Desktop Adapter

  • Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters

  • Contec C-NET(PI)-100TX (PC-98)

  • NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98)

  • NEC PC-9821X-B06 (PC-98)

  • Many on-board network interfaces on Intel motherboards

Chips supported by the gem(4) driver include:

  • Apple GMAC

  • Sun ERI 10/100 Mbps Ethernet

  • Sun GEM Gigabit Ethernet

The following add-on cards are known to work with the gem(4) driver at this time:

  • Sun Gigabit Ethernet PCI 2.0/3.0 (GBE/P) (part no. 501-4373)

  • Sun Gigabit Ethernet SBus 2.0/3.0 (GBE/S) (part no. 501-4375)

The hme(4) driver supports the on-board Ethernet interfaces of many Sun UltraSPARC workstation and server models.

Cards supported by the hme(4) driver include:

  • Sun PCI SunSwift Adapter

  • Sun SBus SunSwift Adapter “( hme” and “SUNW,hme”)

  • Sun PCI Sun100BaseT Adapter 2.0

  • Sun SBus Sun100BaseT 2.0

  • Sun PCI Quad FastEthernet Controller

  • Sun SBus Quad FastEthernet Controller

[i386] The ie(4) driver provides supports the following 8 and 16bit ISA Ethernet cards that are based on the Intel i82586 chip:

  • 3COM 3C507

  • AT&T EN100

  • AT&T Starlan 10

  • AT&T Starlan Fiber

  • Intel EtherExpress 16

  • RACAL Interlan NI5210

The igb(4) driver supports Gigabit Ethernet adapters based on the Intel 82575 and 82576 controller chips:

  • Intel Gigabit ET Dual Port Server Adapter (82576)

  • Intel Gigabit VT Quad Port Server Adapter (82575)

[i386,amd64] The ixgb(4) driver supports the following cards:

  • Intel PRO/10GbE LR Server Adapter

  • Intel PRO/10GbE SR Server Adapter

The ixgbe(4) driver supports the following cards:

  • Intel(R) 10 Gigabit XF SR/AF Dual Port Server Adapter

  • Intel(R) 10 Gigabit XF SR/LR Server Adapter

  • Intel(R) 82598EB 10 Gigabit AF Network Connection

  • Intel(R) 82598EB 10 Gigabit AT CX4 Network Connection

The jme(4) device driver provides support for the following Ethernet controllers:

  • JMicron JMC250 PCI Express Gigabit Ethernet controller

  • JMicron JMC251 PCI Express Gigabit Ethernet with Card Read Host controller

  • JMicron JMC260 PCI Express Fast Ethernet controller

  • JMicron JMC261 PCI Express Gigabit Ethernet with Card Read Host controller

[i386,pc98,ia64,amd64,powerpc] The kue(4) driver supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:

  • 3Com 3c19250

  • 3Com 3c460 HomeConnect Ethernet USB Adapter

  • ADS Technologies USB-10BT

  • AOX USB101

  • ATen UC10T

  • Abocom URE 450

  • Corega USB-T

  • D-Link DSB-650C

  • Entrega NET-USB-E45, NET-HUB-3U1E

  • I/O Data USB ETT

  • Kawasaki DU-H3E

  • LinkSys USB10T

  • Netgear EA101

  • Peracom USB Ethernet Adapter

  • Psion Gold Port USB Ethernet adapter

  • SMC 2102USB, 2104USB

[i386,pc98,amd64] Adapters supported by the lge(4) driver include:

  • SMC TigerCard 1000 (SMC9462SX)

  • D-Link DGE-500SX

[i386,amd64] The msk(4) driver provides support for various NICs based on the Marvell/SysKonnect Yukon II based Gigabit Ethernet controller chips, including:

  • D-Link 550SX Gigabit Ethernet

  • D-Link 560SX Gigabit Ethernet

  • D-Link 560T Gigabit Ethernet

  • Marvell Yukon 88E8021CU Gigabit Ethernet

  • Marvell Yukon 88E8021 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8022CU Gigabit Ethernet

  • Marvell Yukon 88E8022 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8061CU Gigabit Ethernet

  • Marvell Yukon 88E8061 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8062CU Gigabit Ethernet

  • Marvell Yukon 88E8062 SX/LX Gigabit Ethernet

  • Marvell Yukon 88E8035 Fast Ethernet

  • Marvell Yukon 88E8036 Fast Ethernet

  • Marvell Yukon 88E8038 Fast Ethernet

  • Marvell Yukon 88E8039 Fast Ethernet

  • Marvell Yukon 88E8040 Fast Ethernet

  • Marvell Yukon 88E8040T Fast Ethernet

  • Marvell Yukon 88E8042 Fast Ethernet

  • Marvell Yukon 88E8048 Fast Ethernet

  • Marvell Yukon 88E8050 Gigabit Ethernet

  • Marvell Yukon 88E8052 Gigabit Ethernet

  • Marvell Yukon 88E8053 Gigabit Ethernet

  • Marvell Yukon 88E8055 Gigabit Ethernet

  • Marvell Yukon 88E8056 Gigabit Ethernet

  • Marvell Yukon 88E8057 Gigabit Ethernet

  • Marvell Yukon 88E8058 Gigabit Ethernet

  • Marvell Yukon 88E8059 Gigabit Ethernet

  • Marvell Yukon 88E8070 Gigabit Ethernet

  • Marvell Yukon 88E8071 Gigabit Ethernet

  • Marvell Yukon 88E8072 Gigabit Ethernet

  • Marvell Yukon 88E8075 Gigabit Ethernet

  • SysKonnect SK-9Sxx Gigabit Ethernet

  • SysKonnect SK-9Exx Gigabit Ethernet

[i386,amd64] The mxge(4) driver supports 10 Gigabit Ethernet adapters based on the Myricom LANai Z8E chips:

  • Myricom 10GBase-CX4 (10G-PCIE-8A-C, 10G-PCIE-8AL-C)

  • Myricom 10GBase-R (10G-PCIE-8A-R, 10G-PCIE-8AL-R)

  • Myricom 10G XAUI over ribbon fiber (10G-PCIE-8A-Q, 10G-PCIE-8AL-Q)

[i386,pc98] The my(4) driver provides support for various NICs based on the Myson chipset. Supported models include:

  • Myson MTD800 PCI Fast Ethernet chip

  • Myson MTD803 PCI Fast Ethernet chip

  • Myson MTD89X PCI Gigabit Ethernet chip

[i386,amd64] The nfe(4) driver supports the following NVIDIA MCP onboard adapters:

  • NVIDIA nForce MCP Networking Adapter

  • NVIDIA nForce MCP04 Networking Adapter

  • NVIDIA nForce 430 MCP12 Networking Adapter

  • NVIDIA nForce 430 MCP13 Networking Adapter

  • NVIDIA nForce MCP51 Networking Adapter

  • NVIDIA nForce MCP55 Networking Adapter

  • NVIDIA nForce MCP61 Networking Adapter

  • NVIDIA nForce MCP65 Networking Adapter

  • NVIDIA nForce MCP67 Networking Adapter

  • NVIDIA nForce MCP73 Networking Adapter

  • NVIDIA nForce MCP77 Networking Adapter

  • NVIDIA nForce MCP79 Networking Adapter

  • NVIDIA nForce2 MCP2 Networking Adapter

  • NVIDIA nForce2 400 MCP4 Networking Adapter

  • NVIDIA nForce2 400 MCP5 Networking Adapter

  • NVIDIA nForce3 MCP3 Networking Adapter

  • NVIDIA nForce3 250 MCP6 Networking Adapter

  • NVIDIA nForce3 MCP7 Networking Adapter

  • NVIDIA nForce4 CK804 MCP8 Networking Adapter

  • NVIDIA nForce4 CK804 MCP9 Networking Adapter

The nge(4) driver supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters including:

  • Addtron AEG320T

  • Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI)

  • Asante FriendlyNet GigaNIX 1000TA and 1000TPC

  • D-Link DGE-500T

  • Linksys EG1032, revision 1

  • Netgear GA621

  • Netgear GA622T

  • SMC EZ Card 1000 (SMC9462TX)

  • Surecom Technology EP-320G-TX

  • Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI)

[i386,amd64] The nve(4) driver supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:

  • nForce

  • nForce2

  • nForce3

  • nForce4

[i386,amd64] The nxge(4) driver supports Neterion Xframe 10 Gigabit Ethernet adapters listed in http://www.neterion.com/how/pricing.html.

[i386,amd64] The oce(4) driver supports the following network adapters:

  • Emulex BladeEngine 2

  • Emulex BladeEngine 3

  • Emulex Lancer

[i386,pc98,ia64,amd64] The pcn(4) driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:

  • AMD Am79C971 PCnet-FAST

  • AMD Am79C972 PCnet-FAST+

  • AMD Am79C973/Am79C975 PCnet-FAST III

  • AMD Am79C976 PCnet-PRO

  • AMD Am79C978 PCnet-Home

  • Allied-Telesis LA-PCI

The re(4) driver supports RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, RTL8168, RTL810xE and RTL8111 based Fast Ethernet and Gigabit Ethernet adapters including:

  • Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)

  • Compaq Evo N1015v Integrated Ethernet (8139C+)

  • Corega CG-LAPCIGT Gigabit Ethernet (8169S)

  • D-Link DGE-528(T) Gigabit Ethernet (8169S)

  • Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)

  • LevelOne GNC-0105T (8169S)

  • LinkSys EG1032 (32-bit PCI)

  • PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)

  • USRobotics USR997902 Gigabit Ethernet (8169S)

  • Xterasys XN-152 10/100/1000 NIC (8169)

Adapters supported by the rl(4) driver include:

  • Accton “Cheetah” EN1207D (MPX 5030/5038; RealTek 8139 clone)

  • Allied Telesyn AT2550

  • Allied Telesyn AT2500TX

  • Belkin F5D5000

  • BUFFALO (Melco INC.) LPC-CB-CLX (CardBus)

  • Compaq HNE-300

  • CompUSA no-name 10/100 PCI Ethernet NIC

  • Corega FEther CB-TXD

  • Corega FEtherII CB-TXD

  • D-Link DFE-520TX (rev. C1)

  • D-Link DFE-528TX

  • D-Link DFE-530TX+

  • D-Link DFE-538TX

  • D-Link DFE-690TXD

  • Edimax EP-4103DL CardBus

  • Encore ENL832-TX 10/100 M PCI

  • Farallon NetLINE 10/100 PCI

  • Genius GF100TXR

  • GigaFast Ethernet EE100-AXP

  • KTX-9130TX 10/100 Fast Ethernet

  • LevelOne FPC-0106TX

  • Longshine LCS-8038TX-R

  • NDC Communications NE100TX-E

  • Netronix Inc. EA-1210 NetEther 10/100

  • Nortel Networks 10/100BaseTX

  • OvisLink LEF-8129TX

  • OvisLink LEF-8139TX

  • Peppercon AG ROL-F

  • Planex FNW-3603-TX

  • Planex FNW-3800-TX

  • SMC EZ Card 10/100 PCI 1211-TX

  • SOHO (PRAGMATIC) UE-1211C

[i386,pc98,amd64] The rue(4) driver supports RealTek RTL8150 based USB Ethernet adapters including:

  • Buffalo (Melco Inc.) LUA-KTX

  • Green House GH-USB100B

  • LinkSys USB100M

  • Billionton 10/100 FastEthernet USBKR2

Adapters supported by the sf(4) driver include:

  • ANA-62011 64-bit single port 10/100baseTX adapter

  • ANA-62022 64-bit dual port 10/100baseTX adapter

  • ANA-62044 64-bit quad port 10/100baseTX adapter

  • ANA-69011 32-bit single port 10/100baseTX adapter

  • ANA-62020 64-bit single port 100baseFX adapter

[i386,pc98,ia64,amd64] The sis(4) driver supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and embedded controllers, as well as Fast Ethernet adapters based on the National Semiconductor DP83815 (MacPhyter) and DP83816 chips. Supported adapters include:

  • @Nifty FNECHARD IFC USUP-TX

  • MELCO LGY-PCI-TXC

  • Netgear FA311-TX (DP83815)

  • Netgear FA312-TX (DP83815)

  • SiS 630, 635, and 735 motherboard chipsets

  • Soekris Engineering net45xx, net48xx, lan1621, and lan1641

[i386,sparc64,pc98,amd64] Adapters supported by the sk(4) driver include:

  • 3Com 3C940 single port, 1000baseT adapter

  • 3Com 3C2000-T single port, 1000baseT adapter

  • Belkin F5D5005 single port, 1000baseT adapter

  • D-Link DGE-530T single port, 1000baseT adapter

  • Linksys (revision 2) single port, 1000baseT adapter

  • SK-9521 SK-NET GE-T single port, 1000baseT adapter

  • SK-9821 SK-NET GE-T single port, 1000baseT adapter

  • SK-9822 SK-NET GE-T dual port, 1000baseT adapter

  • SK-9841 SK-NET GE-LX single port, single mode fiber adapter

  • SK-9842 SK-NET GE-LX dual port, single mode fiber adapter

  • SK-9843 SK-NET GE-SX single port, multimode fiber adapter

  • SK-9844 SK-NET GE-SX dual port, multimode fiber adapter

  • SMC 9452TX single port, 1000baseT adapter

[i386,amd64] The sn(4) driver supports SMC91Cxx based ISA and PCMCIA cards including:

  • 3Com Megahertz X-Jack Ethernet PC Card XJ10BT, XJ10BC

  • 3Com Megahertz XJEM and CCEM series: CCEM3288C, CCEM3288T, CCEM3336, CEM3336C, CCEM3336T, XJEM1144C, XJEM1144T, XJEM3288C, XJEM3288T, XJEM3336

  • Farallon EtherMac PC Card 595a

  • Motorola Mariner Ethernet/Modem PC Card

  • Ositech Seven of Diamonds Ethernet PC Card

  • Ositech Jack of Hearts Ethernet/Modem PC Card

  • Psion Gold Card Netglobal Ethernet PC Card

  • Psion Gold Card Netglobal 10/100 Fast Ethernet PC Card

  • Psion Gold Card Netglobal 56k+10Mb Ethernet PC Card

  • SMC EZEther PC Card (8020BT)

  • SMC EZEther PC Card (8020T)

The sn(4) driver supports the SMC 91C90, SMC 91C92, SMC 91C94, SMC 91C95, SMC 91C96, SMC91C100 and SMC 91C100FD chips from SMC.

The Farallon EtherWave and EtherMac card came in two varieties. The ep(4) driver supports the 595 and 895 cards. These cards have the blue arrow on the front along with a 3Com logo. The Farallon 595a cards, which have a red arrow on the front, are also called EtherWave and EtherMac. They are supported by the sn(4) driver.

[pc98] The snc(4) driver supports the following cards:

  • National Semiconductor DP83934AVQB

  • NEC PC-9801-83

  • NEC PC-9801-84

  • NEC PC-9801-103

  • NEC PC-9801-104

  • NEC PC-9801N-15

  • NEC PC-9801N-25

  • NEC PC-9801N-J02 PCMCIA

  • NEC PC-9801N-J02R PCMCIA

The snc(4) driver also includes support for the National Semiconductor NS46C46 as 64 * 16 bits Microwave Serial EEPROM.

[i386,pc98,amd64] The ste(4) driver supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded controllers including:

  • D-Link DFE-530TXS

  • D-Link DFE-550TX

  • D-Link DFE-580TX

[i386,amd64,sparc64] The stge(4) driver provides support for various NICs based on the Sundance/Tamarack TC9021 based Gigabit Ethernet controller chips, including:

  • Antares Microsystems Gigabit Ethernet

  • ASUS NX1101 Gigabit Ethernet

  • D-Link DL-4000 Gigabit Ethernet

  • IC Plus IP1000A Gigabit Ethernet

  • Sundance ST-2021 Gigabit Ethernet

  • Sundance ST-2023 Gigabit Ethernet

  • Sundance TC9021 Gigabit Ethernet

  • Tamarack TC9021 Gigabit Ethernet

[i386,pc98,amd64,sparc64] The ti(4) driver supports Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The ti(4) driver has been tested with the following adapters:

  • 3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1)

  • 3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2)

  • Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX)

  • Alteon AceNIC V Gigabit Ethernet adapter (1000baseT)

  • Digital EtherWORKS 1000SX PCI Gigabit adapter

  • Netgear GA620 Gigabit Ethernet adapter (1000baseSX)

  • Netgear GA620T Gigabit Ethernet adapter (1000baseT)

The following adapters should also be supported but have not yet been tested:

  • Asante GigaNIX1000T Gigabit Ethernet adapter

  • Asante PCI 1000BASE-SX Gigabit Ethernet adapter

  • Farallon PN9000SX Gigabit Ethernet adapter

  • NEC Gigabit Ethernet

  • Silicon Graphics PCI Gigabit Ethernet adapter

[i386,pc98,amd64] The tl(4) driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet adapters. Also supported are:

  • Olicom OC-2135/2138 10/100 TX UTP adapter

  • Olicom OC-2325/OC-2326 10/100 TX UTP adapter

  • Racore 8148 10baseT/100baseTX/100baseFX adapter

  • Racore 8165 10/100baseTX adapter

The tl(4) driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including:

  • Compaq Netelligent 10

  • Compaq Netelligent 10 T PCI UTP/Coax

  • Compaq Netelligent 10/100

  • Compaq Netelligent 10/100 Dual-Port

  • Compaq Netelligent 10/100 Proliant

  • Compaq Netelligent 10/100 TX Embedded UTP

  • Compaq Netelligent 10/100 TX UTP

  • Compaq NetFlex 3P

  • Compaq NetFlex 3P Integrated

  • Compaq NetFlex 3P w/BNC

[amd64, i386, pc98] SMC 83c17x (EPIC)-based Ethernet NICs (tx(4) driver)

The txp(4) driver supports the following cards:

  • 3Com 3CR990-TX-95

  • 3Com 3CR990-TX-97

  • 3Com 3cR990B-TXM

  • 3Com 3CR990SVR95

  • 3Com 3CR990SVR97

  • 3Com 3cR990B-SRV

[i386,pc98,amd64] The udav(4) driver supports the following adapters:

  • Corega FEther USB-TXC

  • ShanTou ST268 USB NIC

[i386,pc98,amd64] The vge(4) driver supports VIA Networking VT6120, VT6122, VT6130 and VT6132 based Gigabit Ethernet adapters including:

  • VIA Networking LAN-on-motherboard Gigabit Ethernet

  • ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)

  • ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)

The vr(4) driver supports VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters including:

  • AOpen/Acer ALN-320

  • D-Link DFE520-TX

  • D-Link DFE530-TX

  • Hawking Technologies PN102TX

  • Soekris Engineering net5501

[i386,pc98,ia64,amd64] The vx(4) driver supports the following cards:

  • 3Com 3c590 EtherLink III PCI

  • 3Com 3c592 EtherLink III EISA

  • 3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode

  • 3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode

[i386,pc98,amd64] The wb(4) driver supports Winbond W89C840F based Fast Ethernet adapters and embedded controllers including:

  • Trendware TE100-PCIE

[i386,amd64] The xe(4) driver supports the following cards:

  • Xircom CreditCard Ethernet (PS-CE2-10)

  • Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28)

  • Xircom CreditCard Ethernet + Modem 33 (CEM33)

  • Xircom CreditCard 10/100 (CE3, CE3B)

  • Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56)

  • Xircom RealPort Ethernet 10 (RE10)

  • Xircom RealPort Ethernet 10/100 (RE100)

  • Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G)

  • Accton Fast EtherCard-16 (EN2226)

  • Compaq Microcom CPQ550 Ethernet/Modem PC Card

  • Compaq Netelligent 10/100 PC Card (CPQ-10/100)

  • Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A)

  • Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B)

Other similar devices using the same hardware may also be supported.

The xl(4) driver supports the following hardware:

  • 3Com 3c900-TPO

  • 3Com 3c900-COMBO

  • 3Com 3c905-TX

  • 3Com 3c905-T4

  • 3Com 3c900B-TPO

  • 3Com 3c900B-TPC

  • 3Com 3c900B-FL

  • 3Com 3c900B-COMBO

  • 3Com 3c905B-T4

  • 3Com 3c905B-TX

  • 3Com 3c905B-FX

  • 3Com 3c905B-COMBO

  • 3Com 3c905C-TX

  • 3Com 3c980, 3c980B, and 3c980C server adapters

  • 3Com 3cSOHO100-TX OfficeConnect adapters

  • 3Com 3c450 HomeConnect adapters

  • 3Com 3c555, 3c556 and 3c556B mini-PCI adapters

  • 3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, 3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters

  • 3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded adapters

Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a built-in proprietary modem. Neither the xl(4) driver nor any other FreeBSD driver supports this modem.

3.3 FDDI Interfaces

[i386, pc98] DEC DEFPA PCI ( fpa(4) driver)

[i386] DEC DEFEA EISA ( fpa(4) driver)

3.4 ATM Interfaces

[i386, pc98] Midway-based ATM interfaces (en(4) driver)

[i386, pc98 sparc64] FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa and fatm(4) drivers)

[i386, pc98] IDT NICStAR 77201/211-based ATM Adapters ( idt(4) driver)

[i386, pc98 sparc64] FORE Systems, Inc. HE155 and HE622 ATM interfaces ( hatm(4) driver)

[i386, pc98] IDT77252-based ATM cards ( patm(4) driver)

3.5 Wireless Network Interfaces

[amd64, i386, pc98] Cisco/Aironet 802.11b wireless adapters (an(4) driver)

[i386,pc98,amd64,sparc64] The ath(4) driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset.

The bwi(4) driver supports Broadcom BCM43xx based wireless devices, including:

  • Apple Airport Extreme

  • Apple Airport Extreme

  • ASUS WL-138g

  • Buffalo WLI-CB-G54S

  • Buffalo WLI-PCI-G54S

  • Compaq R4035 onboard

  • Dell Wireless 1470

  • Dell Truemobile 1400

  • HP nx6125

  • Linksys WPC54G Ver 3

  • Linksys WPC54GS Ver 2

  • TRENDnet TEW-401PCplus

  • US Robotics 5411

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter ( ipw(4) driver)

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters ( iwi(4) driver)

[i386, amd64] Intel Wireless WiFi Link 4965AGN IEEE 802.11n PCI network adapters ( iwn(4) driver)

[i386, amd64] Marvell Libertas IEEE 802.11b/g PCI network adapters ( malo(4) driver)

[i386,amd64] The ral(4) driver supports PCI/PCIe/CardBus wireless adapters based on Ralink Technology chipsets, including:

  • A-Link WL54H

  • A-Link WL54PC

  • AirLink101 AWLC5025

  • AirLink101 AWLH5025

  • Amigo AWI-914W

  • Amigo AWI-922W

  • Amigo AWI-926W

  • AMIT WL531C

  • AMIT WL531P

  • AOpen AOI-831

  • ASUS WL-107G

  • ASUS WL-130g

  • Atlantis Land A02-PCI-W54

  • Atlantis Land A02-PCM-W54

  • Belkin F5D7000 v3

  • Belkin F5D7010 v2

  • Billionton MIWLGRL

  • Canyon CN-WF511

  • Canyon CN-WF513

  • CC&C WL-2102

  • CNet CWC-854

  • CNet CWP-854

  • Compex WL54G

  • Compex WLP54G

  • Conceptronic C54RC

  • Conceptronic C54Ri

  • Digitus DN-7001G-RA

  • Digitus DN-7006G-RA

  • E-Tech WGPC02

  • E-Tech WGPI02

  • Edimax EW-7108PCg

  • Edimax EW-7128g

  • Eminent EM3036

  • Eminent EM3037

  • Encore ENLWI-G-RLAM

  • Encore ENPWI-G-RLAM

  • Fiberline WL-400P

  • Fibreline WL-400X

  • Gigabyte GN-WI01GS

  • Gigabyte GN-WIKG

  • Gigabyte GN-WMKG

  • Gigabyte GN-WP01GS

  • Gigabyte GN-WPKG

  • Hawking HWC54GR

  • Hawking HWP54GR

  • iNexQ CR054g-009 (R03)

  • JAHT WN-4054P

  • JAHT WN-4054PCI

  • LevelOne WNC-0301 v2

  • LevelOne WPC-0301 v2

  • Linksys WMP54G v4

  • Micronet SP906GK

  • Micronet SP908GK V3

  • Minitar MN54GCB-R

  • Minitar MN54GPC-R

  • MSI CB54G2

  • MSI MP54G2

  • MSI PC54G2

  • OvisLink EVO-W54PCI

  • PheeNet HWL-PCIG/RA

  • Pro-Nets CB80211G

  • Pro-Nets PC80211G

  • Repotec RP-WB7108

  • Repotec RP-WP0854

  • SATech SN-54C

  • SATech SN-54P

  • Sitecom WL-112

  • Sitecom WL-115

  • SMC SMCWCB-GM

  • SMC SMCWPCI-GM

  • SparkLAN WL-685R

  • Surecom EP-9321-g

  • Surecom EP-9321-g1

  • Surecom EP-9428-g

  • Sweex LC500050

  • Sweex LC700030

  • TekComm NE-9321-g

  • TekComm NE-9428-g

  • Unex CR054g-R02

  • Unex MR054g-R02

  • Zinwell ZWX-G160

  • Zinwell ZWX-G360

  • Zinwell ZWX-G361

  • Zonet ZEW1500

  • Zonet ZEW1600

[i386,amd64] The rum(4) driver supports USB 2.0 wireless adapters based on the Ralink RT2501USB and RT2601USB chipsets, including:

  • 3Com Aolynk WUB320g

  • Abocom WUG2700

  • Airlink101 AWLL5025

  • ASUS WL-167g ver 2

  • Belkin F5D7050 ver 3

  • Belkin F5D9050 ver 3

  • Buffalo WLI-U2-SG54HP

  • Buffalo WLI-U2-SG54HG

  • Buffalo WLI-U2-G54HP

  • Buffalo WLI-UC-G

  • CNet CWD-854 ver F

  • Conceptronic C54RU ver 2

  • Corega CG-WLUSB2GO

  • D-Link DWA-110

  • D-Link DWA-111

  • D-Link DWL-G122 rev C1

  • D-Link WUA-1340

  • Digitus DN-7003GR

  • Edimax EW-7318USG

  • Gigabyte GN-WB01GS

  • Gigabyte GN-WI05GS

  • Hawking HWUG1

  • Hawking HWU54DM

  • Hercules HWGUSB2-54-LB

  • Hercules HWGUSB2-54V2-AP

  • LevelOne WNC-0301USB v3

  • Linksys WUSB54G rev C

  • Linksys WUSB54GR

  • Planex GW-US54HP

  • Planex GW-US54Mini2

  • Planex GW-USMM

  • Senao NUB-3701

  • Sitecom WL-113 ver 2

  • Sitecom WL-172

  • Sweex LW053

  • TP-LINK TL-WN321G

The uath(4) driver should work with the following adapters:

  • Li Compex WLU108AG

  • Li Compex WLU108G

  • Li D-Link DWL-G132

  • Li IODATA WN-G54/US

  • Li MELCO WLI-U2-KAMG54

  • Li Netgear WG111T

  • Li Netgear WG111U

  • Li Netgear WPN111

  • Li Olitec 000544

  • Li PLANET WDL-U357

  • Li Siemens Gigaset 108

  • Li SMC SMCWUSBT-G

  • Li SMC SMCWUSBT-G2

  • Li SparkLAN WL-785A

  • Li TP-Link TL-WN620G

  • Li TRENDware International TEW-444UB

  • Li TRENDware International TEW-504UB

  • Li Unex Technology UR054ag

  • Li ZyXEL XtremeMIMO M-202

An up to date list can be found at http://customerproducts.atheros.com/customerproducts/default.asp.

The upgt(4) driver supports USB 2.0 Conexant/Intersil PrismGT series wireless adapters based on the GW3887 chipset, among them:

  • Belkin F5D7050 (version 1000)

  • Cohiba Proto Board

  • D-Link DWL-G120 Cohiba

  • FSC Connect2Air E-5400 USB D1700

  • Gigaset USB Adapter 54

  • Inventel UR045G

  • SMC EZ ConnectG SMC2862W-G

  • Sagem XG703A

  • Spinnaker DUT

  • Spinnaker Proto Board

[i386,amd64] The ural(4) driver supports USB 2.0 wireless adapters based on the Ralink Technology RT2500USB chipset, including:

  • AMIT WL532U

  • ASUS WL-167g

  • Belkin F5D7050 v2000

  • Buffalo WLI-U2-KG54-AI

  • CNet CWD-854

  • Compex WLU54G 2A1100

  • Conceptronic C54RU

  • D-Link DWL-G122 b1

  • Dynalink WLG25USB

  • E-Tech WGUS02

  • Gigabyte GN-WBKG

  • Hercules HWGUSB2-54

  • KCORP LifeStyle KLS-685

  • Linksys WUSB54G v4

  • Linksys WUSB54GP v4

  • MSI MS-6861

  • MSI MS-6865

  • MSI MS-6869

  • NovaTech NV-902

  • OvisLink Evo-W54USB

  • SerComm UB801R

  • SparkLAN WL-685R

  • Surecom EP-9001-g

  • Sweex LC100060

  • Tonze UW-6200C

  • Zinwell ZWX-G261

  • Zonet ZEW2500P

An up to date list can be found at http://ralink.rapla.net/.

The urtw(4) driver supports Realtek RTL8187B/L based wireless network devices, including:

  • Belkin F5D7050E

  • Linksys WUSB54GCv2

  • Netgear WG111v2

  • Netgear WG111v3

  • Safehome WLG-1500SMA5

  • Shuttle XPC Accessory PN20

  • Sitecom WL168v1

  • Sitecom WL168v4

  • SureCom EP-9001-g(2A)

  • TRENDnet TEW-424UB V3.xR

[amd64, i386, pc98] Lucent Technologies WaveLAN/IEEE 802.11b wireless network adapters and workalikes using the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24 chipsets (wi(4) driver)

[i386] NCR / AT&T / Lucent Technologies WaveLan T1-speed ISA/radio LAN cards (wl(4) driver)

[i386, amd64] Intel PRO/Wireless 3945ABG MiniPCI network adapters ( wpi(4) driver)

[i386,amd64] The following devices are known to be supported by the zyd(4) driver:

  • 3COM 3CRUSB10075

  • Acer WLAN-G-US1

  • Airlink+ AWLL3025

  • Airlink 101 AWLL3026

  • AOpen 802.11g WL54

  • Asus A9T integrated wireless

  • Asus WL-159g

  • Belkin F5D7050 v.4000

  • Billion BiPAC 3011G

  • Buffalo WLI-U2-KG54L

  • CC&C WL-2203B

  • DrayTek Vigor 550

  • Edimax EW-7317UG

  • Edimax EW-7317LDG

  • Fiberline Networks WL-43OU

  • iNexQ UR055g

  • Linksys WUSBF54G

  • Longshine LCS-8131G3

  • MSI US54SE

  • MyTek MWU-201 USB adapter

  • Philips SNU5600

  • Planet WL-U356

  • Planex GW-US54GZ

  • Planex GW-US54GZL

  • Planex GW-US54Mini

  • Safecom SWMULZ-5400

  • Sagem XG 760A

  • Sagem XG 76NA

  • Sandberg Wireless G54 USB

  • Sitecom WL-113

  • SMC SMCWUSB-G

  • Sweex wireless USB 54 Mbps

  • Tekram/Siemens USB adapter

  • Telegent TG54USB

  • Trendnet TEW-424UB rev A

  • Trendnet TEW-429UB

  • TwinMOS G240

  • Unicorn WL-54G

  • US Robotics 5423

  • X-Micro XWL-11GUZX

  • Yakumo QuickWLAN USB

  • Zonet ZEW2501

  • ZyXEL ZyAIR G-220

3.6 Miscellaneous Networks

[i386,pc98] The ce(4) driver supports the following models of Tau-PCI/32 WAN adapters:

  • Cronyx Tau-PCI/32

  • Cronyx Tau-PCI/32-Lite

[i386] The cx(4) driver supports the following cards:

  • Cronyx Sigma-22, Sigma-24

  • Cronyx Sigma-100

  • Cronyx Sigma-400, Sigma-401, Sigma-404, Sigma-410, Sigma-440

  • Cronyx Sigma-500

  • Cronyx Sigma-703

  • Cronyx Sigma-800, Sigma-801, Sigma-810, Sigma-840

[i386,pc98] The cp(4) driver supports the following models of Tau-PCI WAN adapters:

  • Cronyx Tau-PCI

  • Cronyx Tau-PCI/R

  • Cronyx Tau-PCI-L

  • Cronyx Tau-PCI-L/R

  • Cronyx Tau-PCI-E1

  • Cronyx Tau-PCI-G703

  • Cronyx Tau-PCI-2E1

  • Cronyx Tau-PCI-4E1

  • Cronyx Tau-PCI-E3

  • Cronyx Tau-PCI-T3

  • Cronyx Tau-PCI-STS1

[i386] The ctau(4) driver supports the following cards:

  • Cronyx Tau (RS-232/V.35)

  • Cronyx Tau/R (RS-530/RS-449)

  • Cronyx Tau/E1 (fractional E1)

  • Cronyx Tau/G703 (unframed E1)

[i386] The cm(4) driver supports the following card models:

  • SMC90c26

  • SMC90c56

  • SMC90c66 in '56 compatibility mode.

3.7 Serial Interfaces

[amd64, i386] “PC standard” 8250, 16450, and 16550-based serial ports ( sio(4) driver)

The uart(4) driver supports the following classes of UARTs:

  • NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 UARTs.

  • SCC: serial communications controllers supported by the scc(4) device driver.

The scc(4) driver supports the following classes of SCCs:

  • SAB82532: Siemens SAB 82532 based serial communications controllers.

  • Z8530: Zilog 8530 based serial communications controllers.

[amd64, i386] AST 4 port serial card using shared IRQ

  • ARNET 8 port serial card using shared IRQ

  • ARNET (now Digiboard) Sync 570/i high-speed serial

[i386] Boca multi-port serial cards

  • Boca BB1004 4-Port serial card (Modems not supported)

  • Boca IOAT66 6-Port serial card (Modems supported)

  • Boca BB1008 8-Port serial card (Modems not supported)

  • Boca BB2016 16-Port serial card (Modems supported)

[i386] Comtrol Rocketport card (rp(4) driver)

[i386] Cyclades Cyclom-Y serial board (cy(4) driver)

[i386] STB 4 port card using shared IRQ

[i386] DigiBoard intelligent serial cards (digi driver)

[amd64, i386, ia64] PCI-Based multi-port serial boards ( puc(4) driver)

  • [amd64, i386] Actiontech 56K PCI

  • [amd64, i386] Avlab Technology, PCI IO 2S and PCI IO 4S

  • [amd64, i386] Comtrol RocketPort 550

  • [amd64, i386] Decision Computers PCCOM 4-port serial and dual port RS232/422/485

  • [ia64] Diva Serial (GSP) Multiport UART

  • [amd64, i386] Dolphin Peripherals 4025/4035/4036

  • [amd64, i386] IC Book Labs Dreadnought 16x Lite and Pro

  • [amd64, i386] Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550

  • [amd64, i386] Middle Digital, Weasle serial port

  • [amd64, i386] Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI

  • [amd64, i386] NEC PK-UG-X001 and PK-UG-X008

  • [amd64, i386] Netmos NM9835 PCI-2S-550

  • [amd64, i386] Oxford Semiconductor OX16PCI954 PCI UART

  • [amd64, i386] Syba Tech SD-LAB PCI-4S2P-550-ECP

  • [amd64, i386] SIIG Cyber I/O PCI 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 2P1S PCI 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 2S1P PCI 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber 4S PCI 16C550/16C650/16C850

  • [amd64, i386] SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850

  • [amd64, i386] Syba Tech Ltd. PCI-4S2P-550-ECP

  • [amd64, i386] Titan PCI-200H and PCI-800H

  • [amd64, i386] US Robotics (3Com) 3CP5609 modem

  • [amd64, i386] VScom PCI-400 and PCI-800

[i386] The rc(4) driver provides support for the SDL Communications RISCom/8 boards.

[i386, amd64] Specialix SI/XIO/SX multiport serial cards, with both the older SIHOST2.x and the “enhanced” (transputer based, aka JET) host cards (ISA, EISA and PCI) are supported. Note that the newer SX+ PCI cards are not currently supported. (si(4) driver)

[pc98] Internel serial interfaces ( sio(4) driver)

  • PC-9801 on-board

  • PC-9821 2'nd CCU (flags 0x12000000)

[pc98] NEC PC-9861K, PC-9801-101 and Midori-Denshi MDC-926Rs ( sio(4) driver)

  • COM2 (flags 0x01000000)

  • COM3 (flags 0x02000000)

[pc98] NEC PC-9801-120 ( sio(4) driver)

Note: "flags 0x11000000" is necessary in kernel configuration.

[pc98] Microcore MC-16550, MC-16550II, MC-RS98 ( sio(4) driver)

Note: "flags 0x14000?01" is necessary in kernel configuration.

[pc98] Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 ( sio(4) driver)

Note: "flags 0x15000?01" is necessary in kernel configuration.

[pc98] Media Intelligent RSB-384 ( sio(4) driver)

Note: "flags 0x16000001" is necessary in kernel configuration.

[pc98] I-O DATA RSA-98III ( sio(4) driver)

Note: "flags 0x18000?01" is necessary in kernel configuration.

[pc98] Hayes ESP98 ( sio(4) driver)

Note: "options COM_ESP" and "flags 0x19000000" are necessary in kernel configuration.

3.8 Sound Devices

[i386,amd64] The snd_ad1816(4) driver supports the following sound cards:

  • Analog Devices AD1816

[i386] The snd_als4000(4) driver supports the following sound cards:

  • Avance Logic ALS4000

[i386,amd64] The snd_atiixp(4) driver supports the following audio chipsets:

  • ATI IXP 200

  • ATI IXP 300

  • ATI IXP 400

[sparc64] The snd_audiocs(4) driver supports the following audio devices:

  • CS4231 on SBus based UltraSPARC

  • CS4231 on PCI/EBus based UltraSPARC

[i386,amd64] The snd_cmi(4) driver supports the following sound cards:

  • CMedia CMI8338A

  • CMedia CMI8338B

  • CMedia CMI8738

  • CMedia CMI8738B

[i386,amd64] The snd_cs4281(4) driver supports the following sound cards:

  • Crystal Semiconductor CS4281

[i386,amd64] The snd_csa(4) driver supports the following sound cards:

  • Crystal Semiconductor CS4280

  • Crystal Semiconductor CS4610

  • Crystal Semiconductor CS4611

  • Crystal Semiconductor CS4614

  • Crystal Semiconductor CS4615

  • Crystal Semiconductor CS4622

  • Crystal Semiconductor CS4624

  • Crystal Semiconductor CS4630

  • Genius Soundmaker 128 Value

  • Hercules Game Theatre XP

  • Turtle Beach Santa Cruz

Some onboard CS4610 chips are accompanied by the CS423x ISA codec instead of the CS4297 AC97 codec. Such configurations are not supported by the snd_csa(4) driver yet.

[i386,amd64] The snd_ds1(4) driver supports the following sound cards:

  • Yamaha DS-1

  • Yamaha DS-1E

[i386,amd64] The snd_emu10k1(4) driver supports the following sound cards:

  • Creative SoundBlaster Live! (EMU10K1 Chipset)

  • Creative SoundBlaster Audigy (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K2 Chipset)

  • Creative SoundBlaster Audigy 2 (EMU10K3 Chipset)

[i386,amd64] The snd_emu10kx(4) driver supports the following sound cards:

  • Creative Sound Blaster Live! (EMU10K1 Chipset). Both PCM and MIDI interfaces are available.

  • Creative Sound Blaster Audigy (CA0100 and CA0101 Chipset). PCM and two MIDI interfaces available.

  • Creative Sound Blaster Audigy 2 and Creative Sound Blaster Audigy 4 (CA0102 Chipset). PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit part of this chipset is not supported).

  • Creative Sound Blaster Audigy 2 Value (CA0108 Chipset). PCM support is limited to 48kHz/16 bit stereo (192kHz/24 bit part of this chipset is not supported). There is no MIDI support for this card.

The snd_emu10kx(4) driver does not support the following sound cards (although they have names similar to some supported ones):

  • Creative Sound Blaster Live! 24-Bit, identified by FreeBSD as

  • Creative Sound Blaster Audigy LS / ES, identified by FreeBSD as

  • All other Creative sound cards with -DAT chipsets.

  • All Creative X-Fi series sound cards.

[i386,amd64] The snd_envy24(4) driver supports the following audio devices:

  • M-Audio Audiophile 2496

  • M-Audio Delta Dio 2496

  • Terratec DMX 6fire

[i386,amd64] The snd_envy24ht(4) driver supports the following audio devices:

  • Audiotrak Prodigy 7.1

  • Audiotrak Prodigy 7.1 LT

  • Audiotrak Prodigy 7.1 XT

  • Audiotrak Prodigy HD2

  • ESI Juli@

  • M-Audio Audiophile 192

  • M-Audio Revolution 5.1

  • M-Audio Revolution 7.1

  • Terratec Aureon 5.1 Sky

  • Terratec Aureon 7.1 Space

  • Terratec Aureon 7.1 Universe

  • Terratec PHASE 22

  • Terratec PHASE 28

[i386,sparc64,amd64] The snd_es137x(4) driver supports the following sound cards:

  • Creative CT5880-A

  • Creative CT5880-C

  • Creative CT5880-D

  • Creative CT5880-E

  • Creative SB AudioPCI CT4730

  • Ensoniq AudioPCI ES1370

  • Ensoniq AudioPCI ES1371-A

  • Ensoniq AudioPCI ES1371-B

  • Ensoniq AudioPCI ES1373-A

  • Ensoniq AudioPCI ES1373-B

  • Ensoniq AudioPCI ES1373-8

[i386,amd64] The snd_ess(4) driver supports the following sound cards:

  • Ensoniq ESS ISA PnP/non-PnP

[i386,amd64] The snd_fm801(4) driver supports audio devices based on the following chipset:

  • Forte Media FM801

[i386,amd64] The snd_gusc(4) driver supports the following sound cards:

  • Gravis UltraSound MAX

  • Gravis UltraSound PnP

[i386,amd64] The snd_hda(4) driver supports controllers having PCI class 4 (multimedia) and subclass 3 (HDA), compatible with Intel HDA specification.

The snd_hda(4) driver supports more then two hundred different controllers and CODECs. There is no sense to list all of them here, as in most cases specific CODEC configuration and wiring are more important then type of the CODEC itself.

[i386,amd64] The snd_ich(4) driver supports the following audio devices:

  • AMD 768

  • AMD 8111

  • Intel 443MX

  • Intel ICH

  • Intel ICH revision 1

  • Intel ICH2

  • Intel ICH3

  • Intel ICH4

  • Intel ICH5

  • Intel ICH6

  • Intel ICH7

  • NVIDIA nForce

  • NVIDIA nForce2

  • NVIDIA nForce2 400

  • NVIDIA nForce3

  • NVIDIA nForce3 250

  • NVIDIA nForce4

  • SiS 7012

[i386,amd64] The snd_maestro(4) driver supports the following PCI sound cards:

  • ESS Technology Maestro-1

  • ESS Technology Maestro-2

  • ESS Technology Maestro-2E

[i386,amd64] The snd_maestro3(4) driver supports the following audio devices:

  • ESS Technology Allegro-1

  • ESS Technology Maestro3

[i386] The snd_mss(4) driver supports the following audio devices:

  • AD1845

  • AD1848

  • Aztech 2320

  • CMedia CMI8330

  • Crystal Semiconductor CS4231

  • Crystal Semiconductor CS4232

  • Crystal Semiconductor CS4234

  • Crystal Semiconductor CS4235

  • Crystal Semiconductor CS4236

  • Crystal Semiconductor CS4237

  • ENSONIQ SoundscapeVIVO ENS4081

  • NeoMagic 256AV (non-AC97)

  • OPTi 924

  • OPTi 925

  • OPTi 930

  • OPTi 931

  • OPTi 933

  • Yamaha OPL-SA2

  • Yamaha OPL-SA3

[i386,amd64] The snd_neomagic(4) driver supports the following audio devices:

  • NeoMagic 256AV

  • NeoMagic 256ZX

[i386,amd64] The snd_sbc(4) driver supports the following sound cards:

  • Avance Asound 110

  • Avance Logic ALS100+

  • Avance Logic ALS120

  • Creative SB16

  • Creative SB32

  • Creative AWE64

  • Creative AWE64 Gold

  • Creative ViBRA16C

  • Creative ViBRA16X

  • ESS ES1681

  • ESS ES1688

  • ESS ES1868

  • ESS ES1869

  • ESS ES1878

  • ESS ES1879

  • ESS ES1888

[i386,amd64] The snd_solo(4) driver supports the following sound cards:

  • ESS Solo-1 (ES1938 Chipset)

  • ESS Solo-1E (ES1946 Chipset)

Note that older ESS ISA cards with ES18xx chipset are supported via snd_ess(4) and/or snd_sbc(4).

[i386,amd64] The snd_spicds(4) driver supports the following codecs:

  • AK4358

  • AK4381

  • AK4396

  • AK4524

  • AK4528

  • WM8770

[i386,amd64] The snd_t4dwave(4) driver supports the following audio devices:

  • Acer Labs M5451

  • SIS 7018

  • Trident 4DWave DX

  • Trident 4DWave NX

[i386,amd64] The snd_via8233(4) driver supports the following audio chipsets:

  • VIA VT8233

  • VIA VT8233A

  • VIA VT8233C

  • VIA VT8235

  • VIA VT8237

  • VIA VT8251

[i386,amd64] The snd_via82c686(4) driver supports audio devices based on the following chipset:

  • VIA 82C686A

[i386,amd64] The snd_vibes(4) driver supports audio devices based on the following chipset:

  • S3 SonicVibes

[pc98] NEC PC-9801-73, 86 and compatibles (nss driver)

  • NEC A-MATE internal sound

  • Q-Vision WaveStar, WaveMaster

[pc98] NEC X-MATE, CanBe, ValueStar internal (mss driver)

[pc98] Creative Technologies SoundBlaster(98) (sb(4) driver)

[pc98] I-O DATA CD-BOX (sb(4) driver)

[pc98] MPU-401 and compatible interfaces (mpu driver)

  • Q-Vision WaveStar

3.9 Camera and Video Capture Devices

[i386,pc98] The bktr(4) driver supports video capture cards based on the Brooktree Bt848/849/878/879 chips, as well as Pinnacle PCTV cards, including:

  • AOpen VA1000

  • AVerMedia AVerTV Studio

  • AVerMedia TF/FM-98

  • ATI TV Wonder VE

  • Hauppauge WinCast/TV

  • Hauppauge WinTV-Go-FM

  • Hauppauge WinTV-pci

  • Hauppauge WinTV-radio

  • Intel Smart Video Recorder III

  • KWORLD PCI TV Tuner

  • Miro PC TV

  • Pinnacle PCTV Pro

  • Pinnacle PCTV Rave

  • PixelView PlayTV PAK

  • PixelView PlayTV Pro (rev 4C, 9D)

  • SIGMA TV II

  • STB TV PCI Television Tuner

  • Super TV Tuner

  • TerraTec TValue

  • V-Stream XPERT TV-PVR 878

  • Video Highway XTreme

  • VideoLogic Captivator PCI

[i386] Connectix QuickCam

3.10 USB Devices

[amd64, i386, ia64, pc98] A range of USB peripherals are supported; devices known to work are listed in this section. Owing to the generic nature of most USB devices, with some exceptions any device of a given class will be supported, even if not explicitly listed here.

Note: [amd64, i386, ia64, pc98] USB Ethernet adapters can be found in the section listing Ethernet interfaces.

Note: [amd64, i386, ia64, pc98] USB Bluetooth adapters can be found in Bluetooth section.

[i386,pc98,ia64,amd64,powerpc] The ohci(4) driver supports all OHCI v1.0 compliant controllers including:

  • AcerLabs M5237 (Aladdin-V)

  • AMD-756

  • OPTi 82C861 (FireLink)

  • NEC uPD 9210

  • CMD Tech 670 (USB0670)

  • CMD Tech 673 (USB0673)

  • NVIDIA nForce3

  • Sun PCIO-2 (RIO USB)

[i386,pc98,ia64,amd64,powerpc] The uhci(4) driver supports all UHCI v1.1 compliant controllers including:

  • Intel 82371AB/EB (PIIX4)

  • Intel 82371SB (PIIX3)

  • VIA 83C572

[amd64, i386, ia64, pc98] USB 2.0 controllers using the EHCI interface ( ehci(4) driver)

[amd64, i386, ia64, pc98] Hubs

[amd64, i386, ia64, pc98] Keyboards ( ukbd(4) driver)

[amd64, i386, pc98] Miscellaneous

  • Assist Computer Systems PC Camera C-M1

  • ActiveWire I/O Board

  • Creative Technology Video Blaster WebCam Plus

  • D-Link DSB-R100 USB Radio ( ufm(4) driver)

  • Mirunet AlphaCam Plus

[i386,pc98,amd64,powerpc] The following devices are supported by the urio(4) driver:

  • Diamond MultiMedia Rio 500

  • Diamond MultiMedia Rio 600

  • Diamond MultiMedia Rio 800

[i386,pc98,amd64] Devices supported by the umodem(4) driver include:

  • 3Com 5605

  • Curitel PC5740 Wireless Modem

  • Kyocera AH-K3001V Mobile Phone(WILLCOM)

  • Kyocera WX320K Mobile Phone(WILLCOM)

  • Metricom Ricochet GS USB wireless modem

  • Sierra MC5720 Wireless Modem

  • Yamaha Broadband Wireless Router RTW65b

  • ELSA MicroLink 56k USB modem

  • Sony Ericsson W810i phone

[amd64, i386, ia64, pc98] Mice ( ums(4) driver)

[i386,pc98,amd64,powerpc] The ulpt(4) driver provides support for USB printers and parallel printer conversion cables, including the following:

  • ATen parallel printer adapter

  • Belkin F5U002 parallel printer adapter

  • Canon BJ F850, S600

  • Canon LBP-1310, 350

  • Entrega USB-to-parallel printer adapter

  • Hewlett-Packard HP Deskjet 3420 (P/N: C8947A #ABJ)

  • Oki Data MICROLINE ML660PS

  • Seiko Epson PM-900C, 880C, 820C, 730C

[i386,pc98,amd64] The ubsa(4) driver supports the following adapters:

  • AnyData ADU-500A EV-DO modem

  • AnyData ADU-E100A (no EV-DO mode support)

  • Belkin F5U103

  • Belkin F5U120

  • e-Tek Labs Kwik232

  • GoHubs GoCOM232

  • Peracom single port serial adapter

[i386,pc98,amd64] The ubser(4) driver provides support for the BWCT console management serial adapters.

[i386,pc98,amd64] The uftdi(4) driver supports the following adapters:

  • B&B Electronics USB->RS422/485 adapter

  • Elexol USB MOD1 and USB MOD3

  • HP USB-Serial adapter shipped with some HP laptops

  • Inland UAS111

  • QVS USC-1000

  • Buffalo PC-OP-RS / Kurouto-shikou KURO-RS universal remote

  • Prologix GPIB-USB Controller

[i386,pc98,amd64] The uplcom(4) driver supports the following devices and adapters:

  • ADLINK ND-6530 USB-Serial Adapter

  • Alcatel One Touch 535/735 Phone

  • Alcor AU9720 USB-RS232 Serial Adapter

  • AlDiga AL-11U Modem

  • Alltronix ACM003U00 Modem

  • Anchor Serial adapter

  • ATEN UC-232A

  • BAFO BF-800 and BF-810

  • Belkin F5U257

  • BenQ S81 Phone

  • Corega CG-USBRS232R Serial Adapter

  • Cressi Edy (Seiko) Diving Computer

  • ELECOM UC-SGT Serial Adapter

  • HAL Corporation Crossam2+USB IR commander

  • Hama USB RS-232 Serial Adapter

  • Hamlet exagerate XURS232

  • HP LD220 Point-Of-Sale (POS) Display

  • IOGEAR UC-232A

  • I/O DATA USB-RSAQ, USB-RSAQ2, USB-RSAQ3 and USB-RSAQ5

  • iTegno WM1080A GSM/GFPRS Modem

  • iTegno WM2080A CDMA Modem

  • Leadtek 9531 GPS

  • Micromax 610U Modem

  • Microsoft Palm 700WX

  • Mobile Action MA-620 Infrared Adapter

  • Motorola Cables

  • Nokia CA-42 Cable

  • OTI DKU-5 cable

  • Panasonic TY-TP50P6-S flat screen

  • PLX CA-42 Phone Cable

  • PLANEX USB-RS232 URS-03

  • Prolific Generic USB-Serial Adapters

  • Prolific Pharos USB-Serial Adapter

  • RATOC REX-USB60

  • Radio Shack USB Serial Cable

  • Sagem USB-Serial Adapter

  • Samsung I330 Phone Cradle

  • Sandberg USB to Serial Link (model number 133-08)

  • Sanwa KB-USB2 Multimeter cable

  • Siemens/BenQ EF81, SX1, X65 and X75 Mobile Phones

  • Sitecom USB-Serial Adapter

  • SMART Technologies USB-Serial Adapter

  • Sony QN3 Phone Cable

  • Sony Ericsson Datapilot

  • Sony Ericsson DCU-10 and DCU-11 (Susteen) USB Cables

  • SOURCENEXT KeikaiDenwa 8 (with and without charger)

  • Speed Dragon USB-Serial Cable

  • Syntech CPT-8001C Barcode Scanner

  • TDK UHA6400 and UPA9664 USB-PHS Adapters

  • TRENDnet USB to Serial Converter (TU-S9)

  • Tripp-Lite U209-000-R USB-Serial Adapter

  • UIC HCR331 Magnetic Stripe Card Reader

  • UIC MSR206 Magnetic Stripe Card Reader

  • Willcom W-SIM DD PHS terminal.(WS002IN)

  • YC-Cable USB-Serial Adapter

  • Zeagle N2iTion3 Diving Computer

The umct(4) driver supports the following adapters:

  • Belkin F5U109

  • Belkin F5U409

  • D-Link DU-H3SP USB BAY Hub

  • Magic Control Technology USB-232

  • Sitecom USB-232

[i386,pc98,amd64,powerpc] The umass(4) driver supports USB Mass Storage devices, including:

  • ADTEC Stick Drive AD-UST32M, 64M, 128M, 256M

  • Denno FireWire/USB2 Removable 2.5-inch HDD Case MIFU-25CB20

  • FujiFilm Zip USB Drive ZDR100 USB A

  • GREEN HOUSE USB Flash Memory "PicoDrive" GH-UFD32M, 64M, 128M

  • Huawei Mobile (SD slot)

  • IBM 32MB USB Memory Key (P/N 22P5296)

  • IBM 256MB USB Drive (MSYSTEM DiskOnKey2)

  • IBM ThinkPad USB Portable CD-ROM Drive (P/N 33L5151)

  • I-O DATA USB CD/CD-R/CD-RW/DVD-R/DVD-RW/DVD-RAM/DVD-ROM Drive DVR-iUH2 (CDROM, DVD-RAM only)

  • I-O DATA USB x6 CD-RW Drive CDRW-i64/USB (CDROM only)

  • I-O DATA USB/IEEE1394 Portable HD Drive HDP-i30P/CI, HDP-i40P/CI

  • Iomega USB Zip 100/250 drive

  • Iomega Zip750 USB2.0 drive

  • Keian USB1.1/2.0 3.5-inch HDD Case KU350A

  • Kurouto Shikou USB 2.5-inch HDD Case GAWAP2.5PS-USB2.0

  • LaCie P3 HardDrive USB 200GB

  • Logitec LDR-H443U2 DVD-RAM/-R/+R/-RW/+RW drive

  • Logitec Mobile USB Memory LMC-256UD

  • Logitec USB1.1/2.0 HDD Unit SHD-E60U2

  • Logitec USB Double-Speed Floppy Drive LFD-31U2

  • Logitec USB/IEEE1394 DVD-RAM/R/RW Unit LDR-N21FU2 (CDROM only)

  • MELCO USB Flash Disk "ClipDrive", RUF-C32M, -C64M, -C128M, -C256M, -C512M

  • MELCO USB Flash Disk "PetitDrive", RUF-32M, -64M, -128M, -256Mm

  • MELCO USB2.0 Flash Disk "PetitDrive2", RUF-256M/U2, -512M/U2

  • MELCO USB2.0 MO Drive MO-CH640U2

  • Matshita CF-VFDU03 floppy drive

  • Merlin SM300 MP3/WMA Player (256Mb)

  • Microtech International, Inc. USB-SCSI-HD 50 USB to SCSI cable

  • Motorola E398 Mobile Phone (TransFlash memory card)

  • NOVAC USB2.0 2.5/3.5-inch HDD Case NV-HD351U

  • PNY Attache Flash Drive

  • Panasonic ("Matshita FDD CF-VFDU03")

  • Panasonic KXL-CB20AN Portable DVD-ROM/CD-R/RW

  • Panasonic KXL-CB35AN (DVD-ROM & CD-R/RW)

  • Panasonic USB2.0 Portable CD-RW Drive KXL-RW40AN (CDROM only)

  • Panasonic floppy drive

  • Qware BeatZkey! Pro

  • RATOC Systems USB2.0 Removable HDD Case U2-MDK1, U2-MDK1B

  • SanDisk SDDR-31 (Compact Flash)

  • SanDisk SDDR-75 (only Compact Flash port works)

  • Sitecom CN-300 MultiFlash (MMC/SD, SmartMedia, CF, MemoryStick)

  • Sony Portable CD-R/RW Drive CRX10U (CDROM only)

  • TEAC Portable USB CD-ROM Unit CD-110PU/210PU

  • Time DPA20B MP3 Player (1Gb)

  • Trek Thumbdrive 8MB

  • VAIO floppy drive (includes Y-E Data Flashbuster-U)

  • Y-E Data floppy drive (720/1.44/2.88Mb)

Among the supported digital cameras are:

  • Asahi Optical (PENTAX) Optio 230 & 330

[amd64, i386, pc98] Audio Devices ( uaudio(4) driver)

[i386,pc98,amd64] The uvisor(4) driver supports the following devices:

  • Aceeca Mez1000 RDA

  • Handspring Treo

  • Handspring Treo 600

  • Handspring Visor

  • Palm I705

  • Palm M125

  • Palm M130

  • Palm M500

  • Palm M505

  • Palm M515

  • Palm Tungsten T

  • Palm Tungsten Z

  • Palm Zire

  • Palm Zire 31

  • Sony Clie 4.0

  • Sony Clie 4.1

  • Sony Clie 5.0

  • Sony Clie PEG-S500C

  • Sony Clie NX60

  • Sony Clie S360

  • Sony Clie TJ37

3.11 IEEE 1394 (Firewire) Devices

[i386,sparc64,ia64,amd64,powerpc] The fwohci(4) driver provides support for PCI/CardBus FireWire interface cards. The driver supports the following IEEE 1394 OHCI chipsets:

  • Adaptec AHA-894x/AIC-5800

  • Apple Pangea

  • Apple UniNorth

  • Intel 82372FB

  • IOGEAR GUF320

  • Lucent / Agere FW322/323

  • NEC uPD72861

  • NEC uPD72870

  • NEC uPD72871/2

  • NEC uPD72873

  • NEC uPD72874

  • National Semiconductor CS4210

  • Ricoh R5C551

  • Ricoh R5C552

  • Sony CX3022

  • Sony i.LINK (CXD3222)

  • Sun PCIO-2 (RIO 1394)

  • Texas Instruments PCI4410A

  • Texas Instruments PCI4450

  • Texas Instruments PCI4451

  • Texas Instruments TSB12LV22

  • Texas Instruments TSB12LV23

  • Texas Instruments TSB12LV26

  • Texas Instruments TSB43AA22

  • Texas Instruments TSB43AB21/A/AI/A-EP

  • Texas Instruments TSB43AB22/A

  • Texas Instruments TSB43AB23

  • Texas Instruments TSB82AA2

  • VIA Fire II (VT6306)

[amd64, i386, sparc64] Serial Bus Protocol 2 (SBP-2) storage devices ( sbp(4) driver)

3.12 Bluetooth Devices

[i386,pc98,amd64] The ng_bt3c(4) driver provides support for the 3Com/HP 3CRWB6096-A PCCARD bluetooth adapter.

[i386,pc98,amd64] The ng_ubt(4) driver supports all Bluetooth USB devices that conform with the Bluetooth specification v1.1, including:

  • 3Com 3CREB96

  • AIPTEK BR0R02

  • EPoX BT-DG02

  • Mitsumi Bluetooth USB adapter

  • MSI MS-6967

  • TDK Bluetooth USB adapter

  • Broadcom Bluetooth USB adapter

3.13 Cryptographic Accelerators

[i386,pc98,amd64] The hifn(4) driver supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, such as:

  • Invertex AEON

  • Hifn 7751

  • PowerCrypt

  • XL-Crypt

  • NetSec 7751

  • Soekris Engineering vpn1201 and vpn1211

  • Soekris Engineering vpn1401 and vpn1411

[i386,pc98,amd64] The safe(4) driver supports cards containing any of the following chips:

  • SafeNet 1141

  • SafeNet 1741

[i386,pc98,amd64] The ubsec(4) driver supports cards containing any of the following chips:

  • Bluesteel 5501

  • Bluesteel 5601

  • Broadcom BCM5801

  • Broadcom BCM5802

  • Broadcom BCM5805

  • Broadcom BCM5820

  • Broadcom BCM5821

  • Broadcom BCM5822

  • Broadcom BCM5823

  • Broadcom BCM5825

3.14 Miscellaneous

[amd64, i386, pc98] FAX-Modem/PCCARD

  • MELCO IGM-PCM56K/IGM-PCM56KH

  • Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal)

[amd64, i386, pc98] Floppy drives ( fdc(4) driver)

[amd64, i386] VGA-compatible video cards ( vga(4) driver)

Note: Information regarding specific video cards and compatibility with Xorg can be found at http://www.x.org/.

[amd64, i386, ia64, pc98] Keyboards including:

  • [i386] AT-style keyboards ( atkbd(4) driver)

  • [amd64, i386] PS/2 keyboards ( atkbd(4) driver)

  • [pc98] Standard keyboards

  • [amd64, i386, ia64, pc98] USB keyboards ( ukbd(4) driver)

[amd64, i386, ia64, pc98] Pointing devices including:

  • [amd64, i386, pc98] Bus mice and compatible devices ( mse(4) driver)

  • [amd64, i386] PS/2 mice and compatible devices, including many laptop pointing devices ( psm(4) driver)

  • Serial mice and compatible devices

  • [amd64, i386, ia64, pc98] USB mice ( ums(4) driver)

Note: moused(8) has more information on using pointing devices with FreeBSD. Information on using pointing devices with Xorg can be found at http://www.x.org/.

[amd64, i386] “PC standard” parallel ports ( ppc(4) driver)

[pc98] “PC-9821 standard” parallel ports ( ppc(4) driver)

[i386, amd64] PC-compatible joysticks ( joy(4) driver)

[pc98] Joystick port of SoundBlaster(98) ( joy(4) driver)

[i386, pc98] PHS Data Communication Card/PCCARD

  • NTT DoCoMo P-in Comp@ct

  • Panasonic KX-PH405

  • SII MC-P200

[i386] Xilinx XC6200-based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (xrpu driver).

[pc98] Power Management Controller of NEC PC-98 Note (pmc driver)

This file, and other release-related documents, can be downloaded from ftp://ftp.FreeBSD.org/.

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.

For questions about this documentation, e-mail <doc@FreeBSD.org>.

diff --git a/website/content/en/releases/8.4R/relnotes-detailed.html b/website/content/en/releases/8.4R/relnotes-detailed.html index d93deb0427..b60ecda268 100644 --- a/website/content/en/releases/8.4R/relnotes-detailed.html +++ b/website/content/en/releases/8.4R/relnotes-detailed.html @@ -1,2382 +1,2382 @@ FreeBSD 8.4-RELEASE Release Notes

FreeBSD 8.4-RELEASE Release Notes

The FreeBSD Project

Copyright © 2013 The FreeBSD Documentation Project

$FreeBSD: releng/8.4/release/doc/en_US.ISO8859-1/relnotes/article.xml 251258 2013-06-02 16:21:02Z hrs $

FreeBSD is a registered trademark of the FreeBSD Foundation.

IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both.

IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and Electronics Engineers, Inc. in the United States.

Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

SPARC, SPARC64, SPARCengine, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol.

The release notes for FreeBSD 8.4-RELEASE contain a summary of the changes made to the FreeBSD base system on the 8.4-STABLE development line. This document lists applicable security advisories that were issued since the last release, as well as significant changes to the FreeBSD kernel and userland. Some brief remarks on upgrading are also presented.

Table of Contents
1 Introduction
2 What's New
2.1 Security Advisories
2.2 Kernel Changes
2.2.1 Boot Loader Changes
2.2.2 Hardware Support
2.2.3 Network Protocols
2.2.4 Disks and Storage
2.2.5 File Systems
2.3 Userland Changes
2.3.1 /etc/rc.d Scripts
2.4 Contributed Software
2.5 Ports/Packages Collection Infrastructure
2.6 Release Engineering and Integration
3 Upgrading from previous releases of FreeBSD

1 Introduction

This document contains the release notes for FreeBSD 8.4-RELEASE. It describes recently added, changed, or deleted features of FreeBSD. It also provides some notes on upgrading from previous versions of FreeBSD.

This distribution of FreeBSD 8.4-RELEASE is a release distribution. It can be found at ftp://ftp.FreeBSD.org/ or any of its mirrors. More information on obtaining this (or other) release distributions of FreeBSD can be found in the “Obtaining FreeBSD” appendix to the FreeBSD Handbook.

All users are encouraged to consult the release errata before installing FreeBSD. The errata document is updated with “late-breaking” information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 8.4-RELEASE can be found on the FreeBSD Web site.

2 What's New

This section describes the most user-visible new or changed features in FreeBSD since 8.3-RELEASE.

Typical release note items document recent security advisories issued after 8.3-RELEASE, new drivers or hardware support, new commands or options, major bug fixes, or contributed software upgrades. They may also list changes to major ports/packages or release engineering practices. Clearly the release notes cannot list every single change made to FreeBSD between releases; this document focuses primarily on security advisories, user-visible changes, and major architectural improvements.

2.1 Security Advisories

Problems described in the following security advisories have been fixed. For more information, consult the individual advisories available from http://security.FreeBSD.org/.

- + - + - + - + - + - + - + - + - + - + - + - +
Advisory Date Topic
SA-12:01.openssl03 May 201203 May 2012

OpenSSL multiple vulnerabilities
SA-12:02.crypt30 May 201230 May 2012

Incorrect crypt() hashing
SA-12:03.bind12 June 201212 June 2012

Incorrect handling of zero-length RDATA fields in named(8)
SA-12:04.sysret12 June 201212 June 2012

Privilege escalation when returning from kernel
SA-12:05.bind06 August 201206 August 2012

named(8) DNSSEC validation Denial of Service
SA-12:06.bind22 November 201222 November 2012

Multiple Denial of Service vulnerabilities with named(8)
SA-12:07.hostapd22 November 201222 November 2012

Insufficient message length validation for EAP-TLS messages
SA-12:08.linux22 November 201222 November 2012

Linux compatibility layer input validation error
SA-13:02.libc19 February 201319 February 2013

glob(3) related resource exhaustion
SA-13:03.openssl02 April 201302 April 2013

OpenSSL multiple vulnerabilities
SA-13:04.bind02 April 201302 April 2013

BIND remote denial of service
SA-13:05.nfsserver29 April 201329 April 2013

Insufficient input validation in the NFS server

2.2 Kernel Changes

A bug which could cause a kernel thread to have a wrong CPU affinity configuration has been fixed.[r232757]

loader(8) environment variables comconsole_port and comconsole_pcidev have been added. The former allows to set the base address of the serial console I/O port. The later takes the string of the format bus:device:function:[bar] as a value and uses the serial port attached as PCI device at the specified location for console. Both variants pass hw.uart.console variable to the uart(4) driver to properly hand-over the kernel console.[r245847]

A new loader(8) tunable hw.broken_txfifo has been added to enable workaround for old version of QEMU and Xen which have a buggy emulated UART.[r246626]

The F_DUPFD_CLOEXEC command for fcntl(2) has been implemented. This is standardized in IEEE Std 1003.1-2008 (POSIX, Single UNIX Specification Version 4). In addition to this, F_DUP2FD_CLOEXEC has been implemented in analogy with F_DUP2FD.[r239860, r239861]

The filemon(4) pseudo-device has been added. This allows a process to collect file operations data of its children.[r240707]

A bug in VIMAGE jail(8) which could make the network subsystem run on an wrong vnet context has been fixed.[r233584]

debug.kdb.break_to_debugger and debug.kdb.alt_break_to_debugger have been added as sysctl(8) variables and loader tunables. These are disabled by default and BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER kernel options now set them enabled. These changes allow GENERIC kernel to support break-to-debugger capability.[r235121]

The FreeBSD sched_ule(4) scheduler has been improved in CPU selection on systems which support SMT (Symmetric MultiThreading, also known as HyperThreading on Intel CPUs). It now prefers a logical CPU when the the other logical CPUs on the physical one are idle, and an idle CPU in an SMT CPU group always has lower priority. The CPU load calculation for load balancing has also been improved to consider highest and lowest CPU load in comparison to differentiate load in CPU groups. This change gives 10-15% performance improvement in SMT CPUs such as Core i7.[r241246]

The shm_map(9) and shm_unmap(9) functions have been added to allow in-kernel code to map portions of shared memory objects created by shm_open(2) into the kernel's address space.[r236684]

A new sysctl(8) variable kern.stop_scheduler_on_panic has been added. When set to 1, only one thread runs uninterruptedly after a system panic and the other CPUs are stopped. The default value is 0.[r235502]

The loader(8) tunables kern.maxtsiz, kern.dfldsiz, kern.maxdsiz, kern.dflssiz, kern.maxssiz, and kern.sgrowsiz are now writable sysctl(8) variables.[r240502]

A bug that changes to a mapped file with the mmap(2) system call were not flushed properly under certain circumstances has been fixed. If a process has an NFS-backed file and adds changes to it, normally the changes are written into the backing store automatically. However, the NFS client recognized the modified parts are written successfully even when the write operation was failed for some reason such as permission denied.[r233765, r234094, r236150]

2.2.1 Boot Loader Changes

[amd64, i386, pc98] A bug in FreeBSD boot block has been fixed. A pathname of the third stage loader (or kernel) in the boot.config(5) configuration file could not be recognized.[r233377, r234563]

A bug in loader(8) which could prevents a UFS1 filesystem on big endian platforms from booting.[r232963]

[sparc64] FreeBSD loader(8) now supports heap to show the heap usage.[r235998]

The gptboot boot block now reads the backup GPT header from the last LBA only when the primary GPT header and tables are invalid. This mitigates interoperability issues with some geom(4) providers like MIRROR which use the last LBA for the metadata.[r234694]

[sparc64] FreeBSD/sparc64 now supports booting from ZFS via the zfsboot boot block and zfsloader.[r236077]

A bug in the zfsboot boot block which could prevent -q option from working has been fixed.[r234680]

The zfsboot boot block and zfsloader support filesystems within a ZFS storage pool. In zfsloader, the ZFS device name format is now zfs:pool/fs and the fully qualified file path format is zfs:pool/fs:/path/to/file. The zfsboot boot block accepts the kernel/loader name in the format pool:fs:path/to/file or, as before, pool:path/to/file. In the latter case a default filesystem is used (the pool root or a filesystem with the bootfs property). The zfsboot boot block passes the GUIDs of the selected storage pool and dataset to zfsloader to be used as its defaults.[r237765]

2.2.2 Hardware Support

FreeBSD acpi(4) subsystem now uses MADT to match ACPI Processor objects to CPUs and ignores disabled cores while it is possible that MADT and DSDT/SSDTs may list CPUs in different orders. A new loader tunable debug.acpi.cpu_unordered has been added for buggy systems that do not have unique ACPI IDs for MADT and Processor objects. Setting it to 1 restores the old behavior.[r237823]

[amd64] A workaround for Erratum 721 for AMD Processor Family 10h and 12h has been implemented. Under a highly specific and detailed set of internal timing conditions, the processor may incorrectly update the stack pointer after a long series of push and/or near-call instructions, or a long series of pop and/or near-return instructions.[r233799]

[amd64] The extended FPU states for native 64-bit and 32-bit ABIs have been supported. AVX instructions are also enabled on capable CPUs.[r237009]

[amd64, i386, pc98] The atkbdc(4) driver now supports a keyboard controller which has PnP ID PNP0320. This can be found on machines which have Japanese PS/2 keyboard with 106/109 keys.[r233795]

[amd64, i386, pc98] The atkbdc(4) driver now supports Synaptics touchpad v7.5 and above.[r244982]

A bug in cpufreq(4) which could prevent CPU frequency tuning from working properly has been fixed.[r233369]

A bug in hwpmc(4) driver which could cause a deadlock in pmcstat(8) utility has been fixed.[r233825]

The pcf8563(4) driver for the NXP (Philips) PCF8563 RTC has been added.[r236079]

[amd64] The pci(4) driver now supports mapping between MSI (Message Signaled Interrupt) and HyperTransport interrupt messages on HyperTransport to PCI bus briges. This change improves handling of MSIs on AMD CPUs.[r234151]

The puc(4) driver now supports Sun 1040 PCI Quad Serial, Moxa PCIe CP102E/CP102EL/CP104EL-A/CP104JU/CP114EL/CP118EL-A/CP168EL-A multiport serial boards, Advantech PCI-1602 RS-485/RS-422 serial card, and Sunix SER5437A dual serial PCI Express card.[r236651, r238775, r243009, r248041]

[amd64, i386] The random(4) driver now supports VIA C3 Nehemiah random number generator on VIA Nano processors. PADLOCK kernel option has been replaced with PADLOCK_RNG in GENERIC kernel.[r240991]

[amd64, i386] The random(4) driver now supports RDRAND instruction on Intel on-chip Digital Random Number Generator (called Bull Mountain). RDRAND_RND kernel option has been added to GENERIC kernel.[r240994]

A new syscons(4) keyboard map for Danish ISO-8859-1 keyboard found on Apple MacBook has been added.[r242338]

A bug in the syscons(4) driver has been fixed. It could cause a button of a USB mouse to be pressed and never released after detaching.[r246787]

[amd64, i386] The uart(4) driver now supports Intel AMT Serial Port for Remote Keyboard and Text (KT) Redirection (Serial Over LAN) on Intel 4 Series Chipset family.[r233065]

The uart(4) driver now supports Wacom Tablet at FuS Lifebook T, multiport serial device IrDA devices with PnP ID PNP0502, PNP0510, and PNP0511, V.34 modems based on CIR1000 Cirrus Logic chip, and MosChip MCS9904 four serial ports controller.[r242883, r243357, r244140]

The uftdi(4) driver now supports BeagleBone and FT2232-based egnite Turtelizer 2 JTAG/RS232 Adapter.[r237189, r237381]

The uchcom(4) driver now supports CH341/CH340 USB-Serial Bridge.[r240570]

The ukbd(4) driver now supports Microsoft Natural Ergonomic Keyboard 4000. It had an issue that function keys were not recognized.[r239426]

The uplcom(4) driver now supports Motorola cable.[r239726]

The usb(4) driver now handles suspend events synchronously. This fixed problems of suspend and resume.[r232871]

The usb(4) driver now supports multi-TT mode operation, which can have one transaction translator for each downstream-facing port on a USB hub. This allows more bandwidth for isochronous FULL speed application connected through a High Speed USB HUB.[r235011]

The uslcom(4) driver now supports Silicon Laboratories CP2103/CP2104/CP2105 based USB serial adapter.[r239820, r239827]

[amd64, i386] The paravirtualized virtio(4) drivers have been added to GENERIC kernel. They include PCI fontend, net, block, balloon, and scsi drivers. The module files are virtio.ko, virtio_pci.ko, if_vtnet.ko, virtio_blk.ko, virtio_balloon.ko, and virtio_scsi.ko, respectively.[r239473, r247907, r247909]

The wbwd(4) driver, which supports the watchdog timer found in Winbond Super I/O chips, has been added.[r235947]

The xhci(4) USB driver now supports XHCI port routing on Intel 7 Series chipsets (Panther Point) and Intel 8 Series chipsets (Lynx Point). A new loader(8) tunable hw.usb.xhci.xhci_port_route has been added for routing bitmap for switching EHCI ports to XHCI controller.[r242985]

The xhci(4) USB driver now supports Etron EJ168 USB 3.0 Host Controllers.[r245736]

2.2.2.1 Multimedia Support

[i386] A bug in the snd_emu10kx(4) driver which could prevent it from working with PAE kernel option has been fixed.[r238674]

The snd_hda(4) driver has been updated. It now supports and provides HDMI, new volume control, automatic recording source selection, runtime reconfiguration, more than 4 PCM devices on a controller, multichannel recording, additional playback/record streams, higher bandwidth, and more informative device names.[r236750, r236753]

The snd_uaudio(4) driver now supports USB Audio v2.0.[r242983]

The snd_uaudio(4) driver now supports Intel 8 Series chipsets (Lynx Point).[r247121]

The snd_uaudio(4) driver now supports various Yamaha keyboards.[r244248]

The snd_uaudio(4) driver now supports buttons such as volume up/down.[r246788]

2.2.2.2 Network Interface Support

The age(4) network interface driver now supports jumbo frames.[r246725]

Link state change handling in the ale(4) network interface driver has been improved.[r234127]

The ale(4) network interface driver now supports flow control.[r234241]

A bug in the bce(4) network interface driver has been fixed. It could prevent jumbo frame configuration from working.[r235424]

A bug in bce(4) which could prevent IPMI (Intelligent Platform Management Interface) from working when the interface is down has been fixed.[r236217]

The bce(4) network interface driver now supports remote PHYs, which allow the controller to perform MDIO type accesses to a remote transceiver by using message pages defined through MRBE (MultiRate Backplane Ethernet). This is found on machines such as the Dell PowerEdge M610 Blade.[r235819]

A bug in the bge(4) network interface driver which could cause watchdog timeout on BCM5704 controller connected behind AMD 8131 PCI-X bridge has been fixed.[r233496]

The bge(4) driver now supports BCM5717/5718/5719/5720/5761/57766 controllers.[r243547, r245152]

A bug in if_ierrors counter in the bge(4) driver running on BCM5700, 5701, 5702, 5703, or 5704 controller has been fixed. It reported only the number of discarded packets.[r233499]

A bug in bge(4) which could make the device stop working has been fixed.[r236219]

[amd64, i386, pc98] The cas(4), gem(4), and hme(4) drivers have been added to GENERIC kernel.[r233744]

The cxgbe(4) network interface driver has been updated to firmware version 1.8.4.[r247670]

A bug in statistics counters in the em(4), lem(4), and igb(4) drivers has been fixed.[r241376]

The em(4) and lem(4) network interface drivers have been updated to version 7.3.7 and 2.3.9, respectively. It now supports Intel 82580 and I210/I217/I218 interfaces.[r247430]

The fxp(4) network interface driver has been improved. It does not cause unnecessary media change in controller reconfiguration such as promiscuous mode change which leads to an extra link reestablishment.[r233502]

The igb(4) network interface driver now attempts to attach as many CPUs as possible to each queue. If the number of CPUs are greater than or equal to the number of queues, all queues are bound to different CPUs.[r235616]

The ipheth(4) driver now supports Apple iPhone 5 tethering mode.[r242279]

The iwn(4) driver now supports Intel Centrino 6150 wireless N and WiMAX chipsets, and Intel Centrino Wireless-N 100/130 devices.[r233839, r235844]

The ixgbe(4) network interface driver has been updated to version 1.1.4.[r247501]

A bug in ixgbe(4) network interface driver has been fixed. It could cause packet loss in TCP communication when TSO (TCP Segmentation Offload) is enabled.[r235666]

The mxge(4) driver has been updated to firmware version 1.4.55 from Myricom.[r236416]

The oce(4) network interface driver has been updated to version 4.6.95.0.[r248062]

The ral(4) network interface driver now supports Ralink RT2800 and RT3000 chipsets.[r236008]

A bug in the re(4) and rl(4) network interface drivers which could cause a problem on RTL8139 family has been fixed.[r233490]

A bug in the re(4) network interface driver which could cause intermittent link up/down on RTL8169 controller has been fixed.[r233493]

The rl(4) network interface driver now supports D-Link DFE-520TX rev C1.[r245858]

WoL (Wake-on-LAN) support in the rl(4) driver is now disabled by default.[r233490]

The run(4) driver now supports Logitec LAN-W300NU2.[r232594]

The run(4) network interface driver now loads the firmware upon initialization, not attachment. This fixes an issue when the root filesystem is not available at the time of device detection.[r233461]

The run(4) driver has been updated to firmware version 0.236.[r234029]

The sf(4) network interface driver has been improved. System load fluctuation under high network load has been fixed.[r233487]

The tap(4) pseudo network interface driver now supports VIMAGE jail(8).[r237145]

The u3g(4) driver now supports Qualcomm Vertex Wireless 110L modem, Qualcomm 3G modem, Qualcomm Vertex VW110L modem, SIMCom SIM5218, and Huawei K4505, K3770, E3131, E392, E3131, K3765, K4505, and ETS2055 3G modems.[r232875, r235012, r243655]

The udav(4) network interface driver now supports JP1082 USB-LAN adapter.[r242984]

2.2.3 Network Protocols

Locking performance of the bpf(4) Berkeley Packet Filter has been improved.[r247732]

The if_bridge(4) pseudo network interface driver now supports multiple bridges in the same STP domain. It used the same MAC address as the bridge ID for all bridges on the system before.[r236056]

The if_bridge(4) now supports link state change notification and works with carp(4) protocol.[r236058]

The net.link.bridge sysctl(8) variables can now be set in loader(8) and/or loader.conf(5).[r236072]

The default number of the bridge forwarding cache entries of the if_bridge(4) pseudo network interface driver has been increased from 100 to 2000.[r233085]

The table argument in the ipfw(4) packet filter rule syntax now supports IP address, interface name, port number, and jail ID. The following syntax is valid:

 skipto tablearg ip from any to any via table(42) in

A new sysctl(8) variable net.inet.ip.fw.tables_max has been added to specify the maximum number of tables. The default value is 128.[r234637]

IP_RECVTOS socket option to receive for received UDP/IPv4 packets a cmsg of type IP_RECVTOS which contains the TOS byte has been implemented. This allows access to the ECN bits in a protocol on top of UDP.[r247944]

A bug in FreeBSD IPv6 stack has been fixed. It could cause a vlan(4) pseudo network interface to get the EUI64 part in an autoconfigured IPv6 address from an unrelated Ethernet interface on the system.[r233112]

FreeBSD IPv6 stack now supports multiple FIBs. One can use setfib(1) to select a different routing table for IPv6.[r232552]

A bug in reference counting of IPv6 interface routes has been fixed.[r236609, r236611, r236827]

FreeBSD IPv6 stack now handles fragment packets which are not actually fragments but have Fragment Header with both the Fragment Offset and the M bit set to 0 as a regular (non-fragment) packet. For more detail, see Internet Draft draft-gont-6man-ipv6-atomic-fragments.[r238495]

A bug which could cause a system panic in the multicast routing in kernel with VIMAGE kernel option has been fixed. This option is disabled in GENERIC kernel.[r233605]

The lagg(4) pseudo network driver now allows the configuration of which layers are used for the load balance hash calculation. It can be set in ifconfig lagghash option in a comma-separated list. The default value is lagghash l2,l3,l4. For more detail, see ifconfig(8) manual page.[r236057]

A bug in the lagg(4) pseudo network interface driver which could cause an unexpected removal of a member interface upon interface renaming has been fixed.[r238048]

The ng_netflow(4) netgraph(4) node and flowctl(8) utility now supports NetFlow version 9. A new export9 hook has been added for NetFlow v9 data. Note that data export can be done simultaneously in both version 5 and version 9.[r238619, r238620]

A bug in the ng_patch(4) netgraph(4) node which could cause a system panic has been fixed.[r234682]

FreeBSD routing table handling has been improved. It can now perform packet forwarding even while a user application is reading the whole routing table via sysctl(8).[r235056]

A loader tunable net.fibs now supports specifying the number of routing tables. The ROUTETABLES kernel option can still be used to set the default number of routing tables.[r235104]

FreeBSD SCTP stack now supports ng_iface(4) and stf(4) interfaces.[r233245, r233246]

FreeBSD SCTP stack now supports net.inet.udp.checksum sysctl(8) variable for SCTP over UDP over IPv4 encapsulation.[r234805]

SO_PROTOCOL and SO_PROTOTYPE socket option have been added. These are socket level options to get the protocol number found in Linux or Solaris. For more detail, see setsockopt(2) manual page.[r232819]

An issue in FreeBSD tcp(4) host cache has been fixed. It could cause extra ICMP message exchanges when an ICMP unreach is received but allocation of the corresponding TCP host cache fails.[r235053]

A sysctl(8) variable net.inet.tcp.rexmit_drop_options has been added to not drop options from the third retransmitted SYN. The default value is set to 1 for backward compatibility.[r247499]

2.2.4 Disks and Storage

The ahci(4) driver now supports Marvell 88SE9220/9230/9235 PCIe 2.0 x2 6Gbps SATA controllers.[r237114]

The arcmsr(4) driver has been updated to version 1.20.00.26 and now supports ARC-1214 and ARC-1224.[r244923, r247827]

A bug in the amr(4) driver which could cause data corruption has been fixed.[r236319]

The ata(4) driver now supports Intel 8 Series chipsets (Lynx Point).[r247099]

The ata(4) driver now creates symbolic links for backward compatibility when ATA_CAM kernel option is enabled. In a kernel with ATA_CAM, an ATA/SATA disk is recognized as a device node with a name ada0 instead of ad0. A symbolic link /dev/ad0 is automatically generated for /dev/ada0 to keep backward compatibility. This symbolic link generation can be controlled by a kern.cam.ada.legacy_aliases (enabled by default when ATA_CAM is set).[r234912]

The ata(4) driver now has loader(8) tunables to set initial SATA revision for the specific device. The tunable name is hint.ata.busnum.devdevnum.sata_rev for a device devnum on a bus busnum, or hint.ata.busnum.sata_rev for all devices on a bus busnum. The valid values are 1, 2, and 3, -which correspond to 1.5 Gbps, 3 Gbps, and 6 Gbps.[r243124]

A new sysctl(8) kern.features.ata_cam has been added. This shows whether ATA_CAM kernel option is enabled or not. This option is disabled in GENERIC kernel.[r233714]

A new sysctl(8) variable kern.cam.pmp.hide_special has been added. This controls whether special PMP ports such as PMP (Port MultiPlier) configuration or SEMB (SATA Enclosure Management Bridge) will be exposed or hidden. The default value is 1 (hidden).[r236766]

The cam(4) driver now uses READ CAPACITY(16) SCSI command to get device information by default when possible. This enables to detect whether Logical Block Provisioning (also known as TRIM or UNMAP) in SBC-3 (SCSI Block Commands-3) Specification is supported on the device.[r232942, r236804]

The sysctl(8) variables kern.cam.da.da_send_ordered and kern.cam.ada.ada_send_ordered have been renamed with kern.cam.da.send_ordered and kern.cam.ada.send_ordered.[r247105]

Performance of the da(4) driver has been improved. It now handles subsequent BIO_DELETE requests handled as a single TRIM request.[r234914]

[amd64, i386] The hpt27xx(4) driver has been included in GENERIC kernel.[r245941]

The hptiop(4) driver has been updated to version 1.8 and now supports HighPoint RocketRAID 4500/4311/4310/4211/4210/3560/3530.[r239159, r242216]

The isci(4) driver now supports Intel C600 Serial Attached SCSI controllers with chip IDs from 0x1d6c to 0x1d6f.[r232554]

A bug in the isci(4) driver which could not correctly handle READ CAPACITY(16) SCSI command for an SATA device has been fixed.[r233789]

The isci(4) driver now supports SCSI UNMAP to ATA DSM translation.[r239735]

A bug in isci(4) driver which could prevent smartctl (sysutils/smartmontools in the Ports Collection) from working.[r236264]

The mfi(4) driver now supports LSI MegaRAID SAS cards named "Drake Skinny" and "ThunderBolt". This includes Dell PERC H810/H800/H710/H700 and Intel RAID Controller RS25DB080/RS25NB008.[r235625]

A bug which could make the mpt(4) driver attach LSI MegaRAID cards which should be handled by the mfi(4) driver has been fixed.[r232563]

The mfi(4) driver now supports loader(8) tunable hw.mfi.allow_cam_disk_passthrough to control raw disk attachment. The default value is 0 (disabled).[r243826]

The mps(4) driver has been updated to version 14.00.00.01-fbsd. This now supports Integrated RAID, WarpDrive controllers, WRITE12 and READ12 for direct I/O, SCSI protection information (EEDP), Transport Level Retries (TLR) for tape drives, and LSI's userland utility.[r237877]

[sparc64, powerpc] The mps(4) driver has been added to GENERIC kernel.[r237944, r238074]

The MULTIPATH geom(4) class has been updated. It now supports Active/Active mode, Active/Read mode as hybrid of Active/Active and Active/Passive, keeping a failed path without removing the geom provider, manual configuration without on-disk metadata, and add, remove, fail, restore, configure subcommands in the gmultipath(8) utility to manage the configured paths.[r234917]

The PART_LDM geom(4) class has been added. This partition scheme has support for Logical Disk Manager, which is also known as dynamic volumes in Microsoft Windows NT. Note that JBOD, RAID0, and RAID5 volumes are not supported yet.[r234407]

The RAID geom(4) class now supports the DDF metadata format, which is defined in the SNIA Common RAID Disk Data Format Specification v2.0. It can read non-degraded RAID4/5/5E/5EE/5R/6/MDF volumes. An -o option in graid(8) utility can be used to specify byte order for the DDF metadata.[r235875]

The RAID geom(4) class now partially supports Intel Rapid Recover Technology (Intel RRT). It is alike to RAID1, but with dedicating master and recovery disks and providing manual control over synchronization. It allows to use recovery disk as snapshot of the master disk from the time of the last sync.[r246170]

The RAID geom(4) class now supports sysctl(8) variables kern.geom.raid.enable and kern.geom.raid.format. kern.geom.raid.enable is to control on-disk metadata recognition in a systemwide basis. When it is set to 1, it is enabled (the default value is 1). kern.geom.raid.format are similar variables to control enable/disable of specific metadata or transformation modules. The valid keywords for format are raid0, raid1, raid1e, raid5, and concat.[r240554, r240556]

The RAID geom(4) class now supports BIO_DELETE requests.[r243679]

The tmpfs(5) filesystem is production ready, and no longer considered an experimental implementation.[r234512]

The tws(4) driver has been updated to version 10.80.00.005 from LSI.[r241763]

The umass(4) driver now supports Olympus FE-210 camera, LG UP3S MP3 player, Laser MP3-2GA13 MP3, and Garmin GPS devices.[r235086, r236654]

A bug in the xen(4) blkfront driver has been fixed. It could not attach on Citrix XenServer configurations that advertise the multi-page ring extension.[r233791]

2.2.5 File Systems

The linprocfs(5) filesystem now supports /proc/filesystems.[r247808]

Bugs in msdosfs(5) which could cause mounting a FAT32 filesystem to fail, create a broken directory entry in a FAT32 filesystem, and prevent sync and async mount option from working, have been fixed.[r246547, r246548, r246550]

Bugs in FreeBSD NFS subsystem has been fixed. They could cause stale name cache entries on an NFS client.[r233286]

A memory leak when a ZFS volume is exported via the FreeBSD NFS (newnfs) server has been fixed. Note that oldnfs is used as the default NFS implementation in GENERIC kernel.[r236147]

FreeBSD NFS subsystem now supports a timeout parameter on positive name cache entries on the NFS client side. nametimeo mount option has been added to specify the timeout. The default value is 60 seconds, and one can disable the positive name caching by setting it to 0.[r233327]

A workaround has been implemented in FreeBSD NFS subsystem to handle a reply to an NFS create RPC which do not include file attributes under certain circumstances. This improves interoperability between non-FreeBSD NFS servers and FreeBSD NFS clients.[r235417]

A bug in exports(5) handling in FreeBSD NFS subsystem has been fixed. It could cause an unintended security configuration when there are multiple export entries with different security flavors.[r241348]

Several bugs in nullfs(5) which could cause a system panic have been fixed.[r232665]

FreeBSD ZFS subsystem has been updated to support feature flags for ZFS pools (the SPA version is 5000). Asynchronous destroy of ZFS dataset, LZ4 compression, ZIO NOP-write optimization have been implemented as new features. loader(8) tunables vfs.zfs.sync_pass_deferred_free, vfs.zfs.sync_pass_dont_compress, vfs.zfs.sync_pass_rewrite, and vfs.zfs.nopwrite_enabled have been added.[r243717, r244088, r247310]

Note that this upgrade can cause interoperability issues when upgrading a FreeBSD 8.4 system to 9.0 or 9.1. This is because FreeBSD 9.0 and 9.1 support SPA version 28 and do not recognize version 5000. To mitigate this issue, the default SPA version for a newly created ZFS pool on FreeBSD 8.4 is set to version 28. To create a ZFS pool with version 5000, use zpool(8) upgrade command after the creation.

A bug in ZFS subsystem which could cause a system panic when importing a ZFS pool has been fixed.[r246578]

The sysctl(8) variable vfs.zfs.txg.timeout has been changed from read-only to writable.[r235507]

2.3 Userland Changes

The load average limit in the atrun(8) utility has been set based on the number of CPUs.[r242991]

The chkgrp(8) utility now supports a -q flag to disable printing of text when the group format is correct.[r244064]

The crontab(1) utility now waits for a second before updating the spool directory's mtime. It could happen that the modified crontab updated the mtime of the spool directory, and then crontab(1) utility updated the mtime again within a second. In this case, the crontab database is not updated properly.[r239877]

The cut(1) utility now supports a -w flag to specify whitespace as the delimiter.[r244305]

The default dot.cshrc file for csh(1) and tcsh(1) has been changed. For more detail, see /usr/share/skel/dot.cshrc.[r234979, r242642]

The daemon(8) utility now supports an -r flag to restart the program if it has been terminated.[r233762]

The devd(8) daemon now supports the ! character in regex matching in devd.conf(5). It inverts the logic of the matching.[r247768]

The devfs(5) mount now supports ruleset=number mount option and updating the existing mount by using -u flag in the mount(8) utility. This new option sets the specified ruleset number as the active ruleset of the new devfs mount and applies all its rules at mount time. If the specified ruleset doesn't exist, a new empty ruleset is created.[r233867]

The du(1) utility now supports a -g flag to display the results in gigabytes.[r247539]

The fetch(1) utility now supports percent-encoded strings in user and password component of a URL.[r235254]

The maximum number of HTTP redirections has been increased from 5 to 20 in the fetch(1) utility.[r242034]

The fetch(1) utility now supports HTTP status codes 305 (Use Proxy) and 308 (Permanent Redirect).[r242288, r242291]

A countermeasure against possible DoS (Denial of Service) attack described in CVE-2010-2632 in the ftpd(8) daemon has been implemented.[r246357]

A new environment variable PROFIL_USE_PID has been added to generate profiling data for the gprof(1) utility with a filename including the process ID.[r235084]

The ifconfig(8) now supports a state option for carp(4) protocol to set the state of a carp cluster. Valid state keywords are master and backup.[r243466]

A bug in the inetd(8) daemon which could cause wrong accounting for elapsed time has been fixed.[r236875]

The inetd(8) daemon now set the listen queue size to the value of kern.ipc.somaxconn instead of hardcoded value 64.[r246403]

The default ip6addrctl(8) address selection policy for IPv4 and IPv6 has been updated to one in RFC 6724.[r246599]

The kdump(1) utility now supports a -p pid option to accept either a process ID or a thread ID.[r237790]

The lastcomm(1) utility now supports a +format option to specify strftime(3) format for process start and exit times.[r235888]

The libedit library has been updated to a NetBSD snapshot as of 28 December, 2009.[r237739]

The libpmc library has been updated to support more PMCs (Performance Monitoring Counters) in Intel Core i7 and Xeon 5500 family based on Intel documentation as of October 2011. Specifically, DTLB_MISSES.PDE_MISS and DTLB_MISSES.LARGE_WALK_COMPLETED have been added.[r234045]

The libradius now supports the rad_bind_to(3) function.[r234555]

The libusb(3) library now supports a libusb_get_max_iso_packet_size(3) function.[r235017]

A bug in the the libutil library has been fixed. It could prevent configuration of priority class capability in /etc/login.conf (LOGIN_SETPRIORITY in setusercontext(3) function) from working when the password is not set.[r233153]

The make(1) utility has been updated to version 8201210080. It now supports -V ${VAR} variable expansion, and :tu and :tl variable modifiers.[r241368]

The mktemp(1) utility now uses tmp as the default prefix when -t is not specified.[r241422]

The mv(1) utility now supports a -h flag. This forces it to treat a symbolic link to a directory for the target as a symbolic instead of a directory.[r241321]

The pam_exec(8) module now supports return_prog_exit_status. When this option is enabled, the program exit status is used as the pam_exec(8) return code. It allows the program to tell why the step failed (user unknown, for example).[r234843]

A bug in pam_unix(8) module has been fixed. It could prevent passwordtime login capability in login.conf(5) from working.[r234741]

The pciconf(8) utility now supports a -e flag to display PCI error details in listing mode. When this is specified, the status of any error bits in the PCI status register and PCI-express device status register will be displayed. It also lists any errors indicated by version 1 of PCI-express Advanced Error Reporting (AER).[r237732]

A workaround has been implemented in the ppp(8) daemon to support some 3G modems which return a wrong signature in echo packets and make it impossible to use LQR and ECHO.[r242198]

The procstat(1) utility now displays osreldate in binary information for a process.[r233953]

The procstat(1) utility now displays superpage mapping flag in the process virtual memory mappings.[r238752]

The procstat(1) and fstat(1) utilities now shows pathname associated with a shared memory object.[r236699]

The ps(1) utility now supports cow keyword to show the number of copy-on-write faults in a process.[r236306]

The ps(1) utility now supports dsiz and ssiz keywords to show data and stack size respectively.[r241159]

The rarpd(8) daemon now supports vlan(4) interface and -P option to specify the PID file. When -a flag is specified, /var/run/rarpd.ifname.pid is used as the PID filename by default.[r245077]

A bug in the remquo(3) functions where the quotient did not always have the correct sign when the remainder was 0, and another bug that the remainder and quotient were both off by a bit in certain cases involving subnormal remainders, have been fixed. Note that these bugs affected all platforms except amd64 and i386.[r234534]

The rtld(1) dynamic linker has been improved in performance of TLS (Thread Local Storage) handling.[r233067]

The setbuf(1) utility and libstdbuf library have been added. This controls the default buffering behavior of standard stdio streams.[r235141]

The sh(1) program now allows underscore characters in the arithmetic expansion.[r234001]

The sockstat(1) utility now supports a -j jid option to specify the socket list to be limited to a specific jail(8) ID.[r237672]

A variable NO_FOO in src.conf(5) now overrides WITH_FOO.[r241969]

The syslogd(8) daemon now supports IPv6 destination address in syslog.conf(5).[r241472]

The systat(1) utility now accepts fractional number of seconds.[r243684]

The tcpdrop(8) utility now allows addresses and ports to be separated by a colon or period rather than a space to permit directly pasting the output of commands such as netstat and sockstat on the command line.[r247563]

The top(1) utility now displays ZFS ARC memory usage on hosts using ZFS.[r239751]

A bug in traceroute(8) utility which could result in not accepting any incoming packets has been fixed.[r235163]

The unzip(1) program now supports a -Z flag to enable zipinfo mode.[r234331]

The usbdump(8) utility now supports filtering USB devices and USB endpoints.[r235015]

The usbhidctl(1) utility now supports a -z flag for reading operation. It allows to not request current values from the device, but only receive changes.[r235881]

Performance of the zfs(8) list -t snapshot command has been dramatically improved.[r233862]

The zfs(8) get command now supports a -t datatype option.[r233862]

The zfs(8) jail and unjail commands now support a jail name as well as a jail ID.[r246750]

The zfs(8) send command now reports transmitted data size in bytes when -v flag is specified.[r235952]

Changing zfs(8) canmount property to on no longer causes remount of the ZFS dataset when a dataset is already mounted.[r237457]

2.3.1 /etc/rc.d Scripts

The rc.d scripts now display script filename running to standard error when SIGINFO is issued. This message was sent to standard output and could prevent redirection from working.[r232549]

The rc.d/jail script now supports a jail_parameters variable to specify extra parameters for each jail.[r242083]

The service(8) utility now supports a -R flag to restart all third party services in /usr/local/etc/rc.d.[r246609]

2.4 Contributed Software

AWK has been updated to 20121220.[r246374]

ISC BIND has been updated to version 9.8.4-P2.[r248807]

BZIP2 has been updated to version 1.0.6.[r247448]

TENEX C shell ( tcsh(1)) has been updated to version 6.18.01.[r232635]

LESS ( less(1)) has been updated to version v451.[r240160]

libexpat has been updated to version 2.1.0.[r247514]

netcat has been updated to a version as of OpenBSD 5.2.[r243819]

OpenSSH has been updated to version 6.1.[r247521]

OpenSSL has been updated to version 0.9.8y.[r248057]

sendmail has been updated to version 8.14.7.[r250167]

The timezone database has been updated to tzdata2012j release.[r243006]

XZ has been updated to version 5.0.4.[r245129]

2.5 Ports/Packages Collection Infrastructure

The pkg(8) command has been added. This is used as a bootstrap tool for ports-mgmt/pkg in the Ports Collection.[r239563]

The pkg_add(1) utility now supports PACKAGESUFFIX to specify extension in a package filename.[r240674]

The pkg_create(1) program now allows a relative pathname in the -p option.[r233686]

2.6 Release Engineering and Integration

The supported version of the KDE desktop environment (x11/kde4) has been updated from 4.7.4 to 4.10.1.

3 Upgrading from previous releases of FreeBSD

[amd64, i386] Upgrades between RELEASE versions (and snapshots of the various security branches) are supported using the freebsd-update(8) utility. The binary upgrade procedure will update unmodified userland utilities, as well as unmodified GENERIC kernel distributed as a part of an official FreeBSD release. The freebsd-update(8) utility requires that the host being upgraded has Internet connectivity.

An older form of binary upgrade is supported through the Upgrade option from the main sysinstall(8) menu on CDROM distribution media. This type of binary upgrade may be useful on non-i386, non-amd64 machines or on systems with no Internet connectivity.

Source-based upgrades (those based on recompiling the FreeBSD base system from source code) from previous versions are supported, according to the instructions in /usr/src/UPDATING.

Important: Upgrading FreeBSD should, of course, only be attempted after backing up all data and configuration files.

This file, and other release-related documents, can be downloaded from ftp://ftp.FreeBSD.org/.

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.

For questions about this documentation, e-mail <doc@FreeBSD.org>.

diff --git a/website/content/en/releases/8.4R/relnotes.html b/website/content/en/releases/8.4R/relnotes.html index b878561562..856e6e6b4d 100644 --- a/website/content/en/releases/8.4R/relnotes.html +++ b/website/content/en/releases/8.4R/relnotes.html @@ -1,290 +1,290 @@ FreeBSD 8.4-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.4-RELEASE Release Notes

Important: All users are encouraged to consult the release errata before installing FreeBSD or submitting a problem report. The errata document is updated with late-breaking information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 8.4-RELEASE can be found on the FreeBSD Web site.

Other Release Documentation for 8.4-RELEASE

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


diff --git a/website/content/en/releases/8.4R/schedule.html b/website/content/en/releases/8.4R/schedule.html index 2197009a3c..b40403f407 100644 --- a/website/content/en/releases/8.4R/schedule.html +++ b/website/content/en/releases/8.4R/schedule.html @@ -1,385 +1,385 @@ FreeBSD 8.4 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 8.4 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list.

Schedule

- + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - +
Action Expected Actual Description
Initial release schedule announcement -08 February 201308 February 2013 Release Engineers send announcement email to developers with a rough schedule.
Announce doc/ tree slush -28 February 201328 February 2013 Notification of the impending doc/ tree slush should be sent to doc@.
Code freeze begins08 March 201308 March 201308 March 201308 March 2013 Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA120 March 201322 March 201320 March 201322 March 2013 First beta test snapshot.
doc/ tree slush17 March 201317 March 201317 March 201317 March 2013 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 freeze30 March 201330 March 201330 March 201330 March 2013 Only security updates and critical fixes will be allowed to the tree during this freeze.
releng/8.4 branch18 March 201328 March 201318 March 201328 March 2013 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
RC130 March 201310 April 201330 March 201310 April 2013 First release candidate.
RC221 April 201322 April 201321 April 201322 April 2013 Second release candidate.
RC330 April 20138 May 201330 April 20138 May 2013 Third release candidate.
RELEASE build02 June 201302 June 201302 June 201302 June 2013 8.4-RELEASE build.
RELEASE announcement07 June 201307 June 201307 June 201307 June 2013 8.4-RELEASE press release.
Turn over to the secteam -16 June 201316 June 2013 releng/8.4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

diff --git a/website/content/en/releases/9.0R/announce.html b/website/content/en/releases/9.0R/announce.html index b2ddf5c92e..09732d1ca5 100644 --- a/website/content/en/releases/9.0R/announce.html +++ b/website/content/en/releases/9.0R/announce.html @@ -1,644 +1,644 @@ FreeBSD 9.0-RELEASE Announcement
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 9.0-RELEASE Announcement

The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 9.0-RELEASE. This is the first release from the stable/9 branch, which improves on stable/8 and adds many new features. Some of the highlights:

  • A new installer, bsdinstall(8) has been added and is the installer used by the ISO images provided as part of this release

  • The Fast Filesystem now supports softupdates journaling

  • ZFS updated to version 28

  • Updated ATA/SATA drivers support AHCI, moved into updated CAM framework

  • Highly Available Storage (HAST) framework

  • Kernel support for Capsicum Capability Mode, an experimental set of features for sandboxing support

  • User-level DTrace

  • The TCP/IP stack now supports pluggable congestion control framework and five congestion control algorithm implementations available

  • NFS subsystem updated, new implementation supports NFSv4 in addition to NFSv3 and NFSv2

  • High Performance SSH (HPN-SSH)

  • Flattened device tree (FDT), simplifying FreeBSD configuration for embedded platforms

  • The powerpc architecture now supports Sony Playstation 3

  • The LLVM compiler infrastructure and clang have been imported

  • Gnome version 2.32.1, KDE version 4.7.3

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

For more information about FreeBSD release engineering activities please see:

Dedication

The FreeBSD Project dedicates the FreeBSD 9.0-RELEASE to the memory of Dennis M. Ritchie, one of the founding fathers of the UNIX[tm] operating system. It is on the foundation laid by the work of visionaries like Dennis that software like the FreeBSD operating system came to be. The fact that his work of so many years ago continues to influence new design decisions to this very day speaks for the brilliant engineer that he was.

May he rest in peace.

Availability

FreeBSD 9.0-RELEASE is now available for the amd64, i386, ia64, powerpc, powerpc64, and sparc64 architectures.

FreeBSD 9.0 can be installed from bootable ISO images or over the network. Some architectures also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.

NOTE: A problem was discovered with the DVD images for amd64 and i386 architectures shortly after they were loaded on the FTP distribution server. Those images have since been replaced and we have allowed enough time that the newer images should have distributed to all the FTP servers that carry the release. If you downloaded the amd64 or i386 DVD images prior to this announcement it would be a good idea to verify the checksums of the image you downloaded with the checksums provided as part of this Release Announcement. The only thing wrong with the images that were replaced is that sysinstall(8) can not be used to install the pre-built packages on the DVD. Other than that there is nothing different on the updated images. The bad DVD images were never available on BitTorrent.

MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1

This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages aimed at getting a graphical workstation up and running. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

disc1

This contains the base FreeBSD operating system. It also supports booting into a "livefs" based rescue mode. There are no pre-built packages.

bootonly

This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.

memstick

This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. There are no pre-built packages.

As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:

# dd if="FreeBSD"-9.0-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"

Be careful to make sure you get the target (of=) correct.

FreeBSD 9.0-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 9.0-based products is:

BitTorrent

9.0-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:

FTP

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

However before trying these sites 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:

For instructions on installing FreeBSD or updating an existing machine to 9.0-RELEASE please see:

Support

The FreeBSD Security Team currently plans to support FreeBSD 9.0 until January 31st, 2013. For more information on the Security Team and their support of the various FreeBSD branches see:

Other Projects Based on FreeBSD

There are many "third party" Projects based on FreeBSD. The Projects range from re-packaging FreeBSD into a more "novice friendly" distribution to making FreeBSD available on Amazon's EC2 infrastructure. For more information about these Third Party Projects see:

Acknowledgments

Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 9.0 including The FreeBSD Foundation, Yahoo!, NetApp, Internet Systems Consortium, Sentex Communications, New York Internet, Juniper Networks, and iXsystems.

The release engineering team for 9.0-RELEASE includes:

- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
Ken Smith <kensmith@FreeBSD.org>Ken Smith <kensmith@FreeBSD.org> Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination
Robert Watson <rwatson@FreeBSD.org>Robert Watson <rwatson@FreeBSD.org> Release Engineering, Security
Konstantin Belousov <kib@FreeBSD.org>Konstantin Belousov <kib@FreeBSD.org> Release Engineering
Marc Fonvieille <blackend@FreeBSD.org>Marc Fonvieille <blackend@FreeBSD.org> Release Engineering, Documentation
Josh Paetzel <jpaetzel@FreeBSD.org>Josh Paetzel <jpaetzel@FreeBSD.org> Release Engineering
Hiroki Sato <hrs@FreeBSD.org>Hiroki Sato <hrs@FreeBSD.org> Release Engineering, Documentation
Bjoern Zeeb <bz@FreeBSD.org>Bjoern Zeeb <bz@FreeBSD.org> Release Engineering
Marcel Moolenaar <marcel@FreeBSD.org>Marcel Moolenaar <marcel@FreeBSD.org> ia64, powerpc Release Building
Nathan Whitehorn <nwhitehorn@FreeBSD.org>Nathan Whitehorn <nwhitehorn@FreeBSD.org> powerpc64 Release Building
Joe Marcus Clarke <marcus@FreeBSD.org>Joe Marcus Clarke <marcus@FreeBSD.org> Package Building
Erwin Lansing <erwin@FreeBSD.org>Erwin Lansing <erwin@FreeBSD.org> Package Building
Mark Linimon <linimon@FreeBSD.org>Mark Linimon <linimon@FreeBSD.org> Package Building
Pav Lucistnik <pav@FreeBSD.org>Pav Lucistnik <pav@FreeBSD.org> Package Building
Ion-Mihai Tetcu <itetcu@FreeBSD.org>Ion-Mihai Tetcu <itetcu@FreeBSD.org> Package Building
Martin Wilke <miwi@FreeBSD.org>Martin Wilke <miwi@FreeBSD.org> Package Building, Ports Security
Colin Percival <cperciva@FreeBSD.org>Colin Percival <cperciva@FreeBSD.org> Security Officer

Trademark

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums

MD5 (FreeBSD-9.0-RELEASE-amd64-bootonly.iso) = 477019a305797186a8b3e4147f44edec
 MD5 (FreeBSD-9.0-RELEASE-amd64-disc1.iso) = b23ef73412bd50ed62ef8613ca1a4199
 MD5 (FreeBSD-9.0-RELEASE-amd64-dvd1.iso) = 61221643ebeefeeb74bd552311e07070
 MD5 (FreeBSD-9.0-RELEASE-amd64-memstick.img) = b37217292ad626d6ab2d3a9c1d215d2d
MD5 (FreeBSD-9.0-RELEASE-i386-bootonly.iso) = 70b4b0dd42c309da79ce63ba2789cfe3
 MD5 (FreeBSD-9.0-RELEASE-i386-disc1.iso) = 5bf615f286ee6eeb3ecce45bd8d1622c
 MD5 (FreeBSD-9.0-RELEASE-i386-dvd1.iso) = fee32ba2041285b971daf7ea429e36e4
 MD5 (FreeBSD-9.0-RELEASE-i386-memstick.img) = 79ddd8f3422e209ae9bd11fee4e399eb
MD5 (FreeBSD-9.0-RELEASE-ia64-bootonly.iso) = 5c83f9a5bf359b2971059d1664ef5f7e
 MD5 (FreeBSD-9.0-RELEASE-ia64-memstick) = ee1d5196eb281966b9ef95b953a36d8d
 MD5 (FreeBSD-9.0-RELEASE-ia64-release.iso) = 73ca213db21379eb2527dcea37eeb824
MD5 (FreeBSD-9.0-RELEASE-powerpc-bootonly.iso) = bfe036760daac0cddfe8ce2915eaec54
 MD5 (FreeBSD-9.0-RELEASE-powerpc-memstick) = e7a09f343ee248ee538954b39549c241
 MD5 (FreeBSD-9.0-RELEASE-powerpc-release.iso) = 2431f52b2f9cc1951b0e568b3cd0f126
MD5 (FreeBSD-9.0-RELEASE-powerpc64-bootonly.iso) = 377714742e5f2e16e34b7818347d4e3f
 MD5 (FreeBSD-9.0-RELEASE-powerpc64-memstick) = 9e4ee64a7460c3c930d0e3e2e3cd03b9
 MD5 (FreeBSD-9.0-RELEASE-powerpc64-release.iso) = 347e51ceb3e65c1eff3cc3acdb519ffb
MD5 (FreeBSD-9.0-RELEASE-sparc64-bootonly.iso) = 81778b8ee1a8881b8597ee4275cc3b4e
 MD5 (FreeBSD-9.0-RELEASE-sparc64-disc1.iso) = a63a07e3c45275568db2cead1b3e7167
SHA256 (FreeBSD-9.0-RELEASE-amd64-bootonly.iso) = d16fd5f32c9483177a01241f37ed84f347484c65e52aba4dbf8a2f3108fb457d
 SHA256 (FreeBSD-9.0-RELEASE-amd64-disc1.iso) = bcc69320cd2f227411d55967113abc8ffa5ede0a6526090ca3fb5ab776fead9d
 SHA256 (FreeBSD-9.0-RELEASE-amd64-dvd1.iso) = f338e24645f0bcc792b8417411ed737d8057cd2f470f9d2b601c143352d6d459
 SHA256 (FreeBSD-9.0-RELEASE-amd64-memstick.img) = b8c964f362200d758e06dc6ea8dd556a4d6fedc2f3cd44c300318d9c2f4fb7a5
SHA256 (FreeBSD-9.0-RELEASE-i386-bootonly.iso) = e655de649040269ffdaa40179c3b91c59c8febef7486e340c3a5a5493097366d
 SHA256 (FreeBSD-9.0-RELEASE-i386-disc1.iso) = b03df5fbd345781cab7dcab1fd0ea4d84c7c48712a6035476a709e6c0d5763f0
 SHA256 (FreeBSD-9.0-RELEASE-i386-dvd1.iso) = ebc75ecdbd0580fbe9e59373962e0fc452c4480082af563e5cd765aca1ecd705
 SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img) = 99193a7895109d415936ba89e4f2c24227af48f064073dee7c4b49722c3656f8
SHA256 (FreeBSD-9.0-RELEASE-ia64-bootonly.iso) = 1d25fc52d868877eb3cbdc012be895827f9c2bd808f886755d7ca2e9257af108
 SHA256 (FreeBSD-9.0-RELEASE-ia64-memstick) = af147d20765bdbe6f71a8fb113fdba64de4d152b554c1fc8d78dc6f941e4737c
 SHA256 (FreeBSD-9.0-RELEASE-ia64-release.iso) = 289f31e0dadfa46f51e9a44e26cd9cf6652ff4b5a631a21dca065dcd0d66890d
SHA256 (FreeBSD-9.0-RELEASE-powerpc-bootonly.iso) = 7ca03f71d2dd0cad929d0005601b4c994a54b02ab140d4218fa326b0fce7dad8
 SHA256 (FreeBSD-9.0-RELEASE-powerpc-memstick) = 042bb4d473b615cf0d3c46d48d4db1fb457a54695e6ef3e47ee1b2dc6a4f3d9b
 SHA256 (FreeBSD-9.0-RELEASE-powerpc-release.iso) = 0a7af5c74ebc0e13e79dfde03d54d3d752f3c71aff39659406ad6e5bcc0cefc3
SHA256 (FreeBSD-9.0-RELEASE-powerpc64-bootonly.iso) = 2eb5f141fb702a9c757f91a54ff8ea5ded13d51b29dfa86e5ba6bfbe9bb8e48e
 SHA256 (FreeBSD-9.0-RELEASE-powerpc64-memstick) = 91648a0377cd4cf8dc5453e48416dd16ac99a30e5439534053a1ca16f9944a0d
 SHA256 (FreeBSD-9.0-RELEASE-powerpc64-release.iso) = 17ab67fe62e1da232038b1ff598be1aef5fe8ccea620e0fbd67d8e262992fd66
SHA256 (FreeBSD-9.0-RELEASE-sparc64-bootonly.iso) = 1f633899cf42be1fecc61f82aa9fd9197da0cf88dda25aabbbf67250653459f5
 SHA256 (FreeBSD-9.0-RELEASE-sparc64-disc1.iso) = 8414abb3a501a9f712fe137a2f3667249ab3d2666815a877a93c934ced5d1110

diff --git a/website/content/en/releases/9.0R/relnotes.html b/website/content/en/releases/9.0R/relnotes.html index 53f5fb953a..c24eedbd95 100644 --- a/website/content/en/releases/9.0R/relnotes.html +++ b/website/content/en/releases/9.0R/relnotes.html @@ -1,580 +1,580 @@ FreeBSD 9.0-RELEASE Release Notes
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 9.0-RELEASE Release Notes

Important: If you are upgrading from a previous release of FreeBSD, please read upgrading section in the Release Notes for notable incompatibilities carefully.

Release Highlights

The highlights in the 9.0-RELEASE are the following. For more details, please see the Detailed Release Notes.

  • The FreeBSD kernel now supports Capsicum Capability Mode. Capsicum is a set of features for sandboxing support, using a capability model in which the capabilities are file descriptors. Two new kernel options CAPABILITIES and CAPABILITY_MODE have been added to the GENERIC kernel. For more information about Capsicum, see http://www.cl.cam.ac.uk/research/security/capsicum/.[r219129]

  • The hhook(9) (Helper Hook) and khelp(9) (Kernel Helpers) KPIs have been implemented. These are a kind of superset of pfil(9) framework for more general use in the kernel. The hhook(9) KPI provides a way for kernel subsystems to export hook points that khelp(9) modules can hook to provide enhanced or new functionality to the kernel. The khelp(9) KPI provides a framework for managing khelp(9) modules, which indirectly use the hhook(9) KPI to register their hook functions with hook points of interest within the kernel. These allow a structured way to dynamically extend the kernel at runtime in an ABI preserving manner.[r216758, r216615]

  • A new resource accounting API has been implemented. It can keep per-process, per-jail, and per-loginclass resource accounting information. Note that this is not built nor installed by default. To build and install them, specify options RACCT in the kernel configuration file and rebuild the base system as described in the FreeBSD Handbook.[r220137]

  • A new resource-limiting API has been implemented. It works in conjunction with the RACCT resource accounting implementation and takes user-configurable actions based on the set of rules it maintains and the current resource usage. The rctl(8) utility has been added to manage the rules in userland. Note that this is not built nor installed by default. To build and install them, specify options RCTL in the kernel configuration file and rebuild the base system as described in the FreeBSD Handbook.[r220163]

  • [powerpc] FreeBSD/powerpc now supports Sony Playstation 3 using the OtherOS feature available on firmwares 3.15 and earlier.[r217044]

  • [amd64, i386] The FreeBSD usb(4) subsystem now supports USB 3.0 by default.[r223098]

  • The FreeBSD usb(4) subsystem now supports USB packet filter. This allows to capture packets which go through each USB host controller. The implementation is almost based on bpf(4) code. The userland program usbdump(8) has been added.[r215649]

  • A bxe(4) driver for Broadcom NetXtreme II 10GbE controllers (BCM57710, BCM57711, BCM57711E) has been added.[r219647]

  • A cxgbe(4) driver for Chelsio T4 (Terminator 4) based 10Gb/1Gb adapters has been added.[r218794]

  • The em(4) driver has been updated to version 7.3.2.[r219753]

  • The igb(4) driver has been updated to version 2.2.5.[r223350]

  • The igb(4) driver now supports Intel I350 PCIe Gigabit Ethernet controllers.[r218530]

  • The ixgbe(4) driver has been updated to version 2.3.8.[r217593]

  • The re(4) driver now supports RTL8168E/8111E-VL PCIe Gigabit Ethernet controllers and RTL8401E PCIe Fast Ethernet controllers.[r217498, r218760]

  • A vte(4) driver for RDC R6040 Fast Ethernet controllers, which are commonly found on the Vortex86 System On a Chip, has been added.[r216829]

  • A vxge(4) driver for the Neterion X3100 10GbE Server/Storage adapter has been added.[r221167]

  • ipfw(8) now supports IPv6 in the fwd action.[r225044]

  • ipfw(8) now supports the call and return actions. Upon the call number action, the current rule number is saved in the internal stack and ruleset processing continues with the first rule numbered number or higher. The return action takes the rule number saved to internal stack by the latest call action and returns ruleset processing to the first rule with number greater than that saved number.[r223666]

  • For Infiniband support, OFED (OpenFabrics Enterprise Distribution) version 1.5.3 has been imported into the base system. Note that this is not built nor installed by default. To build and install them, specify WITH_OFED=yes in /etc/src.conf and rebuild the base system as described in the FreeBSD Handbook.[r219820]

  • The FreeBSD TCP/IP network stack now supports IPv4 prefixes with /31 as described in RFC 3021, “Using 31-Bit Prefixes on IPv4 Point-to-Point Links”.[r226572]

  • The FreeBSD TCP/IP network stack now supports the mod_cc(9) pluggable congestion control framework. This allows TCP congestion control algorithms to be implemented as dynamically loadable kernel modules. The following kernel modules are available as of 9.0-RELEASE: cc_chd(4) for the CAIA-Hamilton-Delay algorithm, cc_cubic(4) for the CUBIC algorithm, cc_hd(4) for the Hamilton-Delay algorithm, cc_htcp(4) for the H-TCP algorithm, cc_newreno(4) for the NewReno algorithm, and cc_vegas(4) for the Vegas algorithm. The default algorithm can be set by a new sysctl(8) variable net.inet.tcp.cc.algorithm. The value must be set to one of the names listed by net.inet.tcp.cc.available, and newreno is the default set at boot time. For more detail, see the mod_cc(4) and mod_cc(9) manual pages.[r216109, r216114, r216115, r218152, r218153, r218155]

  • An h_ertt(4) (Enhanced Round Trip Time) khelp(9) module has been added. This module allows per-connection, low noise estimates of the instantaneous RTT in the TCP/IP network stack with a robust implementation even in the face of delayed acknowledgments and/or TSO (TCP Segmentation Offload) being in use for a connection.[r217806]

  • A new tcp(4) socket option TCP_CONGESTION has been added. This allows to select or query the congestion control algorithm that the TCP/IP network stack will use for connections on the socket.[r218912]

  • The ng_netflow(4) netgraph(4) node now supports NetFlow version 9. A new export9 hook has been added for NetFlow v9 data. Note that data export can be done simultaneously in both version 5 and version 9.[r219183]

  • The geom_map(4) GEOM class has been added. This allows to generate multiple geom providers based on a hard-coded layout of a device with no explicit partition table such as embedded flash storage. For more information, see the geom_map(4) manual page.[r220559]

  • The graid(8) GEOM class has been added. This is a replacement of the ataraid(4) driver supporting various BIOS-based software RAID.[r219974]

  • A tws(4) driver for 3ware 9750 SATA+SAS 6Gb/s RAID controllers has been added.[r226115]

  • The FreeBSD Fast File System now supports softupdates journaling. It introduces a intent log into a softupdates-enabled file system which eliminates the need for background fsck(8) even on unclean shutdown. This can be enabled in a per-filesystem basis by using the -j flag of the newfs(8) utility or the -j enable option of the tunefs(8) utility. Note that the 9.0-RELEASE installer automatically enables softupdates journaling for newly-created UFS file systems.[r207141, r218726]

  • The FreeBSD Fast File System now supports the TRIM command when freeing data blocks. A new flag -t in the newfs(8) and tunefs(8) utilities sets the TRIM-enable flag for a file system. The TRIM-enable flag makes the file system send a delete request to the underlying device for each freed block. The TRIM command is specified as a Data Set Management Command in the ATA8-ACS2 standard to carry the information related to deleted data blocks to a device, especially for a SSD (Solid-State Drive) for optimization.[r216796]

  • The FreeBSD NFS subsystem has been updated. The new implementation supports NFS version 4 in addition to 2 and 3. The kernel options for the NFS server and client are changed from NFSSERVER and NFSCLIENT to NFSD and NFSCL. sysctl(8) variables which start with vfs.nfssrv. have been renamed to vfs.nfsd.. The NFS server now supports vfs.nfsd.server_max_nfsvers and vfs.nfsd.server_min_nfsvers sysctl(8) variables to specify the maximum and the minimum NFS version number which the server accepts. The default value is set to 3 and 2, respectively.[r221124]

  • The FreeBSD ZFS subsystem has been updated to the SPA (Storage Pool Allocator, also known as zpool) version 28. It now supports data deduplication, triple parity RAIDZ (raidz3), snapshot holds, log device removal, zfs diff, zpool split, zpool import -F, and read-only zpool import.[r219089]

  • An implementation of iconv() API libraries and utilities which are standardized in Single UNIX Specification has been imported. These are based on NetBSD's Citrus implementation. Note that these are not built nor installed by default. To build and install them, specify WITH_ICONV=yes in /etc/src.conf and rebuild the base system as described in the FreeBSD Handbook.[r219019]

  • A readline(3) API set has been imported into libedit. This is based on NetBSD's implementation and BSD licensed utilities now use it instead of GNU libreadline.[r220370]

  • The rtsold(8) and rtadvd(8) daemons now support the RDNSS and DNSSL options described in RFC 6106, “IPv6 Router Advertisement Options for DNS Configuration”. A rtadvctl(8) utility to control the rtadvd(8) daemon has been added.[r222732, r224006]

  • The rtld(1) runtime linker now supports shared objects as filters in ELF shared libraries. Both standard and auxiliary filtering have been supported. The rtld(1) linker's processing of a filter defers loading a filtee until a filter symbol is referenced unless the LD_LOADFLTR environment variable is defined or a -z loadfltr option was specified when the filter was created.[r216695]

  • A bug in the tftpd(8) daemon has been fixed. It had an interoperability issue when transferring a large file.[r224536]

  • The utmp(5) user accounting database has been replaced by utmpx(3). User accounting utilities will now use utmpx database files exclusively. The wtmpcvt(1) utility can be used to convert wtmp files to the new format, making it possible to read them using the updated utilities.[r202188]

  • The zpool(8): utility now supports a zpool labelclear command. This allows to wipe the label data from a drive that is not active in a pool.[r224171]

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


diff --git a/website/content/en/releases/9.0R/schedule.html b/website/content/en/releases/9.0R/schedule.html index fa453d5cb7..e04eec62b3 100644 --- a/website/content/en/releases/9.0R/schedule.html +++ b/website/content/en/releases/9.0R/schedule.html @@ -1,395 +1,395 @@ FreeBSD 9.0 Release Process
Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 9.0 Release Process

Introduction

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

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

- + - + - - + + - - + + - - + + - - + + - - + + - - + + - - + + - + - - + + - + - +
Action Expected Actual Description
Initial release schedule announcement -19 April 201119 April 2011 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder -6 May 2011,
15 June 2011		6 May 2011,
15 June 2011		 Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code freeze begins17 July 201118 July 201117 July 201118 July 2011 Release Engineers announce that all further commits to the head branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA120 July 20111 August 201120 July 20111 August 2011 First beta test snapshot.
BETA23 August 20117 September 20113 August 20117 September 2011 Second beta test snapshot.
releng/9.0 branch3 August 201110 November 20113 August 201110 November 2011 Subversion branch created, propagated to CVS; future release engineering proceeds on this branch.
BETA317 August 201128 September 201117 August 201128 September 2011 Third beta test snapshot.
RC124 August 201122 October 201124 August 201122 October 2011 First release candidate.
RC231 August 201117 November 201131 August 201117 November 2011 Second release candidate.
RC3 -8 December 20118 December 2011 Third release candidate.
RELEASE build7 September 20113 January 20127 September 20113 January 2012 9.0-RELEASE built.
RELEASE announcement -12 January 201212 January 2012 9.0-RELEASE press release.
Turn over to the secteam -16 February 201216 February 2012 RELENG_9_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Status / TODO

http://wiki.freebsd.org/Releng/9.0TODO

Additional Information