d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix mandoc warnings/errors.

Browse Source 
MFC after:	1 week
This commit is contained in:
Christian Brueffer 2015-08-12 11:56:19 +00:00
parent f3fe76ecd8
commit 548afe2bec
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=286663
19 changed files with 36 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
share/man/man4/cloudabi.4
View File

@ -99,5 +99,4 @@ cloudlibc on GitHub:
CloudABI support first appeared in CloudABI support first appeared in
.Fx 11.0 . .Fx 11.0 .
.Sh AUTHORS .Sh AUTHORS
Nuxi: .An Nuxi : Pa https://nuxi.nl/ .
.Pa https://nuxi.nl/ .

1
share/man/man4/ctl.4
View File

@ -119,6 +119,7 @@ In the event that there is no response within that time the session gets
forcibly terminated. forcibly terminated.
Set to 0 to disable sending NOP-In PDUs. Set to 0 to disable sending NOP-In PDUs.
Defaults to 5. Defaults to 5.
.El
.Sh SEE ALSO .Sh SEE ALSO
.Xr ctladm 8 , .Xr ctladm 8 ,
.Xr ctld 8 , .Xr ctld 8 ,

1
share/man/man4/em.4
View File

@ -307,5 +307,4 @@ The
driver was written by driver was written by
.An Intel Corporation Aq Mt freebsd@intel.com . .An Intel Corporation Aq Mt freebsd@intel.com .
.Sh BUGS .Sh BUGS
.Pp
Activating EM_MULTIQUEUE support requires MSI-X features. Activating EM_MULTIQUEUE support requires MSI-X features.

1
share/man/man4/gre.4
View File

@ -154,7 +154,6 @@ ifconfig greN create
ifconfig greN inet 198.51.100.1 203.0.113.1 ifconfig greN inet 198.51.100.1 203.0.113.1
ifconfig greN inet tunnel 198.51.100.1 203.0.113.1 tunnelfib 1 ifconfig greN inet tunnel 198.51.100.1 203.0.113.1 tunnelfib 1
.Ed .Ed
.Pp
.Sh NOTES .Sh NOTES
The MTU of The MTU of
.Nm .Nm

3
share/man/man4/hptiop.4
View File

@ -135,4 +135,5 @@ device driver first appeared in
.Sh AUTHORS .Sh AUTHORS
The The
.Nm .Nm
driver was written by HighPoint Technologies, Inc. driver was written by
.An HighPoint Technologies, Inc.

4
share/man/man4/man4.i386/wl.4
View File

@ -165,7 +165,9 @@ ported the Mach drivers to BSDI.
ported them to ported them to
.Fx 2.1 . .Fx 2.1 .
.An Michael Smith .An Michael Smith
ported the wl driver only to 2.2.2. ported the
.Nm
driver only to 2.2.2.
Jim and Michael have been Jim and Michael have been
maintaining them. maintaining them.
The current state of the driver is NOT ANYONE'S The current state of the driver is NOT ANYONE'S

14
share/man/man4/ng_btsocket.4
View File

