Date: Fri, 31 May 2002 14:51:26 +1000 (EST) From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/38760: Shrinking text on vinum(4) man page Message-ID: <200205310451.g4V4pP47045343@gsmx07.alcatel.com.au>
next in thread | raw e-mail | index | archive | help
>Number: 38760
>Category: kern
>Synopsis: Shrinking text on vinum(4) man page
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Thu May 30 22:00:06 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Peter Jeremy
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
Alcatel Australia Limited
>Environment:
System: FreeBSD gsmx07.alcatel.com.au 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Tue May 7 08:15:34 EST 2002 root@:/usr/obj/3.0/cvs/src/sys/gsmx i386
Problem also exists in -STABLE.
>Description:
When formatting vinum(4) as Postscript, the text starting from
the section "DEBUGGING PROBLEMS WITH VINUM" shrinks following
each example, becoming illegibly small during the "Kernel
Panics" section. The line spacing for the two lines following
"Configuration problems" is also smaller than it should be.
The man page include raw groff markup to shrink the size and
line-spacing of examples in this section by 3p.
Unfortunately, it seems that either the .Bd or .Ed macros
include a pointsize change so that the trailing "revert to
previous pointsize" command actually reverts to the smaller
point size. The next example then shrinks that by a further
3p. And so on...
>How-To-Repeat:
$ groff -mdoc /usr/src/share/man/man4/vinum.4 >/tmp/vinum.ps
View or print /tmp/vinum.ps
>Fix:
A cleaner and more general solution would be to extend mdoc to
allow examples to be shown in a smaller point size. The
following patch just places the pointsize and spacing changes
within the .Bd/.Ed block so that the "revert to previous
pointsize/spacing" commands apply to the appropriate size change.
Index: vinum.4
===================================================================
RCS file: /home/CVSROOT/src/share/man/man4/vinum.4,v
retrieving revision 1.42
diff -u -r1.42 vinum.4
--- vinum.4 16 May 2002 05:21:44 -0000 1.42
+++ vinum.4 31 May 2002 04:34:41 -0000
@@ -720,36 +720,36 @@
.Nm
configuration. If you do, the first thing you should do is stop configuration
updates:
+.Bd -literal
.if t .ps -3
.if t .vs -3
-.Bd -literal
# vinum setdaemon 4
-.Ed
.if t .vs
.if t .ps
+.Ed
.Pp
This will stop updates and any further corruption of the on-disk configuration.
.Pp
Next, look at the on-disk configuration, using a Bourne-style shell:
+.Bd -literal
.if t .ps -3
.if t .vs -3
-.Bd -literal
# rm -f log
# for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
(dd if=$i skip=8 count=6|tr -d '\e000-\e011\e200-\e377'; echo) >> log
done
-.Ed
.if t .vs
.if t .ps
+.Ed
.Pp
The names of the devices are the names of all
.Nm
slices. The file
.Pa log
should then contain something like this:
+.Bd -literal
.if t .ps -3
.if t .vs -3
-.Bd -literal
IN VINOpanic.lemis.comdrive1}6E7~^K6T^Yfoovolume obj state up
volume src state up
volume raid state down
@@ -769,9 +769,9 @@
sd name obj.p1.s1 drive drive2 plex obj.p1 state reborn len 204800b driveoffset 409865b plexoffset 128b
sd name obj.p1.s2 drive drive3 plex obj.p1 state up len 204800b driveoffset 265b plexoffset 256b
sd name obj.p1.s3 drive drive4 plex obj.p1 state up len 204800b driveoffset 409865b plexoffset 384b
-.Ed
.if t .vs
.if t .ps
+.Ed
.Pp
The first line contains the
.Nm
@@ -904,9 +904,9 @@
.Ar debug
command of
.Xr vinum 8 :
+.Bd -literal
.if t .ps -3
.if t .vs -3
-.Bd -literal
GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc.
Debugger (msg=0xf1093174 "vinum debug") at ../../i386/i386/db_interface.c:318
318 in_Debugger = 0;
@@ -934,21 +934,21 @@
#9 0x804832d in ?? ()
#10 0x80482ad in ?? ()
#11 0x80480e9 in ?? ()
-.Ed
.if t .vs
.if t .ps
+.Ed
.Pp
When entering from the debugger, it's important that the source of frame 1
(listed by the
.Pa .gdbinit
file at the top of the example) contains the text
+.Bd -literal
.if t .ps -3
.if t .vs -3
-.Bd -literal
Debugger ("vinum debug");
-.Ed
.if t .vs
.if t .ps
+.Ed
.Pp
This is an indication that the address specifications are correct. If you get
some other output, your symbols and the kernel module are out of sync, and the
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205310451.g4V4pP47045343>