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">
8 <article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
9 <info><title>&os; &release.current; Release Notes</title>
11 <author><orgname>The &os; Project</orgname></author>
13 <pubdate>$FreeBSD$</pubdate>
17 <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
20 <legalnotice xml:id="trademarks" role="trademarks">
30 <para>The release notes for &os; &release.current; contain a summary
31 of the changes made to the &os; base system on the
32 &release.branch; development line.
33 This document lists applicable security advisories that were issued since
34 the last release, as well as significant changes to the &os;
36 Some brief remarks on upgrading are also presented.</para>
40 <sect1 xml:id="intro">
41 <title>Introduction</title>
43 <para>This document contains the release notes for &os;
45 describes recently added, changed, or deleted features of &os;.
46 It also provides some notes on upgrading
47 from previous versions of &os;.</para>
49 <para releasetype="current">The &release.type; distribution to which these release notes
50 apply represents the latest point along the &release.branch; development
51 branch since &release.branch; was created. Information regarding pre-built, binary
52 &release.type; distributions along this branch
53 can be found at <uri xlink:href="&release.url;"></uri>.</para>
55 <para releasetype="snapshot">The &release.type; distribution to which these release notes
56 apply represents a point along the &release.branch; development
57 branch between &release.prev; and the future &release.next;.
59 pre-built, binary &release.type; distributions along this branch
60 can be found at <uri xlink:href="&release.url;"></uri>.</para>
62 <para releasetype="release">This distribution of &os; &release.current; is a
63 &release.type; distribution. It can be found at <uri xlink:href="&release.url;" />
64 or any of its mirrors. More
65 information on obtaining this (or other) &release.type;
66 distributions of &os; can be found in the <link xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
67 &os;</quote> appendix</link> to the <link xlink:href="&url.books.handbook;/">&os;
68 Handbook</link>.</para>
70 <para>All users are encouraged to consult the release errata before
71 installing &os;. The errata document is updated with
72 <quote>late-breaking</quote> information discovered late in the
73 release cycle or after the release. Typically, it contains
74 information on known bugs, security advisories, and corrections to
75 documentation. An up-to-date copy of the errata for &os;
76 &release.current; can be found on the &os; Web site.</para>
81 <title>What's New</title>
83 <para>This section describes the most user-visible new or changed
84 features in &os; since &release.prev;.</para>
86 <para>Typical release note items document recent security
87 advisories issued after &release.prev;, new drivers or hardware
88 support, new commands or options, major bug fixes, or
89 contributed software upgrades. They may also list changes to
90 major ports/packages or release engineering practices. Clearly
91 the release notes cannot list every single change made to &os;
92 between releases; this document focuses primarily on security
93 advisories, user-visible changes, and major architectural
96 <sect2 xml:id="security">
97 <title>Security Advisories</title>
99 <para>Problems described in the following security advisories have
100 been fixed. For more information, consult the individual
101 advisories available from
102 <uri xlink:href="http://security.FreeBSD.org/">http://security.FreeBSD.org/</uri>.</para>
104 <informaltable frame="none" pgwide="1">
106 <colspec colwidth="1*"/>
107 <colspec colwidth="1*"/>
108 <colspec colwidth="3*"/>
111 <entry>Advisory</entry>
119 <entry><uri xlink:href="http://security.freebsd.org/advisories/FreeBSD-SA-10:08.bzip2.asc">SA-10:08.bzip2</uri></entry>
120 <entry>20 September 2010</entry>
121 <entry><para>Integer overflow in bzip2 decompression</para></entry>
124 <entry><uri xlink:href="http://security.freebsd.org/advisories/FreeBSD-SA-10:10.openssl.asc">SA-10:10.openssl</uri></entry>
125 <entry>29 November 2010</entry>
126 <entry><para>OpenSSL multiple vulnerabilities</para></entry>
133 <sect2 xml:id="kernel">
134 <title>Kernel Changes</title>
136 <para arch="ia64" revision="209326">The maximum number of pages
137 used for DMA bounce buffer pool has been increased from 256 to
140 <para arch="powerpc" revision="209765">The default value of
141 <varname>kern.hz</varname> has been increased from 100 to
144 <para arch="powerpc" revision="209767">The SMP kernel now works on
145 MPC7400-based Apple desktop machines such as
148 <para arch="powerpc" revision="211593">&os;/powerpc now supports
149 DMA bounce buffer which is required on systems with larger RAM
152 <para arch="mips" revision="215938">&os;/mips support has been
153 improved. It now supports SMP on a SWARM with a dual-core
154 Sibyte processor.</para>
156 <para arch="mips">&os;/mips now supports Netlogic Microsystems'
157 XLR and XLS multi-core processor families.</para>
159 <para arch="sparc64" revision="215598">&os;/sparc64 now supports
160 reservation-based physical memory allocation which provides
161 better performance.</para>
163 <para arch="amd64" revision="214620">&os;/amd64 now always sets
164 the KVA space as equal to or larger than physical memory size.
165 The default size was calculated based on one-third of the
166 physical memory size by a code derived from one for i386. It
167 has been changed because constraints for memory space are not
168 severe on amd64 and this change would help to prevent a
169 <quote>kmem_map too small</quote> panic which often occurs
170 when using ZFS.</para>
172 <para arch="amd64,i386" revision="214621">CPU topology detection
173 for Intel CPUs has been improved.</para>
175 <para arch="amd64,i386" revision="215513">ACPI suspend/resume
176 functionality support has been improved.</para>
178 <para arch="amd64,i386" revision="215513">&os; kernel now
179 supports <function>kern_fpu_enter()</function> and
180 <function>kern_fpu_leave()</function> KPIs which allow the
181 kernel subsystems to use XMM register files used in Intel SSE
182 (Streaming SIMD Extensions).</para>
184 <para arch="amd64,i386,ia64" revision="215006">The &man.acpi.4;
185 driver now uses ACPI Reset Register capability by default only
186 when a flag in the FADT which indicates it is available. This
187 behavior was controlled by a &man.sysctl.8; variable
188 <varname>hw.acpi.handle_reboot</varname> and the default value
189 was always set to <literal>0</literal>.</para>
191 <para arch="amd64,i386,ia64" revision="215521">The &man.acpi.4;
192 driver now supports new loader tunables
193 <varname>hw.acpi.install_interface</varname> and
194 <varname>hw.acpi.remove_interface</varname>. For more
195 details, see &man.acpi.4; manual page.</para>
197 <para revision="209788">The &man.alq.9; support has been
198 improved. The <function>alq_writen()</function> and
199 <function>alq_getn()</function> KPIs have been extended to
200 support variable length messages, which is enabled at ALQ
201 creation time depending on the arguments passed to
202 <function>alq_open()</function>. Also, the
203 <literal>ALQ_NOACTIVATE</literal> and
204 <literal>ALQ_ORDERED</literal> flags have been added to allow
205 ALQ consumers to have more control over I/O scheduling and
206 resource acquisition respectively. These extensions are fully
207 backward compatible.</para>
209 <para revision="209783">The &man.alq.9; support is now provided
210 as a kernel module <filename>alq.ko</filename>.</para>
212 <para revision="209692">The &man.ddb.8; kernel debugger now
213 supports an optional delay in <command>reset</command> and
214 <command>reboot</command> commands. This allows an
215 administrator to break the system into debugger and trigger
216 automatic textdump when an unattended panic occurs.</para>
218 <para revision="212230">The &man.ddb.8; kernel debugger now
219 supports a <command>show cdev</command> command. This
220 displays the list of all created cdev's, consisting of devfs
221 node name and struct cdev address.</para>
223 <para revision="214326">The &os; <filename>GENERIC</filename>
224 kernel is now compiled with <option>KDB</option> and
225 <option>KDB_TRACE</option> options. From 8.2-RELEASE the
226 kernel supports displaying a stack trace on panic by using
227 &man.stack.9; facility with no debugger backend like
228 &man.ddb.8;. Note that this does not change the default
229 behaviors of the <filename>GENERIC</filename> kernel on
232 <para revision="213554,213556,213560">The following
233 &man.sysctl.8; variables are also now loader tunables:
234 <varname>vm.kmem_size</varname>,
235 <varname>vm.kmem_size_max</varname>, and
236 <varname>vm.kmem_size_min</varname>,
237 <varname>debug.kdb.stop_cpus</varname>,
238 <varname>debug.trace_on_panic</varname>, and
239 <varname>kern.sync_on_panic</varname>. Also, new
240 &man.sysctl.8; variables <varname>vm.kmem_map_size</varname>
241 for the current kmem map size and
242 <varname>vm.kmem_map_free</varname> for largest contiguous
243 free range in kmem map, <varname>vfs.ncsizefactor</varname>
244 for size factor for namecache, and
245 <varname>vfs.ncnegfactor</varname> for ratio of negative
246 namecache entries have been added.</para>
248 <para revision="212427">The &os; &man.memguard.9; framework has
249 been improved to make it able to detect use-after-free of
250 allocated memories over a longer time. For more details, see
251 &man.memguard.9; manual page.</para>
253 <para revision="214756"><literal>PT_LWPINFO</literal> request to
254 obtain information about the kernel thread that caused the
255 traced process to stop in the &man.ptrace.2; process tracing
256 and debugging facility has been improved. It now reports
257 system call entry and leave events, as well as availability of
258 <varname>siginfo_t</varname> accompanying the reported
261 <para revision="214254">The &os; &man.crypto.4; framework
262 (opencrypto) now supports XTS-AES (XEX-TCB-CTS, or XEX-based
263 Tweaked Code Book mode with CipherText Stealing), which is
264 defined in IEEE Std. 1619-2007.</para>
266 <para arch="amd64" revision="215788">Xen HVM support in
267 &os;/amd64 kernel has been improved. For more details, see
268 &man.xen.4; manual page.</para>
270 <para arch="amd64,i386" revision="214784">The qpi(4) pseudo bus
271 driver has been added. This supports extra PCI buses on Intel
272 QPI chipsets where various hardware such as memory controllers
273 for each socket is connected.</para>
275 <sect3 xml:id="boot">
276 <title>Boot Loader Changes</title>
278 <para revision="213994">&os; now fully supports GPT (GUID
279 Partition Table). Checksums of primary header and primary
280 partition table are verified properly now.</para>
282 <para arch="powerpc" revision="215919,215920">Memory
283 management issues that prevented &os; OpenFirmware loader
284 and netbooting from working have been fixed.</para>
286 <para revision="212717">The &man.pxeboot.8; now uses NFS
287 version 3 instead of version 2 by default.</para>
290 <sect3 xml:id="proc">
291 <title>Hardware Support</title>
293 <para arch="amd64,i386" revision="215633">The &man.aesni.4;
294 driver has been added. This supports AES accelerator on
295 Intel CPUs and accelerates AES operations for
296 &man.crypto.4;.</para>
298 <para arch="amd64,i386" revision="210476">The &man.aibs.4;
299 driver has been added. This supports the hardware sensors
300 in ASUS motherboards and replaces the &man.acpi.aiboost.4;
303 <para arch="amd64,i386" revision="211914">The &man.coretemp.4;
304 driver now supports Xeon 5500/5600 series.</para>
306 <para arch="powerpc" revision="215694">&os;/powerpc now
307 supports the I2C bus in Apple System Management Unit.</para>
309 <para arch="powerpc" revision="215695">A device driver that
310 supports CPU temperature sensors on PowerMac 11,2 has been
313 <para revision="215482">The &man.ehci.4;, &man.ohci.4;, and
314 &man.uhci.4; driver now support LOW speed BULK transfer
317 <para arch="amd64,i386" revision="209952">The &man.ichwd.4;
318 driver now supports Intel NM10 Express chipset watchdog
321 <para revision="215036">The &man.tpm.4; driver, which supports
322 Trusted Platform Module has been added.</para>
324 <para revision="215944">The xhci(4) driver, which supports
325 Extensible Host Controller Interface (xHCI) and USB 3.0, has
329 <title>Multimedia Support</title>
331 <para>The &os; Linux emulation subsystem now supports the
332 <application>video4linux</application> API. This requires
333 native <application>video4linux</application> hardware
334 drivers such as the ones provided by <filename
335 role="ports">multimedia/pwcbsd</filename> and <filename
336 role="ports">multimedia/webcamd</filename>.</para>
338 <para revision="215483">MIDI input buffer size in the
339 &man.uaudio.4; driver has been changed. This fixes a
340 problem where the input appears several seconds
343 <para revision="215484">An issue in the &man.uaudio.4;
344 driver that prevented some USB audio devices from working
345 has been fixed.</para>
348 <sect4 xml:id="net-if">
349 <title>Network Interface Support</title>
351 <para revision="212021">The &man.alc.4; driver now supports
352 Atheros AR8151/AR8152 PCIe Gigabit/Fast Ethernet
355 <para revision="215003">A bug in the &man.alc.4; driver was
356 fixed that could lead to a system freeze when the system
357 was booted without a cable plugged in. This symptom was
358 found in AR8132 on EEE PC.</para>
360 <para revision="212011">The TX interrupt moderation timer in
361 the &man.alc.4; driver has been reduced from 50ms to 1ms.
362 The 50ms timer resulted in a poor UDP performance.</para>
364 <para revision="214297,214298,214301">The &man.axe.4; driver
365 has been improved for stability and better performance on
366 the TX packet rate.</para>
368 <para revision="214997">The &man.bge.4; driver now supports
369 BCM5718 x2 PCI Express dual-port gigabit Ethernet
370 controller family. This family is the successor to the
371 BCM5714/BCM5715 family and supports IPv4/IPv6 checksum
372 offloading, TSO, VLAN hardware tagging, jumbo frames,
373 MSI/MSIX, IOV, RSS and TSS. The current version of the
374 driver supports all hardware features except IOV and
377 <para revision="211367">A bug in the &man.bge.4; driver which
378 prevented TSO from working in BCM57780 has been
381 <para revision="214700">A bug in the &man.bge.4; driver that
382 could wrongly disable the TX checksum offloading feature
383 as well when one tries to disable only the RX checksum
384 offloading has been fixed.</para>
386 <para revision="214714">Some improvements for reliability of
387 the &man.bge.4; driver with BCM5906 controller has been
390 <para revision="214698">The &man.bge.4; driver now supports
391 hardware MAC statistics in controller's internal memory
392 for BCM5705 or newer Broadcom controllers. These counters
393 can be accessed via &man.sysctl.8; variable
394 <varname>dev.bge.<replaceable>N</replaceable>.stats.*</varname>
395 and provide useful information to diagnose driver
398 <para revision="213109">UDP checksum offloading in the
399 &man.bge.4; driver has been disabled by default. This is
400 because Broadcom controllers have a bug which can generate
401 UDP datagrams with checksum value <literal>0</literal>
402 when TX UDP checksum offloading is enabled. The checksum
403 offloading can be enabled by using the following loader
406 <programlisting>dev.bge.<replaceable>N</replaceable>.forced_udpcsum</programlisting>
408 <para revision="213593">A bug in the &man.bge.4; driver that
409 could lead to poor performance on a system with more than
410 4 GB RAM has been fixed. The cause was that all of
411 Broadcom controllers except the BCM5755 and later have a
412 bug in 4 GB-boundary DMA processing and used the bounce
413 buffer in an inefficient way.</para>
415 <para revision="212275">The &man.bwi.4; driver, which supports
416 Broadcom BCM430* and BCM431* family Wireless Ethernet
417 controllers, has been added. This is not compiled into
418 the <filename>GENERIC</filename> kernel because there are
419 some problems. The kernel module
420 <filename>if_bwi.ko</filename> is available and can be
421 loaded without recompiling the kernel to enable this
424 <para revision="212274">A bug in the &man.bwn.4; driver that
425 prevented WPA authentication from working has been
428 <para revision="215499">A bug in the &man.cdce.4; driver has
431 <para revision="211848">The &man.cxgb.4; driver now supports
432 the following new &man.sysctl.8; variables:
433 <varname>hw.cxgb.nfilters</varname> sets the maximum
434 number of entries in the hardware filter table,
435 <varname>dev.cxgbc.<replaceable>N</replaceable>.pkt_timestamp</varname>
436 provides packet timestamp instead of connection hash, and
437 <varname>dev.cxgbc.<replaceable>N</replaceable>.core_clock</varname>
438 provides the core clock frequency in kHz.</para>
440 <para>The &man.em.4; driver has been updated to version
443 <para>The &man.igb.4; driver has been updated to version
446 <para revision="209309">The &man.em.4; and &man.igb.4; drivers
447 now provide statistics counters as &man.sysctl.8; MIB
450 <para revision="211241">The &man.em.4; and &man.igb.4; drivers
451 now support the &man.led.4; interface via
452 <filename>/dev/led/em<replaceable>N</replaceable></filename>
454 <filename>/dev/led/igb<replaceable>N</replaceable></filename>
455 for identification LED control. The following command
456 line makes the LED blink on <literal>em0</literal>:</para>
458 <screen>&prompt.root; echo f2 > /dev/led/em0</screen>
460 <para revision="212150">The &man.epair.4; virtual Ethernet
461 interface driver now supports explicit UP/DOWN linkstate.
462 This fixes an issue when it is used with the &man.carp.4;
465 <para revision="214717">The &man.fxp.4; driver now supports
466 TSO over VLAN on i82550 and i82551 controllers.</para>
468 <para revision="210673">The &man.iwn.4; driver now supports
469 Intel Wireless WiFi Link 6000 series. The firmware has
470 been updated to version 9.221.4.1.</para>
472 <para revision="212386">The &man.ixgbe.4;
473 driver is now also provided as a kernel module.</para>
475 <para revision="209308,215970,217593">The &man.ixgbe.4;
476 driver has been updated to version 2.3.8. It now supports
477 82599, better interrupt handling, hardware assist to LRO,
478 VM SRIOV interface, and so on.</para>
481 revision="211379,215881,215890,2105894,216002,216023,216029,216031,216033">The
482 &man.miibus.4; has been rewritten for the generic IEEE
483 802.3 annex 31B full duplex flow control support. The
484 &man.alc.4;, &man.bge.4;, &man.bce.4;, &man.cas.4;,
485 &man.fxp.4;, &man.gem.4;, &man.jme.4;, &man.msk.4;,
486 &man.nfe.4;, &man.re.4;, &man.stge.4;, and &man.xl.4;
487 drivers along with atphy(4), bmtphy(4), brgphy(4),
488 e1000phy(4), gentbi(4), inphy(4), ip1000phy(4), jmphy(4),
489 nsgphy(4), nsphyter(4), and &man.rgephy.4; have been
490 updated to support flow control via this facility.</para>
492 <para revision="212386">The &man.mwlfw.4;
493 driver is now also provided as a kernel module.</para>
495 <para revision="216054">A bug in the &man.mxge.4; driver
496 that prevented TSO from working has been fixed.</para>
498 <para revision="215456">The &man.nfe.4; driver now supports
499 WoL (Wake on LAN).</para>
501 <para revision="215218">The &man.re.4; driver now supports
502 64-bit DMA addressing for RTL810xE/RTL8168/RTL8111 PCIe
505 <para revision="215405">The &man.re.4; driver now supports
506 hardware interrupt moderation of TX completion interrupts
507 on RTL8169/RTL8168 controllers.</para>
509 <para revision="211377">The &man.rl.4; driver now supports WoL
510 (Wake on LAN) on RTL8139B or newer controllers.</para>
512 <para revision="215222">The &man.rl.4; driver now supports
513 reading hardware statistics counters by setting a
514 &man.sysctl.8; variable
515 <varname>dev.rl.<replaceable>N</replaceable>.stats</varname>
516 to <literal>1</literal>.</para>
518 <para revision="212039">The &man.rl.4; driver now supports a
519 device hint to change a way of register access. Although
520 some newer RTL8139 controllers support memory-mapped
521 register access, it is difficult to detect the support
522 automatically. For this reason the driver uses I/O
523 mapping by default and provides the following device hint.
524 If it is set to <literal>0</literal>, the driver uses
525 memory mapping for register access.</para>
527 <programlisting>hint.rl.<replaceable>N</replaceable>.prefer_iomap="0"</programlisting>
529 <para>Note that the default value is <literal>1</literal>.</para>
531 <para revision="214407">The &man.rl.4; driver has improved
532 interrupt handling. It now has better TX performance
533 under high RX load.</para>
535 <para revision="215216">A bug in the &man.sk.4; driver has
536 been fixed. It did not program the station address for
537 Yukon controllers and overriding the station address with
538 &man.ifconfig.8; was not possible.</para>
540 <para revision="211359">The &man.sk.4; driver now disables TX
541 checksum offloading by default. This is because some
542 revisions of the Yukon controller generate corrupted frames.
543 The checksum offloading can be enabled manually by using
544 <option>txcsum</option> option in the &man.ifconfig.8;
547 <para revision="212468,213612,213628">The &man.sis.4; driver
548 now works on all supported platforms. Some stability and
549 performance issues have also been fixed.</para>
551 <para revision="213637">The &man.sis.4; driver now supports
552 WoL (Wake on LAN) on NS DP8315 controller.</para>
554 <para revision="213626">A tunable
555 <varname>dev.sis.<replaceable>N</replaceable>.manual_pad</varname>
556 for the &man.sis.4; driver has been added. This controls
557 whether padding with 0x00 for short frames is done by CPU,
558 rather than the controller. The reason why this tunable
559 has been added is that NS DP83815/DP83816 pads them with
560 0xff though RFC 1042 specifies it should be 0x00. The
561 tunable is disabled by default, which means padding with
562 0xff is used because padding with 0x00 by software needs
563 extra CPU cycles. Enabling <varname>manual_pad</varname>,
564 by setting this &man.sysctl.8; variable to a non-zero
565 value, forces the use of software padding.</para>
567 <para revision="211357">The &man.ste.4; driver now supports
568 a device hint to change the device register access mode.
569 The driver uses memory-mapped register access by default,
570 but this caused stability problems with some old IC Plus
571 Corp (formerly Sundace) controllers. The following device
572 hint makes the driver use I/O mapping for register
575 <programlisting>hint.ste.<replaceable>N</replaceable>.prefer_iomap="1"</programlisting>
577 <para revision="213120">The &man.xl.4; driver now supports
578 WoL (Wake on LAN). Note that not all controllers support
579 this functionality and some need an additional remote
584 <sect3 xml:id="net-proto">
585 <title>Network Protocols</title>
587 <para revision="213505">An issue in the &man.carp.4; pseudo
588 interface and linkstate changes of the underlying interfaces
589 has been fixed. This happened when a &man.carp.4; interface
590 was created before the underlying interface and its
591 linkstate became <literal>UP</literal>.</para>
593 <para>The stdtime part of libc, &man.zdump.8; and &man.zic.8;
594 have been updated from the <application>tzcode2004a</application>
595 release to the <application>tzcode2009h</application> release.
596 If you have upgraded from source or via the &man.freebsd-update.8;,
597 then please run &man.tzsetup.8; to install a new /etc/localtime.
600 <para revision="215342">A new loader tunable
601 <varname>net.link.ifqmaxlen</varname> has been added. It
602 specifies the default value of send interface queue length.
603 The default value for this parameter is
604 <varname>50</varname>.</para>
606 <para revision="212742">The <literal>ngtee</literal> action in
607 the &man.ipfw.4; packet filter subsystem has been changed.
608 It no longer accepts a packet.</para>
610 <para revision="214108">A possible panic in the &man.ipfw.4;
611 pseudo interface for logging has been fixed.</para>
613 <para revision="209691">IPsec flow distribution has been
614 improved for more parallel processing.</para>
616 <para revision="209277">A bug in the &os; IPv4 stack that
617 prevented adding a proxy ARP entry over &man.netgraph.4;
618 interfaces has been fixed.</para>
620 <para revision="211435">A bug in the &os; IPv6 stack that
621 prevented an <option>-I</option> in the &man.ping6.8;
622 utility from working with
623 <varname>net.inet6.ip6.use_defaultzone=1</varname> has been
626 <para revision="214111">The &man.lagg.4; interface now
627 supports a &man.sysctl.8; variable
628 <varname>net.link.lagg.failover_rx_all</varname>. This
629 controls whether to accept input packets on any link in a
630 failover lagg.</para>
632 <para revision="215869">The &man.ng.eiface.4; &man.netgraph.4;
633 node now supports VLAN-compatible MTU and an MTU size which
634 is larger than 1500.</para>
636 <para revision="212320">The &man.ng.ether.4; &man.netgraph.4;
637 node now supports interface transfer between multiple virtual
638 network stacks by &man.ifconfig.8; <command>vnet</command>
639 command. A &man.ng.ether.4; node associated with a network
640 interface is now destroyed and recreated when the network
641 interface is moved to another vnet.</para>
643 <para revision="209843">A new &man.netgraph.4; node
644 &man.ng.patch.4; has been added. This performs data
645 modification of packets passing through. Modifications are
646 restricted to a subset of C language operations on unsigned
647 integers of 8, 16, 32 or 64-bit size.</para>
649 <para revision="212905">An ICMP unreachable problem in the
650 &man.pf.4; packet filter subsystem when TSO support is
651 enabled has been fixed.</para>
653 <para revision="211538">The TCP bandwidth delay product window
654 limiting algorithm controlled by the &man.sysctl.8; variable
655 <varname>net.inet.tcp.inflight.enable</varname> is now
656 disabled by default. It has been found that this algorithm
657 is inefficient on a fast network with smaller RTT than 10ms.
658 It had been enabled by default since 5.2-RELEASE, and then
659 had been disabled only if the RTT was lesser than 10ms since
660 7.0-RELEASE. Pluggable TCP congestion control algorithm
661 modules are planned to be added for the future
664 <para revision="211602">A bug in &os; TCP Path MTU discovery
665 which could lead to a wrong calculation for an MTU smaller
666 than 256 octets has been fixed. Note that this bug did not
667 affect MTUs equal to or larger than 256 octets.</para>
669 <para revision="214865,214866">The &os; TCP reassembly
670 implementation has been improved. A long-standing
671 accounting bug affecting SMP systems has been fixed and the
672 <varname>net.inet.tcp.reass.maxqlen</varname> &man.sysctl.8;
673 variable has been retired in favor of a per-connection
674 dynamic limit based on the receive socket buffer size. &os;
675 receivers now handle packet loss (particularly losses caused
676 by queue overflows) significantly better than before which
677 improves connection throughput.</para>
679 <para revision="211870">The TCP initial window increase in RFC
680 3390 which can be controlled by a &man.sysctl.8; variable
681 <varname>net.inet.tcp.rfc3390</varname> now reduces the
682 congestion window to the restart window if a TCP connection
683 has been idle for one retransmit timeout or more. For more
684 details, see RFC 5681 Section 4.1.</para>
686 <para revision="214859">The &man.siftr.4;, Statistical
687 Information For TCP Research (SIFTR) kernel module has been
688 added. This is a facility that logs a range of statistics
689 on active TCP connections to a log file. It provides the
690 ability to make highly granular measurements of TCP
691 connection state, aimed at system administrators, developers
692 and researchers.</para>
694 <para revision="212319">&os; virtual network stack (vnet) now
695 supports IPv4 multicast routing.</para>
697 <para revision="239616">The IEEE 802.11s element identifiers have
698 been updated to reflect the final version of the amendment. This
699 update breaks compatibility with older mesh setups but is necessary
700 as the previous IDs are used by another amendment leading to
701 unexpected results when trying to associate with an accesspoint
702 using the affected IDs.</para>
705 <sect3 xml:id="disks">
706 <title>Disks and Storage</title>
708 <para revision="211458">The &man.ahci.4; driver now disables NCQ
709 and PMP support on VIA VT8251 because they are unreliable
712 <para revision="211718">The &man.ahci.4; driver now uses 15
713 seconds for device reset timeout instead of 10 seconds
714 because some devices need 10 - 12 seconds to spin up.</para>
716 <para revision="215825">The &man.arcmsr.4; driver
717 has been updated to version 1.20.00.19.</para>
719 <para revision="215173">The &man.ada.4; driver now supports a
720 new &man.sysctl.8; variable
721 <varname>kern.cam.ada.spindown_shutdown</varname> which
722 controls whether or not to spin-down disks when shutting
723 down if the device supports the functionality. The default
724 value is <literal>1</literal>.</para>
726 <para revision="210164">The &man.ata.4; driver
727 now supports limiting initial ATA mode for devices via
729 <varname>hint.<replaceable>devname</replaceable>.<replaceable>unit</replaceable>.dev<replaceable>N</replaceable
731 <varname>hint.<replaceable>devname</replaceable>.<replaceable>unit</replaceable>.mode</varname>.
732 The valid values are the same as ones supported in the
733 &man.atacontrol.8; and &man.camcontrol.8; utilities.</para>
735 <para revision="210204">The &man.ata.4; driver now disables
736 cable status check on both controller and device side
737 when the loader tunable
738 <varname>hw.ata.ata_dma_check_80pin</varname> is
739 <literal>0</literal>. The check on controller side was
740 performed regardless of this loader tunable.</para>
742 <para revision="215777">The &man.ata.4; driver now reports
743 SATA power management capabilities to the &man.CAM.4; layer when
744 <option>ATA_CAM</option> is enabled. This allows a device
745 to initiate transitions if controller configured to accept
747 <varname>hint.ata.<replaceable>N</replaceable>.pm_level=1</varname>
750 <para revision="214671">The &man.ata.4; driver has been
751 improved on hotplugging and connection speed reporting
752 support for some Intel SATA controllers including ICH5 and
753 ICH8+ operating in legacy mode.</para>
755 <para revision="213291">An issue of device detection of
756 Serverworks K2 SATA controllers in the &man.ata.4; has been fixed.</para>
758 <para revision="214667">A bug in the &man.ata.4; driver that
759 prevented some Silicon Image chipsets from working on big
760 endian systems has been fixed.</para>
762 <para revision="214330">The &man.gconcat.8; GEOM class now
763 supports kernel crash dump. The dumping is performed to the
764 component where a dump partition begins.</para>
766 <para revision="214405">A bug in the &man.geli.8; GEOM class
767 on little endian platforms has been fixed. The metadata
768 version for newly created providers has been updated to
769 <literal>4</literal> due to this. Providers with the older
770 versions are fully interoperable with 8.2-RELEASE and later
771 by being treated as ones with the native byte order flag
772 automatically.</para>
774 <para revision="214405">The &man.geli.8; GEOM class now
775 supports a &man.sysctl.8; variable
776 <varname>kern.geom.eli.overwrites</varname>. This specifies
777 the number of times on-disk keys should be overwritten when
778 destroying them. The default value is
779 <literal>5</literal>.</para>
781 <para revision="214405">The &man.geli.8; GEOM class has been
782 improved for preventing the same encryption key from being
783 used in 2^20 blocks (sectors).</para>
785 <para revision="214405">The &man.geli.8; GEOM class now uses
786 XTS-AES mode by default.</para>
788 <para revision="214405">A &man.sysctl.8; variable
789 <varname>kern.geom.eli.debug</varname> now allows a value
790 <literal>-1</literal>. This means turn off any log messages
791 of the &man.geli.8; GEOM class.</para>
793 <para revision="210376">The &man.mpt.4; driver now supports
794 larger I/O sizes which the device and &man.CAM.4; subsystem
795 can support. This was limited to 64KB, and the number of
796 scatter/gather segments was limited to 33 on platforms with
799 <para revision="209404">The &man.twa.4;
800 driver has been updated. The version number is
805 <title>File Systems</title>
807 <para revision="214050">The &man.linprocfs.5; Linux process
808 file system now supports
809 <filename>proc/$$/environment</filename>.</para>
811 <para revision="212716">The &os; NFS client now supports a
812 kernel environment variable
813 <varname>boot.nfsroot.nfshandlelen</varname>. This lets the
814 diskless root file system on boot to use NFS version 3 and
815 the specified file handle length. If this variable is not
816 set, NFS version 2 is used.</para>
818 <para revision="212668">The ZFS on-disk format has been updated
819 to version 15.</para>
821 <para revision="212671">The ZFS metaslab code has been updated.
822 This provides a noticeable improvement on write speed,
823 especially on pools with less than 30% of free space. The
824 related OpenSolaris Bug IDs are 6826241, 6869229, 6918420,
827 <para revision="214013">The ZFS now supports offlining of log
828 devices. The related OpenSolaris Bug IDs are 6599442,
829 6726045, and 6803605.</para>
831 <para revision="212672">Performance improvements for the ZFS
832 have been imported from OpenSolaris. They include caching of
833 ACL permission checks, faster handling of &man.stat.2;,
834 mitigation of mutex lock contention. The related
835 OpenSolaris Bug IDs are 6802734, 6844861, 6848431, 6775100,
836 6827779, 6857433, 6860318, 6865875, 6867395, 6868276, and
839 <para revision="210541">The default value of
840 <varname>vfs.zfs.vdev.max_pending</varname> has been
841 decreased from 35 to 10 (OpenSolaris Bug ID is 6891731) to
842 improve latency.</para>
844 <para>Various bugs in the ZFS subsystem have been fixed. The
845 related OpenSolaris Bug IDs are: 6328632, 6396518, 6501037,
846 6504953, 6542860, 6551866, 6572357, 6572376, 6582163,
847 6586537, 6595194, 6596237, 6604992, 6621164, 6623978,
848 6633095, 6635482, 6664765, 6674216, 6696242, 6696858,
849 6702206, 6710376, 6713916, 6717022, 6722540, 6722991,
850 6737463, 6739487, 6739553, 6740164, 6745863, 6747596,
851 6747698, 6748436, 6755435, 6757430, 6758107, 6759986,
852 6759999, 6761100, 6761406, 6764124, 6765294, 6767129,
853 6769612, 6770866, 6774713, 6774886, 6775697, 6776104,
854 6776548, 6780491, 6784104, 6784108, 6785914, 6788152,
855 6788830, 6789318, 6790064, 6790345, 6790687, 6791064,
856 6791066, 6791071, 6791101, 6792134, 6792139, 6792884,
857 6793430, 6794136, 6794570, 6794830, 6797109, 6797118,
858 6798384, 6798878, 6799895, 6800184, 6800942, 6801507,
859 6801810, 6803343, 6803822, 6804954, 6807339, 6807765,
860 6809340, 6809683, 6809691, 6810367, 6815592, 6815893,
861 6816124, 6818183, 6821169, 6821170, 6822816, 6824006,
862 6824062, 6824968, 6826466, 6826468, 6826469, 6826470,
863 6826471, 6826472, 6827260, 6830237, 6830541, 6833162,
864 6833711, 6833999, 6834217, 6836714, 6836768, 6838062,
865 6838344, 6841321, 6843014, 6843069, 6843235, 6844069,
866 6844900, 6847229, 6848242, 6856634, 6857012, 6861983,
867 6862984, 6863610, 6870564, 6880764, 6882227, 6892298,
868 6898245, 6906110, 6906946, 6939941, 6950219, 6951024, and
873 <sect2 xml:id="userland">
874 <title>Userland Changes</title>
876 <para revision="209267">The &man.arp.8; utility has been improved.
877 It now runs faster even when a single interface has a number
880 <para revision="214729">A bug in the &man.b64decode.1; utility that
881 prevented an <option>-r</option> option from handling arbitrary
882 breaks in a base64 encoded string has been fixed.</para>
884 <para revision="211723">The &man.calendar.1; utility now supports
885 repeating events which span multiple years, lunar events, and
888 <para revision="210915">The &man.dhclient.8; utility now reports a
889 reason for exiting and the 10-second period in which the
890 &man.dhclient.8; ignores routing messages has been changed to
891 start just after <filename>dhclient-script</filename> starts
892 instead of just after it finished. This change fixes a
893 symptom that &man.dhclient.8; silently exits under a certain
896 <para revision="214983">Userland support for the &man.dtrace.1;
897 subsystem has been added. This allows inspection of userland
898 software itself and its correlation with the kernel, thus
899 allowing a much better picture of what exactly is going on
900 behind the scenes. The &man.dtruss.1; utility has been added
901 and the <filename>libproc</filename> library has been updated
902 to support the facility.</para>
904 <para revision="209362">The &man.du.1; utility now supports a
905 <option>-t <replaceable>threshold</replaceable></option>
906 option to display entries that exceeds the value of
907 <replaceable>threshold</replaceable>. If the value is
908 negative, it displays entries with a value less than the
909 absolute value of <replaceable>threshold</replaceable>.</para>
911 <para revision="215667">The &man.fdisk.8; utility now supports
912 partitions which are provided by &man.gjournal.8; or
913 &man.geli.8; GEOM classes.</para>
915 <para revision="210567">The &man.gcore.1; utility now supports an
916 <option>-f</option> flag which forces a full dump of all the
917 segments except for the malformed ones.</para>
919 <para revision="214405">The &man.geli.8; utility now supports
920 <command>resize</command> subcommand to resize encrypted file
921 systems after growing it.</para>
923 <para revision="214405">The &man.geli.8; utility now supports
924 <command>suspend</command> and <command>resume</command>
925 subcommands. The <command>suspend</command> subcommand makes
926 &man.geli.8; devices wait for all in-flight I/O requests,
927 suspend new I/O requests, remove all &man.geli.8; sensitive
928 data from the kernel memory (like encryption keys) and will
929 wait for either <command>geli resume</command> or
930 <command>geli detach</command> command. For more
931 information, see &man.geli.8; manual page.</para>
933 <para revision="214405">The &man.geli.8; utility now checks the
934 metadata provider size strictly. If the check fails, the
935 provider is not attached. A new option <option>-f</option>
936 can override this behavior.</para>
938 <para revision="214405">The &man.geli.8; utility now supports
939 <option>-J <replaceable>newpassfile</replaceable></option> and
940 <option>-j <replaceable>oldpassfile</replaceable></option>
941 options for loading passphrase from a file.</para>
943 <para revision="211938">The <function>gethost*()</function>,
944 <function>getnet*()</function>, and
945 <function>getproto*()</function> functions now set the errno
946 to <literal>ERANGE</literal> and the NSS backend terminates
947 with <literal>NS_RETURN</literal> when the result buffer size
950 <para revision="209497">The &man.gpart.8; utility now supports a
951 <command>resize</command> command to resize partitions for all
952 schemes but EBR.</para>
954 <para revision="215941">The &man.gpart.8; utility now supports
955 <command>backup</command> and <command>restore</command>
956 subcommands to backup partition tables and restore
959 <para revision="213661">The &man.gpart.8; utility now handles
960 given geom/provider names with and without
961 <filename>/dev/</filename> prefix.</para>
963 <para revision="213684">The &man.gpart.8; utility now supports
964 an <option>-F</option> option for the
965 <command>destroy</command> subcommand. This option forces
966 destroying of the partition table even if it is not
969 <para revision="213684">The &man.gpart.8; utility now supports a
970 <command>recover</command> subcommand for GPT partition
971 tables. A corrupted GPT is now marked when the following
972 three types of corruption:</para>
976 <para>Primary GPT header or table is corrupted.</para>
980 <para>Secondary GPT header or table is corrupted.</para>
984 <para>Secondary GPT header is not located at the last LBA.</para>
988 <para>Changes to the corrupted GPT table are not allowed except
989 for <command>destroy</command> and <command>recover</command>
992 <para revision="213994">The &man.gpart.8; utility now supports
993 <literal>GPT_ENT_ATTR_BOOTME</literal>,
994 <literal>GPT_ENT_ATTR_BOOTONCE</literal>, and
995 <literal>GPT_ENT_ATTR_BOOTFAILED</literal> attributes in GPT.
996 The attribute keywords in the command line are
997 <literal>bootme</literal>, <literal>bootonce</literal>, and
998 <literal>bootfailed</literal> respectively.</para>
1000 <para revision="215728">An issue in the &man.newfs.8; utility
1001 has been fixed. A UFS1 file system created with 64KB
1002 blocksize was incorrectly recognized as one with a broken
1003 superblock. This is because the &os; kernel checks a
1004 partition first for a UFS2 superblock at 64KB offset while it
1005 is possible that a UFS1 file systems with 64KB blocksize has
1006 an alternative superblock at the same location. For example,
1007 a file system created by <command>newfs -U -O 1 -b 65536 -f
1008 8192</command> could lead to this symptom.</para>
1010 <para revision="213049">The &man.hastd.8; utility now supports
1011 <literal>SIGHUP</literal> for reloading the configuration
1012 file. When <literal>SIGTERM</literal> or
1013 <literal>SIGINT</literal> is received, the worker processes
1016 <para revision="212144">The &man.ifconfig.8; utility now check an
1017 invalid CIDR subnet notation more strictly. It wrongly
1018 accepted <literal>10.0.0.1/10.0.0.1</literal> as
1019 <literal>10.0.0.1/10</literal>.</para>
1021 <para revision="215237">An accuracy issue in the &man.jn.3; and
1022 &man.jnf.3; functions in <filename>libm</filename> has been
1025 <para revision="209284">Incorrect behaviors in stuttering
1026 sequences and reverse ranges in the &man.jot.1; utility have
1029 <para revision="213667">The <filename>libarchive</filename>
1030 library and &man.tar.1; utility now support LZMA
1031 (Lempel-Ziv-Markov chain-Algorithm) compression format.</para>
1033 <para revision="215229">The &man.tar.1; utility now supports a
1034 blocksize which is up to <literal>8192</literal> (4MB) in the
1035 <option>-b <replaceable>blocksize</replaceable></option>
1038 <para revision="214442">A bug in the &man.lpr.1; utility that
1039 prevented it from working with some files on a ZFS file system
1040 has been fixed.</para>
1042 <para revision="213978">The <option>-p</option> option in the
1043 &man.mount.8; utility now displays the <literal>rw</literal>
1044 mount option correctly as in the &man.fstab.5; format.</para>
1046 <para revision="213889">The &man.ncal.1; utility has been
1047 updated. The option <option>-b</option> has been replaced
1048 with <option>-C</option> and <option>-B
1049 <replaceable>number</replaceable></option>. Options
1050 <option>-3</option> to show previous, current and next month, and
1051 <option>-A <replaceable>number</replaceable></option> to show
1052 months after current month have been added. The option
1053 <option>-m <replaceable>N</replaceable>
1054 <replaceable>YYYY</replaceable></option> now prints only the
1055 month, not the whole year.</para>
1057 <para revision="211699">The &man.newsyslog.8; utility now supports
1058 an <option>-S <replaceable>pidfile</replaceable></option>
1059 option to override the default &man.syslogd.8; PID
1062 <para revision="215622">The &man.newsyslog.8; utility now
1063 supports a special log file name
1064 <literal><include></literal> for processing file
1065 inclusion. Globbing in the file name and circular dependency
1066 detection are supported. For more details, see
1067 the &man.newsyslog.conf.5; manual page.</para>
1069 <para revision="213980">The &man.ntpd.8; utility is now compiled
1070 with shared memory reference clock driver. For example, GPS
1071 devices can be used as source of precise time via <filename
1072 role="ports">astro/gpsd</filename> in the Ports
1075 <para revision="212848">An off-by-one error in the &man.pax.1;
1076 utility when ustar file name is too long has been
1079 <para revision="209912">The &man.pkill.1; utility now supports
1080 an <option>-l</option> option like the &man.kill.1; utility
1083 <para revision="211098">The &man.pmcstat.8; utility now supports a
1084 file and a network socket as a top source. A new option
1085 <option>-O <replaceable>filename</replaceable></option>
1086 specifies to send log output to
1087 <replaceable>filename</replaceable>, and another new option
1088 <option>-R <replaceable>filename</replaceable></option>
1089 specifies to receive events from
1090 <replaceable>filename</replaceable>. For a socket, the
1091 <replaceable>filename</replaceable> is in a form of
1092 <replaceable>ipaddr:port</replaceable>. This allows top
1093 monitoring over TCP on a system with no local symbols, for
1096 <para revision="210089">The &man.pom.6; utility now
1097 supports a <option>-p</option> flag to print only the
1100 <para revision="212472">The &man.powerd.8; utility now supports
1101 an <option>-m <replaceable>freq</replaceable></option> and
1102 <option>-M <replaceable>freq</replaceable></option> to control
1103 the minimum and maximum frequency, respectively.</para>
1105 <para revision="213825">The &man.ruptime.1; utility now displays
1106 hostnames longer than 12 characters.</para>
1108 <para revision="215066">A behavior of the &man.sh.1; program
1109 when an <option>-u</option> option is specified has been
1110 changed. The special parameters <varname>$@</varname> and
1111 <varname>$*</varname> no longer cause an error when there are
1112 no positional parameters.</para>
1114 <para revision="210616">A bug in the &man.sh.1; program has been
1115 fixed. A <literal>SIGINT</literal> signal is now passed
1116 through from a child process if the shell is interactive and
1117 the job control is enabled. For example, aborting
1118 &man.sleep.1; command by Ctrl-C no longer display
1119 <literal>ok</literal> in the following command line:</para>
1121 <screen>&prompt.user; sleep 5; echo ok</screen>
1123 <para revision="210732">The &man.sh.1; program now supports a
1124 <command>bg</command> command consisting solely of
1125 redirections. For example:</para>
1127 <screen>&prompt.user; < /dev/null &</screen>
1129 <para revision="211536">The &man.sleep.1; utility now supports
1130 the <literal>SIGINFO</literal> signal and reports the specified
1131 sleep time and the remaining time.</para>
1133 <para revision="213036,213038">The &man.tftp.1; and &man.tftpd.8;
1134 utilities have been improved for better interoperability and
1135 they now support RFC 1350, 2347, 2348, 2349, and 3617.</para>
1137 <para revision="213899">A bug in <literal>[=]=]</literal>
1138 equivalent class handling in the &man.tr.1; utility has been
1139 fixed. A closing bracket immediately after
1140 <literal>[=</literal> was incorrectly treated as
1143 <para revision="210566">The &man.uname.1; utility now supports an
1144 <option>-o</option> flag as a synonym for the
1145 <option>-s</option> flag for compatibility with other
1148 <para revision="211060">Bugs in &man.vi.1; utility have been
1149 fixed. They include handling of <literal>^@</literal> and
1150 <literal>^C</literal> in insert mode when reading an ex
1153 <para revision="214345">The &man.watchdogd.8; program now uses
1154 <literal>MADV_PROTECT</literal> memory flag to protect itself
1155 from being terminated by the &os; kernel when available memory
1156 becomes short. This kind of process termination happens in a
1157 swap-intensive workload.</para>
1159 <para revision="209870">The <command>set sharenfs</command>
1160 command in the &man.zfs.8; utility now supports
1161 <option>sec</option> option.</para>
1163 <sect3 xml:id="periodic-scripts">
1164 <title><filename>/etc/periodic</filename> Scripts</title>
1166 <para>A periodic script for <command>zfs scrub</command> has
1167 been added. For more details, see &man.periodic.conf.5;
1170 <para>A periodic script which can be used to find installed
1171 ports' files with mismatched checksum has been added. For more
1172 details, see the &man.periodic.conf.5; manual page.</para>
1176 <sect2 xml:id="contrib">
1177 <title>Contributed Software</title>
1179 <para>The <application>ACPI-CA</application> has been updated to
1182 <para revision="214287">The &man.ee.1; program has been updated
1183 to version 1.5.2.</para>
1185 <para><application>ISC BIND</application> has been updated to
1186 version 9.6-ESV-R3.</para>
1188 <para><application>netcat</application> has been updated to
1191 <para><application>OpenSSL</application> has been updated to
1192 version 0.9.8q.</para>
1194 <para revision="249868"><application>sendmail</application> has
1195 been updated to version 8.14.7.</para>
1197 <para>The <application>timezone</application> database has been
1198 updated to the <application>tzdata2010o</application>
1201 <para>The <application>xz</application> has been updated
1202 from snapshot as of 12 April 2010 to 5.0.0 release</para>
1205 <sect2 xml:id="ports">
1206 <title>Ports/Packages Collection Infrastructure</title>
1208 <para revision="215738">The &man.pkg.create.1; utility now supports LZMA
1209 (<application>xz</application>) compression. Note that the
1210 default is still <application>bzip2</application>.</para>
1213 <sect2 xml:id="releng">
1214 <title>Release Engineering and Integration</title>
1216 <para revision="211007">The &man.sysinstall.8; utility now uses
1217 the following numbers for default and minimum partition sizes:
1218 1GB for <filename>/</filename>, 4GB for
1219 <filename>/var</filename>, and 1GB for
1220 <filename>/tmp</filename>.</para>
1222 <para revision="211009">The &man.sysinstall.8; utility now
1223 attempts to enable &man.getty.8; on a serial port when no VGA
1224 card is detected on the system.</para>
1226 <para>The supported version of
1227 the <application>GNOME</application> desktop environment
1228 (<package>x11/gnome2</package>) has been
1229 updated to 2.32.1.</para>
1231 <para>The supported version of
1232 the <application>KDE</application> desktop environment
1233 (<package>x11/kde4</package>) has been
1234 updated to 4.5.5.</para>
1238 <sect1 xml:id="upgrade">
1239 <title>Upgrading from previous releases of &os;</title>
1241 <para arch="amd64,i386">Upgrades between RELEASE versions (and
1242 snapshots of the various security branches) are supported using
1243 the &man.freebsd-update.8; utility. The binary upgrade
1244 procedure will update unmodified userland utilities, as well as
1245 unmodified GENERIC kernel distributed as a part of an
1246 official &os; release. The &man.freebsd-update.8; utility
1247 requires that the host being upgraded has Internet
1248 connectivity.</para>
1250 <para>An older form of binary upgrade is supported through the
1251 <command>Upgrade</command> option from the main
1252 &man.sysinstall.8; menu on CDROM distribution media. This type
1253 of binary upgrade may be useful on non-&arch.i386;,
1254 non-&arch.amd64; machines or on systems with no Internet
1255 connectivity.</para>
1257 <para>Source-based upgrades (those based on recompiling the &os;
1258 base system from source code) from previous versions are
1259 supported, according to the instructions in
1260 <filename>/usr/src/UPDATING</filename>.</para>
1263 <para>Upgrading &os; should, of course, only be attempted after
1264 backing up <emphasis>all</emphasis> data and configuration