Flesh out the compatibility section a little bit. Bump doc date.

svn path=/head/; revision=163666

bin/cp/cp.1

@@ -32,7 +32,7 @@
 .\"	@(#)cp.1	8.3 (Berkeley) 4/18/94
 .\" $FreeBSD$
 .\"
-.Dd October 7, 2006
+.Dd October 24, 2006
 .Dt CP 1
 .Os
 .Sh NAME
@@ -251,38 +251,28 @@ Historic versions of the
 utility had a
 .Fl r
 option.
-This implementation supports that option, however, its use is strongly
+This implementation supports that option, however, its behavior
-discouraged as its behavior is very implementation dependent.
+is different from historical
-In this version of
+.Fx
+behavior.
+Use
+of this option
+is strongly discouraged as the behavior is
+implementation-dependent.
+In this implementation of
 .Nm ,
 .Fl r
-is just a synonym for
+works alike
-.Fl RL .
+.Fl RL
-The
+thus all files, including special files, are copied
-.Fl R
+in a manner similar to normal files.
-option gives the correct behavior while
+Data within these special files
-.Fl L
+will not be copied, only the file itself.
-preserves the sometimes-useful historical behavior of following symbolic links. 
+Historical implemenations
-The
+of
 .Fl r
-option is deprecated in
+differ as they could copy the internal contents of special
-.Tn POSIX 
+files while recreating a hierarchy.
- and its behavior is likely to be different
-in future versions of 
-.Nm
-and its behavior is likely to be different
-in future versions of
-.Fx .
-Previous versions of
-.Nm
-in
-.Fx ,
-the
-.Fl r
-behavior was to not correctly copy special files, symbolic links
-or fifos.
-Symbolic links were followed, and the contents of special
-files and fifos were copied to regular files.
 .Pp
 The
 .Fl v