System Administration Guide: Resource Management and Network Services

UUCP /etc/uucp/Devices File

The /etc/uucp/Devices file contains information for all the devices that can be used to establish a link to a remote computer. These devices include ACUs—which includes modern, high-speed modems—direct links, and network connections.

Here is an entry in /etc/uucp/Devices for a US Robotics V.32bis modem that is attached to port A and running at 38,400 bps.


Type   Line  Line2 Class Dialer-Token-Pairs
 ACUEC  cua/a -     38400 usrv32bis-ec

Each field is described in the next section.

UUCP Type Field

This field describes the type of link that the device establishes. The UUCP Type field can contain one of the keywords that is described in the sections that follow.

Direct Keyword

The Direct keyword appears mainly in entries for cu connections. This keyword indicates that the link is a direct link to another computer or a port selector. Create a separate entry for each line that you want to reference through the -l option of cu.

ACU Keyword

The ACU keyword indicates that the link to a remote computer (whether through cu, UUCP, asppp, or Solaris PPP 4.0) is made through a modem. This modem can be connected either directly to your computer or indirectly through a port selector.

Port Selector

This is a variable that is replaced in the Type field by the name of a port selector. Port selectors are devices that are attached to a network that prompts for the name of a calling modem, then grant access. The file /etc/uucp/Dialers contains caller scripts only for the micom and develcon port selectors. You can add your own port selector entries to the Dialers file. See UUCP /etc/uucp/Dialers File for more information.

Sys-Name

This variable is replaced by the name of a machine in the Type field, indicating that the link is a direct link to this particular computer. This naming scheme is used to associate the line in this Devices entry with an entry in /etc/uucp/Systems for the computer Sys-Name.

Type Field and /etc/uucp/Systems File

Example 40–5 shows a comparison between the fields in /etc/uucp/Devices and fields in /etc/uucp/Systems. The titles of each column apply only to fields in the Devices file.

The keyword that is used in the Type field of the Devices file is matched against the third field of the Systems file entries. In the Devices file, the Type field has the entry ACUEC, indicating an automatic call unit, in this instance a V.32bis modem. This value is matched against the third field in the Systems file, which also contains the entry ACUEC. See UUCP /etc/uucp/Systems File for more information.


Example 40–5 Type Field and /etc/uucp/Systems File Equivalent


File Name Type   Line  Line2 Class Dialer-Token-Pairs
 
Devices   ACUEC  cua/a -     38400 usrv32bis-ec
 
System    nubian Any   ACUEC 38400 9998888 ““ \d\d\r\n\c-ogin-\r\n\c-ogin.......      
 

UUCP Line Field

This field contains the device name of the line (port) that is associated with the Devices entry. If the modem that is associated with a particular entry were attached to the /dev/cua/a device (serial port A), the name that is entered in this field would be cua/a. An optional modem control flag, M, can be used in the Line field to indicate that the device should be opened without waiting for a carrier. For example:


cua/a,M

UUCP Line2 Field

This field is a placeholder. Always use a dash (-) here. 801–type dialers, which are not supported in the Solaris environment, use the Line2 field. Non-801 dialers do not normally use this configuration, but still require a hyphen in this field.

UUCP Class Field

The Class field contains the speed of the device, if the keyword ACU or Direct is used in the Type field. However, the Class field can contain a letter and a speed (for example, C1200, D1200) to differentiate between classes of dialers (Centrex or Dimension PBX).

This differentiation is necessary because many larger offices can have more than one type of telephone network: one network might be dedicated to serving only internal office communications while another handles the external communications. In such a situation, you must distinguish which line(s) should be used for internal communications and which should be used for external communications.

The keyword that is used in the Class field of the Devices file is matched against the Speed field of Systems file.


Example 40–6 UUCP Class Field


File Name  Type   Line  Line2  Class  Dialer-Token-Pairs
 
Devices    ACU    cua/a -      D2400  hayes

Some devices can be used at any speed, so the keyword Any can be used in the Class field. If Any is used, the line matches any speed that is requested in the Speed field of the Systems file. If this field is Any and the Systems file Speed field is Any, the speed defaults to 2400 bps.

UUCP Dialer-Token-Pairs Field

