summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorbmah <bmah@FreeBSD.org>2002-10-26 17:13:01 +0000
committerbmah <bmah@FreeBSD.org>2002-10-26 17:13:01 +0000
commit771abe87e237d291f6de6cf71ec02b35084a1ac9 (patch)
tree2cc3105fd1178200acafd4654cf8a9cdbd7b3ce0 /release
parente5d68aabbabff2ae3ffcb696eabaf36529f221b3 (diff)
downloadFreeBSD-src-771abe87e237d291f6de6cf71ec02b35084a1ac9.zip
FreeBSD-src-771abe87e237d291f6de6cf71ec02b35084a1ac9.tar.gz
Get rid of the boilerplate upgrading information in the release notes,
and point to the Early Adopter's Guide instead, at least for the next release or two.
Diffstat (limited to 'release')
-rw-r--r--release/doc/en_US.ISO8859-1/relnotes/article.sgml56
-rw-r--r--release/doc/en_US.ISO8859-1/relnotes/common/new.sgml56
2 files changed, 18 insertions, 94 deletions
diff --git a/release/doc/en_US.ISO8859-1/relnotes/article.sgml b/release/doc/en_US.ISO8859-1/relnotes/article.sgml
index 0c90e0b..e1b3d85 100644
--- a/release/doc/en_US.ISO8859-1/relnotes/article.sgml
+++ b/release/doc/en_US.ISO8859-1/relnotes/article.sgml
@@ -4500,53 +4500,15 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
<sect1>
<title>Upgrading from previous releases of &os;</title>
- <para>If you're upgrading from a previous release of &os;, you
- generally will have three options:
-
- <itemizedlist>
- <listitem>
- <para>Using the binary upgrade option of &man.sysinstall.8;.
- This option is perhaps the quickest, although it presumes
- that your installation of &os; uses no special compilation
- options.</para>
- </listitem>
- <listitem>
- <para>Performing a complete reinstall of &os;. Technically,
- this is not an upgrading method, and in any case is usually less
- convenient than a binary upgrade, in that it requires you to
- manually backup and restore the contents of
- <filename>/etc</filename>. However, it may be useful in
- cases where you want (or need) to change the partitioning of
- your disks.
- </listitem>
- <listitem>
- <para>From source code in <filename>/usr/src</filename>. This
- route is more flexible, but requires more disk space, time,
- and technical expertise. More information can be found
- in the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html"><quote>Using
- <command>make world</command></quote></ulink> section of the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
- Handbook</ulink>. Upgrading from very old
- versions of &os; may be problematic; in cases like this, it
- is usually more effective to perform a binary upgrade or a
- complete reinstall.</para>
- </listitem>
- </itemizedlist>
- </para>
-
- <para>Please read the <filename>INSTALL.TXT</filename> file for more
- information, preferably <emphasis>before</emphasis> beginning an
- upgrade. If you are upgrading from source, please be sure to read
- <filename>/usr/src/UPDATING</filename> as well.</para>
-
- <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 <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html"><quote>-CURRENT
- vs. -STABLE</quote></ulink> section of the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
- Handbook</ulink>.</para>
+ <para>Users with existing &os; systems are
+ <emphasis>highly</emphasis> encouraged to read the <quote>Early
+ Adopter's Guide to &os; 5.0</quote>. This document generally has
+ the filename <filename>EARLY.TXT</filename> on the distribution
+ media, or any other place that the release notes can be found. It
+ offers some notes on upgrading, but more importantly, also
+ discusses some of the relative merits of upgrading to &os;
+ 5.<replaceable>X</replaceable> versus running &os;
+ 4.<replaceable>X</replaceable>.</para>
<important>
<para>Upgrading &os; should, of course, only be attempted after
diff --git a/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml b/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml
index 0c90e0b..e1b3d85 100644
--- a/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml
+++ b/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml
@@ -4500,53 +4500,15 @@ options HZ=1000 # not compulsory but strongly recommended</programlisting>
<sect1>
<title>Upgrading from previous releases of &os;</title>
- <para>If you're upgrading from a previous release of &os;, you
- generally will have three options:
-
- <itemizedlist>
- <listitem>
- <para>Using the binary upgrade option of &man.sysinstall.8;.
- This option is perhaps the quickest, although it presumes
- that your installation of &os; uses no special compilation
- options.</para>
- </listitem>
- <listitem>
- <para>Performing a complete reinstall of &os;. Technically,
- this is not an upgrading method, and in any case is usually less
- convenient than a binary upgrade, in that it requires you to
- manually backup and restore the contents of
- <filename>/etc</filename>. However, it may be useful in
- cases where you want (or need) to change the partitioning of
- your disks.
- </listitem>
- <listitem>
- <para>From source code in <filename>/usr/src</filename>. This
- route is more flexible, but requires more disk space, time,
- and technical expertise. More information can be found
- in the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html"><quote>Using
- <command>make world</command></quote></ulink> section of the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
- Handbook</ulink>. Upgrading from very old
- versions of &os; may be problematic; in cases like this, it
- is usually more effective to perform a binary upgrade or a
- complete reinstall.</para>
- </listitem>
- </itemizedlist>
- </para>
-
- <para>Please read the <filename>INSTALL.TXT</filename> file for more
- information, preferably <emphasis>before</emphasis> beginning an
- upgrade. If you are upgrading from source, please be sure to read
- <filename>/usr/src/UPDATING</filename> as well.</para>
-
- <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 <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html"><quote>-CURRENT
- vs. -STABLE</quote></ulink> section of the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
- Handbook</ulink>.</para>
+ <para>Users with existing &os; systems are
+ <emphasis>highly</emphasis> encouraged to read the <quote>Early
+ Adopter's Guide to &os; 5.0</quote>. This document generally has
+ the filename <filename>EARLY.TXT</filename> on the distribution
+ media, or any other place that the release notes can be found. It
+ offers some notes on upgrading, but more importantly, also
+ discusses some of the relative merits of upgrading to &os;
+ 5.<replaceable>X</replaceable> versus running &os;
+ 4.<replaceable>X</replaceable>.</para>
<important>
<para>Upgrading &os; should, of course, only be attempted after
OpenPOWER on IntegriCloud