intro.1, time.1, access.2, acct.2, alloc_hugepages.2, bind.2, chdir.2, chmod.2, chown.2, chroot.2, clone.2, close.2, execve.2, fallocate.2, fcntl.2, getdents.2, getrusage.2, getxattr.2, init_module.2, inotify_add_watch.2, ioprio_set.2, kcmp.2, link.2, listxattr.2, lseek.2, madvise.2, mkdir.2, mknod.2, mmap.2, mount.2, move_pages.2, msgctl.2, nfsservctl.2, open.2, pivot_root.2, quotactl.2, read.2, readlink.2, removexattr.2, rename.2, rmdir.2, semctl.2, setfsgid.2, setfsuid.2, setresuid.2, setuid.2, setup.2, setxattr.2, shmctl.2, splice.2, spu_create.2, stat.2, statfs.2, swapon.2, symlink.2, sync.2, sync_file_range.2, sysfs.2, truncate.2, umount.2, unlink.2, unshare.2, ustat.2, utime.2, utimensat.2, write.2, btree.3, errno.3, fexecve.3, ftw.3, futimes.3, get_nprocs_conf.3, getcwd.3, getdirentries.3, getmntent.3, glob.3, mkfifo.3, mq_open.3, readdir.3, realpath.3, recno.3, remove.3, sem_open.3, shm_open.3, statvfs.3, sysconf.3, telldir.3, tmpfile.3, cciss.4, initrd.4, pts.4, sk98lin.4, vcs.4, core.5, filesystems.5, proc.5, boot.7, bootparam.7, capabilities.7, cpuset.7, credentials.7, feature_test_macros.7, fifo.7, hier.7, inotify.7, intro.7, mq_overview.7, path_resolution.7, pipe.7, sem_overview.7, shm_overview.7, spufs.7, symlink.7, unix.7, uri.7, sync.8: Global fix: s/file system/filesystem/

Notwithstanding 24d01c530c5a3f75217543d02bf6712395e5f90c,
"filesystem" is the form used by the great majority of man pages
outside the man-pages project and in a number of other sources,
so let's go with that.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

3 files changed, 75 insertions, 75 deletions

diff --git a/man5/core.5 b/man5/core.5
index 17d0cce3..551f4a3b 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -63,9 +63,9 @@ A (writable, regular) file with the same name as would be used for the
 core dump already exists, but there is more than one hard link to that
 file.
 .IP *
-The file system where the core dump file would be created is full;
+The filesystem where the core dump file would be created is full;
 or has run out of inodes; or is mounted read-only;
-or the user has reached their quota for the file system.
+or the user has reached their quota for the filesystem.
 .IP *
 The directory in which the core dump file is to be created does
 not exist.
diff --git a/man5/filesystems.5 b/man5/filesystems.5
index 22f3220c..0667e942 100644
--- a/man5/filesystems.5
+++ b/man5/filesystems.5
@@ -26,29 +26,29 @@
 .TH FILESYSTEMS 5 2012-08-05 "Linux" "Linux Programmer's Manual"
 .nh
 .SH NAME
-filesystems \- Linux file-system types: minix, ext, ext2, ext3, ext4, Reiserfs,
+filesystems \- Linux filesystem types: minix, ext, ext2, ext3, ext4, Reiserfs,
 XFS, JFS, xia, msdos,
 umsdos, vfat, ntfs, proc, nfs, iso9660, hpfs, sysv, smb, ncpfs
 .SH DESCRIPTION
 When, as is customary, the
 .B proc
-file system is mounted on
+filesystem is mounted on
 .IR /proc ,
 you can find in the file
 .I /proc/filesystems
-which file systems your kernel currently supports.
+which filesystems your kernel currently supports.
 If you need a currently unsupported one, insert the corresponding
 module or recompile the kernel.
 
-In order to use a file system, you have to
+In order to use a filesystem, you have to
 .I mount
 it; see
 .BR mount (8).
 
-Below a short description of a few of the available file systems.
+Below a short description of a few of the available filesystems.
 .TP 10
 .B "minix"
-is the file system used in the Minix operating system, the first to run
+is the filesystem used in the Minix operating system, the first to run
 under Linux.
 It has a number of shortcomings: a 64MB partition size
 limit, short filenames, a single timestamp, etc.
@@ -57,24 +57,24 @@ It remains useful for floppies and RAM disks.
 .B ext
 is an elaborate extension of the
 .B minix
-file system.
+filesystem.
 It has been completely superseded by the second version
-of the extended file system
+of the extended filesystem
 .RB ( ext2 )
 and has been removed from the kernel (in 2.1.21).
 .TP
 .B ext2
-is the high performance disk file system used by Linux for fixed disks
+is the high performance disk filesystem used by Linux for fixed disks
 as well as removable media.
