Commit | Line | Data |
---|---|---|
9b270428 BK |
1 | .sp |
2 | .SH | |
3 | I. GETTING STARTED | |
4 | .SH | |
5 | Logging In | |
6 | .PP | |
7 | Most of the details about logging in are in the manual | |
8 | section | |
9 | called | |
10 | ``How to Get Started'' | |
11 | (pages | |
12 | .ul | |
13 | iv-v | |
14 | in the 5th Edition). | |
15 | Here are a couple of extra warnings. | |
16 | .PP | |
17 | You must have a | |
18 | .UC UNIX | |
19 | login name, which you can get from | |
20 | whoever administers your system. | |
21 | You also need to know the phone number. | |
22 | .UC UNIX | |
23 | is capable of dealing with a variety of terminals: | |
24 | Terminet 300's; Execuport, TI and similar | |
25 | portables; | |
26 | video terminals; GSI's; and even the venerable | |
27 | Teletype in its various forms. | |
28 | But note: | |
29 | .UC UNIX | |
30 | will not handle IBM 2741 terminals | |
31 | and their derivatives | |
32 | (e.g., some Anderson-Jacobsons, Novar). | |
33 | Furthermore, | |
34 | .UC UNIX | |
35 | is strongly oriented towards devices with | |
36 | .ul | |
37 | lower case. | |
38 | If your terminal produces only upper case (e.g., model 33 Teletype), | |
39 | life will be so difficult that you should look for another | |
40 | terminal. | |
41 | .PP | |
42 | Be sure to set the switches appropriately on your device: | |
43 | speed (if it's variable) to 30 characters per second, | |
44 | lower case, | |
45 | full duplex, even parity, and any others | |
46 | that local wisdom advises. | |
47 | Establish a connection using whatever | |
48 | magic is needed for your terminal. | |
49 | .UC UNIX | |
50 | should type ``login:'' at you. | |
51 | If it types garbage, you may be at the wrong speed; | |
52 | push the `break' or `interrupt' key once. | |
53 | If that fails to produce a login message, consult a guru. | |
54 | .PP | |
55 | When you get a ``login:'' message, | |
56 | type your | |
57 | login name | |
58 | .ul | |
59 | in lower case. | |
60 | Follow it by a | |
61 | .UC RETURN | |
62 | if the terminal has one. | |
63 | If a password is required, | |
64 | you will be asked for it, | |
65 | and (if possible) | |
66 | printing will be turned off while you type it, | |
67 | again followed by a | |
68 | .UC RETURN. | |
69 | (On M37 Teletypes always use | |
70 | .UC NEWLINE | |
71 | or | |
72 | .UC LINEFEED | |
73 | in place of | |
74 | .UC RETURN ). | |
75 | .PP | |
76 | The culmination of your login efforts is a percent sign ``%''. | |
77 | The percent sign means that | |
78 | .UC UNIX | |
79 | is ready to accept commands from the terminal. | |
80 | (You may also get a message of the day just before the | |
81 | percent sign or a notification that you have mail.) | |
82 | .SH | |
83 | Typing Commands | |
84 | .PP | |
85 | Once you've seen the percent sign, you can type commands, | |
86 | which are | |
87 | requests that | |
88 | .UC UNIX | |
89 | do something. | |
90 | Try typing | |
91 | .B1 | |
92 | date | |
93 | .B2 | |
94 | followed by | |
95 | .UC RETURN. | |
96 | You should get back something like | |
97 | .B1 | |
98 | Sun Sep 22 10:52:29 EDT 1974 | |
99 | .B2 | |
100 | Don't forget the | |
101 | .UC RETURN | |
102 | after the command, | |
103 | or nothing will happen. | |
104 | If you think you're being ignored, | |
105 | type a | |
106 | .UC RETURN ; | |
107 | something should happen. | |
108 | We won't show the carriage returns, | |
109 | but they have to be there. | |
110 | .PP | |
111 | Another command you might try is | |
112 | .C who , | |
113 | which tells you everyone who is currently logged in: | |
114 | .B1 | |
115 | who | |
116 | .B2 | |
117 | gives something like | |
118 | .B1 | |
119 | pjp ttyf Sep 22 09:40 | |
120 | bwk ttyg Sep 22 09:48 | |
121 | mel ttyh Sep 22 09:58 | |
122 | .B2 | |
123 | The time is when the user logged in. | |
124 | .PP | |
125 | If you make a mistake typing the command name, | |
126 | .UC UNIX | |
127 | will tell you. | |
128 | For example, if you type | |
129 | .B1 | |
130 | whom | |
131 | .B2 | |
132 | you will be told | |
133 | .B1 | |
134 | whom: not found | |
135 | .B2 | |
136 | .SH | |
137 | Strange Terminal Behavior | |
138 | .PP | |
139 | Sometimes you can get into a state | |
140 | where your terminal acts strangely. | |
141 | For example, | |
142 | each letter may be typed twice, | |
143 | or the | |
144 | .UC RETURN | |
145 | may not cause a line feed. | |
146 | You can often fix this by logging out and logging back in. | |
147 | Or you can read the description of the command | |
148 | .C stty | |
149 | in section I of the manual. | |
150 | This will also tell you how to get intelligent treatment of | |
151 | tab characters | |
152 | (which are much used in | |
153 | .UC UNIX ) | |
154 | if your terminal doesn't have tabs. | |
155 | If it does have computer-settable tabs, | |
156 | the command | |
157 | .C tabs | |
158 | will set the stops correctly for you. | |
159 | .SH | |
160 | Mistakes in Typing | |
161 | .PP | |
162 | If you make a typing mistake, and see it before the carriage return | |
163 | has been typed, | |
164 | there are two ways to recover. | |
165 | The sharp-character ``#'' erases the last character typed; | |
166 | in fact successive uses of ``#'' erase characters back to | |
167 | the beginning of the line (but not beyond). | |
168 | So if you type badly, you can correct as you go: | |
169 | .B1 | |
170 | dd#atte##e | |
171 | .B2 | |
172 | is the same as ``date''. | |
173 | .PP | |
174 | The at-sign ``@'' erases all of the characters | |
175 | typed so far | |
176 | on the current input line, | |
177 | so if the line is irretrievably fouled up, type an ``@'' and start over | |
178 | (on the same line!). | |
179 | .PP | |
180 | What if you must enter a sharp or at-sign | |
181 | as part of the text? | |
182 | If you precede either ``#'' or ``@'' by a backslash ``\\'', | |
183 | it loses its erase meaning. | |
184 | This implies that to erase a backslash, | |
185 | you have to type two sharps or two at-signs. | |
186 | The backslash is used extensively in | |
187 | .UC UNIX | |
188 | to indicate that the following character is in some way special. | |
189 | .SH | |
190 | Readahead | |
191 | .PP | |
192 | .UC UNIX | |
193 | has full readahead, | |
194 | which means that you can type as fast as you want, | |
195 | whenever you want, | |
196 | even when some command is typing at you. | |
197 | If you type during output, | |
198 | your input characters will appear intermixed with the output characters, | |
199 | but they will be stored away by | |
200 | .UC UNIX | |
201 | and interpreted in the correct order. | |
202 | So you can type two commands one after another without | |
203 | waiting for the first to finish or even begin. | |
204 | .SH | |
205 | Stopping a Program | |
206 | .PP | |
207 | You can stop most programs by | |
208 | typing the character ``DEL'' | |
209 | (perhaps called ``delete'' or ``rubout'' on your terminal). | |
210 | There are exceptions, like the text editor, | |
211 | where | |
212 | .UC DEL | |
213 | stops whatever the program is doing but leaves you in that program. | |
214 | You can also just hang up the phone. | |
215 | The ``interrupt'' or ``break'' key found on most terminals | |
216 | has no effect. | |
217 | .SH | |
218 | Logging Out | |
219 | .PP | |
220 | The easiest way to log out is to hang up the phone. | |
221 | You can also type | |
222 | .B1 | |
223 | login name-of-new-user | |
224 | .B2 | |
225 | and let someone else use the terminal you were on. | |
226 | It is not sufficient just to turn off the terminal. | |
227 | .UC UNIX | |
228 | has no time-out mechanism, so you'll be | |
229 | there forever unless you hang up. | |
230 | .SH | |
231 | ||
232 | .PP | |
233 | When you log in, you may sometimes get the message | |
234 | .B1 | |
235 | You have mail. | |
236 | .B2 | |
237 | .UC UNIX | |
238 | provides a postal system so you can send and receive letters | |
239 | from other users of the system. | |
240 | To read your mail, | |
241 | issue the command | |
242 | .B1 | |
243 | ||
244 | .B2 | |
245 | Your mail will be printed, and then you will be asked | |
246 | .B1 | |
247 | Save? | |
248 | .B2 | |
249 | If you do want to save the mail, type | |
250 | .ul | |
251 | y, | |
252 | for ``yes''; | |
253 | any other response means ``no''. | |
254 | .PP | |
255 | How do you send mail to someone else? | |
256 | Suppose it is to go to ``joe'' (assuming ``joe'' is someone's login name). | |
257 | The easiest way is this: | |
258 | .B1 | |
259 | .ne 7 | |
260 | mail joe | |
261 | .I | |
262 | now type in the text of the letter | |
263 | on as many lines as you like ... | |
264 | after the last line of the letter | |
265 | type the character ``control-d'', | |
266 | that is, hold down ``control'' and type | |
267 | a letter ``d''. | |
268 | .B2 | |
269 | .R | |
270 | And that's it. | |
271 | The ``control-d'' sequence, usually called ``EOT'', is used throughout | |
272 | .UC UNIX | |
273 | to mark the end of input from a terminal, | |
274 | so you might as well get used to it. | |
275 | .PP | |
276 | There are other ways to send mail _ | |
277 | you can send a previously prepared letter, | |
278 | and you can mail to a number of people all at once. | |
279 | For more details see | |
280 | .SE mail (I). | |
281 | .PP | |
282 | The notation | |
283 | .SE mail (I) | |
284 | means the command | |
285 | .C mail | |
286 | in section (I) | |
287 | of the | |
288 | .ul | |
289 | .UC UNIX | |
290 | .ul | |
291 | Programmer's Manual. | |
292 | .SH | |
293 | Writing to other users | |
294 | .PP | |
295 | At some point in your | |
296 | .UC UNIX | |
297 | career, out of the blue will come a message | |
298 | like | |
299 | .B1 | |
300 | Message from joe... | |
301 | .B2 | |
302 | accompanied by a startling beep. | |
303 | It means that Joe wants to talk to you, | |
304 | but unless you take explicit action you won't be able to talk back. | |
305 | To respond, | |
306 | type the command | |
307 | .B1 | |
308 | write joe | |
309 | .B2 | |
310 | This establishes a two-way communication path. | |
311 | Now whatever Joe types on his terminal will appear on yours | |
312 | and vice versa. | |
313 | The path is slow, rather like talking to the moon. | |
314 | (If you are in the middle of something, you have to | |
315 | get to a state where you can type a command. | |
316 | Normally, whatever program you are running has to terminate or be terminated. | |
317 | If you're editing, you can escape temporarily from the editor _ | |
318 | read the manual.) | |
319 | .PP | |
320 | A protocol is needed to keep what you type from getting | |
321 | garbled up with what Joe types. | |
322 | Typically it's like this: | |
323 | .B1 | |
324 | .fi | |
325 | Joe types ``write smith'' and waits. | |
326 | .br | |
327 | Smith types ``write joe'' and waits. | |
328 | .br | |
329 | Joe now types his message | |
330 | (as many lines as he likes). | |
331 | When he's ready for a reply, he | |
332 | signals it by typing (o), which | |
333 | stands for ``over''. | |
334 | .br | |
335 | Now Smith types a reply, also | |
336 | terminated by (o). | |
337 | .br | |
338 | This cycle repeats until | |
339 | someone gets tired; he then | |
340 | signals his intent to quit with | |
341 | (o+o), for ``over | |
342 | and out''. | |
343 | .br | |
344 | To terminate | |
345 | the conversation, each side must | |
346 | type a ``control-d'' character alone | |
347 | on a line. (``Delete'' also works.) | |
348 | When the other person types his ``control-d'', | |
349 | you will get the message ``EOT'' on your terminal. | |
350 | .B2 | |
351 | .PP | |
352 | If you write to someone who isn't logged in, | |
353 | or who doesn't want to be disturbed, | |
354 | you'll be told. | |
355 | If the target is logged in but doesn't answer | |
356 | after a decent interval, | |
357 | simply type ``control-d''. | |
358 | .SH | |
359 | On-line Manual | |
360 | .PP | |
361 | The | |
362 | .UC UNIX | |
363 | Programmer's Manual | |
364 | is typically kept on-line. | |
365 | If you get stuck on something, | |
366 | and can't find an expert to assist you, | |
367 | you can print on your terminal some manual section that might help. | |
368 | It's also useful for getting the most up-to-date | |
369 | information on a command. | |
370 | To print a manual section, type | |
371 | ``man section-name''. | |
372 | Thus to read up on the | |
373 | .C who | |
374 | command, | |
375 | type | |
376 | .B1 | |
377 | man who | |
378 | .B2 | |
379 | If the section in question isn't in part I of the manual, | |
380 | you have to give the section number as well, as in | |
381 | .B1 | |
382 | man 6 chess | |
383 | .B2 | |
384 | Of course you're out of luck if you can't remember the section name. |