diff options
| -rw-r--r-- | sys/miscfs/nullfs/null_vnops.c | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/sys/miscfs/nullfs/null_vnops.c b/sys/miscfs/nullfs/null_vnops.c index 026f04e27e3..7df52de9f75 100644 --- a/sys/miscfs/nullfs/null_vnops.c +++ b/sys/miscfs/nullfs/null_vnops.c @@ -1,4 +1,4 @@ -/* $OpenBSD: null_vnops.c,v 1.15 2002/03/14 01:27:08 millert Exp $ */ +/* $OpenBSD: null_vnops.c,v 1.16 2002/10/27 15:27:18 brad Exp $ */ /* $NetBSD: null_vnops.c,v 1.7 1996/05/10 22:51:01 jtk Exp $ */ /* @@ -54,15 +54,15 @@ * name space under a new name. In this respect, it is * similar to the loopback file system. It differs from * the loopback fs in two respects: it is implemented using - * a stackable layers techniques, and it's "null-node"s stack above + * a stackable layers techniques, and its "null-node"s stack above * all lower-layer vnodes, not just over directory vnodes. * * The null layer has two purposes. First, it serves as a demonstration - * of layering by proving a layer which does nothing. (It actually + * of layering by providing a layer which does nothing. (It actually * does everything the loopback file system does, which is slightly * more than nothing.) Second, the null layer can serve as a prototype * layer. Since it provides all necessary layer framework, - * new file system layers can be created very easily be starting + * new file system layers can be created very easily by starting * with a null layer. * * The remainder of this man page examines the null layer as a basis @@ -88,11 +88,11 @@ * pass. * * The bypass routine accepts arbitrary vnode operations for - * handling by the lower layer. It begins by examing vnode + * handling by the lower layer. It begins by examining vnode * operation arguments and replacing any null-nodes by their - * lower-layer equivlants. It then invokes the operation + * lower-layer equivalents. It then invokes the operation * on the lower layer. Finally, it replaces the null-nodes - * in the arguments and, if a vnode is return by the operation, + * in the arguments and, if a vnode is returned by the operation, * stacks a null-node on top of the returned vnode. * * Although bypass handles most operations, @@ -101,13 +101,13 @@ * Vop_lock and vop_unlock must handle any locking for the * current vnode as well as pass the lock request down. * Vop_inactive and vop_reclaim are not bypassed so that - * the can handle freeing null-layer specific data. Vop_print + * they can handle freeing null-layer specific data. Vop_print * is not bypassed to avoid excessive debugging information. - * Also, certain vnod eoperations change the locking state within + * Also, certain vnode operations change the locking state within * the operation (create, mknod, remove, link, rename, mkdir, rmdir, * and symlink). Ideally, these operations should not change the * lock state, but should be changed to let the caller of the - * function unlock them.Otherwise all intermediate vnode layers + * function unlock them. Otherwise all intermediate vnode layers * (such as union, umapfs, etc) must catch these functions * to the necessary locking at their layer * @@ -115,7 +115,7 @@ * INSTANTIATING VNODE STACKS * * Mounting associates the null layer with a lower layer, - * effect stacking two VFSes. Vnode stacks are instead + * in effect stacking two VFSes. Vnode stacks are instead * created on demand as files are accessed. * * The initial mount creates a single vnode stack for the @@ -123,7 +123,7 @@ * are created as a result of vnode operations on * this or other null vnode stacks. * - * New vnode stacks come into existance as a result of + * New vnode stacks come into existence as a result of * an operation which returns a vnode. * The bypass routine stacks a null-node above the new * vnode before returning it to the caller. @@ -145,7 +145,7 @@ * * One of the easiest ways to construct new file system layers is to make * a copy of the null layer, rename all files and variables, and - * then begin modifing the copy. Sed can be used to easily rename + * then begin modifing the copy. sed(1) can be used to easily rename * all variables. * * The umap layer is an example of a layer descended from the @@ -163,15 +163,15 @@ * * The first approach is to call the aliasing layer's bypass routine. * This method is most suitable when you wish to invoke the operation - * currently being hanldled on the lower layer. It has the advantage + * currently being handled on the lower layer. It has the advantage * that the bypass routine already must do argument mapping. * An example of this is null_getattrs in the null layer. * - * A second approach is to directly invoked vnode operations on + * A second approach is to directly invoke vnode operations on * the lower layer with the VOP_OPERATIONNAME interface. * The advantage of this method is that it is easy to invoke * arbitrary operations on the lower layer. The disadvantage - * is that vnodes arguments must be manualy mapped. + * is that vnode arguments must be manually mapped. * */ |