From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: making grml boot with speech with grml2hd
Date: Tue, 26 Aug 2008 08:45:59 -0600 [thread overview]
Message-ID: <001501c9078a$74eead10$4200a8c0@tdsportable> (raw)
In-Reply-To: <48B3C7F9.4070203@baechler.net>
hello,
I'll try it again in a bit and see how things go.
I can just dpkg --purge the unwanted stuff, when it does install.
Thanks,
_|_|_|_|_| _| _|_|_|_|
_| _|_|_| _| _|_|_|
_| _| _| _|_|_| _|
_| _| _| _| _|
_| _| _| _|_|_|_| _|_|_|
Visit TDS for quality software and website production
http://tysdomain.com
msn: tyler@tysdomain.com
aim: st8amnd2005
skype: st8amnd127
----- Original Message -----
From: "Tony Baechler" <tony@baechler.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, August 26, 2008 3:08 AM
Subject: Re: making grml boot with speech with grml2hd
> Tyler Littlefield wrote:
>> I am installing grml with grml2hd, and was wondering what kernel
>> parameters I should pass for swspeak... Is it just swspeak?
>>
>
>
>
> Hi,
>
> I didn't have to pass anything, but I don't use software speech. If in
> doubt, pass swspeak. The worst you would get is an error in your logs.
> Also, how accessible is grml2hd? When I tried it, the cursor either
> didn't follow my selection or Speakup couldn't follow the cursor. I
> needed sighted help because I almost formatted and installed the wrong
> hard disk partition. I hope that got fixed. Mika posted here that he was
> unaware of the problem and it sounded like it would be fixed, but since
> it's already installed, I had no reason to try it again. Also be aware
> that just by the nature of a live CD installation, you'll probably end up
> with lots of extra packages that you don't need or want. If you're on a
> desktop for example, it still installs a bunch of packages for laptops,
> wireless, Apache, etc. Hopefully some of those can be turned off easily
> in grml2hd, but I couldn't when I tried. I was not running the final 1.1,
> I was running 1.1RC1. Hopefully some of these problems have been fixed.
> I would like to know how it goes for you.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3387 (20080826) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Tony Baechler
` Tyler Littlefield [this message]
` Al Sten-Clanton
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='001501c9078a$74eead10$4200a8c0@tdsportable' \
--to=tyler@tysdomain.com \
--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).