Bug 238550 - Cannot upgrade from LiveCD
Summary: Cannot upgrade from LiveCD
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-01 11:18 UTC by Kaare Fiedler Christiansen
Modified: 2013-03-06 03:50 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2007-05-01 12:19:29 UTC

Attachments (Terms of Use)

Description Kaare Fiedler Christiansen 2007-05-01 11:18:13 UTC
Description of problem:

The only available CD image of Fedora 7 test 4 is a LiveCD, which you can
install from. However, you cannot upgrade from this LiveCD

Version-Release number of selected component (if applicable):

7 test 4

How reproducible:


Steps to Reproduce:
1. Have an installed Fedora Core 6
2. Download and burn Fedora 7 test 4 LiveCD
3. Boot it
Actual results:

No possibility of upgrading, only removing all partitions and reinstalling.

Expected results:

Possibility of upgrading my old installation.

Comment 1 Jeremy Katz 2007-05-01 12:19:29 UTC
The way that the live CD installation method works, there isn't any possible way
to do an upgrade; what happens is that we dd the filesystem image from the live
image over and make it the root filesystem.  This works less well for upgrading :-)

You can run anaconda by hand as 
  /usr/sbin/anaconda --method=http://some.site.com/with/a/fedora/repo
--graphical --selinux

if you want to do a more normal network install (and thus get upgrade
capability) rather than the live CD install method.  But at that point, you're
about as well off to just download the boot.iso to start your upgrade from.

Comment 2 Kaare Fiedler Christiansen 2007-05-01 14:46:37 UTC
Thanks for the quick feedback.

In that case, documentation on how to upgrade is _seriously_ needed. I will
proceed with a network upgrade instead. 

Possibly a link to starting anaconda as a network upgrade would be in order on
the LiveCD?

Note You need to log in before you can comment on or make changes to this bug.