diff options
authorMurray Stokely <murray@FreeBSD.org>2001-09-02 22:25:56 +0000
committerMurray Stokely <murray@FreeBSD.org>2001-09-02 22:25:56 +0000
commita90b86c5415e774bac25e7ef688063ed2fb5bdfc (patch)
parentf1979ede58acfd640f7ee8c8a58fb46cf3a3546b (diff)
Add a footnote admitting that we can't support old versions of FreeBSD
forever, and point the user to freebsd.org/security for more information about which branches/releases are currently supported. PR: docs/29182 Submitted by: Tony Fleisher <takhus@takhus.mind.net>
Notes: svn path=/head/; revision=10546
1 files changed, 10 insertions, 2 deletions
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>