summaryrefslogtreecommitdiffstats
path: root/share/man/man5/fstab.5
diff options
context:
space:
mode:
authorschweikh <schweikh@FreeBSD.org>2001-07-14 19:41:16 +0000
committerschweikh <schweikh@FreeBSD.org>2001-07-14 19:41:16 +0000
commit511e378b14868fd06fca565a7db84b7080fdbcb7 (patch)
treefb1031efffc2846e7cacb61180a01c78ece1c3e9 /share/man/man5/fstab.5
parentb855a121e272a07bd83ce7b51f776e73d7412cf4 (diff)
downloadFreeBSD-src-511e378b14868fd06fca565a7db84b7080fdbcb7.zip
FreeBSD-src-511e378b14868fd06fca565a7db84b7080fdbcb7.tar.gz
Removed whitespace at end-of-line; no content changes. I simply did
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//' BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block... Reviewed by: Silence from cvs diff -b MFC after: 7 days
Diffstat (limited to 'share/man/man5/fstab.5')
-rw-r--r--share/man/man5/fstab.520
1 files changed, 10 insertions, 10 deletions
diff --git a/share/man/man5/fstab.5 b/share/man/man5/fstab.5
index 3981be5..2aa625e 100644
--- a/share/man/man5/fstab.5
+++ b/share/man/man5/fstab.5
@@ -47,7 +47,7 @@ contains descriptive information about the various file
systems.
.Nm
is only read by programs, and not written;
-it is the duty of the system administrator to properly create
+it is the duty of the system administrator to properly create
and maintain this file.
Each filesystem is described on a separate line;
fields on each line are separated by tabs or spaces.
@@ -68,7 +68,7 @@ describes the block special device or
remote filesystem to be mounted.
For filesystems of type
.Em ufs ,
-the special file name is the block special file name,
+the special file name is the block special file name,
and not the character special file name.
If a program needs the character special file name,
the program must create it by appending a ``r'' after the
@@ -84,27 +84,27 @@ The third field,
describes the type of the filesystem.
The system can support various filesystem types.
Only the root, /usr, and /tmp filesystems need be statically
-compiled into the kernel;
+compiled into the kernel;
everything else will be automatically loaded at mount
time. (Exception: the UFS family - FFS and LFS cannot
currently be demand-loaded.) Some people still prefer to statically
compile other filesystems as well.
.Bl -tag -width indent -offset indent
-.It Em ufs
+.It Em ufs
a local
.Tn UNIX
filesystem
-.It Em nfs
+.It Em nfs
a Sun Microsystems compatible ``Network File System''
-.It Em swap
+.It Em swap
a disk partition to be used for swapping
.It Em msdos
a DOS compatible filesystem
-.It Em cd9660
+.It Em cd9660
a CD-ROM filesystem (as per ISO 9660)
.\" maybe also say Rock Ridge extensions are handled ?
-.It Em procfs
-a file system for accessing process data
+.It Em procfs
+a file system for accessing process data
.El
.Pp
The fourth field,
@@ -193,7 +193,7 @@ program to determine the order in which filesystem checks are done
at reboot time.
The root filesystem should be specified with a
.Fa fs_passno
-of 1, and other filesystems should have a
+of 1, and other filesystems should have a
.Fa fs_passno
of 2.
Filesystems within a drive will be checked sequentially,
OpenPOWER on IntegriCloud