Date: Thu, 23 Mar 2000 09:35:26 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Andy Sparrow <andy@geek4food.org> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Brad Knowles <blk@skynet.be>, David Murphy <drjolt@redbrick.dcu.ie>, stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <38D966CE.2080999D@newsguy.com> References: <200003220411.UAA31479@mega.geek4food.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andy Sparrow wrote:
>
> [1] Actually, I don't fully understand why this happened either - it seemed
> like a very nice feature to be able to force some miscreant Plug'n'Pray
> device into using a known, "safe" configuration to me.
It happened because the devices now don't need the user to tell them
what the settings are. They can infer that from PnP information (which
is what PnP was designed for, in first place).
> But why doesn't Voxware find it then?
Because Voxware has not been changed to do so. Which get us back to the
maintenance issue, which gets us to Voxware being dropped from
5.0-current. Or, simply put, all Voxware problems result from nobody
working on it.
--
Daniel C. Sobral (8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@zurichgnomes.bsdconspiracy.net
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone bind them.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38D966CE.2080999D>