1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
|
<HTML
><HEAD
><TITLE
>IRC</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="The Linux System Administrator's Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Finding Help"
HREF="c2938.html"><LINK
REL="PREVIOUS"
TITLE="Newsgroups and Mailing Lists"
HREF="x2943.html"><LINK
REL="NEXT"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Linux System Administrator's Guide: </TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x2943.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 14. Finding Help</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN2981"
></A
>14.2. IRC</H1
><P
>IRC (Internet Relay Chat) is not covered in the Eric Raymond
document, but IRC can also be an excellent way of finding the answers you need.
However it does require some practice in asking questions in the right way.
Most IRC networks have busy #linux channels and if the answer to your question
is contained in the manpages, or in the HOWTOs then expect to be told
to go read them. The rule about typing in clear and grammatical English
still applies.</P
><P
>Most of what has been said about newsgroups and mailing lists
is still relevant for IRC, with a the following additions</P
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN2985"
></A
>14.2.1. Colours</H2
><P
>Do not use colours, bold, underline or strange (non ASCII)
characters. This breaks some older terminals and is just plain ugly
to look at. If you arrive in a channel and start spewing colour or bold
then expect to be kicked out.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN2988"
></A
>14.2.2. Be Polite</H2
><P
>Remember you are not entitled to an answer. If you ask the
question in the right way then you will probably get one, but you have
no right to get one. The people in Linux IRC channels are all there
on their own time, nobody is paying them, especially not you.</P
><P
>Be polite. Treat others as you would like to be
treated. If you think people are not being polite to you then don't
start calling them names or getting annoyed, become even politer.
This makes them look foolish rather than dragging you down to their level.</P
><P
>Don't go slapping anyone with large trouts. Would you believe
this has been done before once or twice? And that we it wasn't
funny the first time?</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN2993"
></A
>14.2.3. Type Properly, in English</H2
><P
>Most #linux channels are English channels. Speak English whilst
in them. Most of the larger IRC networks also have #linux channel in
other languages, for example the French language channel might be
called #linuxfr, the Spanish one might be #linuxes or #linuxlatino.
If you can't find the right channel then asking in the main #linux
channel (preferably in English) should help you find the one you are looking
for.</P
><P
>Do not type like a <SPAN
CLASS="QUOTE"
>"1337 H4X0R d00d!!!"</SPAN
>. Even if other people
are. It looks silly and thereby makes you look silly. At best you
will only look like an idiot, at worst you will be derided then kicked
out.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN2998"
></A
>14.2.4. Port scanning</H2
><P
>Never <EM
>ever</EM
> ask anyone to port scan you, or
try to <SPAN
CLASS="QUOTE"
>"hack"</SPAN
> you. This is inviolable. There is no way of knowing that
you are who you say you are, or that the IP that you are connected
from belongs to you. Don't put people in the position where they have to
say no to a request like this.</P
><P
><EM
>Don't ever port scan anyone</EM
>, even if they
ask you to. You have no way to tell
that they are who they say they are or that the IP they are connected
from is their own IP. In some jurisdictions port scanning may be illegal
and it is certainly against the Terms of Service of most ISPs.
Most people log TCP connections, they will notice they are being
scanned. Most people <EM
>will</EM
> report you to your ISP
for this (it is trivial to find out who that is).</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3006"
></A
>14.2.5. Keep it in the Channel</H2
><P
>Don't /msg anyone unless they ask you to. It diminishes the
usefulness of the channel and some people just prefer that
you not do it.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3009"
></A
>14.2.6. Stay On Topic</H2
><P
>Stay on topic. The channel is a <SPAN
CLASS="QUOTE"
>"Linux"</SPAN
> channel, not a <SPAN
CLASS="QUOTE"
>"What
Uncle Bob Got Up To Last Weekend"</SPAN
> channel. Even if you see other
people being off topic, this does not mean that you should be. They
are probably channel regulars and different conventions apply to
them.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3014"
></A
>14.2.7. CTCPs</H2
><P
>If you are thinking of mass CTCP
<A
NAME="AEN3017"
HREF="#FTN.AEN3017"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
>
pinging the channel or CTCP
version or CTCP anything, then think again. It is liable to get you
kicked out very quickly.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3019"
></A
>14.2.8. Hacking, Cracking, Phreaking, Warezing</H2
><P
>Don't ask about exploits, unless you are looking for a further
way to be unceremoniously kicked out.</P
><P
>Don't be in hacker/cracker/phreaker/warezer channels whilst in a
#linux channel. For some reason the people in charge of #linux
channels seem to hate people who like causing destruction to people's machines
or who like to steal software. Can't imagine why.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3023"
></A
>14.2.9. Round Up</H2
><P
>Apologies if that seems like a lot of DON'Ts, and very few DOs.
The DOs were already pretty much covered in the section on newsgroups and
mailing lists.</P
><P
>Probably the best thing you can do is to go into a #linux
channel, sit there and watch, getting the feel for a half hour before
you say anything. This can help you to recognise the correct tone you
should be using.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN3027"
></A
>14.2.10. Further Reading</H2
><P
>There are excellent FAQs about how to get the most of IRC #linux
channels. Most #linux channels have an FAQ and/or set or channel
rules. How to find this will usually be in the channel topic (which you can
see at any time using the <B
CLASS="command"
>/topic</B
> command. Make sure
you read the rules if there are any and follow them. One fairly generic
set of rules and advice is the <SPAN
CLASS="QUOTE"
>"Undernet #linux FAQ"</SPAN
> which can be found
at <A
HREF="http://linuxfaq.quartz.net.nz"
TARGET="_top"
>http://linuxfaq.quartz.net.nz
</A
>.</P
></DIV
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN3017"
HREF="x2981.html#AEN3017"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>If you are not familiar with IRC, CTCP stands
for Client To Client Protocol. It is a method whereby you can
find out things about other peoples' clients. See the
documentation for your IRC client for more
details</P
></TD
></TR
></TABLE
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="x2943.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Newsgroups and Mailing Lists</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c2938.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>GNU Free Documentation License</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|