@ -45,8 +45,8 @@ module implements three Netgraph node types.
Each type in its turn implements one protocol within Each type in its turn implements one protocol within
.Dv PF_BLUETOOTH .Dv PF_BLUETOOTH
domain. domain.
.Sh Dv BLUETOOTH_PROTO_HCI Sh protocol .Sh Dv BLUETOOTH_PROTO_HCI protocol
.Ss Dv SOCK_RAW Ss HCI sockets .Ss Dv SOCK_RAW HCI sockets
Implemented by Implemented by
.Nm btsock_hci_raw .Nm btsock_hci_raw
Netgraph type. Netgraph type.
@ -147,7 +147,7 @@ level can be used to obtain via
or change via or change via
.Xr setsockopt 2 .Xr setsockopt 2
raw HCI socket's filter. raw HCI socket's filter.
.Sh Dv BLUETOOTH_PROTO_L2CAP Sh protocol .Sh Dv BLUETOOTH_PROTO_L2CAP protocol
The Bluetooth L2CAP socket address is defined as follows: The Bluetooth L2CAP socket address is defined as follows:
.Bd -literal -offset indent .Bd -literal -offset indent
/* Bluetooth version of struct sockaddr for L2CAP sockets */ /* Bluetooth version of struct sockaddr for L2CAP sockets */
@ -158,7 +158,7 @@ struct sockaddr_l2cap {
bdaddr_t l2cap_bdaddr; /* address */ bdaddr_t l2cap_bdaddr; /* address */
}; };
.Ed .Ed
.Ss Dv SOCK_RAW Ss L2CAP sockets .Ss Dv SOCK_RAW L2CAP sockets
Implemented by Implemented by
.Nm btsock_l2c_raw .Nm btsock_l2c_raw
Netgraph type. Netgraph type.
@ -204,7 +204,7 @@ The
variable, that can be examined and set via variable, that can be examined and set via
.Xr sysctl 8 , .Xr sysctl 8 ,
controls the control request timeout (in seconds) for raw L2CAP sockets. controls the control request timeout (in seconds) for raw L2CAP sockets.
.Ss Dv SOCK_SEQPACKET Ss L2CAP sockets .Ss Dv SOCK_SEQPACKET L2CAP sockets
Implemented by Implemented by
.Nm btsock_l2c .Nm btsock_l2c
Netgraph type. Netgraph type.
@ -264,7 +264,7 @@ Get (set) value of the flush timeout.
Not implemented. Not implemented.
.Ef .Ef
.El .El
.Sh Dv BLUETOOTH_PROTO_RFCOMM Sh protocol .Sh Dv BLUETOOTH_PROTO_RFCOMM protocol
The Bluetooth RFCOMM socket address is defined as follows: The Bluetooth RFCOMM socket address is defined as follows:
.Bd -literal -offset indent .Bd -literal -offset indent
/* Bluetooth version of struct sockaddr for RFCOMM sockets */ /* Bluetooth version of struct sockaddr for RFCOMM sockets */
@ -275,7 +275,7 @@ struct sockaddr_rfcomm {
uint8_t rfcomm_channel; /* channel */ uint8_t rfcomm_channel; /* channel */
}; };
.Ed .Ed
.Ss Dv SOCK_STREAM Ss RFCOMM sockets .Ss Dv SOCK_STREAM RFCOMM sockets
Note that RFCOMM sockets do not have associated Netgraph node type. Note that RFCOMM sockets do not have associated Netgraph node type.
RFCOMM sockets are implemented as additional layer on top of L2CAP sockets. RFCOMM sockets are implemented as additional layer on top of L2CAP sockets.
RFCOMM sockets are either RFCOMM sockets are either

2
share/man/man4/siftr.4
View File

@ -345,7 +345,7 @@ network interface card and drivers being used.
.Bl -tag -offset indent -width Va .Bl -tag -offset indent -width Va
.It Va 28 .It Va 28
Flow type for the connection. Flow type for the connection.
Flowtype defines which protocol fields are hashed to produce the flowid. Flowtype defines which protocol fields are hashed to produce the flowid.
A complete listing is available in A complete listing is available in
.Pa sys/mbuf.h .Pa sys/mbuf.h
under under

2
share/man/man4/snp.4
View File

@ -85,7 +85,7 @@ driver was rewritten to work with the replaced TTY subsystem.
.Sh AUTHORS .Sh AUTHORS
.An -nosplit .An -nosplit
The author of the current implementation is The author of the current implementation is
.An Ed Schouten Aq Mt ed@FreeBSD.org . .An \&Ed Schouten Aq Mt ed@FreeBSD.org .
Previous versions of Previous versions of
.Nm .Nm
were based on code written by were based on code written by

2
share/man/man4/uftdi.4
View File

@ -193,7 +193,7 @@ struct uftdi_eeio
.Pp .Pp
The FT232R chip has an internal eeprom. The FT232R chip has an internal eeprom.
An external serial eeprom is optional on other FTDI chips. An external serial eeprom is optional on other FTDI chips.
The eeprom may contain 64, 128, or 256 words, The eeprom may contain 64, 128, or 256 words,
depending on the part used. depending on the part used.
Multiple calls may be needed to read or write the larger parts. Multiple calls may be needed to read or write the larger parts.
When no eeprom is present, all words in the returned data are 0xffff. When no eeprom is present, all words in the returned data are 0xffff.

