From: Jacob Schmude <jacobs@ncinter.net>
To: speakup@braille.uwo.ca
Subject: Re: Speakup V0.09 & new kernel 2.2.16...no talkie
Date: Sat, 1 Jul 2000 19:41:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0007011935370.3632-100000@jscp> (raw)
In-Reply-To: <20000701212833.314.qmail@dalek.dhs.org>
Hi
That depends. If you're on a dedicated partition and use lilo, put
the following in the configuration file after the read-only line for the
kernel:
append="speakup_ser=1"
Now, rerun /sbin/lilo. Note: you can put it anywhere after the
image=/vmlinuz line. In slackware and debian, the kernel is /vmlinuz. In
redhat, it's /boot/vmlinuz. Here's what a section of my lilo.conf looks
like (with my kernel params replaced with yours):
image=/vmlinuz
root=/dev/hda4
read-only
append="speakup_ser=1"
Don't forget to rerun lilo to update the boot sector. Or, just
type:
linux speakup_ser=1
to boot linux at the boot: prompt if you don't want to edit lilo.conf.
If you're using zipspeak or zipslack, add it to the loadlin line
that loads your kernel in linux.bat.
On Sat, 1 Jul 2000, Buddy Brannan wrote:
> Kernel command line--where's that? In lilo.conf?
>
>
> --
> Buddy Brannan, KB5ELV | And if the ground yawned,
> Email: davros@ycardz.com | I'd step to the side and say,
> Phone: (972) 276-6360 | "Hey ground! I'm nobody's lunch!"
> Voice mail: (877) 791-5298 | --Eddie From Ohio
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Buddy Brannan
` Kaare Dehard
` Jacob Schmude
` Buddy Brannan
` Jacob Schmude [this message]
` brent harding
` Gene Collins
` brent harding
` Gene Collins
` Buddy Brannan
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.21.0007011935370.3632-100000@jscp \
--to=jacobs@ncinter.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).