format of UUCP Devices file
type tty_line dialer_line speed dialer [ token ] ...
The Devices file (/usr/lib/uucp/Devices) contains
information for all the devices that can be used to
establish a link to a remote computer.
These devices include automatic call units,
direct links, and network connections.
This file works closely with the
Dialers, Systems, and Dialcodes files.
Each line in the Devices file contains the following
Can contain one of two keywords (direct or ACU),
the name of a Local Area Network switch, or a system name.
Contains the device name of the
line (port) associated with the Devices entry.
For example, if the Automatic Dial Modem for a particular
entry is attached to the /dev/tty11 line, the name
entered in this field is tty11.
Useful only for 801 type dialers, which do not contain a modem
and must use an additional line. If you do not have an 801 dialer,
enter a hyphen ( - ) as a placeholder.
The speed or speed range of the device.
It may contain an indicator for distinguishing different dialer classes.
One or more pairs of dialers and tokens. Each represents a dialer
and an argument to be passed to it.
The dialer portion can be the name of an automatic dial modem,
or it may specify direct for a direct link device.
For best results, dialer programs are preferred entries in this
The following is an example of such an entry using a dialer binary:
ACU ttynn - 300-2400 /usr/lib/uucp/dialHA24
Note that all lines must have at least 5 fields.
Use ``-'' for unused fields.
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.
Blank lines and lines that begin with a Space or Tab 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).
Two escape characters can be used in this file:
do not translate the phone /token
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 that if a phone number is expected and a \D or \T is not present
a \T is used for a built-in function, and \D is used for an entry
referencing the Dialers file.
The following are examples of common Devices files.
Standard modem line
ACU tty00 - 1200 801
ACU tty00 - 1200 penril
ACU tty00 - 1200 penril \D
A direct line
This example will allow cu -ltty00 to work.
This entry could also be used for certain modems in manual mode.
Direct tty00 - 4800 direct
A ventel modem on a develcon switch
``vent'' is the token given to the develcon to reach the ventel modem.
ACU tty00 - 1200 develcon vent ventel
ACU tty00 - 1200 develcon vent ventel \D
To reach a system on the local develcon switch
Develcon tty00 - Any develcon \D
A direct connection to a system
systemx tty00 - Any direct
Streams network examples
A Streams network that conforms to the AT&T Transport Interface
with a direct connection to login service (that is, without
explicitly using the Network Listener Service dial script):
networkx , eg devicex - - TLIS \D
The Systems file entry looks like:
systemx Any networkx - addressx in:--in: nuucp word: nuucp
You must replace systemx, networkx, addressx,
and devicex with system
name, network name, network address and network device, respectively.
For example, entries for machine sffo on a
STARLAN NETWORK might look like:
sffo Any STARLAN - sffo in:--in: nuucp word: nuucp
STARLAN,eg starlan - - TLIS \D
To use a Streams network that conforms to the AT&T Transport Interface
and that uses the Network Listener Service dial script to negotiate
for a server:
networkx,eg devicex - - TLIS \D nls
To use a non-Streams network that conforms to the AT&T Transport
Interface and that uses the Network Listener Service dial script
to negotiate for a server:
networkx,eg devicex - - TLI \D nls
full pathname of Devices
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005