Bug 166705
Summary: | Installer doesn't recognize upgradeable installation | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rene Bauer <rene_falcon> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
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: | 2005-08-25 14:52:47 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
Rene Bauer
2005-08-24 19:48:26 UTC
Absolute symlinks will screw up a number of things on an upgrade since the root of the filesystem is mounted under a chroot. There's, unfortunately, not a lot that can be done to work around that :( (In reply to comment #1) > Absolute symlinks will screw up a number of things on an upgrade since the root > of the filesystem is mounted under a chroot. There's, unfortunately, not a lot > that can be done to work around that :( As I said, wouldn't it be better to not only look for redhat-release, but also look for fedora-release too, if the redhat-release file can not be found? Looking at the code this is currently not the case. It is only a few linces of code in the scripts of anaconda and will save you guys from a lot of strange bug reports ... I would also be happy if Red Hat/Fedora could make sure that the absolute symlink was not actually created by the installer. |