| Summary: | Anaconda should default mount point | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | GeoffLeach <geoffleach.gl> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | anaconda-maint-list, jonathan, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-02 10:14:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
GeoffLeach
2011-12-31 20:10:56 UTC
On a new system install there is no way of knowing which existing partition should be used for which mountpoint or if there is a separate partition for some directory tree at all. We even have cases with more than one system already present on the machine and we cannot do any autodetection because of this (too fragile anyways). So we cannot really do anything with this. If you have an idea about a way to solve this for the general case (multiple partitions, multiple systems, multiple OSs) please reopen this bug and we can discuss it further. |