![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to l.sys CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT|
Return to l.sys CVS log | Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT |
1.1 root 1:
2:
3: L.sys File Format L.sys
4:
5:
6:
7:
8: Format for UUCP site descriptions
9:
10: /uussrr/lliibb/uuuuccpp/LL.ssyyss
11:
12: The file LL.ssyyss holds descriptions of remote sites that are
13: accessed via UUCP. UUCP utilities read from this file the
14: description of any system that you ask them to access. The
15: superuser rroooott can read and edit the contents of this file, both
16: to update its contents and to add new descriptions.
17:
18: Each line in LL.ssyyss is either a comment or a site descriptor. If
19: a line begins with a pound sign (`#'), it is a comment;
20: otherwise, it is treated as a site descriptor. Each site
21: description consists of five or more fields, each field being
22: demarcated by one or more white-space characters.
23:
24: ***** Site Description *****
25:
26: The first five fields of a site description identify the site and
27: how to contact it. These fields are as follows:
28:
29: 11. RReemmoottee ssyysstteemm nnaammee
30: This names the remote system. In COHERENT versions 3.0.0
31: and 3.1.0, only the first seven characters are significant.
32:
33: 22. LLeeggaall ccaallll ttiimmeess
34: This entry specifies when the remote site may be called.
35: There are several possible formats:
36:
37: NNeevveerr
38: _d_a_y__l_i_s_t
39: _d_a_y__a_n_d__t_i_m_e__l_i_s_t
40:
41: NNeevveerr means never call the remote site; use it only for
42: sites that will only be calling you. _d_a_y__l_i_s_t may be any of
43: the following: AAnnyy (that is, call as soon as a file is
44: queued for sending), WWkk (for Monday through Friday), or one
45: or more of SSuu, MMoo, TTuu, WWee, TThh, FFrr, or SSaa, separated by
46: commas (be sure not to use spaces here). A
47: _d_a_y__a_n_d__t_i_m_e__l_i_s_t is identical to a _d_a_y__l_i_s_t but appends a
48: _t_i_m_e field to one or more of the days specified. The _t_i_m_e
49: field consists of two four-digit 24-hour times separated by
50: a hyphen. The legal call time is any time at or after the
51: first time and at or before the second time. If the first
52: time is greater than the second time, then the valid calling
53: times will be from midnight to the second time and from the
54: first time through midnight. Omitting the _t_i_m_e field
55: permits calling at any time on the specified day. For
56: example:
57:
58: # never dial the site
59: Never
60: # dial the site whenever a file is queued
61: Any
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: L.sys File Format L.sys
70:
71:
72:
73: # dial on Sunday, Monday and Tuesday, 2-5 AM
74: SuMoTu0200-0500
75: # Weekdays between 1-7 PM and all day on Saturday
76: Wk1300-1900,Sa
77: # Midnight Sunday through 2 AM and 11 PM through midnight
78: Su2300-0200
79:
80:
81: 33. DDeevviiccee
82: This indicates the device on your computer via which UUCP is
83: to contact the remote site. For sites accessed via a modem,
84: use the entry AACCUU. For sites directly connected via a serial
85: port, use the name of the port, e.g., ccoomm33ll.
86:
87: 4. SSppeeeedd
88: This gives the the baud rate at which UUCP is to call the
89: remote system, e.g., 1200, 2400, or 9600. This speed must
90: be valid according to the file /eettcc/mmooddeemmccaapp for at least
91: one modem described in the file LL-ddeevviicceess.
92:
93: 55. TTeelleepphhoonnee nnuummbbeerr
94: This gives the string that UUCP is to send to the modem in
95: order to call the remote site. This string may include
96: special characters for your modem (e.g., some modems accept
97: a comma if a pause is needed during dialing), but will
98: usually be simply the number to dial, e.g. ``17085590412''.
99: The string that is actually sent to the modem consists of
100: the ccss and ddss strings from the modem's entry in
101: /eettcc/mmooddeemmccaapp, the telephone number, and finally the ddee and
102: ccee strings from /eettcc/mmooddeemmccaapp.
103:
104: ***** Chat Script *****
105:
106: The remaining fields in a descriptor form the ``chat script'',
107: that is, the dialogue that your UUCP system must perform in order
108: to log on to the remote computer. The chat script consists of
109: strings of characters to be exchanged between the remote computer
110: and your UUCP system; first comes an _e_x_p_e_c_t__s_t_r_i_n_g (the string
111: that your system expects), followed by a _s_e_n_d__s_t_r_i_n_g (the string
112: to send in response to the _e_x_p_e_c_t__s_t_r_i_n_g). When calling a remote
113: site, your computer waits for a carrier from the remote modem,
114: then waits for the first _e_x_p_e_c_t__s_t_r_i_n_g, after which it sends the
115: first _s_e_n_d__s_t_r_i_n_g, etc.
116:
117: Consider, for example, the remote system bbaazzooookkaa, which has a
118: login prompt of CCoohheerreenntt llooggiinn:; assume that your login is
119: hhoowwaarrdd, the remote system prompts for passwords with ppaasssswwoorrdd:,
120: and your password is rr5566dd9922. The chat script for bbaazzooookkaa will
121: read as follows:
122:
123:
124:
125:
126:
127:
128:
129:
130: COHERENT Lexicon Page 2
131:
132:
133:
134:
135: L.sys File Format L.sys
136:
137:
138:
139: ogin: howard word: r56d92
140:
141:
142: As you can see from the above example, an _e_x_p_e_c_t__s_t_r_i_n_g need
143: contain only the last five characters of what the remote system
144: sends.
145:
146: An _e_x_p_e_c_t__s_t_r_i_n_g may be compound or simple. A simple
147: _e_x_p_e_c_t__s_t_r_i_n_g is either a sequence of characters (not including
148: spaces, tabs, or hyphens) or a pair of quotation marks "". An
149: empty pair of quotation marks tells UUCP not to wait for any
150: incoming prompt, but go ahead and send the next _s_e_n_d__s_t_r_i_n_g
151: (i.e., expect a null string). A compound _e_x_p_e_c_t__s_t_r_i_n_g is a
152: sequence of fields separated by hyphens, in the format:
153:
154:
155: _s_i_m_p_l_e__e_x_p_e_c_t__s_t_r_i_n_g-_s_e_n_d__s_t_r_i_n_g-_s_i_m_p_l_e__e_x_p_e_c_t__s_t_r_i_n_g-_s_e_n_d__s_t_r_i_n_g...
156:
157:
158: A compound _e_x_p_e_c_t__s_t_r_i_n_g has no spaces or tabs. If the first
159: simple _e_x_p_e_c_t__s_t_r_i_n_g is not received within 25 seconds, the first
160: _s_e_n_d__s_t_r_i_n_g after the hyphen is sent and the system waits for the
161: second simple _e_x_p_e_c_t__s_t_r_i_n_g; if the second simple _e_x_p_e_c_t__s_t_r_i_n_g
162: is not received after 25 seconds, the second _s_e_n_d__s_t_r_i_n_g is sent,
163: and so on. This syntax allows UUCP to use any number of
164: alternate expect/send exchanges, rather than failing if it does
165: not receive the first _e_x_p_e_c_t__s_t_r_i_n_g.
166:
167: A _s_e_n_d__s_t_r_i_n_g is the character sequence that UUCP sents to the
168: remote site. Unless otherwise specified, UUCP sends a newline at
169: the end of any _s_e_n_d__s_t_r_i_n_g. As a special case of this, an empty
170: alternate _s_e_n_d__s_t_r_i_n_g tells UUCP to send a single newline to the
171: remote site if the preceding _e_x_p_e_c_t__s_t_r_i_n_g is not received. For
172: example
173:
174:
175: ogin:--ogin:
176:
177:
178: is a compound _e_x_p_e_c_t__s_t_r_i_n_g that tells UUCP to wait for the
179: string ooggiinn: from the remote site. If UUCP does not receive this
180: string within the specified time limit, it sends a newline and
181: again waits for ooggiinn: from the remote site.
182:
183: You can also use escape sequences to embed non-printable
184: characters in a _s_e_n_d__s_t_r_i_n_g. The following table lists all legal
185: escape sequences and their meaning:
186:
187:
188: _N_o_t_a_t_i_o_n _M_e_a_n_i_n_g
189:
190: \b Send backspace
191: \c Suppress newline after _s_e_n_d__s_t_r_i_n_g
192: (Must appear at end of string)
193: \d Delay one second while sending
194:
195:
196: COHERENT Lexicon Page 3
197:
198:
199:
200:
201: L.sys File Format L.sys
202:
203:
204:
205: \n Send newline
206: \r Send carriage return
207: \s Send a space
208: \t Send tab
209:
210:
211: ***** Limitations *****
212:
213: LL.ssyyss has the following limitations:
214:
215: -> Site descriptors may not continue beyond one line.
216:
217: -> Line length cannot exceed 511 characters.
218:
219: -> No line may have more than 27 composite-expect/send pairs.
220:
221: -> In the COHERENT versions 3.0.0 and 3.1.0, there is no way to
222: send a break signal to the remote modem. This feature will
223: be added in a future release.
224:
225: ***** Example *****
226:
227:
228: The following LL.ssyyss entries are used to dial into the MWC UUCP
229: BBS. The first entry corresponds to 2400 b.p.s. access and the
230: second to 9600 b.p.s via a Telebit Trailblazer modem. Please
231: note that in the example below, entries are continued over
232: multiple lines; in the actual file, each entry must be on a
233: single line, but the line may exceed 80 characters in length.
234:
235:
236: mwcbbs Any ACU 2400 17085590412 \
237: "" \r\d\r in:--in: nuucp word: public word: SERIALNUM
238: #mwcbbs Any ACU 9600 17085590445 \
239: FAST \r\d\r in:--in: nuucp word: public word: SERIALNUM
240:
241:
242: For further details on accessing the MWC BBS, refer to the
243: COHERENT Release Notes.
244:
245: ***** See Also *****
246:
247: ffiillee ffoorrmmaattss, LL-ddeevviicceess, mmooddeemmccaapp, PPeerrmmiissssiioonnss, UUUUCCPP
248:
249:
250:
251:
252:
253:
254:
255:
256:
257:
258:
259:
260:
261:
262: COHERENT Lexicon Page 4
263:
264:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.