public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "David Bruzos" <david@bruzos.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: earliest possible software speech at boot?
Date: Thu, 4 Nov 2004 13:26:26 -0500	[thread overview]
Message-ID: <002001c4c29b$cb82c180$0564a8c0@bonny> (raw)
In-Reply-To: <x7vfcllc72.fsf@speech.braille.uwo.ca>

I did not know that...  However, what about the partition checks and 
anything else that might require action?  Sometimes my system says: " disk 
check returned errors, dropping you to a shell" and I get a bash prompt so I 
can do repare tasks (this is before the rc.d scripts could load 
speech-dispatcher".  Do you think there can be a way to get working software 
speech at this point?

David B.

----- Original Message ----- 
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, November 04, 2004 1:08 PM
Subject: Re: earliest possible software speech at boot?


> If you load the softsynth device early then it will start buffering
> console output up to it's buffer size which is 8k.  Then when
> speechd-up and speech-dispatcher get started you will hear all the
> output which was buffered up until that point.
>
>  Kirk
>
> -- 
>
> Kirk Reiser The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca University of Western Ontario
> phone: (519) 661-3061
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 David Bruzos
 ` Kirk Reiser
   ` David Bruzos
     ` Kirk Reiser
       ` David Bruzos [this message]
         ` Kirk Reiser
           ` David Bruzos
           ` Janina Sajka
 ` Thomas Stivers

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='002001c4c29b$cb82c180$0564a8c0@bonny' \
    --to=david@bruzos.org \
    --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).