From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from web2.serotek.com (web2.serotek.com [216.157.74.112]) by speech.braille.uwo.ca (Postfix) with ESMTP id 5762710315 for ; Thu, 18 Feb 2010 08:16:49 -0500 (EST) Received: from web2.serotek.com (localhost.localdomain [127.0.0.1]) by web2.serotek.com (Postfix) with ESMTP id CAE814F58B1B; Thu, 18 Feb 2010 08:16:48 -0500 (EST) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; format="flowed" From: tony seth To: speakup@braille.uwo.ca Subject: Re: What does it take to fork the kernel? Date: Thu, 18 Feb 2010 08:16:48 -0500 Message-ID: <20100218131648.8946.45371@web2.serotek.com> X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.13 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2010 13:16:49 -0000 Hi there: I can only really answer one of yer questions, but if you're using software speech for Speakup, I don't think you'll have to worry about rambling kernel messages, as software speech takes long enough that you won't hear anything until you actually go to a console and hit enter or something. I didn't get rambling kernel messages until I changed the modules file to load the doubletalk and now I get everything, which I like. Actually I remember the first time I encountered Speakup on the Vinux 2.0 cd I liked knowing that when Orca would die that I could just jump into a console and software speech would just work, or I could switch over to the doubletalk if I wanted to. Anyway, hope that helps a little, sorry for the rambling message... Cheereo! -- Email services provided by the System Access Mobile Network. Visit www.serotek.com to learn more about accessibility anywhere.