-The second extended file system was designed as an extension of the
-extended file system
+The second extended filesystem was designed as an extension of the
+extended filesystem
 .RB ( ext ).
 .B ext2
 offers the best performance (in terms of speed and CPU usage) of
-the file systems supported under Linux.
+the filesystems supported under Linux.
 .TP
 .B ext3
-is a journaling version of the ext2 file system.
+is a journaling version of the ext2 filesystem.
 It is easy to
 switch back and forth between ext2 and ext3.
 .TP
@@ -84,51 +84,51 @@ reliability enhancements,
 plus large increases in volume, file, and directory size limits.
 .TP
 .B Reiserfs
-is a journaling file system, designed by Hans Reiser,
+is a journaling filesystem, designed by Hans Reiser,
 that was integrated into Linux in kernel 2.4.1.
 .TP
 .B XFS
-is a journaling file system, developed by SGI,
+is a journaling filesystem, developed by SGI,
 that was integrated into Linux in kernel 2.4.20.
 .TP
 .B JFS
-is a journaling file system, developed by IBM,
+is a journaling filesystem, developed by IBM,
 that was integrated into Linux in kernel 2.4.24.
 .TP
 .B xiafs
-was designed and implemented to be a stable, safe file system by
-extending the Minix file system code.
+was designed and implemented to be a stable, safe filesystem by
+extending the Minix filesystem code.
 It provides the basic most
 requested features without undue complexity.
 The
 .B xia
-file system is no longer actively developed or maintained.
+filesystem is no longer actively developed or maintained.
 It was removed from the kernel in 2.1.21.
 .TP
 .B msdos
-is the file system used by DOS, Windows, and some OS/2 computers.
+is the filesystem used by DOS, Windows, and some OS/2 computers.
 .B msdos
 filenames can be no longer than 8 characters, followed by an
 optional period and 3 character extension.
 .TP
 .B umsdos
-is an extended DOS file system used by Linux.
+is an extended DOS filesystem used by Linux.
 It adds capability for
 long filenames, UID/GID, POSIX permissions, and special files
-(devices, named pipes, etc.)  under the DOS file system, without
+(devices, named pipes, etc.)  under the DOS filesystem, without
 sacrificing compatibility with DOS.
 .TP
 .B vfat
-is an extended DOS file system used by Microsoft Windows95 and Windows NT.
-VFAT adds the capability to use long filenames under the MSDOS file system.
+is an extended DOS filesystem used by Microsoft Windows95 and Windows NT.
+VFAT adds the capability to use long filenames under the MSDOS filesystem.
 .TP
 .B ntfs
-replaces Microsoft Window's FAT file systems (VFAT, FAT32).
+replaces Microsoft Window's FAT filesystems (VFAT, FAT32).
 It has reliability, performance, and space-utilization enhancements
 plus features like ACLs, journaling, encryption, and so on.
 .TP
 .B proc
-is a pseudo file system which is used as an interface to kernel data
+is a pseudo filesystem which is used as an interface to kernel data
 structures rather than reading and interpreting
 .IR /dev/kmem .
 In particular, its files do not take disk space.
@@ -136,42 +136,42 @@ See
 .BR proc (5).
 .TP
 .B iso9660
-is a CD-ROM file system type conforming to the ISO 9660 standard.
+is a CD-ROM filesystem type conforming to the ISO 9660 standard.
 .RS
 .TP
 .B "High Sierra"
 Linux supports High Sierra, the precursor to the ISO 9660 standard for
-CD-ROM file systems.
+CD-ROM filesystems.
 It is automatically recognized within the
 .B iso9660
-file-system support under Linux.
+filesystem support under Linux.
 .TP
 .B "Rock Ridge"
 Linux also supports the System Use Sharing Protocol records specified
 by the Rock Ridge Interchange Protocol.
 They are used to further describe the files in the
 .B iso9660
-file system to a UNIX host, and provide information such as long
+filesystem to a UNIX host, and provide information such as long
 filenames, UID/GID, POSIX permissions, and devices.
 It is automatically recognized within the
 .B iso9660
-file-system support under Linux.
+filesystem support under Linux.
 .RE
 .TP
 .B hpfs
 is the High Performance Filesystem, used in OS/2.
-This file system is
+This filesystem is
 read-only under Linux due to the lack of available documentation.
 .TP
 .B sysv
-is an implementation of the SystemV/Coherent file system for Linux.
+is an implementation of the SystemV/Coherent filesystem for Linux.
 It implements all of Xenix FS, SystemV/386 FS, and Coherent FS.
 .TP
 .B nfs
-is the network file system used to access disks located on remote computers.
+is the network filesystem used to access disks located on remote computers.
 .TP
 .B smb
