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