From: "Daniel C" <dlchavez@bellsouth.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Problem with Fedora9 and Speakup
Date: Fri, 16 May 2008 14:42:48 -0400 [thread overview]
Message-ID: <000101c8b784$a3a402a0$646e010a@PDMainserver> (raw)
In-Reply-To: <20080516182107.GA21702@localhost.localdomain>
I was under the impression that the updating of documentation was Jennina's
job. I was only just writing to see why speakup doesn't, as it once did with
FC7, come up at boot time anymore.
My apologies for being so moody and bitchy, was uncalled for .. So sorry
Kerk, and whomever else. Suppose at the time of my writing I didn't have my
coffie; I tend to get moody and what not when coffie isn't available.
I've been working at this since 6 A.M., so I suppose coffie is a serious
need now.
There's no way that speakup can come up at boot time? Or will I, from what I
see via the speakupmodified.org site, have to disable the Pulse audio
plugin via yum first then speakup should run a tboot?
Or did I miss something during my tyrade?
Again, my apologies to anyone who I have bitched at. Won't happen again.
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.16/1446 - Release Date: 5/16/2008
7:42 AM
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Daniel C
` Kirk Reiser
` Daniel C
` Kirk Reiser
` Daniel C
` Kirk Reiser
` Kirk Reiser
` Gregory Nowak
` Alex Snow
` Janina Sajka
` Gregory Nowak
` Daniel C [this message]
` Gregory Nowak
` Eric Kosten
` John Heim
` Gaijin
` Janina Sajka
` Upgrading from FC8 to FC9 Scott Ford
` Albert E. Sten-Clanton
` Problem with Fedora9 and Speakup Gregory Nowak
` Janina Sajka
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='000101c8b784$a3a402a0$646e010a@PDMainserver' \
--to=dlchavez@bellsouth.net \
--cc=noreply@danielcproductions.net \
--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).