diff options
Diffstat (limited to 'sys/fs')
| -rw-r--r-- | sys/fs/nullfs/null_vnops.c | 6 | ||||
| -rw-r--r-- | sys/fs/procfs/procfs_mem.c | 4 | ||||
| -rw-r--r-- | sys/fs/unionfs/union_vfsops.c | 4 |
3 files changed, 7 insertions, 7 deletions
diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c index 9575487..877fc37 100644 --- a/sys/fs/nullfs/null_vnops.c +++ b/sys/fs/nullfs/null_vnops.c @@ -37,11 +37,11 @@ * * Ancestors: * @(#)lofs_vnops.c 1.2 (Berkeley) 6/18/92 - * $Id: null_vnops.c,v 1.25 1997/10/21 21:01:34 roberto Exp $ + * $Id: null_vnops.c,v 1.26 1998/01/31 07:23:13 eivind Exp $ * ...and... * @(#)null_vnodeops.c 1.20 92/07/07 UCLA Ficus project * - * $Id: null_vnops.c,v 1.25 1997/10/21 21:01:34 roberto Exp $ + * $Id: null_vnops.c,v 1.26 1998/01/31 07:23:13 eivind Exp $ */ /* @@ -53,7 +53,7 @@ * 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 diff --git a/sys/fs/procfs/procfs_mem.c b/sys/fs/procfs/procfs_mem.c index 5625678..5184f47 100644 --- a/sys/fs/procfs/procfs_mem.c +++ b/sys/fs/procfs/procfs_mem.c @@ -37,7 +37,7 @@ * * @(#)procfs_mem.c 8.5 (Berkeley) 6/15/94 * - * $Id: procfs_mem.c,v 1.29 1998/02/04 22:32:49 eivind Exp $ + * $Id: procfs_mem.c,v 1.30 1998/02/06 12:13:41 eivind Exp $ */ /* @@ -299,7 +299,7 @@ procfs_domem(curp, p, pfs, uio) /* * Given process (p), find the vnode from which - * it's text segment is being executed. + * its text segment is being executed. * * It would be nice to grab this information from * the VM system, however, there is no sure-fire diff --git a/sys/fs/unionfs/union_vfsops.c b/sys/fs/unionfs/union_vfsops.c index 156108d..2f90d05 100644 --- a/sys/fs/unionfs/union_vfsops.c +++ b/sys/fs/unionfs/union_vfsops.c @@ -35,7 +35,7 @@ * SUCH DAMAGE. * * @(#)union_vfsops.c 8.20 (Berkeley) 5/20/95 - * $Id: union_vfsops.c,v 1.26 1998/02/10 08:04:31 kato Exp $ + * $Id: union_vfsops.c,v 1.27 1998/03/01 22:46:25 msmith Exp $ */ /* @@ -237,7 +237,7 @@ union_mount(mp, path, data, ndp, p) /* * Copy in the upper layer's RDONLY flag. This is for the benefit * of lookup() which explicitly checks the flag, rather than asking - * the filesystem for it's own opinion. This means, that an update + * the filesystem for its own opinion. This means, that an update * mount of the underlying filesystem to go from rdonly to rdwr * will leave the unioned view as read-only. */ |
