v0.3 11 November, 2002
|Revision 0.3||2002-11-21||Revised by: fredlwm|
This document is still WIP, and should be treated as such. I'll do my best to keep it updated and accurate.
The following bibles shouldn't be ignored:
RFC1459 by Jarkko Oikarinen and Darren Reed was the first about the Internet Relay Chat Protocol. It can be found at http://ftp.isi.edu/in-notes/rfc1459.txt.
RFC2810 by Christophe Kalt updates RFC1459 and describes the Architecture of the Internet Relay Chat. It can be found at http://ftp.isi.edu/in-notes/rfc2810.txt.
RFC2811 by Christophe Kalt updates RFC1459 and describes the Channel Management of the Internet Relay Chat. It can be found at http://ftp.isi.edu/in-notes/rfc2811.txt.
RFC2812 by Christophe Kalt updates RFC1459 and describes the Client Protocol of the Internet Relay Chat. It can be found at http://ftp.isi.edu/in-notes/rfc2812.txt.
RFC2813 by Christophe Kalt updates RFC1459 and describes the Server Protocol of the Internet Relay Chat. It can be found at http://ftp.isi.edu/in-notes/rfc2813.txt.
Also be sure to check the following links:
Among others, the objectives of this mini-HOWTO are:
Link important resources about IRC;
Avoid common misuses of IRC by writing an IRC Etiquette;
List popular clients, servers, bots, and bouncers, along with their maintainers, #channel, small description, download location, home page, and hints;
List IRC tools available in the latest release of all major distributions.
The latest version of this document is available at http://www.pervalidus.net/documentation/IRC-mini-HOWTO/.
A WIP of the next draft may be available at http://www.pervalidus.net/documentation/IRC-mini-HOWTO/WIP/.
All drafts are archived at http://www.pervalidus.net/documentation/IRC-mini-HOWTO/old/.
Everything is mirrored at http://pervalidus.port5.com/documentation/IRC-mini-HOWTO/.
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.
BTW, someone to work on the protocol and server sides would be very welcome.
Frédéric L. W. Meunier (<linuxdoc @ pervalidus.net>)
Excerpt from RFC2810:
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.
First formally documented in May 1993 by RFC 1459 [IRC], the protocol has kept evolving.
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.
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.
The standard IRC client is the original ircII client. It's part of most Linux distributions.
It's easy to use ircII. Let's say you want to connect to irc.freenode.net as mini-HOWTO.
At the command line, type:
$ irc mini-HOWTO irc.freenode.net
You can also export variables, so you won't need to use them at the command line:
$ export IRCNICK=mini-HOWTO IRCSERVER=irc.freenode.net
Add them to your shell profile (e.g. ~/.bash_profile or ~/.zprofile) when you're done.
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 http://ojnk.sourceforge.net/. To configure, read the oidentd.conf man page. Finally run '/usr/local/sbin/oidentd -g nobody -u nobody'. Add this to your startup scripts (e.g. /etc/rc.d/rc.local) when you're done.
If not set, IRCNICK, IRCUSER, and IRCNAME will be retrieved from /etc/passwd .
Use /help to get a list on all available commands (/help help is a good start). Replace nick by any IRCNICK.
First, /set NOVICE off
/nick IRC-mini-HOWTO changes your IRCNICK to IRC-mini-HOWTO
/set realname The Linux IRC mini-HOWTO changes your IRCNAME to The Linux IRC mini-HOWTO (doesn't change on the same connection)
/j #mini-HOWTO joins channel #mini-HOWTO
/j #unmaintained-HOWTO joins channel #unmaintained-HOWTO
/j #mini-HOWTO changes the active current channel to #mini-HOWTO
/msg nick Hi. sends a private message to nick containing Hi.
/notice nick (or #mini-HOWTO) Hi. sends a notice to nick (or #mini-HOWTO) containing Hi.
/query nick starts a private conversation with nick. /query ends the private conversation
/me loves Linux. sends an action to the current channel or query containing IRC-mini-HOWTO loves Linux.
/dcc chat nick starts a chat with nick. Use /msg =nick (notice the =) to send messages over the chat
/dcc send nick /etc/HOSTNAME sends the given file to nick
/dcc get nick receives the file offered by nick
/part leaves the active current channel
/part #unmaintained-HOWTO leaves channel #unmaintained-HOWTO
/discon disconnects from current IRCSERVER
/server irc.us.freenet.net connects to IRCSERVER irc.us.freenet.net
/quit Bye. quits your IRC session with a reason Bye.
WARNING WARNING WARNING WARNING WARNING
Never use IRC logged as root or any user with excessive privileges. Bad things may happen sooner or later. You were warned. It's safe if you create 2 users, one of them to only use IRC.
$ man adduser
On Linux channels you shouldn't:
Act as an idiot. If you want to be respected, then first respect each other.
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.
Use full CAPS, bold (^B), reverse (^V), underline (^_), blink (^F), and bell (^G). The first 4 are here to emphasize words, not the whole text. The last 2 are just very annoying.
Ask if you can ask a question. Just ask, but first read all documentation available on the subject. Start looking at /usr/doc/ , otherwise go to http://www.tldp.org/ or http://www.ibiblio.org/pub/Linux/docs/. 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.
Maintainer: ircII project (<ircii @ eterna.com.au>)
IRC Channel: #ircII (official channel ?) on EFNet
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.
Maintainer: EPIC Software Labs (<ircii-epic @ concentric.net>)
IRC Channel: #EPIC on EFNet
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.
Maintainer: Colten Edwards (<edwards @ bitchx.dimension6.com>)
IRC Channel: #BitchX on EFNet
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 compiled with the GNOME libraries by using the configure option --with-gtk. Don't be surprised if all you get is a XTerm-BitchX instead.
Maintainer: Timo Sirainen (<tss @ iki.fi>)
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 modular text mode client. Supports Perl scripting.
Maintainer: Lindsay F. Marshall (<Lindsay.Marshall @ ncl.ac.uk>)
IRC Channel: None ?
Written in Tcl/Tk, uses the native network communications of Tcl.
Maintainer: Szymon Stefanek (<stefanek @ tin.it>)
IRC Channel: #KVIrc on freenode
Also written with the Qt toolkit, KVIrc is a beast. Supports DCC Voice, built-in scripting language, and plugins.
Maintainer: Peter Zelezny (<zed @ linux.com>)
IRC Channel: #Linux on ChatJunkies
Using GTK+ and optionally GNOME, supports Perl and Python scripting.
Maintainer: ircd developers(<ircd-dev @ irc.org>)
IRC Channel: #ircd on IRCnet
The original IRC daemon, mainly used by IRCnet.
Maintainer: (<ircd-hybrid @ the-project.org>)
IRC Channel: None ?
Mainly used by EFNet.
Maintainer: Undernet Coder Committee (<coder-com @ undernet.org>)
IRC Channel: #ircu on Undernet
Mainly used by Undernet.
Maintainer: (<eggdev @ eggheads.org>)
IRC Channel: #eggdrop on Undernet
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.
Maintainer: None ?
IRC Channel: None ?
bnc is the original bouncer.
Maintainer: Sebastian Kienzl (<zap @ riot.org>)
IRC Channel: None ?
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.
Maintainer: Murat Deligönül (<druglord @ freelsd.org>)
IRC Channel: None ?
ezbounce's basic features include password protection, remote administration, logging and listening on multiple ports.
You can get the latest version of ezbounce from his Homepage at http://druglord.freelsd.org/ezbounce/.
All popular clients use GNU autoconf and GNU 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 compile. Doing cd sources; mkdir objdir; cd objdir; ../configure --help; ../configure your_options_here; make; make install (or make install_strip) > ~/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.
IRC Channel: #Debian on freenode (irc.debian.org -> irc.freenode.net)
Debian includes too many IRC tools to list. You can find them at the following places:
IRC Channel: #RedHat on freenode (irc.redhat.com -> irc.freenode.net)
Red Hat 8.0 includes the following clients:
Red Hat Raw Hide (current development)
ftp://rawhide.redhat.com/pub/redhat/linux/rawhide/. Use at your own risk.
IRC Channel: #Slackware on freenode
Slackware 8.1 includes the following clients:
Slackware -current (current development)
ftp://ftp.slackware.com/pub/slackware/slackware-current/. Use at your own risk.
Thanks to all authors. Without their hard and volunteer work I'd never write it, and we'd never get our hands on Linux nor IRC.