/[cvs]/eggdrop1.9/README
ViewVC logotype

Diff of /eggdrop1.9/README

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph | View Patch Patch

revision 1.24 by wcc, Thu Dec 11 00:49:10 2003 UTC revision 1.25 by wcc, Thu Dec 11 01:21:48 2003 UTC
# Line 1  Line 1 
1  README  $Id$
   ------------------------------------------------------------------------  
2    
3       Please at least SKIM this document before asking questions. In fact,  Readme
4       READ IT if you've never successfully set up an eggdrop bot before.  Last revised: December 10, 2003
5       PLEASE! READ IT! If you haven't read this file, and ask for help       _________________________________________________________________
6       expect to be told to READ the README file first! or rtfm :)  
7                                       Readme
8    
9    
10      Please at least SKIM this document before asking questions. In fact, READ IT
11      if you've never successfully set up an Eggdrop bot before. PLEASE! READ IT!
12    
13       Contents       Contents
14    
15       0    Important notice      0. Important notice
16        1. What is Eggdrop?
17        2. How do I get Eggdrop?
18        3. Command line
19        4. Boring legal stuff
20        5. Mailing list
21        6. Documentation
22        7. Obtaining help
23    
24       1    What is Eggdrop?       _________________________________________________________________
      2    How do I get Eggdrop  
           2a    CVS usage  
      3    Quick startup  
      4    Upgrading  
           4a    From a pre-1.3 version to 1.6  
           4b    From an older 1.3/1.4/1.5/1.6 version to a newer one  
      5    Frequently Asked Questions  
             1. What do I do if I get the Error "User file not found"?  
             2. My Eggdrop won't run; It just says "Can't find your  
                hostname!"  
             3. What the Heck is TCL?  
             4. My bot dies and the last entry in the logfile is "Received  
                terminate signal". What does that mean and can I prevent it?  
             5. My compile dies at the last minute with "LD fatal signal  
                11"!  
             6. Someone else set up a bot I don't like. Are there any  
                backdoors I can use to take their bot down?  
             7. What are modules?  
             8. Can I compile eggdrop without dynamic modules?  
                8.1    Do I still need to "loadmodule modules"???  
             9. Where can I get a precompiled Eggdrop for my computer?  
            10. I get "Makefile:3 : invalid operator" of some such thing  
                When I try to "make"  
            11. When I "tclsh scripts/weed <userfile> c" It barfs chunks at  
                me and dies.  
            12. I get "ld-elf.so.1: Shared object "libtcl80.so.1" not found"  
                or "eggdrop: error in loading shared libraries /  
                libtcl8.1.so: cannot open shared object file: No such file  
                or directory" when I try to start my bot.  
            13. I get a whole pile of "unresolved symbol 'Tcl_AppendResult'"  
                (or some other symbol) when I try to load a module.  
      6    Setting up a crontab  
           6a    Setting up a crontab using autobotchk  
      7    Boring legal stuff  
      8    Mailing list  
      9    Documentation  
      10  Obtaining help  
25    
   ------------------------------------------------------------------------  