-is a network file system that supports the SMB protocol, used by
+is a network filesystem that supports the SMB protocol, used by
 Windows for Workgroups, Windows NT, and Lan Manager.
 .sp
 To use
@@ -182,7 +182,7 @@ package, found at
 .UE .
 .TP
 .B ncpfs
-is a network file system that supports the NCP protocol, used by
+is a network filesystem that supports the NCP protocol, used by
 Novell NetWare.
 .sp
 To use
diff --git a/man5/proc.5 b/man5/proc.5
index 1c7a3c0a..645d0c27 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -61,11 +61,11 @@
 .\"
 .TH PROC 5 2013-08-08 "Linux" "Linux Programmer's Manual"
 .SH NAME
-proc \- process information pseudo-file system
+proc \- process information pseudo-filesystem
 .SH DESCRIPTION
 The
 .I proc
-file system is a pseudo-file system which is used as an interface to
+filesystem is a pseudo-filesystem which is used as an interface to
 kernel data structures.
 It is commonly mounted at
 .IR /proc .
@@ -630,11 +630,11 @@ parent ID: ID of parent mount (or of self for the top of the mount tree).
 (3)
 major:minor: value of
 .I st_dev
-for files on file system (see
+for files on filesystem (see
 .BR stat (2)).
 .TP
 (4)
-root: root of the mount within the file system.
+root: root of the mount within the filesystem.
 .TP
 (5)
 mount point: mount point relative to the process's root.
@@ -649,10 +649,10 @@ optional fields: zero or more fields of the form "tag[:value]".
 separator: marks the end of the optional fields.
 .TP
 (9)
-file system type: name of file system in the form "type[.subtype]".
+filesystem type: name of filesystem in the form "type[.subtype]".
 .TP
 (10)
-mount source: file system-specific information or "none".
+mount source: filesystem-specific information or "none".
 .TP
 (11)
 super options: per-super block options.
@@ -686,13 +686,13 @@ For more information on mount propagation see:
 in the Linux kernel source tree.
 .TP
 .IR /proc/[pid]/mounts " (since Linux 2.4.19)"
-This is a list of all the file systems currently mounted in the
+This is a list of all the filesystems currently mounted in the
 process's mount namespace.
 The format of this file is documented in
 .BR fstab (5).
 Since kernel version 2.6.15, this file is pollable:
 after opening the file for reading, a change in this file
-(i.e., a file system mount or unmount) causes
+(i.e., a filesystem mount or unmount) causes
 .BR select (2)
 to mark the file descriptor as readable, and
 .BR poll (2)
@@ -718,14 +718,14 @@ The name of the mounted device
 (or "nodevice" if there is no corresponding device).
 .TP
 (2)
-The mount point within the file system tree.
+The mount point within the filesystem tree.
 .TP
 (3)
-The file system type.
+The filesystem type.
 .TP
 (4)
 Optional statistics and configuration information.
-Currently (as at Linux 2.6.26), only NFS file systems export
+Currently (as at Linux 2.6.26), only NFS filesystems export
 information via this field.
 .RE
 .IP
@@ -928,7 +928,7 @@ will change the other with its scaled value.
 .TP
 .I /proc/[pid]/root
 UNIX and Linux support the idea of a per-process root of the
-file system, set by the
+filesystem, set by the
 .BR chroot (2)
 system call.
 This file is a symbolic link that points to the process's
@@ -1347,7 +1347,7 @@ PID of parent process.
 PID of process tracing this process (0 if not being traced).
 .IP *
 .IR Uid ", " Gid :
-Real, effective, saved set, and file system UIDs (GIDs).
+Real, effective, saved set, and filesystem UIDs (GIDs).
 .IP *
 .IR FDSize :
 Number of file descriptor slots currently allocated.
@@ -1577,20 +1577,20 @@ Frame buffer information when
 is defined during kernel compilation.
 .TP
 .I /proc/filesystems
-A text listing of the file systems which are supported by the kernel,
-namely file systems which were compiled into the kernel or whose kernel
+A text listing of the filesystems which are supported by the kernel,
+namely filesystems which were compiled into the kernel or whose kernel
 modules are currently loaded.
 (See also
 .BR filesystems (5).)
-If a file system is marked with "nodev",
+If a filesystem is marked with "nodev",
 this means that it does not require a block device to be mounted
-(e.g., virtual file system, network file system).
+(e.g., virtual filesystem, network filesystem).
 
 Incidentally, this file may be used by
 .BR mount (8)
-when no file system is specified and it didn't manage to determine the
-file system type.
-Then file systems contained in this file are tried
+when no filesystem is specified and it didn't manage to determine the
+filesystem type.
+Then filesystems contained in this file are tried
 (excepted those that are marked with "nodev").
 .TP
 .I /proc/fs
@@ -1961,7 +1961,7 @@ See also
 .TP
 .I /proc/mounts
 Before kernel 2.4.19, this file was a list
-of all the file systems currently mounted on the system.
+of all the filesystems currently mounted on the system.
 With the introduction of per-process mount namespaces in
 Linux 2.4.19, this file became a link to
 .IR /proc/self/mounts ,
@@ -2250,7 +2250,7 @@ root can control bus lockups simulated by the scsi_debug driver.
 .I /proc/self
 This directory refers to the process accessing the
 .I /proc
-file system,
+filesystem,
 and is identical to the
 .I /proc
 directory named by the process ID of the same process.
@@ -2386,7 +2386,7 @@ See also
 This directory (present since 1.3.57) contains a number of files
 and subdirectories corresponding to kernel variables.
 These variables can be read and sometimes modified using
-the \fI/proc\fP file system, and the (deprecated)
+the \fI/proc\fP filesystem, and the (deprecated)
 .BR sysctl (2)
 system call.
 .TP
@@ -2408,7 +2408,7 @@ some systems, it may be empty.
 .TP
 .I /proc/sys/fs
 This directory contains the files and subdirectories for kernel variables
-related to file systems.
+related to filesystems.
 .TP
 .I /proc/sys/fs/binfmt_misc
 Documentation for files in this directory can be found
@@ -2603,9 +2603,9 @@ for details.
 These files
 allow you to change the value of the fixed UID and GID.
 The default is 65534.
-Some file systems support only 16-bit UIDs and GIDs, although in Linux
+Some filesystems support only 16-bit UIDs and GIDs, although in Linux
 UIDs and GIDs are 32 bits.
-When one of these file systems is mounted
+When one of these filesystems is mounted
 with writes enabled, any UID or GID that would exceed 65535 is translated
 to the overflow value before being written to disk.
 .TP
@@ -2637,11 +2637,11 @@ The caller has the
 .BR CAP_FOWNER
 capability.
 .IP *
-The file system UID of the process creating the link matches
+The filesystem UID of the process creating the link matches
 the owner (UID) of the target file
 (as described in
 .BR credentials (7),
-a process's file system UID is normally the same as its effective UID).
+a process's filesystem UID is normally the same as its effective UID).
 .IP *
 All of the following conditions are true:
 .RS 4
@@ -2682,11 +2682,11 @@ When the value in this file is 1, symbolic links are followed only
 in the following circumstances:
 .RS
 .IP * 3
-the file system UID of the process following the link matches
+the filesystem UID of the process following the link matches
 the owner (UID) of the symbolic link
 (as described in
 .BR credentials (7),
-a process's file system UID is normally the same as its effective UID);
+a process's filesystem UID is normally the same as its effective UID);
 .IP *
 the link is not in a sticky world-writable directory; or
 .IP *
@@ -2721,7 +2721,7 @@ or whose binary does not have read permission enabled.
 .TP
 \fI1\ ("debug")\fP
 All processes dump core when possible.
-The core dump is owned by the file system user ID of the dumping process
+The core dump is owned by the filesystem user ID of the dumping process
 and no security is applied.
 This is intended for system debugging situations only.
 Ptrace is unchecked.
@@ -2750,17 +2750,17 @@ does not follow these rules, and no core dump will be produced.
 .I /proc/sys/fs/super-max
 This file
 controls the maximum number of superblocks, and
-thus the maximum number of mounted file systems the kernel
+thus the maximum number of mounted filesystems the kernel
 can have.
 You need increase only
 .I super-max
-if you need to mount more file systems than the current value in
+if you need to mount more filesystems than the current value in
 .I super-max
 allows you to.
 .TP
 .I /proc/sys/fs/super-nr
 This file
-contains the number of file systems currently mounted.
+contains the number of filesystems currently mounted.
 .TP
 .I /proc/sys/kernel
 This directory contains files controlling a range of kernel parameters,
@@ -2775,7 +2775,7 @@ and
 .IR frequency .
 If BSD-style process accounting is enabled these values control
 its behavior.
-If free space on file system where the log lives goes below
+If free space on filesystem where the log lives goes below
 .I lowwater
 percent accounting suspends.
 If free space gets above
@@ -3241,7 +3241,7 @@ manual page for details.
 This directory may be empty.
 .TP
 .I /proc/sys/sunrpc
-This directory supports Sun remote procedure call for network file system
+This directory supports Sun remote procedure call for network filesystem
 (NFS).
 On some systems, it is not present.
 .TP
@@ -3253,7 +3253,7 @@ cache management.
 Writing to this file causes the kernel to drop clean caches, dentries, and
 inodes from memory, causing that memory to become free.
 This can be useful for memory management testing and
-performing reproducible file-system benchmarks.
+performing reproducible filesystem benchmarks.
 Because writing to this file causes the benefits of caching to be lost,
 it can degrade overall system performance.