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

Fix various typos and mdoc style issues.

Browse Source 
Reviewed by:	rwatson
This commit is contained in:
Mike Pritchard 2000-01-29 04:18:51 +00:00
parent ea5cc7f114
commit c32381ada4
22 changed files with 200 additions and 108 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
lib/libc/posix1e/acl.3
View File

@ -29,12 +29,15 @@
.Dt ACL 3
.Os FreeBSD 4.0
.Sh NAME
.Nm acl \- introduction to the POSIX.1e ACL security API
.Nm acl
.Nd introduction to the POSIX.1e ACL security API
.Sh SYNOPSIS
.Fd #include <sys/types.h>
.Fd #include <sys/acl.h>
.Sh DESCRIPTION
As shipped, FreeBSD 4.0 permits file systems to export
As shipped,
.Fx 4.0
permits file systems to export
Access Control Lists via the VFS, and provides a library for userland
access to and manipulation of these ACLs, but support for ACLs is not
provided by any file systems shipped in the base operating system.
@ -50,7 +53,7 @@ POSIX.1e describes a set of ACL manipulation routines to manage the
contents of ACLs, as well as their relationships with files. This
manipulation library is not currently implemented in FreeBSD, although
a third party library was under development at the time this document
was written. There is a general concensus that the POSIX.1e manipulation
was written. There is a general consensus that the POSIX.1e manipulation
routines are ambiguously defined in the specification, and don't meet the
needs of most applications. For the time being, applications may
directly manipulate the ACL structures, defined in acl.h, although the
@ -109,7 +112,7 @@ and may be used to duplicate an ACL structure.
.Fn acl_set_fd ,
.Fn acl_set_fd_np
These funtions are described in
These functions are described in
.Xr acl_set 3 ,
and may be used to assign an ACL to a file system object.
@ -143,9 +146,11 @@ functionality described in POSIX.1. These additional labels provide
fine-grained discretionary access control, fine-grained capabilities,
and labels necessary for mandatory access control. POSIX.2c describes
a set of userland utilities for manipulating these labels. These userland
utilities are not bundled with FreeBSD 4.0 so as to discourage their
utilities are not bundled with
.Fx 4.0
so as to discourage their
use in the short term.
.Sh FILES
.\" .Sh FILES
.Sh SEE ALSO
.Xr acl 3 ,
.Xr acl_dup 3 ,
@ -159,12 +164,16 @@ use in the short term.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

12
lib/libc/posix1e/acl_delete.3
View File

@ -66,7 +66,7 @@ is set to indicate the error.
If any of the following conditions occur, these functions shall return -1
and set
.Va errno
to teh corresponding value:
to the corresponding value:
.Bl -tag -width Er
.It Bq Er EACCES
Search permission is denied for a component of the path prefix, or the
@ -108,12 +108,16 @@ The file system is read-only.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

14
lib/libc/posix1e/acl_dup.3
View File

@ -42,8 +42,8 @@ The
function returns a pointer to a copy of the ACL pointed to by the argument
.Va acl .
This function may cause memory to be allocated. Teh caller should free any
releaseable memory, when the new ACL is no longer required, by calling
This function may cause memory to be allocated. The caller should free any
releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void*)acl_t
@ -89,12 +89,16 @@ system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libc/posix1e/acl_free.3
View File

@ -73,12 +73,16 @@ argument is invalid.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libc/posix1e/acl_from_text.3
View File

@ -90,12 +90,16 @@ hardware or system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

13
lib/libc/posix1e/acl_get.3
View File

@ -29,7 +29,6 @@
.Dt ACL_GET 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_get_file ,
.Nm acl_get_fd ,
.Nm acl_get_fd_np
@ -63,7 +62,7 @@ is a non-portable form of
that allows the retrieval of any type of ACL from a file descriptor.
This function may cause memory to be allocated. The caller should free
any releaseable memory, when the new ACL is no longer required, by calling
any releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void *)acl_t
@ -123,12 +122,16 @@ The file system does not support ACL retrieval.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

14
lib/libc/posix1e/acl_init.3
View File

