From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pw0-f42.google.com (mail-pw0-f42.google.com [209.85.160.42]) by speech.braille.uwo.ca (Postfix) with ESMTP id A0B62102A9 for ; Thu, 18 Feb 2010 06:33:58 -0500 (EST) Received: by pwi10 with SMTP id 10so1504545pwi.29 for ; Thu, 18 Feb 2010 03:33:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=YHOy4G3A9VmO7SHiCaNctK4eGJUPUU7z7WMfaUdWPH4=; b=un1cqvqEcly1Iriqni+2ECY0aTvbvEith1jklEmV109koxwcrZa7nE1LZ0TN0x7Vag 3vu4fYVz9KARzlAsq0pcktbwrRByrAaI0u2KxAKBRYbqpiWtng65URcyJITxjJ8CsDWN 5+LCuxQpRzbs5IHy/ntT0ZFgRG7kULOdYxE0Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=A1rGIA4lcTsvKZVzs8obh8zieqNRigBtQsXl5+2pDqApt19DJC8Dw58xYJsGOFGfe9 z1Ox78aEtZrk39CF89yMTbJY1havrNm8wEIhSJvniq7EFY3HlFXoCnd+yRqa57dU/CW8 M7fddJRBwoerUvG6IKPDpgv0z/fYyq0qB/HbU= MIME-Version: 1.0 Received: by 10.115.85.31 with SMTP id n31mr3256638wal.38.1266492837975; Thu, 18 Feb 2010 03:33:57 -0800 (PST) Date: Thu, 18 Feb 2010 06:33:57 -0500 Message-ID: <499d69a01002180333q748a1c54i2077e94ec6e4bd14@mail.gmail.com> Subject: What does it take to fork the kernel? From: Bill Cox To: "Speakup is a screen review system for Linux." Content-Type: text/plain; charset=ISO-8859-1 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 11:33:59 -0000 Hi. I'm trying to improve integration of speakup for an upcoming Vinux release. Currently, I install it with module-assistant, which has two problems. First, speakup is loaded as a module, rather than compiled into the kernel. Second, every time Ubuntu ships a new kernel, speakup breaks, until the user issues the magic command 'sudo m-a a-i -f speakup-source' and reboots. I'm considering having a custom kernel, compiled with speakup for Vinux. I have two questions, as a speakup novice. In particular, I've never used speakup when compiled in the kernel, so I'm only guessing how it works. First, is there some way to disable speaking by default during boot, and only enable it if the user asks for it? The first sound Vinux normally makes is the login window chime. I think it will confuse some users and possibly annoy others if they wind up listening to the boot messages, but I want the option to listen. Second, do you know what it takes to maintain the kernel packages? I'm also a novice debian packager. Alternatively, I can make it so the user does not have to type the command to recompile speakup by detecting that it is not loading and then recompiling on boot. Finally, I've been asked to make some changes in default speakup settings (turn cursor tracking off, and set punctuation to some). Is the recommended way with speakupconf? Thanks, Bill