summaryrefslogtreecommitdiffstats
path: root/release/doc/en_US.ISO8859-1/relnotes/article.xml
blob: 675dbdb6b3905c550e0f8d0a3c499a6e86f962c9 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
	"../../../share/xml/freebsd50.dtd" [
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent">
 %release;
]>
<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<info>
  <title>&os; &release.current; Release Notes</title>

  <author>
    <orgname>The &os; Project</orgname>
  </author>

  <pubdate>$FreeBSD$</pubdate>

  <copyright>
    <year>2000</year>
    <year>2001</year>
    <year>2002</year>
    <year>2003</year>
    <year>2004</year>
    <year>2005</year>
    <year>2006</year>
    <year>2007</year>
    <year>2008</year>
    <year>2009</year>
    <year>2010</year>
    <year>2011</year>
    <year>2012</year>
    <year>2013</year>
    <year>2014</year>
    <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
  </copyright>

  <legalnotice xml:id="trademarks" role="trademarks">
    &tm-attrib.freebsd;
    &tm-attrib.ibm;
    &tm-attrib.ieee;
    &tm-attrib.intel;
    &tm-attrib.sparc;
    &tm-attrib.general;
  </legalnotice>

  <abstract>
    <para>The release notes for &os; &release.current; contain
      a summary of the changes made to the &os; base system on the
      &release.branch; development line.  This document lists
      applicable security advisories that were issued since the last
      release, as well as significant changes to the &os; kernel and
      userland.  Some brief remarks on upgrading are also
      presented.</para>
  </abstract>
</info>

<sect1 xml:id="intro">
  <title>Introduction</title>

  <para>This document contains the release notes for &os;
    &release.current;.  It describes recently added, changed, or
    deleted features of &os;.  It also provides some notes on
    upgrading from previous versions of &os;.</para>

  <para releasetype="current">The &release.type; distribution to which
    these release notes apply represents the latest point along the
    &release.branch; development branch since &release.branch; was
    created.  Information regarding pre-built, binary &release.type;
    distributions along this branch can be found at <uri
      xlink:href="&release.url;">&release.url;</uri>.</para>

  <para releasetype="snapshot">The &release.type; distribution to
    which these release notes apply represents a point along the
    &release.branch; development branch between &release.prev; and the
    future &release.next;.  Information regarding pre-built, binary
    &release.type; distributions along this branch can be found at
    <uri xlink:href="&release.url;">&release.url;</uri>.</para>

  <para releasetype="release">This distribution of &os;
    &release.current; is a &release.type; distribution.  It can be
    found at <uri xlink:href="&release.url;">&release.url;</uri> or
    any of its mirrors.  More information on obtaining this (or other)
    &release.type; distributions of &os; can be found in the <link
      xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
	&os;</quote> appendix</link> to the <link
      xlink:href="&url.books.handbook;/">&os; Handbook</link>.</para>

  <para>All users are encouraged to consult the release errata before
    installing &os;.  The errata document is updated with
    <quote>late-breaking</quote> 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 &os;
    &release.current; can be found on the &os; Web site.</para>
</sect1>

