.SS Disks and filesystems
The command
.I mount
-will attach the file system found on some disk (or floppy, or CDROM or so)
-to the big file system hierarchy.
+will attach the filesystem found on some disk (or floppy, or CDROM or so)
+to the big filesystem hierarchy.
And
.I umount
detaches it again.
.B "I/O"
.TP
.B %I
-Number of file system inputs by the process.
+Number of filesystem inputs by the process.
.TP
.B %O
-Number of file system outputs by the process.
+Number of filesystem outputs by the process.
.TP
.B %r
Number of socket messages received by the process.
is not, in fact, a directory.
.TP
.B EROFS
-Write permission was requested for a file on a read-only file system.
+Write permission was requested for a file on a read-only filesystem.
.PP
.BR access ()
may fail if:
call will still fail.
.PP
.BR access ()
-may not work correctly on NFS file systems with UID mapping enabled,
+may not work correctly on NFS filesystems with UID mapping enabled,
because UID mapping is done on the server and hidden from the client,
which checks permissions.
Similar problems can occur to FUSE mounts.
.B MS_NOEXEC
flag if it was used to
.BR mount (2)
-the underlying file system.
+the underlying filesystem.
Since kernel 2.6.20,
.BR access ()
honors this flag.
.TP
.B EROFS
.I filename
-refers to a file on a read-only file system.
+refers to a file on a read-only filesystem.
.TP
.B EUSERS
There are no more free file structures or we ran out of memory.
.SH NOTES
These system calls are gone;
they existed only in Linux 2.5.36 through to 2.5.54.
-Now the hugetlbfs file system can be used instead.
+Now the hugetlbfs filesystem can be used instead.
Memory backed by huge pages (if the CPU supports them) is obtained by
using
.BR mmap (2)
-to map files in this virtual file system.
+to map files in this virtual filesystem.
.LP
The maximal number of huge pages can be specified using the
.B hugepages=
A component of the path prefix is not a directory.
.TP
.B EROFS
-The socket inode would reside on a read-only file system.
+The socket inode would reside on a read-only filesystem.
.SH CONFORMING TO
SVr4, 4.4BSD, POSIX.1-2001
.RB ( bind ()
.I errno
is set appropriately.
.SH ERRORS
-Depending on the file system, other errors can be returned.
+Depending on the filesystem, other errors can be returned.
The more
general errors for
.BR chdir ()
bit will be turned off,
but this will not cause an error to be returned.
-As a security measure, depending on the file system,
+As a security measure, depending on the filesystem,
the set-user-ID and set-group-ID execution bits
may be turned off if a file is written.
(On Linux this occurs if the writing process does not have the
.B CAP_FSETID
capability.)
-On some file systems, only the superuser can set the sticky bit,
+On some filesystems, only the superuser can set the sticky bit,
which may have a special meaning.
For the sticky bit, and for set-user-ID and set-group-ID bits on
directories, see
.BR stat (2).
-On NFS file systems, restricting the permissions will immediately influence
+On NFS filesystems, restricting the permissions will immediately influence
already open files, because the access control is done on the server, but
open files are maintained by the client.
Widening the permissions may be
.I errno
is set appropriately.
.SH ERRORS
-Depending on the file system, other errors can be returned.
+Depending on the filesystem, other errors can be returned.
The more general errors for
.BR chmod ()
are listed below:
capability).
.TP
.B EROFS
-The named file resides on a read-only file system.
+The named file resides on a read-only filesystem.
.PP
The general errors for
.BR fchmod ()
.I errno
is set appropriately.
.SH ERRORS
-Depending on the file system, other errors can be returned.
+Depending on the filesystem, other errors can be returned.
The more general errors for
.BR chown ()
are listed below.
(see above) to change owner and/or group.
.TP
.B EROFS
-The named file resides on a read-only file system.
+The named file resides on a read-only filesystem.
.PP
The general errors for
.BR fchown ()
.BR open (2)
or
.BR mkdir (2)),
-its owner is made the same as the file system user ID of the
+its owner is made the same as the filesystem user ID of the
creating process.
The group of the file depends on a range of factors,
-including the type of file system,
-the options used to mount the file system,
+including the type of filesystem,
+the options used to mount the filesystem,
and whether or not the set-group-ID permission bit is enabled
on the parent directory.
-If the file system supports the
+If the filesystem supports the
.I "\-o\ grpid"
(or, synonymously
.IR "\-o\ bsdgroups" )
.BR mount (8)
options, then the rules are as follows:
.IP * 2
-If the file system is mounted with
+If the filesystem is mounted with
.IR "\-o\ grpid" ,
then the group of a new file is made
the same as that of the parent directory.
.IP *
-If the file system is mounted with
+If the filesystem is mounted with
.IR "\-o\ nogrpid"
and the set-group-ID bit is disabled on the parent directory,
then the group of a new file is made the same as the
-process's file system GID.
+process's filesystem GID.
.IP *
-If the file system is mounted with
+If the filesystem is mounted with
.IR "\-o\ nogrpid"
and the set-group-ID bit is enabled on the parent directory,
then the group of a new file is made
and
.IR "\-o\ nogrpid"
mount options are supported by ext2, ext3, ext4, and XFS.
-File systems that don't support these mount options follow the
+Filesystems that don't support these mount options follow the
.IR "\-o\ nogrpid"
rules.
.PP
The
.BR chown ()
-semantics are deliberately violated on NFS file systems
+semantics are deliberately violated on NFS filesystems
which have UID mapping enabled.
Additionally, the semantics of all system
calls which access the file contents are violated, because
.I errno
is set appropriately.
.SH ERRORS
-Depending on the file system, other errors can be returned.
+Depending on the filesystem, other errors can be returned.
The more general errors are listed below:
.TP
.B EACCES
.BR CLONE_FS " (since Linux 2.0)"
If
.B CLONE_FS
-is set, the caller and the child process share the same file system
+is set, the caller and the child process share the same filesystem
information.
-This includes the root of the file system, the current
+This includes the root of the filesystem, the current
working directory, and the umask.
Any call to
.BR chroot (2),
If
.B CLONE_FS
-is not set, the child process works on a copy of the file system
+is not set, the child process works on a copy of the filesystem
information of the calling process at the time of the
.BR clone ()
call.
.PP
A successful close does not guarantee that the data has been successfully
saved to disk, as the kernel defers writes.
-It is not common for a file system
+It is not common for a filesystem
to flush the buffers when the stream is closed.
If you need to be sure that
the data is physically stored use
If the set-user-ID bit is set on the program file pointed to by
\fIfilename\fP,
-and the underlying file system is not mounted
+and the underlying filesystem is not mounted
.I nosuid
(the
.B MS_NOSUID
Execute permission is denied for the file or a script or ELF interpreter.
.TP
.B EACCES
-The file system is mounted
+The filesystem is mounted
.IR noexec .
.TP
.B EFAULT
or a script or ELF interpreter is not a directory.
.TP
.B EPERM
-The file system is mounted
+The filesystem is mounted
.IR nosuid ,
the user is not the superuser,
and the file has the set-user-ID or set-group-ID bit set.
Linux ignores the set-user-ID and set-group-ID bits on scripts.
-The result of mounting a file system
+The result of mounting a filesystem
.I nosuid
varies across Linux kernel versions:
some will refuse execution of set-user-ID and set-group-ID
and continuing for
.I len
bytes.
-Within the specified range, partial file system blocks are zeroed,
-and whole file system blocks are removed from the file.
+Within the specified range, partial filesystem blocks are zeroed,
+and whole filesystem blocks are removed from the file.
After a successful call,
subsequent reads from this range will return zeroes.
.BR stat (2))
does not change.
-Not all file systems support
+Not all filesystems support
.BR FALLOC_FL_PUNCH_HOLE ;
-if a file system doesn't support the operation, an error is returned.
+if a filesystem doesn't support the operation, an error is returned.
.SH RETURN VALUE
On success,
.BR fallocate ()
was less than or equal to 0.
.TP
.B EIO
-An I/O error occurred while reading from or writing to a file system.
+An I/O error occurred while reading from or writing to a filesystem.
.TP
.B ENODEV
.I fd
.BR fallocate ().
.TP
.B EOPNOTSUPP
-The file system containing the file referred to by
+The filesystem containing the file referred to by
.I fd
does not support this operation;
or the
.I mode
-is not supported by the file system containing the file referred to by
+is not supported by the filesystem containing the file referred to by
.IR fd .
.TP
.B EPERM
.BR EAGAIN .
To make use of mandatory locks, mandatory locking must be enabled
-both on the file system that contains the file to be locked,
+both on the filesystem that contains the file to be locked,
and on the file itself.
-Mandatory locking is enabled on a file system
+Mandatory locking is enabled on a filesystem
using the "\-o mand" option to
.BR mount (8),
or the
.P
Leases may be taken out only on regular files.
An unprivileged process may take out a lease only on a file whose
-UID (owner) matches the file system UID of the process.
+UID (owner) matches the filesystem UID of the process.
A process with the
.B CAP_LEASE
capability may take out leases on arbitrary files.
.I inotify
interface (available since kernel 2.6.13),
which provides a much superior interface for obtaining notifications of
-file system events.
+filesystem events.
See
.BR inotify (7).
.SS Changing the capacity of a pipe
Currently,
.\" kernel 2.6.27
.\" The same sentence is in readdir.2
-only some file systems (among them: Btrfs, ext2, ext3, and ext4)
+only some filesystems (among them: Btrfs, ext2, ext3, and ext4)
have full support for returning the file type in
.IR d_type .
All applications must properly handle a return of
The original Linux
.BR getdents ()
-system call did not handle large file systems and large file offsets.
+system call did not handle large filesystems and large file offsets.
Consequently, Linux 2.4 added
.BR getdents64 (),
with wider types for the
.\" On some systems, this is the number of swaps out of physical memory.
.TP
.IR ru_inblock " (since Linux 2.6.22)"
-The number of times the file system had to perform input.
+The number of times the filesystem had to perform input.
.TP
.IR ru_oublock " (since Linux 2.6.22)"
-The number of times the file system had to perform output.
+The number of times the filesystem had to perform output.
.TP
.IR ru_msgsnd " (unmaintained)"
This field is currently unused on Linux.
.I name
and associated with the given
.I path
-in the file system.
+in the filesystem.
The length of the attribute
.I value
is returned.
.IR <attr/xattr.h> .)
.TP
.B ENOTSUP
-Extended attributes are not supported by the file system, or are disabled.
+Extended attributes are not supported by the filesystem, or are disabled.
.TP
.B ERANGE
The
but reads the module to be loaded from the file descriptor
.IR fd .
It is useful when the authenticity of a kernel module
-can be determined from its location in the file system;
+can be determined from its location in the filesystem;
in cases where that is possible,
the overhead of using cryptographically signed modules to
determine the authenticity of a module can be avoided.
.I inotify_event
structures (see
.BR inotify (7))
-indicating file system events;
+indicating filesystem events;
the watch descriptor inside this structure identifies
the object for which the event occurred.
.SH RETURN VALUE
One can view the current I/O scheduler via the
.I /sys
-file system.
+filesystem.
For example, the following command
displays a list of all schedulers currently loaded in the kernel:
.sp
are ignored.
.TP
.BR KCMP_FS
-Check whether the processes share the same file system information
-(i.e., file mode creation mask, working directory, and file system root).
+Check whether the processes share the same filesystem information
+(i.e., file mode creation mask, working directory, and filesystem root).
The arguments
.I idx1
and
The alternative to this system call would have been to expose suitable
process information via the
.BR proc (5)
-file system; this was deemed to be unsuitable for security reasons.
+filesystem; this was deemed to be unsuitable for security reasons.
See
.BR clone (2)
.BR path_resolution (7).)
.TP
.B EDQUOT
-The user's quota of disk blocks on the file system has been exhausted.
+The user's quota of disk blocks on the filesystem has been exhausted.
.TP
.B EEXIST
.I newpath
is a directory.
.TP
.B EPERM
-The file system containing
+The filesystem containing
.IR oldpath " and " newpath
does not support the creation of hard links.
.TP
.BR proc (5)).
.TP
.B EROFS
-The file is on a read-only file system.
+The file is on a read-only filesystem.
.TP
.B EXDEV
.IR oldpath " and " newpath
-are not on the same mounted file system.
-(Linux permits a file system to be mounted at multiple points, but
+are not on the same mounted filesystem.
+(Linux permits a filesystem to be mounted at multiple points, but
.BR link ()
does not work across different mount points,
-even if the same file system is mounted on both.)
+even if the same filesystem is mounted on both.)
.SH CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES).
.\" SVr4 documents additional ENOLINK and
.SH NOTES
Hard links, as created by
.BR link (),
-cannot span file systems.
+cannot span filesystems.
Use
.BR symlink (2)
if this is required.
creating a link, see
.BR linkat (2).
.SH BUGS
-On NFS file systems, the return code may be wrong in case the NFS server
+On NFS filesystems, the return code may be wrong in case the NFS server
performs the link creation and dies before it can say so.
Use
.BR stat (2)
retrieves the list
of extended attribute names associated with the given
.I path
-in the file system.
+in the filesystem.
The retrieved list is placed in
.IR list ,
a caller-allocated buffer whose size (in bytes) is specified in the argument
.SH ERRORS
.TP
.B ENOTSUP
-Extended attributes are not supported by the file system, or are disabled.
+Extended attributes are not supported by the filesystem, or are disabled.
.TP
.B ERANGE
The
For the purposes of these operations, a hole is a sequence of zeros that
(normally) has not been allocated in the underlying file storage.
-However, a file system is not obliged to report holes,
+However, a filesystem is not obliged to report holes,
so these operations are not a guaranteed mechanism for
mapping the storage space actually allocated to a file.
(Furthermore, a sequence of zeros that actually has been written
to the underlying storage may not be reported as a hole.)
In the simplest implementation,
-a file system can support the operations by making
+a filesystem can support the operations by making
.BR SEEK_HOLE
always return the offset of the end of the file,
and making
Or: the resulting file offset would be negative,
or beyond the end of a seekable device.
.\" Some systems may allow negative offsets for character devices
-.\" and/or for remote file systems.
+.\" and/or for remote filesystems.
.TP
.B EOVERFLOW
.\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
and its associated backing store.
Currently,
.\" 2.6.18-rc5
-only shmfs/tmpfs supports this; other file systems return with the
+only shmfs/tmpfs supports this; other filesystems return with the
error
.BR ENOSYS .
.\" Databases want to use this feature to drop a section of their
The newly created directory will be owned by the effective user ID of the
process.
If the directory containing the file has the set-group-ID
-bit set, or if the file system is mounted with BSD group semantics
+bit set, or if the filesystem is mounted with BSD group semantics
.RI ( "mount -o bsdgroups"
or, synonymously
.IR "mount -o grpid" ),
.BR path_resolution (7).)
.TP
.B EDQUOT
-The user's quota of disk blocks or inodes on the file system has been
+The user's quota of disk blocks or inodes on the filesystem has been
exhausted.
.TP
.B EEXIST
is not, in fact, a directory.
.TP
.B EPERM
-The file system containing
+The filesystem containing
.I pathname
does not support the creation of directories.
.TP
.B EROFS
.I pathname
-refers to a file on a read-only file system.
+refers to a file on a read-only filesystem.
.SH CONFORMING TO
SVr4, BSD, POSIX.1-2001.
.\" SVr4 documents additional EIO, EMULTIHOP
.SH DESCRIPTION
The system call
.BR mknod ()
-creates a file system node (file, device special file or
+creates a filesystem node (file, device special file or
named pipe) named
.IR pathname ,
with attributes specified by
The newly created node will be owned by the effective user ID of the
process.
If the directory containing the node has the set-group-ID
-bit set, or if the file system is mounted with BSD group semantics, the
+bit set, or if the filesystem is mounted with BSD group semantics, the
new node will inherit the group ownership from its parent directory;
otherwise it will be owned by the effective group ID of the process.
.SH RETURN VALUE
.BR path_resolution (7).)
.TP
.B EDQUOT
-The user's quota of disk blocks or inodes on the file system has been
+The user's quota of disk blocks or inodes on the filesystem has been
exhausted.
.TP
.B EEXIST
.\" For UNIX domain sockets and regular files, EPERM is returned only in
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
.\" use mknod() to make these files.
-also returned if the file system containing
+also returned if the filesystem containing
.I pathname
does not support the type of node requested.
.TP
.B EROFS
.I pathname
-refers to a file on a read-only file system.
+refers to a file on a read-only filesystem.
.SH CONFORMING TO
SVr4, 4.4BSD, POSIX.1-2001 (but see below).
.\" The Linux version differs from the SVr4 version in that it
.\" A file could not be mapped for reading.
.TP
.B ENODEV
-The underlying file system of the specified file does not support
+The underlying filesystem of the specified file does not support
memory mapping.
.TP
.B ENOMEM
.I prot
argument asks for
.B PROT_EXEC
-but the mapped area belongs to a file on a file system that
+but the mapped area belongs to a file on a filesystem that
was mounted no-exec.
.\" (Since 2.4.25 / 2.6.0.)
.TP
.\"
.TH MOUNT 2 2012-07-05 "Linux" "Linux Programmer's Manual"
.SH NAME
-mount \- mount file system
+mount \- mount filesystem
.SH SYNOPSIS
.nf
.B "#include <sys/mount.h>"
.fi
.SH DESCRIPTION
.BR mount ()
-attaches the file system specified by
+attaches the filesystem specified by
.I source
(which is often a device name, but can also be a directory name
or a dummy) to the directory specified by
Appropriate privilege (Linux: the
.B CAP_SYS_ADMIN
-capability) is required to mount file systems.
+capability) is required to mount filesystems.
-Since Linux 2.4 a single file system can be visible at
+Since Linux 2.4 a single filesystem can be visible at
multiple mount points, and multiple mounts can be stacked
on the same mount point.
.\" Multiple mounts on same mount point: since 2.3.99pre7.
.BR MS_BIND " (Linux 2.4 onward)"
.\" since 2.4.0-test9
Perform a bind mount, making a file or a directory subtree visible at
-another point within a file system.
-Bind mounts may cross file system boundaries and span
+another point within a filesystem.
+Bind mounts may cross filesystem boundaries and span
.BR chroot (2)
jails.
The
the underlying mount point).
.TP
.BR MS_DIRSYNC " (since Linux 2.5.19)"
-Make directory changes on this file system synchronous.
+Make directory changes on this filesystem synchronous.
(This property can be obtained for individual directories
or subtrees using
.BR chattr (1).)
.TP
.B MS_MANDLOCK
-Permit mandatory locking on files in this file system.
+Permit mandatory locking on files in this filesystem.
(Mandatory locking must still be enabled on a per-file basis,
as described in
.BR fcntl (2).)
arguments are ignored.
.TP
.B MS_NOATIME
-Do not update access times for (all types of) files on this file system.
+Do not update access times for (all types of) files on this filesystem.
.TP
.B MS_NODEV
-Do not allow access to devices (special files) on this file system.
+Do not allow access to devices (special files) on this filesystem.
.TP
.B MS_NODIRATIME
-Do not update access times for directories on this file system.
+Do not update access times for directories on this filesystem.
This flag provides a subset of the functionality provided by
.BR MS_NOATIME ;
that is,
.BR MS_NODIRATIME .
.TP
.B MS_NOEXEC
-Do not allow programs to be executed from this file system.
-.\" (Possibly useful for a file system that contains non-Linux executables.
+Do not allow programs to be executed from this filesystem.
+.\" (Possibly useful for a filesystem that contains non-Linux executables.
.\" Often used as a security feature, e.g., to make sure that restricted
.\" users cannot execute files uploaded using ftp or so.)
.TP
.B MS_NOSUID
Do not honor set-user-ID and set-group-ID bits when executing
-programs from this file system.
+programs from this filesystem.
.\" (This is a security feature to prevent users executing set-user-ID and
.\" set-group-ID programs from removable disk devices.)
.TP
.B MS_RDONLY
-Mount file system read-only.
+Mount filesystem read-only.
.\"
.\" FIXME Document MS_REC, available since 2.4.11.
.\" This flag has meaning in conjunction with MS_BIND and
.\" also with the shared subtree flags.
.TP
.BR MS_RELATIME " (Since Linux 2.6.20)"
-When a file on this file system is accessed,
+When a file on this filesystem is accessed,
update the file's last access time (atime) only if the current value
of atime is less than or equal to the file's last modification time (mtime)
or last status change time (ctime).
.I mountflags
and
.I data
-of an existing mount without having to unmount and remount the file system.
+of an existing mount without having to unmount and remount the filesystem.
.I target
should be the same value specified in the initial
.BR mount ()
.TP
.BR MS_STRICTATIME " (Since Linux 2.6.30)"
Always update the last access time (atime) when files on this
-file system are accessed.
+filesystem are accessed.
(This was the default behavior before Linux 2.6.30.)
Specifying this flag overrides the effect of setting the
.BR MS_NOATIME
flags.
.TP
.B MS_SYNCHRONOUS
-Make writes on this file system synchronous (as though
+Make writes on this filesystem synchronous (as though
the
.B O_SYNC
flag to
.BR open (2)
-was specified for all file opens to this file system).
+was specified for all file opens to this filesystem).
.PP
From Linux 2.4 onward, the
.BR MS_NODEV ", " MS_NOEXEC ", and " MS_NOSUID
.PP
The
.I data
-argument is interpreted by the different file systems.
+argument is interpreted by the different filesystems.
Typically it is a string of comma-separated options
-understood by this file system.
+understood by this filesystem.
See
.BR mount (8)
for details of the options available for each filesystem type.
.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
A component of a path was not searchable.
(See also
.BR path_resolution (7).)
-Or, mounting a read-only file system was attempted without giving the
+Or, mounting a read-only filesystem was attempted without giving the
.B MS_RDONLY
flag.
Or, the block device
.I source
-is located on a file system mounted with the
+is located on a filesystem mounted with the
.B MS_NODEV
option.
.\" mtk: Probably: write permission is required for MS_BIND, with
was added to \fI<mman.h>\fP.
.LP
Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
-on a file system mounted with
+on a filesystem mounted with
.B MS_NOSUID
would fail with
.BR EPERM .
.SS Per-process namespaces
Starting with kernel 2.4.19, Linux provides
per-process mount namespaces.
-A mount namespace is the set of file system mounts that
+A mount namespace is the set of filesystem mounts that
are visible to a process.
Mount-point namespaces can be (and usually are)
shared between multiple processes,
.B -EIO
Unable to write back a page.
The page has to be written back
-in order to move it since the page is dirty and the file system
+in order to move it since the page is dirty and the filesystem
does not provide a migration function that would allow the move
of dirty pages.
.TP
.B -EINVAL
A dirty page cannot be moved.
-The file system does not
+The filesystem does not
provide a migration function and has no ability to write back pages.
.TP
.B -ENOENT
operations are used by the
.BR ipcs (1)
program to provide information on allocated resources.
-In the future these may modified or moved to a /proc file system
+In the future these may modified or moved to a /proc filesystem
interface.
Various fields in the \fIstruct msqid_ds\fP were
#define NFSCTL_SVC 0 /* This is a server process. */
#define NFSCTL_ADDCLIENT 1 /* Add an NFS client. */
#define NFSCTL_DELCLIENT 2 /* Remove an NFS client. */
-#define NFSCTL_EXPORT 3 /* Export a file system. */
-#define NFSCTL_UNEXPORT 4 /* Unexport a file system. */
+#define NFSCTL_EXPORT 3 /* Export a filesystem. */
+#define NFSCTL_UNEXPORT 4 /* Unexport a filesystem. */
#define NFSCTL_UGIDUPDATE 5 /* Update a client's UID/GID map
(only in Linux 2.4.x and earlier). */
#define NFSCTL_GETFH 6 /* Get a file handle (used by mountd)
as if with
.BR lseek (2).
.B O_APPEND
-may lead to corrupted files on NFS file systems if more than one process
+may lead to corrupted files on NFS filesystems if more than one process
appends data to a file at once.
.\" For more background, see
.\" http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453946
of the process.
The group ownership (group ID) is set either to
the effective group ID of the process or to the group ID of the
-parent directory (depending on file system type and mount options,
+parent directory (depending on filesystem type and mount options,
and the mode of the parent directory, see the mount options
.I bsdgroups
and
and need to avoid reliance on NFS support for
.BR O_EXCL ,
can create a unique file on
-the same file system (e.g., incorporating hostname and PID), and use
+the same filesystem (e.g., incorporating hostname and PID), and use
.BR link (2)
to make a link to the lockfile.
If
.BR read (2).
This flag is intended for use by indexing or backup programs,
where its use can significantly reduce the amount of disk activity.
-This flag may not be effective on all file systems.
+This flag may not be effective on all filesystems.
One example is NFS, where the server maintains the access time.
.\" The O_NOATIME flag also affects the treatment of st_atime
.\" by mmap() and readdir(2), MTK, Dec 04.
.\" 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),
Where
.B O_CREAT
is specified, the file does not exist, and the user's quota of disk
-blocks or inodes on the file system has been exhausted.
+blocks or inodes on the filesystem has been exhausted.
.TP
.B EEXIST
.I pathname
The
.B O_NOATIME
flag was specified, but the effective user ID of the caller
-.\" Strictly speaking, it's the file system UID... (MTK)
+.\" Strictly speaking, it's the filesystem UID... (MTK)
did not match the owner of the file and the caller was not privileged
.RB ( CAP_FOWNER ).
.TP
.B EROFS
.I pathname
-refers to a file on a read-only file system and write access was
+refers to a file on a read-only filesystem and write access was
requested.
.TP
.B ETXTBSY
.B O_RSYNC
to the same numerical value as
.BR O_SYNC .
-Most Linux file systems don't actually implement the POSIX
+Most Linux filesystems don't actually implement the POSIX
.B O_SYNC
semantics, which require all metadata updates of a write
to be on disk on returning to user space, but only the
.BR mknod (2)
instead.
.LP
-On NFS file systems with UID mapping enabled,
+On NFS filesystems with UID mapping enabled,
.BR open ()
may
return a file descriptor but, for example,
flag may impose alignment restrictions on the length and address
of user-space buffers and the file offset of I/Os.
In Linux alignment
-restrictions vary by file system and kernel version and might be
+restrictions vary by filesystem and kernel version and might be
absent entirely.
-However there is currently no file system\-independent
+However there is currently no filesystem\-independent
interface for an application to discover these restrictions for a given
-file or file system.
-Some file systems provide their own interfaces
+file or filesystem.
+Some filesystems provide their own interfaces
for doing so, for example the
.B XFS_IOC_DIOINFO
operation in
.LP
Under Linux 2.4, transfer sizes, and the alignment of the user buffer
and the file offset must all be multiples of the logical block size
-of the file system.
+of the filesystem.
Under Linux 2.6, alignment to 512-byte boundaries suffices.
.LP
.B O_DIRECT
.B O_DIRECT
support was added under Linux in kernel version 2.4.10.
Older Linux kernels simply ignore this flag.
-Some file systems may not implement the flag and
+Some filesystems may not implement the flag and
.BR open ()
will fail with
.B EINVAL
.B O_DIRECT
and normal I/O to the same file,
and especially to overlapping byte regions in the same file.
-Even when the file system correctly handles the coherency issues in
+Even when the filesystem correctly handles the coherency issues in
this situation, overall I/O throughput is likely to be slower than
using either mode alone.
Likewise, applications should avoid mixing
.LP
The behaviour of
.B O_DIRECT
-with NFS will differ from local file systems.
+with NFS will differ from local filesystems.
Older kernels, or
kernels configured in certain ways, may not support this combination.
The NFS protocol does not support passing the flag to the server, so
.\"
.TH PIVOT_ROOT 2 2012-07-13 "Linux" "Linux Programmer's Manual"
.SH NAME
-pivot_root \- change the root file system
+pivot_root \- change the root filesystem
.SH SYNOPSIS
.BI "int pivot_root(const char *" new_root ", const char *" put_old );
There is no glibc wrapper for this system call; see NOTES.
.SH DESCRIPTION
.BR pivot_root ()
-moves the root file system of the calling process to the
-directory \fIput_old\fP and makes \fInew_root\fP the new root file system
+moves the root filesystem of the calling process to the
+directory \fIput_old\fP and makes \fInew_root\fP the new root filesystem
of the calling process.
.\"
.\" The
The typical use of
.BR pivot_root ()
is during system startup, when the
-system mounts a temporary root file system (e.g., an \fBinitrd\fP), then
-mounts the real root file system, and eventually turns the latter into
+system mounts a temporary root filesystem (e.g., an \fBinitrd\fP), then
+mounts the real root filesystem, and eventually turns the latter into
the current root of all relevant processes or threads.
.BR pivot_root ()
is necessary in order to prevent kernel threads from keeping the old
root directory busy with their root and current working directory,
even if they never access
-the file system in any way.
+the filesystem in any way.
In the future, there may be a mechanism for
-kernel threads to explicitly relinquish any access to the file system,
+kernel threads to explicitly relinquish any access to the filesystem,
such that this fairly intrusive mechanism can be removed from
.BR pivot_root ().
.IP \- 3
They must be directories.
.IP \- 3
-\fInew_root\fP and \fIput_old\fP must not be on the same file system as
+\fInew_root\fP and \fIput_old\fP must not be on the same filesystem as
the current root.
.IP \- 3
\fIput_old\fP must be underneath \fInew_root\fP, that is, adding a nonzero
number of \fI/..\fP to the string pointed to by \fIput_old\fP must yield
the same directory as \fInew_root\fP.
.IP \- 3
-No other file system may be mounted on \fIput_old\fP.
+No other filesystem may be mounted on \fIput_old\fP.
.PP
See also
.BR pivot_root (8)
or
.BR pivot_root (),
see also below), not the old root directory, but the
-mount point of that file system is mounted on \fIput_old\fP.
+mount point of that filesystem is mounted on \fIput_old\fP.
\fInew_root\fP does not have to be a mount point.
In this case,
-\fI/proc/mounts\fP will show the mount point of the file system containing
+\fI/proc/mounts\fP will show the mount point of the filesystem containing
\fInew_root\fP as root (\fI/\fP).
.SH RETURN VALUE
On success, zero is returned.
Additionally, it may return:
.TP
.B EBUSY
-\fInew_root\fP or \fIput_old\fP are on the current root file system,
-or a file system is already mounted on \fIput_old\fP.
+\fInew_root\fP or \fIput_old\fP are on the current root filesystem,
+or a filesystem is already mounted on \fIput_old\fP.
.TP
.B EINVAL
\fIput_old\fP is not underneath \fInew_root\fP.
.SH DESCRIPTION
.LP
The quota system can be used to set per-user and per-group limits on the
-amount of disk space used on a file system.
+amount of disk space used on a filesystem.
For each user and/or group,
-a soft limit and a hard limit can be set for each file system.
+a soft limit and a hard limit can be set for each filesystem.
The hard limit can't be exceeded.
The soft limit can be exceeded, but warnings will ensue.
Moreover, the user can't exceed the soft limit for more than one week
The
.I special
argument is a pointer to a null-terminated string containing the pathname
-of the (mounted) block special device for the file system being manipulated.
+of the (mounted) block special device for the filesystem being manipulated.
The
.I addr
value is one of the following:
.TP 8
.B Q_QUOTAON
-Turn on quotas for a file system.
+Turn on quotas for a filesystem.
The
.I id
argument is the identification number of the quota format to be used.
The
.IR addr
argument points to the pathname of a file containing the quotas for
-the file system.
+the filesystem.
The quota file must exist; it is normally created with the
.BR quotacheck (8)
program.
.RB ( CAP_SYS_ADMIN ).
.TP 8
.B Q_QUOTAOFF
-Turn off quotas for a file system.
+Turn off quotas for a filesystem.
The
.I addr
and
.RB ( CAP_SYS_ADMIN ).
.TP
.B Q_GETFMT
-Get quota format used on the specified file system.
+Get quota format used on the specified filesystem.
The
.I addr
argument should be a pointer to a 4-byte buffer
where the format number will be stored.
.TP
.B Q_SYNC
-Update the on-disk copy of quota usages for a file system.
+Update the on-disk copy of quota usages for a filesystem.
If
.I special
-is NULL, then all file systems with active quotas are sync'ed.
+is NULL, then all filesystems with active quotas are sync'ed.
The
.I addr
and
.I /proc/sys/fs/quota/
carry the information instead.
.PP
-For XFS file systems making use of the XFS Quota Manager (XQM),
+For XFS filesystems making use of the XFS Quota Manager (XQM),
the above commands are bypassed and the following commands are used:
.TP 8
.B Q_XQUOTAON
-Turn on quotas for an XFS file system.
+Turn on quotas for an XFS filesystem.
XFS provides the ability to turn on/off quota limit enforcement
with quota accounting.
Therefore, XFS expects
.RB ( CAP_SYS_ADMIN ).
.TP
.B Q_XQUOTAOFF
-Turn off quotas for an XFS file system.
+Turn off quotas for an XFS filesystem.
As with
.BR Q_QUOTAON ,
-XFS file systems expect a pointer to an
+XFS filesystems expect a pointer to an
.I "unsigned int"
that specifies whether quota accounting and/or limit enforcement need
to be turned off.
.B Q_XGETQSTAT
Returns an
.I fs_quota_stat
-structure containing XFS file system specific quota information.
+structure containing XFS filesystem specific quota information.
This is useful for finding out how much space is used to store quota
information, and also to get quotaon/off status of a given local XFS
-file system.
+filesystem.
.TP
.B Q_XQUOTARM
Free the disk space taken by disk quotas.
.B Q_SYNC
for XFS since
.BR sync (1)
-writes quota information to disk (in addition to the other file system
+writes quota information to disk (in addition to the other filesystem
metadata that it writes out).
.SH RETURN VALUE
.LP
.TP
.B ESRCH
No disk quota is found for the indicated user.
-Quotas have not been turned on for this file system.
+Quotas have not been turned on for this filesystem.
.LP
If
.I cmd
exists, but is not a regular file; or,
the quota file pointed to by
.I addr
-exists, but is not on the file system pointed to by
+exists, but is not on the filesystem pointed to by
.IR special .
.TP
.B EBUSY
.SH CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
.SH NOTES
-On NFS file systems, reading small amounts of data will update the
+On NFS filesystems, reading small amounts of data will update the
timestamp only the first time, subsequent calls may not do so.
This is caused
by client side attribute caching, because most if not all NFS clients
The named file is not a symbolic link.
.TP
.B EIO
-An I/O error occurred while reading from the file system.
+An I/O error occurred while reading from the filesystem.
.TP
.B ELOOP
Too many symbolic links were encountered in translating the pathname.
.I name
and associated with the given
.I path
-in the file system.
+in the filesystem.
.PP
.BR lremovexattr ()
is identical to
.IR <attr/xattr.h> .)
.TP
.B ENOTSUP
-Extended attributes are not supported by the file system, or are disabled.
+Extended attributes are not supported by the filesystem, or are disabled.
.PP
In addition, the errors documented in
.BR stat (2)
handle such situations.)
.TP
.B EDQUOT
-The user's quota of disk blocks on the file system has been exhausted.
+The user's quota of disk blocks on the filesystem has been exhausted.
.TP
.B EFAULT
.IR oldpath " or " newpath " points outside your accessible address space."
(Linux: does not have the
.B CAP_FOWNER
capability);
-or the file system containing
+or the filesystem containing
.I pathname
does not support renaming of the type requested.
.TP
.B EROFS
-The file is on a read-only file system.
+The file is on a read-only filesystem.
.TP
.B EXDEV
.IR oldpath " and " newpath
-are not on the same mounted file system.
-(Linux permits a file system to be mounted at multiple points, but
+are not on the same mounted filesystem.
+(Linux permits a filesystem to be mounted at multiple points, but
.BR rename ()
does not work across different mount points,
-even if the same file system is mounted on both.)
+even if the same filesystem is mounted on both.)
.SH CONFORMING TO
4.3BSD, C89, C99, POSIX.1-2001.
.SH BUGS
-On NFS file systems, you can not assume that if the operation
+On NFS filesystems, you can not assume that if the operation
failed the file was not renamed.
If the server does the rename operation
and then crashes, the retransmitted RPC which will be processed when the
capability).
.TP
.B EPERM
-The file system containing
+The filesystem containing
.I pathname
does not support the removal of directories.
.TP
.B EROFS
.I pathname
-refers to a directory on a read-only file system.
+refers to a directory on a read-only filesystem.
.SH CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
.SH BUGS
operations are used by the
.BR ipcs (1)
program to provide information on allocated resources.
-In the future these may modified or moved to a /proc file system
+In the future these may modified or moved to a /proc filesystem
interface.
.LP
Various fields in a \fIstruct semid_ds\fP were typed as
.\"
.TH SETFSGID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
.SH NAME
-setfsgid \- set group identity used for file system checks
+setfsgid \- set group identity used for filesystem checks
.SH SYNOPSIS
.B #include <unistd.h>
/* glibc uses <sys/fsuid.h> */
The system call
.BR setfsgid ()
sets the group ID that the Linux kernel uses to check for all accesses
-to the file system.
+to the filesystem.
Normally, the value of
.I fsgid
will shadow the value of the effective group ID.
.\"
.TH SETFSUID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
.SH NAME
-setfsuid \- set user identity used for file system checks
+setfsuid \- set user identity used for filesystem checks
.SH SYNOPSIS
.B #include <unistd.h>
/* glibc uses <sys/fsuid.h> */
The system call
.BR setfsuid ()
sets the user ID that the Linux kernel uses to check for all accesses
-to the file system.
+to the filesystem.
Normally, the value of
.I fsuid
will shadow the value of the effective user ID.
If one of the arguments equals \-1, the corresponding value is not changed.
Regardless of what changes are made to the real UID, effective UID,
-and saved set-user-ID, the file system UID is always set to the same
+and saved set-user-ID, the filesystem UID is always set to the same
value as the (possibly new) effective UID.
Completely analogously,
.BR setresgid ()
sets the real GID, effective GID, and saved set-group-ID
-of the calling process (and always modifies the file system GID
+of the calling process (and always modifies the filesystem GID
to be the same as the effective GID),
with the same restrictions for unprivileged processes.
.SH RETURN VALUE
sets all of the real, saved, and effective user IDs.
.\" SVr4 documents an additional EINVAL error condition.
.SH NOTES
-Linux has the concept of the file system user ID, normally equal to the
+Linux has the concept of the filesystem user ID, normally equal to the
effective user ID.
The
.BR setuid ()
-call also sets the file system user ID of the calling process.
+call also sets the filesystem user ID of the calling process.
See
.BR setfsuid (2).
.PP
.\"
.TH SETUP 2 2008-12-03 "Linux" "Linux Programmer's Manual"
.SH NAME
-setup \- setup devices and file systems, mount root file system
+setup \- setup devices and filesystems, mount root filesystem
.SH SYNOPSIS
.B #include <unistd.h>
.sp
.BR setup ()
is called once from within
.IR linux/init/main.c .
-It calls initialization functions for devices and file systems
-configured into the kernel and then mounts the root file system.
+It calls initialization functions for devices and filesystems
+configured into the kernel and then mounts the root filesystem.
.PP
No user process may call
.BR setup ().
.I name
and associated with the given
.I path
-in the file system.
+in the filesystem.
The
.I size
of the
There is insufficient space remaining to store the extended attribute.
.TP
.B ENOTSUP
-Extended attributes are not supported by the file system, or are disabled,
+Extended attributes are not supported by the filesystem, or are disabled,
.I errno
is set to
.BR ENOTSUP .
operations are used by the
.BR ipcs (1)
program to provide information on allocated resources.
-In the future these may modified or moved to a /proc file system
+In the future these may modified or moved to a /proc filesystem
interface.
Linux permits a process to attach
or do not have proper read-write mode.
.TP
.B EINVAL
-Target file system doesn't support splicing;
+Target filesystem doesn't support splicing;
target file is opened in append mode;
.\" The append-mode error is given since 2.6.27; in earlier kernels,
.\" splice() in append mode was broken
and returns a file descriptor associated with it.
.I pathname
must refer to a nonexistent directory in the mount point of
-the SPU file system
+the SPU filesystem
.RB ( spufs ).
If
.BR spu_create ()
gid_t st_gid; /* group ID of owner */
dev_t st_rdev; /* device ID (if special file) */
off_t st_size; /* total size, in bytes */
- blksize_t st_blksize; /* blocksize for file system I/O */
+ blksize_t st_blksize; /* blocksize for filesystem I/O */
blkcnt_t st_blocks; /* number of 512B blocks allocated */
time_t st_atime; /* time of last access */
time_t st_mtime; /* time of last modification */
The
.I st_blksize
-field gives the "preferred" blocksize for efficient file system I/O.
+field gives the "preferred" blocksize for efficient filesystem I/O.
(Writing to a file in smaller chunks may cause
an inefficient read-modify-rewrite.)
.PP
-Not all of the Linux file systems implement all of the time fields.
-Some file system types allow mounting in such a way that file
+Not all of the Linux filesystems implement all of the time fields.
+Some filesystem types allow mounting in such a way that file
and/or directory accesses do not cause an update of the
.I st_atime
field.
If none of the aforementioned macros are defined,
then the nanosecond values are exposed with names of the form
.IR st_atimensec .
-On file systems that do not support subsecond timestamps,
+On filesystems that do not support subsecond timestamps,
the nanosecond fields are returned with the value 0.
.\" As at kernel 2.6.25, XFS and JFS support nanosecond timestamps,
.\" but ext2, ext3, and Reiserfs do not.
.\"
.TH STATFS 2 2010-11-21 "Linux" "Linux Programmer's Manual"
.SH NAME
-statfs, fstatfs \- get file system statistics
+statfs, fstatfs \- get filesystem statistics
.SH SYNOPSIS
.BR "#include <sys/vfs.h> " "/* or <sys/statfs.h> */"
.sp
.SH DESCRIPTION
The function
.BR statfs ()
-returns information about a mounted file system.
+returns information about a mounted filesystem.
.I path
-is the pathname of any file within the mounted file system.
+is the pathname of any file within the mounted filesystem.
.I buf
is a pointer to a
.I statfs
#endif
struct statfs {
- __SWORD_TYPE f_type; /* type of file system (see below) */
+ __SWORD_TYPE f_type; /* type of filesystem (see below) */
__SWORD_TYPE f_bsize; /* optimal transfer block size */
- fsblkcnt_t f_blocks; /* total data blocks in file system */
+ fsblkcnt_t f_blocks; /* total data blocks in filesystem */
fsblkcnt_t f_bfree; /* free blocks in fs */
fsblkcnt_t f_bavail; /* free blocks available to
unprivileged user */
- fsfilcnt_t f_files; /* total file nodes in file system */
+ fsfilcnt_t f_files; /* total file nodes in filesystem */
fsfilcnt_t f_ffree; /* free file nodes in fs */
- fsid_t f_fsid; /* file system id */
+ fsid_t f_fsid; /* filesystem id */
__SWORD_TYPE f_namelen; /* maximum length of filenames */
__SWORD_TYPE f_frsize; /* fragment size (since Linux 2.6) */
__SWORD_TYPE f_spare[5];
};
-File system types:
+Filesystem types:
ADFS_SUPER_MAGIC 0xadf5
AFFS_SUPER_MAGIC 0xADFF
.I f_fsid
is supposed to contain (but see below).
.PP
-Fields that are undefined for a particular file system are set to 0.
+Fields that are undefined for a particular filesystem are set to 0.
.BR fstatfs ()
returns the same information about an open file referenced by descriptor
.IR fd .
This call was interrupted by a signal.
.TP
.B EIO
-An I/O error occurred while reading from the file system.
+An I/O error occurred while reading from the filesystem.
.TP
.B ELOOP
.RB ( statfs ())
Insufficient kernel memory was available.
.TP
.B ENOSYS
-The file system does not support this call.
+The filesystem does not support this call.
.TP
.B ENOTDIR
.RB ( statfs ())
.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),
-because this field is used in the filehandle of the file system
+because this field is used in the filehandle of the filesystem
when NFS-exported, and giving it out is a security concern.
.LP
Under some operating systems the
or, for
.BR swapon (),
the indicated path does not contain a valid swap signature or
-resides on an in-memory file system like tmpfs; or, for
+resides on an in-memory filesystem like tmpfs; or, for
.BR swapoff (),
.I path
is not currently a swap area.
.BR path_resolution (7).)
.TP
.B EDQUOT
-The user's quota of resources on the file system has been exhausted.
+The user's quota of resources on the filesystem has been exhausted.
The resources could be inodes or disk blocks, depending on the file
system implementation.
.TP
is not, in fact, a directory.
.TP
.B EPERM
-The file system containing
+The filesystem containing
.I newpath
does not support the creation of symbolic links.
.TP
.B EROFS
.I newpath
-is on a read-only file system.
+is on a read-only filesystem.
.SH CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
.\" SVr4 documents additional error codes EDQUOT and ENOSYS.
.SH DESCRIPTION
.BR sync ()
causes all buffered modifications to file metadata and data to be
-written to the underlying file systems.
+written to the underlying filesystems.
.BR syncfs ()
is like
.BR sync (),
-but synchronizes just the file system containing file
+but synchronizes just the filesystem containing file
referred to by the open file descriptor
.IR fd .
.SH RETURN VALUE
already-instantiated disk blocks, there are no guarantees that the data will
be available after a crash.
There is no user interface to know if a write is purely an overwrite.
-On file systems using copy-on-write semantics (e.g.,
+On filesystems using copy-on-write semantics (e.g.,
.IR btrfs )
an overwrite of existing allocated blocks is impossible.
When writing into preallocated space,
-many file systems also require calls into the block
+many filesystems also require calls into the block
allocator, which this system call does not sync out to disk.
This system call does not flush disk write caches and thus does not provide
any data integrity on systems with volatile disk write caches.
.\"
.TH SYSFS 2 2010-06-27 "Linux" "Linux Programmer's Manual"
.SH NAME
-sysfs \- get file system type information
+sysfs \- get filesystem type information
.SH SYNOPSIS
.BI "int sysfs(int " option ", const char *" fsname );
.BI "int sysfs(int " option );
.SH DESCRIPTION
.BR sysfs ()
-returns information about the file system types currently present in
+returns information about the filesystem types currently present in
the kernel.
The specific form of the
.BR sysfs ()
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 .
has enough space to accept the string.
.TP
.B 3
-Return the total number of file system types currently present in the
+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 ,
-and the number of currently configured file systems for option
+and the number of currently configured filesystems for option
.BR 3 .
On error, \-1 is returned, and
.I errno
.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
A component of the path prefix is not a directory.
.TP
.B EPERM
-.\" This happens for at least MSDOS and VFAT file systems
+.\" This happens for at least MSDOS and VFAT filesystems
.\" on kernel 2.6.13
-The underlying file system does not support extending
+The underlying filesystem does not support extending
a file beyond its current size.
.TP
.B EROFS
-The named file resides on a read-only file system.
+The named file resides on a read-only filesystem.
.TP
.B ETXTBSY
The file is a pure procedure (shared text) file that is being executed.
is not specified at all in such an environment):
either returning an error, or extending the file.
Like most UNIX implementations, Linux follows the XSI requirement
-when dealing with native file systems.
-However, some nonnative file systems do not permit
+when dealing with native filesystems.
+However, some nonnative filesystems do not permit
.BR truncate ()
and
.BR ftruncate ()
.\"
.TH UMOUNT 2 2010-06-19 "Linux" "Linux Programmer's Manual"
.SH NAME
-umount, umount2 \- unmount file system
+umount, umount2 \- unmount filesystem
.SH SYNOPSIS
.nf
.B "#include <sys/mount.h>"
.BR umount ()
and
.BR umount2 ()
-remove the attachment of the (topmost) file system mounted on
+remove the attachment of the (topmost) filesystem mounted on
.IR target .
.\" Note: the kernel naming differs from the glibc naming
.\" umount2 is the glibc name for what the kernel now calls umount
Appropriate privilege (Linux: the
.B CAP_SYS_ADMIN
-capability) is required to unmount file systems.
+capability) is required to unmount filesystems.
Linux 2.1.116 added the
.BR umount2 ()
.I target
if it is a symbolic link.
This flag allows security problems to be avoided in set-user-ID-\fIroot\fP
-programs that allow unprivileged users to unmount file systems.
+programs that allow unprivileged users to unmount filesystems.
.SH RETURN VALUE
On success, zero is returned.
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 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
.BR umount2 ()
specifying
.B MNT_EXPIRE
-successfully marked an unbusy file system as expired.
+successfully marked an unbusy filesystem as expired.
.TP
.B EBUSY
.I target
.BI "int unlink(const char *" pathname );
.SH DESCRIPTION
.BR unlink ()
-deletes a name from the file system.
+deletes a name from the filesystem.
If that name was the
last link to a file and no processes have the file open the file is
deleted and the space it was using is made available for reuse.
for this case.)
.TP
.BR EPERM " (Linux only)"
-The file system does not allow unlinking of files.
+The filesystem does not allow unlinking of files.
.TP
.BR EPERM " or " EACCES
The directory containing
.TP
.B EROFS
.I pathname
-refers to a file on a read-only file system.
+refers to a file on a read-only filesystem.
.SH CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
.\" SVr4 documents additional error
.BR clone (2)
.B CLONE_FS
flag.
-Unshare file system attributes, so that the calling process
+Unshare filesystem attributes, so that the calling process
no longer shares its root directory
.RB ( chroot (2)),
current directory
.\"
.TH USTAT 2 2003-08-04 "Linux" "Linux Programmer's Manual"
.SH NAME
-ustat \- get file system statistics
+ustat \- get filesystem statistics
.SH SYNOPSIS
.nf
.B #include <sys/types.h>
.fi
.SH DESCRIPTION
.BR ustat ()
-returns information about a mounted file system.
+returns information about a mounted filesystem.
.I dev
is a device number identifying a device containing
-a mounted file system.
+a mounted filesystem.
.I ubuf
is a pointer to a
.I ustat
.TP
.B EINVAL
.I dev
-does not refer to a device containing a mounted file system.
+does not refer to a device containing a mounted filesystem.
.TP
.B ENOSYS
-The mounted file system referenced by
+The mounted filesystem referenced by
.I dev
does not support this operation, or any version of Linux before
1.3.16.
.IR f_blksize ,
that is unknown elsewhere.
HP-UX warns:
-For some file systems, the number of free inodes does not change.
-Such file systems will return \-1 in the field
+For some filesystems, the number of free inodes does not change.
+Such filesystems will return \-1 in the field
.IR f_tinode .
.\" Some software tries to use this in order to test whether the
-.\" underlying file system is NFS.
-For some file systems, inodes are dynamically allocated.
-Such file systems will return the current number of free inodes.
+.\" underlying filesystem is NFS.
+For some filesystems, inodes are dynamically allocated.
+Such filesystems will return the current number of free inodes.
.SH SEE ALSO
.BR stat (2),
.BR statfs (2)
.TP
.B EROFS
.I path
-resides on a read-only file system.
+resides on a read-only filesystem.
.SH CONFORMING TO
.BR utime ():
SVr4, POSIX.1-2001.
.in
.PP
Updated file timestamps are set to the greatest value
-supported by the file system that is not greater than the specified time.
+supported by the filesystem that is not greater than the specified time.
If the
.I tv_nsec
.IP *
the file is marked immutable (see
.BR chattr (1)).
-.\" EXT2_IMMUTABLE_FL and similar flags for other file systems.
+.\" EXT2_IMMUTABLE_FL and similar flags for other filesystems.
.RE
.PD
.TP
the file is marked append-only or immutable (see
.BR chattr (1)).
.\" EXT2_IMMUTABLE_FL EXT_APPPEND_FL and similar flags for
-.\" other file systems.
+.\" other filesystems.
.\"
.\" Why the inconsistency (which is described under NOTES) between
.\" EACCES and EPERM, where only EPERM tests for append-only.
.PD
.TP
.B EROFS
-The file is on a read-only file system.
+The file is on a read-only filesystem.
.TP
.B ESRCH
.RB ( utimensat ())
which can be proved to occur after a
.BR write ()
has returned returns the new data.
-Note that not all file systems are POSIX conforming.
+Note that not all filesystems are POSIX conforming.
.SH RETURN VALUE
On success, the number of bytes written is returned (zero indicates
nothing was written).
.BR connect (2).
.TP
.B EDQUOT
-The user's quota of disk blocks on the file system containing the file
+The user's quota of disk blocks on the filesystem containing the file
referred to by
.I fd
has been exhausted.
If
.I psize
is 0 (no page size is specified) a page size is chosen based on the
-underlying file system I/O block size.
+underlying filesystem I/O block size.
.TP
.I compare
Compare is the key comparison function.
Interrupted system call should be restarted
.TP
.B EROFS
-Read-only file system (POSIX.1)
+Read-only filesystem (POSIX.1)
.TP
.B ESHUTDOWN
Cannot send after transport endpoint shutdown
.B ESTALE
Stale file handle (POSIX.1)
.sp
-This error can occur for NFS and for other file systems
+This error can occur for NFS and for other filesystems
.TP
.B ESTRPIPE
Streams pipe error
.B ENOSYS
The
.I /proc
-file system could not be accessed.
+filesystem could not be accessed.
.SH VERSIONS
.BR fexecve ()
is implemented since glibc 2.3.2.
.BR fexecve ()
is implemented using the
.BR proc (5)
-file system, so
+filesystem, so
.I /proc
needs to be mounted and available at the time of the call.
.SH SEE ALSO
(By default, each directory is handled \fIbefore\fP its contents.)
.TP
.B FTW_MOUNT
-If set, stay within the same file system
+If set, stay within the same filesystem
(i.e., do not cross mount points).
.TP
.B FTW_PHYS
.B ENOSYS
The
.I /proc
-file system could not be accessed.
+filesystem could not be accessed.
.PP
The following additional error may occur for
.BR lutimes ():
implementation of these functions is rather expensive,
since they open and parse files in the
.I /sys
-file system each time they are called.
+filesystem each time they are called.
The following
.BR sysconf (3)
(Note that on some systems,
.B PATH_MAX
may not be a compile-time constant;
-furthermore, its value may depend on the file system, see
+furthermore, its value may depend on the filesystem, see
.BR pathconf (3).)
For portability and security reasons, use of
.BR getwd ()
is a system call (since 2.1.92).
On older systems it would query
.IR /proc/self/cwd .
-If both system call and proc file system are missing, a
+If both system call and proc filesystem are missing, a
generic implementation is called.
Only in that case can
these calls fail under Linux with
.\"
.TH GETDIRENTRIES 3 2007-07-26 "GNU" "Linux Programmer's Manual"
.SH NAME
-getdirentries \- get directory entries in a file system-independent format
+getdirentries \- get directory entries in a filesystem-independent format
.SH SYNOPSIS
.B #include <dirent.h>
.sp
.TH GETMNTENT 3 2009-09-15 "" "Linux Programmer's Manual"
.SH NAME
getmntent, setmntent, addmntent, endmntent, hasmntopt,
-getmntent_r \- get file system descriptor file entry
+getmntent_r \- get filesystem descriptor file entry
.SH SYNOPSIS
.nf
.B #include <stdio.h>
.BR getmntent_r ():
_BSD_SOURCE || _SVID_SOURCE
.SH DESCRIPTION
-These routines are used to access the file system description file
+These routines are used to access the filesystem description file
.I /etc/fstab
-and the mounted file system description file
+and the mounted filesystem description file
.IR /etc/mtab .
.PP
The
.BR setmntent ()
-function opens the file system description file
+function opens the filesystem description file
.I filename
and returns a file pointer which can be used by
.BR getmntent ().
.PP
The
.BR getmntent ()
-function reads the next line from the file system
+function reads the next line from the filesystem
description file
.I fp
and returns a pointer to a structure
.PP
The
.BR endmntent ()
-function closes the file system description file
+function closes the filesystem description file
.IR fp .
.PP
The
.in +4n
.nf
struct mntent {
- char *mnt_fsname; /* name of mounted file system */
- char *mnt_dir; /* file system path prefix */
+ char *mnt_fsname; /* name of mounted filesystem */
+ char *mnt_dir; /* filesystem path prefix */
char *mnt_type; /* mount type (see mntent.h) */
char *mnt_opts; /* mount options (see mntent.h) */
int mnt_freq; /* dump frequency in days */
a match is found and NULL otherwise.
.SH FILES
.nf
-/etc/fstab file system description file
-/etc/mtab mounted file system description file
+/etc/fstab filesystem description file
+/etc/mtab mounted filesystem description file
.fi
.SH CONFORMING TO
The nonreentrant functions are from SunOS 4.1.3.
.IR pglob\->gl_opendir ,
.IR pglob\->gl_lstat ", and"
.I pglob\->gl_stat
-for file system access instead of the normal library
+for filesystem access instead of the normal library
functions.
.TP
.B GLOB_BRACE
A FIFO special file is similar to a pipe, except that it is created
in a different way.
Instead of being an anonymous communications
-channel, a FIFO special file is entered into the file system by
+channel, a FIFO special file is entered into the filesystem by
calling
.BR mkfifo ().
.PP
(execute) permission.
.TP
.B EDQUOT
-The user's quota of disk blocks or inodes on the file system has been
+The user's quota of disk blocks or inodes on the filesystem has been
exhausted.
.TP
.B EEXIST
\fBPATH_MAX\fP, or an individual filename component has a length
greater than \fBNAME_MAX\fP.
In the GNU system, there is no imposed
-limit on overall filename length, but some file systems may place
+limit on overall filename length, but some filesystems may place
limits on the length of a component.
.TP
.B ENOENT
dangling symbolic link.
.TP
.B ENOSPC
-The directory or file system has no room for the new file.
+The directory or filesystem has no room for the new file.
.TP
.B ENOTDIR
A component used as a directory in \fIpathname\fP is not, in fact, a
directory.
.TP
.B EROFS
-\fIpathname\fP refers to a read-only file system.
+\fIpathname\fP refers to a read-only filesystem.
.SH CONFORMING TO
POSIX.1-2001.
.SH SEE ALSO
user ID of the calling process.
The group ownership (group ID) is set to the effective group ID
of the calling process.
-.\" In reality the file system IDs are used on Linux.
+.\" In reality the filesystem IDs are used on Linux.
.TP
.B O_EXCL
If
off_t d_off; /* not an offset; see NOTES */
unsigned short d_reclen; /* length of this record */
unsigned char d_type; /* type of file; not supported
- by all file system types */
+ by all filesystem types */
char d_name[256]; /* filename */
};
.fi
at the current position in the directory stream.
Be aware that despite its type and name, the
.I d_off
-field is seldom any kind of directory offset on modern file systems.
+field is seldom any kind of directory offset on modern filesystems.
.\" https://lwn.net/Articles/544298/
Applications should treat this field as an opaque value,
making no assumptions about its contents; see also
Currently,
.\" kernel 2.6.27
.\" The same sentence is in getdents.2
-only some file systems (among them: Btrfs, ext2, ext3, and ext4)
+only some filesystems (among them: Btrfs, ext2, ext3, and ext4)
have full support for returning the file type in
.IR d_type .
All applications must properly handle a return of
is NULL.)
.TP
.B EIO
-An I/O error occurred while reading from the file system.
+An I/O error occurred while reading from the filesystem.
.TP
.B ELOOP
Too many symbolic links were encountered in translating the pathname.
If
.I psize
is 0 (no page size is specified) a page size is chosen based on the
-underlying file system I/O block size.
+underlying filesystem I/O block size.
See
.BR btree (3)
for more information.
.BI "int remove(const char *" pathname );
.SH DESCRIPTION
.BR remove ()
-deletes a name from the file system.
+deletes a name from the filesystem.
It calls
.BR unlink (2)
for files, and
user ID of the calling process.
The group ownership (group ID) is set to the effective group ID
of the calling process.
-.\" In reality the file system IDs are used on Linux.
+.\" In reality the filesystem IDs are used on Linux.
If both
.B O_CREAT
and
Create the shared memory object if it does not exist.
The user and group ownership of the object are taken
from the corresponding effective IDs of the calling process,
-.\" In truth it is actually the file system IDs on Linux, but these
+.\" In truth it is actually the filesystem IDs on Linux, but these
.\" are nearly always the same as the effective IDs. (MTK, Jul 05)
and the object's
permission bits are set according to the low-order 9 bits of
shared memory object\(emthis may not be so on other UNIX systems.
.LP
The POSIX shared memory object implementation on Linux 2.4 makes use
-of a dedicated file system, which is normally
+of a dedicated filesystem, which is normally
mounted under
.IR /dev/shm .
.SH SEE ALSO
.\"
.TH STATVFS 3 2003-08-22 "Linux" "Linux Programmer's Manual"
.SH NAME
-statvfs, fstatvfs \- get file system statistics
+statvfs, fstatvfs \- get filesystem statistics
.SH SYNOPSIS
.B #include <sys/statvfs.h>
.sp
.SH DESCRIPTION
The function
.BR statvfs ()
-returns information about a mounted file system.
+returns information about a mounted filesystem.
.I path
-is the pathname of any file within the mounted file system.
+is the pathname of any file within the mounted filesystem.
.I buf
is a pointer to a
.I statvfs
.in +4n
.nf
struct statvfs {
- unsigned long f_bsize; /* file system block size */
+ unsigned long f_bsize; /* filesystem block size */
unsigned long f_frsize; /* fragment size */
fsblkcnt_t f_blocks; /* size of fs in f_frsize units */
fsblkcnt_t f_bfree; /* # free blocks */
fsfilcnt_t f_files; /* # inodes */
fsfilcnt_t f_ffree; /* # free inodes */
fsfilcnt_t f_favail; /* # free inodes for unprivileged users */
- unsigned long f_fsid; /* file system ID */
+ unsigned long f_fsid; /* filesystem ID */
unsigned long f_flag; /* mount flags */
unsigned long f_namemax; /* maximum filename length */
};
Bits defined by POSIX are
.TP
.B ST_RDONLY
-Read-only file system.
+Read-only filesystem.
.TP
.B ST_NOSUID
Set-user-ID/set-group-ID bits are ignored by
.BR exec (3).
.LP
It is unspecified whether all members of the returned struct
-have meaningful values on all file systems.
+have meaningful values on all filesystems.
.BR fstatvfs ()
returns the same information about an open file referenced by descriptor
This call was interrupted by a signal.
.TP
.B EIO
-An I/O error occurred while reading from the file system.
+An I/O error occurred while reading from the filesystem.
.TP
.B ELOOP
.RB ( statvfs ())
Insufficient kernel memory was available.
.TP
.B ENOSYS
-The file system does not support this call.
+The filesystem does not support this call.
.TP
.B ENOTDIR
.RB ( statvfs ())
At run time, one can ask for numerical values using the present function
.BR sysconf ().
One can ask for numerical values that may depend
-on the file system a file is in using the calls
+on the filesystem a file is in using the calls
.BR fpathconf (3)
and
.BR pathconf (3).
.IR long ,
and this is the type used since glibc 2.1.2.
-In early file systems, the value returned by
+In early filesystems, the value returned by
.BR telldir ()
was a simple file offset within a directory.
-Modern file systems use tree or hash structures, rather than flat tables,
+Modern filesystems use tree or hash structures, rather than flat tables,
to represent directories.
-On such file systems, the value returned by
+On such filesystems, the value returned by
.BR telldir ()
(and used internally by
.BR readdir (3))
There was no room in the directory to add the new filename.
.TP
.B EROFS
-Read-only file system.
+Read-only filesystem.
.SH CONFORMING TO
SVr4, 4.3BSD, C89, C99, SUSv2, POSIX.1-2001.
.SH NOTES
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.
.B cciss
driver must be informed that changes to the SCSI bus
have been made.
-This may be done via the /proc file system.
+This may be done via the /proc filesystem.
For example:
echo "rescan" > /proc/scsi/cciss0/1
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).
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
are loaded from the initial root device's contents.
-After loading the additional modules, a new root file system
-(i.e., the normal root file system) is mounted from a
+After loading the additional modules, a new root filesystem
+(i.e., the normal root filesystem) is mounted from a
different device.
.\"
.\"
.IP 3.
The kernel then read-write mounts the device
.I /dev/ram0
-as the initial root file system.
+as the initial root filesystem.
.IP 4.
-If the indicated normal root file system is also the initial
-root file-system (e.g.,
+If the indicated normal root filesystem is also the initial
+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
.I /linuxrc
is not executed or when
.I /linuxrc
-terminates, the normal root file system is mounted.
+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.
-If the normal root file system has a directory
+If the normal root filesystem has a directory
.IR /initrd ,
the device
.I /dev/ram0
.IR /dev/ram0 .
If directory
.I /initrd
-does not exist on the normal root file system
+does not exist on the normal root filesystem
and any processes remain running from
.IR /dev/ram0
when
.IP 8.
The usual boot sequence (e.g., invocation of
.IR /sbin/init )
-is performed on the normal root file system.
+is performed on the normal root filesystem.
.\"
.\"
.\"
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.
loaded into memory by the boot loader contents are preserved.
This option permits the contents of
.I /dev/initrd
-to be any data and need not be limited to a file system image.
+to be any data and need not be limited to a filesystem image.
However, device
.I /dev/initrd
is read-only and can be read only one time after system startup.
.TP
.BI root= "device-name"
-Specifies the device to be used as the normal root file system.
+Specifies the device to be used as the normal root filesystem.
For
.B LOADLIN
this is a command-line option.
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.
.\"
.\"
.\"
-.SS Changing the normal root file system
+.SS Changing the normal root filesystem
By default,
the kernel's settings
(e.g., set in the kernel file with
.BR rdev (8)
or compiled into the kernel file),
or the boot loader option setting
-is used for the normal root file systems.
-For an NFS-mounted normal root file system, one has to use the
+is used for the normal root filesystems.
+For an NFS-mounted normal root filesystem, one has to use the
.B nfs_root_name
and
.B nfs_root_addrs
boot options to give the NFS settings.
For more information on NFS-mounted root see the kernel documentation file
.BR Documentation/filesystems/nfsroot.txt .
-For more information on setting the root file system see also the
+For more information on setting the root filesystem see also the
.BR LILO
and
.BR LOADLIN
.IR /proc/sys/kernel/nfs-root-addrs .
For a physical root device, the root device is changed by having
.I /linuxrc
-write the new root file system device number into
+write the new root filesystem device number into
.IR /proc/sys/kernel/real-root-dev .
-For an NFS root file system, the root device is changed by having
+For an NFS root filesystem, the root device is changed by having
.I /linuxrc
write the NFS setting into files
.IR /proc/sys/kernel/nfs-root-name
.BR Note :
The use of
.I /proc/sys/kernel/real-root-dev
-to change the root file system is obsolete.
+to change the root filesystem is obsolete.
See the Linux kernel source file
.I Documentation/initrd.txt
as well as
.BR pivot_root (2)
and
.BR pivot_root (8)
-for information on the modern method of changing the root file system.
+for information on the modern method of changing the root filesystem.
.\" FIXME the manual page should describe the pivot_root mechanism.
.\"
.\"
(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
-(i.e., device type, device drivers, file system) and (2) the
+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,
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
-creates and populates the root file system.
-(At this stage the normal root file system does not have to be a
+creates and populates the root filesystem.
+(At this stage the normal root filesystem does not have to be a
completed system yet.)
.IP 5.
The executable
.IR /proc/sys/kernel/real-root-dev ,
unmount
.IR /proc ,
-the normal root file system and any other file
+the normal root filesystem and any other file
systems it has mounted, and then terminates.
.IP 6.
-The kernel then mounts the normal root file system.
+The kernel then mounts the normal root filesystem.
.IP 7.
-Now that the file system is accessible and intact,
+Now that the filesystem is accessible and intact,
the boot loader can be installed.
.IP 8.
The boot loader is configured to load into
.I /dev/initrd
-a file system with the set of modules that was used to bring up the system.
+a filesystem with the set of modules that was used to bring up the system.
(e.g., Device
.I /dev/ram0
can be modified, then unmounted, and finally, the image is written from
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
.\"
.SH NOTES
.IP 1. 3
-With the current kernel, any file systems that remain mounted when
+With the current kernel, any filesystems that remain mounted when
.I /dev/ram0
is moved from
.I /
.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
The Linux support for the above (known as UNIX 98 pseudoterminal naming)
is done using the
.I devpts
-file system, that should be mounted on
+filesystem, that should be mounted on
.IR /dev/pts .
.LP
Before this UNIX 98 scheme, master pseudoterminals were called
.B sk98lin
is bound to one or more adapter cards and the
.I /proc
-file system is mounted on your system, a dedicated statistics file
+filesystem is mounted on your system, a dedicated statistics file
will be created in the folder
.I /proc/net/sk98lin
for all ports of the installed network adapter cards.
operations of
.BR console (4),
so the system
-administrator can control access using file system permissions.
+administrator can control access using filesystem permissions.
.PP
The devices for the first eight virtual consoles may be created by:
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.
.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.
.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
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.
.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
.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
.\"
.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 .
(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.
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.
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)
(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
.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
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.
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
.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 ,
.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.
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
.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
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
.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
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 *
.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.
.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,
.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
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
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.
When the kernel is loaded, it initializes the devices (via
their drivers), starts the swapper (it is a "kernel process",
called kswapd in modern Linux kernels), and mounts the root
-file system (/).
+filesystem (/).
Some of the parameters that may be passed to the kernel
relate to these activities (e.g: You can override the
-default root file system).
+default root filesystem).
For further information
on Linux kernel parameters read
.BR bootparam (7).
.TP
.B "'root=...'"
This argument tells the kernel what device is to be used as the root
-file system while booting.
+filesystem while booting.
The default of this setting is determined
at compile time, and usually is the value of the root device of the
system that the kernel was built on.
(The type nfs specifies a net boot; ram refers to a ram disk.)
Note that this has nothing to do with the designation of these
-devices on your file system.
+devices on your filesystem.
The '/dev/' part is purely conventional.
The more awkward and less portable numeric specification of the above
need to boot the box from alternate media.
.TP
.BR 'ro' " and " 'rw'
-The 'ro' option tells the kernel to mount the root file system
-as 'read-only' so that file system consistency check programs (fsck)
-can do their work on a quiescent file system.
+The 'ro' option tells the kernel to mount the root filesystem
+as 'read-only' so that filesystem consistency check programs (fsck)
+can do their work on a quiescent filesystem.
No processes can
-write to files on the file system in question until it is 'remounted'
+write to files on the filesystem in question until it is 'remounted'
as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
(See also
.BR mount (8).)
-The 'rw' option tells the kernel to mount the root file system read/write.
+The 'rw' option tells the kernel to mount the root filesystem read/write.
This is the default.
.TP
it is often useful to load the floppy contents into a
ramdisk.
One might also have a system in which first
-some modules (for file system or hardware) must be loaded
+some modules (for filesystem or hardware) must be loaded
before the main disk can be accessed.
In Linux 1.3.48, ramdisk handling was changed drastically.
a "normal" ramdisk, which is mounted read-write as root device;
then
.I /linuxrc
-is executed; afterward the "real" root file system is mounted,
-and the initrd file system is moved over to
+is executed; afterward the "real" root filesystem is mounted,
+and the initrd filesystem is moved over to
.IR /initrd ;
finally
the usual boot sequence (e.g., invocation of
.RS
.IP * 2
Bypass permission checks on operations that normally
-require the file system UID of the process to match the UID of
+require the filesystem UID of the process to match the UID of
the file (e.g.,
.BR chmod (2),
.BR utime (2)),
Don't clear set-user-ID and set-group-ID permission
bits when a file is modified;
set the set-group-ID bit for a file whose GID does not match
-the file system or any of the supplementary GIDs of the calling process.
+the filesystem or any of the supplementary GIDs of the calling process.
.TP
.B CAP_IPC_LOCK
.\" FIXME As at Linux 3.2, there are some strange uses of this capability
.BR ioctl (2)
operations;
.IP *
-perform various privileged file-system
+perform various privileged filesystem
.BR ioctl (2)
operations;
.IP *
.PD 0
.RS
.IP * 2
-Use reserved space on ext2 file systems;
+Use reserved space on ext2 filesystems;
.IP *
make
.BR ioctl (2)
The kernel must provide system calls allowing a thread's capability sets to
be changed and retrieved.
.IP 3.
-The file system must support attaching capabilities to an executable file,
+The filesystem must support attaching capabilities to an executable file,
so that a process gains those capabilities when the file is executed.
.PP
Before kernel 2.6.24, only the first two of these requirements are met;
0 and nonzero user IDs,
the kernel makes the following changes to a thread's capability
sets on changes to the thread's real, effective, saved set,
-and file system user IDs (using
+and filesystem user IDs (using
.BR setuid (2),
.BR setresuid (2),
or similar):
If the effective user ID is changed from nonzero to 0,
then the permitted set is copied to the effective set.
.IP 4.
-If the file system user ID is changed from 0 to nonzero (see
+If the filesystem user ID is changed from 0 to nonzero (see
.BR setfsuid (2))
then the following capabilities are cleared from the effective set:
.BR CAP_CHOWN ,
and
.B CAP_MKNOD
(since Linux 2.2.30).
-If the file system UID is changed from nonzero to 0,
+If the filesystem UID is changed from nonzero to 0,
then any of these capabilities that are enabled in the permitted set
are enabled in the effective set.
.PP
.TP
.B SECBIT_NO_SETUID_FIXUP
Setting this flag stops the kernel from adjusting capability sets when
-the threads's effective and file system UIDs are switched between
+the threads's effective and filesystem UIDs are switched between
zero and nonzero values.
(See the subsection
.IR "Effect of User ID Changes on Capabilities" .)
.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.
.B nodev cpuset
in the file
.IR /proc/filesystems .
-By mounting the cpuset file system (see the
+By mounting the cpuset filesystem (see the
.B EXAMPLE
section below),
the administrator can configure the cpusets on a system
while NUMA (non-uniform memory access) systems have multiple memory nodes.
.PP
Cpusets are represented as directories in a hierarchical
-pseudo-file system, where the top directory in the hierarchy
+pseudo-filesystem, where the top directory in the hierarchy
.RI ( /dev/cpuset )
represents the entire system (all online CPUs and memory nodes)
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
.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.
each process has a pseudo-file,
.IR /proc/<pid>/cpuset ,
that displays the path of the process's cpuset directory
-relative to the root of the cpuset file system.
+relative to the root of the cpuset filesystem.
.\" ================== proc status ==================
.PP
Also the
or not, restrict allocations of memory for user space.
.PP
This enables configuring a system so that several independent
-jobs can share common kernel data, such as file system pages,
+jobs can share common kernel data, such as filesystem pages,
while isolating each job's user allocation in its own cpuset.
To do this, construct a large
.I hardwall
the kernel will run the command
.IR /sbin/cpuset_release_agent ,
supplying the pathname (relative to the mount point of the
-cpuset file system) of the abandoned cpuset.
+cpuset filesystem) of the abandoned cpuset.
This enables automatic removal of abandoned cpusets.
.PP
The default value of
The kernel direct reclaim code is entered whenever a process has to
satisfy a memory page request by first finding some other page to
repurpose, due to lack of any readily available already free pages.
-Dirty file system pages are repurposed by first writing them
+Dirty filesystem pages are repurposed by first writing them
to disk.
-Unmodified file system buffer pages are repurposed
+Unmodified filesystem buffer pages are repurposed
by simply dropping them, though if that page is needed again, it
will have to be reread from disk.
.PP
.\" ================== 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
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.
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,
.\" ================== PERMISSIONS ==================
.SH PERMISSIONS
The permissions of a cpuset are determined by the permissions
-of the directories and pseudo-files in the cpuset file system,
+of the directories and pseudo-files in the cpuset filesystem,
normally mounted at
.IR /dev/cpuset .
.PP
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.
.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
-the cpuset file system (usually, but not necessarily,
+the cpuset filesystem (usually, but not necessarily,
.IR /dev/cpuset ).
In practice, all user level code that this author is aware of
-simply assumes that if the cpuset file system is mounted, then
+simply assumes that if the cpuset filesystem is mounted, then
it is mounted at
.IR /dev/cpuset .
Furthermore, it is common practice for carefully written
user code to verify the presence of the pseudo-file
.I /dev/cpuset/tasks
-in order to verify that the cpuset pseudo-file system
+in order to verify that the cpuset pseudo-filesystem
is currently mounted.
.\" ================== WARNINGS ==================
.SH WARNINGS
as message queues, shared memory, and semaphores.
On most UNIX systems, these IDs also determine the
permissions when accessing files.
-However, Linux uses the file system IDs described below
+However, Linux uses the filesystem IDs described below
for this task.
A process can obtain its effective user (group) ID using
.BR geteuid (2)
.BR getresuid (2)
.RB ( getresgid (2)).
.IP *
-File system user ID and file system group ID (Linux-specific).
+Filesystem user ID and filesystem group ID (Linux-specific).
These IDs, in conjunction with the supplementary group IDs described
below, are used to determine permissions for accessing files; see
.BR path_resolution (7)
for details.
Whenever a process's effective user (group) ID is changed,
-the kernel also automatically changes the file system user (group) ID
+the kernel also automatically changes the filesystem user (group) ID
to the same value.
-Consequently, the file system IDs normally have the same values
+Consequently, the filesystem IDs normally have the same values
as the corresponding effective ID, and the semantics for file-permission
checks are thus the same on Linux as on other UNIX systems.
-The file system IDs can be made to differ from the effective IDs
+The filesystem IDs can be made to differ from the effective IDs
by calling
.BR setfsuid (2)
and
are specified in POSIX.1-2001.
The real, effective, and saved set user and groups IDs,
and the supplementary group IDs, are specified in POSIX.1-2001.
-The file system user and group IDs are a Linux extension.
+The filesystem user and group IDs are a Linux extension.
.SH NOTES
The POSIX threads specification requires that
credentials are shared by all of the threads in a process.
.B _FILE_OFFSET_BITS
Defining this macro with the value 64
automatically converts references to 32-bit functions and data types
-related to file I/O and file system operations into references to
+related to file I/O and filesystem operations into references to
their 64-bit counterparts.
This is useful for performing I/O on large files (> 2 Gigabytes)
on 32-bit systems.
fifo \- first-in first-out special file, named pipe
.SH DESCRIPTION
A FIFO special file (a named pipe) is similar to a pipe,
-except that it is accessed as part of the file system.
+except that it is accessed as part of the filesystem.
It can be opened by multiple processes for reading or
writing.
When processes are exchanging data via the FIFO,
the kernel passes all data internally without writing it
-to the file system.
+to the filesystem.
Thus, the FIFO special file has no
-contents on the file system; the file system entry merely
+contents on the filesystem; the filesystem entry merely
serves as a reference point so that processes can access
-the pipe using a name in the file system.
+the pipe using a name in the filesystem.
.PP
The kernel maintains exactly one pipe object for each
FIFO special file that is opened by at least one process.
.\" Modified Fri Sep 7 20:32:45 2001 by Tammy Fox <tfox@redhat.com>
.TH HIER 7 2012-08-05 "Linux" "Linux Programmer's Manual"
.SH NAME
-hier \- description of the file system hierarchy
+hier \- description of the filesystem hierarchy
.SH DESCRIPTION
A typical Linux system has, among others, the following directories:
.TP
.TP
.I /lib
This directory should hold those shared libraries that are necessary
-to boot the system and to run the commands in the root file system.
+to boot the system and to run the commands in the root filesystem.
.TP
.I /media
This directory contains mount points for removable media such as CD
and DVD disks or USB sticks.
.TP
.I /mnt
-This directory is a mount point for a temporarily mounted file system.
+This directory is a mount point for a temporarily mounted filesystem.
In some distributions,
.I /mnt
contains subdirectories intended to be used as mount points for several
-temporary file systems.
+temporary filesystems.
.TP
.I /opt
This directory should contain add-on packages that contain static files.
.I /proc
This is a mount point for the
.I proc
-file system, which provides information about running processes and
+filesystem, which provides information about running processes and
the kernel.
-This pseudo-file system is described in more detail in
+This pseudo-filesystem is described in more detail in
.BR proc (5).
.TP
.I /root
.I LCK..<device>
where
.I <device>
-is the device's name in the file system.
+is the device's name in the filesystem.
The format used is that of HDU UUCP lock files, that is, lock files
contain a PID as a 10-byte ASCII decimal number, followed by a newline
character.
.\"
.TH INOTIFY 7 2013-07-21 "Linux" "Linux Programmer's Manual"
.SH NAME
-inotify \- monitoring file system events
+inotify \- monitoring filesystem events
.SH DESCRIPTION
The
.I inotify
-API provides a mechanism for monitoring file system events.
+API provides a mechanism for monitoring filesystem events.
Inotify can be used to monitor individual files,
or to monitor directories.
When a directory is monitored, inotify will return events
.B IN_IGNORED
Watch was removed explicitly
.RB ( inotify_rm_watch (2))
-or automatically (file was deleted, or file system was unmounted).
+or automatically (file was deleted, or filesystem was unmounted).
.TP
.B IN_ISDIR
Subject of this event is a directory.
is \-1 for this event).
.TP
.B IN_UNMOUNT
-File system containing watched object was unmounted.
+Filesystem containing watched object was unmounted.
.PD
.RE
.SS /proc interfaces
.SH DESCRIPTION
Section 7 of the manual provides overviews on various topics, and
describes conventions and protocols,
-character set standards, the standard file system layout,
+character set standards, the standard filesystem layout,
and miscellaneous other things.
.SH NOTES
.SS Authors and copyright conditions
that can be consumed by all of the message queues
belonging to a process's real user ID, is described in
.BR getrlimit (2).
-.SS Mounting the message queue file system
-On Linux, message queues are created in a virtual file system.
+.SS Mounting the message queue filesystem
+On Linux, message queues are created in a virtual filesystem.
(Other implementations may also provide such a feature,
but the details are likely to differ.)
-This file system can be mounted (by the superuser) using the following
+This filesystem can be mounted (by the superuser) using the following
commands:
.in +4n
.nf
.in
The sticky bit is automatically enabled on the mount directory.
-After the file system has been mounted, the message queues on the system
+After the filesystem has been mounted, the message queues on the system
can be viewed and manipulated using the commands usually used for files
(e.g.,
.BR ls (1)
The path resolution process will assume that these entries have
their conventional meanings, regardless of whether they are
-actually present in the physical file system.
+actually present in the physical filesystem.
One cannot walk down past the root: "/.." is the same as "/".
.SS Mount points
After a "mount dev path" command, the pathname "path" refers to
-the root of the file system hierarchy on the device "dev", and no
+the root of the filesystem hierarchy on the device "dev", and no
longer to whatever it referred to earlier.
-One can walk out of a mounted file system: "path/.." refers to
+One can walk out of a mounted filesystem: "path/.." refers to
the parent directory of "path",
-outside of the file system hierarchy on "dev".
+outside of the filesystem hierarchy on "dev".
.SS Trailing slashes
If a pathname ends in a \(aq/\(aq, that forces resolution of the preceding
component as in Step 2: it has to exist and resolve to a directory.
changed by the system call
.BR setfsuid (2).
-(Here "fsuid" stands for something like "file system user ID".
+(Here "fsuid" stands for something like "filesystem user ID".
The concept was required for the implementation of a user space
NFS server at a time when processes could send a signal to a process
with the same effective user ID.
Nobody should use
.BR setfsuid (2).)
-Similarly, Linux uses the fsgid ("file system group ID")
+Similarly, Linux uses the fsgid ("filesystem group ID")
instead of the effective group ID.
See
.BR setfsgid (2).
-.\" FIXME say something about file system mounted read-only ?
+.\" FIXME say something about filesystem mounted read-only ?
.SS Bypassing permission checks: superuser and capabilities
On a traditional UNIX system, the superuser
.RI ( root ,
.BR fifo (7)
for further details.
.IR Note :
-although FIFOs have a pathname in the file system,
+although FIFOs have a pathname in the filesystem,
I/O on FIFOs does not involve operations on the underlying device
(if there is one).
.SS I/O on pipes and FIFOs
.I cc \-pthread
to link against the real-time library,
.IR librt .
-.SS Accessing named semaphores via the file system
-On Linux, named semaphores are created in a virtual file system,
+.SS Accessing named semaphores via the filesystem
+On Linux, named semaphores are created in a virtual filesystem,
normally mounted under
.IR /dev/shm ,
with names of the form
.I cc \-lrt
to link against the real-time library,
.IR librt .
-.SS Accessing shared memory objects via the file system
+.SS Accessing shared memory objects via the filesystem
On Linux, shared memory objects are created in a
.RI ( tmpfs )
-virtual file system, normally mounted under
+virtual filesystem, normally mounted under
.IR /dev/shm .
Since kernel 2.6.19, Linux supports the use of access control lists (ACLs)
-to control the permissions of objects in the virtual file system.
+to control the permissions of objects in the virtual filesystem.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.\"
.TH SPUFS 7 2007-12-20 Linux "Linux Programmer's Manual"
.SH NAME
-spufs \- SPU file system
+spufs \- SPU filesystem
.SH DESCRIPTION
-The SPU file system is used on PowerPC machines that implement the
+The SPU filesystem is used on PowerPC machines that implement the
Cell Broadband Engine Architecture in order to access Synergistic
Processor Units (SPUs).
-The file system provides a name space similar to POSIX shared
+The filesystem provides a name space similar to POSIX shared
memory or message queues.
Users that have write permissions
-on the file system can use
+on the filesystem can use
.BR spu_create (2)
to establish SPU contexts under the
.B spufs
or
.BR write (2),
but often support only a subset of the operations
-supported on regular file systems.
+supported on regular filesystems.
This list details the supported
operations and the deviations from the standard behavior described
in the respective man pages.
the same
.IR "i-node number" ,
where an i-node number is an index into the i-node table,
-which contains metadata about all files on a file system.
+which contains metadata about all files on a filesystem.
See
.BR stat (2).)
Changes to a file are independent of the name used to reference the file.
Hard links may not refer to directories
-(to prevent the possibility of loops within the file system tree,
+(to prevent the possibility of loops within the filesystem tree,
which would confuse many programs)
-and may not refer to files on different file systems
-(because i-node numbers are not unique across file systems).
+and may not refer to files on different filesystems
+(because i-node numbers are not unique across filesystems).
A symbolic link is a special type of file whose contents are a string
that is the pathname another file, the file to which the link refers.
In other words, a symbolic link is a pointer to another name,
and not to an underlying object.
For this reason, symbolic links may refer to directories and may cross
-file system boundaries.
+filesystem boundaries.
There is no requirement that the pathname referred to by a symbolic link
should exist.
to be a
.IR "dangling link" .
-Because a symbolic link and its referenced object coexist in the file system
+Because a symbolic link and its referenced object coexist in the filesystem
name space, confusion can arise in distinguishing between the link itself
and the referenced object.
On historical systems,
socket family is used to communicate between processes on the same machine
efficiently.
Traditionally, UNIX domain sockets can be either unnamed,
-or bound to a file system pathname (marked as being of type socket).
+or bound to a filesystem pathname (marked as being of type socket).
Linux also supports an abstract namespace which is independent of the
-file system.
+filesystem.
Valid types are:
.BR SOCK_STREAM ,
.IR sun_path
that are covered by the specified length of the address structure.
(Null bytes in the name have no special significance.)
-The name has no connection with file system pathnames.
+The name has no connection with filesystem pathnames.
When the address of an abstract socket is returned by
.BR getsockname (2),
.BR getpeername (2),
.SH ERRORS
.TP
.B EADDRINUSE
-The specified local address is already in use or the file system socket
+The specified local address is already in use or the filesystem socket
object already exists.
.TP
.B ECONNREFUSED
Unknown socket type.
.PP
Other errors can be generated by the generic socket layer or
-by the file system while generating a file system socket object.
+by the filesystem while generating a filesystem socket object.
See the appropriate manual pages for more information.
.SH VERSIONS
.B SCM_CREDENTIALS
but the implementation details differ.)
.SH NOTES
In the Linux implementation, sockets which are visible in the
-file system honor the permissions of the directory they are in.
+filesystem honor the permissions of the directory they are in.
Their owner, group and their permissions can be changed.
Creation of a new socket will fail if the process does not have write and
search (execute) permission on the directory the socket is created in.
this feature for security.
Binding to a socket with a filename creates a socket
-in the file system that must be deleted by the caller when it is no
+in the filesystem that must be deleted by the caller when it is no
longer needed (using
.BR unlink (2)).
The usual UNIX close-behind semantics apply; the socket can be unlinked
-at any time and will be finally removed from the file system when the last
+at any time and will be finally removed from the filesystem when the last
reference to it is closed.
To pass file descriptors or credentials over a
(though filename globbing could partially overcome this).
Finally, using the file: scheme doesn't easily support people
who dynamically load documentation from the Internet (instead of
-loading the files onto a local file system).
+loading the files onto a local filesystem).
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
The kernel keeps data in memory to avoid doing (relatively slow) disk
reads and writes.
This improves performance, but if the computer
-crashes, data may be lost or the file system corrupted as a result.
+crashes, data may be lost or the filesystem corrupted as a result.
.B sync
ensures that everything in memory is written to disk.
.PP
projects / thirdparty / man-pages.git / commitdiff
