Fix a bunch of "xref refers to *this* page" igor(1) warnings.
MFC after: 1 month
This commit is contained in:
parent
21c0e4e1ab
commit
d477060046
@ -64,7 +64,6 @@ The IP cores used in
|
||||
devices were adapted by Broadcom for compatibility with the new
|
||||
interconnect.
|
||||
.Sh SEE ALSO
|
||||
.Xr bcma 4 ,
|
||||
.Xr bhnd 4
|
||||
.Sh HISTORY
|
||||
The
|
||||
|
@ -100,7 +100,7 @@ See
|
||||
for more details.
|
||||
.Pp
|
||||
If you want to use
|
||||
.Xr dcons 4
|
||||
.Nm
|
||||
as a
|
||||
.Xr gdb 1
|
||||
port, add the following line into
|
||||
|
@ -122,7 +122,7 @@ may be used to set the Don't Fragment flag on IP packets.
|
||||
Currently this option is respected only on
|
||||
.Xr udp 4
|
||||
and raw
|
||||
.Xr ip 4
|
||||
.Nm
|
||||
sockets, unless the
|
||||
.Dv IP_HDRINCL
|
||||
option has been set.
|
||||
|
@ -230,7 +230,7 @@ node which will check for the specified string and return non-matching
|
||||
packets to
|
||||
.Xr ipfw 8 .
|
||||
Matching packets are passed to
|
||||
.Xr ng_tag 4
|
||||
.Nm
|
||||
node, which will set a tag and pass them back to
|
||||
.Xr ng_bpf 4
|
||||
node on a hook programmed to accept all packets and pass them back to
|
||||
@ -246,7 +246,7 @@ expressions must be altered accordingly.
|
||||
Thus, there will be expression
|
||||
.Dq Li "ether[40:2]=0x244c && ether[42:4]=0x6f636b20"
|
||||
on incoming hook and empty expression to match all packets from
|
||||
.Xr ng_tag 4 .
|
||||
.Nm .
|
||||
.Pp
|
||||
So, this is
|
||||
.Xr ngctl 8
|
||||
|
@ -98,7 +98,7 @@ It is probably more useful to issue this ioctl through the
|
||||
device.
|
||||
.It CAMIOQUEUE union ccb *
|
||||
Queue a CCB to the
|
||||
.Xr pass 4
|
||||
.Nm
|
||||
driver to be executed asynchronously.
|
||||
The caller may use
|
||||
.Xr select 2 ,
|
||||
@ -167,7 +167,7 @@ ioctl.
|
||||
An error will only be returned from the
|
||||
.Dv CAMIOGET
|
||||
ioctl if the
|
||||
.Xr pass 4
|
||||
.Nm
|
||||
driver fails to copy data to the user process or if there are no completed
|
||||
CCBs available to retrieve.
|
||||
If no CCBs are available to retrieve,
|
||||
|
@ -53,5 +53,5 @@ Support for new cards should be added there.
|
||||
.Sh HISTORY
|
||||
This driver took the idea from the
|
||||
.Nx
|
||||
.Xr puc 4
|
||||
.Nm
|
||||
driver.
|
||||
|
@ -48,7 +48,7 @@ it is seeded for the first time.
|
||||
This may cause trouble at system boot
|
||||
when keys and the like
|
||||
are generated from
|
||||
.Xr random 4
|
||||
.Nm
|
||||
so steps should be taken to ensure a
|
||||
seeding as soon as possible.
|
||||
.Pp
|
||||
@ -63,7 +63,7 @@ this could be done by
|
||||
This sysctl will not return
|
||||
random bytes unless
|
||||
the
|
||||
.Xr random 4
|
||||
.Nm
|
||||
device is seeded.
|
||||
.Pp
|
||||
This initial seeding
|
||||
|
@ -62,7 +62,7 @@ If any of these checks fail, then the kernel will panic.
|
||||
The
|
||||
.Dv WITNESS_COUNT
|
||||
kernel option controls the maximum number of
|
||||
.Xr witness 4
|
||||
.Nm
|
||||
entries that are tracked in the kernel.
|
||||
The maximum number of entries can be queried via the
|
||||
.Va debug.witness.count
|
||||
@ -76,7 +76,7 @@ environment variable.
|
||||
The
|
||||
.Dv WITNESS_NO_VNODE
|
||||
kernel option tells
|
||||
.Xr witness 4
|
||||
.Nm
|
||||
to ignore locking issues between
|
||||
.Xr vnode 9
|
||||
objects.
|
||||
|
@ -70,7 +70,7 @@ file attributes associated with the member.
|
||||
An archive header describes the file attributes for the archive member that
|
||||
follows it.
|
||||
The
|
||||
.Xr ar 5
|
||||
.Nm
|
||||
format only supports a limited number of attributes: the file name,
|
||||
the file creation time stamp, the uid and gid of the creator, the file
|
||||
mode and the file size.
|
||||
|
@ -1308,5 +1308,5 @@ This manual page was written by
|
||||
.An Jeroen Ruigrok van der Werven Aq Mt asmodai@FreeBSD.org
|
||||
with inspiration from BSDi's
|
||||
.Bsx
|
||||
.Xr elf 5
|
||||
.Nm
|
||||
manpage.
|
||||
|
@ -223,7 +223,7 @@ and continue on anything else (i.e,
|
||||
You can enable caching for the particular database by specifying
|
||||
.Dq cache
|
||||
as the first source in the
|
||||
.Xr nsswitch.conf 5
|
||||
.Nm
|
||||
file.
|
||||
You should also enable caching for this database in
|
||||
.Xr nscd.conf 5 .
|
||||
|
@ -1207,12 +1207,12 @@ Note that the maximum number of the generated addresses from a range
|
||||
specification is limited to an integer value specified in
|
||||
.Va netif_ipexpand_max
|
||||
in
|
||||
.Xr rc.conf 5
|
||||
.Nm
|
||||
because a small typo can unexpectedly generate a large number of addresses.
|
||||
The default value is
|
||||
.Li 2048 .
|
||||
It can be increased by adding the following line into
|
||||
.Xr rc.conf 5 :
|
||||
.Nm :
|
||||
.Bd -literal
|
||||
netif_ipexpand_max="4096"
|
||||
.Ed
|
||||
@ -3900,7 +3900,7 @@ all configured jails in
|
||||
are stopped in reverse order.
|
||||
.It Va jail_* variables
|
||||
Note that older releases supported per-jail configuration via
|
||||
.Xr rc.conf 5
|
||||
.Nm
|
||||
variables.
|
||||
For example,
|
||||
hostname of a jail named
|
||||
|
@ -44,7 +44,7 @@ The
|
||||
method is called on each bus device to rescan the device tree when the pass
|
||||
level has been changed.
|
||||
This method is responsible for invoking
|
||||
.Xr BUS_NEW_PASS 9
|
||||
.Nm
|
||||
on child bus devices to propagate the rescan to child devices.
|
||||
It is also responsible for reprobing any unattached child devices and
|
||||
allowing drivers for the current pass to identify new children.
|
||||
|
@ -87,7 +87,6 @@ and it must be updated by the implementation after each relevant
|
||||
.Nm
|
||||
operation.
|
||||
.Sh SEE ALSO
|
||||
.Xr pmap 9 ,
|
||||
.Xr pmap_activate 9 ,
|
||||
.Xr pmap_clear_modify 9 ,
|
||||
.Xr pmap_copy 9 ,
|
||||
|
@ -171,10 +171,10 @@ is returned if the operation is not implemented.
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
The
|
||||
.Xr stack 9
|
||||
.Nm
|
||||
function suite was created by
|
||||
.An Antoine Brodin .
|
||||
.Xr stack 9
|
||||
.Nm
|
||||
was extended by
|
||||
.An Robert Watson
|
||||
for general-purpose use outside of
|
||||
|
Loading…
Reference in New Issue
Block a user