26    
27       (0) NOTICE       (0) NOTICE
28    
29            Please read this file carefully before trying to set up this      Please read this file carefully before trying to set up Eggdrop. Also,
30            bot. Also, make SURE that you select your +n (owner) users      make SURE that you select your +n (owner) users wisely! They have 100%
31            wisely! They have 100% access to your bot and account! ONLY      access to your bot and account! ONLY GIVE THIS POWER TO SOMEONE YOU
32            GIVE THIS POWER TO SOMEONE YOU TRUST COMPLETELY!!      TRUST COMPLETELY!!
33        
34        Remember that this is a DEVELOPMENT VERSION. Everything isn't guaranteed
35        to work. Eggdrop 1.7 should *NOT* be used in a production environment.
36    
37    
38       (1) WHAT IS EGGDROP?       (1) WHAT IS EGGDROP?
39    
40            Eggdrop is an IRC bot, written in C. If you don't know what      Eggdrop is the world's most popular Internet Relay Chat (IRC) bot; it is
41            IRC is, this is probably not whatever you're looking for!      freely distributable under the GNU General Public License (GPL). Eggdrop
42            Eggdrop, being a bot, sits on a channel and takes protective      is a feature rich program designed to be easily used and expanded upon by
43            measures: to keep the channel from being taken over (in the      both novice and advanced IRC users on a variety of hardware and software
44            few ways that anything CAN), to recognize banished users or      platforms.
45            sites and reject them, to recognize privileged users and let  
46            them gain ops, etc.      An IRC bot is a program that sits on an IRC channel and preforms automated
47        tasks while looking just like a normal user on the channel. Some of these
48            One of the more unique features of eggdrop is its      functions include protecting the channel from abuse, allowing privileged
49            "partyline", accessible via DCC chat, which allows you to      users to gain op or voice status, logging channel events, providing
50            talk to other people lag-free. Consider it a multi-way DCC      information, hosting games, etc.
51            chat, or a miniature IRC (complete with channels). You can  
52            link up with other bots and expand the partyline until it      One of the features that makes Eggdrop stand out from other bots is module
53            actually becomes something very much like IRC, in fact.      and Tcl scripting support. With scripts and modules, you can make the bot
54        preform almost any task you want. They can do anything from preventing
55            Eggdrop is always being improved and adjusted because there      floods to greeting users and banning advertisers from channels.
56            are bugs to be fixed and features to be added (if the users  
57            demand them, and they make actually sense). In fact, it      You can also link multiple Eggdrop bots together to form a botnet. This
58            existed for several years as v0.7 - v0.9 before finally      can allow bots to op each other securely, control floods efficiently, and
59            going 1.0. This version of eggdrop is part of the 1.6 tree.      even link channels across multiple IRC networks. It also allows the
60            A valiant effort has been made to chase down and destroy      Eggdrops share user lists, ban lists, exempt/invite lists, and ignore
61            bugs.      lists with other bots if userfile sharing is enabled. This allows users
62        to have the same access on every bot on your botnet. It also allows the
63            This README file contains information about how to get      bots to distribute tasks such as opping and banning users. See doc/BOTNET
64            eggdrop, how to quickly compile the bot, what you may need      for information on setting up a botnet.
65            to do when upgrading from older versions, a list of  
66            frequently asked questions about compiling, how to set up a      Eggdrop is always being improved and adjusted because there are bugs to
67            crontab, some boring legal stuff, info about the mailing      be fixed and features to be added (if the users demand them, and they make
68            list (a great place to ask questions, and a good place to      actually sense). In fact, it existed for several years as v0.7 - v0.9
69            report bugs also), some basics about CVS usage and some      before finally going 1.0. This version of Eggdrop is part of the 1.6 tree.
70            channels where you might get help with eggdrop.      A valiant effort has been made to chase down and destroy bugs.
71    
72            The preliminary documentation is in "eggdrop.doc" and is      This README file contains information about how to get Eggdrop, command
73            intended to be read after you have eggdrop compiled and set      line options for Eggdrop, what you may need to do when upgrading from
74            up.      older versions, a list of frequently asked questions, how to set up a
75        crontab, some boring legal stuff, info about the mailing list (a great
76        place to ask questions, and a good place to report bugs, too), some basics
77        about CVS usage, and some channels where you might get help with Eggdrop.
78    
79    
80       (2) HOW TO GET EGGDROP       (2) HOW TO GET EGGDROP
81    
82            Before you can compile eggdrop, you need to have Tcl      You can obtain the LATEST version of Eggdrop 1.7 by using CVS. CVS means
83            installed on your system. Most systems should have Tcl on      'Concurrent Versions System' and is a tool for developers to always keep
84            them by now -- you can check by trying the command "tclsh".      source code up to date. Try 'man cvs' on your shell for more information
85            If it works, you will be given a "%" prompt, and you can      about CVS.
86            type "exit" to exit the program. That means Tcl is on your  
87            system. If tclsh doesn't load, then Tcl probably isn't on      To obtain Eggdrop 1.7 via CVS, do as follows:
88            your system, and you will need to ftp it. The best ftp site  
89            is:        1. Log into your shell.
90    
91                           ftp://ftp.scriptics.com/pub/tcl        2. Type: 'export
92             CVSROOT=:pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot'.
93            Tcl comes with the Slackware distribution of Linux. HOWEVER,  
94            the one that comes on Slackware 3.0 is goofed up and you'll        3. Type 'cvs login'.
95            have to re-install it for yourself to get it working.  
96          4. Press <enter> when prompted for a password.
97            Currently, the 1.6 tree of eggdrop is developed at  
98            eggheads.org. You can get the latest version of eggdrop from        5. In your home dir, type 'cvs checkout eggdrop1.7'
99            ftp://ftp.eggheads.org/pub/eggdrop/source/stable/  
100          6. In ~/eggdrop1.7, you should have a copy of the latest CVS version
101            You might try www.eggheads.org for help and information.           of Eggdrop 1.7.
   
   
      (2a) CVS USAGE  
   
           You might obtain the *very latest* version of eggdrop that  
           is still under development by using CVS. CVS means  
           'Concurrent Versions System' and is a tool for developers to  
           always keep source code up to date. Try 'man cvs' on your  
           shell for more information about CVS ;-)  
   
           This intended only for users that know a fairly bit about  
           eggdrop. Be aware that the versions of eggdrop that you get  
           by CVS are still being developed, and may be buggy. The  
           Eggheads devteam will in *NO WAY* take any responsibility  
           for whatever might happen to you or your shell if you use a  
           CVS version of eggdrop.  
   
           To obtain eggdrop over CVS, do as follows:  
   
                (1) log into your shell  
                (2) type 'export  
                CVSROOT=:pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot'  
   
                (3) type 'cvs login'  
                (4) press <enter> when it asks for a password.  
                (5) in your home dir, type 'cvs checkout  
                eggdrop1.7'  
                (6) in ~/eggdrop1.7, you should have a copy of the  
                latest CVS version of eggdrop.  
