Fix some typos and do some minor mdoc cleanup.
This commit is contained in:
parent
f858a016d8
commit
5d70612b3f
@ -29,13 +29,13 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: buf.9,v 1.1 1998/12/22 19:47:48 dillon Exp $
|
||||
.\" $Id: buf.9,v 1.2 1999/02/01 22:55:54 mpp Exp $
|
||||
.\"
|
||||
.Dd December 22, 1998
|
||||
.Dt BUF 9
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm BUF/BP
|
||||
.Nm BUF
|
||||
.Nd Kernel Buffer I/O scheme used in FreeBSD VM system
|
||||
.Sh DESCRIPTION
|
||||
.Pp
|
||||
@ -112,12 +112,13 @@ instantiated VM Buffers (struct buf's) prevent their underlying pages in the
|
||||
buffer cache from being freed. This can complicate the life of the paging
|
||||
system.
|
||||
.Pp
|
||||
.Sh SEE ALSO
|
||||
.Pp
|
||||
.Xr <fillmein> 9
|
||||
.\" .Sh SEE ALSO
|
||||
.\" .Xr <fillmein> 9
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
manual page was originally written by Matthew Dillon and first appeared
|
||||
in FreeBSD-3.0.1, December 1998.
|
||||
in
|
||||
.Fx 3.0.1 ,
|
||||
December 1998.
|
||||
|
||||
|
@ -26,7 +26,7 @@
|
||||
.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: ifnet.9,v 1.5 1997/01/15 19:28:39 wollman Exp $
|
||||
.\" $Id: ifnet.9,v 1.6 1998/03/12 07:31:17 charnier Exp $
|
||||
.Dd January 15, 1997
|
||||
.Os FreeBSD 3.0
|
||||
.Dt IFNET 9
|
||||
@ -712,7 +712,7 @@ order.
|
||||
.It Li ifma_lladdr
|
||||
.Pq Li "struct sockaddr *"
|
||||
A pointer to the link-layer multicast address, if any, to which the
|
||||
network-layter multicast address in
|
||||
network-layer multicast address in
|
||||
.Li ifma_addr
|
||||
is mapped, else a null pointer. If this element is non-nil, this
|
||||
membership also holds an invisible reference to another membership for
|
||||
|
@ -116,7 +116,7 @@ and return
|
||||
immediately. It is expected that the caller will at some point call
|
||||
.Fn await
|
||||
and then retry the allocation. Depending on the routine in question, the
|
||||
caller may decide to propogate the temporary failure up the call chain
|
||||
caller may decide to propagate the temporary failure up the call chain
|
||||
and actually have some other higher level routine block on the async wait
|
||||
that
|
||||
.Fn malloc
|
||||
|
@ -400,7 +400,7 @@ struct ppb_microseq {
|
||||
};
|
||||
.Ed
|
||||
.Ss Using microsequences
|
||||
To instanciate a microsequence, just declare an array of ppb_microseq
|
||||
To instantiate a microsequence, just declare an array of ppb_microseq
|
||||
structures and initialize it as needed. You may either use predefined macros
|
||||
or code directly your microinstructions according to the ppb_microseq
|
||||
definition. For example,
|
||||
|
@ -22,7 +22,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: style.9,v 1.22 1997/12/07 20:25:45 wollman Exp $
|
||||
.\" $Id: style.9,v 1.23 1999/01/30 04:17:14 julian Exp $
|
||||
.\"
|
||||
.Dd December 14, 1995
|
||||
.Dt STYLE 9
|
||||
@ -435,7 +435,7 @@ function(a1, a2, fl, a4)
|
||||
{
|
||||
.Ed
|
||||
.Pp
|
||||
Use ANSI function declarations unless you explicitly need K&R compatability.
|
||||
Use ANSI function declarations unless you explicitly need K&R compatibility.
|
||||
.Pp
|
||||
Variable numbers of arguments should look like this.
|
||||
.Bd -literal -offset 0i
|
||||
@ -486,7 +486,7 @@ placed in a single set of braces.
|
||||
.Pp
|
||||
New core kernel code should be reasonably compliant with the style guides.
|
||||
The guidelines for third-party maintained modules and device drivers are more
|
||||
relaxed but at a minimum should be internally consistant with their style.
|
||||
relaxed but at a minimum should be internally consistent with their style.
|
||||
.Pp
|
||||
Stylistic changes (including whitespace changes) are hard on the source
|
||||
repository and are to be avoided without good reason. Code that is
|
||||
|
@ -31,7 +31,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: suser.9,v 1.6 1999/04/28 11:38:52 phk Exp $
|
||||
.\" $Id: suser.9,v 1.7 1999/06/02 16:33:22 bde Exp $
|
||||
.\"
|
||||
.Dd Oct 15, 1996
|
||||
.Dt SUSER 9
|
||||
@ -63,7 +63,7 @@ The
|
||||
.Nm suser_xxx
|
||||
function should be used when the credentials to be checked are
|
||||
not the process' own, when there is no process or when superuser
|
||||
powers should be extended to prisoned roots.
|
||||
powers should be extended to imprisoned roots.
|
||||
.Pp
|
||||
By default a process does not command superuser powers if it has
|
||||
been imprisoned by the
|
||||
|
Loading…
Reference in New Issue
Block a user