1
--- deadwood-3.0.02/INSTALL.txt 2010-08-20 02:54:13.000000000 -0500
2
+++ deadwood-3.0.03/INSTALL.txt 2011-06-24 13:54:52.524103344 -0500
4
Deadwood is a recursive DNS program that is supported for two platforms:
5
-Windows XP (via MinGW) and CentOS Linux version 5. This program may or
6
+Windows XP (via MinGW) and Scientific Linux version 6. This program may or
7
may not work on other platforms, but will not be supported on any other
8
platform without some kind of support deal made (but see "Other platforms"
11
is a supplied document (doc\Windows\Vista.txt) that describes one way
12
to get Deadwood to run in Vista and Windows 7.
14
-The rest of this document deals with how to compile this code in CentOS 5,
15
-followed by a section on how to compile this code in Windows XP.
16
+The rest of this document deals with how to compile this code in Scientific
17
+Linux 6, followed by a section on how to compile this code in Windows XP.
20
+==SCIENTIFIC LINUX 6==
22
-To compile this program in CentOS 5, first set the environmental variable
23
-FLAGS to the flags you wish to give the compiler. For example, with gcc,
24
-you probably want to make the compile-time flags "-O3" unless you
25
-are making this as small as possible for an embedded system.
26
+To compile this program in Scientific Linux 6, first set the environmental
27
+variable FLAGS to the flags you wish to give the compiler. For example,
28
+with gcc, you probably want to make the compile-time flags "-O3" unless
29
+you are making this as small as possible for an embedded system.
31
To set tha flags to be "-O3" using a POSIX-compliant shell (Bash, ash, etc.):
35
Once the compile-time flags are set, the next step is to compile the
36
-program. If in CentOS 5, enter the src directory and use 'make' to do this:
37
+program. If in Scientific Linux 6, enter the src directory and use 'make'
41
- make -f Makefile.centos5
42
+ make -f Makefile.sl6
44
There is a single program compiled, Deadwood. Place this program where
45
it can be used. For example, to place this program in the directory
48
Of course, you may want to start up this program and run it as a
49
daemon when the system starts up. First, look at the text file
50
-dwood2rc (in the doc/ directory) and edit it. Then, make
51
+dwood3rc (in the doc/ directory) and edit it. Then, make
52
this file /etc/dwood3rc. For example:
57
You will also want to make a directory for Deadwood. This is the
58
-chroot_dir parameter in the dwood2rc file, and by default points to
59
+chroot_dir parameter in the dwood3rc file, and by default points to
64
The directory /etc/maradns/logger is needed for duende to run.
66
Now, you will want to edit your system start-up scripts to start
67
-up Deadwood. To do this in CentOS 5, make a file with the name
68
+up Deadwood. To do this in Scientific Linux 6, make a file with the name
69
/etc/init.d/deadwood with the following content:
73
ln -s ../init.d/deadwood S61deadwood
75
Note that system startup is variable between distributions and the above
76
-steps may not work if you're not using CentOS 5. If you wish help with
77
-using Deadwood with another version of Linux or *NIX, send me an email
78
-and we'll discuss rates. Or send an email to the MaraDNS list and someone
79
-(possibly me) may or may not help you.
80
+steps may not work if you're not using Scientific Linux 6. If you wish
81
+help with using Deadwood with another version of Linux or *NIX, send
82
+me an email and we'll discuss rates. Or send an email to the MaraDNS
83
+list and someone (possibly me) may or may not help you.
85
It is possible to compile Deadwood with IPv6 support, or with caching
86
disabled (which makes the binary a little smaller, for really tiny
88
The simplest way to run this program in Windows XP is to use the prebuilt
89
binary (.exe file) which should be in the same place as the place where
90
you obtained this source code, with a name like
91
-"Deadwood-2-X-XX-win32.zip" (or "Deadwood-2-X-XX-win32.7z").
92
+"Deadwood-3-0-XX-win32.zip" (or "Deadwood-3-0-XX-win32.7z").
94
The simplest way to compile this program in Windows XP is to use the
95
version of Deadwood bundled with the Tiny C Compiler and a batch file
96
called "tcc-compile.bat" which compiles Deadwood; this has a filename
97
-like "deadwood-tcc-2.X.XX.7z", but needs the 7-zip program
98
+like "deadwood-tcc-3.0.XX.7z", but needs the 7-zip program
99
(http://7.zip.org) or another program that can understand .7z files such
100
as WinRAR in order to decompress.
102
@@ -183,10 +184,11 @@
106
-Just because Deadwood is only fully supported in CentOS 5 and Windows XP
107
-doesn't mean Deadwood doesn't run on other platforms. It just means that,
108
-if you wish to run Deadwood on another platform, it's up to you to make
109
-the port. Or, if you prefer, pay me to make the port for you.
110
+Just because Deadwood is only fully supported in Scientific Linux 6
111
+and Windows XP doesn't mean Deadwood doesn't run on other platforms.
112
+It just means that, if you wish to run Deadwood on another platform,
113
+it's up to you to make the port. Or, if you prefer, pay me to make
116
I have made the code portable; there should not be any endian issues (this
117
has not been tested since I don't have access to a big-endian computer) nor
118
@@ -199,14 +201,15 @@
119
stdint.h for your compiler; I know there is a pstdint.h out there that
120
works with most Microsoft and Borland compilers.
122
-The CentOS 5 Makefile should work on other Linux variants, as well as other
123
-*NIX clones, but no guarantees. For example, there is a Cygwin Makefile
124
-included in the "src/" directory; I have verified that Deadwood 2.4 compiles
125
-in Cygwin without problem. This may make it possible to have a version of
126
-Deadwood in Windows with IPv6 support; Cygwin 1.7 and later should have
127
-IPv6 and it might be possible to compile in IPv6 this way. Again, if this
128
-is something you're interested in, feel free to send patches to the MaraDNS
129
-mailing list, or offer to pay me.
130
+The Scientific Linux 6 Makefile should work on other Linux variants,
131
+as well as other *NIX clones, but no guarantees. For example,
132
+there is a Cygwin Makefile included in the "src/" directory; I
133
+have verified that Deadwood 2.4 compiles in Cygwin without problem.
134
+This may make it possible to have a version of Deadwood in Windows
135
+with IPv6 support; Cygwin 1.7 and later should have IPv6 and it might
136
+be possible to compile in IPv6 this way. Again, if this is something
137
+you're interested in, feel free to send patches to the MaraDNS mailing
138
+list, or offer to pay me.
142
--- deadwood-3.0.02/bug.reporting.policy 2010-07-29 12:39:09.000000000 -0500
143
+++ deadwood-3.0.03/bug.reporting.policy 2011-06-24 13:55:47.366105168 -0500
145
* Valgrind-reported memory leaks can always be reported. Valgrind-reported
146
errors are only valid if Deadwood is compiled with -DVALGRIND_NOERRORS
148
-* The only officially supported OSes are Windows XP and CentOS 5. OS-specific
149
- issues such as startup, daemonizing, sysloggin, and /etc/resolv.conf
150
- setup are only supported on these two OSes.
151
+* The only officially supported OSes are Windows XP and Scientific Linux 6.
152
+ OS-specific issues such as startup, daemonizing, sysloggin, and
153
+ /etc/resolv.conf setup are only supported on these two OSes.
155
* Bugs need to be reported to the MaraDNS list, not to my email account nor
156
- as blog comments. I hope to have time to set up a web forum for
157
- MaraDNS/Deadwood support for people not comfortable with mailing
158
- lists, but no promises.
161
* Bugs reporting Deadwood crashes will be marked "unreproducible" unless
162
either a stack trace (or core dump if the program was compiled with