From: Ted Lemon Date: Tue, 30 Mar 1999 15:46:04 +0000 (+0000) Subject: Add information about reporting bugs to the README and update version. X-Git-Tag: V3-ALPHA-19990330~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0cd6935365834c7d6be8d35ac0a135e0108a4e47;p=thirdparty%2Fdhcp.git Add information about reporting bugs to the README and update version. --- diff --git a/README b/README index 71750856e..cc727bac3 100644 --- a/README +++ b/README @@ -1,7 +1,7 @@ Internet Software Consortium Dynamic Host Configuration Protocol Distribution Version 3, Alpha Snapshot - March 29, 1998 (a) + March 30, 1998 This is an alpha test snapshot of Version 3 of the Internet Software Consortium DHCP Distribution. In version 3, this distribution @@ -91,9 +91,9 @@ information. On Digital Unix, type ``man pfilt''. To build the DHCP Distribution, unpack the compressed tar file using the tar utility and the gzip command - type something like: - zcat dhcp-3.0-alpha-19990329a.tar.gz |tar xvf - + zcat dhcp-3.0-alpha-19990330.tar.gz |tar xvf - -Now, cd to the dhcp-3.0-alpha-19990329a subdirectory that you've just +Now, cd to the dhcp-3.0-alpha-19990330 subdirectory that you've just created and configure the source tree by typing: ./configure @@ -319,9 +319,74 @@ mailing list. If you are going to use dhcpd, you should probably subscribe to the dhcp-server and dhcp-announce mailing lists. If you will be using dhclient, you should subscribe to the dhcp-client mailing list. + +If you need help, you should ask on the dhcp-server or dhcp-client +mailing list (or both) - whichever is appropriate to your +application. This includes reporting bugs. Please do not report +bugs in old software releases - fetch the latest release and see if +the bug is still in that copy of the software, and if it's not, _then_ +report it. It's okay to report bugs in the latest patchlevel of a +major version that's not the most recent major version, though - for +example, if you're running 2.0, you don't have to upgrade to 3.0 +before you can report bugs. + +PLEASE READ THIS README FILE CAREFULLY BEFORE REPORTING BUGS! + +When you report bugs, please provide us complete information. A list +of information we need follows. Please read it carefully, and put +all the information you can into your initial bug report, so that we +don't have to ask you any questions in order to figure out your +problem. + + - The specific operating system name and version of the + machine on which the DHCP server or client is running. + - The specific operating system name and version of the + machine on which the client is running, if you are having + trouble getting a client working with the server. + - If you're running Linux, the version number we care about is + the kernel version and maybe the library version, not the + distribution version - e.g., while we don't mind knowing + that you're running Redhat version mumble.foo, we must know + what kernel version you're running, and it helps if you can + tell us what version of the C library you're running, + although if you don't know that off the top of your head it + may be hard for you to figure it out, so don't go crazy + trying. + - The specific version of the DHCP distribution you're + running, for example 2.0b1pl19, not 2.0. + - Please explain the problem carefully, thinking through what + you're saying to ensure that you don't assume we know + something about your situation that we don't know. + - Include your dhcpd.conf and dhcpd.leases file if they're not + huge (if they are huge, we may need them anyway, but don't + send them until you're asked). + - Include a log of your server or client running until it + encounters the problem - for example, if you are having + trouble getting some client to get an address, restart the + server with the -d flag and then restart the client, and + send us what the server prints. Likewise, with the client, + include the output of the client as it fails to get an + address or otherwise does the wrong thing. Do not leave + out parts of the output that you think aren't interesting. + - If the client or server is dumping core, please run the + debugger and get a stack trace, and include that in your + bug report. For example, if your debugger is gdb, do the + following: + + gdb dhcpd dhcpd.core + (gdb) where + [...] + (gdb) quit + + This assumes that it's the dhcp server you're debugging, and + that the core file is in dhcpd.core. + PLEASE DO NOT send queries about non-isc clients to the dhcp-client mailing list. If you're asking about them on an ISC mailing list, it's probably because you're using the ISC DHCP server, so ask there. +If you are having problems with a client whose executable is called +dhcpcd, this is _not_ the ISC DHCP client, and we probably can't help +you with it. Please see http://www.fugue.com/dhcp/lists for details on how to subscribe. If you don't have WorldWide Web access, you can send mail