1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
3 "../../../share/xml/freebsd50.dtd" [
4 <!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent">
6 <!ENTITY % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN" "sponsor.ent">
8 <!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN" "vendor.ent">
11 <article xmlns="http://docbook.org/ns/docbook"
12 xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
15 <title>&os; &release.current; Release Notes</title>
18 <orgname>The &os; Project</orgname>
21 <pubdate>$FreeBSD$</pubdate>
40 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
44 <legalnotice xml:id="trademarks" role="trademarks">
54 <para>The release notes for &os; &release.current; contain
55 a summary of the changes made to the &os; base system on the
56 &release.branch; development line. This document lists
57 applicable security advisories that were issued since the last
58 release, as well as significant changes to the &os; kernel and
59 userland. Some brief remarks on upgrading are also
64 <sect1 xml:id="intro">
65 <title>Introduction</title>
67 <para>This document contains the release notes for &os;
68 &release.current;. It describes recently added, changed, or
69 deleted features of &os;. It also provides some notes on
70 upgrading from previous versions of &os;.</para>
72 <para releasetype="current">The &release.type; distribution to
73 which these release notes apply represents the latest point
74 along the &release.branch; development branch since
75 &release.branch; was created. Information regarding pre-built,
76 binary &release.type; distributions along this branch can be
78 xlink:href="&release.url;">&release.url;</uri>.</para>
80 <para releasetype="snapshot">The &release.type; distribution to
81 which these release notes apply represents a point along the
82 &release.branch; development branch between &release.prev; and
83 the future &release.next;. Information regarding pre-built,
84 binary &release.type; distributions along this branch can be
86 xlink:href="&release.url;">&release.url;</uri>.</para>
88 <para releasetype="release">This distribution of &os;
89 &release.current; is a &release.type; distribution. It can be
90 found at <uri xlink:href="&release.url;">&release.url;</uri> or
91 any of its mirrors. More information on obtaining this (or
92 other) &release.type; distributions of &os; can be found in the
94 xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
95 &os;</quote> appendix</link> to the <link
96 xlink:href="&url.books.handbook;/">&os;
97 Handbook</link>.</para>
99 <para>All users are encouraged to consult the release errata
100 before installing &os;. The errata document is updated with
101 <quote>late-breaking</quote> information discovered late in the
102 release cycle or after the release. Typically, it contains
103 information on known bugs, security advisories, and corrections
104 to documentation. An up-to-date copy of the errata for &os;
105 &release.current; can be found on the &os; Web site.</para>
109 <title>What's New</title>
111 <para>This section describes the most user-visible new or changed
112 features in &os; since &release.prev;.</para>
114 <para>Typical release note items document recent security
115 advisories issued after &release.prev;, new drivers or hardware
116 support, new commands or options, major bug fixes, or
117 contributed software upgrades. They may also list changes to
118 major ports/packages or release engineering practices. Clearly
119 the release notes cannot list every single change made to &os;
120 between releases; this document focuses primarily on security
121 advisories, user-visible changes, and major architectural
124 <sect2 xml:id="security">
125 <title>Security Advisories</title>
131 <sect2 xml:id="kernel">
132 <title>Kernel Changes</title>
136 <sect3 xml:id="kernel-virtualization">
137 <title>Virtualization Support</title>
142 <sect3 xml:id="kernel-arm">
143 <title>ARM Support</title>
148 <sect3 xml:id="boot">
149 <title>Boot Loader Changes</title>
154 <sect3 xml:id="proc">
155 <title>Hardware Support</title>
160 <title>Multimedia Support</title>
165 <sect4 xml:id="net-if">
166 <title>Network Interface Support</title>
172 <sect3 xml:id="net-proto">
173 <title>Network Protocols</title>
178 <sect3 xml:id="disks">
179 <title>Disks and Storage</title>
185 <title>File Systems</title>
191 <sect2 xml:id="userland">
192 <title>Userland Changes</title>
196 <sect3 xml:id="rc-scripts">
197 <title><filename>/etc/rc.d</filename> Scripts</title>
203 <sect2 xml:id="contrib">
204 <title>Contributed Software</title>
209 <sect2 xml:id="ports">
210 <title>Ports/Packages Collection Infrastructure</title>
215 <sect2 xml:id="releng">
216 <title>Release Engineering and Integration</title>
222 <title>Documentation</title>
228 <sect1 xml:id="upgrade">
229 <title>Upgrading from Previous Releases of &os;</title>
231 <para arch="amd64,i386">Binary upgrades between RELEASE versions
232 (and snapshots of the various security branches) are supported
233 using the &man.freebsd-update.8; utility. The binary upgrade
234 procedure will update unmodified userland utilities, as well as
235 unmodified <filename>GENERIC</filename> kernel distributed as
236 a part of an official &os; release. The &man.freebsd-update.8;
237 utility requires that the host being upgraded have Internet
240 <para>Source-based upgrades (those based on recompiling the &os;
241 base system from source code) from previous versions are
242 supported, according to the instructions in
243 <filename>/usr/src/UPDATING</filename>.</para>
246 <para>Upgrading &os; should only be attempted after
247 backing up <emphasis>all</emphasis> data and configuration