From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.44.254]) by listman.redhat.com (Postfix) with ESMTP id 92BE63EA0F for ; Sun, 18 Nov 2001 21:23:46 -0500 (EST) Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id fAJ2Nkp23870 for ; Sun, 18 Nov 2001 21:23:46 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAJ2Nk929308 for blinux-list@listman.redhat.com; Sun, 18 Nov 2001 21:23:46 -0500 Received: from idscc07.onewest.net (idscc07.onewest.net [199.104.81.26]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAJ2Njw29301; Sun, 18 Nov 2001 21:23:45 -0500 Received: from rupin.localnet (ras221-112.srv.net [12.7.221.112]) by idscc07.onewest.net (8.11.3/8.11.3) with ESMTP id fAJ2K5D25706; Sun, 18 Nov 2001 19:20:05 -0700 Received: from localhost (lcr@localhost) by rupin.localnet (8.11.6/8.11.6) with ESMTP id fAJ2NeZ00904; Sun, 18 Nov 2001 19:23:41 -0700 Date: Sun, 18 Nov 2001 19:23:40 -0700 (MST) From: "L. C. Robinson" To: Cc: Subject: Re: Problems with Brltty In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com X-Reply-To: List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: I think turning kudzu off is a bad idea, especially for inexperienced users. Undesirable behavior can be reduced or eliminated by adding options to the invocation of kudzu (see the man page for the choices available). In particular, note the following from the man page: -s, --safe Do only 'safe' probes that won't disturb hardware. Currently, this disables the serial probe. So one could add the "--safe" option to the invocation line in /etc/rc.d/init.d/kudzu: /usr/sbin/kudzu -t 30 --safe or even (not recommended): /usr/sbin/kudzu -t 30 --quiet # do only configuration that doesn't require user input (better to just wait 30 seconds) One could also hand edit /etc/sysconfig/hwconf and add: driver: ignore to the appropriate sections (guesswork -- poorly documented). Better yet, complain to RedHat about the lack of documentation, and the need for a line oriented mode for kudzu, for use with adaptive hardware (possibly with a patch submission, for those who have the skills). Best Wishes, LCR On Sun, 18 Nov 2001, Nicolas Pitre wrote: > One of RedHat's service wants to be clever and tries to probe > for any kind of new hardware you might have attached to your > computer. Amongst other things it probes for serial mice which > has the tendency to upset BRLTTY somehow. This service is > called "kudzu" (don't ask me why). > > To prevent kudzu from interfering, just disable it as follows > once logged in as root: > > chkconfig kudzu off -- L. C. Robinson reply to no_spam+munged_lcr@onewest.net.invalid People buy MicroShaft for compatibility, but get incompatibility and instability instead. This is award winning "innovation". Find out how MS holds your data hostage with "The *Lens*"; see "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html