mirror of https://github.com/mkerrisk/man-pages
s/filesystem/file system/
This commit is contained in:
parent
bed47b47a7
commit
24d01c530c
|
@ -234,8 +234,8 @@ and it may be better to use
|
|||
.SS "Disks and Filesystems"
|
||||
The command
|
||||
.I mount
|
||||
will attach the filesystem found on some disk (or floppy, or CDROM or so)
|
||||
to the big filesystem hierarchy. And
|
||||
will attach the file system found on some disk (or floppy, or CDROM or so)
|
||||
to the big file system hierarchy. And
|
||||
.I umount
|
||||
detaches it again.
|
||||
The command
|
||||
|
|
|
@ -126,7 +126,7 @@ A component used as a directory in
|
|||
is not, in fact, a directory.
|
||||
.TP
|
||||
.B EROFS
|
||||
Write permission was requested for a file on a read-only filesystem.
|
||||
Write permission was requested for a file on a read-only file system.
|
||||
.PP
|
||||
.BR access ()
|
||||
may fail if:
|
||||
|
|
|
@ -134,11 +134,11 @@ used in programs intended to be portable.
|
|||
.SH NOTES
|
||||
These system calls are gone;
|
||||
they existed only in Linux 2.5.36 through to 2.5.54.
|
||||
Now the hugetlbfs filesystem can be used instead.
|
||||
Now the hugetlbfs file system can be used instead.
|
||||
Memory backed by huge pages (if the CPU supports them) is obtained by
|
||||
using
|
||||
.BR mmap (2)
|
||||
to map files in this virtual filesystem.
|
||||
to map files in this virtual file system.
|
||||
.LP
|
||||
The maximal number of huge pages can be specified using the
|
||||
.B hugepages=
|
||||
|
|
|
@ -100,7 +100,7 @@ and with disk quota.
|
|||
.PP
|
||||
A successful close does not guarantee that the data has been successfully
|
||||
saved to disk, as the kernel defers writes.
|
||||
It is not common for a filesystem
|
||||
It is not common for a file system
|
||||
to flush the buffers when the stream is closed.
|
||||
If you need to be sure that
|
||||
the data is physically stored use
|
||||
|
|
|
@ -432,7 +432,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.
|
||||
|
||||
The result of mounting a filesystem
|
||||
The result of mounting a file system
|
||||
.I nosuid
|
||||
varies across Linux kernel versions:
|
||||
some will refuse execution of set-user-ID and set-group-ID
|
||||
|
|
|
@ -60,7 +60,7 @@ of the extended attribute identified by
|
|||
.I name
|
||||
and associated with the given
|
||||
.I path
|
||||
in the filesystem.
|
||||
in the file system.
|
||||
The length of the attribute
|
||||
.I value
|
||||
is returned.
|
||||
|
@ -121,7 +121,7 @@ buffer is too small to hold the result,
|
|||
is set to
|
||||
.BR ERANGE .
|
||||
.PP
|
||||
If extended attributes are not supported by the filesystem, or are disabled,
|
||||
If extended attributes are not supported by the file system, or are disabled,
|
||||
.I errno
|
||||
is set to
|
||||
.BR ENOTSUP .
|
||||
|
|
12
man2/link.2
12
man2/link.2
|
@ -111,20 +111,20 @@ is not, in fact, a directory.
|
|||
is a directory.
|
||||
.TP
|
||||
.B EPERM
|
||||
The filesystem containing
|
||||
The file system containing
|
||||
.IR oldpath " and " newpath
|
||||
does not support the creation of hard links.
|
||||
.TP
|
||||
.B EROFS
|
||||
The file is on a read-only filesystem.
|
||||
The file is on a read-only file system.
|
||||
.TP
|
||||
.B EXDEV
|
||||
.IR oldpath " and " newpath
|
||||
are not on the same mounted filesystem.
|
||||
(Linux permits a filesystem to be mounted at multiple points, but
|
||||
are not on the same mounted file system.
|
||||
(Linux permits a file system to be mounted at multiple points, but
|
||||
.BR link ()
|
||||
does not work across different mount points,
|
||||
even if the same filesystem is mounted on both.)
|
||||
even if the same file system is mounted on both.)
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.3BSD, POSIX.1-2001 (except as noted above).
|
||||
.\" SVr4 documents additional ENOLINK and
|
||||
|
@ -133,7 +133,7 @@ SVr4, 4.3BSD, POSIX.1-2001 (except as noted above).
|
|||
.SH NOTES
|
||||
Hard links, as created by
|
||||
.BR link (),
|
||||
cannot span filesystems.
|
||||
cannot span file systems.
|
||||
Use
|
||||
.BR symlink (2)
|
||||
if this is required.
|
||||
|
|
|
@ -55,7 +55,7 @@ retrieves the
|
|||
.I list
|
||||
of extended attribute names associated with the given
|
||||
.I path
|
||||
in the filesystem.
|
||||
in the file system.
|
||||
The list is the set of (null-terminated) names, one after the other.
|
||||
Names of extended attributes to which the calling process does not
|
||||
have access may be omitted from the list.
|
||||
|
@ -133,7 +133,7 @@ buffer is too small to hold the result,
|
|||
is set to
|
||||
.BR ERANGE .
|
||||
.PP
|
||||
If extended attributes are not supported by the filesystem, or are disabled,
|
||||
If extended attributes are not supported by the file system, or are disabled,
|
||||
.I errno
|
||||
is set to
|
||||
.BR ENOTSUP .
|
||||
|
|
|
@ -106,7 +106,7 @@ is not one of
|
|||
or the resulting file offset would be negative,
|
||||
or beyond the end of a seekable device.
|
||||
.\" Some systems may allow negative offsets for character devices
|
||||
.\" and/or for remote filesystems.
|
||||
.\" and/or for remote file systems.
|
||||
.TP
|
||||
.B EOVERFLOW
|
||||
.\" HP-UX 11 says EINVAL for this case (but POSIX.1 says EOVERFLOW)
|
||||
|
|
|
@ -97,7 +97,7 @@ Free up a given range of pages
|
|||
and its associated backing store.
|
||||
Currently,
|
||||
.\" 2.6.18-rc5
|
||||
only shmfs/tmpfs supports this; other filesystems return with the
|
||||
only shmfs/tmpfs supports this; other file systems return with the
|
||||
error
|
||||
.BR ENOSYS .
|
||||
.\" Databases want to use this feature to drop a section of their
|
||||
|
|
|
@ -35,7 +35,7 @@ For Linux, see below.
|
|||
The newly created directory will be owned by the effective user ID of the
|
||||
process.
|
||||
If the directory containing the file has the set-group-ID
|
||||
bit set, or if the filesystem is mounted with BSD group semantics, the
|
||||
bit set, or if the file system is mounted with BSD group semantics, the
|
||||
new directory will inherit the group ownership from its parent;
|
||||
otherwise it will be owned by the effective group ID of the process.
|
||||
|
||||
|
@ -96,13 +96,13 @@ A component used as a directory in
|
|||
is not, in fact, a directory.
|
||||
.TP
|
||||
.B EPERM
|
||||
The filesystem containing
|
||||
The file system containing
|
||||
.I pathname
|
||||
does not support the creation of directories.
|
||||
.TP
|
||||
.B EROFS
|
||||
.I pathname
|
||||
refers to a file on a read-only filesystem.
|
||||
refers to a file on a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, BSD, POSIX.1-2001.
|
||||
.\" SVr4 documents additional EIO, EMULTIHOP
|
||||
|
|
|
@ -33,7 +33,7 @@ _BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE\ >=\ 500
|
|||
.SH DESCRIPTION
|
||||
The system call
|
||||
.BR mknod ()
|
||||
creates a filesystem node (file, device special file or
|
||||
creates a file system node (file, device special file or
|
||||
named pipe) named
|
||||
.IR pathname ,
|
||||
with attributes specified by
|
||||
|
@ -85,7 +85,7 @@ error.
|
|||
The newly created node will be owned by the effective user ID of the
|
||||
process.
|
||||
If the directory containing the node has the set-group-ID
|
||||
bit set, or if the filesystem is mounted with BSD group semantics, the
|
||||
bit set, or if the file system is mounted with BSD group semantics, the
|
||||
new node will inherit the group ownership from its parent directory;
|
||||
otherwise it will be owned by the effective group ID of the process.
|
||||
.SH "RETURN VALUE"
|
||||
|
@ -150,13 +150,13 @@ capability);
|
|||
.\" For Unix domain sockets and regular files, EPERM is only returned in
|
||||
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
|
||||
.\" use mknod() to make these files.
|
||||
also returned if the filesystem containing
|
||||
also returned if the file system containing
|
||||
.I pathname
|
||||
does not support the type of node requested.
|
||||
.TP
|
||||
.B EROFS
|
||||
.I pathname
|
||||
refers to a file on a read-only filesystem.
|
||||
refers to a file on a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.4BSD, POSIX.1-2001 (but see below).
|
||||
.\" The Linux version differs from the SVr4 version in that it
|
||||
|
|
|
@ -398,7 +398,7 @@ The system limit on the total number of open files has been reached.
|
|||
.\" A file could not be mapped for reading.
|
||||
.TP
|
||||
.B ENODEV
|
||||
The underlying filesystem of the specified file does not support
|
||||
The underlying file system of the specified file does not support
|
||||
memory mapping.
|
||||
.TP
|
||||
.B ENOMEM
|
||||
|
@ -410,7 +410,7 @@ The
|
|||
.I prot
|
||||
argument asks for
|
||||
.B PROT_EXEC
|
||||
but the mapped area belongs to a file on a filesystem that
|
||||
but the mapped area belongs to a file on a file system that
|
||||
was mounted no-exec.
|
||||
.\" (Since 2.4.25 / 2.6.0.)
|
||||
.TP
|
||||
|
|
10
man2/mount.2
10
man2/mount.2
|
@ -37,7 +37,7 @@
|
|||
.\"
|
||||
.TH MOUNT 2 2007-12-17 "Linux" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
mount, umount, umount2 \- mount and unmount filesystems
|
||||
mount, umount, umount2 \- mount and unmount file systems
|
||||
.SH SYNOPSIS
|
||||
.nf
|
||||
.B "#include <sys/mount.h>"
|
||||
|
@ -52,7 +52,7 @@ mount, umount, umount2 \- mount and unmount filesystems
|
|||
.fi
|
||||
.SH DESCRIPTION
|
||||
.BR mount ()
|
||||
attaches the filesystem specified by
|
||||
attaches the file system specified by
|
||||
.I source
|
||||
(which is often a device name, but can also be a directory name
|
||||
or a dummy) to the directory specified by
|
||||
|
@ -61,14 +61,14 @@ or a dummy) to the directory specified by
|
|||
.BR umount ()
|
||||
and
|
||||
.BR umount2 ()
|
||||
remove the attachment of the (topmost) filesystem mounted on
|
||||
remove the attachment of the (topmost) file system mounted on
|
||||
.IR target .
|
||||
|
||||
Appropriate privilege (Linux: the
|
||||
.B CAP_SYS_ADMIN
|
||||
capability) is required to mount and unmount filesystems.
|
||||
capability) is required to mount and unmount file systems.
|
||||
|
||||
Since Linux 2.4 a single filesystem can be visible at
|
||||
Since Linux 2.4 a single file system can be visible at
|
||||
multiple mount points, and multiple mounts can be stacked
|
||||
on the same mount point.
|
||||
.\" Multiple mounts on same mount point: since 2.3.99pre7.
|
||||
|
|
22
man2/open.2
22
man2/open.2
|
@ -184,12 +184,12 @@ The owner (user ID) of the file is set to the effective user ID
|
|||
of the process.
|
||||
The group ownership (group ID) is set either to
|
||||
the effective group ID of the process or to the group ID of the
|
||||
parent directory (depending on filesystem type and mount options,
|
||||
parent directory (depending on file system type and mount options,
|
||||
and the mode of the parent directory, see, for example, the mount options
|
||||
.I bsdgroups
|
||||
and
|
||||
.I sysvgroups
|
||||
of the ext2 filesystem, as described in
|
||||
of the ext2 file system, as described in
|
||||
.BR mount (8)).
|
||||
.RS
|
||||
.PP
|
||||
|
@ -355,7 +355,7 @@ when the file is
|
|||
.BR read (2).
|
||||
This flag is intended for use by indexing or backup programs,
|
||||
where its use can significantly reduce the amount of disk activity.
|
||||
This flag may not be effective on all filesystems.
|
||||
This flag may not be effective on all file systems.
|
||||
One example is NFS, where the server maintains the access time.
|
||||
.\" The O_NOATIME flag also affects the treatment of st_atime
|
||||
.\" by mmap() and readdir(2), MTK, Dec 04.
|
||||
|
@ -537,7 +537,7 @@ did not match the owner of the file and the caller was not privileged
|
|||
.TP
|
||||
.B EROFS
|
||||
.I pathname
|
||||
refers to a file on a read-only filesystem and write access was
|
||||
refers to a file on a read-only file system and write access was
|
||||
requested.
|
||||
.TP
|
||||
.B ETXTBSY
|
||||
|
@ -642,12 +642,12 @@ The
|
|||
flag may impose alignment restrictions on the length and address
|
||||
of userspace buffers and the file offset of I/Os.
|
||||
In Linux alignment
|
||||
restrictions vary by filesystem and kernel version and might be
|
||||
restrictions vary by file system and kernel version and might be
|
||||
absent entirely.
|
||||
However there is currently no filesystem\-independent
|
||||
However there is currently no file system\-independent
|
||||
interface for an application to discover these restrictions for a given
|
||||
file or filesystem.
|
||||
Some filesystems provide their own interfaces
|
||||
file or file system.
|
||||
Some file systems provide their own interfaces
|
||||
for doing so, for example the
|
||||
.B XFS_IOC_DIOINFO
|
||||
operation in
|
||||
|
@ -672,7 +672,7 @@ a flag of the same name, but without alignment restrictions.
|
|||
.B O_DIRECT
|
||||
support was added under Linux in kernel version 2.4.10.
|
||||
Older Linux kernels simply ignore this flag.
|
||||
Some filesystems may not implement the flag and
|
||||
Some file systems may not implement the flag and
|
||||
.BR open ()
|
||||
will fail with
|
||||
.B EINVAL
|
||||
|
@ -682,7 +682,7 @@ Applications should avoid mixing
|
|||
.B O_DIRECT
|
||||
and normal I/O to the same file,
|
||||
and especially to overlapping byte regions in the same file.
|
||||
Even when the filesystem correctly handles the coherency issues in
|
||||
Even when the file system correctly handles the coherency issues in
|
||||
this situation, overall I/O throughput is likely to be slower than
|
||||
using either mode alone.
|
||||
Likewise, applications should avoid mixing
|
||||
|
@ -691,7 +691,7 @@ of files with direct I/O to the same files.
|
|||
.LP
|
||||
The behaviour of
|
||||
.B O_DIRECT
|
||||
with NFS will differ from local filesystems.
|
||||
with NFS will differ from local file systems.
|
||||
Older kernels, or
|
||||
kernels configured in certain ways, may not support this combination.
|
||||
The NFS protocol does not support passing the flag to the server, so
|
||||
|
|
|
@ -135,7 +135,7 @@ Enable quota.
|
|||
The
|
||||
.I addr
|
||||
argument is the pathname of the file containing
|
||||
the quota for the filesystem.
|
||||
the quota for the file system.
|
||||
.TP
|
||||
.B Q_QUOTAOFF
|
||||
Disable quota.
|
||||
|
@ -161,7 +161,7 @@ is as before.
|
|||
Set usage.
|
||||
.TP
|
||||
.B Q_SYNC
|
||||
Sync disk copy of a filesystem's quota.
|
||||
Sync disk copy of a file system's quota.
|
||||
.TP
|
||||
.B Q_GETSTATS
|
||||
Get collected stats.
|
||||
|
|
|
@ -153,7 +153,7 @@ UNIX semantics can be obtained by disabling client
|
|||
side attribute caching, but in most situations this will substantially
|
||||
increase server load and decrease performance.
|
||||
.PP
|
||||
Many filesystems and disks were considered to be fast enough that the
|
||||
Many file systems and disks were considered to be fast enough that the
|
||||
implementation of
|
||||
.B O_NONBLOCK
|
||||
was deemed unnecessary.
|
||||
|
|
|
@ -54,7 +54,7 @@ removes the extended attribute identified by
|
|||
.I name
|
||||
and associated with the given
|
||||
.I path
|
||||
in the filesystem.
|
||||
in the file system.
|
||||
.PP
|
||||
.BR lremovexattr ()
|
||||
is identical to
|
||||
|
@ -88,7 +88,7 @@ If the named attribute does not exist,
|
|||
is set to
|
||||
.BR ENOATTR .
|
||||
.PP
|
||||
If extended attributes are not supported by the filesystem, or are disabled,
|
||||
If extended attributes are not supported by the file system, or are disabled,
|
||||
.I errno
|
||||
is set to
|
||||
.BR ENOTSUP .
|
||||
|
|
|
@ -204,24 +204,24 @@ and the process is not privileged
|
|||
(Linux: does not have the
|
||||
.B CAP_FOWNER
|
||||
capability);
|
||||
or the filesystem containing
|
||||
or the file system containing
|
||||
.I pathname
|
||||
does not support renaming of the type requested.
|
||||
.TP
|
||||
.B EROFS
|
||||
The file is on a read-only filesystem.
|
||||
The file is on a read-only file system.
|
||||
.TP
|
||||
.B EXDEV
|
||||
.IR oldpath " and " newpath
|
||||
are not on the same mounted filesystem.
|
||||
(Linux permits a filesystem to be mounted at multiple points, but
|
||||
are not on the same mounted file system.
|
||||
(Linux permits a file system to be mounted at multiple points, but
|
||||
.BR rename ()
|
||||
does not work across different mount points,
|
||||
even if the same filesystem is mounted on both.)
|
||||
even if the same file system is mounted on both.)
|
||||
.SH "CONFORMING TO"
|
||||
4.3BSD, C89, C99, POSIX.1-2001.
|
||||
.SH BUGS
|
||||
On NFS filesystems, you can not assume that if the operation
|
||||
On NFS file systems, you can not assume that if the operation
|
||||
failed the file was not renamed.
|
||||
If the server does the rename operation
|
||||
and then crashes, the retransmitted RPC which will be processed when the
|
||||
|
|
|
@ -114,13 +114,13 @@ and the process is not privileged (Linux: does not have the
|
|||
capability).
|
||||
.TP
|
||||
.B EPERM
|
||||
The filesystem containing
|
||||
The file system containing
|
||||
.I pathname
|
||||
does not support the removal of directories.
|
||||
.TP
|
||||
.B EROFS
|
||||
.I pathname
|
||||
refers to a file on a read-only filesystem.
|
||||
refers to a file on a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.3BSD, POSIX.1-2001.
|
||||
.SH BUGS
|
||||
|
|
|
@ -94,11 +94,11 @@ sets all of the real, saved, and effective user IDs.
|
|||
.\" SVr4 documents an additional EINVAL error condition.
|
||||
.SH NOTES
|
||||
.SS Linux Notes
|
||||
Linux has the concept of filesystem user ID, normally equal to the
|
||||
Linux has the concept of file system user ID, normally equal to the
|
||||
effective user ID.
|
||||
The
|
||||
.BR setuid ()
|
||||
call also sets the filesystem user ID of the calling process.
|
||||
call also sets the file system user ID of the calling process.
|
||||
See
|
||||
.BR setfsuid (2).
|
||||
.PP
|
||||
|
|
|
@ -60,7 +60,7 @@ of the extended attribute identified by
|
|||
.I name
|
||||
and associated with the given
|
||||
.I path
|
||||
in the filesystem.
|
||||
in the file system.
|
||||
The
|
||||
.I size
|
||||
of the
|
||||
|
@ -131,7 +131,7 @@ or
|
|||
.B EDQUOT
|
||||
if quota enforcement was the cause.
|
||||
.PP
|
||||
If extended attributes are not supported by the filesystem, or are disabled,
|
||||
If extended attributes are not supported by the file system, or are disabled,
|
||||
.I errno
|
||||
is set to
|
||||
.BR ENOTSUP .
|
||||
|
|
|
@ -107,7 +107,7 @@ struct stat {
|
|||
gid_t st_gid; /* group ID of owner */
|
||||
dev_t st_rdev; /* device ID (if special file) */
|
||||
off_t st_size; /* total size, in bytes */
|
||||
blksize_t st_blksize; /* blocksize for filesystem I/O */
|
||||
blksize_t st_blksize; /* blocksize for file system I/O */
|
||||
blkcnt_t st_blocks; /* number of blocks allocated */
|
||||
time_t st_atime; /* time of last access */
|
||||
time_t st_mtime; /* time of last modification */
|
||||
|
@ -144,7 +144,7 @@ field gives the "preferred" blocksize for efficient file system I/O.
|
|||
(Writing to a file in smaller chunks may cause
|
||||
an inefficient read-modify-rewrite.)
|
||||
.PP
|
||||
Not all of the Linux filesystems implement all of the time fields.
|
||||
Not all of the Linux file systems implement all of the time fields.
|
||||
Some file system types allow mounting in such a way that file
|
||||
accesses do not cause an update of the
|
||||
.I st_atime
|
||||
|
|
|
@ -37,7 +37,7 @@ The function
|
|||
.BR statfs ()
|
||||
returns information about a mounted file system.
|
||||
.I path
|
||||
is the pathname of any file within the mounted filesystem.
|
||||
is the pathname of any file within the mounted file system.
|
||||
.I buf
|
||||
is a pointer to a
|
||||
.I statfs
|
||||
|
@ -46,7 +46,7 @@ structure defined approximately as follows:
|
|||
.in +4n
|
||||
.nf
|
||||
struct statfs {
|
||||
long f_type; /* type of filesystem (see below) */
|
||||
long f_type; /* type of file system (see below) */
|
||||
long f_bsize; /* optimal transfer block size */
|
||||
long f_blocks; /* total data blocks in file system */
|
||||
long f_bfree; /* free blocks in fs */
|
||||
|
@ -236,11 +236,11 @@ contains some random stuff such that the pair
|
|||
.RI ( f_fsid , ino )
|
||||
uniquely determines a file.
|
||||
Some OSes use (a variation on) the device number, or the device number
|
||||
combined with the filesystem type.
|
||||
combined with the file-system type.
|
||||
Several OSes restrict giving out the
|
||||
.I f_fsid
|
||||
field to the superuser only (and zero it for unprivileged users),
|
||||
because this field is used in the filehandle of the filesystem
|
||||
because this field is used in the filehandle of the file system
|
||||
when NFS-exported, and giving it out is a security concern.
|
||||
.LP
|
||||
Under some OSes the
|
||||
|
|
|
@ -39,7 +39,7 @@ The function
|
|||
.BR statvfs ()
|
||||
returns information about a mounted file system.
|
||||
.I path
|
||||
is the pathname of any file within the mounted filesystem.
|
||||
is the pathname of any file within the mounted file system.
|
||||
.I buf
|
||||
is a pointer to a
|
||||
.I statvfs
|
||||
|
@ -86,7 +86,7 @@ Set-user-ID/set-group-ID bits are ignored by
|
|||
.BR exec (3).
|
||||
.LP
|
||||
It is unspecified whether all members of the returned struct
|
||||
have meaningful values on all filesystems.
|
||||
have meaningful values on all file systems.
|
||||
|
||||
.BR fstatvfs ()
|
||||
returns the same information about an open file referenced by descriptor
|
||||
|
|
|
@ -118,7 +118,7 @@ exists, but refers neither to a regular file nor to a block device;
|
|||
or, for
|
||||
.BR swapon (),
|
||||
the indicated path does not contain a valid swap signature or
|
||||
resides on an in-memory filesystem like tmpfs; or, for
|
||||
resides on an in-memory file system like tmpfs; or, for
|
||||
.BR swapoff (),
|
||||
.I path
|
||||
is not currently a swap area.
|
||||
|
|
|
@ -131,13 +131,13 @@ A component used as a directory in
|
|||
is not, in fact, a directory.
|
||||
.TP
|
||||
.B EPERM
|
||||
The filesystem containing
|
||||
The file system containing
|
||||
.I newpath
|
||||
does not support the creation of symbolic links.
|
||||
.TP
|
||||
.B EROFS
|
||||
.I newpath
|
||||
is on a read-only filesystem.
|
||||
is on a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.3BSD, POSIX.1-2001.
|
||||
.\" SVr4 documents additional error codes EDQUOT and ENOSYS.
|
||||
|
|
|
@ -92,7 +92,7 @@ SVr4.
|
|||
.SH NOTES
|
||||
On Linux with the
|
||||
.I proc
|
||||
filesystem mounted on
|
||||
file system mounted on
|
||||
.IR /proc ,
|
||||
the same information can be derived from
|
||||
.IR /proc/filesystems .
|
||||
|
|
|
@ -38,7 +38,7 @@ unlink \- delete a name and possibly the file it refers to
|
|||
.BI "int unlink(const char *" pathname );
|
||||
.SH DESCRIPTION
|
||||
.BR unlink ()
|
||||
deletes a name from the filesystem.
|
||||
deletes a name from the file system.
|
||||
If that name was the
|
||||
last link to a file and no processes have the file open the file is
|
||||
deleted and the space it was using is made available for reuse.
|
||||
|
@ -119,7 +119,7 @@ as noted above, Linux returns
|
|||
for this case.)
|
||||
.TP
|
||||
.BR EPERM " (Linux only)"
|
||||
The filesystem does not allow unlinking of files.
|
||||
The file system does not allow unlinking of files.
|
||||
.TP
|
||||
.BR EPERM " or " EACCES
|
||||
The directory containing
|
||||
|
@ -134,7 +134,7 @@ capability).
|
|||
.TP
|
||||
.B EROFS
|
||||
.I pathname
|
||||
refers to a file on a read-only filesystem.
|
||||
refers to a file on a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.3BSD, POSIX.1-2001.
|
||||
.\" SVr4 documents additional error
|
||||
|
|
|
@ -108,7 +108,7 @@ For some file systems, the number of free inodes does not change.
|
|||
Such file systems will return \-1 in the field
|
||||
.IR f_tinode .
|
||||
.\" Some software tries to use this in order to test whether the
|
||||
.\" underlying filesystem is NFS.
|
||||
.\" underlying file system is NFS.
|
||||
For some file systems, inodes are dynamically allocated.
|
||||
Such file systems will return the current number of free inodes.
|
||||
.SH "SEE ALSO"
|
||||
|
|
|
@ -118,7 +118,7 @@ does only return the first
|
|||
bytes of the actual pathname.
|
||||
Note that
|
||||
.B PATH_MAX
|
||||
need not be a compile-time constant; it may depend on the filesystem
|
||||
need not be a compile-time constant; it may depend on the file system
|
||||
and may even be unlimited.
|
||||
For portability and security reasons, use of
|
||||
.BR getwd ()
|
||||
|
|
|
@ -26,7 +26,7 @@
|
|||
.\"
|
||||
.TH GETDIRENTRIES 3 2007-07-26 "GNU" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
getdirentries \- get directory entries in a filesystem independent format
|
||||
getdirentries \- get directory entries in a file system-independent format
|
||||
.SH SYNOPSIS
|
||||
.B #include <dirent.h>
|
||||
.sp
|
||||
|
|
|
@ -47,7 +47,7 @@ The \fIstruct fstab\fP is defined by:
|
|||
struct fstab {
|
||||
char *fs_spec; /* block device name */
|
||||
char *fs_file; /* mount point */
|
||||
char *fs_vfstype; /* filesystem type */
|
||||
char *fs_vfstype; /* file-sysem type */
|
||||
char *fs_mntops; /* mount options */
|
||||
const char *fs_type; /* rw/rq/ro/sw/xx option */
|
||||
int fs_freq; /* dump frequency, in days */
|
||||
|
|
|
@ -86,14 +86,14 @@ A directory component in \fIpathname\fP does not exist or is a
|
|||
dangling symbolic link.
|
||||
.TP
|
||||
.B ENOSPC
|
||||
The directory or filesystem has no room for the new file.
|
||||
The directory or file system has no room for the new file.
|
||||
.TP
|
||||
.B ENOTDIR
|
||||
A component used as a directory in \fIpathname\fP is not, in fact, a
|
||||
directory.
|
||||
.TP
|
||||
.B EROFS
|
||||
\fIpathname\fP refers to a read-only filesystem.
|
||||
\fIpathname\fP refers to a read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
POSIX.1-2001.
|
||||
.SH "SEE ALSO"
|
||||
|
|
|
@ -37,7 +37,7 @@ remove \- delete a name and possibly the file it refers to
|
|||
.BI "int remove(const char *" pathname );
|
||||
.SH DESCRIPTION
|
||||
.BR remove ()
|
||||
deletes a name from the filesystem.
|
||||
deletes a name from the file system.
|
||||
It calls
|
||||
.BR unlink (2)
|
||||
for files, and
|
||||
|
|
|
@ -45,7 +45,7 @@ and testing the value of certain macros.
|
|||
At run time, one can ask for numerical values using the present function
|
||||
.BR sysconf ().
|
||||
On can ask for numerical values that may depend
|
||||
on the filesystem a file is in using the calls
|
||||
on the file system a file is in using the calls
|
||||
.BR fpathconf (3)
|
||||
and
|
||||
.BR pathconf (3).
|
||||
|
|
|
@ -70,7 +70,7 @@ Too many files open in the system.
|
|||
There was no room in the directory to add the new filename.
|
||||
.TP
|
||||
.B EROFS
|
||||
Read-only filesystem.
|
||||
Read-only file system.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, 4.3BSD, C89, C99, SUSv2, POSIX.1-2001.
|
||||
.SH NOTES
|
||||
|
|
|
@ -56,7 +56,7 @@ and
|
|||
The Linux support for the above (known as Unix98 pty naming)
|
||||
is done using the
|
||||
.I devpts
|
||||
filesystem, that should be mounted on
|
||||
file system, that should be mounted on
|
||||
.IR /dev/pts .
|
||||
.LP
|
||||
Before this Unix98 scheme, master ptys were called
|
||||
|
|
|
@ -80,7 +80,7 @@ After
|
|||
.B sk98lin
|
||||
is bound to one or more adapter cards and the
|
||||
.I /proc
|
||||
filesystem is mounted on your system, a dedicated statistics file
|
||||
file system is mounted on your system, a dedicated statistics file
|
||||
will be created in folder
|
||||
.I /proc/net/sk98lin
|
||||
for all ports of the installed network adapter cards.
|
||||
|
|
|
@ -25,29 +25,29 @@
|
|||
.TH FILESYSTEMS 5 2007-12-14 "Linux" "Linux Programmer's Manual"
|
||||
.nh
|
||||
.SH NAME
|
||||
filesystems \- Linux filesystem types: minix, ext, ext2, ext3, Reiserfs,
|
||||
filesystems \- Linux file-system types: minix, ext, ext2, ext3, Reiserfs,
|
||||
XFS, JFS, xia, msdos,
|
||||
umsdos, vfat, proc, nfs, iso9660, hpfs, sysv, smb, ncpfs
|
||||
.SH DESCRIPTION
|
||||
When, as is customary, the
|
||||
.B proc
|
||||
filesystem is mounted on
|
||||
file system is mounted on
|
||||
.IR /proc ,
|
||||
you can find in the file
|
||||
.I /proc/filesystems
|
||||
which filesystems your kernel currently supports.
|
||||
which file systems your kernel currently supports.
|
||||
If you need a currently unsupported one, insert the corresponding
|
||||
module or recompile the kernel.
|
||||
|
||||
In order to use a filesystem, you have to
|
||||
In order to use a file system, you have to
|
||||
.I mount
|
||||
it; see
|
||||
.BR mount (8).
|
||||
|
||||
Below a short description of a few of the available filesystems.
|
||||
Below a short description of a few of the available file systems.
|
||||
.TP 10
|
||||
.B "minix"
|
||||
is the filesystem used in the Minix operating system, the first to run
|
||||
is the file system used in the Minix operating system, the first to run
|
||||
under Linux.
|
||||
It has a number of shortcomings: a 64MB partition size
|
||||
limit, short filenames, a single timestamp, etc.
|
||||
|
@ -56,24 +56,24 @@ It remains useful for floppies and RAM disks.
|
|||
.B ext
|
||||
is an elaborate extension of the
|
||||
.B minix
|
||||
filesystem.
|
||||
file system.
|
||||
It has been completely superseded by the second version
|
||||
of the extended filesystem
|
||||
of the extended file system
|
||||
.RB ( ext2 )
|
||||
and has been removed from the kernel (in 2.1.21).
|
||||
.TP
|
||||
.B ext2
|
||||
is the high performance disk filesystem used by Linux for fixed disks
|
||||
is the high performance disk file system used by Linux for fixed disks
|
||||
as well as removable media.
|
||||
The second extended filesystem was designed as an extension of the
|
||||
The second extended file system was designed as an extension of the
|
||||
extended file system
|
||||
.RB ( ext ).
|
||||
.B ext2
|
||||
offers the best performance (in terms of speed and CPU usage) of
|
||||
the filesystems supported under Linux.
|
||||
the file systems supported under Linux.
|
||||
.TP
|
||||
.B ext3
|
||||
is a journaling version of the ext2 filesystem.
|
||||
is a journaling version of the ext2 file system.
|
||||
It is easy to
|
||||
switch back and forth between ext2 and ext3.
|
||||
.TP
|
||||
|
@ -90,34 +90,34 @@ is a journaling file system, developed by IBM,
|
|||
that was integrated into Linux in kernel 2.4.24.
|
||||
.TP
|
||||
.B xiafs
|
||||
was designed and implemented to be a stable, safe filesystem by
|
||||
extending the Minix filesystem code.
|
||||
was designed and implemented to be a stable, safe file system by
|
||||
extending the Minix file system code.
|
||||
It provides the basic most
|
||||
requested features without undue complexity.
|
||||
The
|
||||
.B xia
|
||||
filesystem is no longer actively developed or maintained.
|
||||
file system is no longer actively developed or maintained.
|
||||
It was removed from the kernel in 2.1.21.
|
||||
.TP
|
||||
.B msdos
|
||||
is the filesystem used by DOS, Windows, and some OS/2 computers.
|
||||
is the file system used by DOS, Windows, and some OS/2 computers.
|
||||
.B msdos
|
||||
filenames can be no longer than 8 characters, followed by an
|
||||
optional period and 3 character extension.
|
||||
.TP
|
||||
.B umsdos
|
||||
is an extended DOS filesystem used by Linux.
|
||||
is an extended DOS file system used by Linux.
|
||||
It adds capability for
|
||||
long filenames, UID/GID, POSIX permissions, and special files
|
||||
(devices, named pipes, etc.) under the DOS filesystem, without
|
||||
(devices, named pipes, etc.) under the DOS file system, without
|
||||
sacrificing compatibility with DOS.
|
||||
.TP
|
||||
.B vfat
|
||||
is an extended DOS filesystem used by Microsoft Windows95 and Windows NT.
|
||||
VFAT adds the capability to use long filenames under the MSDOS filesystem.
|
||||
is an extended DOS file system used by Microsoft Windows95 and Windows NT.
|
||||
VFAT adds the capability to use long filenames under the MSDOS file system.
|
||||
.TP
|
||||
.B proc
|
||||
is a pseudo-filesystem which is used as an interface to kernel data
|
||||
is a pseudo file system which is used as an interface to kernel data
|
||||
structures rather than reading and interpreting
|
||||
.IR /dev/kmem .
|
||||
In particular, its files do not take disk space.
|
||||
|
@ -125,42 +125,42 @@ See
|
|||
.BR proc (5).
|
||||
.TP
|
||||
.B iso9660
|
||||
is a CD-ROM filesystem type conforming to the ISO 9660 standard.
|
||||
is a CD-ROM file system type conforming to the ISO 9660 standard.
|
||||
.RS
|
||||
.TP
|
||||
.B "High Sierra"
|
||||
Linux supports High Sierra, the precursor to the ISO 9660 standard for
|
||||
CD-ROM filesystems.
|
||||
CD-ROM file systems.
|
||||
It is automatically recognized within the
|
||||
.B iso9660
|
||||
filesystem support under Linux.
|
||||
file-system support under Linux.
|
||||
.TP
|
||||
.B "Rock Ridge"
|
||||
Linux also supports the System Use Sharing Protocol records specified
|
||||
by the Rock Ridge Interchange Protocol.
|
||||
They are used to further describe the files in the
|
||||
.B iso9660
|
||||
filesystem to a UNIX host, and provide information such as long
|
||||
file system to a UNIX host, and provide information such as long
|
||||
filenames, UID/GID, POSIX permissions, and devices.
|
||||
It is automatically recognized within the
|
||||
.B iso9660
|
||||
filesystem support under Linux.
|
||||
file-system support under Linux.
|
||||
.RE
|
||||
.TP
|
||||
.B hpfs
|
||||
is the High Performance Filesystem, used in OS/2.
|
||||
This filesystem is
|
||||
This file system is
|
||||
read-only under Linux due to the lack of available documentation.
|
||||
.TP
|
||||
.B sysv
|
||||
is an implementation of the SystemV/Coherent filesystem for Linux.
|
||||
is an implementation of the SystemV/Coherent file system for Linux.
|
||||
It implements all of Xenix FS, SystemV/386 FS, and Coherent FS.
|
||||
.TP
|
||||
.B nfs
|
||||
is the network filesystem used to access disks located on remote computers.
|
||||
is the network file system used to access disks located on remote computers.
|
||||
.TP
|
||||
.B smb
|
||||
is a network filesystem that supports the SMB protocol, used by
|
||||
is a network file system that supports the SMB protocol, used by
|
||||
Windows for Workgroups, Windows NT, and Lan Manager.
|
||||
.sp
|
||||
To use
|
||||
|
@ -170,7 +170,7 @@ package, found at
|
|||
.IR ftp://sunsite.unc.edu/pub/Linux/system/Filesystems/smbfs .
|
||||
.TP
|
||||
.B ncpfs
|
||||
is a network filesystem that supports the NCP protocol, used by
|
||||
is a network file system that supports the NCP protocol, used by
|
||||
Novell NetWare.
|
||||
.sp
|
||||
To use
|
||||
|
|
34
man5/proc.5
34
man5/proc.5
|
@ -59,11 +59,11 @@
|
|||
.\"
|
||||
.TH PROC 5 2007-11-30 "Linux" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
proc \- process information pseudo-filesystem
|
||||
proc \- process information pseudo-file system
|
||||
.SH DESCRIPTION
|
||||
The
|
||||
.I proc
|
||||
filesystem is a pseudo-filesystem which is used as an interface to
|
||||
file system is a pseudo-file system which is used as an interface to
|
||||
kernel data structures.
|
||||
It is commonly mounted at
|
||||
.IR /proc .
|
||||
|
@ -268,7 +268,7 @@ and
|
|||
.TP
|
||||
.I /proc/[number]/root
|
||||
Unix and Linux support the idea of a per-process root of the
|
||||
filesystem, set by the
|
||||
file system, set by the
|
||||
.BR chroot (2)
|
||||
system call.
|
||||
This file is a symbolic link that points to the process's
|
||||
|
@ -634,19 +634,19 @@ Frame buffer information when
|
|||
is defined during kernel compilation.
|
||||
.TP
|
||||
.I /proc/filesystems
|
||||
A text listing of the filesystems which are supported by the kernel,
|
||||
namely filesystems which were compiled into the kernel or whose kernel
|
||||
A text listing of the file systems which are supported by the kernel,
|
||||
namely file systems which were compiled into the kernel or whose kernel
|
||||
modules are currently loaded. (See also
|
||||
.BR filesystems (5).)
|
||||
If a filesystem is marked with "nodev",
|
||||
If a file system is marked with "nodev",
|
||||
this means that it does not require a block device to be mounted
|
||||
(e.g., virtual filesystem, network filesystem).
|
||||
(e.g., virtual file system, network file system).
|
||||
|
||||
Incidentally, this file may be used by
|
||||
.BR mount (8)
|
||||
when no filesystem is specified and it didn't manage to determine the
|
||||
filesystem type.
|
||||
Then filesystems contained in this file are tried
|
||||
when no file system is specified and it didn't manage to determine the
|
||||
file system type.
|
||||
Then file systems contained in this file are tried
|
||||
(excepted those that are marked with "nodev").
|
||||
.TP
|
||||
.I /proc/fs
|
||||
|
@ -1043,7 +1043,7 @@ With the \fIlockup\fP and \fIunlock\fP commands,
|
|||
root can control bus lockups simulated by the scsi_debug driver.
|
||||
.TP
|
||||
.I /proc/self
|
||||
This directory refers to the process accessing the /proc filesystem,
|
||||
This directory refers to the process accessing the /proc file system,
|
||||
and is identical to the /proc directory named by the process ID of the
|
||||
same process.
|
||||
.TP
|
||||
|
@ -1335,9 +1335,9 @@ for details.
|
|||
These files
|
||||
allow you to change the value of the fixed UID and GID.
|
||||
The default is 65534.
|
||||
Some filesystems only support 16-bit UIDs and GIDs, although in Linux
|
||||
Some file systems only support 16-bit UIDs and GIDs, although in Linux
|
||||
UIDs and GIDs are 32 bits.
|
||||
When one of these filesystems is mounted
|
||||
When one of these file systems is mounted
|
||||
with writes enabled, any UID or GID that would exceed 65535 is translated
|
||||
to the overflow value before being written to disk.
|
||||
.TP
|
||||
|
@ -1375,15 +1375,15 @@ attempting to debug problems in a normal environment.
|
|||
.I /proc/sys/fs/super-max
|
||||
This file
|
||||
controls the maximum number of superblocks, and
|
||||
thus the maximum number of mounted filesystems the kernel
|
||||
thus the maximum number of mounted file systems the kernel
|
||||
can have.
|
||||
You only need to increase super-max if you need to
|
||||
mount more filesystems than the current value in super-max
|
||||
mount more file systems than the current value in super-max
|
||||
allows you to.
|
||||
.TP
|
||||
.I /proc/sys/fs/super-nr
|
||||
This file
|
||||
contains the number of filesystems currently mounted.
|
||||
contains the number of file systems currently mounted.
|
||||
.TP
|
||||
.I /proc/sys/kernel
|
||||
This directory contains files
|
||||
|
@ -1408,7 +1408,7 @@ This file
|
|||
contains three numbers: highwater, lowwater and frequency.
|
||||
If BSD-style process accounting is enabled these values control
|
||||
its behavior.
|
||||
If free space on filesystem where the log lives
|
||||
If free space on file system where the log lives
|
||||
goes below lowwater percent accounting suspends.
|
||||
If free space gets
|
||||
above highwater percent accounting resumes.
|
||||
|
|
|
@ -168,7 +168,7 @@ to use Linux.
|
|||
.TP
|
||||
.B "'root=...'"
|
||||
This argument tells the kernel what device is to be used as the root
|
||||
filesystem while booting.
|
||||
file system while booting.
|
||||
The default of this setting is determined
|
||||
at compile time, and usually is the value of the root device of the
|
||||
system that the kernel was built on.
|
||||
|
@ -203,16 +203,16 @@ possible root devices in major/minor format is also accepted.
|
|||
alternative.)
|
||||
.TP
|
||||
.BR 'ro' " and " 'rw'
|
||||
The 'ro' option tells the kernel to mount the root filesystem
|
||||
as 'readonly' so that filesystem consistency check programs (fsck)
|
||||
The 'ro' option tells the kernel to mount the root file system
|
||||
as 'readonly' so that file system consistency check programs (fsck)
|
||||
can do their work on a quiescent file system.
|
||||
No processes can
|
||||
write to files on the filesystem in question until it is 'remounted'
|
||||
write to files on the file system in question until it is 'remounted'
|
||||
as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
|
||||
(See also
|
||||
.BR mount (8).)
|
||||
|
||||
The 'rw' option tells the kernel to mount the root filesystem read/write.
|
||||
The 'rw' option tells the kernel to mount the root file system read/write.
|
||||
This is the default.
|
||||
|
||||
The choice between read-only and read/write can also be set using
|
||||
|
@ -369,7 +369,7 @@ But while booting (or while constructing boot floppies)
|
|||
it is often useful to load the floppy contents into a
|
||||
ramdisk.
|
||||
One might also have a system in which first
|
||||
some modules (for filesystem or hardware) must be loaded
|
||||
some modules (for file system or hardware) must be loaded
|
||||
before the main disk can be accessed.
|
||||
|
||||
In Linux 1.3.48, ramdisk handling was changed drastically.
|
||||
|
@ -416,7 +416,7 @@ When this feature is enabled, the boot process will load the kernel
|
|||
and an initial ramdisk; then the kernel converts initrd into
|
||||
a "normal" ramdisk, which is mounted read-write as root device;
|
||||
then /linuxrc is executed; afterwards the "real" root file system is mounted,
|
||||
and the initrd filesystem is moved over to /initrd; finally
|
||||
and the initrd file system is moved over to /initrd; finally
|
||||
the usual boot sequence (e.g., invocation of /sbin/init) is performed.
|
||||
|
||||
For a detailed description of the initrd feature, see
|
||||
|
|
10
man7/hier.7
10
man7/hier.7
|
@ -91,18 +91,18 @@ depends on local administration decisions.
|
|||
.TP
|
||||
.I /lib
|
||||
This directory should hold those shared libraries that are necessary
|
||||
to boot the system and to run the commands in the root filesystem.
|
||||
to boot the system and to run the commands in the root file system.
|
||||
.TP
|
||||
.I /media
|
||||
This directory contains mount points for removable media such as CD
|
||||
and DVD disks or USB sticks.
|
||||
.TP
|
||||
.I /mnt
|
||||
This directory is a mount point for a temporarily mounted filesystem.
|
||||
This directory is a mount point for a temporarily mounted file system.
|
||||
In some distributions,
|
||||
.I /mnt
|
||||
contains subdirectories intended to be used as mount points for several
|
||||
temporary filesystems.
|
||||
temporary file systems.
|
||||
.TP
|
||||
.I /opt
|
||||
This directory should contain add-on packages that contain static files.
|
||||
|
@ -110,7 +110,7 @@ This directory should contain add-on packages that contain static files.
|
|||
.I /proc
|
||||
This is a mount point for the
|
||||
.I proc
|
||||
filesystem, which provides information about running processes and
|
||||
file system, which provides information about running processes and
|
||||
the kernel.
|
||||
This pseudo-file system is described in more detail in
|
||||
.BR proc (5).
|
||||
|
@ -413,7 +413,7 @@ device lock files is
|
|||
.I LCK..<device>
|
||||
where
|
||||
.I <device>
|
||||
is the device's name in the filesystem.
|
||||
is the device's name in the file system.
|
||||
The format used is that of HDU UUCP lock files, that is, lock files
|
||||
contain a PID as a 10-byte ASCII decimal number, followed by a newline
|
||||
character.
|
||||
|
|
|
@ -123,17 +123,17 @@ respectively.
|
|||
|
||||
The path resolution process will assume that these entries have
|
||||
their conventional meanings, regardless of whether they are
|
||||
actually present in the physical filesystem.
|
||||
actually present in the physical file system.
|
||||
|
||||
One cannot walk down past the root: "/.." is the same as "/".
|
||||
.SS "Mount points"
|
||||
After a "mount dev path" command, the pathname "path" refers to
|
||||
the root of the filesystem hierarchy on the device "dev", and no
|
||||
the root of the file system hierarchy on the device "dev", and no
|
||||
longer to whatever it referred to earlier.
|
||||
|
||||
One can walk out of a mounted filesystem: "path/.." refers to
|
||||
One can walk out of a mounted file system: "path/.." refers to
|
||||
the parent directory of "path",
|
||||
outside of the filesystem hierarchy on "dev".
|
||||
outside of the file system hierarchy on "dev".
|
||||
.SS "Trailing slashes"
|
||||
If a pathname ends in a '/', that forces resolution of the preceding
|
||||
component as in Step 2: it has to exist and resolve to a directory.
|
||||
|
@ -198,7 +198,7 @@ Similarly, Linux uses the fsgid ("file system group ID")
|
|||
instead of the effective group ID.
|
||||
See
|
||||
.BR setfsgid (2).
|
||||
.\" FIXME say something about filesystem mounted read-only ?
|
||||
.\" FIXME say something about file system mounted read-only ?
|
||||
.SS "Bypassing permission checks: superuser and capabilities"
|
||||
On a traditional Unix system, the superuser
|
||||
.RI ( root ,
|
||||
|
|
|
@ -49,7 +49,7 @@ and delivers messages in the order that they were sent.
|
|||
Unix sockets support passing file descriptors or process credentials
|
||||
to other processes using ancillary data.
|
||||
.SS Address Format
|
||||
A Unix address is defined as a filename in the filesystem or
|
||||
A Unix address is defined as a filename in the file system or
|
||||
as a unique string in the abstract namespace.
|
||||
Sockets created by
|
||||
.BR socketpair (2)
|
||||
|
@ -199,7 +199,7 @@ option must be enabled on the socket.
|
|||
.SH ERRORS
|
||||
.TP
|
||||
.B EADDRINUSE
|
||||
Selected local address is already taken or filesystem socket
|
||||
Selected local address is already taken or file system socket
|
||||
object already exists.
|
||||
.TP
|
||||
.B ECONNREFUSED
|
||||
|
@ -266,7 +266,7 @@ vs.
|
|||
Unknown socket type.
|
||||
.PP
|
||||
Other errors can be generated by the generic socket layer or
|
||||
by the filesystem while generating a filesystem socket object.
|
||||
by the file system while generating a file system socket object.
|
||||
See the appropriate manual pages for more information.
|
||||
.SH VERSIONS
|
||||
.B SCM_CREDENTIALS
|
||||
|
@ -276,7 +276,7 @@ be used in portable programs.
|
|||
but the implementation details differ.)
|
||||
.SH NOTES
|
||||
In the Linux implementation, sockets which are visible in the
|
||||
filesystem honor the permissions of the directory they are in.
|
||||
file system honor the permissions of the directory they are in.
|
||||
Their owner, group and their permissions can be changed.
|
||||
Creation of a new socket will fail if the process does not have write and
|
||||
search (execute) permission on the directory the socket is created in.
|
||||
|
|
|
@ -678,11 +678,11 @@ Also, the directory ZZZ usually changes when a version changes
|
|||
(though filename globbing could partially overcome this).
|
||||
Finally, using the file: scheme doesn't easily support people
|
||||
who dynamically load documentation from the Internet (instead of
|
||||
loading the files onto a local filesystem).
|
||||
loading the files onto a local file system).
|
||||
A future URI scheme may be added (e.g., "userdoc:") to permit
|
||||
programs to include cross-references to more detailed documentation
|
||||
without having to know the exact location of that documentation.
|
||||
Alternatively, a future version of the filesystem specification may
|
||||
Alternatively, a future version of the file-system specification may
|
||||
specify file locations sufficiently so that the file: scheme will
|
||||
be able to locate documentation.
|
||||
.PP
|
||||
|
|
|
@ -23,7 +23,7 @@ system call.
|
|||
The kernel keeps data in memory to avoid doing (relatively slow) disk
|
||||
reads and writes.
|
||||
This improves performance, but if the computer
|
||||
crashes, data may be lost or the filesystem corrupted as a result.
|
||||
crashes, data may be lost or the file system corrupted as a result.
|
||||
.B sync
|
||||
ensures that everything in memory is written to disk.
|
||||
.PP
|
||||
|
|
Loading…
Reference in New Issue