HPUX checklist[4]
checklist(4) checklist(4)
NAME
checklist - static information about the file systems
SYNOPSIS
#include <checklist.h>
DESCRIPTION
checklist is an ASCII file that resides in directory /etc. It is only
read by programs, and not written. It is the duty of the system
administrator to properly create and maintain this file.
/etc/checklist contains a list of mountable file system entries. The
fields within each entry of a file system are separated by one or more
blanks. Each file system entry is contained on a separate line. The
order of entries in /etc/checklist is only important for entries
without a pass number field. Entries without a pass number are
sequentially checked by fsck (see fsck(1M)) after the entries with a
pass number have been checked.
Each file system entry must contain a special file name and may
additionally contain all of the following fields, in order:
directory
type
options
backup frequency
pass number (on parallel fsck)
comment
If any of the fields after the name of the special file are present,
they must all be present in the order indicated to ensure correct
placeholding.
Entries from this file are accessed by use of getmntent() (see
getmntent(3X)).
The fields are separated by white space, and a # as the first non-
whitespace character in an entry or field indicates a comment.
special file name
is a block special file name. This field is used by
fsck, mount, swapon, and other commands.
directory is the name of the root of the mounted file system that
corresponds to the special file name. If type is
swapfs, directory can be the name of any directory
within a file system. Only one directory should be
specified per file system. directory must already
exist and must be given as an absolute path name.
type can be hfs, cdfs, nfs, swap, swapfs, or ignore. If
type is hfs, a local HFS file system is implied. If
type is cdfs, a local CD-ROM file system is implied.
Hewlett-Packard Company - 1 - HP-UX Release 9.0: August 1992
checklist(4) checklist(4)
If type is nfs, a remote NFS file system is implied
(see NETWORKING FEATURES below). If type is swap, the
special file name is made available as an area of swap
space by the swapon command (see swapon(1M)). The
options field is valid. The fields directory, pass
number, and backup frequency are ignored for swap
entries. If type is swapfs, the file system in which
directory resides is made available as swap space by
swapon. The options field is valid. The fields
special file name, pass number, and backup frequency
are ignored for swapfs entries. Entries marked by the
type ignore are ignored by all commands and can be used
to mark unused sections. If type is specified as
either ignore, swap, or swapfs, the entry is ignored by
the mount and fsck commands (see mount (1M) and
fsck(1M)). fsck also ignores entries with type
specified as cdfs or nfs.
options appear in this entry as a comma-separated list of
option keywords as found in mount(1M) or swapon(1M).
Which keywords are used depends on the parameter
specified in type.
backup frequency
is reserved for possible use by future backup
utilities.
pass number is used by the fsck command to determine the order in
which file system checks are done. The root file
system should be specified with a pass number of 1, and
other file systems should have larger numbers. File
systems within a drive should have distinct numbers,
but file systems on different drives can be checked on
the same pass to utilize possible parallelism available
in the hardware. A file system with a pass number of
zero is ignored by the fsck command. If pass number is
not present, fsck checks each such file system
sequentially after all eligible file systems with pass
numbers have been checked.
comment is an optional field that starts with a # character and
ends with a new-line character. Space from the pass
number up to the comment field, if present, or the
new-line is reserved for future use.
There is no limit to the number of special file name fields in
/etc/checklist.
NETWORKING FEATURES
NFS
If the field type is nfs, a remote NFS file system is implied. For
Hewlett-Packard Company - 2 - HP-UX Release 9.0: August 1992
checklist(4) checklist(4)
NFS file systems, the special file name should be the serving machine
name followed by ":" followed by the path on the serving machine of
the directory to be served. The pass number, and backup frequency
fields are ignored for NFS entries.
EXAMPLES
Examples of typical /etc/checklist entries:
Add an HFS file system at /users using default mount options;
(backup frequency 0) fsck pass 2:
/dev/dsk/c0d1s0 /users hfs defaults 0 2 # /users disk
Add a swap device with default options (directory field (/)
cannot be empty, even though it is ignored):
/dev/dsk/c0d1s0 / swap defaults 0 0 # swap device
Add a swap device on a Series 300, 400, or 700 system using the
space after the end of the file system (options=end):
/dev/dsk/0s0 / swap end 0 0 # swap at end of device
Add file system swap space on the file system containing
directory /swap. type is swapfs; set options to min=10,
lim=4500, res=100, and pri=0 (see swapon(1M)) for explanation of
meanings). device field is ignored but must be non-empty:
default /swap swapfs min=10,lim=4500,res=100,pri=0 0 0
(Note that both a file system entry and a swap entry are required
for devices providing both services.)
DEPENDENCIES
NFS
Here is an example for mounting an NFS file system for systems that
support NFS file systems:
server:/mnt /mnt nfs rw,hard 0 0 #mount from server.
AUTHOR
checklist was developed by HP, AT&T, Sun Microsystems, Inc., and the
University of California, Berkeley.
SEE ALSO
fsck(1M), mount(1M), swapon(1M), getfsent(3X), getmntent(3X),
mnttab(4).
Hewlett-Packard Company - 3 - HP-UX Release 9.0: August 1992