Typo police.

This commit is contained in:
Mike Pritchard 1997-03-04 06:20:48 +00:00
parent d18876a142
commit 3a9c9c6e42
7 changed files with 18 additions and 18 deletions

View File

@ -27,14 +27,14 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_ACCESS.9,v 1.1 1997/03/03 18:00:01 dfr Exp $
.\"
.Dd July 24, 1996
.Os
.Dt VOP_ACCESS 9
.Sh NAME
.Nm VOP_ACCESS
.Nd check access permissions of a file or unix domain socket
.Nd check access permissions of a file or Unix domain socket
.Sh SYNOPSIS
.Fd #include <sys/vnode.h>
.Ft int
@ -64,7 +64,7 @@ is a mask which can contain
.Sh LOCKS
The vnode should be locked on entry.
.Sh RETURN VALUES
If the file is accessable in the specified way, then zero is returned,
If the file is accessible in the specified way, then zero is returned,
otherwise an appropriate error code is returned.
.Sh PSEUDOCODE
.Bd -literal

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_IOCTL.9,v 1.1 1997/03/03 18:00:21 dfr Exp $
.\"
.Dd July 24, 1996
.Os
@ -39,7 +39,7 @@
.Ft int
.Fn VOP_IOCTL "struct vnode *vp" "int command" "caddr_t data" "int fflag" "struct ucred *cred" "struct proc *p"
.Sh DESCRIPTION
Manipulate a file in device dependant ways.
Manipulate a file in device dependent ways.
.Pp
Its arguments are:
.Bl -tag -width command

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_LOCK.9,v 1.1 1997/03/03 18:00:25 dfr Exp $
.\"
.Dd July 24, 1996
.Os
@ -52,7 +52,7 @@ The arguments are:
the vnode being locked or unlocked
.El
.Pp
These calls are used to serialise access to the filesystem, for
These calls are used to serialize access to the filesystem, for
instance to prevent two writes to the same file from happening at the
same time.
.Sh RETURN VALUES

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_LOOKUP.9,v 1.1 1997/03/03 18:00:26 dfr Exp $
.\"
.Dd July 24, 1996
.Os FreeBSD
@ -170,7 +170,7 @@ vop_lookup(struct vnode *dvp,
struct vnode *vp = NULL;
/*
* Check accessiblity of directory.
* Check accessibility of directory.
*/
if (dvp->v_type != VDIR)
return ENOTDIR;
@ -184,7 +184,7 @@ vop_lookup(struct vnode *dvp,
return (EROFS);
/*
* Check name cachec for directory/name pair. This returns ENOENT
* Check name cache for directory/name pair. This returns ENOENT
* if the name is known not to exist, -1 if the name was found, or
* zero if not.
*/

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_PATHCONF.9,v 1.1 1997/03/03 18:00:29 dfr Exp $
.\"
.Dd July 24, 1996
.Os
@ -75,7 +75,7 @@ are truncated.
.Sh RETURN VALUES
If
.Fa name
is recognised,
is recognized,
.Fa *retval
is set to the specified value and zero is returned, otherwise
.Dv EINVAL

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_RDWR.9,v 1.1 1997/03/03 18:00:32 dfr Exp $
.\"
.Dd July 24, 1996
.Os
@ -66,14 +66,14 @@ do I/O as atomic unit
.It Dv IO_APPEND
append write to end
.It Dv IO_SYNC
do I/O syncronously
do I/O synchronously
.It Dv IO_NODELOCKED
underlying node already locked
.It Dv IO_NDELAY
.Dv FNDELAY
flag set in file table
.It Dv IO_VMIO
data alread in VMIO space
data already in VMIO space
.El
.Sh LOCKS
The file should be locked on entry and will still be locked on exit.

View File

@ -26,7 +26,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id$
.\" $Id: VOP_RENAME.9,v 1.1 1997/03/03 18:00:38 dfr Exp $
.\"
.Dd July 24, 1996
.Os
@ -47,7 +47,7 @@ Its arguments are:
.It Ar fdvp
the vnode of the old parent directory
.It Ar fvp
the vnode of the file to be renameed
the vnode of the file to be renamed
.It Ar fcnp
pathname information about the file's current name
.It Ar tdvp
@ -161,7 +161,7 @@ vop_rename(struct vnode *fdvp, struct vnode *fvp, struct componentname *fcnp,
/*
* If ".." must be changed (ie the directory gets a new
* parent) then the source directory must not be in the
* directory heirarchy above the target, as this would
* directory hierarchy above the target, as this would
* orphan everything below the source directory. Also
* the user must have write permission in the source so
* as to be able to change "..".