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;
<!ENTITY % sponsor PUBLIC "-//FreeBSD//ENTITIES Sponsor Specification//EN" "sponsor.ent">
 %sponsor;
<!ENTITY % vendor PUBLIC "-//FreeBSD//ENTITIES Vendor Specification//EN" "vendor.ent">
 %vendor;
]>
<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: stable/10/release/doc/en_US.ISO8859-1/relnotes/article.xml 276720 2015-01-05 20:34:00Z gjb $</pubdate>

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

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

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

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

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

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

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

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

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

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

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

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

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

      <para>&nbsp;</para>

    </sect2>

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

      <para>&nbsp;</para>

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

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

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

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

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

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

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

	<para>&nbsp;</para>

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

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

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

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

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

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

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

	<para revision="274939" contrib="sponsor" sponsor="&ix;">The
	  &man.ctld.8; utility has been updated to include support for
	  registering <acronym>iSCSI</acronym> targets and portals on
	  <acronym>iSNS</acronym> servers.  This provides a mechanism
	  which allows <acronym>iSCSI</acronym> initiators to find
	  targets and portals without requiring active
	  discovery.</para>
      </sect3>

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

	<para revision="275490">A new tunable,
	  <literal>vfs.zfs.spa_slop_shift</literal>, has been added,
	  which controls how much space is reserved by default.</para>
      </sect3>
    </sect2>

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

      <para revision="275040">A new file configuration library,
	&man.figpar.3;, has been added to the base system.</para>

      <para revision="275040">A new utility, &man.dpv.1;, has been
	added to the base system, providing a &man.dialog.1;-style
	progress view from one or more input streams.  A corresponding
	library, &man.dpv.3;, has also been added.</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 <filename>GENERIC</filename> kernel 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>