From: Rackmount <HAL9000@USS_Discovery.gov>
Subject: A breif introduction to the #Linux Channel
Date: 16 Feb 1998 08:44:00 -0700
-- A brief introduction to the #Linux Channel --
NOTE: For more information regarding getting help on using Linux via the
#Linux IRC channel, please visit http://www.linux-efnet.ml.org, as
this info is but merely a very brief "just so you know" document.
At the address given, you can get a very detailed description of
the channel, and much more useful information directly from those
who are responsible for #Linux's creation.
The #Linux channel, in essence, is a place where people can come to get
help with their systems when they decide to stop working properly, or
at all. Users can join, ask a question, and get several answers from
other expert users. This reduces downtime dramatically, and because
of this, #Linux is getting busier, and busier all the time. So, in order
to better help yourself, and others, I would ask that anyone who uses the
#Linux channel to please follow these guidelines:
1.) #Linux has been created to allow you to get help quickly. Don't ask
permission to ask a question... just ask it. If you ask a direct
question, you will get a direct answer. Saying, "my linux don't
work, HALP!!!!", will only get you a response like, "Ask a real
question", or no response at all. For example, questions like:
<somenick> I need help... someone /msg me PLZ!
<somenick> My Linux won't boot!... What's wrong?
are simply not acceptable questions, and will probably not get any
responses from anyone. A proper question would be something like:
<somenick> When I try to mount my HD (/dev/hda3), I get a message telling
me it's not a block device... what does this mean?
<somenick> My soundcard seems to have a great deal of background noise...
what can I do to get rid of the noise?
<somenick> What does <error message> mean?...
These are perfectly valid questions, and often get answered quickly.
Bascially, any questions that don't provide any useful info in them,
don't get answered, whereas questions with descriptive info in them,
do.
2.) Please don't barge into the channel with a lot of anti-Microsoft
sentiments, or propaganda. Since all we really want to do is help
out new users, we really don't care about "how much WindowsNT sucks",
or "how much better Linux is than WindowsXX"... these subjects mean
little or nothing to most of the users on #Linux. Lets leave these
types of discussions to the USENET *.advocacy newsgroups.
3.) Please do not use bold, reversed, or color text on the channel, as
this is very distracting, and makes it difficult for the helpers, and
helpees on the channel to get information. Anyone who uses such ANSI
codes on the channel, will get kicked by one of the bots, or by one
of the channel operators, and if they keep it up, they will most
likely get banned by said ChanOps. Be a sport, and stick to plain
text like everyone else. ;)
4.) Probably the most important thing you can do to get help, is to read
any and all documentation. One of the more annoying occurrences
on #Linux, is when someone asks a question like "how do I set up my
PPP under Linux?", or "How do I recompile my kernel?" These types of
questions will only get you this response... "RTFM!", or "Read The
Fscking Manual!" This may seem snide, and uncalled for, but the
reason why such questions get such responses, is that most people who
ask such questions are just being lazy, and don't want to have to
read the (admittedly lengthy (though very useful)) documentation.
Laziness will get you nothing. If you have read the docs, and you
just don't understand them, then you will be better off posting to
comp.os.linux.setup(.*), as USENETters can give you more details on
things which some documentation may not help you to understand. If
you have a question about something that is not quite #Linux
oriented, you will most likely be directed to another channel, or
given an URL.
Also keep in mind, that not all questions can be answered in #Linux.
Your problem may be something new, that nobody has heard of, or there
may not be someone on the channel with the know-how to help you out
at the moment. If nobody answers your question, then try back later.
Persistence, melded with patience, and good netiquette, DOES pay off
in #Linux.
5.) The absolute most annoying thing a user can do on #Linux, is to try
to show how ELeeT he/she is, by trying to impress others with their
HaXOr jargon. Warezers are NOT welcome on Linux, so please don't
come into #Linux asking for WaREz, SHeLLz, gAMeZ, NuKEz, or anything
else that contributes to illegal activity. The ChanOps do not,
and will not pH33r anyone (especially not someone who comes in with
an attitude, and talks a lot of trash). The only thing that talking
HaXOrish will get you is a permanent ban from the channel, and the
closest thing you will get to a title is "LUSER ELITE".
NEVER use, or threaten to use land, teardrop, bonk, CTCP floods, or
anything else on others. Such things will also get you banned, and
your ISP will be notified of your action(s). Also, nobody on #Linux
is going to 'nuke' someone else for you. Asking such a favor also
results in a ban.
Please don't use nicks like <PhUCkfACe>, <K|LL3r>, <()B3|isK>, etc.
These nicks are not only offensive/annoying/difficult to type
quickly, but they just look plain idiotic. Basically, what I am
trying to convey here is that being a HaXoR 3LeeT on #Linux impresses
no one at all, and will most likely get you /ignore'd by the
other users, and /kickban'd by the Ops.
6.) Try to talk in the channel at all times. It is considered rude to
/msg a user with whom you are not familiar, or who is not familiar
with you. Also, by /msg'ing, you are only hurting yourself, as only
one user can see what your question is. If you talk in the channel,
you'll get much more help.
7.) Finally, make an effort to be polite. Sometimes, tempers flare on
#Linux, and because of that, some people get turned off to the whole
IRC experience. Don't let some jerk, who is probably 4000 miles
away, ruin your IRC session. If someone cops an attitude, then just
use /ignore <nick> all, and you won't have to listen to them. You
may find later on that the person in question is actually pretty
cool, and was just having a bad day. :)
Rarely is a ChanOp on #Linux rude to someone, and if they are, its
because that person is doing something VERY annoying on the channel.
If an Op addresses you, and sternly tells you to do something, do
it, and all will be well. It's nothing personal, mind you. They are
maintaining #Linux out of sheer voluntary effort, and ask for very
little in return. Try to show the Ops courtesy, and they shall do
the same for you. After all, the best way we can push the UNIX
front, is by helping each other out, right? :)
So, if your system is goofin' up, and you need a hand, come on in,
and let us take a whack at it! :)
Stephen Edwards -- a.k.a. <Rackmount> on IRC
--
QUOTE: <No words of wisdom for today, kiddies.>
Stephen S. Edwards II -- r a k m o u n t @ p r i m e n e t . c o m
Homepage: http://www.primenet.com/~rakmount (under construction)
Pub FTP: ftp://ftp.primenet.com/users/p/rakmount