####################################################################### # HoneyDanBer (HDB) UUCP Devices File ####################################################################### # # ACU tty00 - 1200 penril \D # Some sample entries: # NOTE - all lines must have at least 5 fields # use '-' for unused fields # The Devices file is used in conjunction with the Dialers file. # Types that appear in the 5th field must be either built-in # functions (801, Sytek, TCP, Unetserver, DK) # or standard functions whose name appears in the first # field in the Dialers file. # Two escape characters may appear in this file: # - \D which means don't translate the phone #/token # - \T translate the phone #/token using the Dialcodes file # Both refer to the phone number field in the Systems file (field 5) # \D should always be used with entries in the Dialers file, since the # Dialers file can contain a \T to expand the number if necessary. # \T should only be used with built-in functions that require expansion # NOTE: - if a phone number is expected and a \D or \T is not present # a \T is used for a built-in, and \D is used for an entry # referencing the Dialers file. (see examples below) # # # NOTE: blank lines and lines that begin with a , , or # are # ignored. # protocols can be specified as a comma-subfield of the device type # either in the Devices file (where device type is field 1) # or in the Systems file (where it is field 3). # # # TLI connections? TLI,teg tcp - - TLI \D # # TCP/IP connections TCP,teg uucp - - # # Analog dial up ACU,g tty01,M - 38400 hayes \T ACU,g tty00,M - 38400 hayes \T # ####################################################################### # $Id: Devices,v 1.4 2003/05/12 20:09:33 cirr Exp $ #######################################################################