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