Re: Tragic State of FreeBSD Audio/Sound

1. Do not cross post to *three* mailing lists.
2. Post to the correct mailing list. In this case that's freebsd-questions@=
. That's the mailing list for asking questions like "Is anyone else seeing =
this problem?", "What can I do to help debug this problem?", "How did thing=
s become so bad?", etc.
3. Create problem reports in the FreeBSD bug database.
4. Don't wait for months or years before reporting a problem.
5. Test FreeBSD releases when they are in BETA or PRERELEASE. Don't wait un=
til it's too late.
6. Learn the difference between FreeBSD and third-party software from ports=
 (e.g. PulseAudio).
7. Understand that the way you configure your system may be very different =
from the way other people configure their systems. Bugs seen by you might n=
ot occur for others. In particular, a developer making a change might not b=
e seeing the behaviour you consider to be a bug at all.
8. Always consider the possibility that your hardware might be failing.
9. Provide patches and solutions instead of complaining.

Best regards,
Jordan Gordeev