From: Kenny Hitt <kenny@hittsjunk.net>
To: Glenn at home <GlennErvin@cableone.net>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: missing Grub entry
Date: Sun, 29 May 2005 18:33:16 -0500 [thread overview]
Message-ID: <20050529233316.GB18425@blackbox> (raw)
In-Reply-To: <000601c5649e$1a6cde80$6a00a8c0@desktop>
Hi.
Things change quickly in the Linux world. Also, it looks like you read
the Fedora HOWTO and just assumed it would work anywhere. Debian ain't
Fedora. Go read the Debian specific docs instead of guessing.
Especially when you continue to guess wrong.
Since you won't read, ****There is not a 2.6 official Debian kernel with
speakup.*** If you want a 2.6 kernel in Debian, you build it
yourself.
There has never been a text speakup)_synth=synthname for Debian. You're
confusing Debian with Fedora. The answers to your questions are spelled
out clearly in the docs for Debian.
Btw, I'm being harsh with you cause you keep not bothering to read.
Stop guessing and go read!
Kenny
On Sun, May 29, 2005 at 05:31:05PM -0500, Glenn at home wrote:
> I did not build anything.
> I did read the Debian install, but that was some time back on my first
> installation.
> I am wondering now if it was lilo that I needed to configure instead of grub
> for Debian to load up speakup on boot-up.
> It used to be:
> text speakup_synth=txprt
> But I don't recall reading if that has changed for lilo, since I put the
> word speakup in place of "text", for the installation CD.
> But I had 2 choices for the kernel during the installation, and one was
> 2.4.27-speakup, and I did not want that, so I took the newer, which was
> 2.6.? (I don't remember the last part but it did not have "-speakup" at the
> end), I really did not care, I just wanted 2.6 so I could have audio, since
> that was an issue with my last installation.
> * So I guess I will just fdisk and start over, and if I go with lilo instead
> of grub, should I be given the option to add a boot line for calling up
> speakup?
> Glenn
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Glenn at home
` Kenny Hitt
` Glenn at home
` Kenny Hitt [this message]
` Glenn at home
` Sean McMahon
` Sergei V. Fleytin
` Sean McMahon
` Sean McMahon
` Sean McMahon
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=20050529233316.GB18425@blackbox \
--to=kenny@hittsjunk.net \
--cc=GlennErvin@cableone.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).