1 
2                      ngIRCd - Next Generation IRC Server
3 
4                       (c)2001-2003 by Alexander Barton,
5                     alex@barton.de, http://www.barton.de/
6 
7                ngIRCd is free software and published under the
8                    terms of the GNU General Public License.
9 
10                     -- FAQ: Frequently Asked Questions --
11 
12 
13 I. General
14 ~~~~~~~~~~
15 Q: Is it possible to link the ngIRCd with non-ngIRCd servers?
16 A: Yes. ngIRCd is compatible to the original ircd used by IRCNet. Actually
17    this is being tested with version 2.10.3p3.
18 
19 Q: Is there a homepage with further information and downloads?
20 A: Yes. Please visit <http://ngircd.barton.de/>.
21 
22 Q: Why should I use ngIRCd instead of the original one?
23 A: ngIRCd offers several benefits: no problems with dynamic IPs, easy to
24    configure, open source (GPL), under active development.
25 
26 
27 II. Compilation
28 ~~~~~~~~~~~~~~~
29 Q: I did a "CVS checkout" but can't execute ./configure because the script
30    is missing in the generated directory!?
31 A: When using development versions via CVS, the configure script as well as
32    the Makefile.in templates must be generated using GNU automake and GNU
33    autoconf. To simplify this task run the ./autogen.sh script which will
34    execute the required tools for you; then continue with executing the
35    ./configure script as usual.
36 
37 Q: The ./autogen.sh script complains "aclocal: command not found".
38 A: GNU automake is missing on your system but required for building CVS
39    versions of ngIRCd. Install GNU automake 1.6 or later and try again.
40 
41 Q: The ./autogen.sh script stops with "autoheader: command not found".
42 A: GNU autoconf is missing on your system but required for building CVS
43    versions of ngIRCd. Install GNU autoconf 2.52 or later and try again.
44 
45 Q: The ./autogen.sh script fails and the message "automake: configure.in:
46    AM_INIT_AUTOMAKE must be used" is displayed.
47 A: Most probably you are using version 1.5 of GNU automake which seems to be
48    incompatible to the build system of ngIRCd. Solution: upgrade to at least
49    version 1.6 of GNU automake.
50    (If you are using Debian 3.0 "Woody" you can try to downgrade to version
51    1.4 of GNU automake shipped with this distribution; it should work, too.)
52 
53 
54 III. Runtime
55 ~~~~~~~~~~~~
56 
57 Q: I cannot connect to remote peers when I use the chroot option, the
58    following is logged: "Can't resolve example.com: unknown error!".
59 A: On Linux/glibc with chroot enabled you need to put some libraries inside
60    the chroot as well, notably libnss_dns; maybe others. Unfortunately, even
61    linking ngircd statically does not help this. The only known workaround
62    is to either disable chroot support or to link against dietlibc instead
63    of glibc. (tnx to Sebastian Siewior)
64 
65 
66 IV. Bugs!?
67 ~~~~~~~~~~
68 Q: Is there a list of known bugs and desired feature enhancements?
69 A: Yes. Have a look at the bug tracking system (Bugzilla) for ngIRCd located
70    at <http://ngircd.barton.de/bugzilla/index.cgi>. There you can file bug
71    reports and feature requests as well as search the bug database.
72 
73 Q: What should I do if I found a bug?
74 A: Please file a bug report at <http://ngircd.barton.de/bugzilla/index.cgi>!
75    The author of the particular component will be notified automagically :-)
76 
77 
78 -- 
79 $Id: FAQ.txt,v 1.12 2008/01/02 22:47:58 alex Exp $