L-DEVICES(5) File Formats Manual L-DEVICES(5)
L-devices - UUCP device description file
The L-devices file is consulted by the UUCP daemon uucico(8) under the direction of L.sys(5) for information on the devices that it may
use. Each line describes exactly one device.
A line in L-devices has the form:
Caller Device Call_Unit Class Dialer [Expect Send]....
Each item can be separated by any number of blanks or tabs. Lines beginning with a `#' character are comments; long lines can be continued
by appending a `' character to the end of the line.
Caller denotes the type of connection, and must be one of the following:
ACU Automatic call unit, e.g., autodialing modems such as the Hayes Smartmodem 1200 or Novation ``Smart Cat''.
DIR Direct connect; hardwired line (usually RS-232) to a remote system.
DK AT&T Datakit.
MICOM Micom Terminal switch.
PAD X.25 PAD connection.
PCP GTE Telenet PC Pursuit.
SYTEK Sytek high-speed dedicated modem port connection.
TCP Berkeley TCP/IP or 3Com UNET connection. These are mutually exclusive. Note that listing TCP connections in L-devices is superflu-
ous; uucico does not even bother to look here since it has all the information it needs in L.sys(5).
Device is a device file in /dev/ that is opened to use the device. The device file must be owned by UUCP, with access modes of 0600 or bet-
ter. (See chmod(2)).
Call_Unit is an optional second device file name. True automatic call units use a separate device file for data and for dialing; the
Device field specifies the data port, while the Call_unit field specifies the dialing port. If the Call_unit field is unused, it must not
be left empty. Insert a dummy entry as a placeholder, such as ``0'' or ``unused.''
Class is an integer number that specifies the line baud (for dialers and direct lines) or the port number (for network connections).
The Class may be preceded by a non-numeric prefix. This is to differentiate among devices that have identical Caller and baud, but are
distinctly different. For example, ``1200'' could refer to all Bell 212-compatible modems, ``V1200'' to Racal-Vadic modems, and ``C1200''
to CCITT modems, all at 1200 baud. Similarly, ``W1200'' could denote long distance lines, while ``L1200'' could refer to local phone
Dialer applies only to ACU devices. This is the "brand" or type of the ACU or modem.
DF02 DEC DF02 or DF03 modems.
DF112 Dec DF112 modems. Use a Dialer field of DF112T to use tone dialing, or DF112P for pulse dialing.
att AT&T 2224 2400 baud modem.
cds224 Concord Data Systems 224 2400 baud modem.
dn11 DEC DN11 Unibus dialer.
hayes Hayes Smartmodem 1200 and compatible autodialing modems. Use a Dialer field of hayestone to use tone dialing, or hayespulse for
pulse dialing. It is also permissible to include the letters `T' and `P' in the phone number (in L.sys) to change to tone or pulse
midway through dialing. (Note that a leading `T' or `P' will be interpreted as a dialcode!)
Hayes Smartmodem 2400 and compatible modems. Use a Dialer field of hayes2400tone to use tone dialing, or hayes2400pulse for pulse
Novation ``Smart Cat'' autodialing modem.
penril Penril Corp ``Hayes compatible'' modems (they really aren't or they would use the hayes entry.)
rvmacs Racal-Vadic 820 dialer with 831 adapter in a MACS configuration.
va212 Racal-Vadic 212 autodialing modem.
va811s Racal-Vadic 811s dialer with 831 adapter.
va820 Racal-Vadic 820 dialer with 831 adapter.
vadic Racal-Vadic 3450 and 3451 series autodialing modems.
ventel Ventel 212+ autodialing modem.
vmacs Racal-Vadic 811 dialer with 831 adapter in a MACS configuration.
Expect/Send is an optional Expect/Send script for getting through a smart port selector, or for issuing special commands to the modem. The
syntax is identical to that of the Expect/Send script of L.sys. The difference is that the L-devices script is used before the connection
is made, while the L.sys script is used after.
/etc/uucp/UUAIDS/L-devices L-devices example
uucp(1), uux(1), L.sys(5), uucico(8)
4.3 Berkeley Distribution October 22, 1996 L-DEVICES(5)