mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
6f4a9305e8
commit
70f180e226
|
|
@ -2,18 +2,18 @@
|
|||
<article id="index">
|
||||
<articleinfo>
|
||||
<title>Linux IRC mini-HOWTO</title>
|
||||
<pubdate>v0.1 8 January, 2001</pubdate>
|
||||
<pubdate>v0.2 1 July, 2001</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.1</revnumber>
|
||||
<date>2001-01-08</date>
|
||||
<revnumber>0.2</revnumber>
|
||||
<date>2001-07-1</date>
|
||||
<authorinitials>fredlwm</authorinitials>
|
||||
<revremark>
|
||||
Second revision.
|
||||
Third revision.
|
||||
</revremark>
|
||||
</revision>
|
||||
</revhistory>
|
||||
|
|
@ -25,22 +25,22 @@
|
|||
<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>.
|
||||
RFC1459 by Jarkko Oikarinen and Darren Reed was the first about the Internet Relay Chat Protocol. It can be found at
|
||||
<ulink url="http://ftp.isi.edu/in-notes/rfc1459.txt">http://ftp.isi.edu/in-notes/rfc1459.txt</ulink>.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
RFC2811 by Christophe 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>.
|
||||
RFC2811 by Christophe Kalt updates RFC1459 and describes the Channel Management of the Internet Relay Chat. It can be found at
|
||||
<ulink url="http://ftp.isi.edu/in-notes/rfc2811.txt">http://ftp.isi.edu/in-notes/rfc2811.txt</ulink>.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
RFC2812 by Christophe 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>.
|
||||
RFC2812 by Christophe Kalt updates RFC1459 and describes the Client Protocol of the Internet Relay Chat. It can be found at
|
||||
<ulink url="http://ftp.isi.edu/in-notes/rfc2812.txt">http://ftp.isi.edu/in-notes/rfc2812.txt</ulink>.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
RFC2813 by Christophe 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>.
|
||||
RFC2813 by Christophe Kalt updates RFC1459 and describes the Server Protocol of the Internet Relay Chat. It can be found at
|
||||
<ulink url="http://ftp.isi.edu/in-notes/rfc2813.txt">http://ftp.isi.edu/in-notes/rfc2813.txt</ulink>.
|
||||
</para></listitem></itemizedlist>
|
||||
<para>Also be sure to check the following sites:</para>
|
||||
<para>Also be sure to check the following links:</para>
|
||||
<para><ulink url="http://www.irchelp.org/">http://www.irchelp.org/</ulink>.</para>
|
||||
|
||||
<sect2><title>Objectives</title>
|
||||
|
|
@ -53,9 +53,8 @@ Link important resources about IRC;
|
|||
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;
|
||||
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.
|
||||
|
|
@ -66,45 +65,35 @@ List IRC tools available in the latest release of all major distributions.
|
|||
<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>
|
||||
<ulink url="http://www.pervalidus.net/docs/IRC-mini-HOWTO/WIP/">http://www.pervalidus.net/docs/IRC-mini-HOWTO/WIP/</ulink>.</para>
|
||||
<para>All drafts are archived at
|
||||
<ulink url="http://www.pervalidus.net/docs/IRC-mini-HOWTO/old/">http://www.pervalidus.net/docs/IRC-mini-HOWTO/old/</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>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>BTW, someone to work on the protocol and server sides would be very welcome to join the project.</para>
|
||||
|
||||
<para>Frédéric L. W. Meunier (<email>linuxdoc @ pervalidus.net</email>) - fredlwm at BRASnet and OPN.</para></sect2>
|
||||
<para>Frédéric L. W. Meunier (<email>linuxdoc @ pervalidus.net</email>)</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>
|
||||
<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>
|
||||
<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>
|
||||
|
||||
|
|
@ -112,28 +101,24 @@ giving us ever more powerful systems.</para></sect1>
|
|||
|
||||
<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>It's easy to use ircII. Let's say you want to connect to irc.openprojects.net as 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>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>
|
||||
<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>
|
||||
<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>
|
||||
|
|
@ -141,22 +126,23 @@ First, /set NOVICE off
|
|||
/nick IRC-mini-HOWTO changes your IRCNICK to <emphasis>IRC-mini-HOWTO</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/set realname The Linux IRC mini-HOWTO changes your IRCNAME to <emphasis>The Linux IRC mini-HOWTO</emphasis> (doesn't change on the same connection)
|
||||
/set realname The Linux IRC mini-HOWTO changes your IRCNAME to <emphasis>The Linux IRC mini-HOWTO</emphasis> (doesn't change
|
||||
on the same connection)
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/j #LinuxHelp joins channel <emphasis>#LinuxHelp</emphasis>
|
||||
/j #LinPeople joins channel <emphasis>#LinPeople</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/j #Slackware joins channel <emphasis>#Slackware</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/j #LinuxHelp changes the active current channel to <emphasis>#LinuxHelp</emphasis>
|
||||
/j #LinPeople changes the active current channel to <emphasis>#LinPeople</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/msg <emphasis>nick</emphasis> Hi. sends a private message to <emphasis>nick</emphasis> containing <emphasis>Hi.</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/notice <emphasis>nick</emphasis> (or #Linux) Hi. sends a notice to <emphasis>nick</emphasis> (or #Linux) containing <emphasis>Hi.</emphasis>
|
||||
/notice <emphasis>nick</emphasis> (or #LinPeople) Hi. sends a notice to <emphasis>nick</emphasis> (or #LinPeople) containing <emphasis>Hi.</emphasis>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
/query <emphasis>nick</emphasis> starts a private conversation with <emphasis>nick</emphasis>. /query ends the private conversation
|
||||
|
|
@ -193,9 +179,8 @@ First, /set NOVICE off
|
|||
|
||||
<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.
|
||||
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.
|
||||
</para></listitem></itemizedlist>
|
||||
<para>$ man adduser</para>
|
||||
<para>On Linux channels you shouldn't:</para>
|
||||
|
|
@ -203,59 +188,52 @@ create 2 users, one of them to only use IRC.
|
|||
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.
|
||||
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.
|
||||
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.
|
||||
</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.
|
||||
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> ircII project (<email>ircii@eterna.com.au</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #ircii (official channel?) on <ulink url="http://www.efnet.org/servers.html">EFNet</ulink></para>
|
||||
<para><emphasis>Maintainer:</emphasis> ircII project (<email>ircii @ eterna.com.au</email>)</para>
|
||||
<para><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>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> EPIC Software Labs (<email>ircii-epic@concentric.net</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #epic on EFNet</para>
|
||||
<para><emphasis>Maintainer:</emphasis> EPIC Software Labs (<email>ircii-epic @ concentric.net</email>)</para>
|
||||
<para><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>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> Colten Edwards (<email>edwards@bitchx.dimension6.com</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #bitchx on EFNet</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Colten Edwards (<email>edwards @ bitchx.dimension6.com</email>)</para>
|
||||
<para><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>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>.
|
||||
|
|
@ -263,15 +241,12 @@ Homepage of gtkBitchX at <ulink url="http://www.bitchx.org/gtk/">http://www.bitc
|
|||
|
||||
<sect2><title>irssi</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Timo Sirainen (<email>tss@iki.fi</email>)</para>
|
||||
<para><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><emphasis>Maintainer:</emphasis> Timo Sirainen (<email>tss @ iki.fi</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #irssi on <ulink url="http://openprojects.net/irc_servers.shtml">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>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.</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>
|
||||
|
|
@ -280,18 +255,28 @@ Homepage at <ulink url="http://irssi.org/">http://irssi.org/</ulink>.</para></se
|
|||
|
||||
<sect2><title>Zircon</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Lindsay F. Marshall (<email>Lindsay.Marshall@ncl.ac.uk</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Lindsay F. Marshall (<email>Lindsay.Marshall @ ncl.ac.uk</email>)</para>
|
||||
<para><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>Sula PrimeriX II</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Tano Fotang (<email>fotang @ yahoo.com</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None ?</para>
|
||||
|
||||
<para>Uses GTK+ or XForms, and Guile.</para>
|
||||
|
||||
<para>You can get the latest version of Sula PrimeriX II from <ulink url="http://spx.linuxatwork.at/#where-to-get-it">http://spx.linuxatwork.at/#where-to-get-it</ulink>.
|
||||
Homepage at <ulink url="http://spx.linuxatwork.at/">http://spx.linuxatwork.at/</ulink>.</para></sect2>
|
||||
|
||||
<sect2><title>xIrc</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Robert Borrell (<email>borrell@pobox.com</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Robert Borrell (<email>borrell @ pobox.com</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None ?</para>
|
||||
|
||||
<para>Using the Qt toolkit, xIrc is less featured than KVIrc. As an advantage, it's faster.</para>
|
||||
|
||||
|
|
@ -300,8 +285,8 @@ Homepage at <ulink url="http://www.linuxlots.com/~xirc/">http://www.linuxlots.co
|
|||
|
||||
<sect2><title>KVIrc</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Szymon Stefanek (<email>stefanek@tin.it</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #kvirc on OPN</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Szymon Stefanek (<email>stefanek @ tin.it</email>)</para>
|
||||
<para><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>
|
||||
|
||||
|
|
@ -310,19 +295,28 @@ Homepage at <ulink url="http://www.kvirc.net/">http://www.kvirc.net/</ulink>.</p
|
|||
|
||||
<sect2><title>X-Chat</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Peter Zelezny (<email>zed@linux.com</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #linux on <ulink url="http://www.chatjunkies.org/servers.html">ChatJunkies</ulink></para>
|
||||
<para><emphasis>Maintainer:</emphasis> Peter Zelezny (<email>zed @ linux.com</email>)</para>
|
||||
<para><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>Using GTK+ and optionally 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>
|
||||
Homepage at <ulink url="http://xchat.org/">http://xchat.org/</ulink>.</para></sect2>
|
||||
|
||||
<sect2><title>QuIRC</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Patrick Earl (<email>quirc @ patearl.net</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #QuIRC on <ulink url="http://www.dal.net/servers/">DALnet</ulink></para>
|
||||
|
||||
<para>Using Tk, supports Tcl for scripting.</para>
|
||||
|
||||
<para>You can get the latest version of QuIRC from his Homepage at <ulink url="http://quirc.org/">http://quirc.org/</ulink>.</para></sect2></sect1>
|
||||
|
||||
<sect1 id="servers"><title>IRC Servers</title>
|
||||
|
||||
<sect2><title>IRCD</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> ircd developers(<email>ircd-dev@irc.org</email>)</para>
|
||||
<para><emphasis>Maintainer:</emphasis> ircd developers(<email>ircd-dev @ irc.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #ircd on IRCnet</para>
|
||||
|
||||
<para>The original IRC daemon, mainly used by IRCnet.</para>
|
||||
|
|
@ -332,8 +326,8 @@ Homepage at <ulink url="http://www.irc.org/">http://www.irc.org/</ulink>.</para>
|
|||
|
||||
<sect2><title>IRCD-Hybrid</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> (<email>ircd-hybrid@the-project.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> (<email>ircd-hybrid @ the-project.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None ?</para>
|
||||
|
||||
<para>Mainly used by EFNet.</para>
|
||||
|
||||
|
|
@ -342,7 +336,7 @@ Homepage at <ulink url="http://www.ircd-hybrid.net/">http://www.ircd-hybrid.net/
|
|||
|
||||
<sect2><title>ircu</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Undernet Coder Committee (<email>coder-com@undernet.org</email>)</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Undernet Coder Committee (<email>coder-com @ undernet.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #ircu on <ulink url="http://www.undernet.org/servers.shtml">Undernet</ulink></para>
|
||||
|
||||
<para>Mainly used by Undernet.</para>
|
||||
|
|
@ -352,19 +346,19 @@ Homepage at <ulink url="http://coder-com.undernet.org/">http://coder-com.underne
|
|||
|
||||
<sect2><title>Bahamut</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> DALnet Coding Team (<email>bahamut@bahamut.net</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #bahamut on <ulink url="http://www.dal.net/servers/">DALnet</ulink></para>
|
||||
<para><emphasis>Maintainer:</emphasis> DALnet Coding Team (<email>bahamut @ bahamut.net</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #Bahamut on DALnet</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>
|
||||
<para>You can get the latest version of Bahamut from <ulink url="http://bahamut.dal.net/download/">http://bahamut.dal.net/download/</ulink>.
|
||||
Homepage at <ulink url="http://bahamut.dal.net/">http://bahamut.dal.net/</ulink>.</para></sect2></sect1>
|
||||
|
||||
<sect1 id="bots"><title>IRC Bots</title>
|
||||
|
||||
<sect2><title>eggdrop</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> (<email>eggdev@eggheads.org</email>)</para>
|
||||
<para><emphasis>Maintainer:</emphasis> (<email>eggdev @ eggheads.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> #eggdrop on Undernet</para>
|
||||
|
||||
<para>eggdrop is the most known Tcl enabled application on the Net. It's
|
||||
|
|
@ -377,8 +371,8 @@ Homepage at <ulink url="http://www.eggheads.org/">http://www.eggheads.org/</ulin
|
|||
|
||||
<sect2><title>bnc</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> None?</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> None ?</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None ?</para>
|
||||
|
||||
<para>bnc is the original bouncer.</para>
|
||||
|
||||
|
|
@ -386,8 +380,8 @@ Homepage at <ulink url="http://www.eggheads.org/">http://www.eggheads.org/</ulin
|
|||
|
||||
<sect2><title>muh</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Sebastian Kienzl (<email>zap@riot.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Sebastian Kienzl (<email>zap @ riot.org</email>)</para>
|
||||
<para><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
|
||||
|
|
@ -398,45 +392,45 @@ Homepage at <ulink url="http://mind.riot.org/muh/">http://mind.riot.org/muh/</ul
|
|||
|
||||
<sect2><title>ezbounce</title>
|
||||
|
||||
<para><emphasis>Maintainer:</emphasis> Murat Deligönül (<email>druglord@freelsd.org</email>)</para>
|
||||
<para><emphasis>IRC Channel:</emphasis> None?</para>
|
||||
<para><emphasis>Maintainer:</emphasis> Murat Deligönül (<email>druglord @ freelsd.org</email>)</para>
|
||||
<para><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>
|
||||
<para>You can get the latest version of ezbounce from his Homepage at <ulink url="http://druglord.freelsd.org/ezbounce/">http://druglord.freelsd.org/ezbounce/</ulink>.</para></sect2></sect1>
|
||||
|
||||
<sect1 id="install"><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) > ~/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>
|
||||
<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) > ~/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>Do you really need help to set up a server ?</para>
|
||||
|
||||
<para>~$ vim ircd.conf</para></sect2></sect1>
|
||||
|
||||
<sect1 id="distribution"><title>But what's already included in my distribution? (Linux on x86)</title>
|
||||
<sect1 id="distribution"><title>But what's already included in my distribution ? (Linux on x86)</title>
|
||||
|
||||
<sect2><title>Debian</title>
|
||||
|
||||
<para>Debian includes too many IRC tools to list. You can find them at the following places:</para>
|
||||
<para>IRC Channel: #Debian on OPN</para>
|
||||
|
||||
<para><ulink url="http://www.debian.org/">Debian</ulink> 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).
|
||||
Debian <ulink url="ftp://ftp.debian.org/debian/dists/unstable/main/binary-i386/net/">unstable</ulink> (didn't receive enough 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.
|
||||
|
|
@ -447,44 +441,69 @@ Debian non-free (applications with a restrictive license) contains <ulink url="f
|
|||
|
||||
<sect2><title>RedHat</title>
|
||||
|
||||
<para>RedHat 7.0 includes the following clients:</para>
|
||||
<para>IRC Channel: #RedHat on OPN (not official)</para>
|
||||
|
||||
<para><ulink url="http://www.redhat.com/">RedHat</ulink> 7.1 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>.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/os/i386/RedHat/RPMS/ircii-4.4Z-4.i386.rpm">ircII 4.4Z</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>.
|
||||
KSirc from <ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/os/i386/RedHat/RPMS/kdenetwork-2.1.1-1.i386.rpm">KDE Network 2.1.1</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>.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/os/i386/RedHat/RPMS/xchat-1.6.3-4.i386.rpm">X-Chat 1.6.3</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:
|
||||
RedHat Powertools (what's worth but they don't want to include or can't) 7.1 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.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/BitchX-1.0c17-6.i386.rpm">BitchX</ulink>
|
||||
and <ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/gtkBitchX-1.0c17-6.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>.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/epic-4_2000-6.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>.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/kvirc-2.1.0-2.i386.rpm">KVIrc 2.1.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>.
|
||||
<ulink url="ftp://ftp.redhat.com/pub/redhat/redhat-7.1-en/powertools/i386/RedHat/RPMS/tkirc-2.43-2.noarch.rpm">tkIRC 2.43</ulink>.
|
||||
</para></listitem></itemizedlist>
|
||||
|
||||
<itemizedlist><listitem><para>
|
||||
RedHat RawHide (current development)
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<ulink url="ftp://rawhide.redhat.com/pub/redhat/linux/rawhide/">ftp://rawhide.redhat.com/pub/redhat/linux/rawhide/</ulink>. Use at your own risk.
|
||||
</para></listitem></itemizedlist></sect2>
|
||||
|
||||
<sect2><title>Slackware</title>
|
||||
|
||||
<para>Slackware 7.1 includes the following clients:</para>
|
||||
<para>IRC Channel: #Slackware on OPN</para>
|
||||
|
||||
<para><ulink url="http://www.slackware.com/">Slackware</ulink> 8.0 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>.
|
||||
<ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-8.0/slakware/n1/bitchx.tgz">BitchX 1.0c18</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>.
|
||||
<ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-8.0/slakware/n1/epic4.tgz">EPIC4 1.0.1</ulink>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
KSirc from <ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-8.0/slakware/kde1/knetwork.tgz">KDE Network 2.1.1</ulink>.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-8.0/slakware/gtk1/xchat.tgz">X-Chat 1.6.4</ulink>.
|
||||
</para></listitem></itemizedlist></sect2>
|
||||
|
||||
<itemizedlist><listitem><para>
|
||||
Slackware -current (current development)
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<ulink url="ftp://ftp.slackware.com/pub/slackware/slackware-current/">ftp://ftp.slackware.com/pub/slackware/slackware-current/</ulink>. Use at your own risk.
|
||||
</para></listitem></itemizedlist></sect2></sect1>
|
||||
|
||||
<sect1 id="thanks"><title>Hell and Paradise</title>
|
||||
|
|
@ -513,13 +532,12 @@ Put your name here.
|
|||
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.
|
||||
'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>
|
||||
20010108 - v0.1, second draft
|
||||
20010701 - v0.2, third draft
|
||||
</para></listitem></itemizedlist></sect1></article>
|
||||
|
|
|
|||
Loading…
Reference in New Issue