yes, a few things have been done to get to that point. 1 - make the kernel tell the user exactly what to report in the case of a kernel panic http://www.openb

yes, a few things have been done to get to that point. 1 - make the kernel tell the user exactly what to report in the case of a kernel panic http://www.openbsd.org/cgi-bin/cvsweb/src/sys/ddb/db_trap.c.diff?r1=1.13;r2=1.14 http://www.openbsd.org/cgi-bin/cvsweb/src/sys/ddb/db_trap.c.... 2 - rewritten sendbug to remove useless fields and automatically add useful information for developers (dmesg output, acpi dumps, etc.) to make it easier to trace problems to specific hardware http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/sendbug/sendbug.c http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/sendbug/se... 3 - quickly respond to new bugs. if they are valid, poke a developer that will know something about it. assign the bug to someone or at least mark it as verified. if the bug report doesn't have the required info or isn't valid, respond to the user and close it right away. don't let things pile up.