o The revenge of the mdoc(7) police:

- These pages abused Ar macro (they should have used Fa).
   - NULL and other numeric constants should be marked with Dv.
   - VOP_* in the ERRORS section for the EOPNOTSUPP entry should be marked
     with Fn.

Submitted by:	ru
This commit is contained in:
rwatson 2001-03-16 17:42:38 +00:00
parent b796adf323
commit ce67b919f8
3 changed files with 38 additions and 28 deletions

View File

@ -1,5 +1,5 @@
.\"-
.\" Copyright (c) 1999 Robert N. M. Watson
.\" Copyright (c) 1999, 2000, 2001 Robert N. M. Watson
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD$
.\" $FreeBSD$
.\"
.Dd December 23, 1999
.Os
@ -43,24 +43,25 @@ file or directory.
.Pp
Its arguments are:
.Bl -tag -width type
.It Ar vp
.It Fa vp
the vnode of the file or directory
.It Ar type
.It Fa type
the type of ACL to retrieve
.It Ar aclp
.It Fa aclp
a pointer to an ACL structure to receive the ACL data
.It Ar cred
.It Fa cred
the user credentials to use in authorizing the request
.It Ar p
.It Fa p
the process requesting the ACL
.El
.Pp
The
.Fa cred
pointer may be NULL to indicate that access control checks are not to be
performed, of possible. This cred setting might be used to allow the
kernel to authorize ACL retrieval that the active process might not be
permitted to do.
pointer may be
.Dv NULL
to indicate that access control checks are not to be performed, of possible.
This cred setting might be used to allow the kernel to authorize ACL
retrieval that the active process might not be permitted to do.
.Pp
The vnode ACL interface defines the syntax, and not semantics, of file and
directory ACL interfaces. More information about ACL management in kernel
@ -82,7 +83,8 @@ Permission denied
.It Bq Er ENOMEM
Insufficient memory available to fulfill request
.It Bq Er EOPNOTSUPP
The file system does not support VOP_GETACL
The file system does not support
.Fn VOP_GETACL
.El
.Sh SEE ALSO
.Xr acl 9 ,

View File

@ -1,5 +1,5 @@
.\"-
.\" Copyright (c) 1999 Robert N. M. Watson
.\" Copyright (c) 1999, 2000, 2001 Robert N. M. Watson
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD$
.\" $FreeBSD$
.\"
.Dd December 23, 1999
.Os
@ -43,28 +43,31 @@ or directory.
.Pp
Its arguments are:
.Bl -tag -width type
.It Ar vp
.It Fa vp
the vnode of the file or directory
.It Ar type
.It Fa type
the type of ACL to set
.It Ar aclp
.It Fa aclp
a pointer to an ACL structure from which to retrieve the ACL data
.It Ar cred
.It Fa cred
the user credentials to use in authorizing the request
.It Ar p
.It Fa p
the process setting the ACL
.El
.Pp
The
.Fa aclp
pointer may be NULL to indicate that the specified ACL should be deleted.
pointer may be
.Dv NULL
to indicate that the specified ACL should be deleted.
.Pp
The
.Fa cred
pointer may be NULL to indicate that access control checks are not to be
performed, of possible. This cred setting might be used to allow the
kernel to authorize extended attribute changes that the active process might
not be permitted to make.
pointer may be
.Dv NULL
to indicate that access control checks are not to be performed, of possible.
This cred setting might be used to allow the kernel to authorize extended
attribute changes that the active process might not be permitted to make.
.Pp
The vnode ACL interface defines the syntax, and not semantics, of file and
directory ACL interfaces. More information about ACL management in kernel
@ -84,7 +87,8 @@ Permission denied
.It Bq Er ENOMEM
Insufficient memory available to fulfill request
.It Bq Er EOPNOTSUPP
The file system does not support VOP_SETACL
The file system does not support
.Fn VOP_SETACL
.It Bq Er ENOSPC
The file system is out of space
.It Bq Er EROFS

View File

@ -48,7 +48,9 @@ If the same name is present in multiple namespaces, the extended attributes
associated with the names are stored and manipulated independently.
The following two namespaces are defined universally, although individual
file systems may implement additional namespaces, or not implement
these namespaces: EXTATTR_NAMESPACE_USER, EXTATTR_NAMESPACE_SYSTEM.
these namespaces:
.Dv EXTATTR_NAMESPACE_USER ,
.Dv EXTATTR_NAMESPACE_SYSTEM .
The semantics of these attributes are intended to be as follows: user
attribute data is protected according the the normal discretionary
and mandatory protections associated with the data in the file or
@ -88,5 +90,7 @@ the total size of the attribute, or indicate that the buffer space provided
by the caller is insufficient to hold all available data.
In addition, the interface does not provide a mechanism to retrieve
the current set of available attributes; it has been suggested that
providing a NULL attribute name should cause a list of defined attributes
for the passed file or directory, but this is not currently implemented.
providing a
.Dv NULL
attribute name should cause a list of defined attributes for the passed file
or directory, but this is not currently implemented.