Date-stamped : 18 Dec95 - 14:31 How to get the IRC-II client software and install it ==================================================== (Courtesy Fer F.de Jong, fer@harmony.cern.ch) To install an IRC-II client on your machine follow this procedure. People that want to install IRC for global use should be able to change the described procedure so the files go in an /usr/local/bin like place. On your UNIX system type: vaseline:~srini> mkdir irc vaseline:~srini> cd irc vaseline:~srini/irc> ftp ftp2.undernet.org Other sites that can be used instead of ftp2.undernet.org are ftp.undernet.org and cs-pub.bu.edu . [ login as user anonymous ] [ type your e-mail address when asked for a password ] ftp% bin ftp% cd irc ftp% cd clients ftp% get ircii-2.8.2.tar.Z [or get ircii-2.8.2.tar.gz if you prefer gzip instead of compress format] ftp% get ircII2.8help.tar.Z [or get ircii-2.8help.tar.gz] ftp% bye Now you have copied all the files needed for compilation and installation. Type on your UNIX system: vaseline:~srini/irc> zcat ircII2.8.2.tar.Z |tar xf - [or .gz] (if this doesnt work, do either uncompress ircII2.8.2.tar.Z [or gunzip ircII2.2.8.2.gz] tar -xf ircII2.8.2.tar then, vaseline:~srini/irc> cd ircii-2.8.2 vaseline:~srini/irc/ircii-2.8.2> Read the file INSTALL that explains how to compile and install the whole IRC system: First try the following vaseline:~srini/irc/ircii-2.8.2>./install (or ./easyinstall) If this works, it will ask you some system oriented questions. You should be able to answer most of them without much difficulty. If you cant, try to take some local expert advice. If you cant find one, send me a mail. Again, dont expect a prompt reply (but you will get in one or two days tho). If every thing goes smoothly, you have successfully loaded irc and can skip the rest of the posting and directly go to the end. If it doesnt, do the following. See, if there is a file by name configure (executible) in the directory once you have tarred. If it is there, do vaseline:~srini/irc/ircii-2.8.2> ./configure This will configure the makefile and others to your system. You may also have to set various parameters. The important settings that need to be made are in the files Makefile and config.h. Pay special attention to: In config.h: set DEFAULT_SERVER to an IRC server site close to you. Some of server names include: us.undernet.org (default USA server) au.undernet.org (default Australian server) uk.undernet.org (default UK server) eu.undernet.org (default european server - French I think) ca.undernet.org (default canadian server) In the days when #cricket was on the EFnet, you had to remember fancy names, but since it moved to the undernet (which is run on a much more logical basis), the process of working out which server is best for you, has become much server. For example if you live in the USA, and find the default US server no good (it's in california), you can try the one in your state (all the big states have one) eg. ny.us.undernet.org (New York) tx.us.undernet.org (Texas) You don't HAVE to go to the one in your state, or even the nearest one, though. Keep trying state abbreviations, and you'll find one. Remember, #cricket is on the undernet. If your server doesn't have the word "undernet" in it, you are probably on the wrong IRC net. Other Unix stuff: In config.h: Check all other #define's, check the path to zcat and correct the error (forgotten /* at start of AUTO_RECONNECT #define), set HELP_SERVICE to help_UK or help_AU or help_US or ircIIhelp depending on where you are. You can also set it to NULL in which case all the help files should be loaded into your system. You can save your diskspace by selecting one of the above. In Makefile: INSTALL_EXECUTABLE = your_homedir/bin/irc IRCII_LIBRARY = your_homedir/lib/irc (Create these directories yourself and put the bin INSTALL_IRCFLUSH = your_homedir/bin/ircflush directory in your $PATH) Set the DEFINES= line by removing the # at the beginning of the one that is ment for your hardware setup. Now you can (i.e. type) 'make' the whole thing and it should work without any problem. If it doesnt work, you can send me a mail, but as I said, I cant promise a prompt reply, but I will try my best. You might also try sending mail to mgmt@cricinfo.cse.ogi.edu vaseline:~srini/irc/ircii-2.8.2> make vaseline:~srini/irc/ircii-2.8.2> make ircflush vaseline:~srini/irc/ircii-2.8.2> make install vaseline:~srini/irc/ircii-2.8.2> make installflush In the directory your_homedir/lib/irc you should make a file called servers with a list of all the servers you want to try to connect to. If the default server (top line) does not work (machine down, links to machine don't work...) your IRC client will try to connect to the next machine in the list. The file should look something like: default.machine.domain second.choice.machine third.choice.machine last.hope.for.connection.machine Always try to find IRC servers that are network-wise close to where you are. Note that the contents of this file will override the DEFAULT_SERVER setting in config.h, so after you have compiled IRC try to find out the best server and put that one at the top of your servers file. Now you have to install the script files and help files that will make your IRC life easier. vaseline:~srini/irc/ircii-2.8.2> cp -r script $HOME/lib/irc vaseline:~srini/irc/ircii-2.8.2> cd vaseline:~srini/irc/ircii-2.8.2> cd ~/lib/irc vaseline:~srini/lib/irc> zcat $HOME/irc/ircII2.8help.tar.Z | tar xvf - vaseline:~srini/lib/irc> compress help/* vaseline:~srini/lib/irc> compress help/*/* Don't mind the error messages of the last two commands, these are normal. If you want to allow others to use IRC, don't forget to use the chmod(1) command to make the files and directories available. It might seem a lot of work, but you can have a lot of fun with IRC so it is worth a try. To learn to use IRC, type to start IRC, vaseline@home:> rehash vaseline@home:> irc then, type /help newuser and you will get basic commands. you can also type /join #cricket directly and then you will see some of us there and most of us are certainly willing to help you (but also expect you to read the dirty details and not expect to tell you every little thing). Contributed by srini (srini@cricinfo.cse.ogi.edu)