summaryrefslogtreecommitdiffstats
path: root/release/doc
diff options
context:
space:
mode:
authorbmah <bmah@FreeBSD.org>2002-11-09 19:53:02 +0000
committerbmah <bmah@FreeBSD.org>2002-11-09 19:53:02 +0000
commitf87f5e42f8951e77f0645f9f700d5b3bfc3c17b2 (patch)
treeb951508fefd2730f98a786569fd90ee980ce96ad /release/doc
parentd3b65a80d2345887ec791cc6f9d904d9047689ee (diff)
downloadFreeBSD-src-f87f5e42f8951e77f0645f9f700d5b3bfc3c17b2.zip
FreeBSD-src-f87f5e42f8951e77f0645f9f700d5b3bfc3c17b2.tar.gz
Add a warning against trying to do a binary upgrade from 4.X to 5.X.
Diffstat (limited to 'release/doc')
-rw-r--r--release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml13
1 files changed, 13 insertions, 0 deletions
diff --git a/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml b/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml
index ab6db10..7b3a629 100644
--- a/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml
+++ b/release/doc/en_US.ISO8859-1/installation/common/upgrade.sgml
@@ -30,6 +30,19 @@
&os;. This is <emphasis>not</emphasis> recommended.</para>
</important>
+ <warning>
+ <para>Binary upgrades to &os; &release.current; from &os; 4-STABLE
+ are not supported at this time. There are some files present in
+ a &os; 4-STABLE whose presence can be disruptive, but are not
+ removed by a binary upgrade. One notable example is that an old
+ <filename>/usr/include/g++</filename> directory will cause C++
+ programs to compile incorrectly (or not at all).<para>
+
+ <para>These upgrade instructions are provided for the use of users
+ upgrading from relatively recent &os; &release.branch;
+ snapshots.</para>
+ </warning>
+
<sect2>
<title>Introduction</title>
OpenPOWER on IntegriCloud