350 lines
8.0 KiB
HTML
350 lines
8.0 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>IRC</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux System Administrators Guide"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="Finding Help"
|
|
HREF="finding-help.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Newsgroups and Mailing Lists"
|
|
HREF="newsgroups-mailling-lists.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="GNU Free Documentation License"
|
|
HREF="gfdl1.2.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"
|
|
>Linux System Administrators Guide: </TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="newsgroups-mailling-lists.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 18. Finding Help</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="gfdl1.2.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="IRC"
|
|
></A
|
|
>18.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 man pages, 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="COLOURS"
|
|
></A
|
|
>18.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="BE-POLITE"
|
|
></A
|
|
>18.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="TYPE-PROPERLY"
|
|
></A
|
|
>18.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 ``1337 H4X0R d00d!!!''. 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="PORT-SCANNING"
|
|
></A
|
|
>18.2.4. Port scanning</H2
|
|
><P
|
|
>Never <EM
|
|
>ever</EM
|
|
> ask anyone to port scan you, or
|
|
try to ``hack'' 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="KEEP-IN-CHANNEL"
|
|
></A
|
|
>18.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="AEN4751"
|
|
></A
|
|
>18.2.6. Stay On Topic</H2
|
|
><P
|
|
>Stay on topic. The channel is a ``Linux'' channel, not a ``What
|
|
Uncle Bob Got Up To Last Weekend'' 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="MASS-CTCP"
|
|
></A
|
|
>18.2.7. CTCPs</H2
|
|
><P
|
|
>If you are thinking of mass CTCP pinging the channel or CTCP
|
|
version or CTCP anything, then think again. It is liable to get you
|
|
kicked out very quickly.</P
|
|
><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
|
|
for more details.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="HACKING"
|
|
></A
|
|
>18.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="ROUND-UP"
|
|
></A
|
|
>18.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 recognize the correct tone you
|
|
should be using.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="FURTHER-READING"
|
|
></A
|
|
>18.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 ``Undernet #linux FAQ'' which can be found
|
|
at <A
|
|
HREF="http://linuxfaq.quartz.net.nz"
|
|
TARGET="_top"
|
|
>http://linuxfaq.quartz.net.nz
|
|
</A
|
|
>.</P
|
|
></DIV
|
|
></DIV
|
|
><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="newsgroups-mailling-lists.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="gfdl1.2.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="finding-help.html"
|
|
ACCESSKEY="U"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>GNU Free Documentation License</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |