summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorkuriyama <kuriyama@FreeBSD.org>2002-04-16 01:21:06 +0000
committerkuriyama <kuriyama@FreeBSD.org>2002-04-16 01:21:06 +0000
commit4cd83dc2744f6f4c0a41b653c2d2ea05511d56b9 (patch)
tree3aeb62abbd965242620ee29c159d9e53dce10cb7 /share
parentda4022a8af0f621e4984867072647fc70a268e1f (diff)
downloadFreeBSD-src-4cd83dc2744f6f4c0a41b653c2d2ea05511d56b9.zip
FreeBSD-src-4cd83dc2744f6f4c0a41b653c2d2ea05511d56b9.tar.gz
Change reference path/URL.
Submitted by: Olivier Tharan <olivier.tharan@idealx.com> PR: docs/37094 MFC after: 1 week
Diffstat (limited to 'share')
-rw-r--r--share/man/man4/vinum.44
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man4/vinum.4 b/share/man/man4/vinum.4
index 7bf9879..2edbcb8 100644
--- a/share/man/man4/vinum.4
+++ b/share/man/man4/vinum.4
@@ -805,9 +805,9 @@ command if you have this kind of trouble.
In order to analyse a panic which you suspect comes from
.Nm
you will need to build a debug kernel. See the online handbook at
-.Pa /usr/share/doc/handbook/kerneldebug.html
+.Pa /usr/share/doc/en/books/developers-handbook/kerneldebug.html
(if installed) or
-.Pa http://www.FreeBSD.org/handbook/kerneldebug.html
+.Pa http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
for more details of how to do this.
.Pp
Perform the following steps to analyse a
OpenPOWER on IntegriCloud