aboutsummaryrefslogtreecommitdiffstats
path: root/man5
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2008-03-19 07:26:08 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2008-03-19 07:26:08 +0000
commit24d01c530c5a3f75217543d02bf6712395e5f90c (patch)
tree0fff2e832ef0714ca1a56c5c70fad257b6471c14 /man5
parentbed47b47a76a796711a98870ef7d5cf4dc878af7 (diff)
downloadman-pages-24d01c530c5a3f75217543d02bf6712395e5f90c.tar.gz
s/filesystem/file system/
Diffstat (limited to 'man5')
-rw-r--r--man5/filesystems.562
-rw-r--r--man5/proc.534
2 files changed, 48 insertions, 48 deletions
diff --git a/man5/filesystems.5 b/man5/filesystems.5
index 49cfb1684c..57faaaa800 100644
--- a/man5/filesystems.5
+++ b/man5/filesystems.5
@@ -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
diff --git a/man5/proc.5 b/man5/proc.5
index 431a9dbb49..60f812e51d 100644
--- a/man5/proc.5
+++ b/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.
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-11-28 23:09:59 +0000