Bug 248802
Summary: | RFE - yum distro upgrade | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alan Macdonald <alan.macdonald> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | james.antill |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-03 16:10:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alan Macdonald
2007-07-18 21:22:39 UTC
You can already do this by downloading the new fedora-release RPM and then doing a 'yum upgrade'. But please note: this is a very bad idea. You will be upgrading a live system while running the wrong kernel version. There are loads and loads of things that can go horribly wrong with this. The only way to sanely handle upgrades is to boot into the new kernel, preferably running from RAM or a LiveCD, and *then* perform the upgrade. closing this as worksforme - but we're working on a better way to do what wwoods suggested in his last comment |