/[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.35 - (show annotations) (download)
Thu Nov 27 02:44:11 2003 UTC (15 years, 6 months ago) by wcc
Branch: MAIN
Changes since 1.34: +2 -2 lines
* Round 2.

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23