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" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
12 <info><title>&os; &release.current; Release Notes</title>
14 <author><orgname>The &os; Project</orgname></author>
16 <pubdate>$FreeBSD$</pubdate>
20 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
24 <legalnotice xml:id="trademarks" role="trademarks">
34 <para>The release notes for &os; &release.current; contain
35 a summary of the changes made to the &os; base system on the
36 &release.branch; development line. This document lists
37 applicable security advisories that were issued since the last
38 release, as well as significant changes to the &os; kernel and
39 userland. Some brief remarks on upgrading are also
44 <sect1 xml:id="intro">
45 <title>Introduction</title>
47 <para>This document contains the release notes for &os;
48 &release.current;. It describes recently added, changed, or
49 deleted features of &os;. It also provides some notes on
50 upgrading from previous versions of &os;.</para>
52 <para releasetype="current">The &release.type; distribution to which
53 these release notes apply represents the latest point along the
54 &release.branch; development branch since &release.branch; was
55 created. Information regarding pre-built, binary &release.type;
56 distributions along this branch can be found at <uri
57 xlink:href="&release.url;">&release.url;</uri>.</para>
59 <para releasetype="snapshot">The &release.type; distribution to
60 which these release notes apply represents a point along the
61 &release.branch; development branch between &release.prev; and the
62 future &release.next;. Information regarding pre-built, binary
63 &release.type; distributions along this branch can be found at
64 <uri xlink:href="&release.url;">&release.url;</uri>.</para>
66 <para releasetype="release">This distribution of &os;
67 &release.current; is a &release.type; distribution. It can be
68 found at <uri xlink:href="&release.url;">&release.url;</uri> or
69 any of its mirrors. More information on obtaining this (or other)
70 &release.type; distributions of &os; can be found in the <link
71 xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
72 &os;</quote> appendix</link> to the <link
73 xlink:href="&url.books.handbook;/">&os; Handbook</link>.</para>
75 <para>All users are encouraged to consult the release errata before
76 installing &os;. The errata document is updated with
77 <quote>late-breaking</quote> information discovered late in the
78 release cycle or after the release. Typically, it contains
79 information on known bugs, security advisories, and corrections to
80 documentation. An up-to-date copy of the errata for &os;
81 &release.current; can be found on the &os; Web site.</para>
85 <title>What's New</title>
87 <para>This section describes the most user-visible new or changed
88 features in &os; since &release.prev;. In general, changes
89 described here are unique to the &release.branch; branch unless
90 specifically marked as &merged; features.</para>
92 <para>Typical release note items document recent security advisories
93 issued after &release.prev;, new drivers or hardware support, new
94 commands or options, major bug fixes, or contributed software
95 upgrades. They may also list changes to major ports/packages or
96 release engineering practices. Clearly the release notes cannot
97 list every single change made to &os; between releases; this
98 document focuses primarily on security advisories, user-visible
99 changes, and major architectural improvements.</para>
101 <sect2 xml:id="security">
102 <title>Security Advisories</title>
104 <para>No advisories.</para>
108 <sect2 xml:id="kernel">
109 <title>Kernel Changes</title>
111 <para revision="260888">The <filename>VT</filename> kernel
112 configuration file has been added, which enables the new
113 <literal>vt</literal> console driver.</para>
115 <para revision="260903">Support for GPS ports has been added to
118 <para revision="264601" contrib="sponsor"
119 sponsor="&darpa_afrl;">The <literal>if_nf10bmac(4)</literal>
120 device has been added, providing support for NetFPGA-10G
121 Embedded CPU Ethernet Core.</para>
124 <para>The <literal>if_nf10bmac(4)</literal> driver operates on
125 the FPGA, and is not suited for the PCI host interface.</para>
128 <para revision="265132">The &man.full.4; device has been added,
129 and the <literal>lindev(4)</literal> device has been removed.
130 Prior to this change, <literal>lindev(4)</literal> provided only
131 the <filename>/dev/full</filename> character device, returning
132 <literal>ENOSPC</literal> on write attempts. As this device is
133 not specific to &linux;, a native &os; version has been
136 <para revision="265236" contrib="sponsor"
137 sponsor="&lsi;, &spectralogic;" sponsorurl="">The &man.mpr.4;
138 device has been added, providing support for LSI Fusion-MPT
139 3 12Gb SCSI/SATA controllers.</para>
141 <para revision="265555" contrib="sponsor"
142 sponsor="&lsi;">The &man.mrsas.4; driver has been added,
143 providing support for LSI MegaRAID SAS controllers. The
144 &man.mfi.4; driver will attach to the controller, by default.
145 To enable &man.mrsas.4; add
146 <literal>hw.mfi.mrsas_enable=1</literal> to
147 <filename>/boot/loader.conf</filename>, which turns off
148 &man.mfi.4; device probing.</para>
151 <para>At this time, the &man.mfiutil.8; utility and
153 <application>MegaCLI</application> and
154 <application>StorCli</application> do not work with
155 &man.mrsas.4;.</para>
158 <para revision="265876">A kernel bug that inhibited proper
159 functionality of the <literal>dev.cpu.0.freq</literal>
160 &man.sysctl.8; on &intel; processors with Turbo
161 Boost ™ enabled has been fixed.</para>
163 <sect3 xml:id="kernel-virtualization">
164 <title>Virtualization support</title>
166 <para revision="260410">Support for the <quote>Virtual Interrupt
167 Delivery</quote> feature of &intel; VT-x is enabled if
168 supported by the CPU. This feature can be disabled by running
169 <literal>sysctl hw.vmm.vmx.use_apic_vid=0</literal>.
170 Additionally, to persist this setting across reboots, add
171 <literal>hw.vmm.vmx.use_apic_vid=0</literal> to
172 <filename>/etc/sysctl.conf</filename>.</para>
174 <para revision="260532">Support for <quote>Posted Interrupt
175 Processing</quote> is enabled if supported by the CPU. This
176 feature can be disabled by running <literal>sysctl
177 hw.vmm.vmx.use_apic_pir=0</literal>. Additionally, to
178 persist this setting across reboots, add
179 <literal>hw.vmm.vmx.use_apic_pir=0</literal> to
180 <filename>/etc/sysctl.conf</filename>.</para>
182 <para revision="260582">Unmapped IO support has been added to
183 &man.virtio_blk.4;.</para>
185 <para revision="260583">Unmapped IO support has been added to
186 &man.virtio_scsi.4;.</para>
188 <para revision="260847">The &man.virtio_random.4; driver has
189 been added to harvest entropy from the host system.</para>
192 <sect3 xml:id="kernel-arm">
193 <title>ARM support</title>
195 <para revision="260921">The &man.nand.4; device is enabled for
196 ARM devices by default.</para>
199 <sect3 xml:id="boot">
200 <title>Boot Loader Changes</title>
205 <sect3 xml:id="proc">
206 <title>Hardware Support</title>
209 <title>Multimedia Support</title>
214 <sect4 xml:id="net-if">
215 <title>Network Interface Support</title>
217 <para revision="258830">Support for Broadcom chipsets
218 BCM57764, BCM57767, BCM57782, BCM57786 and BCM57787 has
219 been added to &man.bge.4;.</para>
221 <para revision="260448">Support for the &intel;
222 Centrino™ Wireless-N 135 chipset has been
225 <para revision="260552">Firmware for &intel;
226 Centrino™ Wireless-N 105 devices has been added
227 to the base system.</para>
229 <para revision="261975">The deprecated nve(4) driver has been
230 removed. Users of NVIDIA nForce MCP network adapters are
231 advised to use the &man.nfe.4; driver instead, which has been
232 the default driver for this hardware since &os; 7.0.</para>
234 <para revision="265348" contrib="sponsor"
235 sponsor="&netgate;">The &man.ath.hal.4; driver has been
236 updated to support the Atheros AR1111 chipset.</para>
240 <sect3 xml:id="net-proto">
241 <title>Network Protocols</title>
243 <para revision="263140">Support for the IPX network transport
244 protocol has been removed, and will not be supported in
245 &os; 11 and later releases.</para>
248 <sect3 xml:id="disks">
249 <title>Disks and Storage</title>
255 <title>File Systems</title>
259 <sect4 xml:id="fs-zfs">
267 <sect2 xml:id="userland">
268 <title>Userland Changes</title>
270 <para revision="258838" contrib="sponsor" sponsor="&ff;, &google;"
271 sponsorurl="">The &man.casperd.8; daemon has been added,
272 which provides access to functionality that is not available in
273 the <quote>capability mode</quote> sandbox.</para>
275 <para revision="260594">When unable to load a kernel module with
276 &man.kldload.8;, a message informing to view output of
277 &man.dmesg.8; is now printed, opposed to the previous output
278 <quote>Exec format error.</quote>.</para>
280 <para revision="260910">Allow &man.pciconf.8; to identify PCI
281 devices that are attached to a driver to be identified by their
282 device name instead of just the selector. Additionally, an
283 optional device argument to the <literal>-l</literal> flag
284 to restrict the output to only listing details about a single
287 <para revision="260913">A new flag, <quote>onifconsole</quote> has
288 been added to <filename>/etc/ttys</filename>. This allows the
289 system to provide a login prompt via serial console if the
290 device is an active kernel console, otherwise it is equivalent
291 to <literal>off</literal>.</para>
293 <para revision="260926">Support for displaying VPD for PCI devices
294 via &man.pciconf.8; has been added.</para>
296 <para revision="261498">&man.ping.8; protects against malicious
297 network packets using the Capsicum framework to drop
300 <para revision="261504">&os;/&arch.i386; guests can be run under
303 <para revision="265229">The &man.ps.1; utility has been
304 updated to include the <literal>-J</literal> flag, used to
305 filter output by matching &man.jail.8; IDs and names.
306 Additionally, argument <literal>0</literal> can be used to
307 <literal>-J</literal> to only list processes running on the
310 <para revision="265249">The &man.top.1; utility has been updated
311 to filter by &man.jail.8; ID or name, in followup to the
312 &man.ps.1; change in <literal>r265229</literal>.</para>
314 <para revision="265995">The Blowfish &man.crypt.3; default format
316 <literal>$2b$</literal>.</para>
318 <para revision="266209">The &man.pmcstat.8; utility has been
319 updated to include a new flag, <literal>-l</literal>, which
320 ends event collection after the specified number of
323 <para revision="266463">The default &man.newsyslog.conf.5; now
324 includes files in the
325 <filename>/etc/newsyslog.conf.d/</filename> and
326 <filename>/usr/local/etc/newsyslog.conf.d/</filename>
327 directories by default for &man.newsyslog.8;.</para>
329 <sect3 xml:id="rc-scripts">
330 <title><filename>/etc/rc.d</filename> Scripts</title>
336 <sect2 xml:id="contrib">
337 <title>Contributed Software</title>
339 <para revision="258884" contrib="sponsor"
340 sponsor="&darpa_afrl;">&man.lldb.1; has been updated to upstream
341 snapshot version r196259.</para>
343 <para revision="259626">Timezone data files have been updated to
344 version 2013i.</para>
346 <para revision="260445">&man.byacc.1; has been updated to version
349 <para revision="261037"><application>OpenSSL</application> has
350 been updated to version 1.0.1.f.</para>
352 <para revision="261071">&man.jemalloc.3; has been updated to
353 version 3.5.0.</para>
355 <para revision="261212"><application>bmake</application> has been
356 updated to version 20140101.</para>
358 <para revision="261283"><application>libc++</application> has been
359 updated to version 3.4.</para>
361 <para revision="261320"><application>OpenSSH</application> has
362 been updated to 6.5p1.</para>
364 <para revision="261344"><application>mdocml</application> has been
365 updated to version 1.12.3.</para>
367 <para revision="261991"><application>LLVM</application> and
368 <application>Clang</application> have been updated to
371 <para revision="266527" role="merged"><application>Sendmail</application>
372 has been updated from 8.14.7 to 8.14.9.</para>
374 <para revision="267256"><application>OpenSSL</application> has
375 been updated to version 1.0.1h.</para>
378 <sect2 xml:id="ports">
379 <title>Ports/Packages Collection Infrastructure</title>
384 <sect2 xml:id="releng">
385 <title>Release Engineering and Integration</title>
391 <title>Documentation</title>
397 <sect1 xml:id="upgrade">
398 <title>Upgrading from previous releases of &os;</title>
400 <para arch="amd64,i386">Binary upgrades between RELEASE versions
401 (and snapshots of the various security branches) are supported
402 using the &man.freebsd-update.8; utility. The binary upgrade
403 procedure will update unmodified userland utilities, as well as
404 unmodified GENERIC kernels distributed as a part of an official
405 &os; release. The &man.freebsd-update.8; utility requires that
406 the host being upgraded have Internet connectivity.</para>
408 <para>Source-based upgrades (those based on recompiling the &os;
409 base system from source code) from previous versions are
410 supported, according to the instructions in
411 <filename>/usr/src/UPDATING</filename>.</para>
414 <para>Upgrading &os; should only be attempted after backing up
415 <emphasis>all</emphasis> data and configuration files.</para>