1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-18 10:35:55 +00:00

Whitespace and wordwrap fixes, no content or markup changes.

This commit is contained in:
Bruce A. Mah 2002-02-18 21:22:08 +00:00
parent 6d9533da76
commit 4fcc34b3d8
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=90871
2 changed files with 78 additions and 74 deletions

View File

@ -24,31 +24,33 @@
<sect1> <sect1>
<title>Introduction</title> <title>Introduction</title>
<para>This document contains the release notes for &os; &release.current; on <para>This document contains the release notes for &os;
the &arch.print; hardware platform. It describes new features of &os; &release.current; on the &arch.print; hardware platform. It
that have been added (or changed) since &release.prev;. It also describes new features of &os; that have been added (or changed)
provides some notes on upgrading from previous versions of &os;.</para> since &release.prev;. It also provides some notes on upgrading
from previous versions of &os;.</para>
<![ %release.type.snapshot [ <![ %release.type.snapshot [
<para>The &release.type; distribution to which these release notes <para>The &release.type; distribution to which these release notes
apply represents a point along the &release.branch; development apply represents a point along the &release.branch; development
branch between &release.prev; and the future &release.next;. Some pre-built, branch between &release.prev; and the future &release.next;. Some
binary &release.type; distributions along this branch can be found pre-built, binary &release.type; distributions along this branch
at <ulink url="&release.url;"></ulink>.</para> can be found at <ulink url="&release.url;"></ulink>.</para>
]]> ]]>
<![ %release.type.release [ <![ %release.type.release [
<para>This distribution of &os; &release.current; is a &release.type; <para>This distribution of &os; &release.current; is a
distribution. It can be found at <ulink &release.type; distribution. It can be found at <ulink
url="&release.url;"></ulink> or any of its mirrors. More url="&release.url;"></ulink> or any of its mirrors. More
information on obtaining this (or other) &release.type; distributions of information on obtaining this (or other) &release.type;
&os; can be found in the <ulink distributions of &os; can be found in the <ulink
url="http://www.FreeBSD.org/handbook/mirrors.html"><quote>Obtaining url="http://www.FreeBSD.org/handbook/mirrors.html"><quote>Obtaining
FreeBSD</quote> appendix</ulink> to the <ulink FreeBSD</quote> appendix</ulink> to the <ulink
url="http://www.FreeBSD.org/handbook/">FreeBSD Handbook</ulink>.</para> url="http://www.FreeBSD.org/handbook/">FreeBSD
Handbook</ulink>.</para>
]]> ]]>
</sect1> </sect1>
@ -57,17 +59,17 @@
<title>What's New</title> <title>What's New</title>
<para>This section describes the most user-visible new or changed <para>This section describes the most user-visible new or changed
features in &os; since &release.prev;. Typical release note items features in &os; since &release.prev;. Typical release note items
document new drivers or hardware support, new commands or options, document new drivers or hardware support, new commands or options,
major bugfixes, or contributed software upgrades. Security major bugfixes, or contributed software upgrades. Security
advisories issued after &release.prev; are also listed. In general, changes advisories issued after &release.prev; are also listed. In
described here are unique to the &release.branch; branch unless general, changes described here are unique to the &release.branch;
specifically marked as &merged; features.</para> branch unless specifically marked as &merged; features.</para>
<para>Many additional changes were made to &os; that are not listed <para>Many additional changes were made to &os; that are not listed
here for lack of space. For example, documentation was corrected here for lack of space. For example, documentation was corrected
and improved, minor bugs were fixed, insecure coding practices were and improved, minor bugs were fixed, insecure coding practices
audited and corrected, and source code was cleaned up.</para> were audited and corrected, and source code was cleaned up.</para>
<sect2 id="kernel"> <sect2 id="kernel">
<title>Kernel Changes</title> <title>Kernel Changes</title>
@ -2935,7 +2937,7 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
<title>Upgrading from previous releases of &os;</title> <title>Upgrading from previous releases of &os;</title>
<para>If you're upgrading from a previous release of &os;, you <para>If you're upgrading from a previous release of &os;, you
generally will have three options: generally will have three options:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -2965,22 +2967,22 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
</para> </para>
<para>Please read the <filename>INSTALL.TXT</filename> file for more <para>Please read the <filename>INSTALL.TXT</filename> file for more
information, preferably <emphasis>before</emphasis> beginning an information, preferably <emphasis>before</emphasis> beginning an
upgrade. If you are upgrading from source, please be sure to read upgrade. If you are upgrading from source, please be sure to read
<filename>/usr/src/UPDATING</filename> as well.</para> <filename>/usr/src/UPDATING</filename> as well.</para>
<para>Finally, if you want to use one of various means to track the <para>Finally, if you want to use one of various means to track the
-STABLE or -CURRENT branches of &os;, please be sure to consult the -STABLE or -CURRENT branches of &os;, please be sure to consult
<ulink the <ulink
url="http://www.FreeBSD.org/handbook/current-stable.html"><quote>-CURRENT url="http://www.FreeBSD.org/handbook/current-stable.html"><quote>-CURRENT
vs. -STABLE</quote></ulink> section of the <ulink vs. -STABLE</quote></ulink> section of the <ulink
url="http://www.FreeBSD.org/handbook/">FreeBSD url="http://www.FreeBSD.org/handbook/">FreeBSD
Handbook</ulink>.</para> Handbook</ulink>.</para>
<important> <important>
<para>Upgrading &os; should, of course, only be attempted after <para>Upgrading &os; should, of course, only be attempted after
backing up <emphasis>all</emphasis> data and configuration backing up <emphasis>all</emphasis> data and configuration
files.</para> files.</para>
</important> </important>
</sect1> </sect1>

