1999-04-08 Andreas Jaeger <aj@arthur.rhein-neckar.de>

	* manual/install.texi (Reporting Bugs): Add section about reported
	bugs and correct email address of glibcbug script.

diff --git a/ChangeLog b/ChangeLog
index 9182567..6eace59 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+1999-04-08  Andreas Jaeger  <aj@arthur.rhein-neckar.de>
+
+       * manual/install.texi (Reporting Bugs): Add section about reported 
+       bugs and correct email address of glibcbug script.
+
 1999-04-01  Thorsten Kukuk  <kukuk@suse.de>
 
        * sunrpc/Versions: Add new xdr functions to GLIBC_2.1.1

diff --git a/FAQ b/FAQ
index 17168f2..dcc6426 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -823,7 +823,7 @@ copy a NIS_COLD_START file from a Solaris client (the NIS_COLD_START file is
 byte order independent) or generate it with nisinit from the nis-tools
 package; available at
 
-    http://www-vt.uni-paderborn.de/~kukuk/linux/nisplus.html
+    http://www.suse.de/~kukuk/linux/nisplus.html
 
 
 2.13.  I have killed ypbind to stop using NIS, but glibc
@@ -1647,7 +1647,7 @@ Answers were given by:
 {PB} Phil Blundell, <Philip.Blundell@pobox.com>
 {MK} Mark Kettenis, <kettenis@phys.uva.nl>
 {ZW} Zack Weinberg, <zack@rabi.phys.columbia.edu>
-{TK} Thorsten Kukuk, <kukuk@vt.uni-paderborn.de>
+{TK} Thorsten Kukuk, <kukuk@suse.de>
 {GK} Geoffrey Keating, <geoffk@ozemail.com.au>
 {HJ} H.J. Lu, <hjl@gnu.org>
 {CG} Cristian Gafton, <gafton@redhat.com>

diff --git a/manual/install.texi b/manual/install.texi
index 013c1a3..6042029 100644 (file)
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -468,6 +468,14 @@ errors and omissions in this manual.  If you report them, they will get
 fixed.  If you don't, no one will ever know about them and they will
 remain unfixed for all eternity, if not longer.
 
+It is a good idea to check first that the problem was not reported
+before.  Bugs are documented in two places: The file @file{BUGS}
+describes a number of well known bugs and the bug tracking system has a
+WWW interface at
+@url{http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl}.  The WWW
+interface gives you access to open and closed reports.  The closed
+reports normally include a patch or a hint on solving the problem.
+
 To report a bug, first you must find it.  Hopefully, this will be the
 hard part.  Once you've found a bug, make sure it's really a bug.  A
 good way to do this is to see if the GNU C library behaves the same way
@@ -492,7 +500,7 @@ if you haven't installed it, will be in your build directory.  Send your
 test case, the results you got, the results you expected, and what you
 think the problem might be (if you've thought of anything).
 @code{glibcbug} will insert the configuration information we need to
-see, and ship the report off to @email{bug-glibc@@gnu.org}.  Don't send
+see, and ship the report off to @email{bugs@@gnu.org}.  Don't send
 a message there directly; it is fed to a program that expects mail to be
 formatted in a particular way.  Use the script.