From: "Joe Clever" <lists@clevercentral.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Fedora, Good Newby howtos, mailing lists and downloads
Date: Wed, 12 Nov 2003 10:59:53 -0500 [thread overview]
Message-ID: <000b01c3a936$07977380$6701a8c0@private.network> (raw)
In-Reply-To: <EF590AA19DB8C445A9541C1D98191F9447D6E8@COCMAIL2.coc.ca>
Stephen,
Could you clarify your last paragraph. Does this mean that you successfully
upgraded Red Hat 9 to Fedora using yum?
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Dawes, Stephen
Sent: Wednesday, November 12, 2003 10:28 AM
To: Speakup is a screen review system for Linux.
Subject: RE: Fedora, Good Newby howtos, mailing lists and downloads
Janina,
As a suggestion, you may want to add a section on yum into your how-to.
If you don't know yum, it is an easy-to-use command-line-based
application that does an excellent job of managing your rpms. Yum is
also very useful for doing such system activities as:
Installing applications.
Removing applications.
Keeping your system up-to-date.
Doing system upgrades.
The overall advantage to yum is that it takes away all the guess work
when it comes to dependencies.
I have found a partial yum how-to at:
http://www.phy.duke.edu/~rgb/General/yum_HOWTO/yum_HOWTO/yum_HOWTO.html
that you maybe able to use / modify for the speakup community.
The yum info page can be found at:
https://lists.linux.duke.edu/mailman/listinfo/yum
Otherwise, the How-to that I read on RH9 was easy to follow.
Just my thoughts for the future.
OH YEAH! I did an "yum upgrade" to fedora to see if it can be done, and
it worked like a charm. Once all was done, I re-started my computer and
was running fedora. Ain't life good!
Steve Dawes
Phone: (403) 268-5527
Email: SDawes@calgary.ca
NOTICE::
This communication is intended ONLY for the use of the person or entity
named above and may contain information that is confidential or legally
privileged. If you are not the intended recipient named above or a person
responsible for delivering messages or communications to the intended
recipient, YOU ARE HEREBY NOTIFIED that any use, distribution, or copying of
this communication or any of the information contained in it is strictly
prohibited. If you have received this communication in error, please notify
us immediately by telephone and then destroy or delete this communication,
or return it to us by mail if requested by us. The City of Calgary thanks
you for your attention and cooperation.
_______________________________________________
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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Dawes, Stephen
` Darragh
` Janina Sajka
` Darragh
` gnome Darragh
` Joe Clever [this message]
` upgrading the kernal Darragh
` Janina Sajka
-- strict thread matches above, loose matches on Subject: below --
Fedora, Good Newby howtos, mailing lists and downloads Dawes, Stephen
Dawes, Stephen
Fragmented speech using Redhat 8.0 and Apollo2 Sheila Acock
` Fedora, Good Newby howtos, mailing lists and downloads Darragh
` Janina Sajka
` Darragh
` Janina Sajka
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='000b01c3a936$07977380$6701a8c0@private.network' \
--to=lists@clevercentral.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).