[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Sndconfig, does it have to go?

Well, the release notes merely say that it's deprecated, not that it
will actually be removed for the Cambridge release.  I suspect that one
of the reasons it's till there at all is because of what you mention --
some people are still using those older cards.

Also, keep in mind that OSS as a whole is deprecated in kernel 2.6.  I
don't know for sure, but I suspect that sndconfig won't work at all with
alsa -- those sound cards would have to have alsa support then to work
with 2.6.  But it looks like 2.6 won't be ready for Cambridge anyway, so
they can leave sndconfig in but make sure people know it won't be there

I don't think it's unreasonable to assume that a new, modern OS should
have to support all possible hardware from the past.  Sure, it should be
as backwards compatible as possible.  But really, if you desperately
need support for that older hardware, just remain with an older


On Tue, 2003-07-22 at 21:37, Benjamin Vander Jagt wrote:
> Is there any particular problem with sndconfig?  I and some of my
> customers use older ('96) sound cards, like the Turtle Beach Tropez+. 
> No plug-and-play configuration has ever set it up right, and most just
> lock up.  (In fact, I have *never* gotten the MIDI on these CS4232-based
> cards to work.)
> Some of the cards my customers and I use still run over $500 each.  I
> understand that there could possibly be other ways to set up these sound
> cards, but sndconfig seems to do so the best.  Is there some specific
> problem with sndconfig for which it needs to be removed?  If so, would
> you happen to know any better way to set up some of these older cards?
> Thanks.
> P.S.: Wow, now that I'm finally not getting batched mailing list, I can
> see how amazingly active this list is!
| Jeremy Portzer       jeremyp pobox com       trilug.org/~jeremy     |
| GPG Fingerprint: 712D 77C7 AB2D 2130 989F  E135 6F9F F7BC CC1A 7B92 |

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]