@ -48,8 +48,8 @@ storage allocated to contain the ACL is freed by a call to
When the area is first allocated, it shall contain an an ACL that contains
no ACL entries.
This function may cause memory to be allocated. Teh caller should free any
releaseable memory, when the new ACL is no longer required, by calling
This function may cause memory to be allocated. The caller should free any
releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void*)acl_t
@ -88,12 +88,16 @@ system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

13
lib/libc/posix1e/acl_set.3
View File

@ -29,7 +29,6 @@
.Dt ACL_SET 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_set_file ,
.Nm acl_set_fd ,
.Nm acl_set_fd_np
@ -65,7 +64,7 @@ allows the setting of ACLs of any type.
FreeBSD's support for POSIX.1e interfaces and features is still under
development at this time.
.Sh RETURN VALUES
Upon successfull completion, the function shall return a value of zero.
Upon successful completion, the function shall return a value of zero.
Otherwise, a value of -1 shall be returned and
.Va errno
shall be set to indicate the error.
@ -116,12 +115,16 @@ read-only.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libc/posix1e/acl_to_text.3
View File

@ -46,12 +46,12 @@ into a NULL terminated character string. If the pointer
is not NULL, then the function shall return the length of the string (not
including the NULL terminator) in the location pointed to by
.Va len_p .
Teh format of the text string returned by
The format of the text string returned by
.Fn acl_to_text
shall be the POSIX.1e long ACL form.
This function allocates any memory necessary to contain the string and
returns a pointer to the string. The caller should free any releaseable
returns a pointer to the string. The caller should free any releasable
memory, when the new string is no longer required, by calling
.Xr acl_free 3
with the
@ -100,9 +100,11 @@ of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

11
lib/libc/posix1e/acl_valid.3
View File

@ -29,7 +29,6 @@
.Dt ACL_VALID 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_valid ,
.Nm acl_valid_fd_np ,
.Nm acl_valid_file_np
@ -70,7 +69,7 @@ shall contain at most on ACL_MASK entry.
The qualifier field shall be unique among all entries of
the same POSIX.1e ACL facility defined tag type. The
tag type field shall contain valid values including any
implementatino-defined values. Validation of the values
implementation-defined values. Validation of the values
of the qualifier field is implementation-defined.
.Ed
@ -82,7 +81,7 @@ non-portable validation functions will not.
FreeBSD's support for POSIX.1e interfaces and features is still under
development at this time.
.Sh RETURN VALUES
Upon successfull completion, the function shall return a value of zero.
Upon successful completion, the function shall return a value of zero.
Otherwise, a value of -1 shall be returned and
.Va errno
shall be set to indicate the error.
@ -134,9 +133,11 @@ of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

20
lib/libc/posix1e/posix1e.3
View File

@ -29,7 +29,8 @@
.Dt POSIX1E 3
.Os FreeBSD 4.0
.Sh NAME
.Nm posix1e \- introduction to the POSIX.1e security API
.Nm posix1e
.Nd introduction to the POSIX.1e security API
.Sh SYNOPSIS
.Fd #include <sys/acl.h>
.Fd #include <sys/audit.h>
@ -37,7 +38,7 @@
.Fd #include <sys/mac.h>
.Sh DESCRIPTION
The IEEE POSIX.1e specification never left draft form, but the interfaces
it describes are now widely used despite inherrent limitations. Currently,
it describes are now widely used despite inherent limitations. Currently,
only a few of the interfaces and features are implemented in FreeBSD,
although efforts are underway to complete the integration at this time.
@ -71,7 +72,9 @@ functionality described in POSIX.1. These additional labels provide
fine-grained discretionary access control, fine-grained capabilities,
and labels necessary for mandatory access control. POSIX.2c describes
a set of userland utilities for manipulating these labels. These userland
utilities are not bundled with FreeBSD 4.0 so as to discourage their
utilities are not bundled with
.Fx 4.0
so as to discourage their
use in the short term.
.Sh FILES
.Sh SEE ALSO
@ -81,12 +84,17 @@ use in the short term.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson, Ilmar S Habibulin
.An Robert N M Watson ,
.An Ilmar S Habibulin
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

27
lib/libposix1e/acl.3
View File

