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

Scheduled mdoc(7) sweep.

Browse Source
This commit is contained in:
Ruslan Ermilov 2005-01-11 11:47:22 +00:00
parent 14bcbf608e
commit 1a74e6a157
11 changed files with 61 additions and 67 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
usr.sbin/bluetooth/l2ping/l2ping.8
View File

@ -44,7 +44,7 @@ The
.Nm
utility uses L2CAP
.Dv ECHO_REQUEST
datagram to elicit a L2CAP
datagram to elicit an L2CAP
.Dv ECHO_RESPONSE
datagram from a remote device.
.Pp
@ -77,7 +77,7 @@ This option is ignored if
has been specified.
.It Fl n
Numeric output only.
No attempt will be made to lookup symbolic names for host addresses.
No attempt will be made to look up symbolic names for host addresses.
.It Fl S Ar source
Specify the local device which should be used to send L2CAP
.Dv ECHO_REQUEST
@ -92,7 +92,8 @@ Specify the number of payload bytes to be sent.
The default size is 44 bytes.
It is calculated as minimum L2CAP MTU (48 bytes) minus the size of the L2CAP
signalling command header (4 bytes).
The maximum size is 65531 bytes. Is is calculated as maximum L2CAP MTU
The maximum size is 65531 bytes.
Is is calculated as maximum L2CAP MTU
(65535 bytes) minus four bytes of payload reserved for
.Nm
internal use.

14
usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8
View File

@ -132,16 +132,16 @@ In both client and server modes, this required option specifies which
.Xr ppp 8
label will be used.
.It Fl S
In the server mode register the Serial Port (SP) service in addition to the
In the server mode, register the Serial Port (SP) service in addition to the
LAN Access Using PPP (LAN) service.
It appears that some cell phones are using so called
.Dq callback mechanism .
In this scenario the user is trying to connect his cell phone to the Internet,
and, user's host computer is acting as the gateway server.
It appears that some cell phones are using the so-called
.Dq "callback mechanism" .
In this scenario, the user is trying to connect his cell phone to the Internet,
and user's host computer is acting as the gateway server.
It seems that it is not possible to tell the phone to just connect and start
using the LAN service.
Instead the user's host computer must
.Dq jump start
Instead, the user's host computer must
.Dq "jump start"
the phone by connecting to the phone's SP service.
What happens next is the phone kills the existing connection and opens another
connection back to the user's host computer.

2
usr.sbin/eeprom/eeprom.8
View File

@ -257,7 +257,7 @@ If set to
all Ethernet devices with FCode will use the system default MAC address.
If set to
.Dq Li true ,
Ethernet devices with FCode that contains an unique MAC address will use it
Ethernet devices with FCode that contains a unique MAC address will use it
rather than the system's default MAC address.
Default:
.Dq Li false .

3
usr.sbin/fwcontrol/fwcontrol.8
View File

@ -104,7 +104,8 @@ Ports Collection.
.It Fl S Ar filename
Send a DV file as isochronous stream.
.It Fl m Ar EUI64 | hostname
Set default fwmem target. Hostname will be converted to EUI64 using
Set default fwmem target.
Hostname will be converted to EUI64 using
.Xr eui64 5 .
.El
.Sh EXAMPLES

8
usr.sbin/jail/jail.8
View File

@ -42,7 +42,7 @@
.Sh SYNOPSIS
.Nm
.Op Fl i
.Op Fl l Fl u Ar username | Fl U Ar username
.Op Fl l u Ar username | Fl U Ar username
.Ar path hostname ip-number command ...
.Sh DESCRIPTION
The
@ -56,9 +56,7 @@ Output the jail identifier of the newly created jail.
.It Fl l
Run program in the clean environment.
The environment is discarded except for
.Ev HOME ,
.Ev SHELL ,
.Ev TERM
.Ev HOME , SHELL , TERM
and
.Ev USER .
.Ev HOME
@ -68,7 +66,7 @@ are set to the target login's default values.
.Ev USER
is set to the target login.
.Ev TERM
is imported from your current environment.
is imported from the current environment.
The environment variables from the login class capability database for the
target login are also set.
.It Fl u Ar username

2
usr.sbin/lptcontrol/lptcontrol.8
View File

@ -69,7 +69,7 @@ printer control devices
.It Pa /sys/i386/conf/GENERIC
kernel configuration file
.It Pa /boot/device.hints
Device hints for the parallel port chipset driver,
device hints for the parallel port chipset driver,
.Xr ppc 4
.El
.Sh BUGS

2
usr.sbin/moused/moused.8
View File

@ -228,7 +228,7 @@ Specifies at which level
.Nm
should operate the mouse driver.
Refer to
.Em Operation Levels
.Sx Operation Levels
in
.Xr psm 4
for more information on this.

71
usr.sbin/ndiscvt/ndiscvt.8
View File

