Reference dhcpcd-code(8) as well as unvis(1).

diff --git a/dhcpcd.8.in b/dhcpcd.8.in
index 215c73e4f4aa0a72ba8ed9618be96d3099a0fdc7..24f577c476637e7db1299a7d3e9e7c8a8fd20f7b 100644 (file)
--- a/dhcpcd.8.in
+++ b/dhcpcd.8.in
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd September 26, 2014
+.Dd September 28, 2014
 .Dt DHCPCD 8
 .Os
 .Sh NAME
@@ -211,9 +211,13 @@ printable characters in escaped octal and escaping the following characters:
 \*[Lt]tab\*[Gt] \*[Lt]newline\*[Gt]
 .Pp
 It is possible to reverse this encoding by passing the variable to
-.Xr unvis 1 ,
+.Xr dhcpcd-decode 8 ,
 like so:
-.D1 printf \*q%s\*q \*qvariable_name\*q | unvis
+.D1 dhcpcd-decode \*q$variable_name\*q
+or to
+.Xr unvis 1
+like so:
+.D1 printf \*q%s\*q \*q$variable_name\*q | unvis
 .Ss Fine tuning
 You can fine-tune the behaviour of
 .Nm
@@ -642,23 +646,6 @@ to rebind, reconfigure or exit need to include the same restrictive flags
 so that
 .Nm
 knows which process to signal.
-.Pp
-.Nm
-sanitises variables using the
-.Xr svis 3
-function with the
-.Dv VIS_CTYPE
-and
-.Dv VIS_OCTAL
-flags which your libc may provide,
-or it's own compatible one if not.
-Some
-.Xr unvis 1
-implementations may not decode either correctly, depending on how they
-handle VIS_CTYPE in both
-.Xr vis 3
-and
-.Xr unvis 3 .
 .Sh FILES
 .Bl -ohang
 .It Pa @SYSCONFDIR@/dhcpcd.conf
@@ -712,6 +699,7 @@ Control socket to per interface daemon.
 .Xr if_nametoindex 3 ,
 .Xr dhcpcd.conf 5 ,
 .Xr resolv.conf 5 ,
+.Xr dhcpcd-decode 8 ,
 .Xr dhcpcd-run-hooks 8 ,
 .Xr resolvconf 8
 .Sh STANDARDS