From: "propaine" <propaine@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: installed Fedora Core 5 but have questions
Date: Wed, 28 Jun 2006 12:16:48 -0400 [thread overview]
Message-ID: <003b01c69ace$462973a0$6505a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <20060628151104.GA31317@asmodean>
Since I'm considering whether to upgrade Fedora or switch to something else,
can you tell me why you decided that GRML is not for you? Thanks!
Propaine
----- Original Message -----
From: "Raul A. Gallegos" <raul@asmodean.net>
To: "Speakup Mailing-list" <speakup@braille.uwo.ca>
Sent: Wednesday, June 28, 2006 11:11 AM
Subject: installed Fedora Core 5 but have questions
> OK. After a short-lived experience with GRML I relize it was not for me.
> So I figured I'd go back to Fedora Core. I was previously using 3 and
> figured it was time to use 5.
>
> I installed 5 via telnet so am faced with no speakup modified kernel.
> I've downloaded the kernel rpm from speakupmodified.org. The one which
> is currently on my system is:
>
> kernel i686 2.6.17-1.2139_FC5
>
> So I downloaded the kernel I found on the ftp site which appears to have
> the same version. The name of the rpm is
>
> kernel-2.6.17-1.2139_FC5spk.i686.rpm
>
> When I try to install it though I get an error about the gpg key. Output
> is below.
>
> kernel i686 2.6.17-1.2139_FC5 installed
> 37 M
>
> Transaction Summary
>
============================================================================
=
> Install 1 Package(s)
> Update 0 Package(s)
> Remove 1 Package(s)
> Total download size: 37 M
> Is this ok [y/N]: y
> Downloading Packages:
> warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID
> 35571ae2
>
>
> Public key for kernel-2.6.17-1.2139_FC5spk.i686.rpm is not installed
>
> So, first question is how do I install getting past this error?
>
> Second question is what would be the correct syntax in removing the
> original kernel installed by fc5 which is 2.6.15. I was looking in
> /boot/grub/grub.conf and I see that one in there as well.
>
> Third question. Am I correct in assuming that once the speakup modified
> kernel is installed I still need to make the initial ram disk so that it
> knows which synthesizer I'm using?
>
> Thanks and FYI. I've read the various posts on the speakup archives
> especially messages from Janina and Stephen but
> none of them have mentioned the rpm and key bit. Many thanks in advance
> to anyone who can help.
>
> --
> Raul A. Gallegos ... IliwSsmc
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: 6/27/2006
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Raul A. Gallegos
` Willem van der Walt
` Raul A. Gallegos
` Dawes, Stephen
` Raul A. Gallegos
` propaine [this message]
` why I didn't choose GRML Raul A. Gallegos
` propaine
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='003b01c69ace$462973a0$6505a8c0@ALBERTLC7SN0ZA' \
--to=propaine@verizon.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).