Yikes! I thought I updated these references to sup ages ago.. Hmmmm!

2 files changed, 13 insertions, 13 deletions

diff --git a/share/doc/handbook/current.sgml b/share/doc/handbook/current.sgml
index 269cd33..906885e 100644
--- a/share/doc/handbook/current.sgml
+++ b/share/doc/handbook/current.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: current.sgml,v 1.19 1997/02/22 12:58:16 peter Exp $ -->
+<!-- $Id: current.sgml,v 1.20 1997/05/02 14:15:34 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD CURRENT POLICY 
 
-Last updated: $Date: 1997/02/22 12:58:16 $
+Last updated: $Date: 1997/05/02 14:15:34 $
 
 This document attempts to explain the rationale behind
 FreeBSD-current, what you should expect should you decide to run it,
@@ -113,11 +113,11 @@ subscribe cvs-all
             have a good TCP/IP connection at a flat rate, this is 
             the way to do it.
 
-        <item>  Use the CMU <ref id="sup" name="sup"> program (Software Update
-	     Protocol).
+        <item>  Use the <ref id="cvsup" name="cvsup"> program with
+	    <url url="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile" name="this supfile">.
             This is the second most recommended method, since it allows 
 	    you to grab the entire collection once and then only what has
-            changed from then on.  Many people run sup from cron
+            changed from then on.  Many people run cvsup from cron
             and keep their sources up-to-date automatically.
 
         <item>  Use ftp.  The source tree for FreeBSD-current is always
@@ -139,7 +139,7 @@ subscribe cvs-all
     </enum>
 
     <item>  Essentially, if you need rapid on-demand access to the source and
-    communications bandwidth is not a consideration, use sup or ftp.
+    communications bandwidth is not a consideration, use cvsup or ftp.
     Otherwise, use CTM.
 
     <item>  If you are grabbing the sources to run, and not just look at,
diff --git a/share/doc/handbook/stable.sgml b/share/doc/handbook/stable.sgml
index cecfc54..8bb5b1d 100644
--- a/share/doc/handbook/stable.sgml
+++ b/share/doc/handbook/stable.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: stable.sgml,v 1.10 1997/03/19 03:22:29 obrien Exp $ -->
+<!-- $Id: stable.sgml,v 1.11 1997/05/02 14:15:34 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD STABLE POLICY 
 
-Last updated: $Date: 1997/03/19 03:22:29 $
+Last updated: $Date: 1997/05/02 14:15:34 $
 
 This document attempts to explain the rationale behind
 FreeBSD-stable, what you should expect should you decide to run it,
@@ -69,12 +69,12 @@ next section).
             have a good TCP/IP connection at a flat rate, this is 
             the way to do it.
 
-        <item>  Use the CMU <ref id="sup" name="sup"> program (Software Update
-	     Protocol).
+        <item> Use the <ref id="cvsup" name="cvsup"> program with
+	    <url url="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile" name="this supfile">.
             This is the second most recommended method, since it allows 
 	    you to grab the entire collection once and then only what has
-            changed from then on.  Many people run sup from cron
-            and keep their sources up-to-date automatically.
+            changed from then on.  Many people run cvsup from cron
+            to keep their sources up-to-date automatically.
 
         <item>  Use ftp.  The source tree for FreeBSD-stable is always
             "exported" on:
@@ -96,7 +96,7 @@ next section).
     </enum>
 
     <item>  Essentially, if you need rapid on-demand access to the source and
-    communications bandwidth is not a consideration, use sup or ftp.
+    communications bandwidth is not a consideration, use cvsup or ftp.
     Otherwise, use CTM.
 
     <item>  Before compiling stable, read the Makefile in /usr/src