FSTAB(5)                                                              FSTAB(5)



NAME
       fstab - static information about the filesystems

SYNOPSIS
       #include <fstab.h>

DESCRIPTION
       The  file _/_e_t_c_/_f_s_t_a_b contains descriptive information about the various
       file systems.  _/_e_t_c_/_f_s_t_a_b is only _r_e_a_d by programs, and not written; it
       is the duty of the system administrator to properly create and maintain
       this file.  The order of records in  _/_e_t_c_/_f_s_t_a_b  is  important  because
       _f_s_c_k_,  _m_o_u_n_t_,  and _u_m_o_u_n_t sequentially iterate through _/_e_t_c_/_f_s_t_a_b doing
       their thing.

       The special file name is the block special file name, and not the char‐
       acter special file name.  If a program needs the character special file
       name, the program must create it by appending a ‘‘r’’  after  the  last
       ‘‘/’’ in the special file name.

       If _f_s__t_y_p_e is ‘‘rw’’ or ‘‘ro’’ then the file system whose name is given
       in the _f_s__f_i_l_e field is normally mounted read-write or read-only on the
       specified  special file.  If _f_s__t_y_p_e is ‘‘rq’’, then the file system is
       normally mounted read-write with  disk  quotas  enabled.   The  _f_s__f_r_e_q
       field  is  used for these file systems by the _d_u_m_p(8) command to deter‐
       mine which file systems need to be dumped.  The _f_s__p_a_s_s_n_o field is used
       by  the  _f_s_c_k(8)  program  to  determine the order in which file system
       checks are done at reboot time.  The root file system should be  speci‐
       fied  with  a _f_s__p_a_s_s_n_o 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 parallelism available in the hardware.

       If _f_s__t_y_p_e is ‘‘sw’’ then the special file is made available as a piece
       of  swap space by the _s_w_a_p_o_n(8) command at the end of the system reboot
       procedure.  The fields other than _f_s__s_p_e_c and _f_s__t_y_p_e are not  used  in
       this case.

       If _f_s__t_y_p_e is ‘‘rq’’ then at boot time the file system is automatically
       processed by the _q_u_o_t_a_c_h_e_c_k(8) command and disk quotas are then enabled
       with  _q_u_o_t_a_o_n(8).   File  system quotas are maintained in a file ‘‘quo‐
       tas’’, which is located at the root of the associated file system.

       If _f_s__t_y_p_e is specified as ‘‘xx’’ the entry is ignored.  This is useful
       to show disk partitions which are currently not used.

       #define   FSTAB_RW  "rw" /* read-write device */
       #define   FSTAB_RO  "ro" /* read-only device */
       #define   FSTAB_RQ  "rq" /* read-write with quotas */
       #define   FSTAB_SW  "sw" /* swap device */
       #define   FSTAB_XX  "xx" /* ignore totally */

       struct fstab {
               char  *fs_spec;  /* block special device name */
               char  *fs_file;  /* file system path prefix */
               char  *fs_type;  /* rw,ro,sw or xx */
               int   fs_freq;   /* dump frequency, in days */
               int   fs_passno; /* pass number on parallel dump */
       };

       The  proper  way to read records from _/_e_t_c_/_f_s_t_a_b is to use the routines
       getfsent(), getfsspec(), getfstype(), and getfsfile().

FILES
       /etc/fstab

SEE ALSO
       getfsent(3X)



4th Berkeley Distribution        May 15, 1985                         FSTAB(5)