1 files changed, 127 insertions, 0 deletions
diff --git a/doc/fstab(5).html b/doc/fstab(5).html
new file mode 100644
index 0000000..e627015
--- /dev/null
+++ b/doc/fstab(5).html
@@ -0,0 +1,127 @@
+<HTML>
+<HEAD>
+<TITLE>fstab(5) manualpage</TITLE>
+<!-- OWNER_NAME="Marco van Wieringen, OpenWorld System Management" -->
+<!-- OWNER_INFO="The OpenWorld Foundation, The Netherlands" -->
+<LINK REV=MADE HREF="mailto:mvw@planets.elm.net">
+</HEAD>
+<BODY>
+<H1>NAME</H1>
+fstab - static information about the filesystems
+<H1>SYNOPSIS</H1>
+#include <fstab.h>
+<H1>DESCRIPTION</H1>
+The file
+<B>fstab</B>
+contains descriptive information about the various file systems.
+<B>fstab</B>
+is only read by programs, and not written; 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. The order of records in
+<B>fstab</B>
+is important because fsck (8), mount (8), and umount (8) sequentially iterate through
+<B>fstab</B>
+doing their thing.
+<P>
+The first field,
+<B>fs_spec</B>
+describes the block special device or remote filesystem to be mounted.
+<P>
+The second field,
+<B>fs_file</B>
+describes the mount point for the filesystem. For swap partitions, this
+field should be specified as ``none''.
+<P>
+The third field,
+<B>fs_vfstype</B>
+describes the type of the filesystem.  The system currently supports three
+types of filesystems:
+<UL>
+<LI>
+<B>minix</B>
+<BR>
+a local filesystem, supporting filenames of length 14 or 30 characters.
+<LI>
+<B>ext</B>
+<BR>
+a local filesystem with longer filenames and larger inodes.  This
+filesystem has been replaced by the
+<B>ext2</B>
+file system, and should no longer be used.
+<LI>
+<B>ext2</B>
+<BR>
+a local filesystem with longer filenames, larger inodes, and lots of other
+features.
+<LI>
+<B>xiafs</B>
+<BR>
+a local filesystem with longer filenames, larger inodes, and lots of other
+features.
+<LI>
+<B>msdos</B>
+<BR>
+a local filesystem for MS-DOS partitions.
+<LI>
+<B>hpfs</B>
+<BR>
+a local filesystem for HPFS partitions.
+<LI>
+<B>iso9660</B>
+<BR>
+a local filesystem used for CD-ROM drives.
+<LI>
+<B>nfs</B>
+<BR>
+a filesystem for mounting partitions from remote systems.
+<LI>
+<B>swap</B>
+<BR>
+a disk partition to be used for swapping.
+</UL>
+<P>
+If
+<B>vfs_fstype</B>
+is specified as ``ignore'' the entry is ignored. This is useful to show
+disk partitions which are currently unused.
+<P>
+The fourth field,
+<B>fs_mntops</B>
+describes the mount options associated with the filesystem.
+It is formatted as a comma separated list of options.  It contains at least
+the type of mount plus any additional options appropriate to the filesystem
+type.  For documentation on all of the available options, see mount (8).
+<P>
+The fifth field,
+<B>fs_freq</B>
+is used for these filesystems by the dump (8) command to determine which
+filesystems need to be dumped.  If the fifth field is not present, a value
+of zero is returned and dump will assume that the filesystem does not need
+to be dumped.
+<P>
+The sixth field,
+<B>fs_passno</B>
+is used by the fsck (8) program to determine the order in which filesystem
+checks are done at reboot time. The root filesystem should be specified
+with a
+<B>fs_passno</B>
+of 1, and other filesystems should have a 
+<B>fs_passno</B>
+of 2.  Filesystems within a drive will be checked sequentially, but
+filesystems on different drives will be checked at the same time to utilize
+parallelism available in the hardware. If the sixth field is not present
+or zero, a value of zero is returned and fsck will assume that the filesystem
+does not need to be checked.
+<P>
+The proper way to read records from
+<B>fstab</B>
+is to use the routines getmntent (3).
+<H1>FILES</H1>
+<B>/etc/fstab</B>
+resides in
+<B>/etc</B>
+<H1>SEE ALSO</H1>
+getmntent (3), mount (8), swapon (8)
+</BODY>
+</HTML>