From owner-freebsd-hackers  Mon Feb 20 21:57:24 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA08741 for hackers-outgoing; Mon, 20 Feb 1995 21:57:24 -0800
Received: from netcom14.netcom.com (root@netcom14.netcom.com [192.100.81.126]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA08734 for <freebsd-hackers@freefall.cdrom.com>; Mon, 20 Feb 1995 21:57:23 -0800
Received: by netcom14.netcom.com (8.6.9/Netcom)
	id VAA26021; Mon, 20 Feb 1995 21:47:16 -0800
Date: Mon, 20 Feb 1995 21:47:16 -0800
From: hasty@netcom.com (Amancio Hasty Jr)
Message-Id: <199502210547.VAA26021@netcom14.netcom.com>
To: aw2t+@andrew.cmu.edu, freebsd-hackers@freefall.cdrom.com
Subject: Re: snd devices (documentation)
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>Just out of curosity, has any work ever been done to clean up the 

The problem is not the sound driver per se but the lack of a 
volunteer to support a FreeBSD sound driver(s). 

It is already hard enough to keep up with the sound driver.

We could beef up config to understand better about configuring 
the sound driver(s). It places a minor maintenance burden on
config and less painful migration path from linux to FreeBSD.

On FreeBSD-1.1.5 and I believe that with the Linux sound driver
there is a simple document which outlines how to configure the
Linux sound driver. This document got wipe out on FreeBSD-2.0.

I think that in addition to raising the issues of ease of
configuration of the sound drivers, we should focus more 
on sound applications in general. I have yet to see a single
sound app coming out of this FreeBSD group, oops, I just
remember tracker. 

So show us what you can do with the sound drivers and we can
show you a much easier to configure sound driver.

	Enjoy,
	Amancio