new entry

This commit is contained in:
gferg 2000-12-23 00:44:04 +00:00
parent 7f456a625d
commit 7de7fcc32e
1 changed files with 525 additions and 0 deletions

525
LDP/howto/docbook/IRC.sgml Normal file
View File

@ -0,0 +1,525 @@
<!doctype article public "-//OASIS//DTD DocBook V4.1//EN">
<article id="index">
<articleinfo>
<title>Linux IRC mini-HOWTO</title>
<pubdate>v0.05 20 December, 2000</pubdate>
<author><firstname>Frédéric</firstname><othername>L. W.</othername><surname>Meunier</surname></author>
<authorinitials>fredlwm</authorinitials>
<address><email>linuxdoc@pervalidus.net</email></address>
<publisher><publishername>The Linux Documentation Project</publishername></publisher>
<revhistory>
<revision>
<revnumber>0.05</revnumber>
<date>2000-12-20</date>
<authorinitials>fredlwm</authorinitials>
<revremark>
Initial revision.
</revremark>
</revision>
<abstract><para>This document aims to describe the basics of IRC and respective applications for Linux.</para></abstract>
</articleinfo>
<sect1 id="intro"><title>Introduction</title>
<para>This document is still WIP, and should be treated as such. I'll do my best to keep it updated and accurate.</para>
<para>The following bibles shouldn't be ignored:</para>
<itemizedlist><listitem><para>
RFC1459 by Jarkko Oikarinen and Darren Reed was the first about the Internet Relay Chat Protocol.
It can be found at <ulink url="ftp://ftp.isi.edu/in-notes/rfc1459.txt">ftp://ftp.isi.edu/in-notes/rfc1459.txt</ulink>.
</para></listitem>
<listitem><para>
RFC2811 by C. Kalt updates RFC1459 and describes the Channel Management of the Internet Relay Chat.
It can be found at <ulink url="ftp://ftp.isi.edu/in-notes/rfc2811.txt">ftp://ftp.isi.edu/in-notes/rfc2811.txt</ulink>.
</para></listitem>
<listitem><para>
RFC2812 by C. Kalt updates RFC1459 and describes the Client Protocol of the Internet Relay Chat.
It can be found at <ulink url="ftp://ftp.isi.edu/in-notes/rfc2812.txt">ftp://ftp.isi.edu/in-notes/rfc2812.txt</ulink>.
</para></listitem>
<listitem><para>
RFC2813 by C. Kalt updates RFC1459 and describes the Server Protocol of the Internet Relay Chat.
It can be found at <ulink url="ftp://ftp.isi.edu/in-notes/rfc2813.txt">ftp://ftp.isi.edu/in-notes/rfc2813.txt</ulink>.
</para></listitem></itemizedlist>
<para>Also be sure to check the following sites:</para>
<para><ulink url="http://www.irchelp.org/">http://www.irchelp.org/</ulink>.</para>
<sect2><title>Objectives</title>
<para>Among others, the objectives of this mini-HOWTO are:</para>
<itemizedlist><listitem><para>
Link important resources about IRC;
</para></listitem>
<listitem><para>
Avoid common misuses of IRC by writing an IRC Etiquette;
</para></listitem>
<listitem><para>
List popular clients, servers, bots, and bouncers, along with their
maintainers, #channel, small description, download location, homepage,
and hints;
</para></listitem>
<listitem><para>
List IRC tools available in the latest release of all major distributions.
</para></listitem></itemizedlist></sect2>
<sect2><title>Miscellaneous</title>
<para>The latest version of this document is available at
<ulink url="http://www.pervalidus.net/docs/IRC-mini-HOWTO/">http://www.pervalidus.net/docs/IRC-mini-HOWTO/</ulink>.</para>
<para>A WIP of the next draft may be available at
<ulink url="http://www.pervalidus.net/docs/IRC-mini-HOWTO-WIP">http://www.pervalidus.net/docs/IRC-mini-HOWTO/WIP/</ulink>.</para>
<para>You can e-mail me (in English, French, or Portuguese) with
suggestions about the mini-HOWTO. I know this is far from finished, but
hope you find it useful. Just don't ask me to add your application or
site. Most likely I won't. Also don't ask for technical support. I have
no time to help everyone.</para>
<para>BTW, someone to work on the protocol and server sides (if needed) would be very welcome to join the project.</para>
<para><ulink url="mailto:linuxdoc@pervalidus.net">Frédéric L. W. Meunier</ulink> - fredlwm at BRASnet and OPN.</para></sect2>
<sect2><title>Translations</title>
<para>Proposed translations will be linked here. Although I can write in
Brazilian Portuguese and French, I'm not going to translate this
document in the near future, so feel free to make
them.</para></sect2></sect1>
<sect1 id="about"><title>About IRC</title>
<para>Excerpt from RFC2810:</para>
<para>The IRC (Internet Relay Chat) protocol is for use with text based
conferencing. It has been developed since 1989 when it was originally
implemented as a mean for users on a BBS to chat amongst
themselves.</para>
<para>First formally documented in May 1993 by RFC 1459 [IRC], the
protocol has kept evolving.</para>
<para>The IRC Protocol is based on the client-server model, and is well
suited to running on many machines in a distributed fashion. A typical
setup involves a single process (the server) forming a central point for
clients (or other servers) to connect to, performing the required
message delivery/multiplexing and other functions.</para>
<para>This distributed model, which requires each server to have a copy
of the global state information, is still the most flagrant problem of
the protocol as it is a serious handicap, which limits the maximum size
a network can reach. If the existing networks have been able keep
growing at an incredible pace, we must thank hardware manufacturers for
giving us ever more powerful systems.</para></sect1>
<sect1 id="beginners"><title>Beginner's guide on using IRC</title>
<para>The standard IRC client is the original ircII client. It's part of most Linux distributions.</para>
<sect2><title>Running the ircII program</title>
<para>It's easy to use ircII. Let's say you want to connect to irc.openprojects.net with the nick mini-HOWTO.</para>
<para>At the command line, type:</para>
<para>$ irc mini-HOWTO irc.openprojects.net</para>
<para>You can also export variables so you won't need to use them at the command line:</para>
<para>$ export IRCNICK=mini-HOWTO IRCSERVER=irc.openprojects.net</para>
<para>Add them to your shell profile (e.g. ~/.bash_profile or ~/.zprofile) when you're done.</para>
<para>Other common variables are IRCNAME and IRCUSER, to respectively
set the 'ircname' part of a /whois and username as seen at the first
line 'mini-HOWTO is ~username@hostname (IRCNAME)'. Keep in mind that
IRCUSER won't work if you run an ident daemon (default on most
distributions). If you still need to change your username (not
recommended, and I hope you're not using IRC logged as root!), install
oidentd from <ULINK
URL="http://ojnk.sourceforge.net/">http://ojnk.sourceforge.net/</ulink>,
create /etc/identd.spoof with a list of users allowed to spoof their
ident, and ~/.ispoof with their reply (e.g. reply). Finally run
'/usr/local/sbin/oidentd -g nobody -N -s -u nobody'. Add this to your
startup scripts (e.g. /etc/rc.d/rc.local) when you're done.</para>
<para>If not set, IRCNICK, IRCUSER, and IRCNAME will be retrieved from /etc/passwd .</para></sect2>
<sect2><title>Commands</title>
<para>Use /help to get a list on all available commands (/help help is a good start). Replace <emphasis>nick</emphasis> by any IRCNICK.</para>
<itemizedlist><listitem><para>
First, /set NOVICE off
</para></listitem>
<listitem><para>
/nick Linus changes your IRCNICK to Linus
</para></listitem>
<listitem><para>
/set realname Linus Torvalds changes your IRCNAME to Linus Torvalds (doesn't change until you use /server IRCSERVER)
</para></listitem>
<listitem><para>
/j #Linux joins channel #Linux
</para></listitem>
<listitem><para>
/j #Linux1 joins channel #Linux1
</para></listitem>
<listitem><para>
/j #Linux changes the active current channel to #Linux
</para></listitem>
<listitem><para>
/msg <emphasis>nick</emphasis> Hi. sends a private message to <emphasis>nick</emphasis> containing 'Hi.'
</para></listitem>
<listitem><para>
/notice <emphasis>nick</emphasis> (or #Linux) Hi. sends a notice to <emphasis>nick</emphasis> (or #Linux) containing 'Hi.'
</para></listitem>
<listitem><para>
/query <emphasis>nick</emphasis> starts a private conversation with <emphasis>nick</emphasis>. /query ends the private conversation
</para></listitem>
<listitem><para>
/me loves Linux. sends an action to the current channel or query containing 'Linus loves Linux.'
</para></listitem>
<listitem><para>
/dcc chat <emphasis>nick</emphasis> starts a chat with <emphasis>nick</emphasis>. Use /msg =<emphasis>nick</emphasis> (notice the '=') to send messages over the chat
</para></listitem>
<listitem><para>
/dcc send <emphasis>nick</emphasis> /etc/HOSTNAME sends the given file to <emphasis>nick</emphasis>
</para></listitem>
<listitem><para>
/dcc get <emphasis>nick</emphasis> receives the file offered by <emphasis>nick</emphasis>
</para></listitem>
<listitem><para>
/part leaves the active current channel
</para></listitem>
<listitem><para>
/part #Linux1 leaves channel #Linux1
</para></listitem>
<listitem><para>
/discon disconnects from current IRCSERVER
</para></listitem>
<listitem><para>
/server irc.dal.net connects to IRCSERVER irc.dal.net
</para></listitem>
<listitem><para>
/quit Bye. quits your IRC session with a reason 'Bye.'
</para></listitem></itemizedlist></sect2>
<sect2><title>IRC Etiquette</title>
<para>WARNING WARNING WARNING WARNING WARNING</para>
<itemizedlist><listitem><para>
Never use IRC logged as root or any user with excessive privileges. Bad
things may happen sooner or later. You were warned. It's safer if you
create 2 users, one of them to only use IRC.
</para></listitem></itemizedlist>
<para>$ man adduser</para>
<para>On Linux channels you shouldn't:</para>
<itemizedlist><listitem><para>
Act as an idiot. If you want to be respected, then first respect each other.
</para></listitem>
<listitem><para>
Use colors (^C). Most Linux users don't tolerate such mIRC crazes, and
ircII doesn't really support them. The same should apply for ANSI.
</para></listitem>
<listitem><para>
Use full CAPS, bold (^B), reverse (^V), underline (^_), blink (^K), and
bell (^G). The first 4 are here to emphasize words, not the whole text.
The last 2 are just very annoying.
</para></listitem>
<listitem><para>
Ask if you can ask a question. Just ask, but first read all documentation available on the subject.
Start looking at <ulink url="file:/usr/doc/">/usr/doc/</ulink> , otherwise go to
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink> or
<ulink url="http://www.ibiblio.org/pub/Linux/docs/">http://www.ibiblio.org/pub/Linux/docs/</ulink>.
And don't repeat your question immediately. Wait at least 10 minutes. If you don't get any answer
it's because nobody knows or wants to help. Respect their choice, they're not your personal
assistant. Also never send mass private messages. It's like SPAM.
</para></listitem></itemizedlist></sect2></sect1>
<sect1 id="console"><title>Console IRC Clients</title>
<sect2><title>ircII</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="mailto:ircii@eterna.com.au">ircII project</ulink>
<emphasis>IRC Channel:</emphasis> #ircii (official channel?) on <ulink url="http://www.efnet.org/servers.html">EFNet</ulink></para>
<para>Originally written by Michael Sandrof, ircII comes with most Linux
distributions. It uses termcap and shouldn't be a choice for most users,
but is a standard. Mathusalem and other gurus will use it. Less ventured
will regret to have it installed.</para>
<para>You can get the latest version of ircII from <ulink url="ftp://ircftp.au.eterna.com.au/pub/ircII/">ftp://ircftp.au.eterna.com.au/pub/ircII/</ulink>.
Homepage at <ulink url="http://www.eterna.com.au/ircii/">http://www.eterna.com.au/ircii/</ulink>.</para></sect2>
<sect2><title>EPIC</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="mailto:ircii-epic@concentric.net">EPIC Software Labs</ulink>
<emphasis>IRC Channel:</emphasis> #epic on EFNet</para>
<para>Based on ircII, EPIC (Enhanced Programmable ircII Client) is meant
for real scripters and users searching freedom. When you start it for
the first time you'll notice that you should really learn the basics of
scripting.</para>
<para>You can get the latest version of EPIC from <ulink url="ftp://ftp.epicsol.org/pub/epic/">ftp://ftp.epicsol.org/pub/epic/</ulink>.
Homepage at <ulink url="http://www.epicsol.org/">http://www.epicsol.org/</ulink>.</para></sect2>
<sect2><title>BitchX</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="mailto:edwards@bitchx.dimension6.com">Colten Edwards</ulink>
<emphasis>IRC Channel:</emphasis> #bitchx on EFNet</para>
<para>Based on ircII and EPIC, BitchX could be compared to the Pine MUA.
Bloatware (doesn't mean you shouldn't use it) and widely used. The
choice for users that want a client with built-in facilities. It can be
built with the GNOME libraries by using the configure option --with-gtk.
Don't be surprised if all you get is a XTerm-BitchX instead.</para>
<para>You can get the latest version of BitchX from <ulink url="ftp://ftp.bitchx.com/pub/BitchX/source/">ftp://ftp.bitchx.com/pub/BitchX/source/</ulink>.
Homepage at <ulink url="http://www.bitchx.com/">http://www.bitchx.com/</ulink>.
Homepage of gtkBitchX at <ulink url="http://www.bitchx.org/gtk/">http://www.bitchx.org/gtk/</ulink>.</para></sect2>
<sect2><title>irssi</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="tss@iki.fi">Timo Sirainen</ulink>
<emphasis>IRC Channel:</emphasis> #irssi on <ulink url="http://openprojects.nu/services/irc.html">OPN</ulink> and <ulink url="http://www.ircnet.org/">IRCnet</ulink></para>
<para>Timo released yagIRC ~3 years ago. It was a GUI client using the
GTK+ toolkit. The army called on him, and the new maintainers wouldn't
do the job. yagIRC passed away and he started irssi as a replacement. It
used GTK+. GNOME and curses versions would appear later. As of 0.7.90
it's only a text client, a very good one. Supports Perl
scripting.</para>
<para>You can get the latest version of irssi from <ulink url="http://irssi.org/?page=download">http://irssi.org/?page=download</ulink>.
Homepage at <ulink url="http://irssi.org/">http://irssi.org/</ulink>.</para></sect2></sect1>
<sect1 id="xfree"><title>X Window IRC Clients</title>
<sect2><title>Zircon</title>
<para><emphasis>Maintainer:</emphasis> Lindsay F. Marshall <ulink url="Lindsay.Marshall@ncl.ac.uk">Lindsay F. Marshall</ulink>
<emphasis>IRC Channel:</emphasis> None?</para>
<para>Written in Tcl/Tk, uses the native network communications of Tcl.</para>
<para>You can get the latest version of Zircon from <ulink url="ftp://catless.ncl.ac.uk/pub/">ftp://catless.ncl.ac.uk/pub/</ulink>.
Homepage at <ulink url="http://catless.ncl.ac.uk/Programs/Zircon/">http://catless.ncl.ac.uk/Programs/Zircon/</ulink>.</para></sect2>
<sect2><title>xIrc</title>
<para><emphasis>Maintainer:</emphasis> Robert Borrell <ulink url="borrell@pobox.com">Robert Borrell</ulink>
<emphasis>IRC Channel:</emphasis> None?</para>
<para>Using the Qt toolkit, xIrc is less featured than KVIrc. As an advantage, it's faster.</para>
<para>You can get the latest version of xIrc from <ulink url="http://www.linuxlots.com/~xirc/download.html">http://www.linuxlots.com/~xirc/download.html</ulink>.
Homepage at <ulink url="http://www.linuxlots.com/~xirc/">http://www.linuxlots.com/~xirc/</ulink>.</para></sect2>
<sect2><title>KVIrc</title>
<para><emphasis>Maintainer:</emphasis> Szymon Stefanek <ulink url="stefanek@tin.it">Szymon Stefanek</ulink>
<emphasis>IRC Channel:</emphasis> #kvirc on OPN</para>
<para>Also written with the Qt toolkit, KVIrc is a beast. Supports DCC Voice, built-in scripting language, and plugins.</para>
<para>You can get the latest version of KVIrc from <ulink url="http://www.kvirc.net/download.html">http://www.kvirc.net/download.html</ulink>.
Homepage at <ulink url="http://www.kvirc.net/">http://www.kvirc.net/</ulink>.</para></sect2>
<sect2><title>X-Chat</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="zed@linux.com">Peter Zelezny</ulink>
<emphasis>IRC Channel:</emphasis> #linux on <ulink url="http://www.chatjunkies.org/servers.html">ChatJunkies</ulink></para>
<para>Using the GTK+ toolkit and additionaly GNOME, supports Perl and Python scripting.</para>
<para>You can get the latest version of X-Chat from <ulink url="http://xchat.org/download.html">http://xchat.org/download.html</ulink>.
Homepage at <ulink url="http://xchat.org/">http://xchat.org/</ulink>.</para></sect2></sect1>
<sect1 id="servers"><title>IRC Servers</title>
<sect2><title>IRCD</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="ircd-dev@irc.org">ircd developers</ulink>
<emphasis>IRC Channel:</emphasis> #ircd on IRCnet</para>
<para>The original IRC daemon, mainly used by IRCnet.</para>
<para>You can get the latest version of IRCD from <ulink url="ftp://ftp.irc.org/irc/server/">ftp://ftp.irc.org/irc/server/</ulink>.
Homepage at <ulink url="http://www.irc.org/">http://www.irc.org/</ulink>.</para></sect2>
<sect2><title>IRCD-Hybrid</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="ircd-hybrid@the-project.org">ircd-hybrid@the-project.org</ulink>
<emphasis>IRC Channel:</emphasis> None?</para>
<para>Mainly used by EFNet.</para>
<para>You can get the latest version of IRCD-Hybrid from <ulink url="ftp://ftp.blackened.com/pub/irc/hybrid/">ftp://ftp.blackened.com/pub/irc/hybrid/</ulink>.
Homepage at <ulink url="http://www.ircd-hybrid.net/">http://www.ircd-hybrid.net/</ulink>.</para></sect2>
<sect2><title>ircu</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="coder-com@undernet.org">Undernet Coder Committee</ulink>
<emphasis>IRC Channel:</emphasis> #ircu on <ulink url="http://www.undernet.org/servers.shtml">Undernet</ulink></para>
<para>Mainly used by Undernet.</para>
<para>You can get the latest version of ircu from <ulink url="ftp://ftp.coder-com.undernet.org/ircu/">ftp://ftp.coder-com.undernet.org/ircu/</ulink>.
Homepage at <ulink url="http://coder-com.undernet.org/">http://coder-com.undernet.org/</ulink>.</para></sect2>
<sect2><title>Bahamut</title>
<para><emphasis>Maintainer:</emphasis> DALnet Coding Team <ulink url="bahamut@bahamut.net">DALnet Coding Team</ulink>
<emphasis>IRC Channel:</emphasis> #bahamut on <ulink url="http://www.dal.net/servers/">DALnet</ulink></para>
<para>Based on DreamForge and Hybrid, Bahamut is the DALnet server.</para>
<para>You can get the latest version of Bahamut from <ulink url="http://www.bahamut.net/?dir=4">http://www.bahamut.net/?dir=4</ulink>.
Homepage at <ulink url="http://www.bahamut.net/">http://www.bahamut.net/</ulink>.</para></sect2></sect1>
<sect1 id="bots"><title>IRC Bots</title>
<sect2><title>eggdrop</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="eggdev@eggheads.org">eggdev@eggheads.org</ulink>
<emphasis>IRC Channel:</emphasis> #eggdrop on Undernet</para>
<para>eggdrop is the most known Tcl enabled application on the Net. It's
a channel robot for IRC that can be tailored to any situation.</para>
<para>You can get the latest version of eggdrop from <ulink url="ftp://ftp.eggheads.org/pub/eggdrop/source/">ftp://ftp.eggheads.org/pub/eggdrop/source/</ulink>.
Homepage at <ulink url="http://www.eggheads.org/">http://www.eggheads.org/</ulink>.</para></sect2></sect1>
<sect1 id="bouncers"><title>IRC Bouncers (IRC Proxy)</title>
<sect2><title>bnc</title>
<para><emphasis>Maintainer:</emphasis> None?
<emphasis>IRC Channel:</emphasis> None?</para>
<para>bnc is the original bouncer.</para>
<para>You can get the latest version of bnc from <ulink url="http://www.linuxberg.com/files/files/console/servers/bnc2.6.4.tar.gz">LinuxBerg</ulink>.</para></sect2>
<sect2><title>muh</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="zap@riot.org">Sebastian Kienzl</ulink>
<emphasis>IRC Channel:</emphasis> None?</para>
<para>muh is a smart and versatile irc-bouncing tool that will also go
on IRC as soon as it's launched, guarding or attempting to get your
nick.</para>
<para>You can get the latest version of muh from <ulink url="http://mind.riot.org/muh/download.rt">http://mind.riot.org/muh/download.rt</ulink>.
Homepage at <ulink url="http://mind.riot.org/muh/">http://mind.riot.org/muh/</ulink>.</para></sect2>
<sect2><title>ezbounce</title>
<para><emphasis>Maintainer:</emphasis> <ulink url="druglord@freelsd.org">Murat Deligönül</ulink>
<emphasis>IRC Channel:</emphasis> None?</para>
<para>ezbounce's basic features include password protection, remote
administration, logging and listening on multiple ports.</para>
<para>You can get the latest version of ezbounce from his <ulink url="http://druglord.freelsd.org/ezbounce/">Homepage</ulink>.</para></sect2></sect1>
<sect1 id="installation"><title>Installation</title>
<sect2><title>Clients</title>
<para>All popular clients use <emphasis>GNU</emphasis> autoconf and
<emphasis>GNU</emphasis> automake, thus come with a configure script.
Read the installation instructions after you unpack the sources. Be sure
you have the required libraries in order to build. Doing cd
sources;mkdir objdir;cd objdir; ../configure
--help;../configure <emphasis>your_options_here</emphasis>;make;make install (or make
install_strip) &gt; ~/sources_install.log is the right procedure. Also
note that for ircII, EPIC, and BitchX you should really edit
include/config.h to suit your needs.</para></sect2>
<sect2><title>Servers</title>
<para>Do you really need help to set up a server?</para>
<para>~$ vim ircd.conf</para></sect2></sect1>
<sect1 id="included"><title>But what's already included in my distribution?</title>
<sect2><title>Debian</title>
<para>Debian includes too many IRC tools to list. You can find them at the following places:</para>
<itemizedlist><listitem><para>
Debian <ulink url="ftp://ftp.debian.org/debian/dists/stable/main/binary-i386/net/">stable</ulink>.
</para></listitem>
<listitem><para>
Debian <ulink url="ftp://ftp.debian.org/debian/dists/unstable/main/binary-i386/net/">unstable</ulink> (didn't receive so much testing).
</para></listitem>
<listitem><para>
Also be sure to check the <ulink url="ftp://ftp.debian.org/debian/dists/proposed-updates/">proposed updates</ulink>. It may have IRC clients as well.
</para></listitem>
<listitem><para>
Debian non-free (applications with a restrictive license) contains <ulink url="ftp://ftp.debian.org/debian/dists/stable/non-free/binary-i386/net/circus_0.43-1.deb">cIRCus</ulink>.
</para></listitem></itemizedlist></sect2>
<sect2><title>RedHat</title>
<para>RedHat 7.0 includes the following clients:</para>
<itemizedlist><listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/i386/en/RedHat/RPMS/ircii-4.4M-4.i386.rpm">ircII 4.4M</ulink>.
</para></listitem>
<listitem><para>
KSirc from <ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/i386/en/RedHat/RPMS/kdenetwork-1.1.2-17.i386.rpm">KDE Network 1.1.2</ulink>.
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/i386/en/RedHat/RPMS/xchat-1.4.2-6.i386.rpm">X-Chat 1.4.2</ulink>.
</para></listitem></itemizedlist>
<itemizedlist><listitem><para>
RedHat Powertools (what's worth but they don't want? to include or can't) 7.0 includes the following clients:
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/powertools/i386/RedHat/RPMS/BitchX-1.0c16-4.i386.rpm">BitchX</ulink> and <ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/powertools/i386/RedHat/RPMS/gtkBitchX-1.0c16-4.i386.rpm">gtkBitchX</ulink> 1.0c16. Later updated to <ulink url="ftp://updates.redhat.com/powertools/7.0/i386/BitchX-1.0c17-4.i386.rpm"> BitchX</ulink> and <ulink url="ftp://updates.redhat.com/powertools/7.0/i386/gtkBitchX-1.0c17-4.i386.rpm">gtkBitchX</ulink> 1.0c17.
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/powertools/i386/RedHat/RPMS/epic-4_2000-5.i386.rpm">EPIC4-2000</ulink>.
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/powertools/i386/RedHat/RPMS/kvirc-2.0.0-6.i386.rpm">KVIrc 2.0.0</ulink>.
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.0/powertools/i386/RedHat/RPMS/tkirc-1.202-8.noarch.rpm">tkIRC 1.202</ulink>.
</para></listitem></itemizedlist></sect2>
<sect2><title>Slackware</title>
<para>Slackware 7.1 includes the following clients:</para>
<itemizedlist><listitem><para>
KSirc from <ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-7.1/slakware/kde1/ksupport.tgz">KDE Network 1.1.2</ulink>.
</para></listitem>
<listitem><para>
<ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-7.1/slakware/gtk1/xchat.tgz">X-Chat 1.2.1</ulink>.
Later updated to <ulink url="ftp:ftp.slackware.com/pub/slackware/slackware-current/slakware/gtk1/xchat.tgz">1.5.7</ulink>.
</para></listitem></itemizedlist></sect2></sect1>
<sect1 id="thanks"><title>Hell and Paradise</title>
<sect2><title>Gods</title>
<itemizedlist><listitem><para>
Thanks to all authors. Without their hard and volunteer work I'd never write it, and we'd never get our hands on Linux (and IRC).
</para></listitem></itemizedlist></sect2>
<sect2><title>Saints</title>
<itemizedlist><listitem><para>
Put your name here.
</para></listitem></itemizedlist></sect2>
<sect2><title>Angels</title>
<itemizedlist><listitem><para>
Put your name here.
</para></listitem></itemizedlist></sect2>
<sect2><title>Devils</title>
<itemizedlist><listitem><para>
Khaled Mardam-Bey must be stopped <emphasis>:)</emphasis>
</para></listitem>
<listitem><para>
'If idiots could fly, IRC would be an airport'. I don't know who wrote
that, but it makes sense. For those of you using IRC to annoy and piss
off I ordered a /kill for Christmas.
</para></listitem></itemizedlist></sect2></sect1>
<sect1 id="history"><title>Revision History</title>
<itemizedlist><listitem><para>
200012120 - v0.05, first draft
</para></listitem></itemizedlist></sect1></article>