mirror of https://github.com/mkerrisk/man-pages
intro.1, time.1, access.2, acct.2, alloc_hugepages.2, bind.2, chdir.2, chmod.2, chown.2, chroot.2, clone.2, close.2, execve.2, fallocate.2, fcntl.2, getdents.2, getrusage.2, getxattr.2, init_module.2, inotify_add_watch.2, ioprio_set.2, kcmp.2, link.2, listxattr.2, lseek.2, madvise.2, mkdir.2, mknod.2, mmap.2, mount.2, move_pages.2, msgctl.2, nfsservctl.2, open.2, pivot_root.2, quotactl.2, read.2, readlink.2, removexattr.2, rename.2, rmdir.2, semctl.2, setfsgid.2, setfsuid.2, setresuid.2, setuid.2, setup.2, setxattr.2, shmctl.2, splice.2, spu_create.2, stat.2, statfs.2, swapon.2, symlink.2, sync.2, sync_file_range.2, sysfs.2, truncate.2, umount.2, unlink.2, unshare.2, ustat.2, utime.2, utimensat.2, write.2, btree.3, errno.3, fexecve.3, ftw.3, futimes.3, get_nprocs_conf.3, getcwd.3, getdirentries.3, getmntent.3, glob.3, mkfifo.3, mq_open.3, readdir.3, realpath.3, recno.3, remove.3, sem_open.3, shm_open.3, statvfs.3, sysconf.3, telldir.3, tmpfile.3, cciss.4, initrd.4, pts.4, sk98lin.4, vcs.4, core.5, filesystems.5, proc.5, boot.7, bootparam.7, capabilities.7, cpuset.7, credentials.7, feature_test_macros.7, fifo.7, hier.7, inotify.7, intro.7, mq_overview.7, path_resolution.7, pipe.7, sem_overview.7, shm_overview.7, spufs.7, symlink.7, unix.7, uri.7, sync.8: Global fix: s/file system/filesystem/
Notwithstanding 24d01c530c
,
"filesystem" is the form used by the great majority of man pages
outside the man-pages project and in a number of other sources,
so let's go with that.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
af02f8e60d
commit
9ee4a2b6ec
|
@ -240,8 +240,8 @@ and it may be better to use
|
||||||
.SS Disks and filesystems
|
.SS Disks and filesystems
|
||||||
The command
|
The command
|
||||||
.I mount
|
.I mount
|
||||||
will attach the file system found on some disk (or floppy, or CDROM or so)
|
will attach the filesystem found on some disk (or floppy, or CDROM or so)
|
||||||
to the big file system hierarchy.
|
to the big filesystem hierarchy.
|
||||||
And
|
And
|
||||||
.I umount
|
.I umount
|
||||||
detaches it again.
|
detaches it again.
|
||||||
|
|
|
@ -202,10 +202,10 @@ for instance while waiting for an I/O operation to complete.
|
||||||
.B "I/O"
|
.B "I/O"
|
||||||
.TP
|
.TP
|
||||||
.B %I
|
.B %I
|
||||||
Number of file system inputs by the process.
|
Number of filesystem inputs by the process.
|
||||||
.TP
|
.TP
|
||||||
.B %O
|
.B %O
|
||||||
Number of file system outputs by the process.
|
Number of filesystem outputs by the process.
|
||||||
.TP
|
.TP
|
||||||
.B %r
|
.B %r
|
||||||
Number of socket messages received by the process.
|
Number of socket messages received by the process.
|
||||||
|
|
|
@ -131,7 +131,7 @@ A component used as a directory in
|
||||||
is not, in fact, a directory.
|
is not, in fact, a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.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
|
.PP
|
||||||
.BR access ()
|
.BR access ()
|
||||||
may fail if:
|
may fail if:
|
||||||
|
@ -209,7 +209,7 @@ Similarly, a DOS file may be found to be "executable," but the
|
||||||
call will still fail.
|
call will still fail.
|
||||||
.PP
|
.PP
|
||||||
.BR access ()
|
.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,
|
because UID mapping is done on the server and hidden from the client,
|
||||||
which checks permissions.
|
which checks permissions.
|
||||||
Similar problems can occur to FUSE mounts.
|
Similar problems can occur to FUSE mounts.
|
||||||
|
@ -243,7 +243,7 @@ ignored the effect of the
|
||||||
.B MS_NOEXEC
|
.B MS_NOEXEC
|
||||||
flag if it was used to
|
flag if it was used to
|
||||||
.BR mount (2)
|
.BR mount (2)
|
||||||
the underlying file system.
|
the underlying filesystem.
|
||||||
Since kernel 2.6.20,
|
Since kernel 2.6.20,
|
||||||
.BR access ()
|
.BR access ()
|
||||||
honors this flag.
|
honors this flag.
|
||||||
|
|
|
@ -123,7 +123,7 @@ capability is required.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I filename
|
.I filename
|
||||||
refers to a file on a read-only file system.
|
refers to a file on a read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B EUSERS
|
.B EUSERS
|
||||||
There are no more free file structures or we ran out of memory.
|
There are no more free file structures or we ran out of memory.
|
||||||
|
|
|
@ -133,11 +133,11 @@ used in programs intended to be portable.
|
||||||
.SH NOTES
|
.SH NOTES
|
||||||
These system calls are gone;
|
These system calls are gone;
|
||||||
they existed only in Linux 2.5.36 through to 2.5.54.
|
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
|
Memory backed by huge pages (if the CPU supports them) is obtained by
|
||||||
using
|
using
|
||||||
.BR mmap (2)
|
.BR mmap (2)
|
||||||
to map files in this virtual file system.
|
to map files in this virtual filesystem.
|
||||||
.LP
|
.LP
|
||||||
The maximal number of huge pages can be specified using the
|
The maximal number of huge pages can be specified using the
|
||||||
.B hugepages=
|
.B hugepages=
|
||||||
|
|
|
@ -218,7 +218,7 @@ Insufficient kernel memory was available.
|
||||||
A component of the path prefix is not a directory.
|
A component of the path prefix is not a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.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
|
.SH CONFORMING TO
|
||||||
SVr4, 4.4BSD, POSIX.1-2001
|
SVr4, 4.4BSD, POSIX.1-2001
|
||||||
.RB ( bind ()
|
.RB ( bind ()
|
||||||
|
|
|
@ -73,7 +73,7 @@ On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.SH ERRORS
|
||||||
Depending on the file system, other errors can be returned.
|
Depending on the filesystem, other errors can be returned.
|
||||||
The more
|
The more
|
||||||
general errors for
|
general errors for
|
||||||
.BR chdir ()
|
.BR chdir ()
|
||||||
|
|
10
man2/chmod.2
10
man2/chmod.2
|
@ -133,19 +133,19 @@ supplementary group IDs, the
|
||||||
bit will be turned off,
|
bit will be turned off,
|
||||||
but this will not cause an error to be returned.
|
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
|
the set-user-ID and set-group-ID execution bits
|
||||||
may be turned off if a file is written.
|
may be turned off if a file is written.
|
||||||
(On Linux this occurs if the writing process does not have the
|
(On Linux this occurs if the writing process does not have the
|
||||||
.B CAP_FSETID
|
.B CAP_FSETID
|
||||||
capability.)
|
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.
|
which may have a special meaning.
|
||||||
For the sticky bit, and for set-user-ID and set-group-ID bits on
|
For the sticky bit, and for set-user-ID and set-group-ID bits on
|
||||||
directories, see
|
directories, see
|
||||||
.BR stat (2).
|
.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
|
already open files, because the access control is done on the server, but
|
||||||
open files are maintained by the client.
|
open files are maintained by the client.
|
||||||
Widening the permissions may be
|
Widening the permissions may be
|
||||||
|
@ -156,7 +156,7 @@ On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.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
|
The more general errors for
|
||||||
.BR chmod ()
|
.BR chmod ()
|
||||||
are listed below:
|
are listed below:
|
||||||
|
@ -197,7 +197,7 @@ and the process is not privileged (Linux: it does not have the
|
||||||
capability).
|
capability).
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The named file resides on a read-only file system.
|
The named file resides on a read-only filesystem.
|
||||||
.PP
|
.PP
|
||||||
The general errors for
|
The general errors for
|
||||||
.BR fchmod ()
|
.BR fchmod ()
|
||||||
|
|
24
man2/chown.2
24
man2/chown.2
|
@ -122,7 +122,7 @@ On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.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
|
The more general errors for
|
||||||
.BR chown ()
|
.BR chown ()
|
||||||
are listed below.
|
are listed below.
|
||||||
|
@ -158,7 +158,7 @@ The calling process did not have the required permissions
|
||||||
(see above) to change owner and/or group.
|
(see above) to change owner and/or group.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The named file resides on a read-only file system.
|
The named file resides on a read-only filesystem.
|
||||||
.PP
|
.PP
|
||||||
The general errors for
|
The general errors for
|
||||||
.BR fchown ()
|
.BR fchown ()
|
||||||
|
@ -213,14 +213,14 @@ When a new file is created (by, for example,
|
||||||
.BR open (2)
|
.BR open (2)
|
||||||
or
|
or
|
||||||
.BR mkdir (2)),
|
.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.
|
creating process.
|
||||||
The group of the file depends on a range of factors,
|
The group of the file depends on a range of factors,
|
||||||
including the type of file system,
|
including the type of filesystem,
|
||||||
the options used to mount the file system,
|
the options used to mount the filesystem,
|
||||||
and whether or not the set-group-ID permission bit is enabled
|
and whether or not the set-group-ID permission bit is enabled
|
||||||
on the parent directory.
|
on the parent directory.
|
||||||
If the file system supports the
|
If the filesystem supports the
|
||||||
.I "\-o\ grpid"
|
.I "\-o\ grpid"
|
||||||
(or, synonymously
|
(or, synonymously
|
||||||
.IR "\-o\ bsdgroups" )
|
.IR "\-o\ bsdgroups" )
|
||||||
|
@ -231,18 +231,18 @@ and
|
||||||
.BR mount (8)
|
.BR mount (8)
|
||||||
options, then the rules are as follows:
|
options, then the rules are as follows:
|
||||||
.IP * 2
|
.IP * 2
|
||||||
If the file system is mounted with
|
If the filesystem is mounted with
|
||||||
.IR "\-o\ grpid" ,
|
.IR "\-o\ grpid" ,
|
||||||
then the group of a new file is made
|
then the group of a new file is made
|
||||||
the same as that of the parent directory.
|
the same as that of the parent directory.
|
||||||
.IP *
|
.IP *
|
||||||
If the file system is mounted with
|
If the filesystem is mounted with
|
||||||
.IR "\-o\ nogrpid"
|
.IR "\-o\ nogrpid"
|
||||||
and the set-group-ID bit is disabled on the parent directory,
|
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
|
then the group of a new file is made the same as the
|
||||||
process's file system GID.
|
process's filesystem GID.
|
||||||
.IP *
|
.IP *
|
||||||
If the file system is mounted with
|
If the filesystem is mounted with
|
||||||
.IR "\-o\ nogrpid"
|
.IR "\-o\ nogrpid"
|
||||||
and the set-group-ID bit is enabled on the parent directory,
|
and the set-group-ID bit is enabled on the parent directory,
|
||||||
then the group of a new file is made
|
then the group of a new file is made
|
||||||
|
@ -254,13 +254,13 @@ the
|
||||||
and
|
and
|
||||||
.IR "\-o\ nogrpid"
|
.IR "\-o\ nogrpid"
|
||||||
mount options are supported by ext2, ext3, ext4, and XFS.
|
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"
|
.IR "\-o\ nogrpid"
|
||||||
rules.
|
rules.
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.BR chown ()
|
.BR chown ()
|
||||||
semantics are deliberately violated on NFS file systems
|
semantics are deliberately violated on NFS filesystems
|
||||||
which have UID mapping enabled.
|
which have UID mapping enabled.
|
||||||
Additionally, the semantics of all system
|
Additionally, the semantics of all system
|
||||||
calls which access the file contents are violated, because
|
calls which access the file contents are violated, because
|
||||||
|
|
|
@ -93,7 +93,7 @@ On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.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:
|
The more general errors are listed below:
|
||||||
.TP
|
.TP
|
||||||
.B EACCES
|
.B EACCES
|
||||||
|
|
|
@ -224,9 +224,9 @@ process or the child process do not affect the other process.
|
||||||
.BR CLONE_FS " (since Linux 2.0)"
|
.BR CLONE_FS " (since Linux 2.0)"
|
||||||
If
|
If
|
||||||
.B CLONE_FS
|
.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.
|
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.
|
working directory, and the umask.
|
||||||
Any call to
|
Any call to
|
||||||
.BR chroot (2),
|
.BR chroot (2),
|
||||||
|
@ -238,7 +238,7 @@ other process.
|
||||||
|
|
||||||
If
|
If
|
||||||
.B CLONE_FS
|
.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
|
information of the calling process at the time of the
|
||||||
.BR clone ()
|
.BR clone ()
|
||||||
call.
|
call.
|
||||||
|
|
|
@ -101,7 +101,7 @@ and with disk quota.
|
||||||
.PP
|
.PP
|
||||||
A successful close does not guarantee that the data has been successfully
|
A successful close does not guarantee that the data has been successfully
|
||||||
saved to disk, as the kernel defers writes.
|
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.
|
to flush the buffers when the stream is closed.
|
||||||
If you need to be sure that
|
If you need to be sure that
|
||||||
the data is physically stored use
|
the data is physically stored use
|
||||||
|
|
|
@ -83,7 +83,7 @@ after a successful
|
||||||
|
|
||||||
If the set-user-ID bit is set on the program file pointed to by
|
If the set-user-ID bit is set on the program file pointed to by
|
||||||
\fIfilename\fP,
|
\fIfilename\fP,
|
||||||
and the underlying file system is not mounted
|
and the underlying filesystem is not mounted
|
||||||
.I nosuid
|
.I nosuid
|
||||||
(the
|
(the
|
||||||
.B MS_NOSUID
|
.B MS_NOSUID
|
||||||
|
@ -381,7 +381,7 @@ The file or a script interpreter is not a regular file.
|
||||||
Execute permission is denied for the file or a script or ELF interpreter.
|
Execute permission is denied for the file or a script or ELF interpreter.
|
||||||
.TP
|
.TP
|
||||||
.B EACCES
|
.B EACCES
|
||||||
The file system is mounted
|
The filesystem is mounted
|
||||||
.IR noexec .
|
.IR noexec .
|
||||||
.TP
|
.TP
|
||||||
.B EFAULT
|
.B EFAULT
|
||||||
|
@ -436,7 +436,7 @@ A component of the path prefix of
|
||||||
or a script or ELF interpreter is not a directory.
|
or a script or ELF interpreter is not a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
The file system is mounted
|
The filesystem is mounted
|
||||||
.IR nosuid ,
|
.IR nosuid ,
|
||||||
the user is not the superuser,
|
the user is not the superuser,
|
||||||
and the file has the set-user-ID or set-group-ID bit set.
|
and the file has the set-user-ID or set-group-ID bit set.
|
||||||
|
@ -461,7 +461,7 @@ Set-user-ID and set-group-ID processes can not be
|
||||||
|
|
||||||
Linux ignores the set-user-ID and set-group-ID bits on scripts.
|
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
|
.I nosuid
|
||||||
varies across Linux kernel versions:
|
varies across Linux kernel versions:
|
||||||
some will refuse execution of set-user-ID and set-group-ID
|
some will refuse execution of set-user-ID and set-group-ID
|
||||||
|
|
|
@ -90,8 +90,8 @@ in the byte range starting at
|
||||||
and continuing for
|
and continuing for
|
||||||
.I len
|
.I len
|
||||||
bytes.
|
bytes.
|
||||||
Within the specified range, partial file system blocks are zeroed,
|
Within the specified range, partial filesystem blocks are zeroed,
|
||||||
and whole file system blocks are removed from the file.
|
and whole filesystem blocks are removed from the file.
|
||||||
After a successful call,
|
After a successful call,
|
||||||
subsequent reads from this range will return zeroes.
|
subsequent reads from this range will return zeroes.
|
||||||
|
|
||||||
|
@ -106,9 +106,9 @@ in other words, even when punching off the end of the file, the file size
|
||||||
.BR stat (2))
|
.BR stat (2))
|
||||||
does not change.
|
does not change.
|
||||||
|
|
||||||
Not all file systems support
|
Not all filesystems support
|
||||||
.BR FALLOC_FL_PUNCH_HOLE ;
|
.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
|
.SH RETURN VALUE
|
||||||
On success,
|
On success,
|
||||||
.BR fallocate ()
|
.BR fallocate ()
|
||||||
|
@ -142,7 +142,7 @@ was less than 0, or
|
||||||
was less than or equal to 0.
|
was less than or equal to 0.
|
||||||
.TP
|
.TP
|
||||||
.B EIO
|
.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
|
.TP
|
||||||
.B ENODEV
|
.B ENODEV
|
||||||
.I fd
|
.I fd
|
||||||
|
@ -161,12 +161,12 @@ This kernel does not implement
|
||||||
.BR fallocate ().
|
.BR fallocate ().
|
||||||
.TP
|
.TP
|
||||||
.B EOPNOTSUPP
|
.B EOPNOTSUPP
|
||||||
The file system containing the file referred to by
|
The filesystem containing the file referred to by
|
||||||
.I fd
|
.I fd
|
||||||
does not support this operation;
|
does not support this operation;
|
||||||
or the
|
or the
|
||||||
.I mode
|
.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 .
|
.IR fd .
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
|
|
|
@ -414,9 +414,9 @@ flag is enabled, then the system call fails with the error
|
||||||
.BR EAGAIN .
|
.BR EAGAIN .
|
||||||
|
|
||||||
To make use of mandatory locks, mandatory locking must be enabled
|
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.
|
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
|
using the "\-o mand" option to
|
||||||
.BR mount (8),
|
.BR mount (8),
|
||||||
or the
|
or the
|
||||||
|
@ -815,7 +815,7 @@ such descriptors have been closed.
|
||||||
.P
|
.P
|
||||||
Leases may be taken out only on regular files.
|
Leases may be taken out only on regular files.
|
||||||
An unprivileged process may take out a lease only on a file whose
|
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
|
A process with the
|
||||||
.B CAP_LEASE
|
.B CAP_LEASE
|
||||||
capability may take out leases on arbitrary files.
|
capability may take out leases on arbitrary files.
|
||||||
|
@ -1009,7 +1009,7 @@ New applications should use the
|
||||||
.I inotify
|
.I inotify
|
||||||
interface (available since kernel 2.6.13),
|
interface (available since kernel 2.6.13),
|
||||||
which provides a much superior interface for obtaining notifications of
|
which provides a much superior interface for obtaining notifications of
|
||||||
file system events.
|
filesystem events.
|
||||||
See
|
See
|
||||||
.BR inotify (7).
|
.BR inotify (7).
|
||||||
.SS Changing the capacity of a pipe
|
.SS Changing the capacity of a pipe
|
||||||
|
|
|
@ -134,7 +134,7 @@ attempting to access this field always provides the value 0
|
||||||
Currently,
|
Currently,
|
||||||
.\" kernel 2.6.27
|
.\" kernel 2.6.27
|
||||||
.\" The same sentence is in readdir.2
|
.\" 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
|
have full support for returning the file type in
|
||||||
.IR d_type .
|
.IR d_type .
|
||||||
All applications must properly handle a return of
|
All applications must properly handle a return of
|
||||||
|
@ -180,7 +180,7 @@ This call supersedes
|
||||||
|
|
||||||
The original Linux
|
The original Linux
|
||||||
.BR getdents ()
|
.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
|
Consequently, Linux 2.4 added
|
||||||
.BR getdents64 (),
|
.BR getdents64 (),
|
||||||
with wider types for the
|
with wider types for the
|
||||||
|
|
|
@ -147,10 +147,10 @@ This field is currently unused on Linux.
|
||||||
.\" On some systems, this is the number of swaps out of physical memory.
|
.\" On some systems, this is the number of swaps out of physical memory.
|
||||||
.TP
|
.TP
|
||||||
.IR ru_inblock " (since Linux 2.6.22)"
|
.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
|
.TP
|
||||||
.IR ru_oublock " (since Linux 2.6.22)"
|
.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
|
.TP
|
||||||
.IR ru_msgsnd " (unmaintained)"
|
.IR ru_msgsnd " (unmaintained)"
|
||||||
This field is currently unused on Linux.
|
This field is currently unused on Linux.
|
||||||
|
|
|
@ -58,7 +58,7 @@ of the extended attribute identified by
|
||||||
.I name
|
.I name
|
||||||
and associated with the given
|
and associated with the given
|
||||||
.I path
|
.I path
|
||||||
in the file system.
|
in the filesystem.
|
||||||
The length of the attribute
|
The length of the attribute
|
||||||
.I value
|
.I value
|
||||||
is returned.
|
is returned.
|
||||||
|
@ -115,7 +115,7 @@ in
|
||||||
.IR <attr/xattr.h> .)
|
.IR <attr/xattr.h> .)
|
||||||
.TP
|
.TP
|
||||||
.B ENOTSUP
|
.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
|
.TP
|
||||||
.B ERANGE
|
.B ERANGE
|
||||||
The
|
The
|
||||||
|
|
|
@ -96,7 +96,7 @@ system call is like
|
||||||
but reads the module to be loaded from the file descriptor
|
but reads the module to be loaded from the file descriptor
|
||||||
.IR fd .
|
.IR fd .
|
||||||
It is useful when the authenticity of a kernel module
|
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,
|
in cases where that is possible,
|
||||||
the overhead of using cryptographically signed modules to
|
the overhead of using cryptographically signed modules to
|
||||||
determine the authenticity of a module can be avoided.
|
determine the authenticity of a module can be avoided.
|
||||||
|
|
|
@ -73,7 +73,7 @@ These reads fetch
|
||||||
.I inotify_event
|
.I inotify_event
|
||||||
structures (see
|
structures (see
|
||||||
.BR inotify (7))
|
.BR inotify (7))
|
||||||
indicating file system events;
|
indicating filesystem events;
|
||||||
the watch descriptor inside this structure identifies
|
the watch descriptor inside this structure identifies
|
||||||
the object for which the event occurred.
|
the object for which the event occurred.
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
|
|
|
@ -229,7 +229,7 @@ file
|
||||||
|
|
||||||
One can view the current I/O scheduler via the
|
One can view the current I/O scheduler via the
|
||||||
.I /sys
|
.I /sys
|
||||||
file system.
|
filesystem.
|
||||||
For example, the following command
|
For example, the following command
|
||||||
displays a list of all schedulers currently loaded in the kernel:
|
displays a list of all schedulers currently loaded in the kernel:
|
||||||
.sp
|
.sp
|
||||||
|
|
|
@ -74,8 +74,8 @@ and
|
||||||
are ignored.
|
are ignored.
|
||||||
.TP
|
.TP
|
||||||
.BR KCMP_FS
|
.BR KCMP_FS
|
||||||
Check whether the processes share the same file system information
|
Check whether the processes share the same filesystem information
|
||||||
(i.e., file mode creation mask, working directory, and file system root).
|
(i.e., file mode creation mask, working directory, and filesystem root).
|
||||||
The arguments
|
The arguments
|
||||||
.I idx1
|
.I idx1
|
||||||
and
|
and
|
||||||
|
@ -210,7 +210,7 @@ checkpoint/restore in user space (CRIU) feature.
|
||||||
The alternative to this system call would have been to expose suitable
|
The alternative to this system call would have been to expose suitable
|
||||||
process information via the
|
process information via the
|
||||||
.BR proc (5)
|
.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
|
See
|
||||||
.BR clone (2)
|
.BR clone (2)
|
||||||
|
|
16
man2/link.2
16
man2/link.2
|
@ -68,7 +68,7 @@ or
|
||||||
.BR path_resolution (7).)
|
.BR path_resolution (7).)
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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
|
.TP
|
||||||
.B EEXIST
|
.B EEXIST
|
||||||
.I newpath
|
.I newpath
|
||||||
|
@ -114,7 +114,7 @@ is not, in fact, a directory.
|
||||||
is a directory.
|
is a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
The file system containing
|
The filesystem containing
|
||||||
.IR oldpath " and " newpath
|
.IR oldpath " and " newpath
|
||||||
does not support the creation of hard links.
|
does not support the creation of hard links.
|
||||||
.TP
|
.TP
|
||||||
|
@ -126,15 +126,15 @@ in
|
||||||
.BR proc (5)).
|
.BR proc (5)).
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The file is on a read-only file system.
|
The file is on a read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B EXDEV
|
.B EXDEV
|
||||||
.IR oldpath " and " newpath
|
.IR oldpath " and " newpath
|
||||||
are not on the same mounted file system.
|
are not on the same mounted filesystem.
|
||||||
(Linux permits a file system to be mounted at multiple points, but
|
(Linux permits a filesystem to be mounted at multiple points, but
|
||||||
.BR link ()
|
.BR link ()
|
||||||
does not work across different mount points,
|
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
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES).
|
SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES).
|
||||||
.\" SVr4 documents additional ENOLINK and
|
.\" SVr4 documents additional ENOLINK and
|
||||||
|
@ -143,7 +143,7 @@ SVr4, 4.3BSD, POSIX.1-2001 (but see NOTES).
|
||||||
.SH NOTES
|
.SH NOTES
|
||||||
Hard links, as created by
|
Hard links, as created by
|
||||||
.BR link (),
|
.BR link (),
|
||||||
cannot span file systems.
|
cannot span filesystems.
|
||||||
Use
|
Use
|
||||||
.BR symlink (2)
|
.BR symlink (2)
|
||||||
if this is required.
|
if this is required.
|
||||||
|
@ -179,7 +179,7 @@ For precise control over the treatment of symbolic links when
|
||||||
creating a link, see
|
creating a link, see
|
||||||
.BR linkat (2).
|
.BR linkat (2).
|
||||||
.SH BUGS
|
.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.
|
performs the link creation and dies before it can say so.
|
||||||
Use
|
Use
|
||||||
.BR stat (2)
|
.BR stat (2)
|
||||||
|
|
|
@ -52,7 +52,7 @@ A complete overview of extended attributes concepts can be found in
|
||||||
retrieves the list
|
retrieves the list
|
||||||
of extended attribute names associated with the given
|
of extended attribute names associated with the given
|
||||||
.I path
|
.I path
|
||||||
in the file system.
|
in the filesystem.
|
||||||
The retrieved list is placed in
|
The retrieved list is placed in
|
||||||
.IR list ,
|
.IR list ,
|
||||||
a caller-allocated buffer whose size (in bytes) is specified in the argument
|
a caller-allocated buffer whose size (in bytes) is specified in the argument
|
||||||
|
@ -127,7 +127,7 @@ is set appropriately.
|
||||||
.SH ERRORS
|
.SH ERRORS
|
||||||
.TP
|
.TP
|
||||||
.B ENOTSUP
|
.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
|
.TP
|
||||||
.B ERANGE
|
.B ERANGE
|
||||||
The
|
The
|
||||||
|
|
|
@ -130,13 +130,13 @@ if they have a mechanism for discovering holes.
|
||||||
|
|
||||||
For the purposes of these operations, a hole is a sequence of zeros that
|
For the purposes of these operations, a hole is a sequence of zeros that
|
||||||
(normally) has not been allocated in the underlying file storage.
|
(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
|
so these operations are not a guaranteed mechanism for
|
||||||
mapping the storage space actually allocated to a file.
|
mapping the storage space actually allocated to a file.
|
||||||
(Furthermore, a sequence of zeros that actually has been written
|
(Furthermore, a sequence of zeros that actually has been written
|
||||||
to the underlying storage may not be reported as a hole.)
|
to the underlying storage may not be reported as a hole.)
|
||||||
In the simplest implementation,
|
In the simplest implementation,
|
||||||
a file system can support the operations by making
|
a filesystem can support the operations by making
|
||||||
.BR SEEK_HOLE
|
.BR SEEK_HOLE
|
||||||
always return the offset of the end of the file,
|
always return the offset of the end of the file,
|
||||||
and making
|
and making
|
||||||
|
@ -179,7 +179,7 @@ is not valid.
|
||||||
Or: the resulting file offset would be negative,
|
Or: the resulting file offset would be negative,
|
||||||
or beyond the end of a seekable device.
|
or beyond the end of a seekable device.
|
||||||
.\" Some systems may allow negative offsets for character devices
|
.\" Some systems may allow negative offsets for character devices
|
||||||
.\" and/or for remote file systems.
|
.\" and/or for remote filesystems.
|
||||||
.TP
|
.TP
|
||||||
.B EOVERFLOW
|
.B EOVERFLOW
|
||||||
.\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
|
.\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
|
||||||
|
|
|
@ -103,7 +103,7 @@ Free up a given range of pages
|
||||||
and its associated backing store.
|
and its associated backing store.
|
||||||
Currently,
|
Currently,
|
||||||
.\" 2.6.18-rc5
|
.\" 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
|
error
|
||||||
.BR ENOSYS .
|
.BR ENOSYS .
|
||||||
.\" Databases want to use this feature to drop a section of their
|
.\" Databases want to use this feature to drop a section of their
|
||||||
|
|
|
@ -36,7 +36,7 @@ For Linux, see below.
|
||||||
The newly created directory will be owned by the effective user ID of the
|
The newly created directory will be owned by the effective user ID of the
|
||||||
process.
|
process.
|
||||||
If the directory containing the file has the set-group-ID
|
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"
|
.RI ( "mount -o bsdgroups"
|
||||||
or, synonymously
|
or, synonymously
|
||||||
.IR "mount -o grpid" ),
|
.IR "mount -o grpid" ),
|
||||||
|
@ -61,7 +61,7 @@ did not allow search permission.
|
||||||
.BR path_resolution (7).)
|
.BR path_resolution (7).)
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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.
|
exhausted.
|
||||||
.TP
|
.TP
|
||||||
.B EEXIST
|
.B EEXIST
|
||||||
|
@ -108,13 +108,13 @@ A component used as a directory in
|
||||||
is not, in fact, a directory.
|
is not, in fact, a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
The file system containing
|
The filesystem containing
|
||||||
.I pathname
|
.I pathname
|
||||||
does not support the creation of directories.
|
does not support the creation of directories.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I pathname
|
.I pathname
|
||||||
refers to a file on a read-only file system.
|
refers to a file on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, BSD, POSIX.1-2001.
|
SVr4, BSD, POSIX.1-2001.
|
||||||
.\" SVr4 documents additional EIO, EMULTIHOP
|
.\" SVr4 documents additional EIO, EMULTIHOP
|
||||||
|
|
10
man2/mknod.2
10
man2/mknod.2
|
@ -39,7 +39,7 @@ _XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
The system call
|
The system call
|
||||||
.BR mknod ()
|
.BR mknod ()
|
||||||
creates a file system node (file, device special file or
|
creates a filesystem node (file, device special file or
|
||||||
named pipe) named
|
named pipe) named
|
||||||
.IR pathname ,
|
.IR pathname ,
|
||||||
with attributes specified by
|
with attributes specified by
|
||||||
|
@ -95,7 +95,7 @@ error.
|
||||||
The newly created node will be owned by the effective user ID of the
|
The newly created node will be owned by the effective user ID of the
|
||||||
process.
|
process.
|
||||||
If the directory containing the node has the set-group-ID
|
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;
|
new node will inherit the group ownership from its parent directory;
|
||||||
otherwise it will be owned by the effective group ID of the process.
|
otherwise it will be owned by the effective group ID of the process.
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
|
@ -114,7 +114,7 @@ did not allow search permission.
|
||||||
.BR path_resolution (7).)
|
.BR path_resolution (7).)
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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.
|
exhausted.
|
||||||
.TP
|
.TP
|
||||||
.B EEXIST
|
.B EEXIST
|
||||||
|
@ -167,13 +167,13 @@ capability);
|
||||||
.\" For UNIX domain sockets and regular files, EPERM is returned only in
|
.\" 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
|
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
|
||||||
.\" use mknod() to make these files.
|
.\" use mknod() to make these files.
|
||||||
also returned if the file system containing
|
also returned if the filesystem containing
|
||||||
.I pathname
|
.I pathname
|
||||||
does not support the type of node requested.
|
does not support the type of node requested.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I pathname
|
.I pathname
|
||||||
refers to a file on a read-only file system.
|
refers to a file on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.4BSD, POSIX.1-2001 (but see below).
|
SVr4, 4.4BSD, POSIX.1-2001 (but see below).
|
||||||
.\" The Linux version differs from the SVr4 version in that it
|
.\" The Linux version differs from the SVr4 version in that it
|
||||||
|
|
|
@ -451,7 +451,7 @@ The system limit on the total number of open files has been reached.
|
||||||
.\" A file could not be mapped for reading.
|
.\" A file could not be mapped for reading.
|
||||||
.TP
|
.TP
|
||||||
.B ENODEV
|
.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.
|
memory mapping.
|
||||||
.TP
|
.TP
|
||||||
.B ENOMEM
|
.B ENOMEM
|
||||||
|
@ -463,7 +463,7 @@ The
|
||||||
.I prot
|
.I prot
|
||||||
argument asks for
|
argument asks for
|
||||||
.B PROT_EXEC
|
.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.
|
was mounted no-exec.
|
||||||
.\" (Since 2.4.25 / 2.6.0.)
|
.\" (Since 2.4.25 / 2.6.0.)
|
||||||
.TP
|
.TP
|
||||||
|
|
54
man2/mount.2
54
man2/mount.2
|
@ -39,7 +39,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH MOUNT 2 2012-07-05 "Linux" "Linux Programmer's Manual"
|
.TH MOUNT 2 2012-07-05 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
mount \- mount file system
|
mount \- mount filesystem
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.nf
|
.nf
|
||||||
.B "#include <sys/mount.h>"
|
.B "#include <sys/mount.h>"
|
||||||
|
@ -50,7 +50,7 @@ mount \- mount file system
|
||||||
.fi
|
.fi
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR mount ()
|
.BR mount ()
|
||||||
attaches the file system specified by
|
attaches the filesystem specified by
|
||||||
.I source
|
.I source
|
||||||
(which is often a device name, but can also be a directory name
|
(which is often a device name, but can also be a directory name
|
||||||
or a dummy) to the directory specified by
|
or a dummy) to the directory specified by
|
||||||
|
@ -58,9 +58,9 @@ or a dummy) to the directory specified by
|
||||||
|
|
||||||
Appropriate privilege (Linux: the
|
Appropriate privilege (Linux: the
|
||||||
.B CAP_SYS_ADMIN
|
.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
|
multiple mount points, and multiple mounts can be stacked
|
||||||
on the same mount point.
|
on the same mount point.
|
||||||
.\" Multiple mounts on same mount point: since 2.3.99pre7.
|
.\" Multiple mounts on same mount point: since 2.3.99pre7.
|
||||||
|
@ -132,8 +132,8 @@ in the low order 16 bits:
|
||||||
.BR MS_BIND " (Linux 2.4 onward)"
|
.BR MS_BIND " (Linux 2.4 onward)"
|
||||||
.\" since 2.4.0-test9
|
.\" since 2.4.0-test9
|
||||||
Perform a bind mount, making a file or a directory subtree visible at
|
Perform a bind mount, making a file or a directory subtree visible at
|
||||||
another point within a file system.
|
another point within a filesystem.
|
||||||
Bind mounts may cross file system boundaries and span
|
Bind mounts may cross filesystem boundaries and span
|
||||||
.BR chroot (2)
|
.BR chroot (2)
|
||||||
jails.
|
jails.
|
||||||
The
|
The
|
||||||
|
@ -149,13 +149,13 @@ was also ignored
|
||||||
the underlying mount point).
|
the underlying mount point).
|
||||||
.TP
|
.TP
|
||||||
.BR MS_DIRSYNC " (since Linux 2.5.19)"
|
.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
|
(This property can be obtained for individual directories
|
||||||
or subtrees using
|
or subtrees using
|
||||||
.BR chattr (1).)
|
.BR chattr (1).)
|
||||||
.TP
|
.TP
|
||||||
.B MS_MANDLOCK
|
.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,
|
(Mandatory locking must still be enabled on a per-file basis,
|
||||||
as described in
|
as described in
|
||||||
.BR fcntl (2).)
|
.BR fcntl (2).)
|
||||||
|
@ -173,13 +173,13 @@ The
|
||||||
arguments are ignored.
|
arguments are ignored.
|
||||||
.TP
|
.TP
|
||||||
.B MS_NOATIME
|
.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
|
.TP
|
||||||
.B MS_NODEV
|
.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
|
.TP
|
||||||
.B MS_NODIRATIME
|
.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
|
This flag provides a subset of the functionality provided by
|
||||||
.BR MS_NOATIME ;
|
.BR MS_NOATIME ;
|
||||||
that is,
|
that is,
|
||||||
|
@ -188,26 +188,26 @@ implies
|
||||||
.BR MS_NODIRATIME .
|
.BR MS_NODIRATIME .
|
||||||
.TP
|
.TP
|
||||||
.B MS_NOEXEC
|
.B MS_NOEXEC
|
||||||
Do not allow programs to be executed from this file system.
|
Do not allow programs to be executed from this filesystem.
|
||||||
.\" (Possibly useful for a file system that contains non-Linux executables.
|
.\" (Possibly useful for a filesystem that contains non-Linux executables.
|
||||||
.\" Often used as a security feature, e.g., to make sure that restricted
|
.\" Often used as a security feature, e.g., to make sure that restricted
|
||||||
.\" users cannot execute files uploaded using ftp or so.)
|
.\" users cannot execute files uploaded using ftp or so.)
|
||||||
.TP
|
.TP
|
||||||
.B MS_NOSUID
|
.B MS_NOSUID
|
||||||
Do not honor set-user-ID and set-group-ID bits when executing
|
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
|
.\" (This is a security feature to prevent users executing set-user-ID and
|
||||||
.\" set-group-ID programs from removable disk devices.)
|
.\" set-group-ID programs from removable disk devices.)
|
||||||
.TP
|
.TP
|
||||||
.B MS_RDONLY
|
.B MS_RDONLY
|
||||||
Mount file system read-only.
|
Mount filesystem read-only.
|
||||||
.\"
|
.\"
|
||||||
.\" FIXME Document MS_REC, available since 2.4.11.
|
.\" FIXME Document MS_REC, available since 2.4.11.
|
||||||
.\" This flag has meaning in conjunction with MS_BIND and
|
.\" This flag has meaning in conjunction with MS_BIND and
|
||||||
.\" also with the shared subtree flags.
|
.\" also with the shared subtree flags.
|
||||||
.TP
|
.TP
|
||||||
.BR MS_RELATIME " (Since Linux 2.6.20)"
|
.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
|
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)
|
of atime is less than or equal to the file's last modification time (mtime)
|
||||||
or last status change time (ctime).
|
or last status change time (ctime).
|
||||||
|
@ -233,7 +233,7 @@ This allows you to change the
|
||||||
.I mountflags
|
.I mountflags
|
||||||
and
|
and
|
||||||
.I data
|
.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
|
.I target
|
||||||
should be the same value specified in the initial
|
should be the same value specified in the initial
|
||||||
.BR mount ()
|
.BR mount ()
|
||||||
|
@ -268,7 +268,7 @@ flag (available since Linux 2.4.12), which has the same meaning.
|
||||||
.TP
|
.TP
|
||||||
.BR MS_STRICTATIME " (Since Linux 2.6.30)"
|
.BR MS_STRICTATIME " (Since Linux 2.6.30)"
|
||||||
Always update the last access time (atime) when files on this
|
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.)
|
(This was the default behavior before Linux 2.6.30.)
|
||||||
Specifying this flag overrides the effect of setting the
|
Specifying this flag overrides the effect of setting the
|
||||||
.BR MS_NOATIME
|
.BR MS_NOATIME
|
||||||
|
@ -277,12 +277,12 @@ and
|
||||||
flags.
|
flags.
|
||||||
.TP
|
.TP
|
||||||
.B MS_SYNCHRONOUS
|
.B MS_SYNCHRONOUS
|
||||||
Make writes on this file system synchronous (as though
|
Make writes on this filesystem synchronous (as though
|
||||||
the
|
the
|
||||||
.B O_SYNC
|
.B O_SYNC
|
||||||
flag to
|
flag to
|
||||||
.BR open (2)
|
.BR open (2)
|
||||||
was specified for all file opens to this file system).
|
was specified for all file opens to this filesystem).
|
||||||
.PP
|
.PP
|
||||||
From Linux 2.4 onward, the
|
From Linux 2.4 onward, the
|
||||||
.BR MS_NODEV ", " MS_NOEXEC ", and " MS_NOSUID
|
.BR MS_NODEV ", " MS_NOEXEC ", and " MS_NOSUID
|
||||||
|
@ -298,9 +298,9 @@ flag is also settable on a per-mount-point basis.
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.I data
|
.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
|
Typically it is a string of comma-separated options
|
||||||
understood by this file system.
|
understood by this filesystem.
|
||||||
See
|
See
|
||||||
.BR mount (8)
|
.BR mount (8)
|
||||||
for details of the options available for each filesystem type.
|
for details of the options available for each filesystem type.
|
||||||
|
@ -312,7 +312,7 @@ is set appropriately.
|
||||||
.SH ERRORS
|
.SH ERRORS
|
||||||
The error values given below result from filesystem type independent
|
The error values given below result from filesystem type independent
|
||||||
errors.
|
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.
|
own special behavior.
|
||||||
See the Linux kernel source code for details.
|
See the Linux kernel source code for details.
|
||||||
.TP
|
.TP
|
||||||
|
@ -320,12 +320,12 @@ See the Linux kernel source code for details.
|
||||||
A component of a path was not searchable.
|
A component of a path was not searchable.
|
||||||
(See also
|
(See also
|
||||||
.BR path_resolution (7).)
|
.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
|
.B MS_RDONLY
|
||||||
flag.
|
flag.
|
||||||
Or, the block device
|
Or, the block device
|
||||||
.I source
|
.I source
|
||||||
is located on a file system mounted with the
|
is located on a filesystem mounted with the
|
||||||
.B MS_NODEV
|
.B MS_NODEV
|
||||||
option.
|
option.
|
||||||
.\" mtk: Probably: write permission is required for MS_BIND, with
|
.\" mtk: Probably: write permission is required for MS_BIND, with
|
||||||
|
@ -428,7 +428,7 @@ when a different
|
||||||
was added to \fI<mman.h>\fP.
|
was added to \fI<mman.h>\fP.
|
||||||
.LP
|
.LP
|
||||||
Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
|
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
|
.B MS_NOSUID
|
||||||
would fail with
|
would fail with
|
||||||
.BR EPERM .
|
.BR EPERM .
|
||||||
|
@ -438,7 +438,7 @@ just silently ignored in this case.
|
||||||
.SS Per-process namespaces
|
.SS Per-process namespaces
|
||||||
Starting with kernel 2.4.19, Linux provides
|
Starting with kernel 2.4.19, Linux provides
|
||||||
per-process mount namespaces.
|
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.
|
are visible to a process.
|
||||||
Mount-point namespaces can be (and usually are)
|
Mount-point namespaces can be (and usually are)
|
||||||
shared between multiple processes,
|
shared between multiple processes,
|
||||||
|
|
|
@ -124,13 +124,13 @@ This is a zero page or the memory area is not mapped by the process.
|
||||||
.B -EIO
|
.B -EIO
|
||||||
Unable to write back a page.
|
Unable to write back a page.
|
||||||
The page has to be written back
|
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
|
does not provide a migration function that would allow the move
|
||||||
of dirty pages.
|
of dirty pages.
|
||||||
.TP
|
.TP
|
||||||
.B -EINVAL
|
.B -EINVAL
|
||||||
A dirty page cannot be moved.
|
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.
|
provide a migration function and has no ability to write back pages.
|
||||||
.TP
|
.TP
|
||||||
.B -ENOENT
|
.B -ENOENT
|
||||||
|
|
|
@ -333,7 +333,7 @@ and
|
||||||
operations are used by the
|
operations are used by the
|
||||||
.BR ipcs (1)
|
.BR ipcs (1)
|
||||||
program to provide information on allocated resources.
|
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.
|
interface.
|
||||||
|
|
||||||
Various fields in the \fIstruct msqid_ds\fP were
|
Various fields in the \fIstruct msqid_ds\fP were
|
||||||
|
|
|
@ -26,8 +26,8 @@ Since Linux 3.1, this system call no longer exists.
|
||||||
#define NFSCTL_SVC 0 /* This is a server process. */
|
#define NFSCTL_SVC 0 /* This is a server process. */
|
||||||
#define NFSCTL_ADDCLIENT 1 /* Add an NFS client. */
|
#define NFSCTL_ADDCLIENT 1 /* Add an NFS client. */
|
||||||
#define NFSCTL_DELCLIENT 2 /* Remove an NFS client. */
|
#define NFSCTL_DELCLIENT 2 /* Remove an NFS client. */
|
||||||
#define NFSCTL_EXPORT 3 /* Export a file system. */
|
#define NFSCTL_EXPORT 3 /* Export a filesystem. */
|
||||||
#define NFSCTL_UNEXPORT 4 /* Unexport a file system. */
|
#define NFSCTL_UNEXPORT 4 /* Unexport a filesystem. */
|
||||||
#define NFSCTL_UGIDUPDATE 5 /* Update a client's UID/GID map
|
#define NFSCTL_UGIDUPDATE 5 /* Update a client's UID/GID map
|
||||||
(only in Linux 2.4.x and earlier). */
|
(only in Linux 2.4.x and earlier). */
|
||||||
#define NFSCTL_GETFH 6 /* Get a file handle (used by mountd)
|
#define NFSCTL_GETFH 6 /* Get a file handle (used by mountd)
|
||||||
|
|
36
man2/open.2
36
man2/open.2
|
@ -158,7 +158,7 @@ the file offset is positioned at the end of the file,
|
||||||
as if with
|
as if with
|
||||||
.BR lseek (2).
|
.BR lseek (2).
|
||||||
.B O_APPEND
|
.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.
|
appends data to a file at once.
|
||||||
.\" For more background, see
|
.\" For more background, see
|
||||||
.\" http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453946
|
.\" http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453946
|
||||||
|
@ -211,7 +211,7 @@ The owner (user ID) of the file is set to the effective user ID
|
||||||
of the process.
|
of the process.
|
||||||
The group ownership (group ID) is set either to
|
The group ownership (group ID) is set either to
|
||||||
the effective group ID of the process or to the group ID of the
|
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
|
and the mode of the parent directory, see the mount options
|
||||||
.I bsdgroups
|
.I bsdgroups
|
||||||
and
|
and
|
||||||
|
@ -362,7 +362,7 @@ Portable programs that want to perform atomic file locking using a lockfile,
|
||||||
and need to avoid reliance on NFS support for
|
and need to avoid reliance on NFS support for
|
||||||
.BR O_EXCL ,
|
.BR O_EXCL ,
|
||||||
can create a unique file on
|
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)
|
.BR link (2)
|
||||||
to make a link to the lockfile.
|
to make a link to the lockfile.
|
||||||
If
|
If
|
||||||
|
@ -403,7 +403,7 @@ when the file is
|
||||||
.BR read (2).
|
.BR read (2).
|
||||||
This flag is intended for use by indexing or backup programs,
|
This flag is intended for use by indexing or backup programs,
|
||||||
where its use can significantly reduce the amount of disk activity.
|
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.
|
One example is NFS, where the server maintains the access time.
|
||||||
.\" The O_NOATIME flag also affects the treatment of st_atime
|
.\" The O_NOATIME flag also affects the treatment of st_atime
|
||||||
.\" by mmap() and readdir(2), MTK, Dec 04.
|
.\" by mmap() and readdir(2), MTK, Dec 04.
|
||||||
|
@ -451,7 +451,7 @@ in conjunction with mandatory file locks and with file leases, see
|
||||||
.\" Newsgroups: gmane.linux.man, gmane.linux.kernel
|
.\" Newsgroups: gmane.linux.man, gmane.linux.kernel
|
||||||
.\"
|
.\"
|
||||||
Obtain a file descriptor that can be used for two purposes:
|
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.
|
to perform operations that act purely at the file descriptor level.
|
||||||
The file itself is not opened, and other file operations (e.g.,
|
The file itself is not opened, and other file operations (e.g.,
|
||||||
.BR read (2),
|
.BR read (2),
|
||||||
|
@ -587,7 +587,7 @@ is not allowed.
|
||||||
Where
|
Where
|
||||||
.B O_CREAT
|
.B O_CREAT
|
||||||
is specified, the file does not exist, and the user's quota of disk
|
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
|
.TP
|
||||||
.B EEXIST
|
.B EEXIST
|
||||||
.I pathname
|
.I pathname
|
||||||
|
@ -696,13 +696,13 @@ for this case.
|
||||||
The
|
The
|
||||||
.B O_NOATIME
|
.B O_NOATIME
|
||||||
flag was specified, but the effective user ID of the caller
|
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
|
did not match the owner of the file and the caller was not privileged
|
||||||
.RB ( CAP_FOWNER ).
|
.RB ( CAP_FOWNER ).
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I pathname
|
.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.
|
requested.
|
||||||
.TP
|
.TP
|
||||||
.B ETXTBSY
|
.B ETXTBSY
|
||||||
|
@ -810,7 +810,7 @@ and
|
||||||
.B O_RSYNC
|
.B O_RSYNC
|
||||||
to the same numerical value as
|
to the same numerical value as
|
||||||
.BR O_SYNC .
|
.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
|
.B O_SYNC
|
||||||
semantics, which require all metadata updates of a write
|
semantics, which require all metadata updates of a write
|
||||||
to be on disk on returning to user space, but only the
|
to be on disk on returning to user space, but only the
|
||||||
|
@ -826,7 +826,7 @@ cannot create them; use
|
||||||
.BR mknod (2)
|
.BR mknod (2)
|
||||||
instead.
|
instead.
|
||||||
.LP
|
.LP
|
||||||
On NFS file systems with UID mapping enabled,
|
On NFS filesystems with UID mapping enabled,
|
||||||
.BR open ()
|
.BR open ()
|
||||||
may
|
may
|
||||||
return a file descriptor but, for example,
|
return a file descriptor but, for example,
|
||||||
|
@ -864,12 +864,12 @@ The
|
||||||
flag may impose alignment restrictions on the length and address
|
flag may impose alignment restrictions on the length and address
|
||||||
of user-space buffers and the file offset of I/Os.
|
of user-space buffers and the file offset of I/Os.
|
||||||
In Linux alignment
|
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.
|
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
|
interface for an application to discover these restrictions for a given
|
||||||
file or file system.
|
file or filesystem.
|
||||||
Some file systems provide their own interfaces
|
Some filesystems provide their own interfaces
|
||||||
for doing so, for example the
|
for doing so, for example the
|
||||||
.B XFS_IOC_DIOINFO
|
.B XFS_IOC_DIOINFO
|
||||||
operation in
|
operation in
|
||||||
|
@ -877,7 +877,7 @@ operation in
|
||||||
.LP
|
.LP
|
||||||
Under Linux 2.4, transfer sizes, and the alignment of the user buffer
|
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
|
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.
|
Under Linux 2.6, alignment to 512-byte boundaries suffices.
|
||||||
.LP
|
.LP
|
||||||
.B O_DIRECT
|
.B O_DIRECT
|
||||||
|
@ -927,7 +927,7 @@ a flag of the same name, but without alignment restrictions.
|
||||||
.B O_DIRECT
|
.B O_DIRECT
|
||||||
support was added under Linux in kernel version 2.4.10.
|
support was added under Linux in kernel version 2.4.10.
|
||||||
Older Linux kernels simply ignore this flag.
|
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 ()
|
.BR open ()
|
||||||
will fail with
|
will fail with
|
||||||
.B EINVAL
|
.B EINVAL
|
||||||
|
@ -937,7 +937,7 @@ Applications should avoid mixing
|
||||||
.B O_DIRECT
|
.B O_DIRECT
|
||||||
and normal I/O to the same file,
|
and normal I/O to the same file,
|
||||||
and especially to overlapping byte regions in 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
|
this situation, overall I/O throughput is likely to be slower than
|
||||||
using either mode alone.
|
using either mode alone.
|
||||||
Likewise, applications should avoid mixing
|
Likewise, applications should avoid mixing
|
||||||
|
@ -946,7 +946,7 @@ of files with direct I/O to the same files.
|
||||||
.LP
|
.LP
|
||||||
The behaviour of
|
The behaviour of
|
||||||
.B O_DIRECT
|
.B O_DIRECT
|
||||||
with NFS will differ from local file systems.
|
with NFS will differ from local filesystems.
|
||||||
Older kernels, or
|
Older kernels, or
|
||||||
kernels configured in certain ways, may not support this combination.
|
kernels configured in certain ways, may not support this combination.
|
||||||
The NFS protocol does not support passing the flag to the server, so
|
The NFS protocol does not support passing the flag to the server, so
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH PIVOT_ROOT 2 2012-07-13 "Linux" "Linux Programmer's Manual"
|
.TH PIVOT_ROOT 2 2012-07-13 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
pivot_root \- change the root file system
|
pivot_root \- change the root filesystem
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.BI "int pivot_root(const char *" new_root ", const char *" put_old );
|
.BI "int pivot_root(const char *" new_root ", const char *" put_old );
|
||||||
|
|
||||||
|
@ -17,8 +17,8 @@ pivot_root \- change the root file system
|
||||||
There is no glibc wrapper for this system call; see NOTES.
|
There is no glibc wrapper for this system call; see NOTES.
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR pivot_root ()
|
.BR pivot_root ()
|
||||||
moves the root file system of the calling process to the
|
moves the root filesystem of the calling process to the
|
||||||
directory \fIput_old\fP and makes \fInew_root\fP the new root file system
|
directory \fIput_old\fP and makes \fInew_root\fP the new root filesystem
|
||||||
of the calling process.
|
of the calling process.
|
||||||
.\"
|
.\"
|
||||||
.\" The
|
.\" The
|
||||||
|
@ -28,8 +28,8 @@ of the calling process.
|
||||||
The typical use of
|
The typical use of
|
||||||
.BR pivot_root ()
|
.BR pivot_root ()
|
||||||
is during system startup, when the
|
is during system startup, when the
|
||||||
system mounts a temporary root file system (e.g., an \fBinitrd\fP), then
|
system mounts a temporary root filesystem (e.g., an \fBinitrd\fP), then
|
||||||
mounts the real root file system, and eventually turns the latter into
|
mounts the real root filesystem, and eventually turns the latter into
|
||||||
the current root of all relevant processes or threads.
|
the current root of all relevant processes or threads.
|
||||||
|
|
||||||
.BR pivot_root ()
|
.BR pivot_root ()
|
||||||
|
@ -56,9 +56,9 @@ This
|
||||||
is necessary in order to prevent kernel threads from keeping the old
|
is necessary in order to prevent kernel threads from keeping the old
|
||||||
root directory busy with their root and current working directory,
|
root directory busy with their root and current working directory,
|
||||||
even if they never access
|
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
|
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
|
such that this fairly intrusive mechanism can be removed from
|
||||||
.BR pivot_root ().
|
.BR pivot_root ().
|
||||||
|
|
||||||
|
@ -74,14 +74,14 @@ The following restrictions apply to \fInew_root\fP and \fIput_old\fP:
|
||||||
.IP \- 3
|
.IP \- 3
|
||||||
They must be directories.
|
They must be directories.
|
||||||
.IP \- 3
|
.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.
|
the current root.
|
||||||
.IP \- 3
|
.IP \- 3
|
||||||
\fIput_old\fP must be underneath \fInew_root\fP, that is, adding a nonzero
|
\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
|
number of \fI/..\fP to the string pointed to by \fIput_old\fP must yield
|
||||||
the same directory as \fInew_root\fP.
|
the same directory as \fInew_root\fP.
|
||||||
.IP \- 3
|
.IP \- 3
|
||||||
No other file system may be mounted on \fIput_old\fP.
|
No other filesystem may be mounted on \fIput_old\fP.
|
||||||
.PP
|
.PP
|
||||||
See also
|
See also
|
||||||
.BR pivot_root (8)
|
.BR pivot_root (8)
|
||||||
|
@ -92,11 +92,11 @@ If the current root is not a mount point (e.g., after
|
||||||
or
|
or
|
||||||
.BR pivot_root (),
|
.BR pivot_root (),
|
||||||
see also below), not the old root directory, but the
|
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.
|
\fInew_root\fP does not have to be a mount point.
|
||||||
In this case,
|
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).
|
\fInew_root\fP as root (\fI/\fP).
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
On success, zero is returned.
|
On success, zero is returned.
|
||||||
|
@ -109,8 +109,8 @@ may return (in \fIerrno\fP) any of the errors returned by
|
||||||
Additionally, it may return:
|
Additionally, it may return:
|
||||||
.TP
|
.TP
|
||||||
.B EBUSY
|
.B EBUSY
|
||||||
\fInew_root\fP or \fIput_old\fP are on the current root file system,
|
\fInew_root\fP or \fIput_old\fP are on the current root filesystem,
|
||||||
or a file system is already mounted on \fIput_old\fP.
|
or a filesystem is already mounted on \fIput_old\fP.
|
||||||
.TP
|
.TP
|
||||||
.B EINVAL
|
.B EINVAL
|
||||||
\fIput_old\fP is not underneath \fInew_root\fP.
|
\fIput_old\fP is not underneath \fInew_root\fP.
|
||||||
|
|
|
@ -38,9 +38,9 @@ quotactl \- manipulate disk quotas
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.LP
|
.LP
|
||||||
The quota system can be used to set per-user and per-group limits on the
|
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,
|
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 hard limit can't be exceeded.
|
||||||
The soft limit can be exceeded, but warnings will ensue.
|
The soft limit can be exceeded, but warnings will ensue.
|
||||||
Moreover, the user can't exceed the soft limit for more than one week
|
Moreover, the user can't exceed the soft limit for more than one week
|
||||||
|
@ -75,7 +75,7 @@ value is described below.
|
||||||
The
|
The
|
||||||
.I special
|
.I special
|
||||||
argument is a pointer to a null-terminated string containing the pathname
|
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
|
The
|
||||||
.I addr
|
.I addr
|
||||||
|
@ -90,7 +90,7 @@ The
|
||||||
value is one of the following:
|
value is one of the following:
|
||||||
.TP 8
|
.TP 8
|
||||||
.B Q_QUOTAON
|
.B Q_QUOTAON
|
||||||
Turn on quotas for a file system.
|
Turn on quotas for a filesystem.
|
||||||
The
|
The
|
||||||
.I id
|
.I id
|
||||||
argument is the identification number of the quota format to be used.
|
argument is the identification number of the quota format to be used.
|
||||||
|
@ -112,7 +112,7 @@ and quota limits of 2^64 bytes and 2^64 inodes.
|
||||||
The
|
The
|
||||||
.IR addr
|
.IR addr
|
||||||
argument points to the pathname of a file containing the quotas for
|
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
|
The quota file must exist; it is normally created with the
|
||||||
.BR quotacheck (8)
|
.BR quotacheck (8)
|
||||||
program.
|
program.
|
||||||
|
@ -120,7 +120,7 @@ This operation requires privilege
|
||||||
.RB ( CAP_SYS_ADMIN ).
|
.RB ( CAP_SYS_ADMIN ).
|
||||||
.TP 8
|
.TP 8
|
||||||
.B Q_QUOTAOFF
|
.B Q_QUOTAOFF
|
||||||
Turn off quotas for a file system.
|
Turn off quotas for a filesystem.
|
||||||
The
|
The
|
||||||
.I addr
|
.I addr
|
||||||
and
|
and
|
||||||
|
@ -300,17 +300,17 @@ This operation requires privilege
|
||||||
.RB ( CAP_SYS_ADMIN ).
|
.RB ( CAP_SYS_ADMIN ).
|
||||||
.TP
|
.TP
|
||||||
.B Q_GETFMT
|
.B Q_GETFMT
|
||||||
Get quota format used on the specified file system.
|
Get quota format used on the specified filesystem.
|
||||||
The
|
The
|
||||||
.I addr
|
.I addr
|
||||||
argument should be a pointer to a 4-byte buffer
|
argument should be a pointer to a 4-byte buffer
|
||||||
where the format number will be stored.
|
where the format number will be stored.
|
||||||
.TP
|
.TP
|
||||||
.B Q_SYNC
|
.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
|
If
|
||||||
.I special
|
.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
|
The
|
||||||
.I addr
|
.I addr
|
||||||
and
|
and
|
||||||
|
@ -337,11 +337,11 @@ Files in
|
||||||
.I /proc/sys/fs/quota/
|
.I /proc/sys/fs/quota/
|
||||||
carry the information instead.
|
carry the information instead.
|
||||||
.PP
|
.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:
|
the above commands are bypassed and the following commands are used:
|
||||||
.TP 8
|
.TP 8
|
||||||
.B Q_XQUOTAON
|
.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
|
XFS provides the ability to turn on/off quota limit enforcement
|
||||||
with quota accounting.
|
with quota accounting.
|
||||||
Therefore, XFS expects
|
Therefore, XFS expects
|
||||||
|
@ -362,10 +362,10 @@ This operation requires privilege
|
||||||
.RB ( CAP_SYS_ADMIN ).
|
.RB ( CAP_SYS_ADMIN ).
|
||||||
.TP
|
.TP
|
||||||
.B Q_XQUOTAOFF
|
.B Q_XQUOTAOFF
|
||||||
Turn off quotas for an XFS file system.
|
Turn off quotas for an XFS filesystem.
|
||||||
As with
|
As with
|
||||||
.BR Q_QUOTAON ,
|
.BR Q_QUOTAON ,
|
||||||
XFS file systems expect a pointer to an
|
XFS filesystems expect a pointer to an
|
||||||
.I "unsigned int"
|
.I "unsigned int"
|
||||||
that specifies whether quota accounting and/or limit enforcement need
|
that specifies whether quota accounting and/or limit enforcement need
|
||||||
to be turned off.
|
to be turned off.
|
||||||
|
@ -401,10 +401,10 @@ This operation requires privilege
|
||||||
.B Q_XGETQSTAT
|
.B Q_XGETQSTAT
|
||||||
Returns an
|
Returns an
|
||||||
.I fs_quota_stat
|
.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
|
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
|
information, and also to get quotaon/off status of a given local XFS
|
||||||
file system.
|
filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B Q_XQUOTARM
|
.B Q_XQUOTARM
|
||||||
Free the disk space taken by disk quotas.
|
Free the disk space taken by disk quotas.
|
||||||
|
@ -414,7 +414,7 @@ There is no command equivalent to
|
||||||
.B Q_SYNC
|
.B Q_SYNC
|
||||||
for XFS since
|
for XFS since
|
||||||
.BR sync (1)
|
.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).
|
metadata that it writes out).
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
.LP
|
.LP
|
||||||
|
@ -461,7 +461,7 @@ for the specified operation.
|
||||||
.TP
|
.TP
|
||||||
.B ESRCH
|
.B ESRCH
|
||||||
No disk quota is found for the indicated user.
|
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
|
.LP
|
||||||
If
|
If
|
||||||
.I cmd
|
.I cmd
|
||||||
|
@ -490,7 +490,7 @@ The quota file pointed to by
|
||||||
exists, but is not a regular file; or,
|
exists, but is not a regular file; or,
|
||||||
the quota file pointed to by
|
the quota file pointed to by
|
||||||
.I addr
|
.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 .
|
.IR special .
|
||||||
.TP
|
.TP
|
||||||
.B EBUSY
|
.B EBUSY
|
||||||
|
|
|
@ -173,7 +173,7 @@ or to return the number of bytes already read.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, POSIX.1-2001.
|
SVr4, 4.3BSD, POSIX.1-2001.
|
||||||
.SH NOTES
|
.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.
|
timestamp only the first time, subsequent calls may not do so.
|
||||||
This is caused
|
This is caused
|
||||||
by client side attribute caching, because most if not all NFS clients
|
by client side attribute caching, because most if not all NFS clients
|
||||||
|
|
|
@ -106,7 +106,7 @@ is not positive.
|
||||||
The named file is not a symbolic link.
|
The named file is not a symbolic link.
|
||||||
.TP
|
.TP
|
||||||
.B EIO
|
.B EIO
|
||||||
An I/O error occurred while reading from the file system.
|
An I/O error occurred while reading from the filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ELOOP
|
.B ELOOP
|
||||||
Too many symbolic links were encountered in translating the pathname.
|
Too many symbolic links were encountered in translating the pathname.
|
||||||
|
|
|
@ -52,7 +52,7 @@ removes the extended attribute identified by
|
||||||
.I name
|
.I name
|
||||||
and associated with the given
|
and associated with the given
|
||||||
.I path
|
.I path
|
||||||
in the file system.
|
in the filesystem.
|
||||||
.PP
|
.PP
|
||||||
.BR lremovexattr ()
|
.BR lremovexattr ()
|
||||||
is identical to
|
is identical to
|
||||||
|
@ -91,7 +91,7 @@ in
|
||||||
.IR <attr/xattr.h> .)
|
.IR <attr/xattr.h> .)
|
||||||
.TP
|
.TP
|
||||||
.B ENOTSUP
|
.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
|
.PP
|
||||||
In addition, the errors documented in
|
In addition, the errors documented in
|
||||||
.BR stat (2)
|
.BR stat (2)
|
||||||
|
|
|
@ -132,7 +132,7 @@ if the system cannot otherwise
|
||||||
handle such situations.)
|
handle such situations.)
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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
|
.TP
|
||||||
.B EFAULT
|
.B EFAULT
|
||||||
.IR oldpath " or " newpath " points outside your accessible address space."
|
.IR oldpath " or " newpath " points outside your accessible address space."
|
||||||
|
@ -215,24 +215,24 @@ and the process is not privileged
|
||||||
(Linux: does not have the
|
(Linux: does not have the
|
||||||
.B CAP_FOWNER
|
.B CAP_FOWNER
|
||||||
capability);
|
capability);
|
||||||
or the file system containing
|
or the filesystem containing
|
||||||
.I pathname
|
.I pathname
|
||||||
does not support renaming of the type requested.
|
does not support renaming of the type requested.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The file is on a read-only file system.
|
The file is on a read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B EXDEV
|
.B EXDEV
|
||||||
.IR oldpath " and " newpath
|
.IR oldpath " and " newpath
|
||||||
are not on the same mounted file system.
|
are not on the same mounted filesystem.
|
||||||
(Linux permits a file system to be mounted at multiple points, but
|
(Linux permits a filesystem to be mounted at multiple points, but
|
||||||
.BR rename ()
|
.BR rename ()
|
||||||
does not work across different mount points,
|
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
|
.SH CONFORMING TO
|
||||||
4.3BSD, C89, C99, POSIX.1-2001.
|
4.3BSD, C89, C99, POSIX.1-2001.
|
||||||
.SH BUGS
|
.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.
|
failed the file was not renamed.
|
||||||
If the server does the rename operation
|
If the server does the rename operation
|
||||||
and then crashes, the retransmitted RPC which will be processed when the
|
and then crashes, the retransmitted RPC which will be processed when the
|
||||||
|
|
|
@ -117,13 +117,13 @@ and the process is not privileged (Linux: does not have the
|
||||||
capability).
|
capability).
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
The file system containing
|
The filesystem containing
|
||||||
.I pathname
|
.I pathname
|
||||||
does not support the removal of directories.
|
does not support the removal of directories.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I pathname
|
.I pathname
|
||||||
refers to a directory on a read-only file system.
|
refers to a directory on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, POSIX.1-2001.
|
SVr4, 4.3BSD, POSIX.1-2001.
|
||||||
.SH BUGS
|
.SH BUGS
|
||||||
|
|
|
@ -495,7 +495,7 @@ and
|
||||||
operations are used by the
|
operations are used by the
|
||||||
.BR ipcs (1)
|
.BR ipcs (1)
|
||||||
program to provide information on allocated resources.
|
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.
|
interface.
|
||||||
.LP
|
.LP
|
||||||
Various fields in a \fIstruct semid_ds\fP were typed as
|
Various fields in a \fIstruct semid_ds\fP were typed as
|
||||||
|
|
|
@ -30,7 +30,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH SETFSGID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
|
.TH SETFSGID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
setfsgid \- set group identity used for file system checks
|
setfsgid \- set group identity used for filesystem checks
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B #include <unistd.h>
|
.B #include <unistd.h>
|
||||||
/* glibc uses <sys/fsuid.h> */
|
/* glibc uses <sys/fsuid.h> */
|
||||||
|
@ -40,7 +40,7 @@ setfsgid \- set group identity used for file system checks
|
||||||
The system call
|
The system call
|
||||||
.BR setfsgid ()
|
.BR setfsgid ()
|
||||||
sets the group ID that the Linux kernel uses to check for all accesses
|
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
|
Normally, the value of
|
||||||
.I fsgid
|
.I fsgid
|
||||||
will shadow the value of the effective group ID.
|
will shadow the value of the effective group ID.
|
||||||
|
|
|
@ -30,7 +30,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH SETFSUID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
|
.TH SETFSUID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
setfsuid \- set user identity used for file system checks
|
setfsuid \- set user identity used for filesystem checks
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B #include <unistd.h>
|
.B #include <unistd.h>
|
||||||
/* glibc uses <sys/fsuid.h> */
|
/* glibc uses <sys/fsuid.h> */
|
||||||
|
@ -40,7 +40,7 @@ setfsuid \- set user identity used for file system checks
|
||||||
The system call
|
The system call
|
||||||
.BR setfsuid ()
|
.BR setfsuid ()
|
||||||
sets the user ID that the Linux kernel uses to check for all accesses
|
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
|
Normally, the value of
|
||||||
.I fsuid
|
.I fsuid
|
||||||
will shadow the value of the effective user ID.
|
will shadow the value of the effective user ID.
|
||||||
|
|
|
@ -52,13 +52,13 @@ saved set-user-ID to arbitrary values.
|
||||||
If one of the arguments equals \-1, the corresponding value is not changed.
|
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,
|
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.
|
value as the (possibly new) effective UID.
|
||||||
|
|
||||||
Completely analogously,
|
Completely analogously,
|
||||||
.BR setresgid ()
|
.BR setresgid ()
|
||||||
sets the real GID, effective GID, and saved set-group-ID
|
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),
|
to be the same as the effective GID),
|
||||||
with the same restrictions for unprivileged processes.
|
with the same restrictions for unprivileged processes.
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
|
|
|
@ -95,11 +95,11 @@ Not quite compatible with the 4.4BSD call, which
|
||||||
sets all of the real, saved, and effective user IDs.
|
sets all of the real, saved, and effective user IDs.
|
||||||
.\" SVr4 documents an additional EINVAL error condition.
|
.\" SVr4 documents an additional EINVAL error condition.
|
||||||
.SH NOTES
|
.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.
|
effective user ID.
|
||||||
The
|
The
|
||||||
.BR setuid ()
|
.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
|
See
|
||||||
.BR setfsuid (2).
|
.BR setfsuid (2).
|
||||||
.PP
|
.PP
|
||||||
|
|
|
@ -33,7 +33,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH SETUP 2 2008-12-03 "Linux" "Linux Programmer's Manual"
|
.TH SETUP 2 2008-12-03 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
setup \- setup devices and file systems, mount root file system
|
setup \- setup devices and filesystems, mount root filesystem
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B #include <unistd.h>
|
.B #include <unistd.h>
|
||||||
.sp
|
.sp
|
||||||
|
@ -42,8 +42,8 @@ setup \- setup devices and file systems, mount root file system
|
||||||
.BR setup ()
|
.BR setup ()
|
||||||
is called once from within
|
is called once from within
|
||||||
.IR linux/init/main.c .
|
.IR linux/init/main.c .
|
||||||
It calls initialization functions for devices and file systems
|
It calls initialization functions for devices and filesystems
|
||||||
configured into the kernel and then mounts the root file system.
|
configured into the kernel and then mounts the root filesystem.
|
||||||
.PP
|
.PP
|
||||||
No user process may call
|
No user process may call
|
||||||
.BR setup ().
|
.BR setup ().
|
||||||
|
|
|
@ -58,7 +58,7 @@ of the extended attribute identified by
|
||||||
.I name
|
.I name
|
||||||
and associated with the given
|
and associated with the given
|
||||||
.I path
|
.I path
|
||||||
in the file system.
|
in the filesystem.
|
||||||
The
|
The
|
||||||
.I size
|
.I size
|
||||||
of the
|
of the
|
||||||
|
@ -130,7 +130,7 @@ in
|
||||||
There is insufficient space remaining to store the extended attribute.
|
There is insufficient space remaining to store the extended attribute.
|
||||||
.TP
|
.TP
|
||||||
.B ENOTSUP
|
.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
|
.I errno
|
||||||
is set to
|
is set to
|
||||||
.BR ENOTSUP .
|
.BR ENOTSUP .
|
||||||
|
|
|
@ -397,7 +397,7 @@ and
|
||||||
operations are used by the
|
operations are used by the
|
||||||
.BR ipcs (1)
|
.BR ipcs (1)
|
||||||
program to provide information on allocated resources.
|
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.
|
interface.
|
||||||
|
|
||||||
Linux permits a process to attach
|
Linux permits a process to attach
|
||||||
|
|
|
@ -146,7 +146,7 @@ One or both file descriptors are not valid,
|
||||||
or do not have proper read-write mode.
|
or do not have proper read-write mode.
|
||||||
.TP
|
.TP
|
||||||
.B EINVAL
|
.B EINVAL
|
||||||
Target file system doesn't support splicing;
|
Target filesystem doesn't support splicing;
|
||||||
target file is opened in append mode;
|
target file is opened in append mode;
|
||||||
.\" The append-mode error is given since 2.6.27; in earlier kernels,
|
.\" The append-mode error is given since 2.6.27; in earlier kernels,
|
||||||
.\" splice() in append mode was broken
|
.\" splice() in append mode was broken
|
||||||
|
|
|
@ -48,7 +48,7 @@ It creates a new logical context for an SPU in
|
||||||
and returns a file descriptor associated with it.
|
and returns a file descriptor associated with it.
|
||||||
.I pathname
|
.I pathname
|
||||||
must refer to a nonexistent directory in the mount point of
|
must refer to a nonexistent directory in the mount point of
|
||||||
the SPU file system
|
the SPU filesystem
|
||||||
.RB ( spufs ).
|
.RB ( spufs ).
|
||||||
If
|
If
|
||||||
.BR spu_create ()
|
.BR spu_create ()
|
||||||
|
|
10
man2/stat.2
10
man2/stat.2
|
@ -116,7 +116,7 @@ struct stat {
|
||||||
gid_t st_gid; /* group ID of owner */
|
gid_t st_gid; /* group ID of owner */
|
||||||
dev_t st_rdev; /* device ID (if special file) */
|
dev_t st_rdev; /* device ID (if special file) */
|
||||||
off_t st_size; /* total size, in bytes */
|
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 */
|
blkcnt_t st_blocks; /* number of 512B blocks allocated */
|
||||||
time_t st_atime; /* time of last access */
|
time_t st_atime; /* time of last access */
|
||||||
time_t st_mtime; /* time of last modification */
|
time_t st_mtime; /* time of last modification */
|
||||||
|
@ -154,12 +154,12 @@ when the file has holes.)
|
||||||
|
|
||||||
The
|
The
|
||||||
.I st_blksize
|
.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
|
(Writing to a file in smaller chunks may cause
|
||||||
an inefficient read-modify-rewrite.)
|
an inefficient read-modify-rewrite.)
|
||||||
.PP
|
.PP
|
||||||
Not all of the Linux file systems implement all of the time fields.
|
Not all of the Linux filesystems implement all of the time fields.
|
||||||
Some file system types allow mounting in such a way that file
|
Some filesystem types allow mounting in such a way that file
|
||||||
and/or directory accesses do not cause an update of the
|
and/or directory accesses do not cause an update of the
|
||||||
.I st_atime
|
.I st_atime
|
||||||
field.
|
field.
|
||||||
|
@ -516,7 +516,7 @@ is defined with the value 700 or greater.
|
||||||
If none of the aforementioned macros are defined,
|
If none of the aforementioned macros are defined,
|
||||||
then the nanosecond values are exposed with names of the form
|
then the nanosecond values are exposed with names of the form
|
||||||
.IR st_atimensec .
|
.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.
|
the nanosecond fields are returned with the value 0.
|
||||||
.\" As at kernel 2.6.25, XFS and JFS support nanosecond timestamps,
|
.\" As at kernel 2.6.25, XFS and JFS support nanosecond timestamps,
|
||||||
.\" but ext2, ext3, and Reiserfs do not.
|
.\" but ext2, ext3, and Reiserfs do not.
|
||||||
|
|
|
@ -27,7 +27,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH STATFS 2 2010-11-21 "Linux" "Linux Programmer's Manual"
|
.TH STATFS 2 2010-11-21 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
statfs, fstatfs \- get file system statistics
|
statfs, fstatfs \- get filesystem statistics
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.BR "#include <sys/vfs.h> " "/* or <sys/statfs.h> */"
|
.BR "#include <sys/vfs.h> " "/* or <sys/statfs.h> */"
|
||||||
.sp
|
.sp
|
||||||
|
@ -37,9 +37,9 @@ statfs, fstatfs \- get file system statistics
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
The function
|
The function
|
||||||
.BR statfs ()
|
.BR statfs ()
|
||||||
returns information about a mounted file system.
|
returns information about a mounted filesystem.
|
||||||
.I path
|
.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
|
.I buf
|
||||||
is a pointer to a
|
is a pointer to a
|
||||||
.I statfs
|
.I statfs
|
||||||
|
@ -54,21 +54,21 @@ structure defined approximately as follows:
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
struct statfs {
|
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 */
|
__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_bfree; /* free blocks in fs */
|
||||||
fsblkcnt_t f_bavail; /* free blocks available to
|
fsblkcnt_t f_bavail; /* free blocks available to
|
||||||
unprivileged user */
|
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 */
|
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_namelen; /* maximum length of filenames */
|
||||||
__SWORD_TYPE f_frsize; /* fragment size (since Linux 2.6) */
|
__SWORD_TYPE f_frsize; /* fragment size (since Linux 2.6) */
|
||||||
__SWORD_TYPE f_spare[5];
|
__SWORD_TYPE f_spare[5];
|
||||||
};
|
};
|
||||||
|
|
||||||
File system types:
|
Filesystem types:
|
||||||
|
|
||||||
ADFS_SUPER_MAGIC 0xadf5
|
ADFS_SUPER_MAGIC 0xadf5
|
||||||
AFFS_SUPER_MAGIC 0xADFF
|
AFFS_SUPER_MAGIC 0xADFF
|
||||||
|
@ -122,7 +122,7 @@ Nobody knows what
|
||||||
.I f_fsid
|
.I f_fsid
|
||||||
is supposed to contain (but see below).
|
is supposed to contain (but see below).
|
||||||
.PP
|
.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 ()
|
.BR fstatfs ()
|
||||||
returns the same information about an open file referenced by descriptor
|
returns the same information about an open file referenced by descriptor
|
||||||
.IR fd .
|
.IR fd .
|
||||||
|
@ -155,7 +155,7 @@ points to an invalid address.
|
||||||
This call was interrupted by a signal.
|
This call was interrupted by a signal.
|
||||||
.TP
|
.TP
|
||||||
.B EIO
|
.B EIO
|
||||||
An I/O error occurred while reading from the file system.
|
An I/O error occurred while reading from the filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ELOOP
|
.B ELOOP
|
||||||
.RB ( statfs ())
|
.RB ( statfs ())
|
||||||
|
@ -177,7 +177,7 @@ does not exist.
|
||||||
Insufficient kernel memory was available.
|
Insufficient kernel memory was available.
|
||||||
.TP
|
.TP
|
||||||
.B ENOSYS
|
.B ENOSYS
|
||||||
The file system does not support this call.
|
The filesystem does not support this call.
|
||||||
.TP
|
.TP
|
||||||
.B ENOTDIR
|
.B ENOTDIR
|
||||||
.RB ( statfs ())
|
.RB ( statfs ())
|
||||||
|
@ -262,11 +262,11 @@ contains some random stuff such that the pair
|
||||||
.RI ( f_fsid , ino )
|
.RI ( f_fsid , ino )
|
||||||
uniquely determines a file.
|
uniquely determines a file.
|
||||||
Some operating systems use (a variation on) the device number, or the device number
|
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
|
Several OSes restrict giving out the
|
||||||
.I f_fsid
|
.I f_fsid
|
||||||
field to the superuser only (and zero it for unprivileged users),
|
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.
|
when NFS-exported, and giving it out is a security concern.
|
||||||
.LP
|
.LP
|
||||||
Under some operating systems the
|
Under some operating systems the
|
||||||
|
|
|
@ -126,7 +126,7 @@ exists, but refers neither to a regular file nor to a block device;
|
||||||
or, for
|
or, for
|
||||||
.BR swapon (),
|
.BR swapon (),
|
||||||
the indicated path does not contain a valid swap signature or
|
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 (),
|
.BR swapoff (),
|
||||||
.I path
|
.I path
|
||||||
is not currently a swap area.
|
is not currently a swap area.
|
||||||
|
|
|
@ -98,7 +98,7 @@ did not allow search permission.
|
||||||
.BR path_resolution (7).)
|
.BR path_resolution (7).)
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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
|
The resources could be inodes or disk blocks, depending on the file
|
||||||
system implementation.
|
system implementation.
|
||||||
.TP
|
.TP
|
||||||
|
@ -139,13 +139,13 @@ A component used as a directory in
|
||||||
is not, in fact, a directory.
|
is not, in fact, a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.B EPERM
|
||||||
The file system containing
|
The filesystem containing
|
||||||
.I newpath
|
.I newpath
|
||||||
does not support the creation of symbolic links.
|
does not support the creation of symbolic links.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I newpath
|
.I newpath
|
||||||
is on a read-only file system.
|
is on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, POSIX.1-2001.
|
SVr4, 4.3BSD, POSIX.1-2001.
|
||||||
.\" SVr4 documents additional error codes EDQUOT and ENOSYS.
|
.\" SVr4 documents additional error codes EDQUOT and ENOSYS.
|
||||||
|
|
|
@ -65,12 +65,12 @@ _GNU_SOURCE
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR sync ()
|
.BR sync ()
|
||||||
causes all buffered modifications to file metadata and data to be
|
causes all buffered modifications to file metadata and data to be
|
||||||
written to the underlying file systems.
|
written to the underlying filesystems.
|
||||||
|
|
||||||
.BR syncfs ()
|
.BR syncfs ()
|
||||||
is like
|
is like
|
||||||
.BR sync (),
|
.BR sync (),
|
||||||
but synchronizes just the file system containing file
|
but synchronizes just the filesystem containing file
|
||||||
referred to by the open file descriptor
|
referred to by the open file descriptor
|
||||||
.IR fd .
|
.IR fd .
|
||||||
.SH RETURN VALUE
|
.SH RETURN VALUE
|
||||||
|
|
|
@ -89,11 +89,11 @@ Therefore, unless the application is strictly performing overwrites of
|
||||||
already-instantiated disk blocks, there are no guarantees that the data will
|
already-instantiated disk blocks, there are no guarantees that the data will
|
||||||
be available after a crash.
|
be available after a crash.
|
||||||
There is no user interface to know if a write is purely an overwrite.
|
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 )
|
.IR btrfs )
|
||||||
an overwrite of existing allocated blocks is impossible.
|
an overwrite of existing allocated blocks is impossible.
|
||||||
When writing into preallocated space,
|
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.
|
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
|
This system call does not flush disk write caches and thus does not provide
|
||||||
any data integrity on systems with volatile disk write caches.
|
any data integrity on systems with volatile disk write caches.
|
||||||
|
|
22
man2/sysfs.2
22
man2/sysfs.2
|
@ -26,7 +26,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH SYSFS 2 2010-06-27 "Linux" "Linux Programmer's Manual"
|
.TH SYSFS 2 2010-06-27 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
sysfs \- get file system type information
|
sysfs \- get filesystem type information
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.BI "int sysfs(int " option ", const char *" fsname );
|
.BI "int sysfs(int " option ", const char *" fsname );
|
||||||
|
|
||||||
|
@ -35,7 +35,7 @@ sysfs \- get file system type information
|
||||||
.BI "int sysfs(int " option );
|
.BI "int sysfs(int " option );
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR sysfs ()
|
.BR sysfs ()
|
||||||
returns information about the file system types currently present in
|
returns information about the filesystem types currently present in
|
||||||
the kernel.
|
the kernel.
|
||||||
The specific form of the
|
The specific form of the
|
||||||
.BR sysfs ()
|
.BR sysfs ()
|
||||||
|
@ -44,14 +44,14 @@ call and the information returned depends on the
|
||||||
in effect:
|
in effect:
|
||||||
.TP 3
|
.TP 3
|
||||||
.B 1
|
.B 1
|
||||||
Translate the file-system identifier string
|
Translate the filesystem identifier string
|
||||||
.I fsname
|
.I fsname
|
||||||
into a file-system type index.
|
into a filesystem type index.
|
||||||
.TP
|
.TP
|
||||||
.B 2
|
.B 2
|
||||||
Translate the file-system type index
|
Translate the filesystem type index
|
||||||
.I fs_index
|
.I fs_index
|
||||||
into a null-terminated file-system identifier string.
|
into a null-terminated filesystem identifier string.
|
||||||
This string will
|
This string will
|
||||||
be written to the buffer pointed to by
|
be written to the buffer pointed to by
|
||||||
.IR buf .
|
.IR buf .
|
||||||
|
@ -60,18 +60,18 @@ Make sure that
|
||||||
has enough space to accept the string.
|
has enough space to accept the string.
|
||||||
.TP
|
.TP
|
||||||
.B 3
|
.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.
|
kernel.
|
||||||
.PP
|
.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
|
.SH RETURN VALUE
|
||||||
On success,
|
On success,
|
||||||
.BR sysfs ()
|
.BR sysfs ()
|
||||||
returns the file-system index for option
|
returns the filesystem index for option
|
||||||
.BR 1 ,
|
.BR 1 ,
|
||||||
zero for option
|
zero for option
|
||||||
.BR 2 ,
|
.BR 2 ,
|
||||||
and the number of currently configured file systems for option
|
and the number of currently configured filesystems for option
|
||||||
.BR 3 .
|
.BR 3 .
|
||||||
On error, \-1 is returned, and
|
On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
|
@ -84,7 +84,7 @@ is outside your accessible address space.
|
||||||
.TP
|
.TP
|
||||||
.B EINVAL
|
.B EINVAL
|
||||||
.I fsname
|
.I fsname
|
||||||
is not a valid file-system type identifier;
|
is not a valid filesystem type identifier;
|
||||||
.I fs_index
|
.I fs_index
|
||||||
is out-of-bounds;
|
is out-of-bounds;
|
||||||
.I option
|
.I option
|
||||||
|
|
|
@ -163,13 +163,13 @@ The named file does not exist.
|
||||||
A component of the path prefix is not a directory.
|
A component of the path prefix is not a directory.
|
||||||
.TP
|
.TP
|
||||||
.B EPERM
|
.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
|
.\" 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.
|
a file beyond its current size.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The named file resides on a read-only file system.
|
The named file resides on a read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ETXTBSY
|
.B ETXTBSY
|
||||||
The file is a pure procedure (shared text) file that is being executed.
|
The file is a pure procedure (shared text) file that is being executed.
|
||||||
|
@ -218,8 +218,8 @@ exceeds the file length
|
||||||
is not specified at all in such an environment):
|
is not specified at all in such an environment):
|
||||||
either returning an error, or extending the file.
|
either returning an error, or extending the file.
|
||||||
Like most UNIX implementations, Linux follows the XSI requirement
|
Like most UNIX implementations, Linux follows the XSI requirement
|
||||||
when dealing with native file systems.
|
when dealing with native filesystems.
|
||||||
However, some nonnative file systems do not permit
|
However, some nonnative filesystems do not permit
|
||||||
.BR truncate ()
|
.BR truncate ()
|
||||||
and
|
and
|
||||||
.BR ftruncate ()
|
.BR ftruncate ()
|
||||||
|
|
|
@ -29,7 +29,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH UMOUNT 2 2010-06-19 "Linux" "Linux Programmer's Manual"
|
.TH UMOUNT 2 2010-06-19 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
umount, umount2 \- unmount file system
|
umount, umount2 \- unmount filesystem
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.nf
|
.nf
|
||||||
.B "#include <sys/mount.h>"
|
.B "#include <sys/mount.h>"
|
||||||
|
@ -42,7 +42,7 @@ umount, umount2 \- unmount file system
|
||||||
.BR umount ()
|
.BR umount ()
|
||||||
and
|
and
|
||||||
.BR umount2 ()
|
.BR umount2 ()
|
||||||
remove the attachment of the (topmost) file system mounted on
|
remove the attachment of the (topmost) filesystem mounted on
|
||||||
.IR target .
|
.IR target .
|
||||||
.\" Note: the kernel naming differs from the glibc naming
|
.\" Note: the kernel naming differs from the glibc naming
|
||||||
.\" umount2 is the glibc name for what the kernel now calls umount
|
.\" umount2 is the glibc name for what the kernel now calls umount
|
||||||
|
@ -50,7 +50,7 @@ remove the attachment of the (topmost) file system mounted on
|
||||||
|
|
||||||
Appropriate privilege (Linux: the
|
Appropriate privilege (Linux: the
|
||||||
.B CAP_SYS_ADMIN
|
.B CAP_SYS_ADMIN
|
||||||
capability) is required to unmount file systems.
|
capability) is required to unmount filesystems.
|
||||||
|
|
||||||
Linux 2.1.116 added the
|
Linux 2.1.116 added the
|
||||||
.BR umount2 ()
|
.BR umount2 ()
|
||||||
|
@ -95,16 +95,16 @@ Don't dereference
|
||||||
.I target
|
.I target
|
||||||
if it is a symbolic link.
|
if it is a symbolic link.
|
||||||
This flag allows security problems to be avoided in set-user-ID-\fIroot\fP
|
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
|
.SH RETURN VALUE
|
||||||
On success, zero is returned.
|
On success, zero is returned.
|
||||||
On error, \-1 is returned, and
|
On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.SH ERRORS
|
||||||
The error values given below result from file-system type independent
|
The error values given below result from filesystem type independent
|
||||||
errors.
|
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.
|
own special behavior.
|
||||||
See the Linux kernel source code for details.
|
See the Linux kernel source code for details.
|
||||||
.TP
|
.TP
|
||||||
|
@ -113,7 +113,7 @@ A call to
|
||||||
.BR umount2 ()
|
.BR umount2 ()
|
||||||
specifying
|
specifying
|
||||||
.B MNT_EXPIRE
|
.B MNT_EXPIRE
|
||||||
successfully marked an unbusy file system as expired.
|
successfully marked an unbusy filesystem as expired.
|
||||||
.TP
|
.TP
|
||||||
.B EBUSY
|
.B EBUSY
|
||||||
.I target
|
.I target
|
||||||
|
|
|
@ -38,7 +38,7 @@ unlink \- delete a name and possibly the file it refers to
|
||||||
.BI "int unlink(const char *" pathname );
|
.BI "int unlink(const char *" pathname );
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR unlink ()
|
.BR unlink ()
|
||||||
deletes a name from the file system.
|
deletes a name from the filesystem.
|
||||||
If that name was the
|
If that name was the
|
||||||
last link to a file and no processes have the file open the file is
|
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.
|
deleted and the space it was using is made available for reuse.
|
||||||
|
@ -122,7 +122,7 @@ as noted above, Linux returns
|
||||||
for this case.)
|
for this case.)
|
||||||
.TP
|
.TP
|
||||||
.BR EPERM " (Linux only)"
|
.BR EPERM " (Linux only)"
|
||||||
The file system does not allow unlinking of files.
|
The filesystem does not allow unlinking of files.
|
||||||
.TP
|
.TP
|
||||||
.BR EPERM " or " EACCES
|
.BR EPERM " or " EACCES
|
||||||
The directory containing
|
The directory containing
|
||||||
|
@ -137,7 +137,7 @@ capability).
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I pathname
|
.I pathname
|
||||||
refers to a file on a read-only file system.
|
refers to a file on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, POSIX.1-2001.
|
SVr4, 4.3BSD, POSIX.1-2001.
|
||||||
.\" SVr4 documents additional error
|
.\" SVr4 documents additional error
|
||||||
|
|
|
@ -85,7 +85,7 @@ Reverse the effect of the
|
||||||
.BR clone (2)
|
.BR clone (2)
|
||||||
.B CLONE_FS
|
.B CLONE_FS
|
||||||
flag.
|
flag.
|
||||||
Unshare file system attributes, so that the calling process
|
Unshare filesystem attributes, so that the calling process
|
||||||
no longer shares its root directory
|
no longer shares its root directory
|
||||||
.RB ( chroot (2)),
|
.RB ( chroot (2)),
|
||||||
current directory
|
current directory
|
||||||
|
|
20
man2/ustat.2
20
man2/ustat.2
|
@ -29,7 +29,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH USTAT 2 2003-08-04 "Linux" "Linux Programmer's Manual"
|
.TH USTAT 2 2003-08-04 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
ustat \- get file system statistics
|
ustat \- get filesystem statistics
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.nf
|
.nf
|
||||||
.B #include <sys/types.h>
|
.B #include <sys/types.h>
|
||||||
|
@ -42,10 +42,10 @@ ustat \- get file system statistics
|
||||||
.fi
|
.fi
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR ustat ()
|
.BR ustat ()
|
||||||
returns information about a mounted file system.
|
returns information about a mounted filesystem.
|
||||||
.I dev
|
.I dev
|
||||||
is a device number identifying a device containing
|
is a device number identifying a device containing
|
||||||
a mounted file system.
|
a mounted filesystem.
|
||||||
.I ubuf
|
.I ubuf
|
||||||
is a pointer to a
|
is a pointer to a
|
||||||
.I ustat
|
.I ustat
|
||||||
|
@ -84,10 +84,10 @@ points outside of your accessible address space.
|
||||||
.TP
|
.TP
|
||||||
.B EINVAL
|
.B EINVAL
|
||||||
.I dev
|
.I dev
|
||||||
does not refer to a device containing a mounted file system.
|
does not refer to a device containing a mounted filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ENOSYS
|
.B ENOSYS
|
||||||
The mounted file system referenced by
|
The mounted filesystem referenced by
|
||||||
.I dev
|
.I dev
|
||||||
does not support this operation, or any version of Linux before
|
does not support this operation, or any version of Linux before
|
||||||
1.3.16.
|
1.3.16.
|
||||||
|
@ -108,13 +108,13 @@ structure has an additional field,
|
||||||
.IR f_blksize ,
|
.IR f_blksize ,
|
||||||
that is unknown elsewhere.
|
that is unknown elsewhere.
|
||||||
HP-UX warns:
|
HP-UX warns:
|
||||||
For some file systems, the number of free inodes does not change.
|
For some filesystems, the number of free inodes does not change.
|
||||||
Such file systems will return \-1 in the field
|
Such filesystems will return \-1 in the field
|
||||||
.IR f_tinode .
|
.IR f_tinode .
|
||||||
.\" Some software tries to use this in order to test whether the
|
.\" Some software tries to use this in order to test whether the
|
||||||
.\" underlying file system is NFS.
|
.\" underlying filesystem is NFS.
|
||||||
For some file systems, inodes are dynamically allocated.
|
For some filesystems, inodes are dynamically allocated.
|
||||||
Such file systems will return the current number of free inodes.
|
Such filesystems will return the current number of free inodes.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
.BR stat (2),
|
.BR stat (2),
|
||||||
.BR statfs (2)
|
.BR statfs (2)
|
||||||
|
|
|
@ -158,7 +158,7 @@ capability).
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
.I path
|
.I path
|
||||||
resides on a read-only file system.
|
resides on a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
.BR utime ():
|
.BR utime ():
|
||||||
SVr4, POSIX.1-2001.
|
SVr4, POSIX.1-2001.
|
||||||
|
|
|
@ -109,7 +109,7 @@ struct timespec {
|
||||||
.in
|
.in
|
||||||
.PP
|
.PP
|
||||||
Updated file timestamps are set to the greatest value
|
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
|
If the
|
||||||
.I tv_nsec
|
.I tv_nsec
|
||||||
|
@ -277,7 +277,7 @@ capability); or,
|
||||||
.IP *
|
.IP *
|
||||||
the file is marked immutable (see
|
the file is marked immutable (see
|
||||||
.BR chattr (1)).
|
.BR chattr (1)).
|
||||||
.\" EXT2_IMMUTABLE_FL and similar flags for other file systems.
|
.\" EXT2_IMMUTABLE_FL and similar flags for other filesystems.
|
||||||
.RE
|
.RE
|
||||||
.PD
|
.PD
|
||||||
.TP
|
.TP
|
||||||
|
@ -395,7 +395,7 @@ capability); or,
|
||||||
the file is marked append-only or immutable (see
|
the file is marked append-only or immutable (see
|
||||||
.BR chattr (1)).
|
.BR chattr (1)).
|
||||||
.\" EXT2_IMMUTABLE_FL EXT_APPPEND_FL and similar flags for
|
.\" EXT2_IMMUTABLE_FL EXT_APPPEND_FL and similar flags for
|
||||||
.\" other file systems.
|
.\" other filesystems.
|
||||||
.\"
|
.\"
|
||||||
.\" Why the inconsistency (which is described under NOTES) between
|
.\" Why the inconsistency (which is described under NOTES) between
|
||||||
.\" EACCES and EPERM, where only EPERM tests for append-only.
|
.\" EACCES and EPERM, where only EPERM tests for append-only.
|
||||||
|
@ -404,7 +404,7 @@ the file is marked append-only or immutable (see
|
||||||
.PD
|
.PD
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
The file is on a read-only file system.
|
The file is on a read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ESRCH
|
.B ESRCH
|
||||||
.RB ( utimensat ())
|
.RB ( utimensat ())
|
||||||
|
|
|
@ -85,7 +85,7 @@ POSIX requires that a
|
||||||
which can be proved to occur after a
|
which can be proved to occur after a
|
||||||
.BR write ()
|
.BR write ()
|
||||||
has returned returns the new data.
|
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
|
.SH RETURN VALUE
|
||||||
On success, the number of bytes written is returned (zero indicates
|
On success, the number of bytes written is returned (zero indicates
|
||||||
nothing was written).
|
nothing was written).
|
||||||
|
@ -134,7 +134,7 @@ refers to a datagram socket for which a peer address has not been set using
|
||||||
.BR connect (2).
|
.BR connect (2).
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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
|
referred to by
|
||||||
.I fd
|
.I fd
|
||||||
has been exhausted.
|
has been exhausted.
|
||||||
|
|
|
@ -163,7 +163,7 @@ The minimum page size is 512 bytes and the maximum page size is 64K.
|
||||||
If
|
If
|
||||||
.I psize
|
.I psize
|
||||||
is 0 (no page size is specified) a page size is chosen based on the
|
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
|
.TP
|
||||||
.I compare
|
.I compare
|
||||||
Compare is the key comparison function.
|
Compare is the key comparison function.
|
||||||
|
|
|
@ -433,7 +433,7 @@ Remote I/O error
|
||||||
Interrupted system call should be restarted
|
Interrupted system call should be restarted
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
Read-only file system (POSIX.1)
|
Read-only filesystem (POSIX.1)
|
||||||
.TP
|
.TP
|
||||||
.B ESHUTDOWN
|
.B ESHUTDOWN
|
||||||
Cannot send after transport endpoint shutdown
|
Cannot send after transport endpoint shutdown
|
||||||
|
@ -451,7 +451,7 @@ No such process (POSIX.1)
|
||||||
.B ESTALE
|
.B ESTALE
|
||||||
Stale file handle (POSIX.1)
|
Stale file handle (POSIX.1)
|
||||||
.sp
|
.sp
|
||||||
This error can occur for NFS and for other file systems
|
This error can occur for NFS and for other filesystems
|
||||||
.TP
|
.TP
|
||||||
.B ESTRPIPE
|
.B ESTRPIPE
|
||||||
Streams pipe error
|
Streams pipe error
|
||||||
|
|
|
@ -87,7 +87,7 @@ is NULL.
|
||||||
.B ENOSYS
|
.B ENOSYS
|
||||||
The
|
The
|
||||||
.I /proc
|
.I /proc
|
||||||
file system could not be accessed.
|
filesystem could not be accessed.
|
||||||
.SH VERSIONS
|
.SH VERSIONS
|
||||||
.BR fexecve ()
|
.BR fexecve ()
|
||||||
is implemented since glibc 2.3.2.
|
is implemented since glibc 2.3.2.
|
||||||
|
@ -100,7 +100,7 @@ On Linux,
|
||||||
.BR fexecve ()
|
.BR fexecve ()
|
||||||
is implemented using the
|
is implemented using the
|
||||||
.BR proc (5)
|
.BR proc (5)
|
||||||
file system, so
|
filesystem, so
|
||||||
.I /proc
|
.I /proc
|
||||||
needs to be mounted and available at the time of the call.
|
needs to be mounted and available at the time of the call.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
|
|
|
@ -225,7 +225,7 @@ and its subdirectories.
|
||||||
(By default, each directory is handled \fIbefore\fP its contents.)
|
(By default, each directory is handled \fIbefore\fP its contents.)
|
||||||
.TP
|
.TP
|
||||||
.B FTW_MOUNT
|
.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).
|
(i.e., do not cross mount points).
|
||||||
.TP
|
.TP
|
||||||
.B FTW_PHYS
|
.B FTW_PHYS
|
||||||
|
|
|
@ -76,7 +76,7 @@ is not a valid file descriptor.
|
||||||
.B ENOSYS
|
.B ENOSYS
|
||||||
The
|
The
|
||||||
.I /proc
|
.I /proc
|
||||||
file system could not be accessed.
|
filesystem could not be accessed.
|
||||||
.PP
|
.PP
|
||||||
The following additional error may occur for
|
The following additional error may occur for
|
||||||
.BR lutimes ():
|
.BR lutimes ():
|
||||||
|
|
|
@ -53,7 +53,7 @@ The current
|
||||||
implementation of these functions is rather expensive,
|
implementation of these functions is rather expensive,
|
||||||
since they open and parse files in the
|
since they open and parse files in the
|
||||||
.I /sys
|
.I /sys
|
||||||
file system each time they are called.
|
filesystem each time they are called.
|
||||||
|
|
||||||
The following
|
The following
|
||||||
.BR sysconf (3)
|
.BR sysconf (3)
|
||||||
|
|
|
@ -148,7 +148,7 @@ is set to
|
||||||
(Note that on some systems,
|
(Note that on some systems,
|
||||||
.B PATH_MAX
|
.B PATH_MAX
|
||||||
may not be a compile-time constant;
|
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).)
|
.BR pathconf (3).)
|
||||||
For portability and security reasons, use of
|
For portability and security reasons, use of
|
||||||
.BR getwd ()
|
.BR getwd ()
|
||||||
|
@ -233,7 +233,7 @@ Under Linux, the function
|
||||||
is a system call (since 2.1.92).
|
is a system call (since 2.1.92).
|
||||||
On older systems it would query
|
On older systems it would query
|
||||||
.IR /proc/self/cwd .
|
.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.
|
generic implementation is called.
|
||||||
Only in that case can
|
Only in that case can
|
||||||
these calls fail under Linux with
|
these calls fail under Linux with
|
||||||
|
|
|
@ -26,7 +26,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH GETDIRENTRIES 3 2007-07-26 "GNU" "Linux Programmer's Manual"
|
.TH GETDIRENTRIES 3 2007-07-26 "GNU" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
getdirentries \- get directory entries in a file system-independent format
|
getdirentries \- get directory entries in a filesystem-independent format
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B #include <dirent.h>
|
.B #include <dirent.h>
|
||||||
.sp
|
.sp
|
||||||
|
|
|
@ -32,7 +32,7 @@
|
||||||
.TH GETMNTENT 3 2009-09-15 "" "Linux Programmer's Manual"
|
.TH GETMNTENT 3 2009-09-15 "" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
getmntent, setmntent, addmntent, endmntent, hasmntopt,
|
getmntent, setmntent, addmntent, endmntent, hasmntopt,
|
||||||
getmntent_r \- get file system descriptor file entry
|
getmntent_r \- get filesystem descriptor file entry
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.nf
|
.nf
|
||||||
.B #include <stdio.h>
|
.B #include <stdio.h>
|
||||||
|
@ -63,14 +63,14 @@ Feature Test Macro Requirements for glibc (see
|
||||||
.BR getmntent_r ():
|
.BR getmntent_r ():
|
||||||
_BSD_SOURCE || _SVID_SOURCE
|
_BSD_SOURCE || _SVID_SOURCE
|
||||||
.SH DESCRIPTION
|
.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
|
.I /etc/fstab
|
||||||
and the mounted file system description file
|
and the mounted filesystem description file
|
||||||
.IR /etc/mtab .
|
.IR /etc/mtab .
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.BR setmntent ()
|
.BR setmntent ()
|
||||||
function opens the file system description file
|
function opens the filesystem description file
|
||||||
.I filename
|
.I filename
|
||||||
and returns a file pointer which can be used by
|
and returns a file pointer which can be used by
|
||||||
.BR getmntent ().
|
.BR getmntent ().
|
||||||
|
@ -84,7 +84,7 @@ argument of
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.BR getmntent ()
|
.BR getmntent ()
|
||||||
function reads the next line from the file system
|
function reads the next line from the filesystem
|
||||||
description file
|
description file
|
||||||
.I fp
|
.I fp
|
||||||
and returns a pointer to a structure
|
and returns a pointer to a structure
|
||||||
|
@ -106,7 +106,7 @@ the end of the open file
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.BR endmntent ()
|
.BR endmntent ()
|
||||||
function closes the file system description file
|
function closes the filesystem description file
|
||||||
.IR fp .
|
.IR fp .
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
|
@ -149,8 +149,8 @@ as follows:
|
||||||
.in +4n
|
.in +4n
|
||||||
.nf
|
.nf
|
||||||
struct mntent {
|
struct mntent {
|
||||||
char *mnt_fsname; /* name of mounted file system */
|
char *mnt_fsname; /* name of mounted filesystem */
|
||||||
char *mnt_dir; /* file system path prefix */
|
char *mnt_dir; /* filesystem path prefix */
|
||||||
char *mnt_type; /* mount type (see mntent.h) */
|
char *mnt_type; /* mount type (see mntent.h) */
|
||||||
char *mnt_opts; /* mount options (see mntent.h) */
|
char *mnt_opts; /* mount options (see mntent.h) */
|
||||||
int mnt_freq; /* dump frequency in days */
|
int mnt_freq; /* dump frequency in days */
|
||||||
|
@ -195,8 +195,8 @@ function returns the address of the substring if
|
||||||
a match is found and NULL otherwise.
|
a match is found and NULL otherwise.
|
||||||
.SH FILES
|
.SH FILES
|
||||||
.nf
|
.nf
|
||||||
/etc/fstab file system description file
|
/etc/fstab filesystem description file
|
||||||
/etc/mtab mounted file system description file
|
/etc/mtab mounted filesystem description file
|
||||||
.fi
|
.fi
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
The nonreentrant functions are from SunOS 4.1.3.
|
The nonreentrant functions are from SunOS 4.1.3.
|
||||||
|
|
|
@ -153,7 +153,7 @@ Use alternative functions
|
||||||
.IR pglob\->gl_opendir ,
|
.IR pglob\->gl_opendir ,
|
||||||
.IR pglob\->gl_lstat ", and"
|
.IR pglob\->gl_lstat ", and"
|
||||||
.I pglob\->gl_stat
|
.I pglob\->gl_stat
|
||||||
for file system access instead of the normal library
|
for filesystem access instead of the normal library
|
||||||
functions.
|
functions.
|
||||||
.TP
|
.TP
|
||||||
.B GLOB_BRACE
|
.B GLOB_BRACE
|
||||||
|
|
|
@ -45,7 +45,7 @@ file are \fB(\fP\fImode\fP\fB & ~umask)\fP.
|
||||||
A FIFO special file is similar to a pipe, except that it is created
|
A FIFO special file is similar to a pipe, except that it is created
|
||||||
in a different way.
|
in a different way.
|
||||||
Instead of being an anonymous communications
|
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
|
calling
|
||||||
.BR mkfifo ().
|
.BR mkfifo ().
|
||||||
.PP
|
.PP
|
||||||
|
@ -71,7 +71,7 @@ One of the directories in \fIpathname\fP did not allow search
|
||||||
(execute) permission.
|
(execute) permission.
|
||||||
.TP
|
.TP
|
||||||
.B EDQUOT
|
.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.
|
exhausted.
|
||||||
.TP
|
.TP
|
||||||
.B EEXIST
|
.B EEXIST
|
||||||
|
@ -85,7 +85,7 @@ Either the total length of \fIpathname\fP is greater than
|
||||||
\fBPATH_MAX\fP, or an individual filename component has a length
|
\fBPATH_MAX\fP, or an individual filename component has a length
|
||||||
greater than \fBNAME_MAX\fP.
|
greater than \fBNAME_MAX\fP.
|
||||||
In the GNU system, there is no imposed
|
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.
|
limits on the length of a component.
|
||||||
.TP
|
.TP
|
||||||
.B ENOENT
|
.B ENOENT
|
||||||
|
@ -93,14 +93,14 @@ A directory component in \fIpathname\fP does not exist or is a
|
||||||
dangling symbolic link.
|
dangling symbolic link.
|
||||||
.TP
|
.TP
|
||||||
.B ENOSPC
|
.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
|
.TP
|
||||||
.B ENOTDIR
|
.B ENOTDIR
|
||||||
A component used as a directory in \fIpathname\fP is not, in fact, a
|
A component used as a directory in \fIpathname\fP is not, in fact, a
|
||||||
directory.
|
directory.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
\fIpathname\fP refers to a read-only file system.
|
\fIpathname\fP refers to a read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
POSIX.1-2001.
|
POSIX.1-2001.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
|
|
|
@ -85,7 +85,7 @@ The owner (user ID) of the message queue is set to the effective
|
||||||
user ID of the calling process.
|
user ID of the calling process.
|
||||||
The group ownership (group ID) is set to the effective group ID
|
The group ownership (group ID) is set to the effective group ID
|
||||||
of the calling process.
|
of the calling process.
|
||||||
.\" In reality the file system IDs are used on Linux.
|
.\" In reality the filesystem IDs are used on Linux.
|
||||||
.TP
|
.TP
|
||||||
.B O_EXCL
|
.B O_EXCL
|
||||||
If
|
If
|
||||||
|
|
|
@ -78,7 +78,7 @@ struct dirent {
|
||||||
off_t d_off; /* not an offset; see NOTES */
|
off_t d_off; /* not an offset; see NOTES */
|
||||||
unsigned short d_reclen; /* length of this record */
|
unsigned short d_reclen; /* length of this record */
|
||||||
unsigned char d_type; /* type of file; not supported
|
unsigned char d_type; /* type of file; not supported
|
||||||
by all file system types */
|
by all filesystem types */
|
||||||
char d_name[256]; /* filename */
|
char d_name[256]; /* filename */
|
||||||
};
|
};
|
||||||
.fi
|
.fi
|
||||||
|
@ -179,7 +179,7 @@ is the same as would be returned by calling
|
||||||
at the current position in the directory stream.
|
at the current position in the directory stream.
|
||||||
Be aware that despite its type and name, the
|
Be aware that despite its type and name, the
|
||||||
.I d_off
|
.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/
|
.\" https://lwn.net/Articles/544298/
|
||||||
Applications should treat this field as an opaque value,
|
Applications should treat this field as an opaque value,
|
||||||
making no assumptions about its contents; see also
|
making no assumptions about its contents; see also
|
||||||
|
@ -232,7 +232,7 @@ is returned in
|
||||||
Currently,
|
Currently,
|
||||||
.\" kernel 2.6.27
|
.\" kernel 2.6.27
|
||||||
.\" The same sentence is in getdents.2
|
.\" 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
|
have full support for returning the file type in
|
||||||
.IR d_type .
|
.IR d_type .
|
||||||
All applications must properly handle a return of
|
All applications must properly handle a return of
|
||||||
|
|
|
@ -115,7 +115,7 @@ this error is also returned if
|
||||||
is NULL.)
|
is NULL.)
|
||||||
.TP
|
.TP
|
||||||
.B EIO
|
.B EIO
|
||||||
An I/O error occurred while reading from the file system.
|
An I/O error occurred while reading from the filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ELOOP
|
.B ELOOP
|
||||||
Too many symbolic links were encountered in translating the pathname.
|
Too many symbolic links were encountered in translating the pathname.
|
||||||
|
|
|
@ -143,7 +143,7 @@ This value is the size (in bytes) of the pages used for nodes in that tree.
|
||||||
If
|
If
|
||||||
.I psize
|
.I psize
|
||||||
is 0 (no page size is specified) a page size is chosen based on the
|
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
|
See
|
||||||
.BR btree (3)
|
.BR btree (3)
|
||||||
for more information.
|
for more information.
|
||||||
|
|
|
@ -37,7 +37,7 @@ remove \- remove a file or directory
|
||||||
.BI "int remove(const char *" pathname );
|
.BI "int remove(const char *" pathname );
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.BR remove ()
|
.BR remove ()
|
||||||
deletes a name from the file system.
|
deletes a name from the filesystem.
|
||||||
It calls
|
It calls
|
||||||
.BR unlink (2)
|
.BR unlink (2)
|
||||||
for files, and
|
for files, and
|
||||||
|
|
|
@ -63,7 +63,7 @@ The owner (user ID) of the semaphore is set to the effective
|
||||||
user ID of the calling process.
|
user ID of the calling process.
|
||||||
The group ownership (group ID) is set to the effective group ID
|
The group ownership (group ID) is set to the effective group ID
|
||||||
of the calling process.
|
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
|
If both
|
||||||
.B O_CREAT
|
.B O_CREAT
|
||||||
and
|
and
|
||||||
|
|
|
@ -94,7 +94,7 @@ Open the object for read-write access.
|
||||||
Create the shared memory object if it does not exist.
|
Create the shared memory object if it does not exist.
|
||||||
The user and group ownership of the object are taken
|
The user and group ownership of the object are taken
|
||||||
from the corresponding effective IDs of the calling process,
|
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)
|
.\" are nearly always the same as the effective IDs. (MTK, Jul 05)
|
||||||
and the object's
|
and the object's
|
||||||
permission bits are set according to the low-order 9 bits of
|
permission bits are set according to the low-order 9 bits of
|
||||||
|
@ -265,7 +265,7 @@ On Linux, this will successfully truncate an existing
|
||||||
shared memory object\(emthis may not be so on other UNIX systems.
|
shared memory object\(emthis may not be so on other UNIX systems.
|
||||||
.LP
|
.LP
|
||||||
The POSIX shared memory object implementation on Linux 2.4 makes use
|
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
|
mounted under
|
||||||
.IR /dev/shm .
|
.IR /dev/shm .
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
|
|
|
@ -29,7 +29,7 @@
|
||||||
.\"
|
.\"
|
||||||
.TH STATVFS 3 2003-08-22 "Linux" "Linux Programmer's Manual"
|
.TH STATVFS 3 2003-08-22 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
statvfs, fstatvfs \- get file system statistics
|
statvfs, fstatvfs \- get filesystem statistics
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.B #include <sys/statvfs.h>
|
.B #include <sys/statvfs.h>
|
||||||
.sp
|
.sp
|
||||||
|
@ -39,9 +39,9 @@ statvfs, fstatvfs \- get file system statistics
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
The function
|
The function
|
||||||
.BR statvfs ()
|
.BR statvfs ()
|
||||||
returns information about a mounted file system.
|
returns information about a mounted filesystem.
|
||||||
.I path
|
.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
|
.I buf
|
||||||
is a pointer to a
|
is a pointer to a
|
||||||
.I statvfs
|
.I statvfs
|
||||||
|
@ -50,7 +50,7 @@ structure defined approximately as follows:
|
||||||
.in +4n
|
.in +4n
|
||||||
.nf
|
.nf
|
||||||
struct statvfs {
|
struct statvfs {
|
||||||
unsigned long f_bsize; /* file system block size */
|
unsigned long f_bsize; /* filesystem block size */
|
||||||
unsigned long f_frsize; /* fragment size */
|
unsigned long f_frsize; /* fragment size */
|
||||||
fsblkcnt_t f_blocks; /* size of fs in f_frsize units */
|
fsblkcnt_t f_blocks; /* size of fs in f_frsize units */
|
||||||
fsblkcnt_t f_bfree; /* # free blocks */
|
fsblkcnt_t f_bfree; /* # free blocks */
|
||||||
|
@ -58,7 +58,7 @@ struct statvfs {
|
||||||
fsfilcnt_t f_files; /* # inodes */
|
fsfilcnt_t f_files; /* # inodes */
|
||||||
fsfilcnt_t f_ffree; /* # free inodes */
|
fsfilcnt_t f_ffree; /* # free inodes */
|
||||||
fsfilcnt_t f_favail; /* # free inodes for unprivileged users */
|
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_flag; /* mount flags */
|
||||||
unsigned long f_namemax; /* maximum filename length */
|
unsigned long f_namemax; /* maximum filename length */
|
||||||
};
|
};
|
||||||
|
@ -81,14 +81,14 @@ is a bit mask (of mount flags, see
|
||||||
Bits defined by POSIX are
|
Bits defined by POSIX are
|
||||||
.TP
|
.TP
|
||||||
.B ST_RDONLY
|
.B ST_RDONLY
|
||||||
Read-only file system.
|
Read-only filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ST_NOSUID
|
.B ST_NOSUID
|
||||||
Set-user-ID/set-group-ID bits are ignored by
|
Set-user-ID/set-group-ID bits are ignored by
|
||||||
.BR exec (3).
|
.BR exec (3).
|
||||||
.LP
|
.LP
|
||||||
It is unspecified whether all members of the returned struct
|
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 ()
|
.BR fstatvfs ()
|
||||||
returns the same information about an open file referenced by descriptor
|
returns the same information about an open file referenced by descriptor
|
||||||
|
@ -122,7 +122,7 @@ points to an invalid address.
|
||||||
This call was interrupted by a signal.
|
This call was interrupted by a signal.
|
||||||
.TP
|
.TP
|
||||||
.B EIO
|
.B EIO
|
||||||
An I/O error occurred while reading from the file system.
|
An I/O error occurred while reading from the filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ELOOP
|
.B ELOOP
|
||||||
.RB ( statvfs ())
|
.RB ( statvfs ())
|
||||||
|
@ -144,7 +144,7 @@ does not exist.
|
||||||
Insufficient kernel memory was available.
|
Insufficient kernel memory was available.
|
||||||
.TP
|
.TP
|
||||||
.B ENOSYS
|
.B ENOSYS
|
||||||
The file system does not support this call.
|
The filesystem does not support this call.
|
||||||
.TP
|
.TP
|
||||||
.B ENOTDIR
|
.B ENOTDIR
|
||||||
.RB ( statvfs ())
|
.RB ( statvfs ())
|
||||||
|
|
|
@ -47,7 +47,7 @@ and testing the value of certain macros.
|
||||||
At run time, one can ask for numerical values using the present function
|
At run time, one can ask for numerical values using the present function
|
||||||
.BR sysconf ().
|
.BR sysconf ().
|
||||||
One can ask for numerical values that may depend
|
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)
|
.BR fpathconf (3)
|
||||||
and
|
and
|
||||||
.BR pathconf (3).
|
.BR pathconf (3).
|
||||||
|
|
|
@ -72,12 +72,12 @@ POSIX.1-2001 specifies
|
||||||
.IR long ,
|
.IR long ,
|
||||||
and this is the type used since glibc 2.1.2.
|
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 ()
|
.BR telldir ()
|
||||||
was a simple file offset within a directory.
|
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.
|
to represent directories.
|
||||||
On such file systems, the value returned by
|
On such filesystems, the value returned by
|
||||||
.BR telldir ()
|
.BR telldir ()
|
||||||
(and used internally by
|
(and used internally by
|
||||||
.BR readdir (3))
|
.BR readdir (3))
|
||||||
|
|
|
@ -74,7 +74,7 @@ Too many files open in the system.
|
||||||
There was no room in the directory to add the new filename.
|
There was no room in the directory to add the new filename.
|
||||||
.TP
|
.TP
|
||||||
.B EROFS
|
.B EROFS
|
||||||
Read-only file system.
|
Read-only filesystem.
|
||||||
.SH CONFORMING TO
|
.SH CONFORMING TO
|
||||||
SVr4, 4.3BSD, C89, C99, SUSv2, POSIX.1-2001.
|
SVr4, 4.3BSD, C89, C99, SUSv2, POSIX.1-2001.
|
||||||
.SH NOTES
|
.SH NOTES
|
||||||
|
|
|
@ -227,7 +227,7 @@ tape drives with your Smart Array 5xxx controller.
|
||||||
Additionally, note that the driver will not engage the SCSI core at
|
Additionally, note that the driver will not engage the SCSI core at
|
||||||
init time.
|
init time.
|
||||||
The driver must be directed to dynamically engage the SCSI core via
|
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
|
which the "block" side of the driver creates as
|
||||||
.I /proc/driver/cciss/cciss*
|
.I /proc/driver/cciss/cciss*
|
||||||
at run time.
|
at run time.
|
||||||
|
@ -260,7 +260,7 @@ The
|
||||||
.B cciss
|
.B cciss
|
||||||
driver must be informed that changes to the SCSI bus
|
driver must be informed that changes to the SCSI bus
|
||||||
have been made.
|
have been made.
|
||||||
This may be done via the /proc file system.
|
This may be done via the /proc filesystem.
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
echo "rescan" > /proc/scsi/cciss0/1
|
echo "rescan" > /proc/scsi/cciss0/1
|
||||||
|
@ -281,7 +281,7 @@ lun used to address each device.
|
||||||
The driver then notifies the SCSI midlayer
|
The driver then notifies the SCSI midlayer
|
||||||
of these changes.
|
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
|
contains a number in addition to the driver name
|
||||||
(e.g., "cciss0"
|
(e.g., "cciss0"
|
||||||
instead of just "cciss", which you might expect).
|
instead of just "cciss", which you might expect).
|
||||||
|
|
|
@ -79,13 +79,13 @@ The kernel then can use
|
||||||
contents for a two-phase system boot-up.
|
contents for a two-phase system boot-up.
|
||||||
.PP
|
.PP
|
||||||
In the first boot-up phase, the kernel starts up
|
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
|
.I /dev/initrd
|
||||||
(e.g., RAM disk initialized by the boot loader).
|
(e.g., RAM disk initialized by the boot loader).
|
||||||
In the second phase, additional drivers or other modules
|
In the second phase, additional drivers or other modules
|
||||||
are loaded from the initial root device's contents.
|
are loaded from the initial root device's contents.
|
||||||
After loading the additional modules, a new root file system
|
After loading the additional modules, a new root filesystem
|
||||||
(i.e., the normal root file system) is mounted from a
|
(i.e., the normal root filesystem) is mounted from a
|
||||||
different device.
|
different device.
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
|
@ -109,16 +109,16 @@ and then frees the memory used by
|
||||||
.IP 3.
|
.IP 3.
|
||||||
The kernel then read-write mounts the device
|
The kernel then read-write mounts the device
|
||||||
.I /dev/ram0
|
.I /dev/ram0
|
||||||
as the initial root file system.
|
as the initial root filesystem.
|
||||||
.IP 4.
|
.IP 4.
|
||||||
If the indicated normal root file system is also the initial
|
If the indicated normal root filesystem is also the initial
|
||||||
root file-system (e.g.,
|
root filesystem (e.g.,
|
||||||
.IR /dev/ram0 )
|
.IR /dev/ram0 )
|
||||||
then the kernel skips to the last step for the usual boot sequence.
|
then the kernel skips to the last step for the usual boot sequence.
|
||||||
.IP 5.
|
.IP 5.
|
||||||
If the executable file
|
If the executable file
|
||||||
.IR /linuxrc
|
.IR /linuxrc
|
||||||
is present in the initial root file-system,
|
is present in the initial root filesystem,
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
is executed with UID 0.
|
is executed with UID 0.
|
||||||
(The file
|
(The file
|
||||||
|
@ -132,15 +132,15 @@ If
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
is not executed or when
|
is not executed or when
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
terminates, the normal root file system is mounted.
|
terminates, the normal root filesystem is mounted.
|
||||||
(If
|
(If
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
exits with any file-systems mounted on the initial root
|
exits with any filesystems mounted on the initial root
|
||||||
file-system, then the behavior of the kernel is
|
filesystem, then the behavior of the kernel is
|
||||||
.BR UNSPECIFIED .
|
.BR UNSPECIFIED .
|
||||||
See the NOTES section for the current kernel behavior.)
|
See the NOTES section for the current kernel behavior.)
|
||||||
.IP 7.
|
.IP 7.
|
||||||
If the normal root file system has a directory
|
If the normal root filesystem has a directory
|
||||||
.IR /initrd ,
|
.IR /initrd ,
|
||||||
the device
|
the device
|
||||||
.I /dev/ram0
|
.I /dev/ram0
|
||||||
|
@ -162,7 +162,7 @@ is not unmounted and therefore processes can remain running from
|
||||||
.IR /dev/ram0 .
|
.IR /dev/ram0 .
|
||||||
If directory
|
If directory
|
||||||
.I /initrd
|
.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
|
and any processes remain running from
|
||||||
.IR /dev/ram0
|
.IR /dev/ram0
|
||||||
when
|
when
|
||||||
|
@ -173,7 +173,7 @@ See the NOTES section for the current kernel behavior.)
|
||||||
.IP 8.
|
.IP 8.
|
||||||
The usual boot sequence (e.g., invocation of
|
The usual boot sequence (e.g., invocation of
|
||||||
.IR /sbin/init )
|
.IR /sbin/init )
|
||||||
is performed on the normal root file system.
|
is performed on the normal root filesystem.
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
|
@ -195,7 +195,7 @@ you have to use this command in the
|
||||||
configuration file
|
configuration file
|
||||||
.IR /etc/lilo.config .
|
.IR /etc/lilo.config .
|
||||||
The filename specified with this
|
The filename specified with this
|
||||||
option will typically be a gzipped file-system image.
|
option will typically be a gzipped filesystem image.
|
||||||
.TP
|
.TP
|
||||||
.I noinitrd
|
.I noinitrd
|
||||||
This boot option disables the two-phase boot-up operation.
|
This boot option disables the two-phase boot-up operation.
|
||||||
|
@ -207,13 +207,13 @@ With this option, any contents of
|
||||||
loaded into memory by the boot loader contents are preserved.
|
loaded into memory by the boot loader contents are preserved.
|
||||||
This option permits the contents of
|
This option permits the contents of
|
||||||
.I /dev/initrd
|
.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
|
However, device
|
||||||
.I /dev/initrd
|
.I /dev/initrd
|
||||||
is read-only and can be read only one time after system startup.
|
is read-only and can be read only one time after system startup.
|
||||||
.TP
|
.TP
|
||||||
.BI root= "device-name"
|
.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
|
For
|
||||||
.B LOADLIN
|
.B LOADLIN
|
||||||
this is a command-line option.
|
this is a command-line option.
|
||||||
|
@ -225,26 +225,26 @@ can be used as an option line in the
|
||||||
configuration file
|
configuration file
|
||||||
.IR /etc/lilo.config .
|
.IR /etc/lilo.config .
|
||||||
The device specified by the this option must be a mountable
|
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,
|
By default,
|
||||||
the kernel's settings
|
the kernel's settings
|
||||||
(e.g., set in the kernel file with
|
(e.g., set in the kernel file with
|
||||||
.BR rdev (8)
|
.BR rdev (8)
|
||||||
or compiled into the kernel file),
|
or compiled into the kernel file),
|
||||||
or the boot loader option setting
|
or the boot loader option setting
|
||||||
is used for the normal root file systems.
|
is used for the normal root filesystems.
|
||||||
For an NFS-mounted normal root file system, one has to use the
|
For an NFS-mounted normal root filesystem, one has to use the
|
||||||
.B nfs_root_name
|
.B nfs_root_name
|
||||||
and
|
and
|
||||||
.B nfs_root_addrs
|
.B nfs_root_addrs
|
||||||
boot options to give the NFS settings.
|
boot options to give the NFS settings.
|
||||||
For more information on NFS-mounted root see the kernel documentation file
|
For more information on NFS-mounted root see the kernel documentation file
|
||||||
.BR Documentation/filesystems/nfsroot.txt .
|
.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
|
.BR LILO
|
||||||
and
|
and
|
||||||
.BR LOADLIN
|
.BR LOADLIN
|
||||||
|
@ -268,9 +268,9 @@ and
|
||||||
.IR /proc/sys/kernel/nfs-root-addrs .
|
.IR /proc/sys/kernel/nfs-root-addrs .
|
||||||
For a physical root device, the root device is changed by having
|
For a physical root device, the root device is changed by having
|
||||||
.I /linuxrc
|
.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 .
|
.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
|
.I /linuxrc
|
||||||
write the NFS setting into files
|
write the NFS setting into files
|
||||||
.IR /proc/sys/kernel/nfs-root-name
|
.IR /proc/sys/kernel/nfs-root-name
|
||||||
|
@ -302,14 +302,14 @@ IP number 193.8.232.2 and named "idefix":
|
||||||
.BR Note :
|
.BR Note :
|
||||||
The use of
|
The use of
|
||||||
.I /proc/sys/kernel/real-root-dev
|
.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
|
See the Linux kernel source file
|
||||||
.I Documentation/initrd.txt
|
.I Documentation/initrd.txt
|
||||||
as well as
|
as well as
|
||||||
.BR pivot_root (2)
|
.BR pivot_root (2)
|
||||||
and
|
and
|
||||||
.BR pivot_root (8)
|
.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.
|
.\" FIXME the manual page should describe the pivot_root mechanism.
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
|
@ -325,26 +325,26 @@ The loader program boots from floppy or other media with a minimal kernel
|
||||||
(e.g., support for
|
(e.g., support for
|
||||||
.IR /dev/ram ,
|
.IR /dev/ram ,
|
||||||
.IR /dev/initrd ,
|
.IR /dev/initrd ,
|
||||||
and the ext2 file-system) and loads
|
and the ext2 filesystem) and loads
|
||||||
.IR /dev/initrd
|
.IR /dev/initrd
|
||||||
with a gzipped version of the initial file-system.
|
with a gzipped version of the initial filesystem.
|
||||||
.IP 2.
|
.IP 2.
|
||||||
The executable
|
The executable
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
determines what is needed to (1) mount the normal root file-system
|
determines what is needed to (1) mount the normal root filesystem
|
||||||
(i.e., device type, device drivers, file system) and (2) the
|
(i.e., device type, device drivers, filesystem) and (2) the
|
||||||
distribution media (e.g., CD-ROM, network, tape, ...).
|
distribution media (e.g., CD-ROM, network, tape, ...).
|
||||||
This can be done by asking the user, by auto-probing,
|
This can be done by asking the user, by auto-probing,
|
||||||
or by using a hybrid approach.
|
or by using a hybrid approach.
|
||||||
.IP 3.
|
.IP 3.
|
||||||
The executable
|
The executable
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
loads the necessary modules from the initial root file-system.
|
loads the necessary modules from the initial root filesystem.
|
||||||
.IP 4.
|
.IP 4.
|
||||||
The executable
|
The executable
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
creates and populates the root file system.
|
creates and populates the root filesystem.
|
||||||
(At this stage the normal root file system does not have to be a
|
(At this stage the normal root filesystem does not have to be a
|
||||||
completed system yet.)
|
completed system yet.)
|
||||||
.IP 5.
|
.IP 5.
|
||||||
The executable
|
The executable
|
||||||
|
@ -353,17 +353,17 @@ sets
|
||||||
.IR /proc/sys/kernel/real-root-dev ,
|
.IR /proc/sys/kernel/real-root-dev ,
|
||||||
unmount
|
unmount
|
||||||
.IR /proc ,
|
.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.
|
systems it has mounted, and then terminates.
|
||||||
.IP 6.
|
.IP 6.
|
||||||
The kernel then mounts the normal root file system.
|
The kernel then mounts the normal root filesystem.
|
||||||
.IP 7.
|
.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.
|
the boot loader can be installed.
|
||||||
.IP 8.
|
.IP 8.
|
||||||
The boot loader is configured to load into
|
The boot loader is configured to load into
|
||||||
.I /dev/initrd
|
.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
|
(e.g., Device
|
||||||
.I /dev/ram0
|
.I /dev/ram0
|
||||||
can be modified, then unmounted, and finally, the image is written from
|
can be modified, then unmounted, and finally, the image is written from
|
||||||
|
@ -393,7 +393,7 @@ file or a file executed by
|
||||||
would be different.
|
would be different.
|
||||||
.PP
|
.PP
|
||||||
A third scenario is more convenient recovery disks.
|
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
|
partition is not needed at boot time, the system loaded from
|
||||||
.I /dev/initrd
|
.I /dev/initrd
|
||||||
can use a dialog and/or auto-detection followed by a
|
can use a dialog and/or auto-detection followed by a
|
||||||
|
@ -428,7 +428,7 @@ from the CD-ROM.
|
||||||
.\"
|
.\"
|
||||||
.SH NOTES
|
.SH NOTES
|
||||||
.IP 1. 3
|
.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
|
.I /dev/ram0
|
||||||
is moved from
|
is moved from
|
||||||
.I /
|
.I /
|
||||||
|
@ -447,7 +447,7 @@ will
|
||||||
.B not
|
.B not
|
||||||
be fully unmounted if
|
be fully unmounted if
|
||||||
.I /dev/ram0
|
.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
|
If
|
||||||
.IR /dev/ram0
|
.IR /dev/ram0
|
||||||
is
|
is
|
||||||
|
|
|
@ -63,7 +63,7 @@ and
|
||||||
The Linux support for the above (known as UNIX 98 pseudoterminal naming)
|
The Linux support for the above (known as UNIX 98 pseudoterminal naming)
|
||||||
is done using the
|
is done using the
|
||||||
.I devpts
|
.I devpts
|
||||||
file system, that should be mounted on
|
filesystem, that should be mounted on
|
||||||
.IR /dev/pts .
|
.IR /dev/pts .
|
||||||
.LP
|
.LP
|
||||||
Before this UNIX 98 scheme, master pseudoterminals were called
|
Before this UNIX 98 scheme, master pseudoterminals were called
|
||||||
|
|
|
@ -85,7 +85,7 @@ After
|
||||||
.B sk98lin
|
.B sk98lin
|
||||||
is bound to one or more adapter cards and the
|
is bound to one or more adapter cards and the
|
||||||
.I /proc
|
.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
|
will be created in the folder
|
||||||
.I /proc/net/sk98lin
|
.I /proc/net/sk98lin
|
||||||
for all ports of the installed network adapter cards.
|
for all ports of the installed network adapter cards.
|
||||||
|
|
|
@ -75,7 +75,7 @@ These devices replace the screendump
|
||||||
operations of
|
operations of
|
||||||
.BR console (4),
|
.BR console (4),
|
||||||
so the system
|
so the system
|
||||||
administrator can control access using file system permissions.
|
administrator can control access using filesystem permissions.
|
||||||
.PP
|
.PP
|
||||||
The devices for the first eight virtual consoles may be created by:
|
The devices for the first eight virtual consoles may be created by:
|
||||||
|
|
||||||
|
|
|
@ -63,9 +63,9 @@ A (writable, regular) file with the same name as would be used for the
|
||||||
core dump already exists, but there is more than one hard link to that
|
core dump already exists, but there is more than one hard link to that
|
||||||
file.
|
file.
|
||||||
.IP *
|
.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 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 *
|
.IP *
|
||||||
The directory in which the core dump file is to be created does
|
The directory in which the core dump file is to be created does
|
||||||
not exist.
|
not exist.
|
||||||
|
|
|
@ -26,29 +26,29 @@
|
||||||
.TH FILESYSTEMS 5 2012-08-05 "Linux" "Linux Programmer's Manual"
|
.TH FILESYSTEMS 5 2012-08-05 "Linux" "Linux Programmer's Manual"
|
||||||
.nh
|
.nh
|
||||||
.SH NAME
|
.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,
|
XFS, JFS, xia, msdos,
|
||||||
umsdos, vfat, ntfs, proc, nfs, iso9660, hpfs, sysv, smb, ncpfs
|
umsdos, vfat, ntfs, proc, nfs, iso9660, hpfs, sysv, smb, ncpfs
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
When, as is customary, the
|
When, as is customary, the
|
||||||
.B proc
|
.B proc
|
||||||
file system is mounted on
|
filesystem is mounted on
|
||||||
.IR /proc ,
|
.IR /proc ,
|
||||||
you can find in the file
|
you can find in the file
|
||||||
.I /proc/filesystems
|
.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
|
If you need a currently unsupported one, insert the corresponding
|
||||||
module or recompile the kernel.
|
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
|
.I mount
|
||||||
it; see
|
it; see
|
||||||
.BR mount (8).
|
.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
|
.TP 10
|
||||||
.B "minix"
|
.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.
|
under Linux.
|
||||||
It has a number of shortcomings: a 64MB partition size
|
It has a number of shortcomings: a 64MB partition size
|
||||||
limit, short filenames, a single timestamp, etc.
|
limit, short filenames, a single timestamp, etc.
|
||||||
|
@ -57,24 +57,24 @@ It remains useful for floppies and RAM disks.
|
||||||
.B ext
|
.B ext
|
||||||
is an elaborate extension of the
|
is an elaborate extension of the
|
||||||
.B minix
|
.B minix
|
||||||
file system.
|
filesystem.
|
||||||
It has been completely superseded by the second version
|
It has been completely superseded by the second version
|
||||||
of the extended file system
|
of the extended filesystem
|
||||||
.RB ( ext2 )
|
.RB ( ext2 )
|
||||||
and has been removed from the kernel (in 2.1.21).
|
and has been removed from the kernel (in 2.1.21).
|
||||||
.TP
|
.TP
|
||||||
.B ext2
|
.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.
|
as well as removable media.
|
||||||
The second extended file system was designed as an extension of the
|
The second extended filesystem was designed as an extension of the
|
||||||
extended file system
|
extended filesystem
|
||||||
.RB ( ext ).
|
.RB ( ext ).
|
||||||
.B ext2
|
.B ext2
|
||||||
offers the best performance (in terms of speed and CPU usage) of
|
offers the best performance (in terms of speed and CPU usage) of
|
||||||
the file systems supported under Linux.
|
the filesystems supported under Linux.
|
||||||
.TP
|
.TP
|
||||||
.B ext3
|
.B ext3
|
||||||
is a journaling version of the ext2 file system.
|
is a journaling version of the ext2 filesystem.
|
||||||
It is easy to
|
It is easy to
|
||||||
switch back and forth between ext2 and ext3.
|
switch back and forth between ext2 and ext3.
|
||||||
.TP
|
.TP
|
||||||
|
@ -84,51 +84,51 @@ reliability enhancements,
|
||||||
plus large increases in volume, file, and directory size limits.
|
plus large increases in volume, file, and directory size limits.
|
||||||
.TP
|
.TP
|
||||||
.B Reiserfs
|
.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.
|
that was integrated into Linux in kernel 2.4.1.
|
||||||
.TP
|
.TP
|
||||||
.B XFS
|
.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.
|
that was integrated into Linux in kernel 2.4.20.
|
||||||
.TP
|
.TP
|
||||||
.B JFS
|
.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.
|
that was integrated into Linux in kernel 2.4.24.
|
||||||
.TP
|
.TP
|
||||||
.B xiafs
|
.B xiafs
|
||||||
was designed and implemented to be a stable, safe file system by
|
was designed and implemented to be a stable, safe filesystem by
|
||||||
extending the Minix file system code.
|
extending the Minix filesystem code.
|
||||||
It provides the basic most
|
It provides the basic most
|
||||||
requested features without undue complexity.
|
requested features without undue complexity.
|
||||||
The
|
The
|
||||||
.B xia
|
.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.
|
It was removed from the kernel in 2.1.21.
|
||||||
.TP
|
.TP
|
||||||
.B msdos
|
.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
|
.B msdos
|
||||||
filenames can be no longer than 8 characters, followed by an
|
filenames can be no longer than 8 characters, followed by an
|
||||||
optional period and 3 character extension.
|
optional period and 3 character extension.
|
||||||
.TP
|
.TP
|
||||||
.B umsdos
|
.B umsdos
|
||||||
is an extended DOS file system used by Linux.
|
is an extended DOS filesystem used by Linux.
|
||||||
It adds capability for
|
It adds capability for
|
||||||
long filenames, UID/GID, POSIX permissions, and special files
|
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.
|
sacrificing compatibility with DOS.
|
||||||
.TP
|
.TP
|
||||||
.B vfat
|
.B vfat
|
||||||
is an extended DOS file system used by Microsoft Windows95 and Windows NT.
|
is an extended DOS filesystem used by Microsoft Windows95 and Windows NT.
|
||||||
VFAT adds the capability to use long filenames under the MSDOS file system.
|
VFAT adds the capability to use long filenames under the MSDOS filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B ntfs
|
.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
|
It has reliability, performance, and space-utilization enhancements
|
||||||
plus features like ACLs, journaling, encryption, and so on.
|
plus features like ACLs, journaling, encryption, and so on.
|
||||||
.TP
|
.TP
|
||||||
.B proc
|
.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
|
structures rather than reading and interpreting
|
||||||
.IR /dev/kmem .
|
.IR /dev/kmem .
|
||||||
In particular, its files do not take disk space.
|
In particular, its files do not take disk space.
|
||||||
|
@ -136,42 +136,42 @@ See
|
||||||
.BR proc (5).
|
.BR proc (5).
|
||||||
.TP
|
.TP
|
||||||
.B iso9660
|
.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
|
.RS
|
||||||
.TP
|
.TP
|
||||||
.B "High Sierra"
|
.B "High Sierra"
|
||||||
Linux supports High Sierra, the precursor to the ISO 9660 standard for
|
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
|
It is automatically recognized within the
|
||||||
.B iso9660
|
.B iso9660
|
||||||
file-system support under Linux.
|
filesystem support under Linux.
|
||||||
.TP
|
.TP
|
||||||
.B "Rock Ridge"
|
.B "Rock Ridge"
|
||||||
Linux also supports the System Use Sharing Protocol records specified
|
Linux also supports the System Use Sharing Protocol records specified
|
||||||
by the Rock Ridge Interchange Protocol.
|
by the Rock Ridge Interchange Protocol.
|
||||||
They are used to further describe the files in the
|
They are used to further describe the files in the
|
||||||
.B iso9660
|
.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.
|
filenames, UID/GID, POSIX permissions, and devices.
|
||||||
It is automatically recognized within the
|
It is automatically recognized within the
|
||||||
.B iso9660
|
.B iso9660
|
||||||
file-system support under Linux.
|
filesystem support under Linux.
|
||||||
.RE
|
.RE
|
||||||
.TP
|
.TP
|
||||||
.B hpfs
|
.B hpfs
|
||||||
is the High Performance Filesystem, used in OS/2.
|
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.
|
read-only under Linux due to the lack of available documentation.
|
||||||
.TP
|
.TP
|
||||||
.B sysv
|
.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.
|
It implements all of Xenix FS, SystemV/386 FS, and Coherent FS.
|
||||||
.TP
|
.TP
|
||||||
.B nfs
|
.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
|
.TP
|
||||||
.B smb
|
.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.
|
Windows for Workgroups, Windows NT, and Lan Manager.
|
||||||
.sp
|
.sp
|
||||||
To use
|
To use
|
||||||
|
@ -182,7 +182,7 @@ package, found at
|
||||||
.UE .
|
.UE .
|
||||||
.TP
|
.TP
|
||||||
.B ncpfs
|
.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.
|
Novell NetWare.
|
||||||
.sp
|
.sp
|
||||||
To use
|
To use
|
||||||
|
|
74
man5/proc.5
74
man5/proc.5
|
@ -61,11 +61,11 @@
|
||||||
.\"
|
.\"
|
||||||
.TH PROC 5 2013-08-08 "Linux" "Linux Programmer's Manual"
|
.TH PROC 5 2013-08-08 "Linux" "Linux Programmer's Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
proc \- process information pseudo-file system
|
proc \- process information pseudo-filesystem
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
The
|
The
|
||||||
.I proc
|
.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.
|
kernel data structures.
|
||||||
It is commonly mounted at
|
It is commonly mounted at
|
||||||
.IR /proc .
|
.IR /proc .
|
||||||
|
@ -630,11 +630,11 @@ parent ID: ID of parent mount (or of self for the top of the mount tree).
|
||||||
(3)
|
(3)
|
||||||
major:minor: value of
|
major:minor: value of
|
||||||
.I st_dev
|
.I st_dev
|
||||||
for files on file system (see
|
for files on filesystem (see
|
||||||
.BR stat (2)).
|
.BR stat (2)).
|
||||||
.TP
|
.TP
|
||||||
(4)
|
(4)
|
||||||
root: root of the mount within the file system.
|
root: root of the mount within the filesystem.
|
||||||
.TP
|
.TP
|
||||||
(5)
|
(5)
|
||||||
mount point: mount point relative to the process's root.
|
mount point: mount point relative to the process's root.
|
||||||
|
@ -649,10 +649,10 @@ optional fields: zero or more fields of the form "tag[:value]".
|
||||||
separator: marks the end of the optional fields.
|
separator: marks the end of the optional fields.
|
||||||
.TP
|
.TP
|
||||||
(9)
|
(9)
|
||||||
file system type: name of file system in the form "type[.subtype]".
|
filesystem type: name of filesystem in the form "type[.subtype]".
|
||||||
.TP
|
.TP
|
||||||
(10)
|
(10)
|
||||||
mount source: file system-specific information or "none".
|
mount source: filesystem-specific information or "none".
|
||||||
.TP
|
.TP
|
||||||
(11)
|
(11)
|
||||||
super options: per-super block options.
|
super options: per-super block options.
|
||||||
|
@ -686,13 +686,13 @@ For more information on mount propagation see:
|
||||||
in the Linux kernel source tree.
|
in the Linux kernel source tree.
|
||||||
.TP
|
.TP
|
||||||
.IR /proc/[pid]/mounts " (since Linux 2.4.19)"
|
.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.
|
process's mount namespace.
|
||||||
The format of this file is documented in
|
The format of this file is documented in
|
||||||
.BR fstab (5).
|
.BR fstab (5).
|
||||||
Since kernel version 2.6.15, this file is pollable:
|
Since kernel version 2.6.15, this file is pollable:
|
||||||
after opening the file for reading, a change in this file
|
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)
|
.BR select (2)
|
||||||
to mark the file descriptor as readable, and
|
to mark the file descriptor as readable, and
|
||||||
.BR poll (2)
|
.BR poll (2)
|
||||||
|
@ -718,14 +718,14 @@ The name of the mounted device
|
||||||
(or "nodevice" if there is no corresponding device).
|
(or "nodevice" if there is no corresponding device).
|
||||||
.TP
|
.TP
|
||||||
(2)
|
(2)
|
||||||
The mount point within the file system tree.
|
The mount point within the filesystem tree.
|
||||||
.TP
|
.TP
|
||||||
(3)
|
(3)
|
||||||
The file system type.
|
The filesystem type.
|
||||||
.TP
|
.TP
|
||||||
(4)
|
(4)
|
||||||
Optional statistics and configuration information.
|
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.
|
information via this field.
|
||||||
.RE
|
.RE
|
||||||
.IP
|
.IP
|
||||||
|
@ -928,7 +928,7 @@ will change the other with its scaled value.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/[pid]/root
|
.I /proc/[pid]/root
|
||||||
UNIX and Linux support the idea of a per-process root of the
|
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)
|
.BR chroot (2)
|
||||||
system call.
|
system call.
|
||||||
This file is a symbolic link that points to the process's
|
This file is a symbolic link that points to the process's
|
||||||
|
@ -1347,7 +1347,7 @@ PID of parent process.
|
||||||
PID of process tracing this process (0 if not being traced).
|
PID of process tracing this process (0 if not being traced).
|
||||||
.IP *
|
.IP *
|
||||||
.IR Uid ", " Gid :
|
.IR Uid ", " Gid :
|
||||||
Real, effective, saved set, and file system UIDs (GIDs).
|
Real, effective, saved set, and filesystem UIDs (GIDs).
|
||||||
.IP *
|
.IP *
|
||||||
.IR FDSize :
|
.IR FDSize :
|
||||||
Number of file descriptor slots currently allocated.
|
Number of file descriptor slots currently allocated.
|
||||||
|
@ -1577,20 +1577,20 @@ Frame buffer information when
|
||||||
is defined during kernel compilation.
|
is defined during kernel compilation.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/filesystems
|
.I /proc/filesystems
|
||||||
A text listing of the file systems which are supported by the kernel,
|
A text listing of the filesystems which are supported by the kernel,
|
||||||
namely file systems which were compiled into the kernel or whose kernel
|
namely filesystems which were compiled into the kernel or whose kernel
|
||||||
modules are currently loaded.
|
modules are currently loaded.
|
||||||
(See also
|
(See also
|
||||||
.BR filesystems (5).)
|
.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
|
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
|
Incidentally, this file may be used by
|
||||||
.BR mount (8)
|
.BR mount (8)
|
||||||
when no file system is specified and it didn't manage to determine the
|
when no filesystem is specified and it didn't manage to determine the
|
||||||
file system type.
|
filesystem type.
|
||||||
Then file systems contained in this file are tried
|
Then filesystems contained in this file are tried
|
||||||
(excepted those that are marked with "nodev").
|
(excepted those that are marked with "nodev").
|
||||||
.TP
|
.TP
|
||||||
.I /proc/fs
|
.I /proc/fs
|
||||||
|
@ -1961,7 +1961,7 @@ See also
|
||||||
.TP
|
.TP
|
||||||
.I /proc/mounts
|
.I /proc/mounts
|
||||||
Before kernel 2.4.19, this file was a list
|
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
|
With the introduction of per-process mount namespaces in
|
||||||
Linux 2.4.19, this file became a link to
|
Linux 2.4.19, this file became a link to
|
||||||
.IR /proc/self/mounts ,
|
.IR /proc/self/mounts ,
|
||||||
|
@ -2250,7 +2250,7 @@ root can control bus lockups simulated by the scsi_debug driver.
|
||||||
.I /proc/self
|
.I /proc/self
|
||||||
This directory refers to the process accessing the
|
This directory refers to the process accessing the
|
||||||
.I /proc
|
.I /proc
|
||||||
file system,
|
filesystem,
|
||||||
and is identical to the
|
and is identical to the
|
||||||
.I /proc
|
.I /proc
|
||||||
directory named by the process ID of the same process.
|
directory named by the process ID of the same process.
|
||||||
|
@ -2386,7 +2386,7 @@ See also
|
||||||
This directory (present since 1.3.57) contains a number of files
|
This directory (present since 1.3.57) contains a number of files
|
||||||
and subdirectories corresponding to kernel variables.
|
and subdirectories corresponding to kernel variables.
|
||||||
These variables can be read and sometimes modified using
|
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)
|
.BR sysctl (2)
|
||||||
system call.
|
system call.
|
||||||
.TP
|
.TP
|
||||||
|
@ -2408,7 +2408,7 @@ some systems, it may be empty.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/sys/fs
|
.I /proc/sys/fs
|
||||||
This directory contains the files and subdirectories for kernel variables
|
This directory contains the files and subdirectories for kernel variables
|
||||||
related to file systems.
|
related to filesystems.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/sys/fs/binfmt_misc
|
.I /proc/sys/fs/binfmt_misc
|
||||||
Documentation for files in this directory can be found
|
Documentation for files in this directory can be found
|
||||||
|
@ -2603,9 +2603,9 @@ for details.
|
||||||
These files
|
These files
|
||||||
allow you to change the value of the fixed UID and GID.
|
allow you to change the value of the fixed UID and GID.
|
||||||
The default is 65534.
|
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.
|
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
|
with writes enabled, any UID or GID that would exceed 65535 is translated
|
||||||
to the overflow value before being written to disk.
|
to the overflow value before being written to disk.
|
||||||
.TP
|
.TP
|
||||||
|
@ -2637,11 +2637,11 @@ The caller has the
|
||||||
.BR CAP_FOWNER
|
.BR CAP_FOWNER
|
||||||
capability.
|
capability.
|
||||||
.IP *
|
.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
|
the owner (UID) of the target file
|
||||||
(as described in
|
(as described in
|
||||||
.BR credentials (7),
|
.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 *
|
.IP *
|
||||||
All of the following conditions are true:
|
All of the following conditions are true:
|
||||||
.RS 4
|
.RS 4
|
||||||
|
@ -2682,11 +2682,11 @@ When the value in this file is 1, symbolic links are followed only
|
||||||
in the following circumstances:
|
in the following circumstances:
|
||||||
.RS
|
.RS
|
||||||
.IP * 3
|
.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
|
the owner (UID) of the symbolic link
|
||||||
(as described in
|
(as described in
|
||||||
.BR credentials (7),
|
.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 *
|
.IP *
|
||||||
the link is not in a sticky world-writable directory; or
|
the link is not in a sticky world-writable directory; or
|
||||||
.IP *
|
.IP *
|
||||||
|
@ -2721,7 +2721,7 @@ or whose binary does not have read permission enabled.
|
||||||
.TP
|
.TP
|
||||||
\fI1\ ("debug")\fP
|
\fI1\ ("debug")\fP
|
||||||
All processes dump core when possible.
|
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.
|
and no security is applied.
|
||||||
This is intended for system debugging situations only.
|
This is intended for system debugging situations only.
|
||||||
Ptrace is unchecked.
|
Ptrace is unchecked.
|
||||||
|
@ -2750,17 +2750,17 @@ does not follow these rules, and no core dump will be produced.
|
||||||
.I /proc/sys/fs/super-max
|
.I /proc/sys/fs/super-max
|
||||||
This file
|
This file
|
||||||
controls the maximum number of superblocks, and
|
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.
|
can have.
|
||||||
You need increase only
|
You need increase only
|
||||||
.I super-max
|
.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
|
.I super-max
|
||||||
allows you to.
|
allows you to.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/sys/fs/super-nr
|
.I /proc/sys/fs/super-nr
|
||||||
This file
|
This file
|
||||||
contains the number of file systems currently mounted.
|
contains the number of filesystems currently mounted.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/sys/kernel
|
.I /proc/sys/kernel
|
||||||
This directory contains files controlling a range of kernel parameters,
|
This directory contains files controlling a range of kernel parameters,
|
||||||
|
@ -2775,7 +2775,7 @@ and
|
||||||
.IR frequency .
|
.IR frequency .
|
||||||
If BSD-style process accounting is enabled these values control
|
If BSD-style process accounting is enabled these values control
|
||||||
its behavior.
|
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
|
.I lowwater
|
||||||
percent accounting suspends.
|
percent accounting suspends.
|
||||||
If free space gets above
|
If free space gets above
|
||||||
|
@ -3241,7 +3241,7 @@ manual page for details.
|
||||||
This directory may be empty.
|
This directory may be empty.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/sys/sunrpc
|
.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).
|
(NFS).
|
||||||
On some systems, it is not present.
|
On some systems, it is not present.
|
||||||
.TP
|
.TP
|
||||||
|
@ -3253,7 +3253,7 @@ cache management.
|
||||||
Writing to this file causes the kernel to drop clean caches, dentries, and
|
Writing to this file causes the kernel to drop clean caches, dentries, and
|
||||||
inodes from memory, causing that memory to become free.
|
inodes from memory, causing that memory to become free.
|
||||||
This can be useful for memory management testing and
|
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,
|
Because writing to this file causes the benefits of caching to be lost,
|
||||||
it can degrade overall system performance.
|
it can degrade overall system performance.
|
||||||
|
|
||||||
|
|
|
@ -90,11 +90,11 @@ to the kernel.
|
||||||
When the kernel is loaded, it initializes the devices (via
|
When the kernel is loaded, it initializes the devices (via
|
||||||
their drivers), starts the swapper (it is a "kernel process",
|
their drivers), starts the swapper (it is a "kernel process",
|
||||||
called kswapd in modern Linux kernels), and mounts the root
|
called kswapd in modern Linux kernels), and mounts the root
|
||||||
file system (/).
|
filesystem (/).
|
||||||
|
|
||||||
Some of the parameters that may be passed to the kernel
|
Some of the parameters that may be passed to the kernel
|
||||||
relate to these activities (e.g: You can override the
|
relate to these activities (e.g: You can override the
|
||||||
default root file system).
|
default root filesystem).
|
||||||
For further information
|
For further information
|
||||||
on Linux kernel parameters read
|
on Linux kernel parameters read
|
||||||
.BR bootparam (7).
|
.BR bootparam (7).
|
||||||
|
|
|
@ -178,7 +178,7 @@ to use Linux.
|
||||||
.TP
|
.TP
|
||||||
.B "'root=...'"
|
.B "'root=...'"
|
||||||
This argument tells the kernel what device is to be used as the 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
|
The default of this setting is determined
|
||||||
at compile time, and usually is the value of the root device of the
|
at compile time, and usually is the value of the root device of the
|
||||||
system that the kernel was built on.
|
system that the kernel was built on.
|
||||||
|
@ -205,7 +205,7 @@ gscd, sbpcd, sonycd, bpcd.
|
||||||
(The type nfs specifies a net boot; ram refers to a ram disk.)
|
(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
|
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 '/dev/' part is purely conventional.
|
||||||
|
|
||||||
The more awkward and less portable numeric specification of the above
|
The more awkward and less portable numeric specification of the above
|
||||||
|
@ -224,16 +224,16 @@ filesystem, in fact reverting its format from ext3 to ext2 without the
|
||||||
need to boot the box from alternate media.
|
need to boot the box from alternate media.
|
||||||
.TP
|
.TP
|
||||||
.BR 'ro' " and " 'rw'
|
.BR 'ro' " and " 'rw'
|
||||||
The 'ro' option tells the kernel to mount the root file system
|
The 'ro' option tells the kernel to mount the root filesystem
|
||||||
as 'read-only' so that file system consistency check programs (fsck)
|
as 'read-only' so that filesystem consistency check programs (fsck)
|
||||||
can do their work on a quiescent file system.
|
can do their work on a quiescent filesystem.
|
||||||
No processes can
|
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 /'.
|
as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
|
||||||
(See also
|
(See also
|
||||||
.BR mount (8).)
|
.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.
|
This is the default.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
@ -418,7 +418,7 @@ But while booting (or while constructing boot floppies)
|
||||||
it is often useful to load the floppy contents into a
|
it is often useful to load the floppy contents into a
|
||||||
ramdisk.
|
ramdisk.
|
||||||
One might also have a system in which first
|
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.
|
before the main disk can be accessed.
|
||||||
|
|
||||||
In Linux 1.3.48, ramdisk handling was changed drastically.
|
In Linux 1.3.48, ramdisk handling was changed drastically.
|
||||||
|
@ -465,8 +465,8 @@ and an initial ramdisk; then the kernel converts initrd into
|
||||||
a "normal" ramdisk, which is mounted read-write as root device;
|
a "normal" ramdisk, which is mounted read-write as root device;
|
||||||
then
|
then
|
||||||
.I /linuxrc
|
.I /linuxrc
|
||||||
is executed; afterward the "real" root file system is mounted,
|
is executed; afterward the "real" root filesystem is mounted,
|
||||||
and the initrd file system is moved over to
|
and the initrd filesystem is moved over to
|
||||||
.IR /initrd ;
|
.IR /initrd ;
|
||||||
finally
|
finally
|
||||||
the usual boot sequence (e.g., invocation of
|
the usual boot sequence (e.g., invocation of
|
||||||
|
|
|
@ -110,7 +110,7 @@ Invoke
|
||||||
.RS
|
.RS
|
||||||
.IP * 2
|
.IP * 2
|
||||||
Bypass permission checks on operations that normally
|
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.,
|
the file (e.g.,
|
||||||
.BR chmod (2),
|
.BR chmod (2),
|
||||||
.BR utime (2)),
|
.BR utime (2)),
|
||||||
|
@ -140,7 +140,7 @@ and
|
||||||
Don't clear set-user-ID and set-group-ID permission
|
Don't clear set-user-ID and set-group-ID permission
|
||||||
bits when a file is modified;
|
bits when a file is modified;
|
||||||
set the set-group-ID bit for a file whose GID does not match
|
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
|
.TP
|
||||||
.B CAP_IPC_LOCK
|
.B CAP_IPC_LOCK
|
||||||
.\" FIXME As at Linux 3.2, there are some strange uses of this capability
|
.\" FIXME As at Linux 3.2, there are some strange uses of this capability
|
||||||
|
@ -391,7 +391,7 @@ perform various privileged block-device
|
||||||
.BR ioctl (2)
|
.BR ioctl (2)
|
||||||
operations;
|
operations;
|
||||||
.IP *
|
.IP *
|
||||||
perform various privileged file-system
|
perform various privileged filesystem
|
||||||
.BR ioctl (2)
|
.BR ioctl (2)
|
||||||
operations;
|
operations;
|
||||||
.IP *
|
.IP *
|
||||||
|
@ -523,7 +523,7 @@ perform a range of device-specific operations on other devices.
|
||||||
.PD 0
|
.PD 0
|
||||||
.RS
|
.RS
|
||||||
.IP * 2
|
.IP * 2
|
||||||
Use reserved space on ext2 file systems;
|
Use reserved space on ext2 filesystems;
|
||||||
.IP *
|
.IP *
|
||||||
make
|
make
|
||||||
.BR ioctl (2)
|
.BR ioctl (2)
|
||||||
|
@ -632,7 +632,7 @@ capability in its effective set.
|
||||||
The kernel must provide system calls allowing a thread's capability sets to
|
The kernel must provide system calls allowing a thread's capability sets to
|
||||||
be changed and retrieved.
|
be changed and retrieved.
|
||||||
.IP 3.
|
.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.
|
so that a process gains those capabilities when the file is executed.
|
||||||
.PP
|
.PP
|
||||||
Before kernel 2.6.24, only the first two of these requirements are met;
|
Before kernel 2.6.24, only the first two of these requirements are met;
|
||||||
|
@ -918,7 +918,7 @@ To preserve the traditional semantics for transitions between
|
||||||
0 and nonzero user IDs,
|
0 and nonzero user IDs,
|
||||||
the kernel makes the following changes to a thread's capability
|
the kernel makes the following changes to a thread's capability
|
||||||
sets on changes to the thread's real, effective, saved set,
|
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 setuid (2),
|
||||||
.BR setresuid (2),
|
.BR setresuid (2),
|
||||||
or similar):
|
or similar):
|
||||||
|
@ -935,7 +935,7 @@ then all capabilities are cleared from the effective set.
|
||||||
If the effective user ID is changed from nonzero to 0,
|
If the effective user ID is changed from nonzero to 0,
|
||||||
then the permitted set is copied to the effective set.
|
then the permitted set is copied to the effective set.
|
||||||
.IP 4.
|
.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))
|
.BR setfsuid (2))
|
||||||
then the following capabilities are cleared from the effective set:
|
then the following capabilities are cleared from the effective set:
|
||||||
.BR CAP_CHOWN ,
|
.BR CAP_CHOWN ,
|
||||||
|
@ -949,7 +949,7 @@ then the following capabilities are cleared from the effective set:
|
||||||
and
|
and
|
||||||
.B CAP_MKNOD
|
.B CAP_MKNOD
|
||||||
(since Linux 2.2.30).
|
(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
|
then any of these capabilities that are enabled in the permitted set
|
||||||
are enabled in the effective set.
|
are enabled in the effective set.
|
||||||
.PP
|
.PP
|
||||||
|
@ -1017,7 +1017,7 @@ operation.)
|
||||||
.TP
|
.TP
|
||||||
.B SECBIT_NO_SETUID_FIXUP
|
.B SECBIT_NO_SETUID_FIXUP
|
||||||
Setting this flag stops the kernel from adjusting capability sets when
|
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.
|
zero and nonzero values.
|
||||||
(See the subsection
|
(See the subsection
|
||||||
.IR "Effect of User ID Changes on Capabilities" .)
|
.IR "Effect of User ID Changes on Capabilities" .)
|
||||||
|
|
|
@ -26,7 +26,7 @@
|
||||||
.SH NAME
|
.SH NAME
|
||||||
cpuset \- confine processes to processor and memory node subsets
|
cpuset \- confine processes to processor and memory node subsets
|
||||||
.SH DESCRIPTION
|
.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,
|
to the kernel cpuset mechanism,
|
||||||
which is used to control the processor placement
|
which is used to control the processor placement
|
||||||
and memory placement of processes.
|
and memory placement of processes.
|
||||||
|
@ -39,7 +39,7 @@ If a system supports cpusets, then it will have the entry
|
||||||
.B nodev cpuset
|
.B nodev cpuset
|
||||||
in the file
|
in the file
|
||||||
.IR /proc/filesystems .
|
.IR /proc/filesystems .
|
||||||
By mounting the cpuset file system (see the
|
By mounting the cpuset filesystem (see the
|
||||||
.B EXAMPLE
|
.B EXAMPLE
|
||||||
section below),
|
section below),
|
||||||
the administrator can configure the cpusets on a system
|
the administrator can configure the cpusets on a system
|
||||||
|
@ -62,14 +62,14 @@ just one memory node that contains all the system's main memory,
|
||||||
while NUMA (non-uniform memory access) systems have multiple memory nodes.
|
while NUMA (non-uniform memory access) systems have multiple memory nodes.
|
||||||
.PP
|
.PP
|
||||||
Cpusets are represented as directories in a hierarchical
|
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 )
|
.RI ( /dev/cpuset )
|
||||||
represents the entire system (all online CPUs and memory nodes)
|
represents the entire system (all online CPUs and memory nodes)
|
||||||
and any cpuset that is the child (descendant) of
|
and any cpuset that is the child (descendant) of
|
||||||
another parent cpuset contains a subset of that parent's
|
another parent cpuset contains a subset of that parent's
|
||||||
CPUs and memory nodes.
|
CPUs and memory nodes.
|
||||||
The directories and files representing cpusets have normal
|
The directories and files representing cpusets have normal
|
||||||
file-system permissions.
|
filesystem permissions.
|
||||||
.PP
|
.PP
|
||||||
Every process in the system belongs to exactly one cpuset.
|
Every process in the system belongs to exactly one cpuset.
|
||||||
A process is confined to run only on the CPUs in
|
A process is confined to run only on the CPUs in
|
||||||
|
@ -305,7 +305,7 @@ See the
|
||||||
.IR cpuset.memory_spread_page " (since Linux 2.6.17)"
|
.IR cpuset.memory_spread_page " (since Linux 2.6.17)"
|
||||||
Flag (0 or 1).
|
Flag (0 or 1).
|
||||||
If set (1), pages in the kernel page cache
|
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,
|
By default this is off (0) in the top cpuset,
|
||||||
and inherited from the parent cpuset in
|
and inherited from the parent cpuset in
|
||||||
newly created cpusets.
|
newly created cpusets.
|
||||||
|
@ -362,7 +362,7 @@ In addition to the above pseudo-files in each directory below
|
||||||
each process has a pseudo-file,
|
each process has a pseudo-file,
|
||||||
.IR /proc/<pid>/cpuset ,
|
.IR /proc/<pid>/cpuset ,
|
||||||
that displays the path of the process's cpuset directory
|
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 ==================
|
.\" ================== proc status ==================
|
||||||
.PP
|
.PP
|
||||||
Also the
|
Also the
|
||||||
|
@ -446,7 +446,7 @@ All cpusets, whether
|
||||||
or not, restrict allocations of memory for user space.
|
or not, restrict allocations of memory for user space.
|
||||||
.PP
|
.PP
|
||||||
This enables configuring a system so that several independent
|
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.
|
while isolating each job's user allocation in its own cpuset.
|
||||||
To do this, construct a large
|
To do this, construct a large
|
||||||
.I hardwall
|
.I hardwall
|
||||||
|
@ -471,7 +471,7 @@ and the last child cpuset of that cpuset is removed,
|
||||||
the kernel will run the command
|
the kernel will run the command
|
||||||
.IR /sbin/cpuset_release_agent ,
|
.IR /sbin/cpuset_release_agent ,
|
||||||
supplying the pathname (relative to the mount point of the
|
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.
|
This enables automatic removal of abandoned cpusets.
|
||||||
.PP
|
.PP
|
||||||
The default value of
|
The default value of
|
||||||
|
@ -565,9 +565,9 @@ kernel direct reclaim code.
|
||||||
The kernel direct reclaim code is entered whenever a process has to
|
The kernel direct reclaim code is entered whenever a process has to
|
||||||
satisfy a memory page request by first finding some other page to
|
satisfy a memory page request by first finding some other page to
|
||||||
repurpose, due to lack of any readily available already free pages.
|
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.
|
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
|
by simply dropping them, though if that page is needed again, it
|
||||||
will have to be reread from disk.
|
will have to be reread from disk.
|
||||||
.PP
|
.PP
|
||||||
|
@ -580,7 +580,7 @@ times 1000.
|
||||||
.\" ================== Memory Spread ==================
|
.\" ================== Memory Spread ==================
|
||||||
.SS Memory spread
|
.SS Memory spread
|
||||||
There are two Boolean flag files per cpuset that control where the
|
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.
|
in-kernel data structures.
|
||||||
They are called
|
They are called
|
||||||
.I cpuset.memory_spread_page
|
.I cpuset.memory_spread_page
|
||||||
|
@ -590,14 +590,14 @@ and
|
||||||
If the per-cpuset Boolean flag file
|
If the per-cpuset Boolean flag file
|
||||||
.I cpuset.memory_spread_page
|
.I cpuset.memory_spread_page
|
||||||
is set, then
|
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
|
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.
|
of preferring to put those pages on the node where the process is running.
|
||||||
.PP
|
.PP
|
||||||
If the per-cpuset Boolean flag file
|
If the per-cpuset Boolean flag file
|
||||||
.I cpuset.memory_spread_slab
|
.I cpuset.memory_spread_slab
|
||||||
is set,
|
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
|
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
|
that the faulting process is allowed to use, instead of preferring to
|
||||||
put those pages on the node where the process is running.
|
put those pages on the node where the process is running.
|
||||||
|
@ -652,7 +652,7 @@ need to place thread-local data on
|
||||||
memory nodes close to the CPUs which are running the threads that most
|
memory nodes close to the CPUs which are running the threads that most
|
||||||
frequently access that data; but also
|
frequently access that data; but also
|
||||||
.IP b)
|
.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.
|
across the several nodes in the job's cpuset in order to fit.
|
||||||
.PP
|
.PP
|
||||||
Without this policy,
|
Without this policy,
|
||||||
|
@ -946,7 +946,7 @@ its memory nodes may not overlap any sibling.
|
||||||
.\" ================== PERMISSIONS ==================
|
.\" ================== PERMISSIONS ==================
|
||||||
.SH PERMISSIONS
|
.SH PERMISSIONS
|
||||||
The permissions of a cpuset are determined by the 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
|
normally mounted at
|
||||||
.IR /dev/cpuset .
|
.IR /dev/cpuset .
|
||||||
.PP
|
.PP
|
||||||
|
@ -978,7 +978,7 @@ or
|
||||||
file.
|
file.
|
||||||
.PP
|
.PP
|
||||||
There is one minor difference between the manner in which these
|
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.
|
operation permissions are evaluated.
|
||||||
The kernel interprets
|
The kernel interprets
|
||||||
relative pathnames starting at a process's current working directory.
|
relative pathnames starting at a process's current working directory.
|
||||||
|
@ -996,20 +996,20 @@ to its cpuset directory beneath
|
||||||
.IR /dev/cpuset ,
|
.IR /dev/cpuset ,
|
||||||
which is a bit unusual)
|
which is a bit unusual)
|
||||||
or if some user code converts the relative cpuset path to a
|
or if some user code converts the relative cpuset path to a
|
||||||
full file-system path.
|
full filesystem path.
|
||||||
.PP
|
.PP
|
||||||
In theory, this means that user code should specify cpusets
|
In theory, this means that user code should specify cpusets
|
||||||
using absolute pathnames, which requires knowing the mount point of
|
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 ).
|
.IR /dev/cpuset ).
|
||||||
In practice, all user level code that this author is aware of
|
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
|
it is mounted at
|
||||||
.IR /dev/cpuset .
|
.IR /dev/cpuset .
|
||||||
Furthermore, it is common practice for carefully written
|
Furthermore, it is common practice for carefully written
|
||||||
user code to verify the presence of the pseudo-file
|
user code to verify the presence of the pseudo-file
|
||||||
.I /dev/cpuset/tasks
|
.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.
|
is currently mounted.
|
||||||
.\" ================== WARNINGS ==================
|
.\" ================== WARNINGS ==================
|
||||||
.SH WARNINGS
|
.SH WARNINGS
|
||||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue