grub2: Reporting bugs

1 
1 Appendix B Reporting bugs
1 *************************
1 
1 These are the guideline for how to report bugs.  Take a look at this
1 list below before you submit bugs:
1 
1   1. Before getting unsettled, read this manual through and through.
1      Also, see the GNU GRUB FAQ
1      (http://www.gnu.org/software/grub/grub-faq.html).
1 
1   2. Always mention the information on your GRUB. The version number and
1      the configuration are quite important.  If you build it yourself,
1      write the options specified to the configure script and your
1      operating system, including the versions of gcc and binutils.
1 
1   3. If you have trouble with the installation, inform us of how you
1      installed GRUB. Don't omit error messages, if any.  Just 'GRUB
1      hangs up when it boots' is not enough.
1 
1      The information on your hardware is also essential.  These are
1      especially important: the geometries and the partition tables of
1      your hard disk drives and your BIOS.
1 
1   4. If GRUB cannot boot your operating system, write down _everything_
1      you see on the screen.  Don't paraphrase them, like 'The foo OS
1      crashes with GRUB, even though it can boot with the bar boot loader
1      just fine'.  Mention the commands you executed, the messages
1      printed by them, and information on your operating system including
1      the version number.
1 
1   5. Explain what you wanted to do.  It is very useful to know your
1      purpose and your wish, and how GRUB didn't satisfy you.
1 
1   6. If you can investigate the problem yourself, please do.  That will
1      give you and us much more information on the problem.  Attaching a
1      patch is even better.
1 
1      When you attach a patch, make the patch in unified diff format, and
1      write ChangeLog entries.  But, even when you make a patch, don't
1      forget to explain the problem, so that we can understand what your
1      patch is for.
1 
1   7. Write down anything that you think might be related.  Please
1      understand that we often need to reproduce the same problem you
1      encountered in our environment.  So your information should be
1      sufficient for us to do the same thing--Don't forget that we cannot
1      see your computer directly.  If you are not sure whether to state a
1      fact or leave it out, state it!  Reporting too many things is much
1      better than omitting something important.
1 
1    If you follow the guideline above, submit a report to the Bug
1 Tracking System (http://savannah.gnu.org/bugs/?group=grub).
1 Alternatively, you can submit a report via electronic mail to
1 <bug-grub@gnu.org>, but we strongly recommend that you use the Bug
1 Tracking System, because e-mail can be passed over easily.
1 
1    Once we get your report, we will try to fix the bugs.
1