CHECKLIST(4) — HP-UX

NAME

checklist − static information about the file systems

SYNOPSIS

#include <checklist.h>

DESCRIPTION

Checklist is an ASCII file that resides in the 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. The 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 important because fsck[HFS](1M), mount[HFS](1M), and umount[HFS](1M) sequentially iterate through /etc/checklist.

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

The entries from this file are accessed using the routines in getmntent(3X).

The fields are separated by white space, and a # as the first non-white character indicates a comment.

special file name is a block special file name. This field is used by the fsck[HFS](1M), mount[HFS](1M) and swapon[HFS](1M) and other commands.

These additional fields are ignored in an HP-UX system if the set of system administration tools implemented on that system does not support them:

directory is the name of the root of the mounted file system that corresponds to the special file name. The directory must already exist and must be given as an absolute path name.

type can be hfs, nfs, swap or ignore. If type is hfs, a local HFS file system is implied. If type is nfs, a remote NFS file system is implied. (See NETWORKING FEATURES below.) If the type is swap, the special file name, is made available as a piece of swap space by the swapon[HFS](1M) command. The fields directory, pass number, and backup frequency are ignored for swap 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 or swap, the entry is ignored by the mount[HFS](1M) and fsck[HFS](1M) commands. Fsck will also ignore entries with type specified as nfs.

options appear in this entry as a comma-separated list of option keywords as found in mount[HFS](1M).

backup frequency is reserved for possible use by future backup utilities.

pass number is used by the fsck[HFS](1M) command to determine the order in which file system checks are done when using the -p option of fsck. 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 will be ignored by the fsck[HFS](1M) command. If a pass number is not present, fsck will check 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 pound sign (#) and ends with a newline. Space from the backup frequency up to the comment field, if present, or the newline is reserved for future use.

NETWORKING FEATURES

NFS

If the field type is nfs, a remote NFS file system is implied. For 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 fields pass number, and backup frequency are ignored for NFS entries.

EXAMPLES

Examples of file system entries specified in /etc/checklist:

For systems that support only the special file name field:

/dev/dsk/c0d0s0

For systems that support multi-fields:

/dev/dsk/c0d0s0 / hfs defaults 1 0 #root disk

DEPENDENCIES

Series 500, 800
The fields cited with each file system entry used by /etc/checklist must appear in the following order:

special file name
block special file name
directory
types, as follows:
rw (read-write), ro (read-only), sw (swap), xx (ignore)
pass number
backup frequency
comment

Series 300, 800
There is no limit to the number of special file name fields in /etc/checklist. However, the commands mount -a and umount -a give an error if the number of mountable file system entries in /etc/checklist exceeds NMOUNT.

NFS

EXAMPLES
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 Bell Laboratories, Sun Microsystems, Inc. and the University of California, Berkeley.

Museum

Related Articles