[ William Colin Wood: Can you please add this to the documentation that
  you're working on?  Slightly edited, of course... :-) ]

This is just a reminder that the send-pr utility is the proper way to
submit bug reports and change requests.  It should exist on your NetBSD
system and should work fine if you have e-mail set up on your system.
If you don't have e-mail set up, you can use send-pr to create a bug
report which you can then cut & paste or otherwise transfer to a system
from which you can send e-mail.

Using send-pr ensures that the report will be recorded in the GNATS
database.  It can be used to submit any bug (documentation or
programmatic) or change request or fix.

Currently, there are no open bugs filed in category port-mac.  I know
that there are bugs, though.  The example pr, below, for example, is
not entirely made up.

When submitting a bug with send-pr, please be as detailed as you can and
fill out all blanks to the best of your knowledge.  The proper category
for NetBSD/mac68k bugs that are mac-specific would be port-mac.  Here's
an example of a filled out bug report:

========================== beginning of report ============================
SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR: 
SEND-PR: Please consult the send-pr man page `send-pr(1)' or the Texinfo
SEND-PR: manual if you are not sure how to fill out a problem report.
SEND-PR:
SEND-PR: Choose from the following categories:
SEND-PR:
SEND-PR: bin        kern       lib        misc       port-amiga 
SEND-PR: port-hp300 port-i386  port-m68k  port-mac   port-pc532 
SEND-PR: port-pmax  port-sparc port-sun3  standards  
SEND-PR:
To: gnats-bugs@gnats.netbsd.org
Subject: 
From: briggs
Reply-To: briggs


>Submitter-Id:	net
>Originator:	Allen Briggs
>Organization:
Allen Briggs - end killing - allen.briggs@bev.net ** MacBSD == NetBSD/mac68k **
   Where does all my time go?  <a href="http://www.netbsd.org/">Guess.</a>
>Confidential:	no
>Synopsis:	Under high traffic conditions, the ae driver locks the system.
>Severity:	serious
>Priority:	medium
>Category:	port-mac
>Class:		sw-bug
>Release:	Wed Sep 20 1995
>Environment:
	Mac IIcx with 20MB.  Should affect all systems running the ae driver.
System: NetBSD puma.bevd.blacksburg.va.us 1.0A NetBSD 1.0A (PUMA) #35: Wed Sep 20 19:56:59 EDT 1995 briggs@puma.bevd.blacksburg.va.us:/u/home/briggs/bsd/src/sys/arch/mac68k/compile/PUMA mac68k


>Description:
	Under heavy network traffic, the ae driver will wedge the
system.  When this happens, no input works--from the keyboard nor from
the network.  I did not try from a serial console.
>How-To-Repeat:
	In my case, running tcpdump on a busy network caused the system
to freeze.  The exact command was: 'tcpdump -eln'
>Fix:
	No fix, yet, but I suspect that the fix lies in the via nubus
interrupt handling code, not in the ethernet driver, per se.
========================== end of report ============================