From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Speakup With Kernel Compile
Date: Tue, 22 Jan 2002 21:23:28 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0201222120330.10338-100000@lbear> (raw)
In-Reply-To: <00ce01c1a3b7$d7c15980$3c702041@tampabay.rr.com>
On Tue, 22 Jan 2002, Richard Wells wrote:
> Is it possible to update Speakup without compiling the kernel? I have a
> stable kernel but I want to get the latest features into it hopefully
> without compiling it.
No. That is the short answer. The longer answer is that because speakup is
a part of the kernel and the only way to add code to a kernel is to patch
the source and recompile you must recompile. That being said, there is no
reason to fear this. First, having a stable kernel is no huge feat. IT is
really quite simple. Second, if you compiled your current kernal then you
merely need to patch it, run make oldconfig (which then asks only new
questions) and compile away. You can skip the part of making the modules
since you haven't any need for more of them.
=======
Kirk Wood
Cpt.Kirk@1tree.net
Nowlan's Theory:
He who hesitates is not only lost, but several miles from
the next freeway exit.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
bind listening on 1 ip address Raul A. Gallegos
` Geoff Shang
` Raul A. Gallegos
` Speakup With Kernel Compile Richard Wells
` Kirk Wood [this message]
` Geoff Shang
` Gregory Nowak
` Raul A. Gallegos
` A dumb question Angelo Sonnesso
` Play Station 2 and Linux David Arocho
` charles crawford
` Kirk Wood
` A dumb question Gregory Nowak
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.0201222120330.10338-100000@lbear \
--to=cpt.kirk@1tree.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).