--- wikisrc/users/mbalmer/keylock.mdwn	2009/12/29 09:25:41	1.3
+++ wikisrc/users/mbalmer/keylock.mdwn	2009/12/29 09:31:15	1.6
@@ -18,14 +18,17 @@ can access them through the <b>hw.keyloc
 
 The following components have been added:
 
-* '''{{manual page|gpiolock|4|}}''' a driver for GPIO attached keylocks.
+* <b>[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)</b>
+a driver for GPIO attached keylocks.
  The driver registers with the in-kernel keylock "subsystem". See
 [gpiolock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/dev/gpio/gpiolock.c?rev=HEAD).
 
-* <b>secmodel_keylock</b>, a {{manual page|kauth|9}} security model that
+* <b>secmodel_keylock</b>, a
+[kauth(9)](http://netbsd.gw.com/cgi-bin/man-cgi?kauth+9+NetBSD-current)
+security model that
 authorizes based on the keylock "closedness".  Wheter the rightmost
 (default) or leftmost position of the keylock means open can be
-controlled using the '''hw.keylock.order''' sysctl variable. This
+controlled using the <b>hw.keylock.order</b> sysctl variable. This
 variable can only be changed if the keylock state is OPEN. See
 [secmodel_keylock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/secmodel/keylock/secmodel_keylock.c?rev=HEAD).
 
@@ -36,7 +39,7 @@ model as well (e.g. to provide keylock s
 Useful e.g. for POS applications).
 
 The keylock state interpretation is done in
-[keylock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/dev/keylock.c)
+[keylock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/dev/keylock.c?rev=HEAD)
 and not in the driver itself.  This
 allows for adding support for multiple keylocks in the future.  The
 hw.keylock.pos and hw.keylock.npos sysctl variable have debugging
@@ -49,7 +52,8 @@ that means leaves room for interpretatio
 show what makes sense in the end).
 
 To enable the keylock support, the keylock security model, and the
-{{manual page|gpiolock|4|}} driver, add the following lines to your
+[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)
+driver, add the following lines to your
 kernel configuration file:
 
 	options KEYLOCK
@@ -57,7 +61,8 @@ kernel configuration file:
 	gpiolock* at gpio?
 
 Of course you must have at least one GPIO device in your system for the
-{{manual page|gpiolock|4|}} driver to work and the lock must be
+[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)
+driver to work and the lock must be
 connected properly.
 
 <b>Please keep in mind that this is an experimental feature...</b>