1 This is dhcpd-pools which is made for ISC dhcpd pool range analysis.
6 ./configure --prefix=/usr/local
11 == General information
13 With this command you can check usage of pool addresses
14 when address space is great. Command is designed so that
15 it will not get slow even there is thousands of IPs in
16 lease file. This kind of huge dhcpd installation can be
17 near by DSL DSLAMs or some other public access connection
20 This command will not print nice to know information like
21 DHCPStatus does. Output is limited only to list only
22 usage for ranges, shared network and total address space.
23 Limiting what is printed is the right thing to do when
24 there is thousands of addresses. If your address space is
25 small some other dhcp analyzer might be more suitable for
31 Maintainer is interested to get copy of your dhcpd.conf
32 and dhcpd.leases file, with includes if you use them.
33 Intention is to collect large set of data to build
34 realistic regression test environment. By giving your
35 data to maintainer you can be sure that updates will work
38 If you are interested to help this way put all files into
39 tar.gz, and send them to kerolasa@iki.fi. It would be nice
40 that email subject line would have 'dhcpd-pools test data'.
43 == Instructions for developers
47 * "./autogen.sh" generates all files needed to compile
48 and install the code (run it after checkout from git)
50 * "make distclean" removes all unnecessary files, but the
51 code can still be recompiled with "./configure; make"
55 * First get familiar with git. In case you are completely
56 lost watch Greg Kroah-Hartman explaining the very
58 http://archive.fosdem.org/2010/schedule/events/linuxkernelpatch
60 * Get up to date version of the code base.
62 $ git clone git://dhcpd-pools.git.sourceforge.net/gitroot/dhcpd-pools/dhcpd-pools
64 * Don't include generated (autotools) stuff to your
65 patches (hint: use git-clean [-X])
67 * Add a Signed-off-by line, use "git commit -s"
69 * Patches are delivered via email only. The following
70 commands will do the correct thing.
72 $ git format-patch -C origin/master..yourbranch -o ~/patches
74 When you send only one patch use the following.
76 $ git send-email --to kerolasa@iki.fi 0001*
78 The command above expects you have configured email
79 sending properly. See git.wiki for help.
80 https://git.wiki.kernel.org/index.php/GitTips#Mail
82 * One patch per email, with the changelog in the body of
85 * When you send series of pathes include introductory
88 $ git send-email --compose --to kerolasa@iki.fi ~/00*
90 Good introductory message will have at least
94 firstfile.c: short description
95 secondfile.c: another description
100 2 files changed, 3 insertions(+), 3 deletions(-)
103 Above introductory can be generated with git.
105 $ git shortlog master..yourbranch
106 $ git diff --stat master..yourbranch
108 * Subject: [PATCH] subsystem: description. Following
109 ~/.gitconfig will help you a little.
114 email = your.name@example.com
117 subjectprefix = PATCH
123 cc = your.name@example.com
126 * If someone else wrote the patch, they should be
127 credited (and blamed) for it. To communicate this, add
130 From: John Doe <jdoe@wherever.com>
132 The sign-off is a simple line at the end of the
133 explanation for the patch, which certifies that you
134 wrote it or otherwise have the right to pass it on as a
135 open-source patch. The rules are pretty simple: if you
136 can certify the below:
138 By making a contribution to this project, I certify
141 (a) The contribution was created in whole or in
142 part by me and I have the right to submit it
143 under the open source license indicated in the
146 (b) The contribution is based upon previous work
147 that, to the best of my knowledge, is covered
148 under an appropriate open source license and I
149 have the right under that license to submit
150 that work with modifications, whether created
151 in whole or in part by me, under the same open
152 source license (unless I am permitted to submit
153 under a different license), as indicated in the
156 (c) The contribution was provided directly to me by
157 some other person who certified (a), (b) or (c)
158 and I have not modified it.
160 (d) I understand and agree that this project and
161 the contribution are public and that a record
162 of the contribution (including all personal
163 information I submit with it, including my
164 sign-off) is maintained indefinitely and may be
165 redistributed consistent with this project or
166 the open source license(s) involved.
168 then you just add a line saying
170 Signed-off-by: Random J Developer <random@developer.example.org>
172 using your real name (sorry, no pseudonyms or anonymous
175 * If the the business with git is too difficult just send
176 source code files as is as email attachment to
181 * The preferred coding style is based on the linux kernel
182 Documentation/CodingStyle. For more details see:
184 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/CodingStyle
186 * Source code is pretty printed by using two, and only
187 the two, indent command switches -kr -i8