<sect1 xml:id="new">
  <title>What's New</title>

  <para>This section describes the most user-visible new or changed
    features in &os; since &release.prev;.</para>

  <para>Typical release note items document recent security advisories
    issued after &release.prev;, 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 &os; between releases; this
    document focuses primarily on security advisories, user-visible
    changes, and major architectural improvements.</para>

  <sect2 xml:id="security">
    <title>Security Advisories</title>

    <para>&nbsp;</para>

  </sect2>

  <sect2 xml:id="kernel">
    <title>Kernel Changes</title>

    <para revision="260338">The <literal>vfs.zfs.zio.use_uma</literal>
      &man.sysctl.8; has been re-enabled.  On multi-CPU machines with
      enough RAM, this can easily double &man.zfs.8; performance or
      reduce CPU usage in half.  It was originally disabled due to
      memory and <acronym>KVA</acronym> exhaustion problem reports,
      which should be resolved due to several change in the VM
      subsystem.</para>

    <para revision="260385">The &man.geom.4; RAID driver has been
      updated to support unmapped I/O.</para>

    <para revision="260431">A new &man.sysctl.8;,
      <literal>kern.panic_reboot_wait_time</literal>, has been added,
      which allows controlling how long the system will wait after
      &man.panic.9; before rebooting.</para>

    <para revision="265388">The &man.mpr.4; device has been added,
      providing support for LSI Fusion-MPT 3 12Gb SCSI/SATA
      controllers.</para>

    <para revision="265922">The &man.mrsas.4; driver has been added,
      providing support for LSI MegaRAID SAS controllers.  The
      &man.mfi.4; driver will attach to the controller, by default.
      To enable &man.mrsas.4; add
      <literal>hw.mfi.mrsas_enable=1</literal> to
      <filename>/boot/loader.conf</filename>, which turns off
      &man.mfi.4; device probing.</para>

    <note>
      <para>At this time, the &man.mfiutil.8; utility and
	the &os; version of
	<application>MegaCLI</application> and
	<application>StorCli</application> do not work with
	&man.mrsas.4;.</para>
    </note>

    <para revision="266165">A kernel bug that inhibited proper
      functionality of the <literal>dev.cpu.0.freq</literal>
      &man.sysctl.8; on &intel; processors with Turbo
      Boost&nbsp;&trade; enabled has been fixed.</para>

    <sect3 xml:id="kernel-virtualization">
      <title>Virtualization support</title>

      <para>&nbsp;</para>

    </sect3>

    <sect3 xml:id="kernel-arm">
      <title>ARM support</title>

      <para>&nbsp;</para>

    </sect3>

    <sect3 xml:id="boot">
      <title>Boot Loader Changes</title>

      <para>&nbsp;</para>

    </sect3>

    <sect3 xml:id="proc">
      <title>Hardware Support</title>

      <para>&nbsp;</para>

      <sect4 xml:id="mm">
	<title>Multimedia Support</title>

	<para>&nbsp;</para>

      </sect4>

      <sect4 xml:id="net-if">
	<title>Network Interface Support</title>

	<para>&nbsp;</para>

      </sect4>
    </sect3>

    <sect3 xml:id="net-proto">
      <title>Network Protocols</title>

      <para>&nbsp;</para>

    </sect3>

    <sect3 xml:id="disks">
      <title>Disks and Storage</title>

      <para>&nbsp;</para>

    </sect3>

    <sect3 xml:id="fs">
      <title>File Systems</title>

      <para>&nbsp;</para>

    </sect3>
  </sect2>

  <sect2 xml:id="userland">
    <title>Userland Changes</title>

    <para revision="260177">A new flag is added to &man.camcontrol.8;,
      <literal>-b</literal>, which outputs the existing buses and
      their parents.</para>

    <para revision="266279">The &man.ps.1; utility has been
      updated to include the <literal>-J</literal> flag, used to
      filter output by matching &man.jail.8; IDs and names.
      Additionally, argument <literal>0</literal> can be used to
      <literal>-J</literal> to only list processes running on the
      host system.</para>

    <para revision="266280">The &man.top.1; utility has been updated
      to filter by &man.jail.8; ID or name, in followup to the
      &man.ps.1; change in <literal>r265229</literal>.</para>

    <para revision="266890">The &man.pmcstat.8; utility has been
      updated to include a new flag, <literal>-l</literal>, which
      adds event collection after the specified number of
      seconds.</para>

    <para revision="267113">The default &man.newsyslog.conf.5; now
      includes files in the
      <filename>/etc/newsyslog.conf.d/</filename> and
      <filename>/usr/local/etc/newsyslog.conf.d/</filename>
      directories by default for &man.newsyslog.8;.</para>

    <para revision="267236">A new flag, <quote>onifconsole</quote> has
      been added to <filename>/etc/ttys</filename>.  This allows the
      system to provide a login prompt via serial console if the
      device is an active kernel console, otherwise it is equivalent
      to <literal>off</literal>.</para>

    <sect3 xml:id="rc-scripts">
      <title><filename>/etc/rc.d</filename> Scripts</title>

      <para>&nbsp;</para>

    </sect3>
  </sect2>

  <sect2 xml:id="contrib">
    <title>Contributed Software</title>

    <para revision="264377"><application>OpenSSH</application> has
      been updated to version 6.6p1.</para>

    <para revision="266692"><application>Sendmail</application>
      has been updated to 8.14.9.</para>

    <para revision="267258"><application>OpenSSL</application> has
      been updated to version 1.0.1h.</para>
  </sect2>

  <sect2 xml:id="ports">
    <title>Ports/Packages Collection Infrastructure</title>

    <para>&nbsp;</para>

  </sect2>

  <sect2 xml:id="releng">
    <title>Release Engineering and Integration</title>

    <para>&nbsp;</para>

  </sect2>

  <sect2 xml:id="doc">
    <title>Documentation</title>

    <para>&nbsp;</para>

  </sect2>
</sect1>

<sect1 xml:id="upgrade">
  <title>Upgrading from Previous Releases of &os;</title>

  <para arch="amd64,i386">Binary upgrades between RELEASE versions
    (and snapshots of the various security branches) are supported
    using the &man.freebsd-update.8; utility.  The binary upgrade
    procedure will update unmodified userland utilities, as well as
    unmodified GENERIC or SMP kernels distributed as a part of an
    official &os; release.  The &man.freebsd-update.8; utility
    requires that the host being upgraded have Internet
    connectivity.</para>

  <para>Source-based upgrades (those based on recompiling the &os;
    base system from source code) from previous versions are
    supported, according to the instructions in
    <filename>/usr/src/UPDATING</filename>.</para>

  <important>
    <para>Upgrading &os; should only be attempted after
      backing up <emphasis>all</emphasis> data and configuration
      files.</para>
  </important>
</sect1>
</article>
OpenPOWER on IntegriCloud