public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: question on speakup-source debian package
Date: Fri, 25 Jul 2008 15:36:21 -0700	[thread overview]
Message-ID: <20080725223621.GA6738@localhost.localdomain> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

I was just looking at the docs that come with the speakup-source
debian package, and there is something I'm confused on.

Let's say for example, that I am running a 2.6.25.12 custom-built
kernel via kernel-package from the stock kernel.org sources, and that
I want to upgrade to a custom-built 2.6.26 kernel built via
kernel-package, again from stock kernel.org source. The way I
understand the module-assistant man page, I have to:

1. Build the 2.6.26 kernel package, and install it.
2. Reboot into the new 2.6.26 kernel.
3. Ssh into the newly booted machine.
4. Build the speakup modules from the speakup-source package, as
described in the instructions that come with that package.
5. Modprobe the synth module I need, and be able to go back to the
machine's keyboard, now running 2.6.26 with speakup as modules.

Is this correct, or is it in fact possible for me to build speakup
from the speakup-source package for the 2.6.26 kernel, while still
running 2.6.25.12, and thus avoid steps 2-3? This is my first time
having to deal with module-assistant, I'm trying to understand in more
detail what happens when the speakup-source package is built, without
actually having to go through the procedure beforehand.

Any clarification and elaboration on this would be much appreciated,
and thanks in advance.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiKVWUACgkQ7s9z/XlyUyCadgCfSO0rQX8kvOCMreqlXE0p6Ug5
4yoAniYROxWEB58NzEV1xuP76gxHFjoQ
=aq/g
-----END PGP SIGNATURE-----

             reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak [this message]
 ` Gaijin
   ` Gregory Nowak
     ` Gaijin
       ` John covici
         ` Gregory Nowak
           ` John covici
             ` Gregory Nowak
 ` Samuel Thibault

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=20080725223621.GA6738@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).