diff options
author | Jason McIntyre <jmc@cvs.openbsd.org> | 2003-04-11 04:32:29 +0000 |
---|---|---|
committer | Jason McIntyre <jmc@cvs.openbsd.org> | 2003-04-11 04:32:29 +0000 |
commit | c341e62e40dcf89b30d4a2bcf64d515b776dee81 (patch) | |
tree | dd2a9c726fb98b2afc7489db2110c149d2add573 /share/man/man4 | |
parent | f24ceb1e6c7ff64cfd585e68ef0913af97974acf (diff) |
typos;
wscons(4): ok miod@
Diffstat (limited to 'share/man/man4')
-rw-r--r-- | share/man/man4/tp.4 | 12 | ||||
-rw-r--r-- | share/man/man4/vlan.4 | 32 | ||||
-rw-r--r-- | share/man/man4/vnd.4 | 22 | ||||
-rw-r--r-- | share/man/man4/vr.4 | 12 | ||||
-rw-r--r-- | share/man/man4/wb.4 | 14 | ||||
-rw-r--r-- | share/man/man4/we.4 | 6 | ||||
-rw-r--r-- | share/man/man4/wscons.4 | 38 | ||||
-rw-r--r-- | share/man/man4/wsdisplay.4 | 8 | ||||
-rw-r--r-- | share/man/man4/wskbd.4 | 12 | ||||
-rw-r--r-- | share/man/man4/xf86.4 | 14 | ||||
-rw-r--r-- | share/man/man4/xl.4 | 18 |
11 files changed, 97 insertions, 91 deletions
diff --git a/share/man/man4/tp.4 b/share/man/man4/tp.4 index 71119e51c6f..ebab53b2a79 100644 --- a/share/man/man4/tp.4 +++ b/share/man/man4/tp.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: tp.4,v 1.15 2003/03/06 20:40:35 jmc Exp $ +.\" $OpenBSD: tp.4,v 1.16 2003/04/11 04:32:27 jmc Exp $ .\" $NetBSD: tp.4,v 1.4 1994/11/30 16:22:38 jtc Exp $ .\" .\" Copyright (c) 1990, 1991, 1993 @@ -291,7 +291,7 @@ See the description of the flags below. .It Dv TPOPT_PARAMS .Ar struct tp_conn_param .br -Used to get or set a group parameters for a connection. +Used to get or set group parameters for a connection. The .Ar struct tp_conn_param is the argument used with the @@ -308,7 +308,7 @@ structure are described below. .El .Pp -.Em Values for TPOPT_PARAMS: +.Em Values for TPOPT_PARAMS : .Bl -tag -width p_sendack_ticks .It Ar p_Nretrans nonzero short integer [1] @@ -563,7 +563,7 @@ Its meaning is as follows. The bit numbering used is that of the RT PC, which means that bit 0 is the most significant bit, while bit 8 is the least significant bit. .sp 1 -.Em Values for TPOPT_FLAGS: +.Em Values for TPOPT_FLAGS : .Bl -tag -width Bitsx .It Sy Bits .Sy Description [Default] @@ -584,7 +584,7 @@ entity. Not used. .It \&3 .Dv TPFLAG_XPD_PRES : -set when expedited data are present +set when expedited data are present. [0] .It 4\&..7 Reserved. @@ -638,7 +638,7 @@ because the call had not yet returned a legitimate socket descriptor when the signal was handled. .Dv ETIMEDOUT -(or a some other +(or some other .Va errno value appropriate to the type of error) is returned if .Dv SIGURG diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4 index 3b5cff2afa7..c409240c3dc 100644 --- a/share/man/man4/vlan.4 +++ b/share/man/man4/vlan.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: vlan.4,v 1.17 2003/02/18 07:54:53 jmc Exp $ +.\" $OpenBSD: vlan.4,v 1.18 2003/04/11 04:32:28 jmc Exp $ .\" .\" Copyright (c) 2000 The NetBSD Foundation, Inc. .\" All rights reserved. @@ -59,7 +59,9 @@ port(s) the frame can go to. Frames transmitted through the vlan interface will be diverted to the specified physical interface with 802.1Q vlan encapsulation. Frames with 802.1Q encapsulation received by the parent interface with the -correct vlan tag will be diverted to the associated vlan pseudo-interface. +correct vlan tag will be diverted to the associated +.Nm +pseudo-interface. .El .Pp Frame headers which normally contain the destination host, source host, and @@ -78,7 +80,7 @@ etc. The number of interfaces is given by the corresponding .Sy pseudo-device line in the system config file. -.Xr vlan 4 +.Nm interfaces support the following unique .Xr ioctl 2 Ns s : .Bl -tag -width aaa @@ -88,7 +90,7 @@ Set the vlan tag and parent for a given vlan interface. Get the vlan tag and parent for a given vlan interface. .Pp .El -.Xr vlan 4 +.Nm interfaces use the following interface capabilities: .Bl -tag -width aaa .It IFCAP_VLAN_MTU: @@ -100,13 +102,13 @@ The parent interface will participate in the tagging and untagging of frames. .Sh DIAGNOSTICS .Bl -diag .It "vlan%d: initialized with non-standard mtu %d (parent %s)" -The IFCAP_VLAN_MTU capability was not set on the parent interface. +The IFCAP_VLAN_MTU capability was not set on the parent interface. We assume in this event that the parent interface is not capable of handling -frames larger then its MTU. +frames larger than its MTU. This will generally result in a non-compliant 802.1Q implementation. .Pp Some Ethernet chips will either discard or truncate -Ethernet frames that are larger then 1514 bytes. +Ethernet frames that are larger than 1514 bytes. This causes a problem as 802.1Q tagged frames can be up to 1518 bytes. Most controller chips can be told not to discard large frames and/or to increase the allowed frame size. @@ -114,13 +116,13 @@ Refer to the hardware manual for your chip to do this. .El .Pp If the IFCAP_VLAN_MTU capability is set on a vlan parent, -.Xr vlan 4 -assumes that Ethernet chip on the parent can handle +.Nm +assumes that the Ethernet chip on the parent can handle oversized frames. Either the chip allows 1518 byte frames by default (such as .Xr rl 4 ) , the driver has instructed the chip to do so (such as -.Xr fxp 4 +.Xr fxp 4 and .Xr dc 4 ) , or the driver also takes advantage of a hardware tagging capability, @@ -141,7 +143,9 @@ and .%O http://standards.ieee.org/getieee802/802.1.html .Re .Pp -The vlan interface is to be configured with +The +.Nm +interface is to be configured with .Xr ifconfig 8 , see its manual page for more information. .Sh BUGS @@ -150,13 +154,13 @@ as well as Ethernet. This driver only supports such operation with Ethernet devices. .Pp When the IFCAP_VLAN_HWTAGGING capability is set on the parent interface, -.Xr vlan 4 +.Nm does not participate in the actual tagging or untagging of Ethernet frames. It simply passes the vlan ID on to the parent interface for tagging on transmit, -and gets a vlan ID for each packet on receive. +and gets a vlan ID for each packet on receive. The vlan tagged packet is not actually visible to .Ox . -Thus, +Thus, .Xr bpf 4 will show untagged packets on the parent interface, although frames are actually being transmitted and received with tags on the wire. diff --git a/share/man/man4/vnd.4 b/share/man/man4/vnd.4 index e230c1a46dc..afa4984eeca 100644 --- a/share/man/man4/vnd.4 +++ b/share/man/man4/vnd.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: vnd.4,v 1.15 2002/09/26 22:09:53 miod Exp $ +.\" $OpenBSD: vnd.4,v 1.16 2003/04/11 04:32:28 jmc Exp $ .\" $NetBSD: vnd.4,v 1.1 1995/12/30 18:10:48 thorpej Exp $ .\" .\" Copyright (c) 1995 Jason R. Thorpe. @@ -52,8 +52,8 @@ that bypasses the buffercache and thus is suitable for swap on files, but not for building disk-images, and the .Nm svnd ("safe" -.Nm -) variant that goes +.Nm vnd ) +variant that goes through the buffercache, thereby maintaining cache-coherency after the block-device is closed which makes it suitable for creating disk images. The latter is not good for swapping on, though. @@ -63,8 +63,8 @@ how to properly configure disks and pseudo-devices in a kernel configuration file. .Pp In order to compile in support for the -.Nm -, you must add a line similar +.Nm vnd , +you must add a line similar to the following to your kernel configuration file: .Bd -unfilled -offset indent pseudo-device vnd 4 # vnode disk driver @@ -72,7 +72,7 @@ pseudo-device vnd 4 # vnode disk driver .Pp The count argument is how many .Nm vnds -memory is allocated for a boot time. +memory is allocated for at boot time. In this example, no more than 4 .Nm vnds may be configured. @@ -89,15 +89,19 @@ for more information. .Xr MAKEDEV 8 , .Xr config 8 , .Xr disklabel 8 , -.Xr fsck 8 , .Xr fdisk 8 , +.Xr fsck 8 , .Xr mount 8 , .Xr newfs 8 , .Xr vnconfig 8 .Sh HISTORY -The vnode disk driver was originally written at the University of +The +.Nm +disk driver was originally written at the University of Utah. -The svnd variant was first seen in +The +.Nm svnd +variant was first seen in .Ox 2.1 . .Sh BUGS The diff --git a/share/man/man4/vr.4 b/share/man/man4/vr.4 index 2e02b38e229..ea13d78573e 100644 --- a/share/man/man4/vr.4 +++ b/share/man/man4/vr.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: vr.4,v 1.12 2003/01/13 15:55:44 jason Exp $ +.\" $OpenBSD: vr.4,v 1.13 2003/04/11 04:32:28 jmc Exp $ .\" .\" Copyright (c) 1997, 1998 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. @@ -96,7 +96,7 @@ driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex -Force full duplex operation +Force full duplex operation. .It half-duplex Force half duplex operation. .El @@ -130,13 +130,13 @@ configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. -If you see this message at boot time and the driver fails to attach -the device as a network interface, you will have to perform second -warm boot to have the device properly configured. +If this message appears at boot time and the driver fails to attach +the device as a network interface, a second warm boot will have to be +performed to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. -If you power down your system prior to booting +If the system is powered down prior to booting .Ox , the card should be configured correctly. .El diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4 index e122f2e81f2..4e06166a259 100644 --- a/share/man/man4/wb.4 +++ b/share/man/man4/wb.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: wb.4,v 1.10 2002/09/26 22:09:53 miod Exp $ +.\" $OpenBSD: wb.4,v 1.11 2003/04/11 04:32:28 jmc Exp $ .\" .\" Copyright (c) 1997, 1998 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. @@ -98,7 +98,7 @@ driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex -Force full duplex operation +Force full duplex operation. .It half-duplex Force half duplex operation. .El @@ -132,13 +132,13 @@ to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. -If you see this message at boot time and the driver fails to attach -the device as a network interface, you will have to perform second -warm boot to have the device properly configured. +If this message appears at boot time and the driver fails to attach +the device as a network interface, a second warm boot will have to be +performed to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. -If you power down your system prior to booting +If the system is powered down prior to booting .Ox , the card should be configured correctly. .El @@ -166,7 +166,7 @@ driver was written by .Sh BUGS The Winbond chip seems to behave strangely in some cases when the link partner switches modes. -If for example both sides are set to 10Mbps half-duplex, and the other end +If, for example, both sides are set to 10Mbps half-duplex, and the other end is changed to 100Mbps full-duplex, the Winbond's receiver suddenly starts writing trash all over the RX descriptors. The diff --git a/share/man/man4/we.4 b/share/man/man4/we.4 index d2bb9716763..d8fcf22bc64 100644 --- a/share/man/man4/we.4 +++ b/share/man/man4/we.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: we.4,v 1.9 2002/09/26 22:09:53 miod Exp $ +.\" $OpenBSD: we.4,v 1.10 2003/04/11 04:32:28 jmc Exp $ .\" $NetBSD: we.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $ .\" .\" Copyright (c) 1997 The NetBSD Foundation, Inc. @@ -70,7 +70,7 @@ If the transceiver is active, the BNC media is selected. Otherwise, the AUI and UTP ports are both active. Cards of this vintage may also be found which lack one or two of the connectors. -These cards also know what interrupt they are configured for, and will +These cards also know what interrupt they are configured for, and will correct such problems (for further interrupt issues, see .Xr isa 4 and @@ -109,7 +109,7 @@ The IRQ was wildcarded in the kernel configuration file, and the card is a WD8003S, WD8003E, or WD8013EBT, which do not support software IRQ configuration. .It "we0: failed to clear shared memory at offset <off>" -The memory test was unable to clear shared the interface's shared memory +The memory test was unable to clear the interface's shared memory region. This often indicates that the card is configured at a conflicting .Em iomem diff --git a/share/man/man4/wscons.4 b/share/man/man4/wscons.4 index d2c8134eef5..516643e8c06 100644 --- a/share/man/man4/wscons.4 +++ b/share/man/man4/wscons.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: wscons.4,v 1.12 2003/03/05 16:39:34 miod Exp $ +.\" $OpenBSD: wscons.4,v 1.13 2003/04/11 04:32:28 jmc Exp $ .\" $NetBSD: wscons.4,v 1.11 2000/04/13 11:14:42 is Exp $ .\" .\" Copyright (c) 1999 The NetBSD Foundation, Inc. @@ -41,7 +41,7 @@ .Sh SYNOPSIS .Cd option WSEMUL_SUN .Cd option WSEMUL_NO_VT100 -.Cd option \&"WSEMUL_DEFAULT=\e"xxx\e"" +.Cd option WSEMUL_DEFAULT=\&"xxx\&" .Cd option WS_KERNEL_FG=WSCOL_XXX .Cd option WS_KERNEL_BG=WSCOL_XXX .Cd option WSDISPLAY_COMPAT_PCVT @@ -123,7 +123,7 @@ and models. The features of the original .Tn VT100 -which are not or not completely implemented are: +which are not, or not completely, implemented are: .Bl -bullet .It .Tn VT52 @@ -174,20 +174,20 @@ emulator. .Pp The .Va WSEMUL_DEFAULT -kernel option allows to select one of the described terminal options -as default choice. -The default gets into effect in kernel startup, i.e., +kernel option allows selecting one of the described terminal options +as the default choice. +The default goes into effect at kernel startup, i.e., for the operating system console or additional screens allocated through the .Va WSDISPLAY_DEFAULTSCREENS option (see -.Xr wsdisplay 4 -), or if no emulation type was passed to the +.Xr wsdisplay 4 ) , +or if no emulation type was passed to the .Xr wsconscfg 8 utility. .Pp -.Em Compatibility options: -these options allow to run X servers or other programs using low-level +.Em Compatibility options : +these options allow running X servers or other programs using low-level console driver functions which were written specifically for other console drivers to run on .Ox @@ -198,7 +198,7 @@ The options are in particular: Support the protocol for switches between multiple virtual screens on one display as used by most PC-UNIX variants. .It Cd WSDISPLAY_COMPAT_RAWKBD -Allows to get raw XT keyboard scancodes from PC keyboards as needed +Allows getting raw XT keyboard scancodes from PC keyboards as needed by i386 X servers. .It Cd WSDISPLAY_COMPAT_PCVT Emulates enough of the @@ -226,20 +226,18 @@ find the .Nm driver entry points, symlinks are a helpful measure.) .Pp -.Em Other options: +.Em Other options : .Bl -tag -width xxxxxxxx -.It Cd option WS_KERNEL_FG=WSCOL_XXX , -.It Cd option WS_KERNEL_BG=WSCOL_XXX , +.It Cd option WS_KERNEL_FG=WSCOL_XXX +.It Cd option WS_KERNEL_BG=WSCOL_XXX .It Cd option \&WS_KERNEL_COLATTR="(WSATTR_XXX | WSATTR_YYY)" -and .It Cd option \&WS_KERNEL_MONOATTR="(WSATTR_XXX | WSATTR_YYY)" -allow to make console output originating from the kernel appear differently +Make console output originating from the kernel appear differently than output from user level programs (via .Pa /dev/console or the specific tty device like -.Pa /dev/ttyC0 -). +.Pa /dev/ttyC0 ) . .Dq WS_KERNEL_FG and .Dq WS_KERNEL_BG @@ -265,10 +263,10 @@ The virtual screen switching protocol enabled by .Dq WSDISPLAY_COMPAT_USL uses a somewhat complex handshake protocol to pass control to user programs as X servers controlling a virtual screen. -To avoid a non-responsive application to lock the whole console system a +To avoid a non-responsive application locking the whole console system, a screen switch will be rolled back if the user application does not respond to a screen switch request within some time. -This option allows to set this timeout (in seconds), +This option sets the timeout (in seconds); the default value is 5 seconds. .El .Sh SEE ALSO diff --git a/share/man/man4/wsdisplay.4 b/share/man/man4/wsdisplay.4 index 80d5a295937..bce633132e9 100644 --- a/share/man/man4/wsdisplay.4 +++ b/share/man/man4/wsdisplay.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: wsdisplay.4,v 1.19 2003/03/09 02:39:26 miod Exp $ +.\" $OpenBSD: wsdisplay.4,v 1.20 2003/04/11 04:32:28 jmc Exp $ .\" $NetBSD: wsdisplay.4,v 1.5 2000/05/13 15:22:19 mycroft Exp $ .\" .\" Copyright (c) 1999 Matthias Drochner. @@ -103,8 +103,8 @@ display devices are usable as console.) .Pp The logical unit of an independent contents displayed on a display (sometimes referred to as -.Dq virtual terminal -) is called a +.Dq virtual terminal ) +is called a .Dq screen here. If the underlying device driver supports it, multiple screens can @@ -177,8 +177,8 @@ control device .Sh SEE ALSO .Xr agten 4 , .Xr bwtwo 4 , -.Xr cgtwo 4 , .Xr cgthree 4 , +.Xr cgtwo 4 , .Xr cgfour 4 , .Xr cgsix 4 , .Xr cgeight 4 , diff --git a/share/man/man4/wskbd.4 b/share/man/man4/wskbd.4 index 7d6a7cd3c48..cd0ae977674 100644 --- a/share/man/man4/wskbd.4 +++ b/share/man/man4/wskbd.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: wskbd.4,v 1.9 2003/02/19 09:01:47 jmc Exp $ +.\" $OpenBSD: wskbd.4,v 1.10 2003/04/11 04:32:28 jmc Exp $ .\" $NetBSD: wskbd.4,v 1.5 2000/03/20 11:51:59 pk Exp $ .\" .\" Copyright (c) 1999 @@ -64,7 +64,7 @@ keysyms (hardware independent, defined in Handling of .Dq compose sequences. -Characters commonly not present as separate key on keyboards +Characters commonly not present as separate keys on keyboards can be generated after either a special .Dq compose key is pressed or a @@ -92,14 +92,14 @@ The .Nm driver provides a number of ioctl functions to control key maps and other parameters. -These functions are accessible though the associated +These functions are accessible through the associated .Dq wsdisplay device as well. A complete list is in .Pa /usr/include/dev/wscons/wsconsio.h . The .Xr wsconsctl 8 -utility allows to access key maps and other variables. +utility allows access to key maps and other variables. .Pp The .Em console @@ -144,9 +144,9 @@ driver supports it. .Xr comkbd 4 , .Xr hilkbd 4 , .Xr intro 4 , -.Xr wscons 4 , -.Xr wsmux 4 , .Xr pckbd 4 , .Xr ukbd 4 , +.Xr wscons 4 , +.Xr wsmux 4 , .Xr zskbd 4 , .Xr wsconsctl 8 diff --git a/share/man/man4/xf86.4 b/share/man/man4/xf86.4 index cbaf3ef4c45..78215336fda 100644 --- a/share/man/man4/xf86.4 +++ b/share/man/man4/xf86.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: xf86.4,v 1.4 2002/08/24 17:21:44 matthieu Exp $ +.\" $OpenBSD: xf86.4,v 1.5 2003/04/11 04:32:28 jmc Exp $ .\" .\" Copyright (c) 1998 Matthieu Herrb .\" All rights reserved. @@ -42,8 +42,8 @@ and .Va sparc64 the .Pa /dev/xf86 -driver provides access to the memory and I/O ports of a VGA board -and to the PCI configuration registers +driver provides access to the memory and I/O ports of a VGA board +and to the PCI configuration registers for use by the XFree86 X servers when running with a kernel security level > 0. .Pp @@ -54,18 +54,18 @@ Access to the device is allowed when the sysctl variable .Va machdep.allowaperture >= 1. -This variable (which default value is 0) +This variable (which has a default value of 0) can only be manipulated when the security level is <= 0, so it should be set in .Pa /etc/sysctl.conf . -The possible values for -.Va machdep.allowaperture +The possible values for +.Va machdep.allowaperture are: .Bl -tag -width Ds .It 0 the aperture driver is disabled. Opening it returns -.Dv EPERM. +.Dv EPERM. .It 1 the aperture driver allows access to standard VGA framebuffer and BIOS. Access to diff --git a/share/man/man4/xl.4 b/share/man/man4/xl.4 index b390cd4e460..1b2b8197f38 100644 --- a/share/man/man4/xl.4 +++ b/share/man/man4/xl.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: xl.4,v 1.26 2003/01/13 17:25:08 henning Exp $ +.\" $OpenBSD: xl.4,v 1.27 2003/04/11 04:32:28 jmc Exp $ .\" .\" Copyright (c) 1997, 1998 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. @@ -116,7 +116,7 @@ Note that this media type is only available with adapters that have external PHYs or built-in autonegotiation logic. For 3C900 and 3C900B adapters, the driver will choose the mode specified in the EEPROM. -You can change this by adding media options to the appropriate +This can be changed by adding media options to the appropriate .Xr hostname.if 5 file. .It Cm media No 100baseFX Cm mediaopt No full-duplex @@ -139,7 +139,7 @@ Set 10base2 (thin-net) operation (half-duplex only). .Pp For more information on configuring this device, see .Xr ifconfig 8 . -To view a list of media types and options supported by your card try +To view a list of media types and options supported by this card try .Ic ifconfig -m <device> . For example, .Ic ifconfig -m xl0 . @@ -167,7 +167,7 @@ To avoid getting caught in an infinite wait loop, the driver only polls the bit a finite number of times before giving up, at which point it issues this message. This message may be printed during driver initialization on slower machines. -If you see this message but the driver continues to function normally, the +If this message appears but the driver continues to function normally, the message can probably be ignored. .It "xl%d: chip is in D3 power state -- setting to D0" This message applies only to 3C905B adapters, which support power management. @@ -180,13 +180,13 @@ it won't be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. -If you see this message at boot time and the driver fails to attach -the device as a network interface, you will have to perform second -warm boot to have the device properly configured. +If this message appears at boot time and the driver fails to attach +the device as a network interface, a second warm boot will have to be +performed to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. -If you power down your system prior to booting +If the system is powered down prior to booting .Ox , the card should be configured correctly. .It "xl%d: WARNING: no media options bits set in the media options register!" @@ -212,8 +212,8 @@ the author considers it a manufacturing defect. .Xr ie 4 , .Xr ifmedia 4 , .Xr intro 4 , -.Xr ti 4 , .Xr netintro 4 , +.Xr ti 4 , .Xr hostname.if 5 , .Xr ifconfig 8 .Sh HISTORY |