@ -153,52 +153,51 @@ Generate both an
file and
an
.Pa ndis_driver.data.o
file. The latter file will contain a copy of the
file.
The latter file will contain a copy of the
.Tn Windows\[rg]
.Pa .SYS
driver image encoded as a
.Fx
ELF object file
.Po
created with
.Xr objcopy 1
.Pc .
(created with
.Xr objcopy 1 ) .
Turning the
.Tn Windows\[rg]
driver image directly into an object code file saves disk space
and compilation time.
.It Fl f Ar firmfile
A few NDIS drivers come with additional files that the core
driver module will load during initialization time. Typically,
driver module will load during initialization time.
Typically,
these files contain firmware which the driver will transfer to
the device in order to make it fully operational. In
the device in order to make it fully operational.
In
.Tn Windows\[rg] ,
these files are usually just copied into one of the system
directories along with the driver itself.
.Pp
In
.Fx
there are two mechanism for loading these files. If the driver
there are two mechanism for loading these files.
If the driver
is built as a loadable kernel module which is loaded after the
kernel has finished booting
.Po
and after the root filesystem has
been mounted
.Pc ,
(and after the root file system has
been mounted),
the extra files can simply be copied to the
.Pa /compat/ndis
directory, and they will be loaded into the kernel on demand when the
the driver needs them.
.Pp
If however the driver is required to bootstrap the system
.Po
i.e. if
(i.e., if
the NDIS-based network interface is to be used for diskless/PXE
booting
.Pc ,
booting),
the files need to be pre-loaded by the bootstrap
loader in order to be accessible, since the driver will need them
before the root filesystem has been mounted. However, the bootstrap
before the root file system has been mounted.
However, the bootstrap
loader is only able to load files that are shared
.Fx
binary objects.
@ -208,20 +207,19 @@ The
flag can be used to convert an arbitrary file
.Ar firmfile
into shared object format
.Po
the actual conversion is done using
(the actual conversion is done using
the
.Xr objcopy 1
and
.Xr ld 1
commands
.Pc .
commands).
The resulting files can then be copied to the
.Pa /boot/kernel
directory, and can be pre-loaded directly from the boot loader
prompt, or automatically by editing the
.Xr loader.conf 5
file. If desired, the files can also be loaded into memory
file.
If desired, the files can also be loaded into memory
at runtime using the
.Xr kldload 8
command.
@ -232,7 +230,8 @@ code will first search for a loaded kernel module that matches the
name specified in the open request, and if that fails, it will then
try to open the file from the
.Pa /compat/ndis
directory as well. Note that during kernel bootstrap, the ability
directory as well.
Note that during kernel bootstrap, the ability
to open files from
.Pa /compat/ndis
is disabled: only the module search will be performed.
@ -242,32 +241,30 @@ When using the
flag,
.Nm
will generate both a relocatable object file
.Po
with a
(with a
.Pa .o
extension
.Pc
extension)
and a shared object file
.Po
with a
(with a
.Pa .ko
extension
.Pc
. The shared object is the one that should be placed in
extension).
The shared object is the one that should be placed in
the
.Pa /boot/kernel
directory. The relocatable object file is useful if the user wishes
directory.
The relocatable object file is useful if the user wishes
to create a completely static kernel image: the object file can be
linked into the kernel directly along with the driver itself. Some
linked into the kernel directly along with the driver itself.
Some
editing of the kernel configuration files will be necessary in order
to have the extra object included in the build.
.El
.Sh SEE ALSO
.Xr kldload 8 ,
.Xr ld 1 ,
.Xr objcopy 1 ,
.Xr ndis 4 ,
.Xr ndisapi 9 ,
.Xr objcopy 1
.Xr kldload 8 ,
.Xr ndisapi 9
.Sh HISTORY
The
.Nm

12
usr.sbin/pkg_install/version/pkg_version.1
View File

@ -23,7 +23,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $FreeBSD$
.\" $FreeBSD$
.Dd June 29, 2004
.Dt PKG_VERSION 1
.Os
@ -41,9 +41,9 @@
.Oc
.Op Ar index
.Nm
.Op Fl t Ar version1 version2
.Fl t Ar version1 version2
.Nm
.Op Fl T Ar pkgname pattern
.Fl T Ar pkgname pattern
.Sh DESCRIPTION
The
.Nm
@ -139,14 +139,14 @@ to the shell, it is best to quote
with single quotes.
.It Fl q
Enable quiet output.
Quiet output precludes printing the the
Quiet output precludes printing the
.Ar limchar
when used with
.Fl l
or
.Fl L .
This is useful when used as the input to
.Xr portupdate 8 .
.Xr portupgrade 8 .
.It Fl s
Limit the output to those packages whose names match a given
.Ar string .
@ -205,7 +205,7 @@ option has been deprecated and is no longer supported.
.Xr pkg_create 1 ,
.Xr pkg_delete 1 ,
.Xr pkg_info 1 ,
.Xr portupdate 8
.Xr portupgrade 8
.Sh FILES
.Bl -tag -width /usr/ports/INDEX-6 -compact
.It Pa /usr/ports/INDEX-6

2
usr.sbin/ppp/ppp.8.m4
View File

@ -828,7 +828,7 @@ If you want to include a literal
.Dq $
or
.Dq ~
character in a command or argument, enclose them in double quotes, e.g.
character in a command or argument, enclose them in double quotes, e.g.,
.Bd -literal -offset indent
set password "pa$ss~word"
.Ed

5
usr.sbin/syslogd/syslogd.8
View File

@ -40,10 +40,7 @@
.Op Fl a Ar allowed_peer
.Op Fl b Ar bind_address
.Op Fl f Ar config_file
.Oo
.Fl l Op Ar mode: Ns
.Ar path
.Oc
.Op Fl l Oo Ar mode : Oc Ns Ar path
.Op Fl m Ar mark_interval
.Op Fl P Ar pid_file
.Op Fl p Ar log_socket