From: "Ron Marriage" <marriage@seidata.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: New Red Hat Linux/Fedora Core kernels.
Date: Thu, 4 Dec 2003 14:18:15 -0500 [thread overview]
Message-ID: <000401c3ba9b$5f1450d0$4dbdfea9@WOMBAT> (raw)
In-Reply-To: <Pine.LNX.4.58.0312022314580.9957@wb2flw.octothorp.org>
Having just downloaded the ISO's, do I have to re=download all of them
or just disk 1?
Thanks
Ron
----- Original Message -----
From: "William F. Acker WB2FLW +1-303-722-7209" <wacker@octothorp.org>
To: "SPEAKUP Distribution List" <speakup@speech.braille.uwo.ca>
Sent: Wednesday, December 03, 2003 1:29 AM
Subject: New Red Hat Linux/Fedora Core kernels.
> Hi all,
>
> New kernels are being built and uploaded to the Speakup Site
this
> evening into tomorrow morning. They are for Red Hat Linux 7x, 8.0,
9, and
> Fedora Core 1. There's a glitch with the Fedora kernels. I had to
change
> the release number because the stock release numbers are too long
for the
> installer, once the Speakup modifier is added to the end. I guess I
don't
> know enough about how the release numbers are incremented. The
result is
> that RPM thinks that the new kernel is older than the one that's
presently
> installed. The work-around is to add the "--oldpackage" keyword to
the
> command line. For example: "rpm -iv
kernel-2.4.2-2a.nptlspk2.i686.rpm
> --oldpackage".
>
> Installation ISO's for Red Hat Linux 9 and Fedora Core 1 will
appear
> tomorrow.
> HTH.
>
>
> Bill in Denver
>
> _______________________________________________
> 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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
William F. Acker WB2FLW +1-303-722-7209
` Ron Marriage [this message]
` William F. Acker WB2FLW +1-303-722-7209
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='000401c3ba9b$5f1450d0$4dbdfea9@WOMBAT' \
--to=marriage@seidata.com \
--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).