mdoc(7) police: remove whitespace at EOL.
This commit is contained in:
parent
8edb7b74a0
commit
f868de5160
@ -52,7 +52,7 @@ protection of the stored data.
|
||||
.Pp
|
||||
Compared to traditional "volume management", GEOM differs from most
|
||||
and in some cases all previous implementations in the following ways:
|
||||
.Bl -bullet
|
||||
.Bl -bullet
|
||||
.It
|
||||
GEOM is extensible. It is trivially simple to write a new class
|
||||
of transformation and it will not be given stepchild treatment. If
|
||||
|
@ -69,7 +69,7 @@ file that are included as modules on the mfsroot floppy.
|
||||
.Pp
|
||||
The second field,
|
||||
.Ar filename ,
|
||||
is the name of the associated kernel module (without the
|
||||
is the name of the associated kernel module (without the
|
||||
.Pa .ko
|
||||
extension).
|
||||
.Pp
|
||||
|
@ -39,11 +39,11 @@ This document presents guidelines for
|
||||
adding security considerations sections to manual pages.
|
||||
It provides two typical examples.
|
||||
.Pp
|
||||
The guidelines for writing
|
||||
The guidelines for writing
|
||||
.Fx
|
||||
manual pages in
|
||||
.Xr groff_mdoc 7
|
||||
mandate that each manual page describing a feature of the
|
||||
mandate that each manual page describing a feature of the
|
||||
.Fx
|
||||
system should contain a security considerations section
|
||||
describing what security requirements can be broken
|
||||
@ -70,7 +70,7 @@ there are four classes of security requirements:
|
||||
.Bl -hang -offset indent
|
||||
.It Em integrity
|
||||
(example: non-administrators should not modify system binaries),
|
||||
.It Em confidentiality
|
||||
.It Em confidentiality
|
||||
(example: non-administrators should not view the shadow password file),
|
||||
.It Em availability
|
||||
(example: the web server should respond to client requests in a timely
|
||||
@ -187,7 +187,7 @@ the FSA.)
|
||||
Avoid using
|
||||
.Fn strcpy .
|
||||
Instead, use
|
||||
.Fn strncpy
|
||||
.Fn strncpy
|
||||
and ensure that no more characters are copied to the destination buffer
|
||||
than it can hold.
|
||||
Do not forget to NUL-terminate the destination buffer,
|
||||
|
@ -39,11 +39,11 @@ This document presents guidelines for
|
||||
adding security considerations sections to manual pages.
|
||||
It provides two typical examples.
|
||||
.Pp
|
||||
The guidelines for writing
|
||||
The guidelines for writing
|
||||
.Fx
|
||||
manual pages in
|
||||
.Xr groff_mdoc 7
|
||||
mandate that each manual page describing a feature of the
|
||||
mandate that each manual page describing a feature of the
|
||||
.Fx
|
||||
system should contain a security considerations section
|
||||
describing what security requirements can be broken
|
||||
@ -70,7 +70,7 @@ there are four classes of security requirements:
|
||||
.Bl -hang -offset indent
|
||||
.It Em integrity
|
||||
(example: non-administrators should not modify system binaries),
|
||||
.It Em confidentiality
|
||||
.It Em confidentiality
|
||||
(example: non-administrators should not view the shadow password file),
|
||||
.It Em availability
|
||||
(example: the web server should respond to client requests in a timely
|
||||
@ -187,7 +187,7 @@ the FSA.)
|
||||
Avoid using
|
||||
.Fn strcpy .
|
||||
Instead, use
|
||||
.Fn strncpy
|
||||
.Fn strncpy
|
||||
and ensure that no more characters are copied to the destination buffer
|
||||
than it can hold.
|
||||
Do not forget to NUL-terminate the destination buffer,
|
||||
|
@ -39,7 +39,7 @@
|
||||
.In sys/param.h
|
||||
.In sys/vnode.h
|
||||
.Ft int
|
||||
.Fn VOP_ACCESS "struct vnode *vp" "int mode" "struct ucred *cred" "struct thread *td"
|
||||
.Fn VOP_ACCESS "struct vnode *vp" "int mode" "struct ucred *cred" "struct thread *td"
|
||||
.Sh DESCRIPTION
|
||||
This entry point checks the access permissions of the file against the
|
||||
given credentials.
|
||||
|
@ -56,7 +56,7 @@ the attributes of the file
|
||||
.It Ar cred
|
||||
the user credentials of the calling process
|
||||
.It Ar td
|
||||
the thread
|
||||
the thread
|
||||
.El
|
||||
.Pp
|
||||
Attributes which are not being modified by
|
||||
|
@ -65,7 +65,7 @@ start all I/O, but do not wait for it
|
||||
push data not written by filesystem syncer
|
||||
.El
|
||||
.It Ar td
|
||||
the calling thread
|
||||
the calling thread
|
||||
.El
|
||||
.Pp
|
||||
The argument
|
||||
|
@ -51,7 +51,7 @@ the type of ACL to retrieve
|
||||
a pointer to an ACL structure to receive the ACL data
|
||||
.It Fa cred
|
||||
the user credentials to use in authorizing the request
|
||||
.It Fa td
|
||||
.It Fa td
|
||||
the thread requesting the ACL
|
||||
.El
|
||||
.Pp
|
||||
|
@ -55,7 +55,7 @@ some flags ???
|
||||
.It Ar cred
|
||||
the caller's credentials
|
||||
.It Ar td
|
||||
the calling thread
|
||||
the calling thread
|
||||
.El
|
||||
.Pp
|
||||
Most filesystems do not implement this entry point.
|
||||
|
Loading…
Reference in New Issue
Block a user