public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: What does it take to fork the kernel?
Date: Thu, 18 Feb 2010 14:24:31 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1002181416200.8549@localhost.localdomain> (raw)
In-Reply-To: <499d69a01002180333q748a1c54i2077e94ec6e4bd14@mail.gmail.com>

Hi Bill,
I think it would be far easier to just build the .deb package for speakup 
for each specific kernel and, by settings in the /etc/apt/sources.list, 
make sure that the correct speakup is installed when the kernel is 
upgraded.
If you use software speech, there is IMHO no advantage in building speakup 
into the kernel.
As for the talking at boot, you can controll it by deciding when speech is 
started, and the user can hit the numpad-enter once to shut it up.

Finally, I've been asked to make some changes in default speakup
settings (turn cursor tracking off.
I cannot see why anyone could want that as a default setting in console 
mode.

For startup, on all my machines, I disable the gdm graphical login and 
just sign on using speakup.  I then run startx to start gnome/orca when 
needed.
I am not saying that this approach would work for your Vinux users, but it 
works well for me.
HTH, Willem



On Thu, 18 Feb 2010, Bill Cox wrote:

> 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
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


  reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Bill Cox
 ` Willem van der Walt [this message]
 ` Gregory Nowak
 tony seth
 ` Bill Cox
   ` Chris Brannon
     ` Samuel Thibault
   ` Samuel Thibault
     ` Bill Cox
       ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.1002181416200.8549@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).