@ -29,12 +29,15 @@
.Dt ACL 3
.Os FreeBSD 4.0
.Sh NAME
.Nm acl \- introduction to the POSIX.1e ACL security API
.Nm acl
.Nd introduction to the POSIX.1e ACL security API
.Sh SYNOPSIS
.Fd #include <sys/types.h>
.Fd #include <sys/acl.h>
.Sh DESCRIPTION
As shipped, FreeBSD 4.0 permits file systems to export
As shipped,
.Fx 4.0
permits file systems to export
Access Control Lists via the VFS, and provides a library for userland
access to and manipulation of these ACLs, but support for ACLs is not
provided by any file systems shipped in the base operating system.
@ -50,7 +53,7 @@ POSIX.1e describes a set of ACL manipulation routines to manage the
contents of ACLs, as well as their relationships with files. This
manipulation library is not currently implemented in FreeBSD, although
a third party library was under development at the time this document
was written. There is a general concensus that the POSIX.1e manipulation
was written. There is a general consensus that the POSIX.1e manipulation
routines are ambiguously defined in the specification, and don't meet the
needs of most applications. For the time being, applications may
directly manipulate the ACL structures, defined in acl.h, although the
@ -109,7 +112,7 @@ and may be used to duplicate an ACL structure.
.Fn acl_set_fd ,
.Fn acl_set_fd_np
These funtions are described in
These functions are described in
.Xr acl_set 3 ,
and may be used to assign an ACL to a file system object.
@ -143,9 +146,11 @@ functionality described in POSIX.1. These additional labels provide
fine-grained discretionary access control, fine-grained capabilities,
and labels necessary for mandatory access control. POSIX.2c describes
a set of userland utilities for manipulating these labels. These userland
utilities are not bundled with FreeBSD 4.0 so as to discourage their
utilities are not bundled with
.Fx 4.0
so as to discourage their
use in the short term.
.Sh FILES
.\" .Sh FILES
.Sh SEE ALSO
.Xr acl 3 ,
.Xr acl_dup 3 ,
@ -159,12 +164,16 @@ use in the short term.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

12
lib/libposix1e/acl_delete.3
View File

@ -66,7 +66,7 @@ is set to indicate the error.
If any of the following conditions occur, these functions shall return -1
and set
.Va errno
to teh corresponding value:
to the corresponding value:
.Bl -tag -width Er
.It Bq Er EACCES
Search permission is denied for a component of the path prefix, or the
@ -108,12 +108,16 @@ The file system is read-only.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

14
lib/libposix1e/acl_dup.3
View File

@ -42,8 +42,8 @@ The
function returns a pointer to a copy of the ACL pointed to by the argument
.Va acl .
This function may cause memory to be allocated. Teh caller should free any
releaseable memory, when the new ACL is no longer required, by calling
This function may cause memory to be allocated. The caller should free any
releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void*)acl_t
@ -89,12 +89,16 @@ system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libposix1e/acl_free.3
View File

@ -73,12 +73,16 @@ argument is invalid.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libposix1e/acl_from_text.3
View File

@ -90,12 +90,16 @@ hardware or system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

13
lib/libposix1e/acl_get.3
View File

@ -29,7 +29,6 @@
.Dt ACL_GET 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_get_file ,
.Nm acl_get_fd ,
.Nm acl_get_fd_np
@ -63,7 +62,7 @@ is a non-portable form of
that allows the retrieval of any type of ACL from a file descriptor.
This function may cause memory to be allocated. The caller should free
any releaseable memory, when the new ACL is no longer required, by calling
any releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void *)acl_t
@ -123,12 +122,16 @@ The file system does not support ACL retrieval.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

14
lib/libposix1e/acl_init.3
View File

@ -48,8 +48,8 @@ storage allocated to contain the ACL is freed by a call to
When the area is first allocated, it shall contain an an ACL that contains
no ACL entries.
This function may cause memory to be allocated. Teh caller should free any
releaseable memory, when the new ACL is no longer required, by calling
This function may cause memory to be allocated. The caller should free any
releasable memory, when the new ACL is no longer required, by calling
.Xr acl_free 3
with the
.Va (void*)acl_t
@ -88,12 +88,16 @@ system-imposed memory management constraints.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

13
lib/libposix1e/acl_set.3
View File

