path: root/sbin/mount_unionfs/mount_unionfs.8
diff options
Diffstat (limited to 'sbin/mount_unionfs/mount_unionfs.8')
1 files changed, 7 insertions, 7 deletions
diff --git a/sbin/mount_unionfs/mount_unionfs.8 b/sbin/mount_unionfs/mount_unionfs.8
index 90d652325afa..81efdb75fcdf 100644
--- a/sbin/mount_unionfs/mount_unionfs.8
+++ b/sbin/mount_unionfs/mount_unionfs.8
@@ -40,7 +40,7 @@
.Nm mount_unionfs
-.Nd mount union filesystems
+.Nd mount union file systems
.Op Fl br
@@ -88,7 +88,7 @@ Hide the lower layer completely in the same way as mounting with
.Xr mount_nullfs 8 .
-To enforce filesystem security, the user mounting the filesystem
+To enforce file system security, the user mounting the file system
must be superuser or else have write permission on the mounted-on
@@ -110,7 +110,7 @@ which will still allow the lower files to be accessed by a different
Except in the case of a directory,
-access to an object is granted via the normal filesystem access checks.
+access to an object is granted via the normal file system access checks.
For directories, the current user must have access to both the upper
and lower directories (should they both exist).
@@ -128,12 +128,12 @@ Any other operation which would ultimately require modification to
the lower layer fails with
-The union filesystem manipulates the namespace, rather than
-individual filesystems.
+The union file system manipulates the namespace, rather than
+individual file systems.
The union operation applies recursively down the directory tree
now rooted at
.Ar uniondir .
-Thus any filesystems which are mounted under
+Thus any file systems which are mounted under
.Ar uniondir
will take part in the union operation.
This differs from the
@@ -192,7 +192,7 @@ hackers can apply by sending mail to
and announcing
their intent to take it over.
-Without whiteout support from the filesystem backing the upper layer,
+Without whiteout support from the file system backing the upper layer,
there is no way that delete and rename operations on lower layer
objects can be done.