BUG-REPORT revision 59118 
1OPIE Software Distribution, Release 2.32                     Bug Reporting Form
2========================================                     ==================
3
4	Before submitting a bug report, please check the README file and make
5sure that your "bug" is not a known problem.
6
7	Please make a copy of this file and then edit it with your favorite
8text editor to include the answers to the following questions:
9
101. Your name and electronic mail address, in case we need more information.
11	If you can provide multiple addresses, please do so in case we
12	are unable to reply to the first one.
13
142. Your exact operating system vendor, name, and version number. If available,
15        please provide the output of "uname -a" and/or the version of your C
16        runtime library. Please be more specific than "UNIX".
17
183. The exact hardware the system was installed upon.
19
204. Which compiler and C runtime you used and its version number.
21	For instance, some systems have been known to have the GNU libc
22	installed as well as its native one, or to have a "BSD
23	compatibility" environment.
24
255. What version of OPIE you are using (the output of opiepasswd -v) and,
26	if you used the Autoconf install, a copy of the config.h, config.log,
27	and Makefile that Autoconf created.
28
296. A clear description of what you did and what bug then appeared.
30	If your system has the script(1) command, please run a session
31	under that to demonstrate the bug. Window-system cut-and-paste
32	also works well. Sometimes, the exact output is critical to
33	finding the bug.
34
35If you can provide any of the following things, it will greatly assist
36us in fixing the problem and improve the chances that we'll get back to you:
37
387. A diagnosis of what is causing the problem.
39
408. A test case that can repeatably demonstrate the problem.
41
429. A fix for the problem.
43
44	Bug reports should be sent by Internet electronic mail to 
45<opie-bugs@inner.net>. This mail is run through an automated sorter that helps
46get the bug report into the hands of someone who can help you. In order to
47make that program work, we ask that you:
48
49	* Send this is normal RFC822 plain text or MIME text/plain.
50
51	* DO NOT send this or any other file as an "attachment" from
52	  your mailer.
53
54	* DO NOT send a copy of your bug report to ANYONE other than
55	  <opie-bugs@inner.net>. This includes listing more than one recipient
56          or sending it as a carbon-copy ("Cc:") to someone else.
57
58	* DO NOT send a copy of your bug report directly to the
59	  authors or to any mailing lists. This really makes the
60	  authors angry, and will be interpreted as a request to not
61	  provide you with any help.
62
63	* DO NOT re-send bug reports because you didn't receive a
64	  response. We attempt to respond to ALL properly submitted
65	  bug reports. If we can't send mail back to you or you
66	  didn't bother to follow the directions for submitting a
67	  bug report, you won't receive a response.
68
69	While OPIE is NOT a supported program, we generally try to respond
70to all properly submitted bug reports as soon as we can. If your bug report
71is properly submitted so our machine sorter can process it, this usually
72takes one working day. If our machine sorter can't process your bug report,
73it usually takes a week or two.
74
75Copyright
76=========
77
78%%% portions-copyright-cmetz-96
79Portions of this software are Copyright 1996-1998 by Craig Metz, All Rights
80Reserved. The Inner Net License Version 2 applies to these portions of
81the software.
82You should have received a copy of the license with this software. If
83you didn't get a copy, you may request one from <license@inner.net>.
84
85