en_US.ISO8859-1/relnotes/article.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
	"../../../share/xml/freebsd50.dtd" [
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent">
 %release;
]>
<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
  <info><title>&os; &release.current; Release Notes</title>

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

  <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/relnotes/article.xml 260959 2014-01-20 23:59:32Z gjb $</pubdate>

  <copyright>
    <year>2014</year>
    <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
      Project</holder>
  </copyright>

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

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

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

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

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

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

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

  <para>All users are encouraged to consult the release errata before
    installing &os;.  The errata document is updated with
    <quote>late-breaking</quote> information discovered late in the
    release cycle or after the release.  Typically, it contains
    information on known bugs, security advisories, and corrections to
    documentation.  An up-to-date copy of the errata for &os;
    &release.current; can be found on the &os; Web site.</para>
</sect1>

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

  <para>This section describes the most user-visible new or changed
    features in &os; since &release.prev;.  In general, changes
    described here are unique to the &release.branch; branch unless
    specifically marked as &merged; features.</para>

  <para>Typical release note items document recent security advisories
    issued after &release.prev;, new drivers or hardware support, new
    commands or options, major bug fixes, or contributed software
    upgrades.  They may also list changes to major ports/packages or
    release engineering practices.  Clearly the release notes cannot
    list every single change made to &os; between releases; this
    document focuses primarily on security advisories, user-visible
    changes, and major architectural improvements.</para>

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

    <para>No advisories.</para>

  </sect2>

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

    <para revision="260903">Support for GPS ports has been added to
      &man.uhso.4;.</para>

    <para revision="260888">The <filename>VT</filename> kernel
      configuration file has been added, which enables the new
      <literal>vt</literal> console driver.</para>

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

      <para revision="260847">The &man.virtio_random.4; driver has
	been added to harvest entropy from the host system.</para>

      <para revision="260583">Unmapped IO support has been added to
	&man.virtio_scsi.4;.</para>

      <para revision="260582">Unmapped IO support has been added to
	&man.virtio_blk.4;.</para>

      <para revision="260532">Support for <quote>Posted Interrupt
	  Processing</quote> is enabled if supported by the CPU.  This
	feature can be disabled by running <literal>sysctl
	  hw.vmm.vmx.use_apic_pir=0</literal>.  Additionally, to
	persist this setting across reboots, add
	<literal>hw.vmm.vmx.use_apic_pir=0</literal> to
	<filename>/etc/sysctl.conf</filename>.</para>

      <para revision="260410">Support for the <quote>Virtual Interrupt
	  Delivery</quote> feature of &intel;&nbsp;VT-x is enabled if
	supported by the CPU.  This feature can be disabled by running
	<literal>sysctl hw.vmm.vmx.use_apic_vid=0</literal>.
	Additionally, to persist this setting across reboots, add
	<literal>hw.vmm.vmx.use_apic_vid=0</literal> to
	<filename>/etc/sysctl.conf</filename>.</para>
    </sect3>

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

      <para revision="260921">The &man.nand.4; device is enabled for
	ARM devices by default.</para>
    </sect3>

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

      <para>&nbsp;</para>
    </sect3>

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

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

	<para>&nbsp;</para>
      </sect4>

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

	<para revision="260552">Firmware for &intel;
	  Centrino&trade; Wireless-N 105 devices has been added
	  to the base system.</para>

	<para revision="260448">Support for the &intel;
	  Centrino&trade; Wireless-N 135 chipset has been
	  added.</para>
      </sect4>
    </sect3>

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

      <para>&nbsp;</para>
    </sect3>

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

      <para>&nbsp;</para>
    </sect3>

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

      <para>&nbsp;</para>

      <sect4 xml:id="fs-zfs">
	<title>ZFS</title>

	<para>&nbsp;</para>
      </sect4>
    </sect3>
  </sect2>

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

    <para revision="260926">Support for displaying VPD for PCI devices
      via &man.pciconf.8; has been added.</para>

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

    <para revision="260910">Allow &man.pciconf.8; to identify PCI
      devices that are attached to a driver to be identified by their
      device name instead of just the selector.  Additionally, an
      optional device argument to the <literal>-l</literal> flag
      to restrict the output to only listing details about a single
      device.</para>

    <para revision="260594">When unable to load a kernel module with
      &man.kldload.8;, a message informing to view output of
      &man.dmesg.8; is now printed, opposed to the previous output
      <quote>Exec format error.</quote>.</para>

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

      <para>&nbsp;</para>
    </sect3>
  </sect2>

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

    <para>&nbsp;</para>
  </sect2>

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

    <para>&nbsp;</para>
  </sect2>

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

    <para>&nbsp;</para>
  </sect2>

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

    <para>&nbsp;</para>
  </sect2>
</sect1>

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

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

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

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