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

Contents of /eggdrop1.6/README

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


Revision 1.24 - (show annotations) (download)
Sat Mar 9 21:14:14 2002 UTC (17 years, 7 months ago) by wcc
Branch: MAIN
Changes since 1.23: +325 -290 lines
more doc updates

1 README
2 Last revised: March 08, 2002
3 ________________________________________________________________________
4
5 Please at least SKIM this document before asking questions. In fact,
6 READ IT if you've never successfully set up an Eggdrop bot before.
7 PLEASE! READ IT!
8
9 Contents
10
11 0 Important notice
12 1 What is Eggdrop?
13 2 How do I get Eggdrop?
14 2a How to get the latest version of Eggdrop via CVS
15 3 Quick startup
16 4 Upgrading
17 4a Upgrading from a pre-1.3 version to 1.6
18 4b Upgrading from an older 1.3/1.4/1.5/1.6 version to a newer one
19 5 Command line
20 6 Frequently Asked Questions
21 1. What do I do if I get the error "User file not found"?
22 2. My Eggdrop won't run; It just says "Can't find your
23 hostname!"
24 3. What the Heck is Tcl?
25 4. My bot dies and the last entry in the logfile is "Received
26 terminate signal". What does that mean and can I prevent it?
27 5. My compile dies at the last minute with "LD fatal signal
28 11"!
29 6. Someone else set up a bot I don't like. Are there any
30 backdoors I can use to take their bot down?
31 7. What are modules?
32 8. Can I compile Eggdrop without dynamic modules?
33 8.1. Do I still need to "loadmodule" modules?
34 9. Where can I get a pre-compiled Eggdrop for my computer?
35 10. I get "Makefile:3 : invalid operator" or some such thing
36 when I try to "make".
37 11. When I "tclsh scripts/weed <userfile> c" It barfs chunks at
38 me and dies.
39 12. I get "ld-elf.so.1: Shared object "libtcl80.so.1" not found"
40 or "eggdrop: error in loading shared libraries /
41 libtcl8.1.so: cannot open shared object file: No such file
42 or directory" when I try to start my bot.
43 13. I get a whole pile of "unresolved symbol 'Tcl_AppendResult'"
44 (or some other symbol) when I try to load a module.
45 7 Setting up a crontab
46 6a Setting up a crontab using autobotchk
47 8 Boring legal stuff
48 9 Mailing list
49 10 Documentation
50 11 Obtaining help
51
52 ________________________________________________________________________
53
54 (0) NOTICE
55
56 Please read this file carefully before trying to set up Eggdrop.
57 Also, make SURE that you select your +n (owner) users wisely!
58 They have 100% access to your bot and account! ONLY GIVE THIS
59 POWER TO SOMEONE YOU TRUST COMPLETELY!!
60
61 (1) WHAT IS EGGDROP?
62
63 Eggdrop is the world's most popular Internet Relay Chat (IRC)
64 bot; it is freely distributable under the GNU General Public
65 License (GPL). Eggdrop is a feature rich program designed to be
66 easily used and expanded upon by both novice and advanced IRC
67 users on a variety of hardware and software platforms.
68
69 An IRC bot is a program that sits on an IRC channel and preforms
70 automated tasks while looking just like a normal user on the
71 channel. Some of these functions include protecting the channel
72 from abuse, allowing privileged users to gain op or voice status,
73 logging channel events, providing information, hosting games, etc.
74
75 One of the features that makes eggdrop stand out from other bots
76 is module and Tcl scripting support. With scripts and modules,
77 you can make the bot preform almost any task you want. They can
78 do anything from preventing floods to greeting users and banning
79 advertisers from channels.
80
81 You can also link multiple Eggdrop bots together to form a botnet.
82 This can allow bots to op each other securely, control floods
83 efficiently, and even link channels across multiple IRC networks.
84 It also allows the Eggdrops share user lists, ban lists,
85 exempt/invite lists, and ignore lists with other bots if userfile
86 sharing is enabled. This allows users to have the same access on
87 every bot on your botnet. It also allows the bots to distribute
88 tasks such as opping and banning users. See doc/BOTNET for
89 information on setting up a botnet.
90
91 Eggdrop is always being improved and adjusted because there are
92 bugs to be fixed and features to be added (if the users demand
93 them, and they make actually sense). In fact, it existed for
94 several years as v0.7 - v0.9 before finally going 1.0. This
95 version of Eggdrop is part of the 1.6 tree. A valiant effort
96 has been made to chase down and destroy bugs.
97
98 This README file contains information about how to get Eggdrop,
99 command line options for Eggdrop, what you may need to do when
100 upgrading from older versions, a list of frequently asked
101 questions, how to set up a crontab, some boring legal stuff, info
102 about the mailing list (a great place to ask questions, and a good
103 place to report bugs, too), some basics about CVS usage, and some
104 channels where you might get help with Eggdrop.
105
106
107 (2) HOW TO GET EGGDROP
108
109 Before you can compile Eggdrop, you need to have Tcl installed
110 on your system. Most systems should have Tcl on them by now --
111 you can check by trying the command "tclsh". If it works, you
112 will be given a "%" prompt, and you can type "exit" to exit the
113 program. This means Tcl is installed on your system. If tclsh
114 doesn't load, then Tcl probably isn't on your system, and you
115 will need to install it.
116
117 The best ftp site for Tcl is ftp://ftp.scriptics.com/pub/tcl.
118
119 Tcl comes with the Slackware distribution of Linux. HOWEVER,
120 the one that comes on Slackware 3.0 is goofed up and you'll
121 have to re-install it for yourself to get it working.
122
123 Currently, the 1.6 tree of Eggdrop is developed at
124 eggheads.org. You can get the latest version of Eggdrop from
125 ftp://ftp.eggheads.org/pub/eggdrop/source/eggdrop-latest.tar.gz.
126
127 You might try www.eggheads.org for help and information.
128
129
130 (2a) CVS USAGE
131
132 You can obtain the VERY LATEST version of Eggdrop, that is still
133 under development, by using CVS. CVS means 'Concurrent Versions
134 System' and is a tool for developers to always keep source code
135 up to date. Try 'man cvs' on your shell for more information about
136 CVS.
137
138 This is intended only for users that know a good bit about Eggdrop.
139 Be aware that the versions of Eggdrop that you get via CVS are still
140 being developed, and may be buggy. The Eggheads devteam will in
141 NO WAY take any responsibility for whatever might happen to you or
142 your shell if you use a CVS version of Eggdrop.
143
144 To obtain Eggdrop over CVS, do as follows:
145
146 (1) Log into your shell.
147
148 (2) Type 'export CVSROOT=:pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot'.
149
150 (3) Type 'cvs login'.
151
152 (4) Press <enter> when prompted for a password.
153
154 (5) In your home dir, type 'cvs checkout eggdrop1.6'
155
156 (6) In ~/eggdrop1.6, you should have a copy of the latest
157 CVS version of Eggdrop.
158
159 Notes:
160
161 (1) You can 'cvs logout', but you don't need to.
162
163 (2) You don't need to go through this whole process every
164 time. If you want to get a CVS version of Eggdrop at a
165 later time, you can just 'cd ~/eggdrop1.6' and type 'cvs
166 update -dAP'.
167
168 (3) If you experience errors when using 'export', you might
169 be using tclsh as a shell. If so, try using the command
170 'setenv' instead of 'export':
171
172 setenv CVSROOT :pserver:anonymous@cvs.eggheads.org:/usr/local/cvsroot
173
174 (3) QUICK STARTUP
175
176 Please see the 'INSTALL' file AFTER you finish reading this file.
177
178 (4) UPGRADING
179
180 (4a) UPGRADING FROM A PRE-1.3 VERSION TO 1.6
181
182 #### BACK UP YOUR USERFILE ####
183
184 We can't stress this enough. If you are upgrading and
185 you have even a slight possibility of downgrading again
186 later, you will HAVE to back up your userfile, or you will
187 lose it. v1.3 of Eggdrop radically changed a lot of things.
188
189 There are many major changes between v0.9, v1.0, v1.1 and
190 v1.6, so PAY ATTENTION to this part if you have a v0.9, 1.0
191 or 1.1 bot currently. If you're just starting out, you can
192 skip this section.
193
194 If you run share bots, you will need to upgrade them all at
195 the same time because of the new userfile format. Older bots
196 will be able to link in, but will not get or send a userfile.
197 MAKE A NEW CONFIG FILE from the example; there are some radical
198 changes.
199
200 If you are upgrading from 0.9/1.0 to 1.6, just redo the whole
201 thing. Absolutely everything has changed, including the
202 userfile and config file formats.
203
204 If you are upgrading from 1.1/1.2 to 1.6, you will likely want
205 to redo the config file, as much as changed. BACK UP! You will
206 need to run 'tclsh scripts/weed/<userfile> c' to convert your
207 userfile from v3 (1.1/1.2) to v4 (1.3/1.4/1.5/1.6).
208
209 (4b) UPGRADING FROM AN OLDER 1.3/1.4/1.5/1.6 VERSION TO A NEWER 1.6
210 VERSION
211
212 If you followed the 'INSTALL' file and did a 'make install'
213 (or 'make install DEST="path"') after 'make', this will be
214 pretty easy. Just upload the new eggdrop1.6.x.tar.gz file to
215 your home dir on your shell, gunzip and untar it, and type
216 'cd ~/eggdrop1.6.x'. Next, type './configure', 'make config'
217 or 'make iconfig', then 'make'. Then, kill the bot ('.die' on
218 the party line), and 'make install' to the same directory your
219 bot is currently in. After that, you can just restart your
220 bot. You may wish to delete the old Eggdrop executable and
221 modules as well, especially if you have limited disk space.
222
223 You should read through the new eggdrop.complete.conf file
224 for all the new options in Eggdrop 1.6.x if you are upgrading
225 from 1.3.x or 1.4.x. You can copy and paste any of these
226 settings into you current conf file if you do not want to use
227 the default settings.
228
229 (5) COMMAND LINE
230
231 Eggdrop has some command-line options -- not many, because most
232 things should be defined through the config file. However, sometimes
233 you may want to start up the bot in a different mode, and the
234 command-line options let you do that. Basically, the command line
235 for Eggdrop is:
236
237 % eggdrop [options] [config-file]
238
239 The options available are:
240
241 -n: Don't background. Normally, Eggdrop will move itself into the
242 background when you start it up, meaning you'll get another
243 shell prompt, and you can do other things while the bot is
244 running. With -n, you won't return to the shell prompt until
245 the bot exits (which won't normally happen until it's killed).
246 By default, -n will send all log entries to the console.
247
248 -nt: Don't background, use terminal. This is just like -n, except
249 that instead of seeing log entries, your console will simulate
250 a DCC chat with the bot.
251
252 -nc: Don't background, show channel info. This is just like -n,
253 except that instead of seeing log entries, every 10 seconds
254 your screen will clear and you will see the current channel
255 status, sort of like "top".
256
257 -m: Create userfile. If you don't have a userfile, this will make
258 Eggdrop create one and give owner status to the first person
259 that introduces himself or herself to it. You'll need to do
260 this when you first set up your bot.
261
262 -v: Show version info, then quit.
263
264 Most people never use any of the options except -m, and you usually
265 only need to use that once.
266
267 (6) FREQUENTLY ASKED QUESTIONS (or "Why doesn't this thing work?")
268
269 1. WHAT DO I DO IF I GET THE ERROR "USER FILE NOT FOUND"?
270
271 (1) Run Eggdrop with the "-m" option (i.e., "eggdrop
272 -m eggdrop.conf").
273
274 (2) Go to IRC and send "hello" to your bot (i.e., "/msg mybot
275 hello").
276
277 (3) You will become an owner on your bot. You can leave the
278 bot running (nobody else will become an owner if they say
279 "hello"), but in the future, don't use the "-m" option
280 when running the bot.
281
282 2. MY EGGDROP WON'T RUN; IT JUST SAYS "CAN'T FIND YOUR
283 HOSTNAME!"
284
285 Your machine is set up strangely, and Eggdrop can't
286 figure out its network hostname. You can get around this by
287 setting the my-ip setting in the config file correctly.
288
289 3. WHAT THE HECK IS Tcl?
290
291 Tcl is a scripting language written by John Ousterhout. It's
292 much better than most "built-in" script languages (like the
293 one in ircII) and is meant to be linked with anything needing
294 a scripting language, so I linked it with Eggdrop. The file
295 "tcl-commands.doc" in the doc directory contains a list of
296 additional Tcl commands provided by Eggdrop. There are also
297 several example scripts in the scripts/ directory, and one
298 in the doc directory called first_script.txt. There are also
299 hundreds of scripts floating around on the ftp/web sites if
300 you like working by example (which is typically the best way).
301
302 4. MY BOT DIES, AND THE LAST ENTRY IN THE LOGFILE IS "RECEIVED
303 TERMINATE SIGNAL". WHAT DOES THAT MEAN, AND CAN I PREVENT IT?
304
305 There's nothing you can do to prevent it. It means the
306 system administrator is killing the Eggdrop process. Most
307 of the time, it's an automatic thing that happens when the
308 system is being rebooted, so it's harmless. If you have a
309 crontab running, the bot will get restarted when the system
310 is back online. Occasionally, the system administrator will
311 kill the bot manually. For example, if he/she doesn't want
312 bots running on the system.
313
314 5. MY COMPILE DIES AT THE LAST MINUTE WITH "LD FATAL SIGNAL
315 11"!
316
317 See doc/compiling.FAQ.
318
319 6. SOMEONE ELSE SET UP A BOT I DON'T LIKE. ARE THERE ANY
320 BACKDOORS I CAN USE TO TAKE THEIR BOT DOWN?
321
322 No, there have never been any backdoors and there never will
323 be, so please stop asking. Every once in a while, someone
324 finds a way to exploit a bug in Eggdrop, but we fix these
325 bugs as soon as we find out about them. If you want to bring
326 down someone else's bot, you will not have my/our help.
327
328 7. WHAT ARE MODULES?
329
330 Modules are a way of adding extra features to the bot, much
331 like Tcl scripts, without requiring the bot to be recompiled.
332 See doc/MODULES for more information.
333
334 8. CAN I COMPILE EGGDROP WITHOUT DYNAMIC MODULES?
335
336 Yes, you can. If the configure script detects that your system
337 CAN'T run modules, it will setup 'make' to link the modules in
338 statically for you. You can choose this option yourself by
339 using 'make static'. You can also try to compile dynamic
340 modules on a static-only system by using 'make eggdrop'.
341
342 8.1 DO I STILL NEED TO 'loadmodule' MODULES?
343
344 YES, when you compile statically, all the modules are linked
345 into the main executable. HOWEVER, they are not enabled
346 until you use loadmodule to enable them, hence you get nearly
347 the same functionality with static modules as with dynamic
348 modules.
349
350 9. WHERE CAN I GET A PRE-COMPILED EGGDROP FOR MY COMPUTER?
351
352 It is HIGHLY recommended AGAINST using pre-compiled Eggdrops
353 from un-trusted sources. Eggdrop has been a regular target
354 for hacking and crashing. Distribution of pre-compiled
355 (binary) versions of Eggdrop are the easiest way for hackers
356 to provide you with the easiest (and most dangerous) way of
357 gaining access to, not only your bot, but to your computer
358 account directly. Don't advertise your pre-compiled Eggdrop
359 binary sites on the Eggdrop list either. =P
360
361 10. I GET 'Makefile:3 :invalid operator' OR SOME-SUCH-THING
362 WHEN I TRY TO 'make'.
363
364 Try 'gmake'.
365
366 11. WHEN I 'tclsh scripts/weed <userfile> c' IT BARFS CHUNKS
367 AT ME AND DIES. :(
368
369 Upgrade your Tcl. You are probably using Tcl 7.5 or earlier.
370 Some of the commands in weed require Tcl7.6 to run, so either
371 upgrade it or remove the offending lines from you userfile
372 manually (those starting with '.' generally) and accept the
373 loss of that data.
374
375 12. I GET "ld-elf.so.1: Shared object "libtcl80.so.1" not found"
376 or "eggdrop: error in loading shared libraries libtcl8.1.so: \
377 cannot open shared object file: No such file or directory" WHEN
378 I TRY TO START MY BOT.
379
380 './configure' is looking in the wrong place for Tcl; it looks
381 like it compiled with one version of Tcl and tries to load
382 another. Maybe your sysadmin upgraded Tcl and didn't tell
383 you. In that case, you should just need to recompile your
384 bot.
385
386 Maybe, when upgrading, he didn't clean the old version of
387 Tcl and './configure' is looking for the files in the wrong
388 places, or trying to use different versions of tcl.h and
389 libtcl*. Smack your admin and have him install Tcl properly. ;)
390
391 You can also try:
392
393 ./configure --with-tcllib=<path-to-tcl-lib>
394 --with-tclinc=<path-to-tcl-inc>
395
396 Tell configure where to look for the Tcl files.
397
398 Try looking for libtcl by:
399
400 ls /usr/lib/libtcl*
401 ls /usr/local/lib/libtcl*
402
403 Try looking for tcl.h by:
404
405 ls /usr/include/tcl.h
406 ls /usr/local/include/tcl.h
407
408 If everything else fails, try to install Tcl to your home
409 dir ;) (Suggested by dw@Undernet, dw@lixom.nu)
410
411 13. I GET A WHOLE PILE OF "Unresolved symbol 'Tcl_AppendResult'"
412 (OR SOME OTHER SYMBOL) WHEN I TRY TO LOAD A MODULES.
413
414 POSSIBILITY A: See section 12.
415
416 POSSIBILITY B:
417
418 Some of the standard libraries have been compiled for static
419 linking only on your machine, you have 3 options:
420
421 (1) If it's your own machine, recompile Tcl using dynamic
422 linking by using './configure --enable-shared' when you
423 configure Tcl (not the bot) and then remake, and reinstall.
424
425 (2) If it's not your machine, you make have to resort to 'make
426 static' and 'make install DEST="path"' to make and install
427 your bot.
428
429 (3) If you are of a more aggressive sense of mind, go beat
430 the stuffing out of your admin for having lame static
431 libraries. :)
432
433 (7) SETTING UP A CRONTAB
434
435 Eggdrop has become more stable with time, thanks mostly to people
436 reporting bug details and helping find places where it crashes.
437 However, there are still a -few- places where things aren't
438 perfect. Few, if any, things in life are.
439
440 Also, most systems go down from time to time. These things cause
441 your bot to disappear from IRC, and you have to restart it.
442
443 Eggdrop comes with a shell script called 'botchk' that will help
444 keep the bot online. It will make the machine check every ten
445 minutes to make sure your bot is still running. To use it, you
446 have to add a line to your crontab. First, edit 'botchk' and
447 change the directory and command line parameters so that it will
448 be able to start up your bot. Then, add this line to your crontab:
449
450 0,10,20,30,40,50 * * * * /home/mydir/botchk
451
452 If you don't want to get e-mails from cron, use this:
453
454 0,10,20,30,40,50 * * * * /home/mydir/botchk >/dev/null 2>&1
455
456 Naturally, you need to change the path to the correct path for
457 botchk. If you've never used crontab before, here is a simple way
458 to add that line:
459
460 (1) Create a new file called 'mycron' and put the above
461 line into it.
462
463 (2) From your shell prompt, type '% crontab mycron'.
464
465 That will create a new crontab entry for you with a line that
466 runs botchk every ten minutes. Botchk will then restart the bot
467 when necessary (and send you email informing you).
468
469 (7a) SETTING UP A CRONTAB USING AUTOBOTCHK
470
471 Included with your Eggdrop is an Eggdrop utility called
472 'autobotchk'. Using autobotchk is probably the fastest way of
473 creating your botchk and crontabbing it with just a few required
474 steps.
475
476 To crontab your bot, follow these steps:
477
478 (1) Type 'cp scripts/autobotchk ..'.
479
480 (2) Type './autobotchk <Eggdrop config file>'.
481
482 This will hopefully crontab your bot using the default setup.
483 If you want a list of autobotchk options, type './autobotchk'.
484 An example with options would be:
485
486 ./autobotchk <Eggdrop config file> -noemail -5
487
488 This would setup crontab to run the botchk every 5 minutes and
489 also to not send you e-mail saying that it restarted your bot.
490
491 (8) BORING LEGAL STUFF
492
493 The Eggdrop bot is copyright (C) by Robey Pointer. As of January,
494 1997, Eggdrop is distributed according to the GNU General Public
495 License. There should be a copy of this license in the file
496 'COPYING'. If not, write to the Free Software Foundation, Inc.,
497 675 Mass Ave, Cambridge, MA 02139, USA.
498
499 As of eggdrop1.3.28, all changes made by the Eggheads development
500 team to the Eggdrop source code and any related files are copyright
501 (C) by Eggheads. The source code will still be distributed according
502 to the GNU General Public License as Robey Pointer did in the past.
503
504 Releases previous to 1.0m were made using a different licensing
505 scheme. You may, at your option, use the GNU General Public License
506 on those versions (instead of the license packaged with them) with
507 my blessing. For any versions bearing a copyright date of 1997 or
508 later, you have no choice -- you must use the GNU General Public
509 License.
510
511 The files "match.c", "net.c", and "blowfish.c" are exempt from
512 the above restrictions. "match.c" is original code by Chris Fuller
513 (email: crf@cfox.bchs.uh.edu) and has been placed by him into the
514 public domain. "net.c" is by me and I [who?] also choose to place
515 it in the public domain. "blowfish.c" is by various sources and is
516 in the public domain as well. All 3 files contain useful functions
517 that could easily be ported to other applications.
518
519 Tcl is by John Ousterhout and is in no way affiliated with Eggdrop.
520 It likely has its own set of copyrights and whatnots.
521
522 There is no warranty, implied or whatever. You use this software
523 at your own risk, no matter what purpose you put it to.
524
525 (9) MAILING LIST
526
527 There are currently a couple of mailing lists about Eggdrop.
528 eggheads@eggheads.org is the one relevant for posts about
529 Eggdrop 1.4 and up (suggestions, help, etc).
530
531 To subscribe to the eggheads mailing list, send e-mail to
532 eggheads-request@eggheads.org. In the body of the message, put
533 "subscribe eggheads". You can also go to the following url:
534
535 http://scrambled.eggheads.org/mailman/listinfo/eggheads
536
537 ### DO NOT SEND ROBEY EMAIL ABOUT EGGDROP ###
538
539 Robey is no longer developing the Eggdrop code, so don't bother
540 e-mailing him. If you have a serious problem, email the eggheads
541 mailing list and it will get to the coders.
542
543 Please, before posting to this list, see what things are like.
544 When you do post, read over your post for readability, spelling, and
545 grammar mistakes. Obviously, we're all human (or are we?) and we
546 all make mistakes (heck, look at this document! ;).
547
548 Open discussion and debate is integral to change and progress.
549 Don't flame others over mere form (grammar and spelling), or
550 even substantive issues for that matter. Please read and follow
551 the mailing list rules.
552
553 The eggheads@eggheads.org mailing list is not dedicated to those
554 all too common questions we have all seen on other lists... For
555 example:
556
557 o "Why does my bot say this: Please edit your config file."
558 o "How do I telnet my bot?"
559 o "Where do I get Eggdrop for windows??????"
560
561 Technical questions, your thoughts or suggestions on new features
562 being added to Eggdrop, things that should be removed or fixed,
563 amazing problems that even stump the guru's, etc. are what we want
564 to see here.
565
566 Bug reports should be sent to bugs@eggheads.org. Please read
567 and fill out the BUG-REPORT file in the doc directory.
568
569 DO NOT SEND HTML E-MAILS TO ANY OF THE EGGHEADS.ORG MAILING LISTS.
570 ANYONE CAUGHT SENDING HTML E-MAILS TO ONE OF THESE LISTS WILL BE
571 REMOVED IMMEDIATELY!
572
573 (10) DOCUMENTATION
574
575 We're trying to keep the documentation up to date. If you feel
576 that anything is missing here or that anything should be added,
577 etc, please email eggheads@eggheads.org about it. Thank you.
578
579 (11) OBTAINING HELP
580
581 You can obtain help with Eggdrop in the following IRC channels:
582
583 Undernet - #eggdrop, #eggheads
584 EFnet - #egghelp, #eggfaq
585 IRCnet - #eggdrop
586 DALnet - #eggdrop
587
588 If you plan to ask questions in any of the above channels,
589 you should be familiar with and follow IRC etiquette.
590
591 o Don't type using CAPITAL letters, colors, or bold, and don't use
592 "!" and "?" excessively.
593
594 o Don't /msg people without their permission.
595
596 o Don't repeat or paste large amounts of text to the channel.
597
598 If there are any other serious Eggdrop related channels that should
599 be added to the above list, please let us know.
600
601 ________________________________________________________________________
602
603 Copyright (C) 1997 Robey Pointer
604 Copyright (C) 1999, 2000, 2001, 2002 Eggheads Development Team

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23