


      GGGGEEEETTTTTTTTYYYYDDDDEEEEFFFFSSSS((((4444))))                ((((UUUUNNNNIIIIXXXX 5555....0000))))               GGGGEEEETTTTTTTTYYYYDDDDEEEEFFFFSSSS((((4444))))



      NNNNAAAAMMMMEEEE
           gettydefs - speed and terminal settings used by getty

      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
           The ////eeeettttcccc////ggggeeeettttttttyyyyddddeeeeffffssss file contains information used by
           _g_e_t_t_y(_1) to set up the speed and terminal settings for a
           line.  It supplies information on what the _l_o_g_i_n prompt
           should look like. It also supplies the speed to try next if
           the user indicates the current speed is not correct by
           typing a <_b_r_e_a_k> character.

           Each entry in ////eeeettttcccc////ggggeeeettttttttyyyyddddeeeeffffssss has the following format:

                label# initial-flags # final-flags # login-prompt #next-label

           Lines that begin with # are ignored and may be used to
           comment on the file. Each entry, including comment entries,
           must be followed by a blank line. The various fields can
           contain quoted characters of the form \\\\bbbb,,,, \\\\nnnn,,,, \\\\cccc,,,,, etc., as
           well as \_n_n_n, where _n_n_n is the octal value of the desired
           character. The various fields are:

             _l_a_b_e_l    This is the string to which _g_e_t_t_y tries to match
                      its second argument. It is often the speed, such
                      as 1111222200000000, at which the terminal is supposed to
                      run, but it needn't be (see below).

             _i_n_i_t_i_a_l-_f_l_a_g_s
                      These flags are the initial _i_o_c_t_l (2) settings to
                      which the terminal is to be set if a terminal
                      type is not specified to _g_e_t_t_y. _G_e_t_t_y understands
                      the symbolic names specified in
                      ////uuuussssrrrr////iiiinnnncccclllluuuuddddeeee////ssssyyyyssss////tttteeeerrrrmmmmiiiioooo....hhhh (see _t_e_r_m_i_o (7)).
                      Normally, only the speed flag is requried in the
                      _i_n_i_t_i_a_l-_f_l_a_g_s.  _G_e_t_t_y automatically sets the
                      terminal to raw input mode and takes care of most
                      of the other flags. The _i_n_i_t_i_a_l-_f_l_a_g settings
                      remain in effect until _g_e_t_t_y executes _l_o_g_i_n(1).

             _f_i_n_a_l-_f_l_a_g_s
                      These flags assume the values of _i_n_i_t_i_a_l _f_l_a_g_s
                      and are set just before _g_e_t_t_y executes _l_o_g_i_n. The
                      speed flag is again required. The composite flag
                      SSSSAAAANNNNEEEE takes care of most of the other flags that
                      need to be set so that the processor and terminal
                      are communicating in a rational fashion. The
                      other two commonly specified _f_i_n_a_l-_f_l_a_g_s are
                      TTTTAAAABBBB3333, so that tabs are sent to the terminal as
                      spaces, and HHHHUUUUPPPPCCCCLLLL, so that the line is hung up on
                      the final close.





      Page 1                                                   (9010-E)






      GGGGEEEETTTTTTTTYYYYDDDDEEEEFFFFSSSS((((4444))))                ((((UUUUNNNNIIIIXXXX 5555....0000))))               GGGGEEEETTTTTTTTYYYYDDDDEEEEFFFFSSSS((((4444))))



             _l_o_g_i_n-_p_r_o_m_p_t
                      This entire field is printed as the _l_o_g_i_n-_p_r_o_m_p_t.
                      Unlike the above fields where white space is
                      ignored (a space, tab, or new-line), they are
                      included in the _l_o_g_i_n-_p_r_o_m_p_t field.

             _n_e_x_t-_l_a_b_e_l
                      This indicates the next _l_a_b_e_l of the entry in the
                      table that _g_e_t_t_y should use if the user types a
                      <_b_r_e_a_k> or the input cannot be read. Usually, a
                      series of speeds are linked together in this
                      fashion, into a closed set. For instance, 2222444400000000
                      linked to 1111222200000000, which in turn is linked to 333300000000,
                      which finally is linked to 2222444400000000.

           If _g_e_t_t_y is called without a second argument, then the first
           entry of ////eeeettttcccc////ggggeeeettttttttyyyyddddeeeeffffssss is used, thus making the first entry
           of ////eeeettttcccc////ggggeeeettttttttyyyyddddeeeeffffssss the default entry. It is also used if
           _g_e_t_t_y can't find the specified _l_a_b_e_l. If ////eeeettttcccc////ggggeeeettttttttyyyyddddeeeeffffssss
           itself is missing, there is one entry built into the command
           which will bring up a terminal at 9999666600000000 baud.

           It is strongly recommended that after making or modifying
           /fB/etc/gettydefs, it be run through _g_e_t_t_y with the check
           option to be sure there are no errors.

      FFFFIIIILLLLEEEESSSS
           /etc/gettydefs

      SSSSEEEEEEEE AAAALLLLSSSSOOOO
           getty (1), termio (7), login (1), ioctl (2B).
























      Page 2                                                   (9010-E)



