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