The Dialer-Token-Pairs (DTP) field contains the name of a dialer and the token to pass it. The DTP field has this syntax:

dialer token [dialer token]

The dialer portion can be the name of a modem, a port monitor, or it can be direct or uudirect for a direct-link device. You can have any number of dialer-token pairs. If the dialer portion is not present, it is taken from a related entry in the Systems file. The token portion can be supplied immediately after the dialer portion.

The last dialer-token pair might not be present, depending on the associated dialer. In most situations, the last pair contains only a dialer portion. The token portion is retrieved from the Phone field of the associated Systems file entry.

A valid entry in the dialer portion can be defined in the Dialers file or can be one of several special dialer types. These special dialer types are compiled into the software and are therefore available without having entries in the Dialers file. The following table shows the special dialer types.

Table 40–3 Dialer-Token Pairs

TCP

TCP/IP network 

TLI

Transport Level Interface Network (without STREAMS) 

TLIS

Transport Level Interface Network (with STREAMS) 

See UUCP Protocol Definitions in the Devices File for more information.

Structure of the Dialer-Token-Pairs Field

The DTP field can be structured four different ways, depending on the device that is associated with the entry:


Example 40–7 Dialers Field for Direct Connect Modem


Dialers   hayes =,-,  ""          \\dA\pTE1V1X1Q0S2=255S12=255\r\c 
                                  \EATDT\T\r\c CONNECT

Notice that only the dialer portion (hayes) is present in the DTP field of the Devices file entry. This means that the token to be passed on to the dialer (in this instance, the phone number) is taken from the Phone field of a Systems file entry. (\T is implied, as described in Example 40–9.)


Example 40–8 UUCP Dialers Field for Computers on Same Port Selector


Dialers    develcon ,""   ""            \pr\ps\c est:\007 \E\D\e \007

As shown, the token portion is left blank. This designation indicates that it is retrieved from the Systems file. The Systems file entry for this computer contains the token in the Phone field, which is normally reserved for the phone number of the computer. Refer to UUCP /etc/uucp/Systems File for details. This type of DTP contains an escape character (\D), which ensures that the contents of the Phone field are not interpreted as a valid entry in the Dialcodes file.


Example 40–9 UUCP Dialers Field for Modems Connected to Port Selector


Dialers    develcon ""    ""     \pr\ps\c  est:\007    \E\D\e      \007
 
Dialers    ventel   =&-%   t""   \r\p\r\c  $           <K\T%\r>\c  ONLINE!

In the first pair, develcon is the dialer and vent is the token that is passed to the Develcon switch to tell it which device (such as Ventel modem) to connect to your computer. This token is unique for each port selector, as each switch can be set up differently. After the Ventel modem has been connected, the second pair is accessed. Ventel is the dialer and the token is retrieved from the Systems file.

Two escape characters can appear in a DTP field:

UUCP Protocol Definitions in the Devices File

You can define the protocol to use with each device in /etc/uucp/Devices. This specification is usually unnecessary because you can use the default or define the protocol with the particular system you are calling. Refer to UUCP /etc/uucp/Systems File for details. If you do specify the protocol, you must use the following form:

Type,Protocol [parameters]

For example, you can use TCP,te to specify the TCP/IP protocol.

The following table shows the available protocols for the Devices file.

Table 40–4 Protocols Used in /etc/uucp/Devices

Protocol 

Description 

t

This protocol is commonly used for transmissions over TCP/IP and other reliable connections. t assumes error-free transmissions.

g

This protocol is UUCP's native protocol. It is slow, reliable, and good for transmission over noisy telephone lines.  

e

This protocol assumes transmission over error-free channels that are message oriented (as opposed to byte-stream oriented, such as TCP/IP).  

f

This protocol is used for transmission over X.25 connections. f relies on flow control of the data stream, and is meant for working over links that can (almost) be guaranteed to be error-free, specifically X.25/PAD links. A checksum is enacted over a whole file only. If a transport fails, the receiver can request retransmission(s).

Here is an example that shows a protocol designation for a device entry:


TCP,te - - Any TCP - 

This example indicates that, for device TCP, you should try to use the t protocol. If the other end refuses, use the e protocol.

Neither e nor t is appropriate for use over modems. Even if the modem assures error-free transmission, data can still be dropped between the modem and the CPU.