article.xml revision 266032
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">
5 %release;
6<!ENTITY % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN" "sponsor.ent">
7 %sponsor;
8<!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN" "vendor.ent">
9 %vendor;
10]>
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>
13
14  <author><orgname>The &os; Project</orgname></author>
15
16  <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/relnotes/article.xml 266032 2014-05-14 15:31:16Z gjb $</pubdate>
17
18  <copyright>
19    <year>2014</year>
20    <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
21      Project</holder>
22  </copyright>
23
24  <legalnotice xml:id="trademarks" role="trademarks">
25    &tm-attrib.freebsd;
26    &tm-attrib.ibm;
27    &tm-attrib.ieee;
28    &tm-attrib.intel;
29    &tm-attrib.sparc;
30    &tm-attrib.general;
31  </legalnotice>
32
33  <abstract>
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
40      presented.</para>
41  </abstract>
42</info>
43
44<sect1 xml:id="intro">
45  <title>Introduction</title>
46
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>
51
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>
58
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>
65
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>
74
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>
82</sect1>
83
84<sect1 xml:id="new">
85  <title>What's New</title>
86
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>
91
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>
100
101  <sect2 xml:id="security">
102    <title>Security Advisories</title>
103
104    <para>No advisories.</para>
105
106  </sect2>
107
108  <sect2 xml:id="kernel">
109    <title>Kernel Changes</title>
110
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>
114
115    <para revision="260903">Support for GPS ports has been added to
116      &man.uhso.4;.</para>
117
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>
122
123    <note>
124      <para>The <literal>if_nf10bmac(4)</literal> driver operates on
125	the FPGA, and is not suited for the PCI host interface.</para>
126    </note>
127
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
134      added.</para>
135
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>
140
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>
149
150    <note>
151      <para>At this time, the &man.mfiutil.8; utility and
152	the &os; version of
153	<application>MegaCLI</application> and
154	<application>StorCli</application> do not work with
155	&man.mrsas.4;.</para>
156    </note>
157
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&nbsp;&trade; enabled has been fixed.</para>
162
163    <sect3 xml:id="kernel-virtualization">
164      <title>Virtualization support</title>
165
166      <para revision="260410">Support for the <quote>Virtual Interrupt
167	  Delivery</quote> feature of &intel;&nbsp;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>
173
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>
181
182      <para revision="260582">Unmapped IO support has been added to
183	&man.virtio_blk.4;.</para>
184
185      <para revision="260583">Unmapped IO support has been added to
186	&man.virtio_scsi.4;.</para>
187
188      <para revision="260847">The &man.virtio_random.4; driver has
189	been added to harvest entropy from the host system.</para>
190    </sect3>
191
192    <sect3 xml:id="kernel-arm">
193      <title>ARM support</title>
194
195      <para revision="260921">The &man.nand.4; device is enabled for
196	ARM devices by default.</para>
197    </sect3>
198
199    <sect3 xml:id="boot">
200      <title>Boot Loader Changes</title>
201
202      <para>&nbsp;</para>
203    </sect3>
204
205    <sect3 xml:id="proc">
206      <title>Hardware Support</title>
207
208      <sect4 xml:id="mm">
209	<title>Multimedia Support</title>
210
211	<para>&nbsp;</para>
212      </sect4>
213
214      <sect4 xml:id="net-if">
215	<title>Network Interface Support</title>
216
217	<para revision="258830">Support for Broadcom chipsets
218	  BCM57764, BCM57767, BCM57782, BCM57786 and BCM57787 has
219	  been added to &man.bge.4;.</para>
220
221	<para revision="260448">Support for the &intel;
222	  Centrino&trade; Wireless-N 135 chipset has been
223	  added.</para>
224
225	<para revision="260552">Firmware for &intel;
226	  Centrino&trade; Wireless-N 105 devices has been added
227	  to the base system.</para>
228
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>
233
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>
237      </sect4>
238    </sect3>
239
240    <sect3 xml:id="net-proto">
241      <title>Network Protocols</title>
242
243      <para revision="263140">Support for the IPX network transport
244	protocol has been removed, and will not be supported in
245	&os;&nbsp;11 and later releases.</para>
246    </sect3>
247
248    <sect3 xml:id="disks">
249      <title>Disks and Storage</title>
250
251      <para>&nbsp;</para>
252    </sect3>
253
254    <sect3 xml:id="fs">
255      <title>File Systems</title>
256
257      <para>&nbsp;</para>
258
259      <sect4 xml:id="fs-zfs">
260	<title>ZFS</title>
261
262	<para>&nbsp;</para>
263      </sect4>
264    </sect3>
265  </sect2>
266
267  <sect2 xml:id="userland">
268    <title>Userland Changes</title>
269
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>
274
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>
279
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
285      device.</para>
286
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>
292
293    <para revision="260926">Support for displaying VPD for PCI devices
294      via &man.pciconf.8; has been added.</para>
295
296    <para revision="261498">&man.ping.8; protects against malicious
297      network packets using the Capsicum framework to drop
298      privileges.</para>
299
300    <para revision="261504">&os;/&arch.i386; guests can be run under
301      bhyve.</para>
302
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
308      host system.</para>
309
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>
313
314    <sect3 xml:id="rc-scripts">
315      <title><filename>/etc/rc.d</filename> Scripts</title>
316
317      <para>&nbsp;</para>
318    </sect3>
319  </sect2>
320
321  <sect2 xml:id="contrib">
322    <title>Contributed Software</title>
323
324    <para revision="258884" contrib="sponsor"
325      sponsor="&darpa_afrl;">&man.lldb.1; has been updated to upstream
326      snapshot version r196259.</para>
327
328    <para revision="259626">Timezone data files have been updated to
329      version 2013i.</para>
330
331    <para revision="260445">&man.byacc.1; has been updated to version
332      20140101.</para>
333
334    <para revision="261037"><application>OpenSSL</application> has
335      been updated to version 1.0.1.f.</para>
336
337    <para revision="261071">&man.jemalloc.3; has been updated to
338      version 3.5.0.</para>
339
340    <para revision="261197" role="merged"><application>Sendmail</application>
341      has been updated from 8.14.7 to 8.14.8.</para>
342
343    <para revision="261212"><application>bmake</application> has been
344      updated to version 20140101.</para>
345
346    <para revision="261283"><application>libc++</application> has been
347      updated to version 3.4.</para>
348
349    <para revision="261320"><application>OpenSSH</application> has
350      been updated to 6.5p1.</para>
351
352    <para revision="261344"><application>mdocml</application> has been
353      updated to version 1.12.3.</para>
354
355    <para revision="261991"><application>LLVM</application> and
356      <application>Clang</application> have been updated to
357      version 3.4.</para>
358  </sect2>
359
360  <sect2 xml:id="ports">
361    <title>Ports/Packages Collection Infrastructure</title>
362
363    <para>&nbsp;</para>
364  </sect2>
365
366  <sect2 xml:id="releng">
367    <title>Release Engineering and Integration</title>
368
369    <para>&nbsp;</para>
370  </sect2>
371
372  <sect2 xml:id="doc">
373    <title>Documentation</title>
374
375    <para>&nbsp;</para>
376  </sect2>
377</sect1>
378
379<sect1 xml:id="upgrade">
380  <title>Upgrading from previous releases of &os;</title>
381
382  <para arch="amd64,i386">Binary upgrades between RELEASE versions
383    (and snapshots of the various security branches) are supported
384    using the &man.freebsd-update.8; utility.  The binary upgrade
385    procedure will update unmodified userland utilities, as well as
386    unmodified GENERIC kernels distributed as a part of an official
387    &os; release.  The &man.freebsd-update.8; utility requires that
388    the host being upgraded have Internet connectivity.</para>
389
390  <para>Source-based upgrades (those based on recompiling the &os;
391    base system from source code) from previous versions are
392    supported, according to the instructions in
393    <filename>/usr/src/UPDATING</filename>.</para>
394
395  <important>
396    <para>Upgrading &os; should only be attempted after backing up
397      <emphasis>all</emphasis> data and configuration files.</para>
398  </important>
399</sect1>
400</article>
401