Expand *n't contractions.
This commit is contained in:
parent
13e88b41ba
commit
1541af42f1
@ -210,7 +210,7 @@ the clock goes back at 02:00 to 01:00, using
|
||||
.Fl v No +3H
|
||||
will be necessary to reach October 29, 2:30.
|
||||
.Pp
|
||||
When the date is adjusted to a specific value that doesn't actually exist
|
||||
When the date is adjusted to a specific value that does not actually exist
|
||||
(for example March 26, 1:30 BST 2000 in the Europe/London timezone),
|
||||
the date will be silently adjusted forwards in units of one hour until it
|
||||
reaches a valid time.
|
||||
|
@ -69,7 +69,7 @@ the link.
|
||||
Symbolic links may reference other symbolic links,
|
||||
in which case the links are dereferenced until an object that is
|
||||
not a symbolic link is found,
|
||||
a symbolic link which references a file which doesn't exist is found,
|
||||
a symbolic link which references a file which does not exist is found,
|
||||
or a loop is detected.
|
||||
(Loop detection is done by placing an upper limit on the number of
|
||||
links that may be followed, and an error results if this limit is
|
||||
|
@ -475,12 +475,12 @@ variable must be set to
|
||||
.Dq Li xterm-color .
|
||||
Other terminal types may require similar adjustments.
|
||||
Colorization
|
||||
is silently disabled if the output isn't directed to a terminal
|
||||
is silently disabled if the output is not directed to a terminal
|
||||
unless the
|
||||
.Ev CLICOLOR_FORCE
|
||||
variable is defined.
|
||||
.It Ev CLICOLOR_FORCE
|
||||
Color sequences are normally disabled if the output isn't directed to
|
||||
Color sequences are normally disabled if the output is not directed to
|
||||
a terminal.
|
||||
This can be overridden by setting this flag.
|
||||
The
|
||||
|
@ -120,7 +120,7 @@ Write old-style
|
||||
.Pq non- Ns Tn POSIX
|
||||
archives.
|
||||
.It Fl o
|
||||
Don't write directory information that the older (V7) style
|
||||
Do not write directory information that the older (V7) style
|
||||
.Nm
|
||||
is unable to decode.
|
||||
This implies the
|
||||
|
@ -129,7 +129,7 @@ described here
|
||||
has been reimplemented with Kerberos in
|
||||
.Bx 4.3 Reno .
|
||||
.Sh BUGS
|
||||
Doesn't detect all cases where the target of a copy might
|
||||
Does not detect all cases where the target of a copy might
|
||||
be a file in cases where only a directory should be legal.
|
||||
.Pp
|
||||
Is confused by any output generated by commands in a
|
||||
|
@ -96,7 +96,7 @@ Pretend the local hostname is
|
||||
.Ar name .
|
||||
This is useful after the local hostname has been changed and rmtab entries
|
||||
using the old name remain on a remote machine.
|
||||
Unfortunately, most mountd's won't be able to successfully handle removal
|
||||
Unfortunately, most mountd's will not be able to successfully handle removal
|
||||
of such entries, so this option is useful in combination with
|
||||
.Fl v
|
||||
only.
|
||||
|
@ -86,7 +86,7 @@ which defaults to
|
||||
Lookups within that directory are handled by
|
||||
.Nm hlfsd ,
|
||||
which uses the password map to determine how to resolve the lookup. The
|
||||
directory will be created if it doesn't already exist. The symbolic link will
|
||||
directory will be created if it does not already exist. The symbolic link will
|
||||
be to the accessing user's home directory, with
|
||||
.Ar subdir
|
||||
appended to it. If not specified,
|
||||
@ -113,7 +113,7 @@ the symbolic link returned by
|
||||
will point, if it cannot access the home directory of the user. This
|
||||
defaults to
|
||||
.Pa /var/hlfs .
|
||||
This directory will be created if it doesn't exist. It is expected
|
||||
This directory will be created if it does not exist. It is expected
|
||||
that either users will read these files, or the system administrators
|
||||
will run a script to resend this
|
||||
.Dq lost mail
|
||||
|
@ -71,7 +71,7 @@ Only available if compiled with -DDEBUG.
|
||||
Consider all fortune files to be of equal size (see discussion below
|
||||
on multiple files).
|
||||
.It Fl f
|
||||
Print out the list of files which would be searched, but don't
|
||||
Print out the list of files which would be searched, but do not
|
||||
print a fortune.
|
||||
.It Fl l
|
||||
Long dictums only.
|
||||
|
@ -99,7 +99,7 @@ bit in the header
|
||||
.Ar str_flags
|
||||
field to be set.
|
||||
.It Fl s
|
||||
Run silently; don't give a summary message when finished.
|
||||
Run silently; do not give a summary message when finished.
|
||||
.It Fl x
|
||||
Note that each alphabetic character in the groups of lines is rotated
|
||||
13 positions in a simple caesar cypher.
|
||||
|
@ -59,4 +59,4 @@ Display the number on a single line.
|
||||
.Sh BUGS
|
||||
Although
|
||||
.Nm
|
||||
understand fractions, it doesn't understand exponents.
|
||||
understand fractions, it does not understand exponents.
|
||||
|
@ -686,7 +686,7 @@ function gets the current value of the helpful text line.
|
||||
.Pp
|
||||
The
|
||||
.Fn dialog_clear_norefresh
|
||||
function clears the screen back to the dialog background color, but don't
|
||||
function clears the screen back to the dialog background color, but do not
|
||||
refresh the contents just yet.
|
||||
.Pp
|
||||
The
|
||||
|
@ -93,7 +93,7 @@ that match
|
||||
.Ar name ,
|
||||
not just the first.
|
||||
.It Fl d
|
||||
Don't actually display the man pages, but do print gobs of debugging
|
||||
Do not actually display the man pages, but do print gobs of debugging
|
||||
information.
|
||||
.It Fl f
|
||||
Equivalent to
|
||||
@ -191,7 +191,7 @@ The output from
|
||||
may need to be passed through some filter or another before being
|
||||
printed.
|
||||
.It Fl w
|
||||
Don't actually display the man pages, but do print the location(s) of
|
||||
Do not actually display the man pages, but do print the location(s) of
|
||||
the files that would be formatted or displayed.
|
||||
.El
|
||||
.Sh ENVIRONMENT
|
||||
|
@ -51,7 +51,7 @@ If it exists, it is added to the search path.
|
||||
.Nm Manpath
|
||||
is used by
|
||||
.Xr man 1
|
||||
to determine the search path, so users normally don't need to set the
|
||||
to determine the search path, so users normally do not need to set the
|
||||
.Ev MANPATH
|
||||
environment variable directly.
|
||||
.Pp
|
||||
|
@ -205,12 +205,12 @@ Create/list/extract old GNU-format incremental backup.
|
||||
Create/list/extract new GNU-format incremental backup.
|
||||
.It Fl h
|
||||
.It Fl -dereference
|
||||
Don't write symlinks as symlinks; write the data of the files they name.
|
||||
Do not write symlinks as symlinks; write the data of the files they name.
|
||||
.It Fl i
|
||||
.It Fl -ignore-zeros
|
||||
Ignore blocks of zeroes in archive (usually means End-Of-File).
|
||||
.It Fl -ignore-failed-read
|
||||
Don't exit with non-zero status on unreadable files.
|
||||
Do not exit with non-zero status on unreadable files.
|
||||
.It Fl j
|
||||
.It Fl y
|
||||
.It Fl -bzip
|
||||
@ -220,7 +220,7 @@ Filter the archive through
|
||||
.Xr bzip2 1 .
|
||||
.It Fl k
|
||||
.It Fl -keep-old-files
|
||||
Keep files which already exist on disk; don't overwrite them from the archive.
|
||||
Keep files which already exist on disk; do not overwrite them from the archive.
|
||||
.It Fl K Ar file
|
||||
.It Fl -starting-file Ar file
|
||||
Begin at
|
||||
@ -237,13 +237,13 @@ Change tapes after writing
|
||||
* 1024 bytes.
|
||||
.It Fl m
|
||||
.It Fl -modification-time
|
||||
Don't extract file modified time.
|
||||
Do not extract file modified time.
|
||||
.It Fl M
|
||||
.It Fl -multi-volume
|
||||
Create/list/extract multi-volume archive.
|
||||
.It Fl n
|
||||
.It Fl -norecurse
|
||||
Don't recurse into subdirectories when creating.
|
||||
Do not recurse into subdirectories when creating.
|
||||
.It Fl -volno-file Ar file
|
||||
File name with volume number to start with.
|
||||
.It Fl N Ar date
|
||||
@ -270,7 +270,7 @@ Has the effect of
|
||||
.Fl p s .
|
||||
.It Fl P
|
||||
.It Fl -absolute-paths
|
||||
Don't strip leading
|
||||
Do not strip leading
|
||||
.Ql /
|
||||
from file names.
|
||||
.It Fl R
|
||||
@ -333,7 +333,7 @@ Attempt to verify the archive after writing it.
|
||||
.It Fl -exclude Ar pattern
|
||||
Exclude files matching the
|
||||
.Ar pattern
|
||||
(don't extract them, don't add them, don't list them).
|
||||
(do not extract them, do not add them, do not list them).
|
||||
.It Fl X Ar file
|
||||
.It Fl -exclude-from Ar file
|
||||
Exclude files listed in
|
||||
@ -468,7 +468,7 @@ which will add the files contained in
|
||||
.Pa archive2.tar
|
||||
onto the end of
|
||||
.Pa archive1.tar
|
||||
(note that this can't be done by simply typing
|
||||
(note that this cannot be done by simply typing
|
||||
.Dl "cat archive2.tar >> archive1.tar"
|
||||
because of the end-of-file block at the end of a
|
||||
.Nm
|
||||
|
@ -272,7 +272,7 @@ Complete the archive and invoke the close callback.
|
||||
.It Fn archive_read_finish
|
||||
Invokes
|
||||
.Fn archive_read_close
|
||||
if it wasn't invoked maually, then release all resources.
|
||||
if it was not invoked maually, then release all resources.
|
||||
.El
|
||||
.Pp
|
||||
Note that the library determines most of the relevant information about
|
||||
|
@ -196,7 +196,7 @@ Complete the archive and invoke the close callback.
|
||||
.It Fn archive_write_finish
|
||||
Invokes
|
||||
.Fn archive_write_close
|
||||
if it wasn't invoked manually, then release all resources.
|
||||
if it was not invoked manually, then release all resources.
|
||||
.El
|
||||
More information about the
|
||||
.Va struct archive
|
||||
|
@ -98,7 +98,7 @@ is not possible.)
|
||||
.\".Bl -tag -width indent
|
||||
.\".It Dv DB_LOCK
|
||||
.\"Do the necessary locking in the database to support concurrent access.
|
||||
.\"If concurrent access isn't needed or the database is read-only this
|
||||
.\"If concurrent access is not needed or the database is read-only this
|
||||
.\"flag should not be set, as it tends to have an associated performance
|
||||
.\"penalty.
|
||||
.\".It Dv DB_SHMEM
|
||||
@ -541,7 +541,7 @@ The typedef
|
||||
is a mnemonic for
|
||||
.Dq "data base thang" ,
|
||||
and was used
|
||||
because noone could think of a reasonable name that wasn't already used.
|
||||
because noone could think of a reasonable name that was not already used.
|
||||
.Pp
|
||||
The file descriptor interface is a kluge and will be deleted in a
|
||||
future version of the interface.
|
||||
|
@ -196,7 +196,7 @@ function may fail and set
|
||||
for the following:
|
||||
.Bl -tag -width Er
|
||||
.It Bq Er EINVAL
|
||||
The requested record doesn't exist.
|
||||
The requested record does not exist.
|
||||
.El
|
||||
.Pp
|
||||
The
|
||||
|
@ -159,7 +159,7 @@ and
|
||||
search path is the path specified in the environment by
|
||||
.Dq Ev PATH
|
||||
variable.
|
||||
If this variable isn't specified,
|
||||
If this variable is not specified,
|
||||
the default path is set according to the
|
||||
.Dv _PATH_DEFPATH
|
||||
definition in
|
||||
@ -196,7 +196,7 @@ or
|
||||
according to whether at least one file with suitable execute permissions
|
||||
was found.
|
||||
.Pp
|
||||
If the header of a file isn't recognized (the attempted
|
||||
If the header of a file is not recognized (the attempted
|
||||
.Fn execve
|
||||
returned
|
||||
.Er ENOEXEC ) ,
|
||||
|
@ -110,8 +110,8 @@ On success 0 is returned, 1 if the returned
|
||||
record contains an unresolved
|
||||
.Ic tc
|
||||
expansion,
|
||||
\-1 if the requested record couldn't be found,
|
||||
\-2 if a system error was encountered (couldn't open/read a file, etc.) also
|
||||
\-1 if the requested record could not be found,
|
||||
\-2 if a system error was encountered (could not open/read a file, etc.) also
|
||||
setting
|
||||
.Va errno ,
|
||||
and \-3 if a potential reference loop is detected (see
|
||||
@ -178,7 +178,7 @@ in
|
||||
.Fa buf
|
||||
is returned on success,
|
||||
.Dv NULL
|
||||
if the requested capability couldn't be
|
||||
if the requested capability could not be
|
||||
found.
|
||||
The end of the capability value is signaled by a `:' or
|
||||
.Tn ASCII
|
||||
@ -195,7 +195,7 @@ The numeric value is returned in the
|
||||
.Ft long
|
||||
pointed to by
|
||||
.Fa num .
|
||||
0 is returned on success, \-1 if the requested numeric capability couldn't
|
||||
0 is returned on success, \-1 if the requested numeric capability could not
|
||||
be found.
|
||||
.Pp
|
||||
The
|
||||
@ -214,7 +214,7 @@ pointed to by
|
||||
.Fa str .
|
||||
The number of characters in the decoded string not including the trailing
|
||||
.Dv NUL
|
||||
is returned on success, \-1 if the requested string capability couldn't
|
||||
is returned on success, \-1 if the requested string capability could not
|
||||
be found, \-2 if a system error was encountered (storage allocation
|
||||
failure).
|
||||
.Pp
|
||||
@ -257,7 +257,7 @@ expansion is done (see
|
||||
.Ic tc=
|
||||
comments below).
|
||||
Upon completion of the database 0 is returned, 1 is returned upon successful
|
||||
return of record with possibly more remaining (we haven't reached the end of
|
||||
return of record with possibly more remaining (we have not reached the end of
|
||||
the database yet), 2 is returned if the record contains an unresolved
|
||||
.Ic tc
|
||||
expansion, \-1 is returned if a system error occurred, and \-2
|
||||
@ -559,7 +559,7 @@ No memory to allocate.
|
||||
.Xr cap_mkdb 1 ,
|
||||
.Xr malloc 3
|
||||
.Sh BUGS
|
||||
Colons (`:') can't be used in names, types, or values.
|
||||
Colons (`:') cannot be used in names, types, or values.
|
||||
.Pp
|
||||
There are no checks for
|
||||
.Ic tc Ns = Ns Ic name
|
||||
|
@ -147,7 +147,7 @@ is non-zero, file descriptors are left open, significantly speeding
|
||||
functions subsequent calls.
|
||||
This functionality is unnecessary for
|
||||
.Fn getgrent
|
||||
as it doesn't close its file descriptors by default.
|
||||
as it does not close its file descriptors by default.
|
||||
It should also
|
||||
be noted that it is dangerous for long-running programs to use this
|
||||
functionality as the group file may be updated.
|
||||
|
@ -151,7 +151,7 @@ is non-zero, file descriptors are left open, significantly speeding
|
||||
up subsequent accesses for all of the routines.
|
||||
(This latter functionality is unnecessary for
|
||||
.Fn getpwent
|
||||
as it doesn't close its file descriptors by default.)
|
||||
as it does not close its file descriptors by default.)
|
||||
.Pp
|
||||
It is dangerous for long-running programs to keep the file descriptors
|
||||
open as the database will become out of date if it is updated while the
|
||||
|
@ -94,7 +94,7 @@ as held in a character string) to network format (usually a
|
||||
.Ft struct in_addr
|
||||
or some other internal binary representation, in network byte order).
|
||||
It returns 1 if the address was valid for the specified address family, or
|
||||
0 if the address wasn't parseable in the specified address family, or -1
|
||||
0 if the address was not parseable in the specified address family, or -1
|
||||
if some system error occurred (in which case
|
||||
.Va errno
|
||||
will have been set).
|
||||
|
@ -166,7 +166,7 @@ This is useful only in programs that regularly do many queries.
|
||||
.Tn UDP
|
||||
should be the normal mode used.
|
||||
.It Dv RES_IGNTC
|
||||
Unused currently (ignore truncation errors, i.e., don't retry with
|
||||
Unused currently (ignore truncation errors, i.e., do not retry with
|
||||
.Tn TCP ) .
|
||||
.It Dv RES_RECURSE
|
||||
Set the recursion-desired bit in queries.
|
||||
|
@ -436,7 +436,7 @@ places the NUL-terminated message into the buffer pointed to by
|
||||
limiting the length (including the NUL) to at most
|
||||
.Fa errbuf_size
|
||||
bytes.
|
||||
If the whole message won't fit,
|
||||
If the whole message will not fit,
|
||||
as much of it as will fit before the terminating NUL is supplied.
|
||||
In any case,
|
||||
the returned value is the size of buffer needed to hold the whole
|
||||
@ -641,7 +641,7 @@ operand invalid
|
||||
.It Dv REG_EMPTY
|
||||
empty (sub)expression
|
||||
.It Dv REG_ASSERT
|
||||
can't happen - you found a bug
|
||||
cannot happen - you found a bug
|
||||
.It Dv REG_INVARG
|
||||
invalid argument, e.g.\& negative-length string
|
||||
.It Dv REG_ILLSEQ
|
||||
@ -715,7 +715,7 @@ are legal REs because
|
||||
is
|
||||
a special character only in the presence of a previous unmatched
|
||||
.Ql (\& .
|
||||
This can't be fixed until the spec is fixed.
|
||||
This cannot be fixed until the spec is fixed.
|
||||
.Pp
|
||||
The standard's definition of back references is vague.
|
||||
For example, does
|
||||
|
@ -105,7 +105,7 @@ Set the timeout argument to 0 for batching calls.
|
||||
.It Dv CLGET_SVC_ADDR Ta "struct netbuf *" Ta "get servers address"
|
||||
.It Dv CLGET_FD Ta "int *" Ta "get fd from handle"
|
||||
.It Dv CLSET_FD_CLOSE Ta "void" Ta "close fd on destroy"
|
||||
.It Dv CLSET_FD_NCLOSE Ta void Ta "don't close fd on destroy"
|
||||
.It Dv CLSET_FD_NCLOSE Ta void Ta "do not close fd on destroy"
|
||||
.It Dv CLGET_VERS Ta "u_int32_t *" Ta "get RPC program version"
|
||||
.It Dv CLSET_VERS Ta "u_int32_t *" Ta "set RPC program version"
|
||||
.It Dv CLGET_XID Ta "u_int32_t *" Ta "get XID of previous call"
|
||||
|
@ -78,7 +78,7 @@ The
|
||||
function is less well-behaved:
|
||||
for a positive leap second hit the result is not unique,
|
||||
and for a negative leap second hit the corresponding
|
||||
POSIX time_t doesn't exist so an adjacent value is returned.
|
||||
POSIX time_t does not exist so an adjacent value is returned.
|
||||
Both of these are good indicators of the inferiority of the
|
||||
POSIX representation.
|
||||
.Pp
|
||||
|
@ -44,7 +44,7 @@
|
||||
.In sys/file.h
|
||||
.Fd "#define LOCK_SH 0x01 /* shared file lock */"
|
||||
.Fd "#define LOCK_EX 0x02 /* exclusive file lock */"
|
||||
.Fd "#define LOCK_NB 0x04 /* don't block when locking */"
|
||||
.Fd "#define LOCK_NB 0x04 /* do not block when locking */"
|
||||
.Fd "#define LOCK_UN 0x08 /* unlock file */"
|
||||
.Ft int
|
||||
.Fn flock "int fd" "int operation"
|
||||
|
@ -302,7 +302,7 @@ The protocol family has not been configured into the
|
||||
system or no implementation for it exists.
|
||||
.It Er 47 EAFNOSUPPORT Em "Address family not supported by protocol family" .
|
||||
An address incompatible with the requested protocol was used.
|
||||
For example, you shouldn't necessarily expect to be able to use
|
||||
For example, you should not necessarily expect to be able to use
|
||||
.Tn NS
|
||||
addresses with
|
||||
.Tn ARPA
|
||||
@ -426,7 +426,7 @@ on the remote host
|
||||
.It Er 76 EPROCUNAVAIL Em "Bad procedure for program" .
|
||||
An
|
||||
.Tn RPC
|
||||
call was attempted for a procedure which doesn't exist
|
||||
call was attempted for a procedure which does not exist
|
||||
in the remote program.
|
||||
.It Er 77 ENOLCK Em "No locks available" .
|
||||
A system-imposed limit on the number of simultaneous file
|
||||
|
@ -63,7 +63,7 @@ is
|
||||
.Er ENOENT ,
|
||||
which is set when
|
||||
.Va fileid
|
||||
refers to a kld file that does not exist (isn't loaded).
|
||||
refers to a kld file that does not exist (is not loaded).
|
||||
.Sh SEE ALSO
|
||||
.Xr kldfind 2 ,
|
||||
.Xr kldfirstmod 2 ,
|
||||
|
@ -52,7 +52,7 @@ The file referred to by
|
||||
is unloaded unless:
|
||||
.Bl -tag -width Er
|
||||
.It Bq Er EPERM
|
||||
You don't have access to unlink the file from the kernel.
|
||||
You do not have access to unlink the file from the kernel.
|
||||
.It Bq Er ENOENT
|
||||
The file was not found.
|
||||
.It Bq Er EBUSY
|
||||
|
@ -77,7 +77,7 @@ is
|
||||
.Er ENOENT ,
|
||||
which is set when
|
||||
.Va modid
|
||||
refers to a kernel module that does not exist (isn't loaded).
|
||||
refers to a kernel module that does not exist (is not loaded).
|
||||
.Sh SEE ALSO
|
||||
.Xr kldfind 2 ,
|
||||
.Xr kldfirstmod 2 ,
|
||||
|
@ -359,7 +359,7 @@ some process other than the one making the request.
|
||||
A request
|
||||
(other than
|
||||
.Dv PT_ATTACH )
|
||||
specified a process that wasn't stopped.
|
||||
specified a process that was not stopped.
|
||||
.El
|
||||
.It Bq Er EPERM
|
||||
.Bl -bullet -compact
|
||||
@ -367,7 +367,7 @@ specified a process that wasn't stopped.
|
||||
A request
|
||||
(other than
|
||||
.Dv PT_ATTACH )
|
||||
attempted to manipulate a process that wasn't being traced at all.
|
||||
attempted to manipulate a process that was not being traced at all.
|
||||
.It
|
||||
An attempt was made to use
|
||||
.Dv PT_ATTACH
|
||||
|
@ -107,7 +107,7 @@ The
|
||||
system call
|
||||
can be implemented as a call to
|
||||
.Fn rfork "RFFDG | RFPROC"
|
||||
but isn't for backwards compatibility.
|
||||
but is not for backwards compatibility.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion,
|
||||
.Fn rfork
|
||||
|
@ -220,7 +220,7 @@ function appeared in
|
||||
.Sh BUGS
|
||||
Because
|
||||
.Fn sendmsg
|
||||
doesn't necessarily block until the data has been transferred, it
|
||||
does not necessarily block until the data has been transferred, it
|
||||
is possible to transfer an open file descriptor across an
|
||||
.Dv AF_UNIX
|
||||
domain socket
|
||||
|
@ -89,7 +89,7 @@ Be careful, also, to call
|
||||
.Xr _exit 2
|
||||
rather than
|
||||
.Xr exit 3
|
||||
if you can't
|
||||
if you cannot
|
||||
.Xr execve 2 ,
|
||||
since
|
||||
.Xr exit 3
|
||||
|
@ -191,8 +191,8 @@ Once the device name and unit number
|
||||
are determined, a lookup is performed to determine the passthrough device
|
||||
that corresponds to the given device.
|
||||
.Fn cam_open_device
|
||||
is rather simple to use, but it isn't really suitable for general use
|
||||
because its behavior isn't necessarily deterministic.
|
||||
is rather simple to use, but it is not really suitable for general use
|
||||
because its behavior is not necessarily deterministic.
|
||||
Programmers writing
|
||||
new applications should make the extra effort to use one of the other open
|
||||
routines documented below.
|
||||
@ -419,10 +419,10 @@ The CAM library first appeared in
|
||||
.An Kenneth Merry Aq ken@FreeBSD.org
|
||||
.Sh BUGS
|
||||
.Fn cam_open_device
|
||||
doesn't check to see if the
|
||||
does not check to see if the
|
||||
.Fa path
|
||||
passed in is a symlink to something.
|
||||
It also doesn't check to see if the
|
||||
It also does not check to see if the
|
||||
.Fa path
|
||||
passed in is an actual
|
||||
.Xr pass 4
|
||||
|
@ -279,7 +279,7 @@ This flag tells the
|
||||
.Xr pass 4
|
||||
driver to enable error recovery.
|
||||
The default is to not perform error
|
||||
recovery, which means that the retry count won't be honored without this
|
||||
recovery, which means that the retry count will not be honored without this
|
||||
flag, among other things.
|
||||
.It Dv CAM_DATA_PHYS
|
||||
This indicates that the address contained in
|
||||
@ -301,7 +301,7 @@ The
|
||||
.Fa timeout
|
||||
tells the kernel how long to wait for the given command to complete.
|
||||
If
|
||||
the timeout expires and the command hasn't completed, the CCB will be
|
||||
the timeout expires and the command has not completed, the CCB will be
|
||||
returned from the kernel with an appropriate error status.
|
||||
.Pp
|
||||
.Fa cmd_spec
|
||||
@ -559,10 +559,10 @@ CCB.
|
||||
I discovered this while implementing the arbitrary command execution
|
||||
code in
|
||||
.Xr camcontrol 8 ,
|
||||
but I haven't yet had time to implement such a function.
|
||||
but I have not yet had time to implement such a function.
|
||||
.Pp
|
||||
Some of the CCB flag descriptions really don't belong here.
|
||||
Some of the CCB flag descriptions really do not belong here.
|
||||
Rather they
|
||||
belong in a generic CCB man page.
|
||||
Since that man page hasn't yet been
|
||||
Since that man page has not yet been
|
||||
written, the shorter descriptions here will have to suffice.
|
||||
|
@ -324,7 +324,7 @@ returns the name strings associated with the specified
|
||||
.Ql subtype .
|
||||
If
|
||||
.Fn slice_type_name
|
||||
returns "unknown" for slices it isn't familiar with.
|
||||
returns "unknown" for slices it is not familiar with.
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
The
|
||||
|
@ -189,7 +189,7 @@ The return value is
|
||||
-1 if the command is unknown,
|
||||
0 if there was no error or
|
||||
.Dq prog
|
||||
didn't match, or
|
||||
did not match, or
|
||||
1 if the command returned an error.
|
||||
Refer to
|
||||
.Xr editrc 5
|
||||
@ -449,7 +449,7 @@ Insert
|
||||
into the line at the cursor.
|
||||
Returns -1 if
|
||||
.Fa str
|
||||
is empty or won't fit, and 0 otherwise.
|
||||
is empty or will not fit, and 0 otherwise.
|
||||
.It Fn el_deletestr
|
||||
Delete
|
||||
.Fa num
|
||||
|
@ -254,7 +254,7 @@ No sanity checking is done.
|
||||
.Xc
|
||||
Control which tty modes that
|
||||
.Nm
|
||||
won't allow the user to change.
|
||||
will not allow the user to change.
|
||||
.Fl d ,
|
||||
.Fl q
|
||||
or
|
||||
|
@ -381,7 +381,7 @@ To register the authentication callback, simply set
|
||||
.Va fetchAuthMethod
|
||||
to point at it.
|
||||
The callback will be used whenever a site requires authentication and
|
||||
the appropriate environment variables aren't set.
|
||||
the appropriate environment variables are not set.
|
||||
.Pp
|
||||
This interface is experimental and may be subject to change.
|
||||
.Sh RETURN VALUES
|
||||
|
@ -50,7 +50,7 @@ hash-function, that is, you cannot find (except by exhaustive search)
|
||||
the input corresponding to a particular output.
|
||||
This net result is a
|
||||
.Dq fingerprint
|
||||
of the input-data, which doesn't disclose the actual input.
|
||||
of the input-data, which does not disclose the actual input.
|
||||
.Pp
|
||||
MD2 is the slowest, MD4 is the fastest and MD5 is somewhere in the middle.
|
||||
MD2 can only be used for Privacy-Enhanced Mail.
|
||||
@ -196,7 +196,7 @@ Phk ristede runen.
|
||||
.Sh BUGS
|
||||
No method is known to exist which finds two files having the same hash value,
|
||||
nor to find a file with a specific hash value.
|
||||
There is on the other hand no guarantee that such a method doesn't exist.
|
||||
There is on the other hand no guarantee that such a method does not exist.
|
||||
.Pp
|
||||
MD2 has only been licensed for use in Privacy Enhanced Mail.
|
||||
Use MD4 or MD5 if that isn't what you're doing.
|
||||
Use MD4 or MD5 if that is not what you're doing.
|
||||
|
@ -50,7 +50,7 @@ hash function; that is, it is computationally impractical to find
|
||||
the input corresponding to a particular output.
|
||||
This net result is a
|
||||
.Dq fingerprint
|
||||
of the input-data, which doesn't disclose the actual input.
|
||||
of the input-data, which does not disclose the actual input.
|
||||
.Pp
|
||||
The
|
||||
.Fn RIPEMD160_Init ,
|
||||
@ -138,4 +138,4 @@ specification.
|
||||
.Sh BUGS
|
||||
No method is known to exist which finds two files having the same hash value,
|
||||
nor to find a file with a specific hash value.
|
||||
There is on the other hand no guarantee that such a method doesn't exist.
|
||||
There is on the other hand no guarantee that such a method does not exist.
|
||||
|
@ -74,7 +74,7 @@ the input corresponding to a particular output.
|
||||
This net result is
|
||||
a
|
||||
.Dq fingerprint
|
||||
of the input-data, which doesn't disclose the actual input.
|
||||
of the input-data, which does not disclose the actual input.
|
||||
.Pp
|
||||
.Tn SHA
|
||||
(or
|
||||
@ -169,7 +169,7 @@ standards.
|
||||
.Sh BUGS
|
||||
No method is known to exist which finds two files having the same hash value,
|
||||
nor to find a file with a specific hash value.
|
||||
There is on the other hand no guarantee that such a method doesn't exist.
|
||||
There is on the other hand no guarantee that such a method does not exist.
|
||||
.Pp
|
||||
The
|
||||
.Tn IA32
|
||||
|
@ -88,7 +88,7 @@ specifies a NAS identifier to send instead of the hostname.
|
||||
specifies a user whose
|
||||
.Xr passwd 5
|
||||
entry will be used as a template to create the session environment
|
||||
if the supplied username doesn't exist in local password database.
|
||||
if the supplied username does not exist in local password database.
|
||||
The user
|
||||
will be authenticated with the supplied username and password, but his
|
||||
credentials to the system will be presented as the ones for
|
||||
|
@ -55,7 +55,7 @@ must point to a buffer of at least
|
||||
.Ar hsize
|
||||
bytes, and will always be written to by this function.
|
||||
.Pp
|
||||
If the name resolution doesn't work both ways or if the host name is longer
|
||||
If the name resolution does not work both ways or if the host name is longer
|
||||
than
|
||||
.Ar hsize
|
||||
bytes,
|
||||
|
@ -84,7 +84,7 @@ must point to a buffer of at least
|
||||
.Ar hsize
|
||||
bytes, and will always be written to by this function.
|
||||
.Pp
|
||||
If the name resolution doesn't work both ways or if the host name is longer
|
||||
If the name resolution does not work both ways or if the host name is longer
|
||||
than
|
||||
.Ar hsize
|
||||
bytes,
|
||||
|
@ -103,7 +103,7 @@ The lock file could not be read via
|
||||
.Xr read 2 .
|
||||
.Pp
|
||||
.Dv UU_LOCK_CREAT_ERR :
|
||||
Can't create temporary lock file via
|
||||
Cannot create temporary lock file via
|
||||
.Xr creat 2 .
|
||||
.Pp
|
||||
.Dv UU_LOCK_WRITE_ERR :
|
||||
@ -111,7 +111,7 @@ The current process id could not be written to the lock file via a call to
|
||||
.Xr write 2 .
|
||||
.Pp
|
||||
.Dv UU_LOCK_LINK_ERR :
|
||||
Can't link temporary lock file via
|
||||
Cannot link temporary lock file via
|
||||
.Xr link 2 .
|
||||
.Pp
|
||||
.Dv UU_LOCK_TRY_ERR :
|
||||
|
@ -331,7 +331,7 @@ Rather than repeatedly specifying these tags, a full
|
||||
specification can be listed for one host entry and shared by others via the
|
||||
.Em tc
|
||||
(table continuation) mechanism.
|
||||
Often, the template entry is a dummy host which doesn't actually exist and
|
||||
Often, the template entry is a dummy host which does not actually exist and
|
||||
never sends bootp requests.
|
||||
This feature is similar to the
|
||||
.Em tc
|
||||
|
@ -106,7 +106,7 @@ Specify the location of the netid information
|
||||
file.
|
||||
The compiled-in default is
|
||||
.Pa /etc/netid .
|
||||
Note that no error is generated if the netid database can't be
|
||||
Note that no error is generated if the netid database cannot be
|
||||
found.
|
||||
The netid database is not likely to be present on most systems
|
||||
until
|
||||
|
@ -219,7 +219,7 @@ for the local user's login class.
|
||||
.It Sy Can't make pipe.
|
||||
The pipe needed for the
|
||||
.Em stderr ,
|
||||
wasn't created.
|
||||
was not created.
|
||||
.It Sy Can't fork; try again.
|
||||
A
|
||||
.Xr fork 2
|
||||
|
@ -176,7 +176,7 @@ server is registered on the
|
||||
.Tn NIS
|
||||
master server and attempt to use
|
||||
it if it is present.
|
||||
If it isn't it will fall back to the standard
|
||||
If it is not it will fall back to the standard
|
||||
transfer method, copying the map contents from
|
||||
.Xr ypserv 8
|
||||
and creating new maps instead.
|
||||
|
@ -134,7 +134,7 @@ This form should be invoked from root's
|
||||
.Xr crontab 5
|
||||
every half hour between midnight and 5am, when most modern time
|
||||
zone changes occur.
|
||||
Warning: don't use the
|
||||
Warning: do not use the
|
||||
.Fl s
|
||||
option in a
|
||||
.Xr crontab 5
|
||||
|
@ -51,7 +51,7 @@ makes the pack appear perfect, and such packs can then be copied with
|
||||
The technique used by this program is also less general than
|
||||
bad block forwarding, as
|
||||
.Nm
|
||||
can't make amends for
|
||||
cannot make amends for
|
||||
bad blocks in the i-list of file systems or in swap areas.
|
||||
.Pp
|
||||
On some disks,
|
||||
|
@ -285,7 +285,7 @@ argument), the given bus (XPT_SCAN_BUS), or bus:target:lun
|
||||
The user
|
||||
may specify a scan of all busses, a single bus, or a lun.
|
||||
Scanning all luns
|
||||
on a target isn't supported.
|
||||
on a target is not supported.
|
||||
.It Ic reset
|
||||
Tell the kernel to reset all busses in the system (with the
|
||||
.Ar all
|
||||
@ -313,14 +313,14 @@ required.
|
||||
Most drives support the physical sector format.
|
||||
Some drives
|
||||
support the logical block format.
|
||||
Many drives, if they don't support the
|
||||
Many drives, if they do not support the
|
||||
requested format, return the data in an alternate format, along with sense
|
||||
information indicating that the requested data format isn't supported.
|
||||
information indicating that the requested data format is not supported.
|
||||
The
|
||||
.Nm
|
||||
utility
|
||||
attempts to detect this, and print out whatever format the drive returns.
|
||||
If the drive uses a non-standard sense code to report that it doesn't
|
||||
If the drive uses a non-standard sense code to report that it does not
|
||||
support the requested format,
|
||||
.Nm
|
||||
will probably see the error as a failure to complete the request.
|
||||
@ -492,7 +492,7 @@ switch for this
|
||||
.Nm
|
||||
subcommand is described below.
|
||||
.It Fl q
|
||||
Be quiet, and don't report the number of tags.
|
||||
Be quiet, and do not report the number of tags.
|
||||
This is generally used when
|
||||
setting the number of tags.
|
||||
.It Fl v
|
||||
@ -566,7 +566,7 @@ The meaning of the
|
||||
flag for the
|
||||
.Ic negotiate
|
||||
command is described below.
|
||||
Also, some controller drivers don't support
|
||||
Also, some controller drivers do not support
|
||||
setting negotiation parameters, even if the underlying controller supports
|
||||
negotiation changes.
|
||||
Some controllers, such as the Advansys wide
|
||||
@ -584,9 +584,9 @@ Enable or disable disconnection.
|
||||
.It Fl O Ar offset
|
||||
Set the command delay offset.
|
||||
.It Fl q
|
||||
Be quiet, don't print anything.
|
||||
Be quiet, do not print anything.
|
||||
This is generally useful when you want to
|
||||
set a parameter, but don't want any status information.
|
||||
set a parameter, but do not want any status information.
|
||||
.It Fl R Ar syncrate
|
||||
Change the synchronization rate for a device.
|
||||
The sync rate is a floating
|
||||
@ -655,7 +655,7 @@ Some hard
|
||||
disks will complete a format operation in a very short period of time
|
||||
(on the order of 5 minutes or less).
|
||||
This is often because the drive
|
||||
doesn't really support the FORMAT UNIT command -- it just accepts the
|
||||
does not really support the FORMAT UNIT command -- it just accepts the
|
||||
command, waits a few minutes and then returns it.
|
||||
.Pp
|
||||
The
|
||||
@ -669,7 +669,7 @@ arguments can be useful for scripts.
|
||||
.Pp
|
||||
.Bl -tag -width 6n
|
||||
.It Fl q
|
||||
Be quiet, don't print any status messages.
|
||||
Be quiet, do not print any status messages.
|
||||
This option will not disable
|
||||
the questions, however.
|
||||
To disable questions, use the
|
||||
@ -697,7 +697,7 @@ will issue a non-immediate format command, and will be unable to print any
|
||||
information to let the user know what percentage of the disk has been
|
||||
formatted.
|
||||
.It Fl y
|
||||
Don't ask any questions.
|
||||
Do not ask any questions.
|
||||
By default,
|
||||
.Nm
|
||||
will ask the user if he/she really wants to format the disk in question,
|
||||
@ -853,7 +853,7 @@ in
|
||||
.Sh AUTHORS
|
||||
.An Kenneth Merry Aq ken@FreeBSD.org
|
||||
.Sh BUGS
|
||||
The code that parses the generic command line arguments doesn't know that
|
||||
The code that parses the generic command line arguments does not know that
|
||||
some of the subcommands take multiple arguments.
|
||||
So if, for instance, you
|
||||
tried something like this:
|
||||
|
@ -104,7 +104,7 @@ and
|
||||
.Xr m4 1 .
|
||||
If
|
||||
.Ar preproc
|
||||
doesn't start with a slash
|
||||
does not start with a slash
|
||||
.Pq Ql /
|
||||
as its first character, the usual
|
||||
.Ev PATH
|
||||
@ -168,7 +168,7 @@ One rule is always present:
|
||||
65535 deny all from any to any
|
||||
.Ed
|
||||
.Pp
|
||||
This rule is the default policy, i.e., don't allow anything at all.
|
||||
This rule is the default policy, i.e., do not allow anything at all.
|
||||
Your job in setting up rules is to modify this policy to match your
|
||||
needs.
|
||||
.Pp
|
||||
@ -180,7 +180,7 @@ See also
|
||||
.Dq show
|
||||
command.
|
||||
.It Fl f
|
||||
Don't ask for confirmation for commands that can cause problems if misused
|
||||
Do not ask for confirmation for commands that can cause problems if misused
|
||||
(ie; flush).
|
||||
.Ar Note ,
|
||||
if there is no tty associated with the process, this is implied.
|
||||
@ -497,7 +497,7 @@ Most connections need packets going in both directions.
|
||||
Remember to test very carefully.
|
||||
It is a good idea to be near the console when doing this.
|
||||
.It
|
||||
Don't forget the loopback interface.
|
||||
Do not forget the loopback interface.
|
||||
.El
|
||||
.Sh FINE POINTS
|
||||
There is one kind of packet that the firewall will always discard,
|
||||
@ -576,7 +576,7 @@ When
|
||||
using it for the first time, work on the console of the computer, and
|
||||
do
|
||||
.Em NOT
|
||||
do anything you don't understand.
|
||||
do anything you do not understand.
|
||||
.Pp
|
||||
When manipulating/adding chain entries, service and protocol names are
|
||||
not accepted.
|
||||
|
@ -230,7 +230,7 @@ While listing, if the
|
||||
.Fl d
|
||||
option was specified, also show expired dynamic rules.
|
||||
.It Fl f
|
||||
Don't ask for confirmation for commands that can cause problems
|
||||
Do not ask for confirmation for commands that can cause problems
|
||||
if misused,
|
||||
.No i.e. Cm flush .
|
||||
If there is no tty associated with the process, this is implied.
|
||||
@ -303,7 +303,7 @@ and
|
||||
.Xr m4 1 .
|
||||
If
|
||||
.Ar preproc
|
||||
doesn't start with a slash
|
||||
does not start with a slash
|
||||
.Pq Ql /
|
||||
as its first character, the usual
|
||||
.Ev PATH
|
||||
@ -1771,7 +1771,7 @@ If you cannot be near the console,
|
||||
use an auto-recovery script such as the one in
|
||||
.Pa /usr/share/examples/ipfw/change_rules.sh .
|
||||
.It
|
||||
Don't forget the loopback interface.
|
||||
Do not forget the loopback interface.
|
||||
.El
|
||||
.Sh FINE POINTS
|
||||
.Bl -bullet
|
||||
@ -1827,7 +1827,7 @@ A
|
||||
socket bound to the specified port will receive all packets
|
||||
diverted to that port.
|
||||
If no socket is bound to the destination port, or if the divert module is
|
||||
not loaded, or if the kernel wasn't compiled with divert socket support,
|
||||
not loaded, or if the kernel was not compiled with divert socket support,
|
||||
the packets are dropped.
|
||||
.Sh SYSCTL VARIABLES
|
||||
A set of
|
||||
|
@ -153,7 +153,7 @@ in 2003.
|
||||
POSIX device node mapping is currently not supported.
|
||||
.Pp
|
||||
Version numbers are not stripped if Rockridge extensions are in use.
|
||||
In this case, accessing files that don't have Rockridge names without
|
||||
In this case, accessing files that do not have Rockridge names without
|
||||
version numbers gets the one with the lowest version number and not
|
||||
the one with the highest.
|
||||
.Pp
|
||||
|
@ -70,7 +70,7 @@ to determine geometry, if required.
|
||||
The options are as follow:
|
||||
.Bl -tag -width indent
|
||||
.It Fl N
|
||||
Don't create a file system: just print out parameters.
|
||||
Do not create a file system: just print out parameters.
|
||||
.It Fl B Ar boot
|
||||
Get bootstrap from file.
|
||||
.It Fl F Ar FAT-type
|
||||
|
@ -54,7 +54,7 @@ on the cisco.
|
||||
This is because the tunnel is a point-to-point interface
|
||||
in the
|
||||
.Fx
|
||||
end, a concept cisco doesn't really implement.
|
||||
end, a concept cisco does not really implement.
|
||||
.Pp
|
||||
.Ar Protocol number
|
||||
sets tunnel mode.
|
||||
@ -89,4 +89,4 @@ wrote the man-page.
|
||||
.An Isao SEKI Aq iseki@gongon.com
|
||||
added a new flag, IP protocol number.
|
||||
.Sh BUGS
|
||||
We don't allow for setting our source address for multihomed machines.
|
||||
We do not allow for setting our source address for multihomed machines.
|
||||
|
@ -506,4 +506,4 @@ operation that may have been interrupted, the temporary files should
|
||||
be the same across different processes.
|
||||
In all other cases, the files are unique because it is possible to
|
||||
have two different dumps started at the same time, and separate
|
||||
operations shouldn't conflict with each other.
|
||||
operations should not conflict with each other.
|
||||
|
@ -383,7 +383,7 @@ on a directly-connected network.
|
||||
The next-hop gateway must be given.
|
||||
.It "not in table"
|
||||
A delete operation was attempted for an entry which
|
||||
wasn't present in the tables.
|
||||
was not present in the tables.
|
||||
.It "routing table overflow"
|
||||
An add operation was attempted, but the system was
|
||||
low on resources and was unable to allocate memory
|
||||
|
@ -141,7 +141,7 @@ For CHAP, this will be used to compute the response hash value, based
|
||||
on remote's challenge.
|
||||
For PAP, it will be transmitted as plain text
|
||||
together with the system name.
|
||||
Don't forget to quote the secrets from
|
||||
Do not forget to quote the secrets from
|
||||
the shell if they contain shell metacharacters (or white space).
|
||||
.It Va myauthkey Ns Li = Ns Ar secret
|
||||
Same as above.
|
||||
@ -170,7 +170,7 @@ Only meaningful with CHAP.
|
||||
Do not re-challenge peer once the initial
|
||||
CHAP handshake was successful.
|
||||
Used to work around broken peer
|
||||
implementations that can't grok being re-challenged once the
|
||||
implementations that cannot grok being re-challenged once the
|
||||
connection is up.
|
||||
.It Ar rechallenge
|
||||
With CHAP, send re-challenges at random intervals while the connection
|
||||
|
@ -165,4 +165,4 @@ This utility should work on active file systems.
|
||||
.\" Take this out and a Unix Daemon will dog your steps from now until
|
||||
.\" the time_t's wrap around.
|
||||
.Pp
|
||||
You can tune a file system, but you can't tune a fish.
|
||||
You can tune a file system, but you cannot tune a fish.
|
||||
|
@ -299,7 +299,7 @@ Lock a mutex and block until it becomes available or until the timeout expires.
|
||||
.Ft int
|
||||
.Fn pthread_mutex_trylock "pthread_mutex_t *mutex"
|
||||
.Xc
|
||||
Try to lock a mutex, but don't block if the mutex is locked by another thread,
|
||||
Try to lock a mutex, but do not block if the mutex is locked by another thread,
|
||||
including the current thread.
|
||||
.It Xo
|
||||
.Ft int
|
||||
|
@ -156,7 +156,7 @@ always be restored to its value on entry to the object.
|
||||
.Pp
|
||||
This follows from a modularity argument: if the client of an object (or the
|
||||
client of an object that uses that object) has disabled cancelability, it is
|
||||
because the client doesn't want to have to worry about how to clean up if the
|
||||
because the client does not want to have to worry about how to clean up if the
|
||||
thread is canceled while executing some sequence of actions.
|
||||
If an object
|
||||
is called in such a state and it enables cancelability and a cancellation
|
||||
|
@ -80,7 +80,7 @@ A service is unavailable.
|
||||
This can occur if a support program or file
|
||||
does not exist.
|
||||
This can also be used as a catchall message when
|
||||
something you wanted to do doesn't work, but you don't know why.
|
||||
something you wanted to do does not work, but you do not know why.
|
||||
.It Sy EX_SOFTWARE Pq 70
|
||||
An internal software error has been detected.
|
||||
This should be limited
|
||||
|
@ -43,7 +43,7 @@ driver also supports a variant of adhoc mode out of spec for DS radio cards,
|
||||
which makes it possible to communicate with adhoc mode of
|
||||
.Xr wi 8
|
||||
driver.
|
||||
The NWID doesn't affect in this mode.
|
||||
The NWID does not affect in this mode.
|
||||
.Pp
|
||||
For more information on configuring this device, see
|
||||
.Xr ifconfig 8 .
|
||||
|
@ -214,7 +214,7 @@ and
|
||||
.It Li bs_drop
|
||||
the number of packets which were accepted by the filter but dropped by the
|
||||
kernel because of buffer overflows
|
||||
(i.e., the application's reads aren't keeping up with the packet traffic).
|
||||
(i.e., the application's reads are not keeping up with the packet traffic).
|
||||
.El
|
||||
.It Dv BIOCIMMEDIATE
|
||||
.Pq Li u_int
|
||||
@ -349,7 +349,7 @@ header will be word aligned.
|
||||
Suitable precautions
|
||||
must be taken when accessing the link layer protocol fields on alignment
|
||||
restricted machines.
|
||||
(This isn't a problem on an Ethernet, since
|
||||
(This is not a problem on an Ethernet, since
|
||||
the type field is a short falling on an even offset,
|
||||
and the addresses are probably accessed in a bytewise fashion).
|
||||
.Pp
|
||||
@ -586,7 +586,7 @@ BPF_RET+BPF_A accept A bytes
|
||||
BPF_RET+BPF_K accept k bytes
|
||||
.Ed
|
||||
.It Dv BPF_MISC
|
||||
The miscellaneous category was created for anything that doesn't
|
||||
The miscellaneous category was created for anything that does not
|
||||
fit into the above classes, and for any new instructions that might need to
|
||||
be added.
|
||||
Currently, these are the register transfer instructions
|
||||
|
@ -171,11 +171,11 @@ In particular, the initial states for non (POSIX) standard flags
|
||||
should be set to suit the devices attached and may need to be
|
||||
locked to prevent buggy programs from changing them.
|
||||
E.g., CRTSCTS should be locked on for devices that support
|
||||
RTS/CTS handshaking at all times and off for devices that don't
|
||||
RTS/CTS handshaking at all times and off for devices that do not
|
||||
support it at all.
|
||||
CLOCAL should be locked on for devices
|
||||
that don't support carrier.
|
||||
HUPCL may be locked off if you don't
|
||||
that do not support carrier.
|
||||
HUPCL may be locked off if you do not
|
||||
want to hang up for some reason.
|
||||
In general, very bad things happen
|
||||
if something is locked to the wrong state, and things should not
|
||||
|
@ -236,9 +236,9 @@ The default is 6 bytes.
|
||||
The
|
||||
.Nm
|
||||
driver issues a CAM Path Inquiry CCB at probe time to determine whether the
|
||||
protocol the device in question speaks (e.g.\& ATAPI) typically doesn't allow
|
||||
protocol the device in question speaks (e.g.\& ATAPI) typically does not allow
|
||||
6 byte commands.
|
||||
If it doesn't, the
|
||||
If it does not, the
|
||||
.Nm
|
||||
driver will default to using at least 10 byte CDBs.
|
||||
If a 6 byte READ or WRITE fails with an ILLEGAL REQUEST error, the
|
||||
|
@ -314,7 +314,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip
|
||||
out of this state before configuring it.
|
||||
The controller loses all of
|
||||
its PCI configuration in the D3 state, so if the BIOS does not set
|
||||
it back to full power mode in time, it won't be able to configure it
|
||||
it back to full power mode in time, it will not 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
|
||||
|
@ -99,7 +99,7 @@ a hexadecimal format at a prompt.
|
||||
Examine and write commands update `dot' to the address of the last line
|
||||
examined or the last location modified, and set `next' to the address of
|
||||
the next location to be examined or changed.
|
||||
Other commands don't change `dot', and set `next' to be the same as `dot'.
|
||||
Other commands do not change `dot', and set `next' to be the same as `dot'.
|
||||
.Pp
|
||||
The general command syntax is:
|
||||
.Cm command Ns Op Li \&/ Ns Ar modifier
|
||||
@ -394,8 +394,8 @@ only if the machine dependent code supports it.
|
||||
Search memory for
|
||||
.Ar value .
|
||||
This command might fail in interesting
|
||||
ways if it doesn't find the searched-for value.
|
||||
This is because ddb doesn't always recover from touching bad memory.
|
||||
ways if it does not find the searched-for value.
|
||||
This is because ddb does not always recover from touching bad memory.
|
||||
The optional
|
||||
.Ar count
|
||||
argument limits the search.
|
||||
|
@ -72,7 +72,7 @@ Meaning of
|
||||
.It 0x0001
|
||||
use alternate pinout (exchange DCD and DSR lines)
|
||||
.It 0x0002
|
||||
don't use 8K window mode of PC/Xe
|
||||
do not use 8K window mode of PC/Xe
|
||||
.El
|
||||
.Pp
|
||||
Device numbering:
|
||||
@ -100,7 +100,7 @@ Input and output for each line may set to one of following baud rates;
|
||||
50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600,
|
||||
19200, 38400, 57600, or for newer versions of cards 115200.
|
||||
.Pp
|
||||
The driver doesn't use any interrupts, it is
|
||||
The driver does not use any interrupts, it is
|
||||
.Dq polling-based .
|
||||
This means that
|
||||
it uses clock interrupts instead of interrupts generated by DigiBoard cards and
|
||||
@ -126,7 +126,7 @@ to change the pinout of the interface or to use new PC/Xe cards
|
||||
which can work with an 8K memory window in compatibility mode
|
||||
(with a 64K memory window).
|
||||
Note
|
||||
that using 8K memory window doesn't mean shorter input/output buffers, it means
|
||||
that using 8K memory window does not mean shorter input/output buffers, it means
|
||||
only that all buffers will be mapped to the same memory address and switched as
|
||||
needed.
|
||||
.Pp
|
||||
@ -237,13 +237,13 @@ locked to prevent buggy programs from changing them.
|
||||
E.g.,
|
||||
.Dv CRTSCTS
|
||||
should be locked on for devices that support
|
||||
RTS/CTS handshaking at all times and off for devices that don't
|
||||
RTS/CTS handshaking at all times and off for devices that do not
|
||||
support it at all.
|
||||
.Dv CLOCAL
|
||||
should be locked on for devices
|
||||
that don't support carrier.
|
||||
that do not support carrier.
|
||||
.Dv HUPCL
|
||||
may be locked off if you don't
|
||||
may be locked off if you do not
|
||||
want to hang up for some reason.
|
||||
In general, very bad things happen
|
||||
if something is locked to the wrong state, and things should not
|
||||
|
@ -176,7 +176,7 @@ could be cleaner, and it's too dependent on
|
||||
It's questionable whether incoming fragments should be reassembled
|
||||
before being diverted.
|
||||
For example, if only some fragments of a
|
||||
packet destined for another machine don't get routed through the
|
||||
packet destined for another machine do not get routed through the
|
||||
local machine, the packet is lost.
|
||||
This should probably be
|
||||
a settable socket option in any case.
|
||||
|
@ -87,7 +87,7 @@ lossage).
|
||||
Some
|
||||
.No ( non- Ns Fx
|
||||
:-)) machines have terrible Ethernet performance
|
||||
and simply can't cope with 1100K+ data rates.
|
||||
and simply cannot cope with 1100K+ data rates.
|
||||
Use of this flag also provides
|
||||
one more packet worth of receiver buffering, and on 8bit cards, this may help
|
||||
reduce receiver lossage.
|
||||
@ -262,7 +262,7 @@ This is most commonly
|
||||
caused by a BIOS extension ROM being configured in the same address space as the
|
||||
Ethernet card's shared memory.
|
||||
Either find the offending card and change its BIOS
|
||||
ROM to be at an address that doesn't conflict, or change the
|
||||
ROM to be at an address that does not conflict, or change the
|
||||
.Cd iomem
|
||||
option in the kernel config file so that the card's shared memory is mapped at a
|
||||
non-conflicting address.
|
||||
@ -279,7 +279,7 @@ the card is defective.
|
||||
Indicates a logic problem in the driver.
|
||||
Should never happen.
|
||||
.It "ed%d: device timeout"
|
||||
Indicates that an expected transmitter interrupt didn't occur.
|
||||
Indicates that an expected transmitter interrupt did not occur.
|
||||
Usually caused by an
|
||||
interrupt conflict with another card on the ISA bus.
|
||||
This condition could also be caused if the kernel is configured for a
|
||||
|
@ -147,7 +147,7 @@ already has one, or when trying to send a datagram with the destination
|
||||
address specified and the socket is already connected;
|
||||
.It Bq Er ENOTCONN
|
||||
when trying to send a datagram, but
|
||||
no destination address is specified, and the socket hasn't been
|
||||
no destination address is specified, and the socket has not been
|
||||
connected;
|
||||
.It Bq Er ENOBUFS
|
||||
when the system runs out of memory for
|
||||
|
@ -60,4 +60,4 @@ This device requires IRQ 9 exclusively.
|
||||
To use this, you should enable
|
||||
ACPI function in BIOS configuration, or PnP mechanism assigns conflicted
|
||||
IRQ for PnP ISA card.
|
||||
And don't use IRQ 9 for Non-PnP ISA cards.
|
||||
And do not use IRQ 9 for Non-PnP ISA cards.
|
||||
|
@ -564,7 +564,7 @@ already has one, or when trying to send a datagram with the destination
|
||||
address specified and the socket is already connected;
|
||||
.It Bq Er ENOTCONN
|
||||
when trying to send a datagram, but
|
||||
no destination address is specified, and the socket hasn't been
|
||||
no destination address is specified, and the socket has not been
|
||||
connected;
|
||||
.It Bq Er ENOBUFS
|
||||
when the system runs out of memory for
|
||||
|
@ -611,7 +611,7 @@ already has one or when trying to send a datagram with the destination
|
||||
address specified and the socket is already connected.
|
||||
.It Bq Er ENOTCONN
|
||||
when trying to send a datagram, but
|
||||
no destination address is specified, and the socket hasn't been
|
||||
no destination address is specified, and the socket has not been
|
||||
connected.
|
||||
.It Bq Er ENOBUFS
|
||||
when the system runs out of memory for
|
||||
|
@ -185,13 +185,13 @@ driver was written by Matthew Jacob for NASA/Ames Research Center.
|
||||
.Sh BUGS
|
||||
The driver currently ignores some NVRAM settings.
|
||||
.Pp
|
||||
The driver currently doesn't do error recovery for timed out commands
|
||||
The driver currently does not do error recovery for timed out commands
|
||||
very gracefully.
|
||||
.Pp
|
||||
Target mode support isn't completely debugged yet.
|
||||
Target mode support is not completely debugged yet.
|
||||
It works reasonably
|
||||
well for Fibre Channel, somewhat well for Qlogic 1040 cards, but
|
||||
doesn't yet work for the other cards (due to last minute unannounced
|
||||
does not yet work for the other cards (due to last minute unannounced
|
||||
changes in firmware interfaces).
|
||||
.Pp
|
||||
Sometimes, when booting, the driver gets stuck waiting for the
|
||||
|
@ -128,7 +128,7 @@ Many, if not most, of the implementations of APM-bios in laptops
|
||||
today are buggy.
|
||||
You may be putting your LCD-display and batteries at
|
||||
a risk by using this interface.
|
||||
(The reason this isn't a problem for
|
||||
(The reason this is not a problem for
|
||||
MS-Windows is that they use the real-mode interface.)
|
||||
If you see any
|
||||
weird behavior from your system with this code in use, unplug the
|
||||
|
@ -104,7 +104,7 @@ The
|
||||
driver assumes the memory it allocates is within the lower 16Mb range.
|
||||
This is not a very valid assumption but there's nothing that can be done
|
||||
about it yet.
|
||||
For shared memory NICs this isn't relevant.
|
||||
For shared memory NICs this is not relevant.
|
||||
.It "lnc%d: Device timeout -- Resetting"
|
||||
The device has stopped responding to the network, or there is a problem with
|
||||
the network connection (cable).
|
||||
|
@ -147,7 +147,7 @@ features of the interface board, although it has an interrupt handler
|
||||
for any IRQ requests that are generated.
|
||||
Until the DMA features are
|
||||
supported, the only interrupts that the board generates are those that
|
||||
aren't supported by the driver anyway.
|
||||
are not supported by the driver anyway.
|
||||
.Sh SEE ALSO
|
||||
.In sys/cdio.h
|
||||
.Sh HISTORY
|
||||
|
@ -126,7 +126,7 @@ minor = (`unit' << 1) | `non-blocking'
|
||||
.Ed
|
||||
.Pp
|
||||
where `unit' is the device number (usually 0) and the `non-blocking' bit
|
||||
is set to indicate ``don't block waiting for mouse input,
|
||||
is set to indicate ``do not block waiting for mouse input,
|
||||
return immediately''.
|
||||
The `non-blocking' bit should be set for \fIXFree86\fP,
|
||||
therefore the minor device number usually used for \fIXFree86\fP is 1.
|
||||
@ -307,7 +307,7 @@ and
|
||||
are modifiable by the
|
||||
.Dv MOUSE_SETMODE
|
||||
command.
|
||||
Changing the other field doesn't cause error, but has no effect.
|
||||
Changing the other field does not cause error, but has no effect.
|
||||
.Pp
|
||||
.It Dv MOUSE_SETMODE Ar mousemode_t *mode
|
||||
The command changes the current operation parameters of the mouse driver
|
||||
|
@ -381,7 +381,7 @@ memory maps correctly - it works around
|
||||
and then throws it all away assuming the card is an
|
||||
.Xr ed 4
|
||||
driver...).
|
||||
Note that this could be dangerous (because it doesn't interact with
|
||||
Note that this could be dangerous (because it does not interact with
|
||||
.Xr pccardd 8 )
|
||||
if you use other memory mapped cards at the same time or have
|
||||
SCSI cards with on-board BIOS.
|
||||
|
@ -84,7 +84,7 @@ The
|
||||
specification in
|
||||
.Pa /boot/device.hints
|
||||
is optional.
|
||||
If it isn't specified, the driver will
|
||||
If it is not specified, the driver will
|
||||
assume the following:
|
||||
.Pp
|
||||
.Bl -hang -offset indent
|
||||
|
@ -14,7 +14,7 @@ ATM software comes with a
|
||||
which provides socket level access to AAL0 and AAL5 virtual circuits.
|
||||
To enable this protocol layer, add
|
||||
.Dl options NATM
|
||||
to your kernel configuration file and re-make the kernel (don't forget
|
||||
to your kernel configuration file and re-make the kernel (do not forget
|
||||
to do
|
||||
.Dq make clean ) .
|
||||
.Sh NATM API
|
||||
|
@ -202,7 +202,7 @@ is disabled, over the (single) PPP link.
|
||||
Typically when the controlling entity receives an unexpected packet on the
|
||||
.Dv bypass
|
||||
hook it responds either by dropping the frame (if it's not ready for
|
||||
the protocol) or with an LCP protocol reject (if it doesn't recognize
|
||||
the protocol) or with an LCP protocol reject (if it does not recognize
|
||||
or expect the protocol).
|
||||
.Sh MULTILINK OPERATION
|
||||
To enable multi-link PPP, the corresponding configuration flag must be set
|
||||
|
@ -131,7 +131,7 @@ A device must match all specified fields in order to be returned.
|
||||
The match flags are enumerated in the
|
||||
.Va pci_getconf_flags
|
||||
structure.
|
||||
Hopefully the flag values are obvious enough that they don't need to
|
||||
Hopefully the flag values are obvious enough that they do not need to
|
||||
described in detail.
|
||||
.El
|
||||
.It match_buf_len
|
||||
@ -315,11 +315,11 @@ Kenneth Merry, and first appeared in
|
||||
.Sh AUTHORS
|
||||
.An Kenneth Merry Aq ken@FreeBSD.org
|
||||
.Sh BUGS
|
||||
It isn't possible for users to specify an accurate offset into the device
|
||||
It is not possible for users to specify an accurate offset into the device
|
||||
list without calling the
|
||||
.Dv PCIOCGETCONF
|
||||
at least once, since they have no way of knowing the current generation
|
||||
number otherwise.
|
||||
This probably isn't a serious problem, though, since
|
||||
This probably is not a serious problem, though, since
|
||||
users can easily narrow their search by specifying a pattern or patterns
|
||||
for the kernel to match against.
|
||||
|
@ -248,7 +248,7 @@ characteristics of the standard.
|
||||
IEEE1284 interacts with the ppbus system as little as possible.
|
||||
That means
|
||||
you still have to request the ppbus when you want to access it, the negotiate
|
||||
function doesn't do it for you.
|
||||
function does not do it for you.
|
||||
And of course, release it later.
|
||||
.Sh ARCHITECTURE
|
||||
.Ss adapter, ppbus and device layers
|
||||
|
@ -87,7 +87,7 @@ The PS/2 style pointing device typically supports 10, 20, 40, 60, 80, 100
|
||||
and 200 reports per second.
|
||||
60 or 100 appears to be the default value for many devices.
|
||||
Note that when there is no movement and no button has changed its state,
|
||||
the device won't send anything to the host system.
|
||||
the device will not send anything to the host system.
|
||||
The report rate can be changed via an ioctl call.
|
||||
.Ss Operation Levels
|
||||
The
|
||||
@ -186,7 +186,7 @@ minor = (`unit' << 1) | `non-blocking'
|
||||
.Ed
|
||||
.Pp
|
||||
where `unit' is the device number (usually 0) and the `non-blocking' bit
|
||||
is set to indicate ``don't block waiting for mouse input,
|
||||
is set to indicate ``do not block waiting for mouse input,
|
||||
return immediately''.
|
||||
The `non-blocking' bit should be set for \fIXFree86\fP,
|
||||
therefore the minor device number usually used for \fIXFree86\fP is 1.
|
||||
@ -293,14 +293,14 @@ driver will not try to identify the model of the pointing device and
|
||||
will not carry out model-specific initialization.
|
||||
The device should always act like a standard PS/2 mouse without such
|
||||
initialization.
|
||||
Extra features, such as wheels and additional buttons, won't be
|
||||
Extra features, such as wheels and additional buttons, will not be
|
||||
recognized by the
|
||||
.Nm
|
||||
driver.
|
||||
.It bit 10 NORESET
|
||||
When this flag is set, the
|
||||
.Nm
|
||||
driver won't reset the pointing device when initializing the device.
|
||||
driver will not reset the pointing device when initializing the device.
|
||||
If the
|
||||
.Fx
|
||||
kernel
|
||||
|
@ -209,7 +209,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip
|
||||
out of this state before configuring it.
|
||||
The controller loses all of
|
||||
its PCI configuration in the D3 state, so if the BIOS does not set
|
||||
it back to full power mode in time, it won't be able to configure it
|
||||
it back to full power mode in time, it will not 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
|
||||
|
@ -191,5 +191,5 @@ or in the
|
||||
tty layer.
|
||||
.\" (Although my bet is that it's in the higher-level tty layer;
|
||||
.\" given the bugs I found while writing this driver, it's clear
|
||||
.\" the BSD software flow control code hasn't been tested very much
|
||||
.\" the BSD software flow control code has not been tested very much
|
||||
.\" at all! -- TYT)
|
||||
|
@ -169,7 +169,7 @@ If a rewind is requested after a write, then the driver
|
||||
assumes that the last file on the tape has been written, and ensures
|
||||
that there are two file marks written to the tape.
|
||||
The exception to
|
||||
this is that there seems to be a standard (which we follow, but don't
|
||||
this is that there seems to be a standard (which we follow, but do not
|
||||
understand why) that certain types of tape do not actually write two
|
||||
file marks to tape, but when read, report a `phantom' file mark when the
|
||||
last file is read.
|
||||
@ -235,7 +235,7 @@ Additionally, certain
|
||||
tapes (QIC tapes mostly) that were written under
|
||||
.Fx
|
||||
2.X
|
||||
aren't automatically read correctly with this driver: you may need to
|
||||
are not automatically read correctly with this driver: you may need to
|
||||
explicitly set variable block mode or set to the blocksize that works best
|
||||
for your device in order to read tapes written under
|
||||
.Fx
|
||||
|
@ -75,7 +75,7 @@ subsystem:
|
||||
.Bl -tag -width SCSI_NO_SENSE_STRINGS
|
||||
.It Dv CAMDEBUG
|
||||
This option enables the CAM debugging printf code.
|
||||
This won't actually
|
||||
This will not actually
|
||||
cause any debugging information to be printed out when included by itself.
|
||||
Enabling printouts requires additional configuration.
|
||||
See below for details.
|
||||
@ -105,7 +105,7 @@ In most cases, though,
|
||||
this should be enabled, since it speeds the interpretation of
|
||||
.Tn SCSI
|
||||
error messages.
|
||||
Don't let the "kernel bloat" zealots get to you -- leave
|
||||
Do not let the "kernel bloat" zealots get to you -- leave
|
||||
the sense descriptions in your kernel!
|
||||
.It Dv SCSI_NO_OP_STRINGS
|
||||
This disables text descriptions of each
|
||||
@ -113,7 +113,7 @@ This disables text descriptions of each
|
||||
opcode.
|
||||
This option, like the sense string option above, is primarily
|
||||
useful for environments like a boot floppy where kernel size is critical.
|
||||
Enabling this option for normal use isn't recommended, since it slows
|
||||
Enabling this option for normal use is not recommended, since it slows
|
||||
debugging of
|
||||
.Tn SCSI
|
||||
problems.
|
||||
@ -137,7 +137,7 @@ Newer disks
|
||||
may need as little as 100ms, while old, slow devices may need much longer.
|
||||
If the
|
||||
.Dv SCSI_DELAY
|
||||
isn't specified, it defaults to 2 seconds.
|
||||
is not specified, it defaults to 2 seconds.
|
||||
The minimum allowable value for
|
||||
.Dv SCSI_DELAY
|
||||
is "100", or 100ms.
|
||||
@ -268,10 +268,10 @@ Some of these flags, most notably
|
||||
and
|
||||
.Dv CAM_DEBUG_SUBTRACE
|
||||
will produce kernel printfs in EXTREME numbers,
|
||||
and because of that, they aren't especially useful.
|
||||
There aren't many things logged at the
|
||||
and because of that, they are not especially useful.
|
||||
There are not many things logged at the
|
||||
.Dv CAM_DEBUG_INFO
|
||||
level, so it isn't especially useful.
|
||||
level, so it is not especially useful.
|
||||
The most useful debugging flag is the
|
||||
.Dv CAM_DEBUG_CDB
|
||||
flag.
|
||||
|
@ -229,7 +229,7 @@ port.
|
||||
The driver supports controller based PCI modems.
|
||||
The 3Com FaxModem PCI and the Advantec 56k Voice Messaging PCI
|
||||
FaxModem are the only cards supported.
|
||||
WinModems, softmodems, hfc modems and any other modems that aren't
|
||||
WinModems, softmodems, hfc modems and any other modems that are not
|
||||
controller based are not supported.
|
||||
.Pp
|
||||
The
|
||||
@ -330,10 +330,10 @@ In particular, the initial states for non (POSIX) standard flags
|
||||
should be set to suit the devices attached and may need to be
|
||||
locked to prevent buggy programs from changing them.
|
||||
E.g., CRTSCTS should be locked on for devices that support
|
||||
RTS/CTS handshaking at all times and off for devices that don't
|
||||
RTS/CTS handshaking at all times and off for devices that do not
|
||||
support it at all.
|
||||
CLOCAL should be locked on for devices that don't support carrier.
|
||||
HUPCL may be locked off if you don't
|
||||
CLOCAL should be locked on for devices that do not support carrier.
|
||||
HUPCL may be locked off if you do not
|
||||
want to hang up for some reason.
|
||||
In general, very bad things happen
|
||||
if something is locked to the wrong state, and things should not
|
||||
|
@ -78,7 +78,7 @@ signals an
|
||||
event (rise of
|
||||
.Dq carrier ) .
|
||||
This can be used by lower layers to support
|
||||
a dialin connection where the physical layer isn't available
|
||||
a dialin connection where the physical layer is not available
|
||||
immediately at startup, but only after some external event arrives.
|
||||
Receipt of a
|
||||
.Em Down
|
||||
@ -134,7 +134,7 @@ wrong assumptions.
|
||||
In a similar spirit the remote address can be set to the magical
|
||||
value
|
||||
.Li 0.0.0. Ns Em *
|
||||
which means that we don't care what address the remote
|
||||
which means that we do not care what address the remote
|
||||
side will use, as long as it is not 0.0.0.0.
|
||||
This is useful if your ISP has several dial-in
|
||||
servers.
|
||||
@ -227,7 +227,7 @@ for authentication and link quality reporting.
|
||||
.Pp
|
||||
Negotiation loop avoidance is not fully implemented.
|
||||
If the negotiation
|
||||
doesn't converge, this can cause an endless loop.
|
||||
does not converge, this can cause an endless loop.
|
||||
.Pp
|
||||
The various parameters that should be adjustable per RFC 1661 are
|
||||
currently hard-coded into the kernel, and should be made accessible
|
||||
|
@ -136,7 +136,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip
|
||||
out of this state before configuring it.
|
||||
The controller loses all of
|
||||
its PCI configuration in the D3 state, so if the BIOS does not set
|
||||
it back to full power mode in time, it won't be able to configure it
|
||||
it back to full power mode in time, it will not 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
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user