|
|
All entries must contain at least five fields. If a field is left blank, the field must contain a dash (-). Blank lines, and lines that begin with white space, a tab, or a hash sign (#) are ignored.
The fields in the Devices file are defined, in order, as follows:
The keyword used in the ``Type'' field of the Devices file is matched against the third field of Systems file entries, as shown in the following sample files:
#Systems file # eagle Any ACU 1200 3251 ogin: nuucp ssword: password sys1 Any CS - sys1,uucico sys2 Any CS - sys3 Any CS - sys3,login in:--in nuucp word:xx sys4 Any DK 9600 sys4 INVOKE "cr1 -r" sys5 Any DK 9600 sys5 in:--in nuucp word:xx sys6 Any LAN - network_addressThe protocol to use for a device can be designated within the ``Type'' field.#Devices file # ACU term/01m - 2400 att4024 Direct term/00 - Any direct sysb term/03 - Any uudirect CS - - - CS LAN,eg tcp - - TLI \D
term/01m,M
.
CS type entries must contain a dash (-) in the ``Line'' field.
The keyword used in the ``Class'' field of the Devices file is matched against the fourth field of Systems file entries as shown in the following Devices and Systems file lines.
#Devices file # ACU tty11 - D1200 penrilSome devices can be used at any speed. In this case, the keyword Any may be specified in the ``Class'' field. If Any is specified, the line will match any speed requested in a Systems file entry. However, if the Devices file ``Class'' field specifies Any and the Systems file ``Class'' field specifies Any, the speed defaults to 1200bps.#Systems file # eagle Any ACU D1200 3251 ogin: nuucp ssword: password
This field has the format:
dialer token [dialer token]
where the last pair may or may not be present, depending on the associated device (dialer). In most cases, the last pair contains only a dialer portion and the token portion is retrieved from the ``Phone'' field of the Systems file entry.
A valid entry for the dialer portion may be defined in the Dialers(4bnu) file or may be one of several special dialer types. These special dialer types are compiled into the software and are therefore available without having to be entered in the Dialers file.
The ``Dialer-Token-Pairs'' field may be structured differently, depending on the device associated with the entry.
If an automatic dial modem is connected directly to a port on your computer, the ``Dialer-Token-Pairs'' field of the associated Devices file entry should only have one pair. This pair will normally be the name of the modem. The dialer configuration files are found in /etc/uucp/default. If /etc/uucp/dialer exists, then that file is used to configure the dialer. Otherwise, the /etc/uucp/Dialers file is checked for a corresponding entry. For example, the ``28-8_Data_Fax_Modem'' has a configuration file:
#Devices file # ACU term/01m,M - 38400 28-8_Data_Fax_ModemThe ``att2212c'' device is defined in the Dialers file:#/etc/uucp/default/28-8_Data_Fax_Modem file # MDM_SETUP=AT &F E0 V1 \V1 S0=0&K3\N6 MDM_SPEAKER=ATM0 MDM_DIALCMD=ATDT MDM_HANGUP=ATH
#Devices file # ACU term/01m,M - 1200 att2212cNotice that only the dialer portion (``att2212c'') is present in the ``Dialer-Token-Pairs'' field of the Devices file entry. This means that the token to be passed to the dialer (in this case the phone number) is taken from the ``Phone'' field of a Systems file entry.#/etc/uucp/Dialers file # att2212c =+-, "" atzod,o12=y,o4=n\r\c 06 atT\T\r\c ed
If a direct link is to be established to a given computer, the ``Dialer-Token-Pairs'' field of the associated entry should contain the keyword direct or uudirect. This is true for both types of direct link entries, Direct and Sys_name (see the discussion of the ``Type'' field).
If you want to communicate with a computer that is on the same local network switch as your computer, your computer must first access the switch, and the switch can make the connection to the other computer. In this type of entry, there is only one pair. The dialer portion is used to match a Dialers file entry as shown here:
#Devices file # Datakit term/03 - 9600 datakitIn the example, the token portion is left blank. This indicates that it is retrieved from the Systems file. The Systems file entry for this particular computer will contain the token in the ``Phone'' field, which is normally reserved for the telephone number of the computer (see the discussion of the ``Phone'' field in Systems(4bnu). This type of dialer-token pair contains an escape character (\D) to ensure that the contents of the ``Phone'' field will not be interpreted as a valid entry in the Dialcodes file.#Dialers file # datakit "" "" \d TION: - - :TION \D
If an automatic dial modem is connected to a switch, your computer must first access the switch and the switch will make the connection to the automatic dial modem. This type of entry requires two dialer-token pairs. The dialer portion of each pair (the fifth and seventh fields of the entry) will be used to match entries in the Dialers file.
#Devices file # ACU term/04 - 1200 datakit dial att2212cIn the first pair, ``datakit'' is the dialer and ``dial'' is the token that is passed to the Datakit switch to tell it which device (automatic dial modem) to connect to your computer. This token will be unique for each LAN switch since each switch may be set up differently. Once the modem has been connected, the second dialer-token pair is accessed. The second dialer is ``att2212c''; the token is retrieved from the Systems file.#Dialers file # datakit "" "" \d TION: - - :TION \D att2212c =+-, "" atzod,o12=y,o4=n\r\c \006 atT\T\r\c ed
There are two escape characters that may appear in a ``Dialer-Token-Pairs'' field:
If the dialer is an internal dialer, \T is the default. Otherwise, \D is the default.
Available protocols are:
Two parameters characterize the g protocol: windows and packetsize. windows indicates the number of packets that may be transmitted without waiting for an acknowledgement from the remote host. packetsize indicates the number of data bytes in each packet. By default, windows is set to 7 packets and packetsize is set to 64 bytes.
windows may range from 1 to 7, and packetsize may range from 32 to 4096 bytes, in powers of 2.
There are no parameters to be tuned within the e protocol.
There are no parameters to be tuned within the d protocol.
The following example uses the e protocol over a TCP/IP local area network. If the e protocol is not available, g will be used instead.
TCP,eg tcp - - TLIS \DThe next example uses the G protocol on a high-speed modem. The number of windows is set to 7, and the packet size is 512 bytes. If the G protocol is unavailable, the generic g protocol will be used.
ACU,G(7,512)g term/11 - 9600 att2296aPresumably, seven windows with a packet size of 512 bytes will provide optimum throughput for the specified device.
For incoming connections, the preferred protocol priority and parameters may be specified in the Config file (see Config(4bnu)) using the protocol parameter.