diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
index 8b35ac0a41..24fc577a91 100644
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.86 2001/08/19 23:46:43 dd Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.87 2001/08/22 06:53:19 murray Exp $
 -->
 
 <chapter id="cutting-edge">
@@ -312,7 +312,15 @@ subscribe cvs-all</programlisting>
 	  &os.stable; branch, you do not <emphasis>need</emphasis> to
 	  track &os.stable; to do this. Every security advisory for
 	  FreeBSD explains how to fix the problem for the releases it
-	  affects, and tracking an entire development branch just
+	  affects
+	  <footnote><para>That's not quite true.  We can't continue to
+  	    support old releases of FreeBSD forever, although we do
+  	    support them for many years.  For a complete description
+  	    of the current security policy for old releases of
+  	    FreeBSD, please see <ulink
+  	    url="http://www.FreeBSD.org">http://www.FreeBSD.org/security</ulink></para>
+	  </footnote>
+	  , and tracking an entire development branch just
 	  for security reasons is likely to bring in a lot of unwanted
 	  changes as well.</para>