1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
3 "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
4 <!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"
5 "http://www.FreeBSD.org/release/XML/release.ent">
9 <article xmlns="http://docbook.org/ns/docbook"
10 xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
13 <title>&os; &release.current; Errata </title>
15 <author><orgname>The &os; Project</orgname></author>
17 <pubdate>$FreeBSD$</pubdate>
22 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
26 <legalnotice xml:id="trademarks" role="trademarks">
34 <para>This document lists errata items for &os; &release.current;,
35 containing significant information discovered after the
36 release or too late in the release cycle to be otherwise
37 included in the release documentation. This information
38 includes security advisories, as well as news relating to the
39 software or documentation that could affect its operation or
40 usability. An up-to-date version of this document should
41 always be consulted before installing this version of
44 <para>This errata document for &os; &release.current; will be
45 maintained until the release of &os; &release.next;.</para>
49 <sect1 xml:id="intro">
50 <title>Introduction</title>
52 <para>This errata document contains <quote>late-breaking
53 news</quote> about &os; &release.current; before installing this
54 version, it is important to consult this document to learn about
55 any post-release discoveries or problems that may already have
56 been found and fixed.</para>
58 <para>Any version of this errata document actually distributed
59 with the release (for example, on a CDROM distribution) will be
60 out of date by definition, but other copies are kept updated on
61 the Internet and should be consulted as the <quote>current
62 errata</quote> for this release. These other copies of the
63 errata are located at <link
64 xlink:href="http://www.FreeBSD.org/releases/" />, plus any
65 sites which keep up-to-date mirrors of this location.</para>
67 <para>Source and binary snapshots of &os; &release.branch; also
68 contain up-to-date copies of this document (as of the time of
71 <para>For a list of all &os; CERT security advisories, see <link
72 xlink:href="http://www.FreeBSD.org/security/"/> or <link
73 xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"/>.</para>
76 <sect1 xml:id="security">
77 <title>Security Advisories</title>
79 <informaltable frame="none" pgwide="0">
81 <colspec colwidth="1*" />
82 <colspec colwidth="1*" />
83 <colspec colwidth="3*" />
86 <entry>Advisory</entry>
94 <entry>No advisories.</entry>
103 <sect1 xml:id="open-issues">
104 <title>Open Issues</title>
108 <para>&os;/&arch.i386; &release.current; running as a guest
109 operating system on <application>VirtualBox</application>
110 can have a problem with disk I/O access. It depends on some
111 specific hardware configuration and does not depend on a
112 specific version of <application>VirtualBox</application> or
113 host operating system.</para>
115 <para>It causes various errors and makes &os; quite unstable.
116 Although the cause is still unclear, disabling unmapped I/O
117 works as a workaround. To disable it, choose
118 <literal>Escape to loader prompt</literal> in the boot menu
119 and enter the following lines from &man.loader.8; prompt,
120 after an <literal>OK</literal>:</para>
122 <screen>set vfs.unmapped_buf_allowed=0
125 <para>Note that the following line has to be added to
126 <filename>/boot/loader.conf</filename> after a boot. It
127 disables unmapped I/O at every boot:</para>
129 <programlisting>vfs.unmapped_buf_allowed=0</programlisting>
131 <para>[2014-04-03 update] It has been reported that
132 instability may be present on virtual machines running
133 on other hypervisors, such as Xen or KVM.</para>
137 <para>&os;/&arch.i386; &release.current; configured with
138 a multi-disk ZFS dataset (mirror, raidz1, raidz2, raidz3)
139 may crash during boot when the ZFS pool mount is attempted
140 while booting an unmodified <literal>GENERIC</literal>
143 <para>As described in <filename>/usr/src/UPDATING</filename>
144 entry <literal>20121223</literal>, rebuilding the kernel
145 with <literal>options KSTACK_PAGES=4</literal> has been
146 observed to resolve the boot-time crash. This, however, is
147 not an ideal solution for inclusion in the
148 <literal>GENERIC</literal> kernel configuration, as
149 increasing <literal>KSTACK_PAGES</literal> implicitly
150 decreases available usermode threads in an environment that
151 is already resource-starved.</para>
153 <para>Taking into account the heavy resource requirements of
154 ZFS, in addition to the &arch.i386;-specific tuning
155 requirements for general workloads, using ZFS with the
156 &os;/&arch.i386; <literal>GENERIC</literal> kernel
157 is strongly discouraged.</para>
160 <para>It is extremely important to take note that, by
161 default, &man.freebsd-update.8; will install the
162 <literal>GENERIC</literal> kernel configuration, and
163 as such, &man.freebsd-update.8; consumers are strongly
164 encouraged to avoid &os;-provided kernel binary upgrades
165 with such configurations.</para>
169 <para>Although there is slight change in how the crash
170 manifests on &os;/&arch.i386; between &release.prev; and
171 &release.current;, and given the date of the
172 <filename>/usr/src/UPDATING</filename> entry, there is no
173 evidence suggesting this is a regression between
174 &os; &release.prev; and &os; &release.current;
180 <para>Due to an incompatibility between &man.bsdconfig.8;
181 and &man.pkg.8; version 1.3, packages included on the
182 &os; dvd installer will not be recognized by
183 &man.bsdconfig.8;.</para>
185 <para>To install packages from the <literal>dvd1.iso</literal>
186 installer, create the <filename
187 class="directory">/dist</filename> target directory, and
188 manually mount the <literal>dvd1.iso</literal>
189 <acronym>ISO</acronym>:</para>
191 <screen>&prompt.root; mkdir -p /dist
192 &prompt.root; mount -t cd9660 /dev/<replaceable>cd0</replaceable> /dist</screen>
195 <para>Be sure to use the correct <filename
196 class="directory">/dev</filename> device path for the
197 <literal>dvd1.iso</literal> <acronym>ISO</acronym>
201 <para>Next, set <envar>REPOS_DIR</envar> to the path of the
202 <filename class="directory">repos/</filename> directory
203 within the installer so &man.pkg.8; will use the correct
204 repository metadata.</para>
206 <para>If using &man.sh.1;:</para>
208 <screen>&prompt.root; export REPOS_DIR=/dist/packages/repos</screen>
210 <para>If using &man.csh.1;:</para>
212 <screen>&prompt.root; setenv REPOS_DIR /dist/packages/repos</screen>
215 <para>Keep in mind that <envar>REPOS_DIR</envar> will need
216 to be set again after the current shell session is
217 terminated, if continuing to use the packages provided on
218 the <literal>dvd1.iso</literal> installer.</para>
221 <para>Finally, bootstrap &man.pkg.8; from the
222 <acronym>ISO</acronym>, and install required
225 <screen>&prompt.root; pkg bootstrap
226 &prompt.root; pkg install <replaceable>xorg-server</replaceable> <replaceable>xorg</replaceable> <replaceable>gnome2</replaceable> [...]</screen>
231 <sect1 xml:id="late-news">
232 <title>Late-Breaking News</title>
234 <para>No news.</para>