View File

@ -24,31 +24,33 @@
<sect1> <sect1>
<title>Introduction</title> <title>Introduction</title>
<para>This document contains the release notes for &os; &release.current; on <para>This document contains the release notes for &os;
the &arch.print; hardware platform. It describes new features of &os; &release.current; on the &arch.print; hardware platform. It
that have been added (or changed) since &release.prev;. It also describes new features of &os; that have been added (or changed)
provides some notes on upgrading from previous versions of &os;.</para> since &release.prev;. It also provides some notes on upgrading
from previous versions of &os;.</para>
<![ %release.type.snapshot [ <![ %release.type.snapshot [
<para>The &release.type; distribution to which these release notes <para>The &release.type; distribution to which these release notes
apply represents a point along the &release.branch; development apply represents a point along the &release.branch; development
branch between &release.prev; and the future &release.next;. Some pre-built, branch between &release.prev; and the future &release.next;. Some
binary &release.type; distributions along this branch can be found pre-built, binary &release.type; distributions along this branch
at <ulink url="&release.url;"></ulink>.</para> can be found at <ulink url="&release.url;"></ulink>.</para>
]]> ]]>
<![ %release.type.release [ <![ %release.type.release [
<para>This distribution of &os; &release.current; is a &release.type; <para>This distribution of &os; &release.current; is a
distribution. It can be found at <ulink &release.type; distribution. It can be found at <ulink
url="&release.url;"></ulink> or any of its mirrors. More url="&release.url;"></ulink> or any of its mirrors. More
information on obtaining this (or other) &release.type; distributions of information on obtaining this (or other) &release.type;
&os; can be found in the <ulink distributions of &os; can be found in the <ulink
url="http://www.FreeBSD.org/handbook/mirrors.html"><quote>Obtaining url="http://www.FreeBSD.org/handbook/mirrors.html"><quote>Obtaining
FreeBSD</quote> appendix</ulink> to the <ulink FreeBSD</quote> appendix</ulink> to the <ulink
url="http://www.FreeBSD.org/handbook/">FreeBSD Handbook</ulink>.</para> url="http://www.FreeBSD.org/handbook/">FreeBSD
Handbook</ulink>.</para>
]]> ]]>
</sect1> </sect1>
@ -57,17 +59,17 @@
<title>What's New</title> <title>What's New</title>
<para>This section describes the most user-visible new or changed <para>This section describes the most user-visible new or changed
features in &os; since &release.prev;. Typical release note items features in &os; since &release.prev;. Typical release note items
document new drivers or hardware support, new commands or options, document new drivers or hardware support, new commands or options,
major bugfixes, or contributed software upgrades. Security major bugfixes, or contributed software upgrades. Security
advisories issued after &release.prev; are also listed. In general, changes advisories issued after &release.prev; are also listed. In
described here are unique to the &release.branch; branch unless general, changes described here are unique to the &release.branch;
specifically marked as &merged; features.</para> branch unless specifically marked as &merged; features.</para>
<para>Many additional changes were made to &os; that are not listed <para>Many additional changes were made to &os; that are not listed
here for lack of space. For example, documentation was corrected here for lack of space. For example, documentation was corrected
and improved, minor bugs were fixed, insecure coding practices were and improved, minor bugs were fixed, insecure coding practices
audited and corrected, and source code was cleaned up.</para> were audited and corrected, and source code was cleaned up.</para>
<sect2 id="kernel"> <sect2 id="kernel">
<title>Kernel Changes</title> <title>Kernel Changes</title>
@ -2935,7 +2937,7 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
<title>Upgrading from previous releases of &os;</title> <title>Upgrading from previous releases of &os;</title>
<para>If you're upgrading from a previous release of &os;, you <para>If you're upgrading from a previous release of &os;, you
generally will have three options: generally will have three options:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -2965,22 +2967,22 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
</para> </para>
<para>Please read the <filename>INSTALL.TXT</filename> file for more <para>Please read the <filename>INSTALL.TXT</filename> file for more
information, preferably <emphasis>before</emphasis> beginning an information, preferably <emphasis>before</emphasis> beginning an
upgrade. If you are upgrading from source, please be sure to read upgrade. If you are upgrading from source, please be sure to read
<filename>/usr/src/UPDATING</filename> as well.</para> <filename>/usr/src/UPDATING</filename> as well.</para>
<para>Finally, if you want to use one of various means to track the <para>Finally, if you want to use one of various means to track the
-STABLE or -CURRENT branches of &os;, please be sure to consult the -STABLE or -CURRENT branches of &os;, please be sure to consult
<ulink the <ulink
url="http://www.FreeBSD.org/handbook/current-stable.html"><quote>-CURRENT url="http://www.FreeBSD.org/handbook/current-stable.html"><quote>-CURRENT
vs. -STABLE</quote></ulink> section of the <ulink vs. -STABLE</quote></ulink> section of the <ulink
url="http://www.FreeBSD.org/handbook/">FreeBSD url="http://www.FreeBSD.org/handbook/">FreeBSD
Handbook</ulink>.</para> Handbook</ulink>.</para>
<important> <important>
<para>Upgrading &os; should, of course, only be attempted after <para>Upgrading &os; should, of course, only be attempted after
backing up <emphasis>all</emphasis> data and configuration backing up <emphasis>all</emphasis> data and configuration
files.</para> files.</para>
</important> </important>
</sect1> </sect1>