diff options
Diffstat (limited to 'share/man/man9')
48 files changed, 180 insertions, 180 deletions
diff --git a/share/man/man9/VFS.9 b/share/man/man9/VFS.9 index 5a8f008..dc46c5c 100644 --- a/share/man/man9/VFS.9 +++ b/share/man/man9/VFS.9 @@ -33,11 +33,11 @@ .Dt VFS 9 .Sh NAME .Nm VFS -.Nd kernel interface to filesystems +.Nd kernel interface to file systems .Sh DESCRIPTION -Calls used to set or query filesystems for settings or information. +Calls used to set or query file systems for settings or information. .Pp -Filesystems that don't implement a VFS operation should use the appropriate +File systems that don't implement a VFS operation should use the appropriate .Fa vfs_std function from .Pa src/sys/kern/vfs_default.c diff --git a/share/man/man9/VFS_CHECKEXP.9 b/share/man/man9/VFS_CHECKEXP.9 index 3295972..a0ba24f 100644 --- a/share/man/man9/VFS_CHECKEXP.9 +++ b/share/man/man9/VFS_CHECKEXP.9 @@ -29,7 +29,7 @@ .Dt VFS_CHECKEXP 9 .Sh NAME .Nm VFS_CHECKEXP -.Nd check if a filesystem is exported to a client +.Nd check if a file system is exported to a client .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -51,21 +51,21 @@ Return parameter for the export flags for this client. Return parameter for the anonymous credentials for this client. .El .Pp -This should be called on a filesystem's mount structure to determine if it +This should be called on a file system's mount structure to determine if it is exported to a client whose address is contained in .Fa nam . .Pp It is generally called before .Xr VFS_FHTOVP 9 -to validate that a client has access to the filesystem. +to validate that a client has access to the file system. .Pp -The filesystem should call +The file system should call .Xr vfs_export_lookup 9 with the address of an appropriate .Dv netexport structure and the address of the client, .Fa nam , -to verify that the client can access this filesystem. +to verify that the client can access this file system. .Sh RETURN VALUES The export flags and anonymous credentials specific to the client (returned by diff --git a/share/man/man9/VFS_FHTOVP.9 b/share/man/man9/VFS_FHTOVP.9 index 5eb5867..a5d4432 100644 --- a/share/man/man9/VFS_FHTOVP.9 +++ b/share/man/man9/VFS_FHTOVP.9 @@ -46,19 +46,19 @@ This is used by the NFS server to turn an NFS filehandle into a vnode. Its arguments are: .Bl -tag -width vpp .It Ar mp -The filesystem. +The file system. .It Ar fhp The filehandle to convert. .It Ar vpp Return parameter for the new locked vnode. .El .Pp -The contents of the filehandle are defined by the filesystem and are +The contents of the filehandle are defined by the file system and are not examined by any other part of the system. It should contain -enough information to uniquely identify a file within the filesystem -as well as noticing when a file has been removed and the filesystem +enough information to uniquely identify a file within the file system +as well as noticing when a file has been removed and the file system resources have been reused for a new file. For instance, UFS -filesystem stores the inode number and inode generation counter in its +file system stores the inode number and inode generation counter in its filehandle. .Pp A call to this function should generally be preceded by a call to diff --git a/share/man/man9/VFS_INIT.9 b/share/man/man9/VFS_INIT.9 index cadfe1c..0e48bd7 100644 --- a/share/man/man9/VFS_INIT.9 +++ b/share/man/man9/VFS_INIT.9 @@ -33,7 +33,7 @@ .Dt VFS_INIT 9 .Sh NAME .Nm VFS_INIT -.Nd initialize a filesystem +.Nd initialize a file system .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,10 +41,10 @@ .Ft int .Fn VFS_INIT .Sh DESCRIPTION -This function is called once to allow a filesystem to initialize any +This function is called once to allow a file system to initialize any global data structures that it might have. It is either called when -the operating system boots or, for dynamically loaded filesystems, -when the kernel module containing the filesystem is loaded. +the operating system boots or, for dynamically loaded file systems, +when the kernel module containing the file system is loaded. .Sh SEE ALSO .Xr VFS 9 , .Xr vnode 9 diff --git a/share/man/man9/VFS_MOUNT.9 b/share/man/man9/VFS_MOUNT.9 index 8fd2ac4..be00b68 100644 --- a/share/man/man9/VFS_MOUNT.9 +++ b/share/man/man9/VFS_MOUNT.9 @@ -33,7 +33,7 @@ .Dt VFS_MOUNT 9 .Sh NAME .Nm VFS_MOUNT -.Nd mount a filesystem +.Nd mount a file system .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,44 +41,44 @@ .Ft int .Fn VFS_MOUNT "struct mount *mp" "char *path" "caddr_t data" "struct nameidata *ndp" "struct thread *td" .Sh DESCRIPTION -Mount a filesystem into the system's namespace. +Mount a file system into the system's namespace. .Pp Its arguments are: .Bl -tag -width data .It Ar mp -Structure representing the filesystem. +Structure representing the file system. .It Ar path -Pathname where the filesystem is being mounted. +Pathname where the file system is being mounted. .It Ar data -Filesystem specific data. This should be read into the kernel using +File system specific data. This should be read into the kernel using .Xr copyin 9 . .It Ar ndp Contains the result of a .Xr namei 9 call on the pathname of the mountpoint. .It Ar td -Thread which is mounting the filesystem. +Thread which is mounting the file system. .El .Pp -This is called both to mount new filesystems and to change the -attributes of an existing filesystem. If the +This is called both to mount new file systems and to change the +attributes of an existing file system. If the .Dv MNT_UPDATE flag is set in .Fa mp->mnt_flag -then the filesystem should update its internal state from the value of +then the file system should update its internal state from the value of .Fa mp->mnt_flag . -This can be used, for instance, to convert a read-only filesystem to +This can be used, for instance, to convert a read-only file system to read-write. It is also used by .Xr mountd 8 -to update the NFS export information for the filesystem. +to update the NFS export information for the file system. .Pp If the .Dv MNT_UPDATE -flag is not specified, then this is a newly mounted filesystem. The -filesystem code should allocate and initialize +flag is not specified, then this is a newly mounted file system. The +file system code should allocate and initialize any private data needed to represent -the filesystem (it can use the +the file system (it can use the .Fa mp->mnt_data field to store this information). .Sh SEE ALSO diff --git a/share/man/man9/VFS_QUOTACTL.9 b/share/man/man9/VFS_QUOTACTL.9 index 3350b1a..56bbf85 100644 --- a/share/man/man9/VFS_QUOTACTL.9 +++ b/share/man/man9/VFS_QUOTACTL.9 @@ -33,7 +33,7 @@ .Dt VFS_QUOTACTL 9 .Sh NAME .Nm VFS_QUOTACTL -.Nd manipulate filesystem quotas +.Nd manipulate file system quotas .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,7 +41,7 @@ .Ft int .Fn VFS_QUOTACTL "struct mount *mp" "int cmds" "uid_t uid" "caddr_t arg" "struct thread *td" .Sh DESCRIPTION -Implement filesystem quotas. See +Implement file system quotas. See .Xr quotactl 2 for a description of the arguments. .Sh SEE ALSO diff --git a/share/man/man9/VFS_ROOT.9 b/share/man/man9/VFS_ROOT.9 index a4fc77c..fbcc6b7 100644 --- a/share/man/man9/VFS_ROOT.9 +++ b/share/man/man9/VFS_ROOT.9 @@ -33,7 +33,7 @@ .Dt VFS_ROOT 9 .Sh NAME .Nm VFS_ROOT -.Nd return the root vnode of a filesystem +.Nd return the root vnode of a file system .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,12 +41,12 @@ .Ft int .Fn VFS_ROOT "struct mount *mp" "struct vnode **vpp" .Sh DESCRIPTION -Return a locked vnode for the root directory of the filesystem. +Return a locked vnode for the root directory of the file system. .Pp Its arguments are: .Bl -tag -width vpp .It Ar mp -The filesystem. +The file system. .It Ar vpp Return parameter for the root vnode. .El diff --git a/share/man/man9/VFS_SET.9 b/share/man/man9/VFS_SET.9 index 856eace..0383c8d 100644 --- a/share/man/man9/VFS_SET.9 +++ b/share/man/man9/VFS_SET.9 @@ -31,7 +31,7 @@ .Os .Sh NAME .Nm VFS_SET -.Nd set up loadable filesystem +.Nd set up loadable file system .Vt vfsconf .Sh SYNOPSIS .In sys/param.h diff --git a/share/man/man9/VFS_START.9 b/share/man/man9/VFS_START.9 index 64ab8c7..5cec4e3 100644 --- a/share/man/man9/VFS_START.9 +++ b/share/man/man9/VFS_START.9 @@ -33,7 +33,7 @@ .Dt VFS_START 9 .Sh NAME .Nm VFS_START -.Nd make a filesystem operational +.Nd make a file system operational .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -43,15 +43,15 @@ .Sh DESCRIPTION This is called after .Xr VFS_MOUNT 9 -and before the first access to the filesystem. +and before the first access to the file system. Its arguments are: .Bl -tag -width flags .It Ar mp -The filesystem. +The file system. .It Ar flags ?? .It Ar td -Thread which is starting the filesystem. +Thread which is starting the file system. .El .Sh SEE ALSO .Xr VFS 9 , diff --git a/share/man/man9/VFS_STATFS.9 b/share/man/man9/VFS_STATFS.9 index 9a157c6..8ab457f 100644 --- a/share/man/man9/VFS_STATFS.9 +++ b/share/man/man9/VFS_STATFS.9 @@ -33,7 +33,7 @@ .Dt VFS_STATFS 9 .Sh NAME .Nm VFS_STATFS -.Nd return filesystem status +.Nd return file system status .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,17 +41,17 @@ .Ft int .Fn VFS_STATFS "struct mount *mp" "struct statfs *sbp" "struct thread *td" .Sh DESCRIPTION -This call returns various pieces of information about the filesystem, +This call returns various pieces of information about the file system, including recommended I/O sizes, free space, free inodes, etc. .Pp Its arguments are: .Bl -tag -width sbp .It Ar mp -The filesystem. +The file system. .It Ar sbp -Return parameter for the filesystem's status. +Return parameter for the file system's status. .It Ar td -The thread which is querying the filesystem. +The thread which is querying the file system. .El .Sh SEE ALSO .Xr VFS 9 , diff --git a/share/man/man9/VFS_SYNC.9 b/share/man/man9/VFS_SYNC.9 index 2543471..d32cc44 100644 --- a/share/man/man9/VFS_SYNC.9 +++ b/share/man/man9/VFS_SYNC.9 @@ -41,12 +41,12 @@ .Ft int .Fn VFS_SYNC "struct mount *mp" "int waitfor" "struct ucred *cred" "struct thread *td" .Sh DESCRIPTION -This writes out all unwritten data in a filesystem. +This writes out all unwritten data in a file system. .Pp Its arguments are: .Bl -tag -width waitfor .It Ar mp -The filesystem. +The file system. .It Ar waitfor Whether the function should wait for I/O to complete. Possible values are: @@ -56,7 +56,7 @@ synchronously wait for I/O to complete .It Dv MNT_NOWAIT start all I/O, but do not wait for it .It Dv MNT_LAZY -push data not written by filesystem syncer +push data not written by file system syncer .El .It Ar cred The caller's credentials. @@ -66,7 +66,7 @@ The calling thread. .Pp This would normally call .Xr VOP_FSYNC 9 -for all the vnodes in the filesystem. +for all the vnodes in the file system. .Sh SEE ALSO .Xr fsync 2 , .Xr sync 2 , diff --git a/share/man/man9/VFS_UNMOUNT.9 b/share/man/man9/VFS_UNMOUNT.9 index bf6aa7c..e743186 100644 --- a/share/man/man9/VFS_UNMOUNT.9 +++ b/share/man/man9/VFS_UNMOUNT.9 @@ -33,7 +33,7 @@ .Dt VFS_UNMOUNT 9 .Sh NAME .Nm VFS_UNMOUNT -.Nd unmount a filesystem +.Nd unmount a file system .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -41,16 +41,16 @@ .Ft int .Fn VFS_UNMOUNT "struct mount *mp" "int mntflags" "struct thread *td" .Sh DESCRIPTION -Unmount a filesystem. +Unmount a file system. .Pp Its arguments are: .Bl -tag -width mntflags .It Ar mp -The filesystem. +The file system. .It Ar mntflags Various flags. .It Ar td -Thread which is unmounting the filesystem. +Thread which is unmounting the file system. .El .Pp If the diff --git a/share/man/man9/VFS_VGET.9 b/share/man/man9/VFS_VGET.9 index ee015de..eb93c4b 100644 --- a/share/man/man9/VFS_VGET.9 +++ b/share/man/man9/VFS_VGET.9 @@ -46,7 +46,7 @@ This converts an inode number into a locked vnode. Its arguments are: .Bl -tag -width ".Ar flags" .It Ar mp -The filesystem. +The file system. .It Ar ino The inode representing the file. .It Ar flags @@ -55,14 +55,14 @@ Additional locking flags to pass through. Return parameter for the vnode. .El .Pp -This is an optional filesystem entry-point for filesystems which have a -unique id number for every file in the filesystem. It is used -internally by the UFS filesystem and also by the NFSv3 server to +This is an optional file system entry-point for file systems which have a +unique id number for every file in the file system. It is used +internally by the UFS file system and also by the NFSv3 server to implement the .Dv READDIRPLUS nfs call. .Pp -If the filesystem does not support this call, then it should return +If the file system does not support this call, then it should return .Er EOPNOTSUPP . .Sh SEE ALSO .Xr VFS 9 , diff --git a/share/man/man9/VOP_ACCESS.9 b/share/man/man9/VOP_ACCESS.9 index a72a799..f1a1aa2 100644 --- a/share/man/man9/VOP_ACCESS.9 +++ b/share/man/man9/VOP_ACCESS.9 @@ -76,7 +76,7 @@ vop_access(struct vnode *vp, int mode, struct ucred *cred, struct thread *td) int error; /* - * Disallow write attempts on read-only filesystems; + * Disallow write attempts on read-only file systems; * unless the file is a socket, fifo, or a block or * character device resident on the filesystem. */ diff --git a/share/man/man9/VOP_ACLCHECK.9 b/share/man/man9/VOP_ACLCHECK.9 index 4e3f254..0315b2c 100644 --- a/share/man/man9/VOP_ACLCHECK.9 +++ b/share/man/man9/VOP_ACLCHECK.9 @@ -86,7 +86,7 @@ The file or directory ACL does not permit access. .It Bq Er ENOMEM Sufficient memory is not available to fulfill the request. .It Bq Er EOPNOTSUPP -The filesystem does not support +The file system does not support .Fn VOP_ACLCHECK . .El .Sh SEE ALSO diff --git a/share/man/man9/VOP_ADVLOCK.9 b/share/man/man9/VOP_ADVLOCK.9 index e402636..925cc2f 100644 --- a/share/man/man9/VOP_ADVLOCK.9 +++ b/share/man/man9/VOP_ADVLOCK.9 @@ -68,7 +68,7 @@ semantics for lock .El .Pp This entry point manipulates advisory record locks on the file. Most -filesystems delegate the work for this call to +file systems delegate the work for this call to .Fn lf_advlock . .Sh RETURN VALUES Zero is returned on success, otherwise an error is returned. diff --git a/share/man/man9/VOP_ATTRIB.9 b/share/man/man9/VOP_ATTRIB.9 index 1f77e82..e75958b 100644 --- a/share/man/man9/VOP_ATTRIB.9 +++ b/share/man/man9/VOP_ATTRIB.9 @@ -94,7 +94,7 @@ vop_getattr(struct vnode *vp, struct vattr *vap, { /* * Fill in the contents of *vap with information from - * the filesystem. + * the file system. */ ...; @@ -155,7 +155,7 @@ The file is immutable. .It Bq Er EACCES The caller does not have permission to modify the file or directory attributes. .It Bq Er EROFS -The filesystem is read-only. +The file system is read-only. .El .Sh SEE ALSO .Xr VFS 9 , diff --git a/share/man/man9/VOP_BWRITE.9 b/share/man/man9/VOP_BWRITE.9 index c758b59..8aad090 100644 --- a/share/man/man9/VOP_BWRITE.9 +++ b/share/man/man9/VOP_BWRITE.9 @@ -33,7 +33,7 @@ .Dt VOP_BWRITE 9 .Sh NAME .Nm VOP_BWRITE -.Nd write a filesystem buffer +.Nd write a file system buffer .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h diff --git a/share/man/man9/VOP_CREATE.9 b/share/man/man9/VOP_CREATE.9 index 1223dae..558adac 100644 --- a/share/man/man9/VOP_CREATE.9 +++ b/share/man/man9/VOP_CREATE.9 @@ -155,7 +155,7 @@ bad: vput(vp); /* - * Deallocate filesystem resources for vp. + * Deallocate file system resources for vp. */ ...; @@ -167,9 +167,9 @@ bad: .Sh ERRORS .Bl -tag -width Er .It Bq Er ENOSPC -The filesystem is full. +The file system is full. .It Bq Er EDQUOT -The user's filesystem space or inode quota would be exceeded. +The user's file system space or inode quota would be exceeded. .El .Sh SEE ALSO .Xr VOP_LOOKUP 9 diff --git a/share/man/man9/VOP_FSYNC.9 b/share/man/man9/VOP_FSYNC.9 index eabba32..63d49e6 100644 --- a/share/man/man9/VOP_FSYNC.9 +++ b/share/man/man9/VOP_FSYNC.9 @@ -33,14 +33,14 @@ .Dt VOP_FSYNC 9 .Sh NAME .Nm VOP_FSYNC -.Nd flush filesystem buffers for a file +.Nd flush file system buffers for a file .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h .Ft int .Fn VOP_FSYNC "struct vnode *vp" "struct ucred *cred" "int waitfor" "struct thread *td" .Sh DESCRIPTION -This call flushes any dirty filesystem buffers for the file. +This call flushes any dirty file system buffers for the file. It is used to implement the .Xr sync 2 and @@ -62,7 +62,7 @@ synchronously wait for I/O to complete .It Dv MNT_NOWAIT start all I/O, but do not wait for it .It Dv MNT_LAZY -push data not written by filesystem syncer +push data not written by file system syncer .El .It Ar td the calling thread @@ -139,7 +139,7 @@ loop: .Sh ERRORS .Bl -tag -width Er .It Bq Er ENOSPC -The filesystem is full. +The file system is full. .It Bq Er EDQUOT Quota exceeded. .El diff --git a/share/man/man9/VOP_GETACL.9 b/share/man/man9/VOP_GETACL.9 index 47b2a81..a59419a 100644 --- a/share/man/man9/VOP_GETACL.9 +++ b/share/man/man9/VOP_GETACL.9 @@ -83,7 +83,7 @@ The the caller does not have the appropriate privilege. .It Bq Er ENOMEM Sufficient memory is not available to fulfill the request. .It Bq Er EOPNOTSUPP -The filesystem does not support +The file system does not support .Fn VOP_GETACL . .El .Sh SEE ALSO diff --git a/share/man/man9/VOP_GETEXTATTR.9 b/share/man/man9/VOP_GETEXTATTR.9 index 2cd3ce6..8487c54 100644 --- a/share/man/man9/VOP_GETEXTATTR.9 +++ b/share/man/man9/VOP_GETEXTATTR.9 @@ -88,7 +88,7 @@ This setting might be used to allow the kernel to authorize extended attribute retrieval that the active process might not be permitted to do. .Pp -Extended attribute semantics may vary by filesystem implementing the call. +Extended attribute semantics may vary by file system implementing the call. More information on extended attributes may be found in .Xr extattr 9 . .Sh LOCKS @@ -103,7 +103,7 @@ The attribute name is not defined for this vnode. .It Bq Er EACCES The the caller does not have the appropriate privilege. .It Bq Er ENXIO -The request was not valid in this filesystem for the specified vnode and +The request was not valid in this file system for the specified vnode and attribute name. .It Bq Er ENOMEM Sufficient memory is not available to fulfill the request. @@ -116,7 +116,7 @@ or .Fa uio argument is invalid. .It Bq Er EOPNOTSUPP -The filesystem does not support +The file system does not support .Fn VOP_GETEXTATTR . .El .Sh SEE ALSO diff --git a/share/man/man9/VOP_GETVOBJECT.9 b/share/man/man9/VOP_GETVOBJECT.9 index 1e84e07..19b4c84 100644 --- a/share/man/man9/VOP_GETVOBJECT.9 +++ b/share/man/man9/VOP_GETVOBJECT.9 @@ -61,9 +61,9 @@ invokes .Fn VOP_CREATEVOBJECT when it needs to create a VM object for the given .Xr vnode 9 . -Filesystem code may pass this call down to the underlying filesystem. +File system code may pass this call down to the underlying file system. This VOP can be called multiple times, -and filesystem code should ignore any additional calls, +and file system code should ignore any additional calls, exiting with a zero return code. .Pp .Fn VOP_DESTROYVOBJECT @@ -74,7 +74,7 @@ is recycled. .Fn VOP_GETVOBJECT should be used by all kernel code to get a VM object. .\" XXX What is the next sentence trying to tell people? -The returned VM object may belong to a different filesystem in the case +The returned VM object may belong to a different file system in the case of stacked mounts. .Pp .Xr VFS 9 @@ -101,7 +101,7 @@ Zero is returned on success, otherwise an error is returned. .Sh EXAMPLES .\" XXX Why is this code here when it does not use the functions .\" described in this manual page? -By default, filesystems leave VM object handling to the +By default, file systems leave VM object handling to the .Fn vop_std* functions. .Sh SEE ALSO diff --git a/share/man/man9/VOP_INACTIVE.9 b/share/man/man9/VOP_INACTIVE.9 index 696470e..9fa3833 100644 --- a/share/man/man9/VOP_INACTIVE.9 +++ b/share/man/man9/VOP_INACTIVE.9 @@ -34,7 +34,7 @@ .Sh NAME .Nm VOP_INACTIVE , .Nm VOP_RECLAIM -.Nd reclaim filesystem resources for a vnode +.Nd reclaim file system resources for a vnode .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h @@ -52,11 +52,11 @@ the vnode being reclaimed .Xr VOP_INACTIVE 9 is called when the kernel is no longer using the vnode. This may be because the reference count reaches zero or it may be that the -filesystem is being forcibly unmounted while there are open files. +file system is being forcibly unmounted while there are open files. It can be used to reclaim space for 'open but deleted' files. .Xr VOP_RECLAIM 9 -is called when a vnode is being reused for a different filesystem. -Any filesystem specific resources associated with the vnode should be +is called when a vnode is being reused for a different file system. +Any file system specific resources associated with the vnode should be freed. .Sh LOCKS For VOP_INACTIVE, the vp will be locked on entry. Your VOP_INACTIVE code @@ -71,7 +71,7 @@ vop_inactive(struct vnode *vp, struct thread *td) { if (link count of vp == 0) { /* - * Reclaim space in filesystem for vp. + * Reclaim space in file system for vp. */ ...; } @@ -89,7 +89,7 @@ vop_reclaim(struct vnode *vp, struct thread *td) cache_purge(vp); /* - * Free filesystem-related data. + * Free file system related data. */ ...; diff --git a/share/man/man9/VOP_IOCTL.9 b/share/man/man9/VOP_IOCTL.9 index 3670d62..82b335a 100644 --- a/share/man/man9/VOP_IOCTL.9 +++ b/share/man/man9/VOP_IOCTL.9 @@ -58,7 +58,7 @@ the caller's credentials the calling thread .El .Pp -Most filesystems do not implement this entry point. +Most file systems do not implement this entry point. .Sh LOCKS The file should not be locked on entry. .Sh RETURN VALUES diff --git a/share/man/man9/VOP_LOCK.9 b/share/man/man9/VOP_LOCK.9 index fbc597c..e0c2c0d 100644 --- a/share/man/man9/VOP_LOCK.9 +++ b/share/man/man9/VOP_LOCK.9 @@ -50,7 +50,7 @@ .Ft int .Fn vn_lock "struct vnode *vp" "int flags" "struct thread *td" .Sh DESCRIPTION -These calls are used to serialize access to the filesystem, such as +These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. .Pp @@ -106,7 +106,7 @@ Zero is returned on success, otherwise an error is returned. struct vopnode { int von_flag; /* - * Other filesystem specific data. + * Other file system specific data. */ ...; }; diff --git a/share/man/man9/VOP_LOOKUP.9 b/share/man/man9/VOP_LOOKUP.9 index e44f1f2..8934a3a 100644 --- a/share/man/man9/VOP_LOOKUP.9 +++ b/share/man/man9/VOP_LOOKUP.9 @@ -77,7 +77,7 @@ struct componentname { .Pp Convert a component of a pathname into a pointer to a locked vnode. This is a very central and rather complicated routine. -If the filesystem is not maintained in a strict tree hierarchy, +If the file system is not maintained in a strict tree hierarchy, this can result in a deadlock situation. .Pp The @@ -371,7 +371,7 @@ vop_lookup(struct vnode *dvp, * infrequently since we cannot avoid this race condition without * implementing a sophisticated deadlock detection algorithm. * Note also that this simple deadlock detection scheme will not - * work if the filesystem has any hard links other than ".." + * work if the file system has any hard links other than ".." * that point backwards in the directory structure. */ if (flags & ISDOTDOT) { diff --git a/share/man/man9/VOP_OPENCLOSE.9 b/share/man/man9/VOP_OPENCLOSE.9 index bf3fee8..5c1be6c 100644 --- a/share/man/man9/VOP_OPENCLOSE.9 +++ b/share/man/man9/VOP_OPENCLOSE.9 @@ -85,7 +85,7 @@ int vop_open(struct vnode *vp, int mode, struct ucred *cred, struct thread *td) { /* - * Most filesystems don't do much here. + * Most file systems don't do much here. */ return 0; } diff --git a/share/man/man9/VOP_RDWR.9 b/share/man/man9/VOP_RDWR.9 index 545fd57..2202893 100644 --- a/share/man/man9/VOP_RDWR.9 +++ b/share/man/man9/VOP_RDWR.9 @@ -60,9 +60,9 @@ the credentials of the caller .Pp The .Fa ioflag -argument is used to give directives and hints to the filesystem. +argument is used to give directives and hints to the file system. When attempting a read, the high 16 bits are used to provide a -read-ahead hint (in units of filesystem blocks) that the filesystem +read-ahead hint (in units of file system blocks) that the file system should attempt. The low 16 bits are a bit mask which can contain the following flags: .Bl -tag -width IO_NODELOCKED @@ -95,7 +95,7 @@ vop_read(struct vnode *vp, struct uio *uio, int ioflag, struct ucred *cred) long size, xfersize, blkoffset; int error; - size = block size of filesystem; + size = block size of file system; for (error = 0, bp = NULL; uio->uio_resid > 0; bp = NULL) { bytesinfile = size of file - uio->uio_offset; @@ -156,7 +156,7 @@ vop_write(struct vnode *vp, struct uio *uio, int ioflag, struct ucred *cred) int error; osize = size of file; - size = block size of filesystem; + size = block size of file system; resid = uio->uio_resid; if (ioflag & IO_SYNC) flags = B_SYNC; @@ -224,7 +224,7 @@ vop_write(struct vnode *vp, struct uio *uio, int ioflag, struct ucred *cred) An attempt was made to write a file that exceeds the process's file size limit or the maximum file size. .It Bq Er ENOSPC -The filesystem is full. +The file system is full. .It Bq Er EPERM An append-only flag is set on the file, but the caller is attempting to write before the current end of file. diff --git a/share/man/man9/VOP_SETACL.9 b/share/man/man9/VOP_SETACL.9 index 5fd76bc..1c01b71 100644 --- a/share/man/man9/VOP_SETACL.9 +++ b/share/man/man9/VOP_SETACL.9 @@ -87,12 +87,12 @@ The the caller does not have the appropriate privilege. .It Bq Er ENOMEM Sufficient memory is not available to fulfill the request. .It Bq Er EOPNOTSUPP -The filesystem does not support +The file system does not support .Fn VOP_SETACL . .It Bq Er ENOSPC -The filesystem is out of space. +The file system is out of space. .It Bq Er EROFS -The filesystem is read-only. +The file system is read-only. .El .Sh SEE ALSO .Xr acl 9 , diff --git a/share/man/man9/VOP_SETEXTATTR.9 b/share/man/man9/VOP_SETEXTATTR.9 index 9269552..7f7c2a4 100644 --- a/share/man/man9/VOP_SETEXTATTR.9 +++ b/share/man/man9/VOP_SETEXTATTR.9 @@ -80,7 +80,7 @@ This setting might be used to allow the kernel to authorize extended attribute changes that the active process might not be permitted to make. .Pp -Extended attribute semantics may vary by filesystem implementing the call. +Extended attribute semantics may vary by file system implementing the call. More information on extended attributes may be found in .Xr extattr 9 . .Sh LOCKS @@ -93,7 +93,7 @@ Otherwise, an appropriate error code is returned. .It Bq Er EACCES The the caller does not have the appropriate privilege. .It Bq Er ENXIO -The request was not valid in this filesystem for the specified vnode and +The request was not valid in this file system for the specified vnode and attribute name. .It Bq Er ENOMEM Insufficient memory available to fulfill request @@ -102,12 +102,12 @@ The uio structure refers to an invalid userspace address. .It Bq Er EINVAL The name or uio argument is invalid. .It Bq Er EOPNOTSUPP -The filesystem does not support +The file system does not support .Fn VOP_SETEXTATTR . .It Bq Er ENOSPC -The filesystem is out of space. +The file system is out of space. .It Bq Er EROFS -The filesystem is read-only. +The file system is read-only. .El .Sh SEE ALSO .Xr extattr 9 , diff --git a/share/man/man9/VOP_STRATEGY.9 b/share/man/man9/VOP_STRATEGY.9 index d020d15..7336bad 100644 --- a/share/man/man9/VOP_STRATEGY.9 +++ b/share/man/man9/VOP_STRATEGY.9 @@ -33,7 +33,7 @@ .Dt VOP_STRATEGY 9 .Sh NAME .Nm VOP_STRATEGY -.Nd read or write a filesystem buffer +.Nd read or write a file system buffer .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h diff --git a/share/man/man9/acl.9 b/share/man/man9/acl.9 index 0a61575..9ea49de 100644 --- a/share/man/man9/acl.9 +++ b/share/man/man9/acl.9 @@ -30,7 +30,7 @@ .Dt ACL 9 .Sh NAME .Nm acl -.Nd virtual filesystem access control lists +.Nd virtual file system access control lists .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h @@ -42,10 +42,10 @@ In the kernel configuration file: Access control lists, or ACLs, allow fine-grained specification of rights for vnodes representing files and directories. -However, as there are a plethora of filesystems with differing ACL semantics, +However, as there are a plethora of file systems with differing ACL semantics, the vnode interface is aware only of the syntax of ACLs, -relying on the underlying filesystem to implement the details. -Depending on the underlying filesystem, each file or directory +relying on the underlying file system to implement the details. +Depending on the underlying file system, each file or directory may have zero or more ACLs associated with it, named using the .Fa type field of the appropriate vnode ACL calls: diff --git a/share/man/man9/buf.9 b/share/man/man9/buf.9 index 9d8b643..1a2a68a 100644 --- a/share/man/man9/buf.9 +++ b/share/man/man9/buf.9 @@ -40,7 +40,7 @@ .Sh DESCRIPTION The kernel implements a KVM abstraction of the buffer cache which allows it to map potentially disparate vm_page's into contiguous KVM for use by -(mainly filesystem) devices and device I/O. This abstraction supports +(mainly file system) devices and device I/O. This abstraction supports block sizes from DEV_BSIZE (usually 512) to upwards of several pages or more. It also supports a relatively primitive byte-granular valid range and dirty range currently hardcoded for use by NFS. The code implementing the @@ -49,7 +49,7 @@ VM Buffer abstraction is mostly concentrated in .Pp One of the most important things to remember when dealing with buffer pointers (struct buf) is that the underlying pages are mapped directly from the buffer -cache. No data copying occurs in the scheme proper, though some filesystems +cache. No data copying occurs in the scheme proper, though some file systems such as UFS do have to copy a little when dealing with file fragments. The second most important thing to remember is that due to the underlying page mapping, the b_data base pointer in a buf is always *page* aligned, not @@ -83,14 +83,14 @@ system typically unmaps it from KVM and replaces the page in the b_pages[] array with a place-marker called bogus_page. The place-marker forces any kernel subsystems referencing the associated struct buf to re-lookup the associated page. I believe the place-marker hack is used to allow sophisticated devices -such as filesystem devices to remap underlying pages in order to deal with, +such as file system devices to remap underlying pages in order to deal with, for example, re-mapping a file fragment into a file block. .Pp VM buffers are used to track I/O operations within the kernel. Unfortunately, the I/O implementation is also somewhat of a hack because the kernel wants to clear the dirty bit on the underlying pages the moment it queues the I/O to the VFS device, not when the physical I/O is actually initiated. This -can create confusion within filesystem devices that use delayed-writes because +can create confusion within file system devices that use delayed-writes because you wind up with pages marked clean that are actually still dirty. If not treated carefully, these pages could be thrown away! Indeed, a number of serious bugs related to this hack were not fixed until the 2.2.8/3.0 release. diff --git a/share/man/man9/extattr.9 b/share/man/man9/extattr.9 index 224df09..70ecb11 100644 --- a/share/man/man9/extattr.9 +++ b/share/man/man9/extattr.9 @@ -30,7 +30,7 @@ .Dt EXTATTR 9 .Sh NAME .Nm extattr -.Nd virtual filesystem named extended attributes +.Nd virtual file system named extended attributes .Sh SYNOPSIS .In sys/param.h .In sys/vnode.h @@ -47,7 +47,7 @@ operation refers. 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 -filesystems may implement additional namespaces, or not implement +file systems may implement additional namespaces, or not implement these namespaces: .Dv EXTATTR_NAMESPACE_USER , .Dv EXTATTR_NAMESPACE_SYSTEM . @@ -62,16 +62,16 @@ the meta-data, in the style of .Xr VOP_READ 9 , but writes will replace the entire current "value" associated with a given name. -As there are a plethora of filesystems with differing extended attributes, +As there are a plethora of file systems with differing extended attributes, availability and functionality of these functions may be limited, and they should be used with awareness of the underlying semantics of the supporting -filesystem. +file system. Authorization schemes for extended attribute data may also vary by file system, as well as maximum attribute size, and whether or not any or specific new attributes may be defined. .Pp Extended attributes are named using a null-terminated character string. -Depending on underlying filesystem semantics, this name may or may not be +Depending on underlying file system semantics, this name may or may not be case-sensitive. Appropriate vnode extended attribute calls are: .Xr VOP_GETEXTATTR 9 and diff --git a/share/man/man9/getnewvnode.9 b/share/man/man9/getnewvnode.9 index 1ffd9e6..d1790ff 100644 --- a/share/man/man9/getnewvnode.9 +++ b/share/man/man9/getnewvnode.9 @@ -51,7 +51,7 @@ The arguments to are: .Bl -tag -width ".Fa vops" .It Fa tag -The filesystem type string. +The file system type string. This field should only be referenced for debugging or for userland utilities. .It Fa mp The mount point to add the new vnode to. diff --git a/share/man/man9/inittodr.9 b/share/man/man9/inittodr.9 index 281ba23..39dd741 100644 --- a/share/man/man9/inittodr.9 +++ b/share/man/man9/inittodr.9 @@ -48,12 +48,12 @@ The function determines the time and sets the system clock. It tries to pick the correct time using a set of heuristics that examine the system's battery backed clock and the time obtained from the root -filesystem, as given in +file system, as given in .Fa base . How the .Fa base value is obtained will vary depending on the -root filesystem type. +root file system type. The heuristics used include: .Bl -bullet .It diff --git a/share/man/man9/pseudofs.9 b/share/man/man9/pseudofs.9 index 79f47fa..4e5cc8b 100644 --- a/share/man/man9/pseudofs.9 +++ b/share/man/man9/pseudofs.9 @@ -30,14 +30,14 @@ .Os .Sh NAME .Nm pseudofs -.Nd pseudo-filesystem construction kit +.Nd pseudo file system construction kit .Sh SYNOPSIS .In fs/pseudofs/pseudofs.h .\" Insert usage example here .Sh DESCRIPTION The .Nm -module offers an abstract API for pseudo-filesystems such as +module offers an abstract API for pseudo-file systems such as .Xr procfs 5 and .Xr linprocfs 5 . @@ -45,7 +45,7 @@ It takes care of all the hairy bits like interfacing with the VFS system, enforcing access control, keeping track of file numbers, and cloning files and directories that are process-specific. The consumer module, i.e. the module that implements the actual guts -of the filesystem, needs only provide the directory structure +of the file system, needs only provide the directory structure (represented by a collection of structures declared and initialized by macros provided by .Nm ) diff --git a/share/man/man9/vaccess.9 b/share/man/man9/vaccess.9 index b366830..fd05071 100644 --- a/share/man/man9/vaccess.9 +++ b/share/man/man9/vaccess.9 @@ -48,7 +48,7 @@ This call implements the logic for the .Ux discretionary file security model -common to many filesystems in +common to many file systems in .Fx . It accepts the vnodes type .Fa type , diff --git a/share/man/man9/vfs_getnewfsid.9 b/share/man/man9/vfs_getnewfsid.9 index f11f4a1..c09f050 100644 --- a/share/man/man9/vfs_getnewfsid.9 +++ b/share/man/man9/vfs_getnewfsid.9 @@ -31,7 +31,7 @@ .Os .Sh NAME .Nm vfs_getnewfsid -.Nd "allocate a new filesystem identifier" +.Nd "allocate a new file system identifier" .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -40,11 +40,11 @@ .Sh DESCRIPTION The .Fn vfs_getnewfsid -function allocates a new filesystem identifier for the mount point given. -Filesystems typically call +function allocates a new file system identifier for the mount point given. +File systems typically call .Fn vfs_getnewfsid in their mount routine in order to acquire a unique ID within the system -which can later be used to uniquely identify the filesystem via calls such as +which can later be used to uniquely identify the file system via calls such as .Xr vfs_getvfs 9 . .Pp The actual @@ -53,8 +53,8 @@ is made up of two 32 bit integers, that are stored in the .Vt statfs structure of .Fa mp . -The first integer is unique in the set of mounted filesystems, -while the second holds the filesystem type. +The first integer is unique in the set of mounted file systems, +while the second holds the file system type. .Bd -literal typedef struct fsid { int32_t val[2]; diff --git a/share/man/man9/vfs_getvfs.9 b/share/man/man9/vfs_getvfs.9 index 664470c..37d931b 100644 --- a/share/man/man9/vfs_getvfs.9 +++ b/share/man/man9/vfs_getvfs.9 @@ -31,7 +31,7 @@ .Os .Sh NAME .Nm vfs_getvfs -.Nd "returns a mount point given its filesystem identifier" +.Nd "returns a mount point given its file system identifier" .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -40,9 +40,9 @@ .Sh DESCRIPTION The .Fn vfs_getvfs -function returns the mount point structure for a filesystem given its filesystem +function returns the mount point structure for a file system given its file system identifier. -The filesystem ID should have been allocated by calling +The file system ID should have been allocated by calling .Xr vfs_getnewfsid 9 ; otherwise, it will not be found. .Pp @@ -51,12 +51,12 @@ A major user of is NFS, which uses the .Vt fsid as part of file handles in order to determine the -filesystem a given RPC is for. +file system a given RPC is for. If .Fn vfs_getvfs fails to find the mount point related to .Fa fsid , -the filesystem is considered stale. +the file system is considered stale. .Sh RETURN VALUES If .Fa fsid diff --git a/share/man/man9/vfs_mount.9 b/share/man/man9/vfs_mount.9 index d9e37cd..17ef0f3c 100644 --- a/share/man/man9/vfs_mount.9 +++ b/share/man/man9/vfs_mount.9 @@ -31,7 +31,7 @@ .Os .Sh NAME .Nm vfs_mount -.Nd "generic filesystem mount function" +.Nd "generic file system mount function" .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -46,8 +46,8 @@ .Sh DESCRIPTION The .Fn vfs_mount -function handles the generic portion of mounting a filesystem, -and calls the filesystem specific mount function after verifying +function handles the generic portion of mounting a file system, +and calls the file system specific mount function after verifying its parameters and setting up the structures expected by the underlying mount code. .Pp @@ -61,9 +61,9 @@ Its arguments are: .It Fa td The thread responsible for this call. .It Fa fstype -The type of filesystem being mounted. +The type of file system being mounted. .It Fa fspath -The path to the mount point of the filesystem. +The path to the mount point of the file system. .It Fa fsflags Flags controlling the mount. See @@ -75,11 +75,11 @@ for details. .Dv MNT_SNAPSHOT , MNT_NOCLUSTERR , MNT_NOCLUSTERW , MNT_IGNORE , .Dv MNT_UNION , MNT_NOSYMFOLLOW .It Fa fsdata -Filesystem specific data structure. +File system specific data structure. It is in userspace when passed to .Fn vfs_mount -and is left untouched when passed to filesystem's +and is left untouched when passed to file system's .Fn mount . .El .Sh RETURN VALUES @@ -92,7 +92,7 @@ path component is too long. .It Bq Er EPERM Permission denied. There are a number of reason this can occur -ranging from the user not having permission to mount a filesystem +ranging from the user not having permission to mount a file system to the securelevel being to high to load the .Fa fstype module. @@ -105,7 +105,7 @@ The mount point does not exist (from The mount point is a muddle of links (from .Fn namei ) . .It Bq Er EOPNOTSUPP -The operation is not supported (ex: reloading a r/w filesystem). +The operation is not supported (ex: reloading a r/w file system). .It Bq Er EBUSY The mount point is busy or is not really a mount point (on update). .It Bq Er ENOTDIR @@ -118,10 +118,10 @@ or was unable to find the specified module. .El .Pp -Other errors can be returned by the filesystem's +Other errors can be returned by the file system's .Fn mount and -you should check the specific filesystem for details. +you should check the specific file system for details. Also this call relies on a large number of other kernel services whose errors it returns so this list may not be exhaustive. diff --git a/share/man/man9/vfs_mountedon.9 b/share/man/man9/vfs_mountedon.9 index 07f2b09..bdf53d0 100644 --- a/share/man/man9/vfs_mountedon.9 +++ b/share/man/man9/vfs_mountedon.9 @@ -31,7 +31,7 @@ .Os .Sh NAME .Nm vfs_mountedon -.Nd "check if the vnode belongs to a mounted filesystem" +.Nd "check if the vnode belongs to a mounted file system" .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -49,7 +49,7 @@ If the mount is valid, the vnode is considered to be busy. A common use of .Fn vfs_mountedon is to call it on device vnodes to determine if they are already associated with -a filesystem. +a file system. This is done to prevent multiple mounts on the same device. .Sh RETURN VALUES .Er EBUSY diff --git a/share/man/man9/vfs_unmountall.9 b/share/man/man9/vfs_unmountall.9 index 9762c1a..d315077 100644 --- a/share/man/man9/vfs_unmountall.9 +++ b/share/man/man9/vfs_unmountall.9 @@ -29,7 +29,7 @@ .Os .Sh NAME .Nm vfs_unmountall -.Nd unmount all filesystems +.Nd unmount all file systems .Sh SYNOPSIS .In sys/param.h .In sys/mount.h @@ -40,7 +40,7 @@ The .Nm function, run only at system shutdown, -unmounts all mounted filesystems +unmounts all mounted file systems from most recent to oldest in order to avoid handling dependencies. .Sh SEE ALSO diff --git a/share/man/man9/vfsconf.9 b/share/man/man9/vfsconf.9 index e64b8e2..638052d 100644 --- a/share/man/man9/vfsconf.9 +++ b/share/man/man9/vfsconf.9 @@ -42,28 +42,28 @@ .Ft int .Fn vfs_modevent "module_t mod" "int type" "void *data" .Sh DESCRIPTION -Each filesystem type known to the kernel has a +Each file system type known to the kernel has a .Vt vfsconf structure that contains the -information required to create a new mount of that filesystems type. +information required to create a new mount of that file systems type. .Bd -literal struct vfsconf { - struct vfsops *vfc_vfsops; /* filesystem operations vector */ - char vfc_name[MFSNAMELEN]; /* filesystem type name */ - int vfc_typenum; /* historic filesystem type number */ + struct vfsops *vfc_vfsops; /* file system operations vector */ + char vfc_name[MFSNAMELEN]; /* file system type name */ + int vfc_typenum; /* historic file system type number */ int vfc_refcount; /* number mounted of this type */ int vfc_flags; /* permanent flags */ struct vfsconf *vfc_next; /* next in list */ }; .Ed .Pp -When a new filesystem is mounted, +When a new file system is mounted, .Xr vfs_mount 9 does a lookup of the .Vt vfsconf structure by its name, and if it is not already registered, attempts to load a kernel module for it. -The filesystem operations for the new mount point are taken from +The file system operations for the new mount point are taken from .Va vfc_vfsops , and .Va mnt_vfc @@ -72,40 +72,40 @@ in the structure is made to point directly at the .Vt vfsconf structure for the -filesystem type. -The filesystem type number is taken from +file system type. +The file system type number is taken from .Va vfc_typenum which was assigned in .Fn vfs_register , and the mount flags are taken from a mask of .Va vfc_flags . -Each time a filesystem of a given type is mounted, +Each time a file system of a given type is mounted, .Va vfc_refcount is incremented. .Pp .Fn vfs_register takes a new .Vt vfsconf -structure and adds it to the list of existing filesystems. +structure and adds it to the list of existing file systems. If the type has not already been registered, it is initialized by calling the .Fn vfs_init -function in the filesystem operations vector. +function in the file system operations vector. .Fn vfs_register -also updates the oid's of any sysctl nodes for this filesystem type +also updates the oid's of any sysctl nodes for this file system type to be the same as the newly assigned type number. .Pp .Fn vfs_unregister unlinks .Fa vfc -from the list of registered filesystem types if there are currently no mounted instances. +from the list of registered file system types if there are currently no mounted instances. If the .Fn vfs_uninit -function in the filesystems initialization vector is defined, it is called. +function in the file systems initialization vector is defined, it is called. .Pp .Fn vfs_modevent is registered by .Fn VFS_SET -to handle the loading and unloading of filesystem kernel modules. +to handle the loading and unloading of file system kernel modules. In the case of .Dv MOD_LOAD , .Fn vfs_register @@ -118,7 +118,7 @@ is called. .Fn vfs_register returns 0 if successful; otherwise, .Er EEXIST -is returned indicating that the filesystem type has already been registered. +is returned indicating that the file system type has already been registered. .Pp .Fn vfs_unregister returns 0 if successful. @@ -128,7 +128,7 @@ entry can be found matching the name in .Fa vfc , .Er EINVAL is returned. -If the reference count of mounted instances of the filesystem type is not zero, +If the reference count of mounted instances of the file system type is not zero, .Er EBUSY is returned. If diff --git a/share/man/man9/vgone.9 b/share/man/man9/vgone.9 index 3807a0f..3731f93 100644 --- a/share/man/man9/vgone.9 +++ b/share/man/man9/vgone.9 @@ -43,8 +43,8 @@ .Fn vgone and .Fn vgonel -prepare a vnode for reuse by another filesystem. -The preparation includes the cleaning of all filesystem specific data and +prepare a vnode for reuse by another file system. +The preparation includes the cleaning of all file system specific data and the removal from its mount point vnode list. .Pp If the vnode has a @@ -53,7 +53,7 @@ of zero, and its .Dv VDOOMED flag is not set, it is moved to the head of the free list as in most cases the vnode -is about to be reused, or its filesystem being unmounted. +is about to be reused, or its file system being unmounted. .Pp The difference between .Fn vgone diff --git a/share/man/man9/vinvalbuf.9 b/share/man/man9/vinvalbuf.9 index dd5a60f..c00f654 100644 --- a/share/man/man9/vinvalbuf.9 +++ b/share/man/man9/vinvalbuf.9 @@ -87,7 +87,7 @@ if (error) .Sh ERRORS .Bl -tag -width Er .It Bq Er ENOSPC -The filesystem is full. +The file system is full. (With .Dv V_SAVE ) .It Bq Er EDQUOT diff --git a/share/man/man9/vnode.9 b/share/man/man9/vnode.9 index 84510f2..dc163f2 100644 --- a/share/man/man9/vnode.9 +++ b/share/man/man9/vnode.9 @@ -57,7 +57,7 @@ enum vtagtype { }; /* - * Each underlying filesystem allocates its own private area and hangs + * Each underlying file system allocates its own private area and hangs * it from v_data. If non-null, this area is freed in getnewvnode(). */ TAILQ_HEAD(buflists, buf); @@ -127,7 +127,7 @@ struct vnode { /* * Vnode flags. */ -#define VROOT 0x00001 /* root of its filesystem */ +#define VROOT 0x00001 /* root of its file system */ #define VTEXT 0x00002 /* vnode is a pure text prototype */ #define VSYSTEM 0x00004 /* vnode being used by kernel */ #define VISTTY 0x00008 /* vnode represents a tty */ @@ -174,7 +174,7 @@ When both the and the .Dv v_holdcnt of a vnode reaches zero then the vnode will be put on the freelist -and may be reused for another file, possibly in another filesystem. +and may be reused for another file, possibly in another file system. The transition to and from the freelist is handled by .Xr getnewvnode 9 , .Xr vfree 9 @@ -204,17 +204,17 @@ Other commonly used members of the vnode structure are .Dv v_id which is used to maintain consistency in the name cache, .Dv v_mount -which points at the filesystem which owns the vnode, +which points at the file system which owns the vnode, .Dv v_type which contains the type of object the vnode represents and .Dv v_data -which is used by filesystems to store filesystem specific data with +which is used by file systems to store file system specific data with the vnode. The .Dv v_op field is used by the .Dv VOP_* -macros to call functions in the filesystem which implement the vnode's +macros to call functions in the file system which implement the vnode's functionality. .Sh VNODE TYPES .Bl -tag -width VSOCK |