102    
103            Notes:            Notes:
104    
105                 (1) you can 'cvs logout', but you don't need to.        o You can 'cvs logout', but you don't need to.
106                 (2) you don't need to go through this whole  
107                 process every time; if you want to get a CVS        o You don't need to go through this whole process every time. If you
108                 version of eggdrop at a later time, you can just          want to get a CVS version of Eggdrop at a later time, you can just
109                 'cd ~/eggdrop1.7' and type 'cvs update -dAP'.          'cd ~/eggdrop1.7' and type 'cvs update -CdAP'.
110                 (3) if you experience errors when using 'export',  
111                 you might be using tclsh as a shell. If so, try        o If you experience errors when using 'export', you might be using tclsh
112                 using the command 'setenv' instead of 'export':          as a shell. If so, try using the command 'setenv' instead of 'export':
113                 'setenv CVSROOT  
114                 :pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot'            setenv CVSROOT :pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot
115    
116       (3) QUICK STARTUP  
117      (3) COMMAND LINE
118             #### NOW INCLUDED IN 'INSTALL' - READ IT *AFTER* FINISHING  
119                                      THIS ####      Eggdrop has some command-line options -- not many, because most things
120        should be defined through the config file. However, sometimes you may
121       (4) UPGRADING      want to start up the bot in a different mode, and the command-line
122        options let you do that. Basically, the command line for Eggdrop is:
123            (4a) FROM A PRE-1.3 VERSION TO 1.6  
124          % eggdrop [options] [config-file]
125                 #### BACK UP YOUR USERFILE ####  
126        The options available are:
127                 We can't re-iterate this enough, if you are  
128                 upgrading, and you have even a slight possibility        -n: Don't background. Normally, Eggdrop will move itself into the
129                 of downgrading again later you will HAVE to back            background when you start it up, meaning you'll get another shell
130                 up your userfile, or you will lose it. v1.3 of            prompt, and you can do other things while the bot is running. With
131                 eggdrop radically changed alot of things.            -n, you won't return to the shell prompt until the bot exits (which
132              won't normally happen until it's killed). By default, -n will send
133                 There are many major changes between v0.9, v1.0,            all log entries to the console.
134                 v1.1 and v1.6 so PAY ATTENTION to this part if you  
135                 have a v0.9, 1.0 or 1.1 bot already. If you're just        -nt: Don't background, use terminal. This is just like -n, except that
136                 starting out, you can skip this section.             instead of seeing log entries, your console will simulate a DCC
137               chat with the bot.
138                 to 1.6: * If you run sharebots, you will  
139                 need to upgrade them all at the same time because        -nc: Don't background, show channel info. This is just like -n, except
140                 of the new userfile format. Older bots will be             that instead of seeing log entries, every 10 seconds your screen
141                 able to link in, but will not get or send a             will clear and you will see the current channel status, sort of
142                 userfile. MAKE A NEW CONFIG FILE from the example,             like "top".
143                 there are some radical extras.  
144          -m: Create userfile. If you don't have a userfile, this will make Eggdrop
145                 from 0.9/1.0 to 1.6: * Just redo the whole thing,            create one and give owner status to the first person that introduces
146                 absolutely everything has changed including            himself or herself to it. You'll need to do this when you first set
147                 the userfile and config file formats.            up your bot.
148    
149                 from 1.1/1.2 to 1.6: * You will likely want to redo        -v: Show version info, then quit.
                the config file, as much as changed. BACK UP!! You  
                will need to run 'tclsh scripts/weed/<userfile> c'  
                to convert your userfile from v3 (1.1/1.2) to v4  
                (1.3/1.4/1.5)  
   
           (4b) FROM AN OLDER 1.3/1.4/1.5/1.6 VERSION TO A NEWER ONE  
   
                If you followed the INSTALL file and did a 'make  
                install' (or 'make install DEST=<path>') after  
                'make', this will be pretty easy. Just upload the  
                new eggdrop1.6.xx.tar.gz file to the home dir of  
                your shell, gunzip and untar it, and type 'cd  
                ~/eggdrop1.6.xx'. Then, type './configure',  
                'make config' or 'make iconfig', 'make', then kill  
                the bot ('.die' on the partyline, or use 'kill' on  
                the shell) and 'make install' to the same directory  
                your bot is currently in. Then, you can just restart  
                your bot.  
   
                You should read through the new eggdrop.complete.conf  
                file for all the new options in Eggdrop 1.6.x if you  
                are upgrading from 1.3.x or 1.4.x.  You can copy and  
                paste any of these settings into you current conf file  
                if you do not want to use the default settings.  
   
      (5) FREQUENTLY ASKED QUESTIONS (or "Why doesn't this thing work?")  
   
           1. WHAT DO I DO IF I GET THE ERROR "USER FILE NOT FOUND"?  
   
                (1) Run eggdrop with the "-m" option (i.e.,  
                "./eggdrop -m mybot").  
                (2) Go to IRC and send "hello" to your bot (i.e.,  
                "/msg mybot hello").  
                (3) You will become an owner on your bot. You can  
                leave the bot running (nobody else will become a  
                master if they say "hello"), but in the future,  
                don't use the "-m" option when running the bot.  
   
           2. MY EGGDROP WON'T RUN; IT JUST SAYS "CAN'T FIND YOUR  
           HOSTNAME!"  
   
                Your machine is set up strangely, and eggdrop  
                can't figure out its network hostname. You can get  
                around this by setting an environment variable  
                called HOSTNAME.  
   
                In sh or ksh:  
   
                     $ HOSTNAME=myhost.domain.edu  
                     $ export HOSTNAME  
   
                In csh or tcsh:  
   
                     % setenv HOSTNAME myhost.domain.edu  
   
                It should work after that. You may want to bug  
                your system administrator to set up her /etc/hosts  
                file correctly, or add those above commands to  
                your '.login' file (sh or ksh: '.profile').  
   
           3. WHAT THE HECK IS TCL?  
   
                Tcl is a scripting language written by John  
                Ousterhout. It's much better than most "in-built"  
                script languages (like the one in ircII) and is  
                meant to be linked with anything needing a script  
                language. So I linked it with eggdrop. The file  
                "tcl-commands.doc" in the eggdrop directory  
                contains a list of the commands added to Tcl by  
                eggdrop. There are also several example scripts in  
                the scripts/ directory, and there are gobs of  
                scripts floating around on the ftp sites if you  
                like working by example (which is typically the  
                best way).  
   
           4. MY BOT DIES AND THE LAST ENTRY IN THE LOGFILE IS  
           "RECEIVED TERMINATE SIGNAL". WHAT DOES THAT MEAN AND CAN I  
           PREVENT IT?  
   
                There's nothing you can do to prevent it. It means  
                the system administrator is killing the eggdrop  
                process. Most of the time, it's an automatic thing  
                that happens when the system is being rebooted, so  
                it's harmless. If you have a crontab running, the  
                bot will get restarted when the system is back  
                online. Occasionally the system administrator will  
                kill the bot manually -- for example, if he/she  
                doesn't want bots running on the system.  
   
           5. MY COMPILE DIES AT THE LAST MINUTE WITH "LD FATAL SIGNAL  
           11"!  
   
                This happens on Linux machines that have recently  
                been converted to ELF by upgrading to Slackware  
                3.0. Apparently Slackware 3.0 comes with a non-ELF  
                (a.out) Tcl library, and the compiler doesn't  
                handle that well. (It should give you an error;  
                instead it barfs.) Fixing it is tricky because  
                even if you recompile libtcl.a, the linker will  
                most likely find the "bad" one first, and your  
                work will be in vain.  
   
                Here's a fix that's been floating around on the  
                eggdrop list:  
   
                     1. Recompile 'libtcl.a' for yourself, to  
                     make sure an ELF librar is created.  
                     2. Copy it into your eggdrop/src  
                     directory, naming it 'libtcl2.a'.  
                     3. Edit the Makefile and change the line  
                     that says '-L/usr/lib -ltcl' to '-L.  
                     -ltcl2'.  
                     4. Recompile eggdrop.  
   
                Also send hate-mail to the Slackware guy telling  
                him to stop messing up the libraries. He seemed to  
                assume that everyone would still want to compile  
                old-style (a.out) binaries.  
   
           6. SOMEONE ELSE SET UP A BOT I DON'T LIKE. ARE THERE ANY  
           BACKDOORS I CAN USE TO TAKE THEIR BOT DOWN?  
   
                No, there have never been any backdoors and there  
                never will be, so please stop asking. Every once  
                in a while, someone finds a way to exploit a bug  
                in eggdrop, but we fix these bugs as soon as we  
                find out about them. If you want to bring down  
                someone else's bot, you will not have my/our help.  
   
           7. WHAT ARE MODULES?  
   
                Modules are a way of adding extra C code from the  
                bot, much like Tcl scripts, without requiring the  
                bot recompiling, see doc/MODULES for more info.  
   
           8. CAN I COMPILE EGGDROP WITHOUT DYNAMIC MODULES?  
   
                Yes, you can, if ./configure detects that your  
                system CAN'T run modules it will setup 'make' to  
                link the modules in statically for you, you can  
                also choose this option if you can do dynamic  
                modules by typing 'configure --disable-shared'.  
   
                8.1 DO I STILL NEED TO 'loadmodule modules' ???  
   
                     YES, when you compile statically, all  
                     the modules are linked into the main  
                     executable *but* they are not enabled  
                     until you use loadmodule to enable then,  
                     hence you get nearly the same  
                     functionality with static modules as  
                     dynamic modules.  
   
           9. WHERE CAN I GET A PRECOMPILED EGGDROP FOR MY COMPUTER?  
   
                It is HIGHLY recommended AGAINST using precompiled  
                Eggdrops from untrusted sources. Eggdrop has been  
                a regular target for hacking and crashing.  
                Distribution of precompiled (binary) versions of  
                Eggdrop are the easiest way of hackers to provide  
                you with the easiest (and most dangerous) way of  
                gaining access to not only your bot, but to your  
                computer account directly. Don't advertise your  
                precompiled eggdrop binary sites on the eggdrop  
                list either =P  
   
           10. I GET 'Makefile:3 :invalid operator' OR SOME-SUCH-THING  
           WHEN I TRY TO 'make'  
   
                Try 'gmake'  
   
           11. WHEN I 'tclsh scripts/weed <userfile> c' IT BARFS CHUNKS  
           AT ME AND DIES :(  
   
                UPGRADE YOUR TCL, you are probably using tcl 7.5  
                or earlier, some of the commands in weed require  
                tcl7.6 to run, so either upgrade it, or removing  
                the offending lines from you userfile (those  
                starting with '.' generally) and accept the loss  
                of that data.  
   
           12. I get "ld-elf.so.1: Shared object "libtcl80.so.1" not  
           found" or "eggdrop: error in loading shared libraries /  
           libtcl8.1.so: cannot open shared object file: No such file  
           or directory" when I try to start my bot.  
   
                './configure' is looking in the wrong place for  
                tcl; it looks like it compiled with one version of  
                tcl and tries to load another. Maybe your sysadmin  
                upgraded tcl and didn't tell you. In that case,  
                you should just need to recompile your bot.  
   
                Or maybe when upgrading he didn't clean the old  
                version of tcl, and './configure' is looking for  
                the files in the wrong places, or trying to use  
                different versions of tcl.h and libtcl*. Smack  
                your admin and have him install tcl properly ;) Or  
                try to:  
   
                ./configure --with-tcllib=<path-to-tcl-lib>  
                --with-tclinc=<path-to-tcl-inc>  
   
                tell configure where to look for the tcl files.  
                try to look for them like:  
                for libtcl:  
   
                     ls /usr/lib/libtcl*  
                     ls /usr/local/lib/libtcl*  
   
                for tcl.h:  
   
                     ls /usr/include/tcl.h  
                     ls /usr/local/include/tcl.h  
   
                If everything else fails, try to install tcl to  
                your home dir ;) (Suggested by dw@Undernet,  
                dw@lixom.nu)  
   
           13. I get a whole pile of "Unresolved symbol  
           'Tcl_AppendResult'" (or some other symbol) when I try to  
           load a modules.  
   
                POSSIBILITY A: see 12.  
   
                POSSIBILITY B:  
   
                Some of the standard libraries have been compiled  
                for static linking only on your machine, you have  
                3 options:  
   
                (1) if it's your own machine, recompile TCL using  
                dynamic linking by using './configure  
                --enable-shared' when you configure TCL (not the  
                bot) and then remake, & reinstall  
                (2) if it's not you machine, you make have to  
                resort to './configure --disable-shared'.  
                (3) if you are of a more aggressive sense of mind,  
                go beat the stuffing out of your admin for have  
                lame static libraries :)  
   
      (6) SETTING UP A CRONTAB  
   
           Eggdrop has become more stable with time, thanks mostly to  
           people reporting bug details and helping find places where  
           it crashes. However, there are still a -few- places where  
           things aren't perfect. Few if any things in life are.  
   
           Also, most systems go down from time to time. These things  
           cause your bot to disappear from IRC, and you have to  
           restart it.  
   
           The eggdrop source file includes a csh script called  
           'botchk' that will help keep the bot online. It will make  
           the machine check every ten minutes to make sure your bot is  
           still running. To use it, you have to add a line to your  
           crontab. First, edit 'botchk' and change the directory and  
           command line parameters so that it will be able to start up  
           your bot. Then, add this line to your crontab:  
   
           0,10,20,30,40,50 * * * * /home/mydir/botchk  
   
           If you don't want to get emails from cron, put this:  
   
           0,10,20,30,40,50 * * * * /home/mydir/botchk >/dev/null 2>&1  
   
           Naturally, you need to change the path to the correct path  
           for botchk. If you've never used crontab before, here is a  
           simple way to add that line: Create a new file called  
           'mycron' and put the above line into it. Then, from your  
           shell prompt, type % crontab mycron That will create a new  
           crontab entry for you, with a line that runs botchk every  
           ten minutes. Botchk will then restart the bot when necessary  
           (and send you email informing you).  
   
      (6a) SETTING UP A CRONTAB USING AUTOBOTCHK  
   
           Included with your eggdrop is an eggdrop utility called  
           'autobotchk'. Using autobotchk is probably the fastest way  
           of creating your botchk and crontabbing it with just a few  
           required steps.  
   
           To crontab your bot follow the following steps:  
   
           (1) type 'cp scripts/autobotchk ..'  
           (2) type './autobotchk <eggdrop config file>'  
   
           This will hopefully crontab your bot using the default  
           setup. If you want a list of autobotchk options, type  
           './autobotchk'. An example with options would be:  
   
           ./autobotchk <eggdrop config file> -noemail -5  
   
           This would setup crontab to run the botchk every 5 minutes  
           and also to not send you e-mail saying that it restarted  
           your bot.  
   
      (7) BORING LEGAL STUFF  
   
           The eggdrop bot is copyright (C) by Robey Pointer. As of  
           January 1997, eggdrop is distributed according to the GNU  
           General Public License. There should be a copy of this  
           license in the file COPYING. If not, write to the Free  
           Software Foundation, Inc., 59 Temple Place, Suite 330,  
           Boston, MA  02111-1307  USA  
   
           As of eggdrop1.3.28 all changes made by the Eggheads  
           development team to the eggdrop source code and any related  
           files are copyright (C) by Eggheads. The source code will  
           still be distributed according to the GNU General Public  
           License as Robey Pointer did in the past.  
   
           Releases previous to 1.0m were made using a different  
           licensing scheme. You may, at your option, use the GNU  
           General Public License on those versions (instead of the  
           license packaged with them) with my blessing. [Robey Pointer]  
           For any versions bearing a copyright date of 1997 or later,  
           you have no choice -- you must use the GNU General Public  
           License.  
   
           The files "match.c", "net.c", and "blowfish.c" are exempt  
           from the above restrictions. "match.c" is original code by  
           Chris Fuller (email: crf@cfox.bchs.uh.edu) and has been  
           placed by him into the public domain. "net.c" is by me and I  
           [Robey Pointer] also choose to place it in the public domain.  
           "blowfish.c" is by various sources and is in the public  
           domain. All 3 files contain useful functions that could  
           easily be ported to other applications -- the other parts of  
           the bot generally don't.  
   
           Tcl is by John Ousterhout and is in no way affiliated with  
           eggdrop, and likely has its own set of copyrights and  
           whatnots.  
   
           There is no warranty, implied or whatever. You use this  
           software at your own risk, no matter what purpose you put it  
           to.  
   
           You didn't pay for it, so don't expect magic.  
   
      (8) MAILING LIST  
   
           There are currently a couple of mailing lists about eggdrop.  
           eggheads@eggheads.org is the one relevant for posts about  
           eggdrop 1.4 and up (and bug fixes, and suggestions, etc).  
   
           To subscribe to the eggheads mailing list, send email to:  
           eggheads-request@eggheads.org In the body of the message,  
           put "subscribe eggheads"; or go to  
           http://scrambled.eggheads.org/mailman/listinfo/eggheads  
   
                   ### DO NOT SEND ROBEY EMAIL ABOUT EGGDROP ###  
   
           Robey is no longer developing the eggdrop code so don't bother  
           emailing him. If you have a serious problem, email the  
           eggdrop mailing list and it will get to the coders.  
   
           Please, before posting to this list, see what things are  
           like, and when you do post, read over your post for  
           readability, spelling, and grammar mistakes. Obviously,  
           we're all human (or are we?) and we all make mistakes (heck,  
           look at this document! ;).  
   
           Open discussion and debate is integral to change and  
           progress. Don't flame others over mere form (grammar and  
           spelling), or even substantive issues either for that  
           matter. Please read and follow the mailing list rules.  
   
           The eggheads@eggheads.org maillist is not dedicated to those  
           all too common questions we have all seen on other lists...  
           for example:  
   
           "Why does my bot say this: Please edit your config file."  
           "How do I telnet my bot?"  
           "Where do I get eggdrop for windows??????"  
           etc..  
   
           Technical questions, your thoughts or suggestions on new  
           features being added to Eggdrop, things that should be  
           removed or fixed, amazing problems that even stump the  
           guru's, etc... are what we want to see here.  
   
           Bug reports should be sent to bugs@eggheads.org.  Please read  
           and fill out the BUG-REPORT file in the doc directory.  
   
      (9) DOCUMENTATION  
   
           We're trying to keep the documentation up to date. If you  
           feel that anything is missing here, or that anything should  
           be added etc, please email eggheads@eggheads.org about it,  
           thank you.  
   
      (10) OBTAINING HELP  
   
           There is currently no uniform channel in existence to  
           support eggdrop. At one time, such channels did exist, but  
           they most often deteriorate into a vanity channel, where no  
           one is willing to help.  
   
           However, we'll list a few places here where you *might* get  
           help. Note though that we are not responsible for those  
           channels, or necessarily run those channels ourselves.  
   
           Undernet - #eggdrop, #eggheads  
           EFNet - #egghelp, #eggfaq  
           IRCNet - #eggdrop  
   
           However, if you are going to ask some questions there, we can give  
           you some important advices:  
           - don't ask if you may ask or anyone awake, just ask and wait  
           - don't msg people without their agreement, if they know help and  
             have time, they will answer.  
           - don't repeat yourself. This will result in being kicked  
           - don't use !!, colours or only CAPITAL letters.  