4
share/man/man4/vt.4
View File

@ -327,8 +327,8 @@ driver first appeared in
The The
.Nm .Nm
device driver was developed by device driver was developed by
.An Ed Schouten Aq Mt ed@FreeBSD.org , .An \&Ed Schouten Aq Mt ed@FreeBSD.org ,
.An Ed Maste Aq Mt emaste@FreeBSD.org , .An \&Ed Maste Aq Mt emaste@FreeBSD.org ,
and and
.An Aleksandr Rybalko Aq Mt ray@FreeBSD.org , .An Aleksandr Rybalko Aq Mt ray@FreeBSD.org ,
with sponsorship provided by the with sponsorship provided by the

1
share/man/man7/release.7
View File

@ -435,7 +435,6 @@ include support for each hosting provider by default.
The following The following
.Xr make 1 .Xr make 1
environment variables are supported: environment variables are supported:
.Pp
.Bl -tag -width Ev .Bl -tag -width Ev
.It Va CLOUDWARE .It Va CLOUDWARE
Set to a list of one or more cloud hosting providers, enclosed in quotes. Set to a list of one or more cloud hosting providers, enclosed in quotes.

2
share/man/man8/nanobsd.8
View File

@ -104,7 +104,7 @@ Making use of just one shell script and one configuration file it is
possible to build reduced and customized images satisfying any arbitrary possible to build reduced and customized images satisfying any arbitrary
set of requirements. set of requirements.
.El .El
.Ss Nm NanoBSD Ss Media Layout .Ss NanoBSD Media Layout
The mass storage medium is divided into three parts by default (which The mass storage medium is divided into three parts by default (which
are normally mounted read-only): are normally mounted read-only):
.Pp .Pp

4
share/man/man8/uefi.8
View File

@ -114,7 +114,7 @@ typical non-default kernel (optional)
.Xr vt 4 , .Xr vt 4 ,
.Xr msdosfs 5 , .Xr msdosfs 5 ,
.Xr boot 8 , .Xr boot 8 ,
.Xr gpart 8 , .Xr gpart 8 ,
.Xr uefisign 8 .Xr uefisign 8
.Sh HISTORY .Sh HISTORY
.Nm .Nm
@ -125,7 +125,7 @@ boot support first appeared in
.Nm .Nm
boot support was developed by boot support was developed by
.An Benno Rice Aq Mt benno@FreeBSD.org , .An Benno Rice Aq Mt benno@FreeBSD.org ,
.An Ed Maste Aq Mt emaste@FreeBSD.org , .An \&Ed Maste Aq Mt emaste@FreeBSD.org ,
and and
.An Nathan Whitehorn Aq Mt nwhitehorn@FreeBSD.org . .An Nathan Whitehorn Aq Mt nwhitehorn@FreeBSD.org .
The The

11
share/man/man8/yp.8
View File

@ -464,9 +464,11 @@ Some systems, such as
.Tn NIS .Tn NIS
to be running in order to be running in order
for their hostname resolution functions for their hostname resolution functions
.Fn ( gethostbyname , .Po Fn gethostbyname ,
.Fn gethostbyaddr , .Fn gethostbyaddr ,
etc.) to work properly. etc.
.Pc
to work properly.
On these systems, On these systems,
.Xr ypserv 8 .Xr ypserv 8
performs performs
@ -499,13 +501,14 @@ It can also be made to register itself as an
v1 server v1 server
in order to placate certain systems that insist on the presence of in order to placate certain systems that insist on the presence of
a v1 server a v1 server
.No ( Fx .Po Fx
uses only uses only
.Tn NIS .Tn NIS
v2, but many other systems, v2, but many other systems,
including including
.Tn SunOS .Tn SunOS
4.x, search for both a v1 and v2 server when binding). 4.x, search for both a v1 and v2 server when binding
.Pc .
.Fx Ns 's .Fx Ns 's
.Xr ypserv 8 .Xr ypserv 8
does not actually handle does not actually handle

