From owner-freebsd-stable Wed Mar 22 17:11:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EC15737B9C1 for ; Wed, 22 Mar 2000 17:11:19 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p30-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.31]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA15058; Thu, 23 Mar 2000 10:09:37 +0900 (JST) Message-ID: <38D966CE.2080999D@newsguy.com> Date: Thu, 23 Mar 2000 09:35:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Andy Sparrow Cc: "Jordan K. Hubbard" , Brad Knowles , David Murphy , stable@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) References: <200003220411.UAA31479@mega.geek4food.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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