@ -29,7 +29,6 @@
.Dt ACL_SET 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_set_file ,
.Nm acl_set_fd ,
.Nm acl_set_fd_np
@ -65,7 +64,7 @@ allows the setting of ACLs of any type.
FreeBSD's support for POSIX.1e interfaces and features is still under
development at this time.
.Sh RETURN VALUES
Upon successfull completion, the function shall return a value of zero.
Upon successful completion, the function shall return a value of zero.
Otherwise, a value of -1 shall be returned and
.Va errno
shall be set to indicate the error.
@ -116,12 +115,16 @@ read-only.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

10
lib/libposix1e/acl_to_text.3
View File

@ -46,12 +46,12 @@ into a NULL terminated character string. If the pointer
is not NULL, then the function shall return the length of the string (not
including the NULL terminator) in the location pointed to by
.Va len_p .
Teh format of the text string returned by
The format of the text string returned by
.Fn acl_to_text
shall be the POSIX.1e long ACL form.
This function allocates any memory necessary to contain the string and
returns a pointer to the string. The caller should free any releaseable
returns a pointer to the string. The caller should free any releasable
memory, when the new string is no longer required, by calling
.Xr acl_free 3
with the
@ -100,9 +100,11 @@ of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

11
lib/libposix1e/acl_valid.3
View File

@ -29,7 +29,6 @@
.Dt ACL_VALID 3
.Os FreeBSD 4.0
.Sh NAME
.Fd int
.Nm acl_valid ,
.Nm acl_valid_fd_np ,
.Nm acl_valid_file_np
@ -70,7 +69,7 @@ shall contain at most on ACL_MASK entry.
The qualifier field shall be unique among all entries of
the same POSIX.1e ACL facility defined tag type. The
tag type field shall contain valid values including any
implementatino-defined values. Validation of the values
implementation-defined values. Validation of the values
of the qualifier field is implementation-defined.
.Ed
@ -82,7 +81,7 @@ non-portable validation functions will not.
FreeBSD's support for POSIX.1e interfaces and features is still under
development at this time.
.Sh RETURN VALUES
Upon successfull completion, the function shall return a value of zero.
Upon successful completion, the function shall return a value of zero.
Otherwise, a value of -1 shall be returned and
.Va errno
shall be set to indicate the error.
@ -134,9 +133,11 @@ of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson
.An Robert N M Watson
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,

20
lib/libposix1e/posix1e.3
View File

@ -29,7 +29,8 @@
.Dt POSIX1E 3
.Os FreeBSD 4.0
.Sh NAME
.Nm posix1e \- introduction to the POSIX.1e security API
.Nm posix1e
.Nd introduction to the POSIX.1e security API
.Sh SYNOPSIS
.Fd #include <sys/acl.h>
.Fd #include <sys/audit.h>
@ -37,7 +38,7 @@
.Fd #include <sys/mac.h>
.Sh DESCRIPTION
The IEEE POSIX.1e specification never left draft form, but the interfaces
it describes are now widely used despite inherrent limitations. Currently,
it describes are now widely used despite inherent limitations. Currently,
only a few of the interfaces and features are implemented in FreeBSD,
although efforts are underway to complete the integration at this time.
@ -71,7 +72,9 @@ functionality described in POSIX.1. These additional labels provide
fine-grained discretionary access control, fine-grained capabilities,
and labels necessary for mandatory access control. POSIX.2c describes
a set of userland utilities for manipulating these labels. These userland
utilities are not bundled with FreeBSD 4.0 so as to discourage their
utilities are not bundled with
.Fx 4.0
so as to discourage their
use in the short term.
.Sh FILES
.Sh SEE ALSO
@ -81,12 +84,17 @@ use in the short term.
.Sh STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
of the draft continues on the cross-platform POSIX.1e implementation
mailing list. To join this list, see the FreeBSD POSIX.1e implementation
mailing list. To join this list, see the
.Fx
POSIX.1e implementation
page for more information.
.Sh HISTORY
POSIX.1e support was introduced in FreeBSD 4.0, and development continues.
POSIX.1e support was introduced in
.Fx 4.0 ,
and development continues.
.Sh AUTHORS
Robert N M Watson, Ilmar S Habibulin
.An Robert N M Watson ,
.An Ilmar S Habibulin
.Sh BUGS
These features are not yet fully implemented. In particular, the shipped
version of UFS/FFS does not support storage of additional security labels,