2
share/man/man9/PCI_IOV_ADD_VF.9
View File

@ -104,8 +104,8 @@ the PF.
.Sh SEE ALSO .Sh SEE ALSO
.Xr nv 9 , .Xr nv 9 ,
.Xr pci 9 , .Xr pci 9 ,
.Xr pci_iov_schema 9 ,
.Xr PCI_IOV_INIT 9 , .Xr PCI_IOV_INIT 9 ,
.Xr pci_iov_schema 9 ,
.Xr PCI_IOV_UNINIT 9 .Xr PCI_IOV_UNINIT 9
.Sh AUTHORS .Sh AUTHORS
This manual page was written by This manual page was written by

2
share/man/man9/PCI_IOV_INIT.9
View File

@ -77,8 +77,8 @@ and no VFs will be created.
.Sh SEE ALSO .Sh SEE ALSO
.Xr nv 9 , .Xr nv 9 ,
.Xr pci 9 , .Xr pci 9 ,
.Xr pci_iov_schema 9 ,
.Xr PCI_IOV_ADD_VF 9 , .Xr PCI_IOV_ADD_VF 9 ,
.Xr pci_iov_schema 9 ,
.Xr PCI_IOV_UNINIT 9 .Xr PCI_IOV_UNINIT 9
.Sh AUTHORS .Sh AUTHORS
This manual page was written by This manual page was written by

2
share/man/man9/altq.9
View File

@ -237,7 +237,7 @@ sets a flag to indicate that a driver was converted to use the new macros.
.Nm .Nm
can be enabled only on interfaces with this flag. can be enabled only on interfaces with this flag.
.Sh COMPATIBILITY .Sh COMPATIBILITY
.Ss Vt ifaltq Ss structure .Ss Vt ifaltq structure
In order to keep compatibility with the existing code, the new In order to keep compatibility with the existing code, the new
output queue structure output queue structure
.Vt ifaltq .Vt ifaltq

8
share/man/man9/ifnet.9
View File

@ -215,7 +215,7 @@ Interfaces are also associated with an output queue, defined as a
this structure is used to hold packets while the interface is in the this structure is used to hold packets while the interface is in the
process of sending another. process of sending another.
.Pp .Pp
.Ss The Vt ifnet Ss structure .Ss The ifnet Structure
The fields of The fields of
.Vt "struct ifnet" .Vt "struct ifnet"
are as follows: are as follows:
@ -840,7 +840,7 @@ routine.
The The
.Xr polling .Xr polling
handler returns the number of packets processed. handler returns the number of packets processed.
.Ss The Vt if_data Ss Structure .Ss The if_data Structure
The The
.Vt if_data .Vt if_data
structure contains statistics and identifying information used structure contains statistics and identifying information used
@ -1021,7 +1021,7 @@ The link is down.
.It Dv LINK_STATE_UP .It Dv LINK_STATE_UP
The link is up. The link is up.
.El .El
.Ss The Vt ifaddr Ss Structure .Ss The ifaddr Structure
Every interface is associated with a list Every interface is associated with a list
(or, rather, a (or, rather, a
.Li TAILQ ) .Li TAILQ )
@ -1119,7 +1119,7 @@ In addition to these functions, there
may also be link-layer support routines which are used by a number of may also be link-layer support routines which are used by a number of
drivers implementing a specific link layer over different hardware; drivers implementing a specific link layer over different hardware;
see the documentation for that link layer for more details. see the documentation for that link layer for more details.
.Ss The Vt ifmultiaddr Ss Structure .Ss The ifmultiaddr Structure
Every multicast-capable interface is associated with a list of Every multicast-capable interface is associated with a list of
multicast group memberships, which indicate at a low level which multicast group memberships, which indicate at a low level which
link-layer multicast addresses (if any) should be accepted, and at a link-layer multicast addresses (if any) should be accepted, and at a