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>
39 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
43 <legalnotice xml:id="trademarks" role="trademarks">
53 <para>The release notes for &os; &release.current; contain
54 a summary of the changes made to the &os; base system on the
55 &release.branch; development line. This document lists
56 applicable security advisories that were issued since the last
57 release, as well as significant changes to the &os; kernel and
58 userland. Some brief remarks on upgrading are also
63 <sect1 xml:id="intro">
64 <title>Introduction</title>
66 <para>This document contains the release notes for &os;
67 &release.current;. It describes recently added, changed, or
68 deleted features of &os;. It also provides some notes on
69 upgrading from previous versions of &os;.</para>
71 <para releasetype="current">The &release.type; distribution to
72 which these release notes apply represents the latest point
73 along the &release.branch; development branch since
74 &release.branch; was created. Information regarding pre-built,
75 binary &release.type; distributions along this branch can be
77 xlink:href="&release.url;">&release.url;</uri>.</para>
79 <para releasetype="snapshot">The &release.type; distribution to
80 which these release notes apply represents a point along the
81 &release.branch; development branch between &release.prev; and
82 the future &release.next;. Information regarding pre-built,
83 binary &release.type; distributions along this branch can be
85 xlink:href="&release.url;">&release.url;</uri>.</para>
87 <para releasetype="release">This distribution of &os;
88 &release.current; is a &release.type; distribution. It can be
89 found at <uri xlink:href="&release.url;">&release.url;</uri> or
90 any of its mirrors. More information on obtaining this (or
91 other) &release.type; distributions of &os; can be found in the
93 xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
94 &os;</quote> appendix</link> to the <link
95 xlink:href="&url.books.handbook;/">&os;
96 Handbook</link>.</para>
98 <para>All users are encouraged to consult the release errata
99 before installing &os;. The errata document is updated with
100 <quote>late-breaking</quote> information discovered late in the
101 release cycle or after the release. Typically, it contains
102 information on known bugs, security advisories, and corrections
103 to documentation. An up-to-date copy of the errata for &os;
104 &release.current; can be found on the &os; Web site.</para>
108 <title>What's New</title>
110 <para>This section describes the most user-visible new or changed
111 features in &os; since &release.prev;.</para>
113 <para>Typical release note items document recent security
114 advisories issued after &release.prev;, new drivers or hardware
115 support, new commands or options, major bug fixes, or
116 contributed software upgrades. They may also list changes to
117 major ports/packages or release engineering practices. Clearly
118 the release notes cannot list every single change made to &os;
119 between releases; this document focuses primarily on security
120 advisories, user-visible changes, and major architectural
123 <sect2 xml:id="security">
124 <title>Security Advisories</title>
130 <sect2 xml:id="kernel">
131 <title>Kernel Changes</title>
135 <sect3 xml:id="kernel-virtualization">
136 <title>Virtualization Support</title>
141 <sect3 xml:id="kernel-arm">
142 <title>ARM Support</title>
147 <sect3 xml:id="boot">
148 <title>Boot Loader Changes</title>
153 <sect3 xml:id="proc">
154 <title>Hardware Support</title>
159 <title>Multimedia Support</title>
164 <sect4 xml:id="net-if">
165 <title>Network Interface Support</title>
171 <sect3 xml:id="net-proto">
172 <title>Network Protocols</title>
177 <sect3 xml:id="disks">
178 <title>Disks and Storage</title>
184 <title>File Systems</title>
190 <sect2 xml:id="userland">
191 <title>Userland Changes</title>
195 <sect3 xml:id="rc-scripts">
196 <title><filename>/etc/rc.d</filename> Scripts</title>
202 <sect2 xml:id="contrib">
203 <title>Contributed Software</title>
208 <sect2 xml:id="ports">
209 <title>Ports/Packages Collection Infrastructure</title>
214 <sect2 xml:id="releng">
215 <title>Release Engineering and Integration</title>
221 <title>Documentation</title>
227 <sect1 xml:id="upgrade">
228 <title>Upgrading from Previous Releases of &os;</title>
230 <para arch="amd64,i386">Binary upgrades between RELEASE versions
231 (and snapshots of the various security branches) are supported
232 using the &man.freebsd-update.8; utility. The binary upgrade
233 procedure will update unmodified userland utilities, as well as
234 unmodified <filename>GENERIC</filename> kernel distributed as
235 a part of an official &os; release. The &man.freebsd-update.8;
236 utility requires that the host being upgraded have Internet
239 <para>Source-based upgrades (those based on recompiling the &os;
240 base system from source code) from previous versions are
241 supported, according to the instructions in
242 <filename>/usr/src/UPDATING</filename>.</para>
245 <para>Upgrading &os; should only be attempted after
246 backing up <emphasis>all</emphasis> data and configuration