public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Janina Sajka <janina@afb.net>
To: blinux-list@redhat.com
Subject: Re: Speakup questions
Date: Wed, 14 Aug 2002 16:13:18 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0208141607110.26724-100000@TekRD.grg.afb.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141555230.26724-100000@TekRD.grg.afb.net>

Geetha:

One more suggestion, and I'm sorry if I overwhelm you with ideas!

If downloading 10 mB is unworkable from your side of the planet, here's 
yet another very good shortcut to a talking Linux.

Be sure you've installed the kernel source rpm. Look at 
/usr/src/linux-2.4. if you see files, you've got it. If not, it's on one 
of your CD ROMs in the RedHat/RPMS directory. Install with a similar rpm 
command:

rpm -iv kernel-source*

Next, cd to /usr/src and create one more symbolic link which the Speakup 
patch will look for:

ln -sf linux-2.4 linux

Now, you can cd to linux/configs. In there you'll find the Red Hat kernel 
configuration for each supported cpu. Find the one for your cpu and copy 
it to ../.config, so that it is in /usr/src/linux/.config.

Now, after patching the source files with Speakup, you can simply issue 
this command:

make oldconfig

And you'll only be prompted about Speakup specific things.

This should help insure you don't make a mistake in the dozens of 
configuration choices and end up with a kernel that won't boot. We know 
that your installation boots. It's highly advisable to add Speakup before 
trying out other configuration changes--if any. This way, Speakup is the 
only change you'll make.

The rest of the process remains the same:

make deps; clean; bzImage; modules; modules_install; install

And, you still need to edit /etc/lilo.conf and rerun lilo as before.




-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org




  reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Geetha Shamanna
 ` Janina Sajka
 ` Dave Hunt <
   ` Geetha Shamanna
     ` Dave Hunt <
       ` Janina Sajka
         ` Geetha Shamanna
           ` Janina Sajka
     [not found] ` <Pine.LNX.4.44.0208141404080.26724-100000@TekRD.grg.afb.net >
   ` Geetha Shamanna
     ` Janina Sajka
       ` ADFM
         ` John
           ` Janina Sajka
             ` John
             ` Jude DaShiell
               ` David Csercsics
                 ` John
         ` Pawel (Paul) Loba
     ` Janina Sajka
       ` Janina Sajka [this message]
     [not found]       ` <Pine.LNX.4.44.0208141607110.26724-100000@TekRD.grg.afb.net >
         ` Geetha Shamanna
  -- strict thread matches above, loose matches on Subject: below --
 speakup questions Kristoffer Gustafsson
 ` Buddy Brannan
 ` Kirk Reiser

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.44.0208141607110.26724-100000@TekRD.grg.afb.net \
    --to=janina@afb.net \
    --cc=blinux-list@redhat.com \
    /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).