L-devices(5) - bsd211

1L-DEVICES(5)                  File Formats Manual                 L-DEVICES(5)
2
3
4

NAME

6       L-devices - UUCP device description file
7

DESCRIPTION

9       The  L-devices file is consulted by the UUCP daemon uucico(8) under the
10       direction of L.sys(5) for information on the devices that it  may  use.
11       Each line describes exactly one device.
12
13       A line in L-devices has the form:
14
15       Caller  Device  Call_Unit  Class  Dialer  [Expect  Send]....
16
17       Each  item  can  be  separated  by  any number of blanks or tabs. Lines
18       beginning with a `#' character are comments; long lines can be  contin‐
19       ued by appending a `\' character to the end of the line.
20
21       Caller  denotes  the type of connection, and must be one of the follow‐
22       ing:
23
24       ACU     Automatic call unit, e.g., autodialing modems such as the Hayes
25               Smartmodem 1200 or Novation ``Smart Cat''.
26
27       DIR     Direct  connect;  hardwired  line  (usually RS-232) to a remote
28               system.
29
30       DK      AT&T Datakit.
31
32       MICOM   Micom Terminal switch.
33
34       PAD     X.25 PAD connection.
35
36       PCP     GTE Telenet PC Pursuit.
37
38       SYTEK   Sytek high-speed dedicated modem port connection.
39
40       TCP     Berkeley TCP/IP or 3Com UNET  connection.  These  are  mutually
41               exclusive.   Note  that listing TCP connections in L-devices is
42               superfluous; uucico does not even bother to look here since  it
43               has all the information it needs in L.sys(5).
44
45       Device  is a device file in /dev/ that is opened to use the device. The
46       device file must be owned by UUCP, with access modes of 0600 or better.
47       (See chmod(2)).
48
49       Call_Unit  is an optional second device file name.  True automatic call
50       units use a separate device file for data and for dialing;  the  Device
51       field  specifies the data port, while the Call_unit field specifies the
52       dialing port.  If the Call_unit field is unused, it must  not  be  left
53       empty.   Insert  a  dummy  entry  as  a  placeholder,  such as ``0'' or
54       ``unused.''
55
56       Class is an integer number that specifies the line  baud  (for  dialers
57       and direct lines) or the port number (for network connections).
58
59       The  Class may be preceded by a non-numeric prefix.  This is to differ‐
60       entiate among devices that have identical Caller and baud, but are dis‐
61       tinctly  different.   For  example,  ``1200''  could  refer to all Bell
62       212-compatible modems, ``V1200'' to Racal-Vadic modems,  and  ``C1200''
63       to  CCITT  modems, all at 1200 baud.  Similarly, ``W1200'' could denote
64       long distance lines, while ``L1200'' could refer to local phone lines.
65
66       Dialer applies only to ACU devices. This is the "brand" or type of  the
67       ACU or modem.
68
69       DF02    DEC DF02 or DF03 modems.
70
71       DF112   Dec  DF112  modems.  Use  a  Dialer field of DF112T to use tone
72               dialing, or DF112P for pulse dialing.
73
74       att     AT&T 2224 2400 baud modem.
75
76       cds224  Concord Data Systems 224 2400 baud modem.
77
78       dn11    DEC DN11 Unibus dialer.
79
80       hayes   Hayes Smartmodem 1200 and compatible autodialing modems.  Use a
81               Dialer  field  of  hayestone to use tone dialing, or hayespulse
82               for pulse dialing.  It is also permissible to include the  let‐
83               ters  `T'  and  `P' in the phone number (in L.sys) to change to
84               tone or pulse midway through dialing.  (Note that a leading `T'
85               or `P' will be interpreted as a dialcode!)
86
87       hayes2400
88               Hayes  Smartmodem  2400  and  compatible  modems.  Use a Dialer
89               field of hayes2400tone to use tone dialing,  or  hayes2400pulse
90               for pulse dialing.
91
92       novation
93               Novation ``Smart Cat'' autodialing modem.
94
95       penril  Penril  Corp ``Hayes compatible'' modems (they really aren't or
96               they would use the hayes entry.)
97
98       rvmacs  Racal-Vadic 820 dialer with 831 adapter in  a  MACS  configura‐
99               tion.
100
101       va212   Racal-Vadic 212 autodialing modem.
102
103       va811s  Racal-Vadic 811s dialer with 831 adapter.
104
105       va820   Racal-Vadic 820 dialer with 831 adapter.
106
107       vadic   Racal-Vadic 3450 and 3451 series autodialing modems.
108
109       ventel  Ventel 212+ autodialing modem.
110
111       vmacs   Racal-Vadic  811  dialer  with 831 adapter in a MACS configura‐
112               tion.
113
114       Expect/Send is an optional Expect/Send script  for  getting  through  a
115       smart port selector, or for issuing special commands to the modem.  The
116       syntax is identical to that of the Expect/Send script  of  L.sys.   The
117       difference  is  that the L-devices script is used before the connection
118       is made, while the L.sys script is used after.
119

FILES

121       /etc/uucp/L-devices
122       /etc/uucp/UUAIDS/L-devices    L-devices example
123

NAME

DESCRIPTION

FILES

SEE ALSO