LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

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 24d01c530c,
"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>
This commit is contained in:
Michael Kerrisk 2013-08-08 10:07:57 +02:00
parent af02f8e60d
commit 9ee4a2b6ec
116 changed files with 541 additions and 541 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man2/mount.2
View File

@ -312,7 +312,7 @@ is set appropriately.
.SH ERRORS
The error values given below result from filesystem type independent
errors.
Each file-system type may have its own special errors and its
Each filesystem type may have its own special errors and its
own special behavior.
See the Linux kernel source code for details.
.TP

2
man2/open.2
View File

@ -451,7 +451,7 @@ in conjunction with mandatory file locks and with file leases, see
.\" Newsgroups: gmane.linux.man, gmane.linux.kernel
.\"
Obtain a file descriptor that can be used for two purposes:
to indicate a location in the file-system tree and
to indicate a location in the filesystem tree and
to perform operations that act purely at the file descriptor level.
The file itself is not opened, and other file operations (e.g.,
.BR read (2),

2
man2/statfs.2
View File

@ -262,7 +262,7 @@ contains some random stuff such that the pair
.RI ( f_fsid , ino )
uniquely determines a file.
Some operating systems use (a variation on) the device number, or the device number
combined with the file-system type.
combined with the filesystem type.
Several OSes restrict giving out the
.I f_fsid
field to the superuser only (and zero it for unprivileged users),

14
man2/sysfs.2
View File

@ -44,14 +44,14 @@ call and the information returned depends on the
in effect:
.TP 3
.B 1
Translate the file-system identifier string
Translate the filesystem identifier string
.I fsname
into a file-system type index.
into a filesystem type index.
.TP
.B 2
Translate the file-system type index
Translate the filesystem type index
.I fs_index
into a null-terminated file-system identifier string.
into a null-terminated filesystem identifier string.
This string will
be written to the buffer pointed to by
.IR buf .
@ -63,11 +63,11 @@ has enough space to accept the string.
Return the total number of filesystem types currently present in the
kernel.
.PP
The numbering of the file-system type indexes begins with zero.
The numbering of the filesystem type indexes begins with zero.
.SH RETURN VALUE
On success,
.BR sysfs ()
returns the file-system index for option
returns the filesystem index for option
.BR 1 ,
zero for option
.BR 2 ,
@ -84,7 +84,7 @@ is outside your accessible address space.
.TP
.B EINVAL
.I fsname
is not a valid file-system type identifier;
is not a valid filesystem type identifier;
.I fs_index
is out-of-bounds;
.I option

2
man2/umount.2
View File

@ -102,7 +102,7 @@ On error, \-1 is returned, and
.I errno
is set appropriately.
.SH ERRORS
The error values given below result from file-system type independent
The error values given below result from filesystem type independent
errors.
Each filesystem type may have its own special errors and its
own special behavior.

4
man4/cciss.4
View File

@ -227,7 +227,7 @@ tape drives with your Smart Array 5xxx controller.
Additionally, note that the driver will not engage the SCSI core at
init time.
The driver must be directed to dynamically engage the SCSI core via
the /proc file-system entry,
the /proc filesystem entry,
which the "block" side of the driver creates as
.I /proc/driver/cciss/cciss*
at run time.
@ -281,7 +281,7 @@ lun used to address each device.
The driver then notifies the SCSI midlayer
of these changes.
Note that the naming convention of the /proc file-system entries
Note that the naming convention of the /proc filesystem entries
contains a number in addition to the driver name
(e.g., "cciss0"
instead of just "cciss", which you might expect).

26
man4/initrd.4
View File

@ -79,7 +79,7 @@ The kernel then can use
contents for a two-phase system boot-up.
.PP
In the first boot-up phase, the kernel starts up
and mounts an initial root file-system from the contents of
and mounts an initial root filesystem from the contents of
.I /dev/initrd
(e.g., RAM disk initialized by the boot loader).
In the second phase, additional drivers or other modules
@ -112,13 +112,13 @@ The kernel then read-write mounts the device
as the initial root filesystem.
.IP 4.
If the indicated normal root filesystem is also the initial
root file-system (e.g.,
root filesystem (e.g.,
.IR /dev/ram0 )
then the kernel skips to the last step for the usual boot sequence.
.IP 5.
If the executable file
.IR /linuxrc
is present in the initial root file-system,
is present in the initial root filesystem,
.I /linuxrc
is executed with UID 0.
(The file
@ -135,8 +135,8 @@ is not executed or when
terminates, the normal root filesystem is mounted.
(If
.I /linuxrc
exits with any file-systems mounted on the initial root
file-system, then the behavior of the kernel is
exits with any filesystems mounted on the initial root
filesystem, then the behavior of the kernel is
.BR UNSPECIFIED .
See the NOTES section for the current kernel behavior.)
.IP 7.
@ -195,7 +195,7 @@ you have to use this command in the
configuration file
.IR /etc/lilo.config .
The filename specified with this
option will typically be a gzipped file-system image.
option will typically be a gzipped filesystem image.
.TP
.I noinitrd
This boot option disables the two-phase boot-up operation.
@ -225,7 +225,7 @@ can be used as an option line in the
configuration file
.IR /etc/lilo.config .
The device specified by the this option must be a mountable
device having a suitable root file-system.
device having a suitable root filesystem.
.\"
.\"
.\"
@ -325,13 +325,13 @@ The loader program boots from floppy or other media with a minimal kernel
(e.g., support for
.IR /dev/ram ,
.IR /dev/initrd ,
and the ext2 file-system) and loads
and the ext2 filesystem) and loads
.IR /dev/initrd
with a gzipped version of the initial file-system.
with a gzipped version of the initial filesystem.
.IP 2.
The executable
.I /linuxrc
determines what is needed to (1) mount the normal root file-system
determines what is needed to (1) mount the normal root filesystem
(i.e., device type, device drivers, filesystem) and (2) the
distribution media (e.g., CD-ROM, network, tape, ...).
This can be done by asking the user, by auto-probing,
@ -339,7 +339,7 @@ or by using a hybrid approach.
.IP 3.
The executable
.I /linuxrc
loads the necessary modules from the initial root file-system.
loads the necessary modules from the initial root filesystem.
.IP 4.
The executable
.I /linuxrc
@ -393,7 +393,7 @@ file or a file executed by
would be different.
.PP
A third scenario is more convenient recovery disks.
Because information like the location of the root file-system
Because information like the location of the root filesystem
partition is not needed at boot time, the system loaded from
.I /dev/initrd
can use a dialog and/or auto-detection followed by a
@ -447,7 +447,7 @@ will
.B not
be fully unmounted if
.I /dev/ram0
is used by any process or has any file-system mounted on it.
is used by any process or has any filesystem mounted on it.
If
.IR /dev/ram0
is

6
man5/filesystems.5
View File

@ -26,7 +26,7 @@
.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
@ -144,7 +144,7 @@ Linux supports High Sierra, the precursor to the ISO 9660 standard for
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
@ -155,7 +155,7 @@ file system 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

2
man5/proc.5
View File

@ -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.

2
man7/capabilities.7
View File

@ -391,7 +391,7 @@ perform various privileged block-device
.BR ioctl (2)
operations;
.IP *
perform various privileged file-system
perform various privileged filesystem
.BR ioctl (2)
operations;
.IP *

18
man7/cpuset.7
View File

@ -26,7 +26,7 @@
.SH NAME
cpuset \- confine processes to processor and memory node subsets
.SH DESCRIPTION
The cpuset file system is a pseudo-file-system interface
The cpuset filesystem is a pseudo-filesystem interface
to the kernel cpuset mechanism,
which is used to control the processor placement
and memory placement of processes.
@ -69,7 +69,7 @@ and any cpuset that is the child (descendant) of
another parent cpuset contains a subset of that parent's
CPUs and memory nodes.
The directories and files representing cpusets have normal
file-system permissions.
filesystem permissions.
.PP
Every process in the system belongs to exactly one cpuset.
A process is confined to run only on the CPUs in
@ -305,7 +305,7 @@ See the
.IR cpuset.memory_spread_page " (since Linux 2.6.17)"
Flag (0 or 1).
If set (1), pages in the kernel page cache
(file-system buffers) are uniformly spread across the cpuset.
(filesystem buffers) are uniformly spread across the cpuset.
By default this is off (0) in the top cpuset,
and inherited from the parent cpuset in
newly created cpusets.
@ -580,7 +580,7 @@ times 1000.
.\" ================== Memory Spread ==================
.SS Memory spread
There are two Boolean flag files per cpuset that control where the
kernel allocates pages for the file-system buffers and related
kernel allocates pages for the filesystem buffers and related
in-kernel data structures.
They are called
.I cpuset.memory_spread_page
@ -590,14 +590,14 @@ and
If the per-cpuset Boolean flag file
.I cpuset.memory_spread_page
is set, then
the kernel will spread the file-system buffers (page cache) evenly
the kernel will spread the filesystem buffers (page cache) evenly
over all the nodes that the faulting process is allowed to use, instead
of preferring to put those pages on the node where the process is running.
.PP
If the per-cpuset Boolean flag file
.I cpuset.memory_spread_slab
is set,
then the kernel will spread some file-system-related slab caches,
then the kernel will spread some filesystem-related slab caches,
such as those for inodes and directory entries, evenly over all the nodes
that the faulting process is allowed to use, instead of preferring to
put those pages on the node where the process is running.
@ -652,7 +652,7 @@ need to place thread-local data on
memory nodes close to the CPUs which are running the threads that most
frequently access that data; but also
.IP b)
need to access large file-system data sets that must to be spread
need to access large filesystem data sets that must to be spread
across the several nodes in the job's cpuset in order to fit.
.PP
Without this policy,
@ -978,7 +978,7 @@ or
file.
.PP
There is one minor difference between the manner in which these
permissions are evaluated and the manner in which normal file-system
permissions are evaluated and the manner in which normal filesystem
operation permissions are evaluated.
The kernel interprets
relative pathnames starting at a process's current working directory.
@ -996,7 +996,7 @@ to its cpuset directory beneath
.IR /dev/cpuset ,
which is a bit unusual)
or if some user code converts the relative cpuset path to a
full file-system path.
full filesystem path.
.PP
In theory, this means that user code should specify cpusets
using absolute pathnames, which requires knowing the mount point of

2
man7/uri.7
View File

@ -689,7 +689,7 @@ loading the files onto a local file system).
A future URI scheme may be added (e.g., "userdoc:") to permit
programs to include cross-references to more detailed documentation
without having to know the exact location of that documentation.
Alternatively, a future version of the file-system specification may
Alternatively, a future version of the filesystem specification may
specify file locations sufficiently so that the file: scheme will
be able to locate documentation.
.PP