150    
151            If there are any serious places that should be added, let us      Most people never use any of the options except -m, and you usually only
152            know.      need to use that once.
153    
154    
155      (4) BORING LEGAL STUFF
156    
157        The Eggdrop bot is copyright (C) by Robey Pointer. As of January, 1997,
158        Eggdrop is distributed according to the GNU General Public License. There
159        should be a copy of this license in the file 'COPYING'. If not, write to
160        the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
161    
162        As of eggdrop1.3.28, all changes made by the Eggheads development team to
163        the Eggdrop source code and any related files are copyright (C) by
164        Eggheads. The source code will still be distributed according to the GNU
165        General Public License as Robey Pointer did in the past.
166    
167        Releases previous to 1.0m were made using a different licensing scheme.
168        You may, at your option, use the GNU General Public License on those
169        versions (instead of the license packaged with them) with my blessing.
170        For any versions bearing a copyright date of 1997 or later, you have
171        no choice -- you must use the GNU General Public License.
172    
173        The files "match.c", "net.c", and "blowfish.c" are exempt from the above
174        restrictions. "match.c" is original code by Chris Fuller (email:
175        crf@cfox.bchs.uh.edu) and has been placed by him into the public domain.
176        "net.c" is by me, and I [who?] also choose to place it in the public
177        domain. "blowfish.c" is by various sources and is in the public domain
178        as well. All 3 files contain useful functions that could easily be
179        ported to other applications.
180    
181        There is no warranty, implied or whatever. You use this software at your
182        own risk, no matter what purpose you put it to.
183    
184    
185      (5) MAILING LIST
186    
187        If you are interested in Eggdrop 1.7, and/or the development of Eggdrop,
188        the eggdev@eggheads.org mailing list focuses on these topics.
189    
190        To subscribe to the eggdev mailing list, send an e-mail to wcc@eggheads.org
191        explaining why you would like to be a part of the list. Then visit the
192        following url to subscribe to the list:
193    
194          http://scrambled.eggheads.org/mailman/listinfo/eggdev
195    
196        NOTE: All subscribe requests not accompanied by an e-mail to
197        wcc@eggheads.org WILL be rejected.
198    
199        ### DO NOT SEND ROBEY EMAIL ABOUT EGGDROP! ###
200    
201        Robey is no longer developing the Eggdrop code, so don't bother e-mailing
202        him. If you have a serious problem, email the eggheads mailing list and
203        it will get to the coders.
204    
205        Please, before posting to this list, see what things are like. When you do
206        post, read over your post for readability, spelling, and grammar mistakes.
207    
208        DO NOT SEND HTML E-MAILS TO ANY OF THE EGGHEADS.ORG MAILING LISTS. ANYONE
209        CAUGHT SENDING HTML E-MAILS TO ONE OF THESE LISTS WILL BE REMOVED
210        IMMEDIATELY!
211    
212    
213      (6) DOCUMENTATION
214    
215        We're trying to keep the documentation up to date. If you feel that
216        anything is missing here or that anything should be added, etc, please
217        email docteam@eggheads.org about it. Thank you.
218    
219    
220      (7) OBTAINING HELP
221    
222        See 'MAILING LIST' (5). IRC support is NOT available for Eggdrop 1.7 at
223        this time.
224    
225      ________________________________________________________________________
226    
   ------------------------------------------------------------------------  
227  Copyright (C) 1997 Robey Pointer  Copyright (C) 1997 Robey Pointer
228  Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 Eggheads Development Team  Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 Eggheads Development Team
229    

Legend:
Removed from v.1.24  
changed lines
  Added in v.1.25

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23