From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: <sdawes@telus.net>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: PROBLEM UPGRADING FROM FC2 TO FC6
Date: Tue, 05 Dec 2006 19:43:52 -0500 [thread overview]
Message-ID: <001201c718cf$9a705b20$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <KCEEIMDNLJHPIDNANLPLEEIKDPAA.sdawes@telus.net>
Thanks very much. I'd wondered about that, but nothing I read about
upgrading--and I didn't find much--told me one way or the other.
No, I'm not worried about the data. I just wanted to avoid repartitioning.
Maybe I'll have better partitioning for it.
Al
----- Original Message -----
From: "Steve Dawes" <sdawes@telus.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, December 05, 2006 7:13 PM
Subject: RE: PROBLEM UPGRADING FROM FC2 TO FC6
> You cannot upgrade from 2 straight to 6.
> There has been too many significant changes to make such a version jump.
> Your best bet is to tell the installer that you are installing, (not
> upgrading).
> If you are worried about loosing existing data, then I strongly recommend
> that you backup all your data before you proceed with the new install.
>
> In fact, regardless, you should always do a backup of your data, and
> configuration directories as part of an upgrade or fresh install process.
>
> Good luck.
>
> Steve
>
>
> _______________________________________________
> 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.409 / Virus Database: 268.15.9/571 - Release Date: 12/5/2006
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Albert E. Sten-Clanton
` Steve Dawes
` Albert E. Sten-Clanton [this message]
` Janina Sajka
` Albert E. Sten-Clanton
` Dawes, Stephen
` Albert E. Sten-Clanton
` Buddy Brannan
` 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='001201c718cf$9a705b20$6405a8c0@ALBERTLC7SN0ZA' \
--to=albert.e.sten_clanton@verizon.net \
--cc=sdawes@telus.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).