Bug 883141 - [custom part usability] Confusion about mount point within existing installation vs. mount point in target installation
[custom part usability] Confusion about mount point within existing installat...
Status: NEW
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2012-12-03 16:38 EST by Adam Williamson
Modified: 2017-04-28 09:18 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Williamson 2012-12-03 16:38:34 EST
Another usability issue with newUI custom part which has come up at least a few times on test@ and in the forums (referenced to some extent in the second half of https://lists.fedoraproject.org/pipermail/test/2012-December/112124.html , for e.g.): some people are getting confused by the fact that, for already-existing partitions, we both show an existing mount point and allow you to assign a new one.

If you select an existing partition in 'custom part', its mount point in the existing OS is shown in its left-hand pane entry, and there is a 'Mount Point' dialog in the right-hand pane which assigns its mount point for the new OS install.

Once you understand the model this kind of makes sense, but it seems to be pretty confusing to people initially. I'm not sure of the best way to improve on this: again, perhaps it comes down to labelling? Somehow explain more clearly what the two mount points are, and what is being set and displayed where?
Comment 1 Fedora End Of Life 2013-12-21 04:37:29 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Adam Williamson 2013-12-21 14:32:45 EST
This is an enhancement request really, bumping to Rawhide and marking FutureFeature.
Comment 3 Fedora Update System 2017-04-28 08:49:22 EDT
anaconda-26.21.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f620d8c7c2
Comment 4 Martin Kolman 2017-04-28 09:18:20 EDT
Looks like the Bodhi web UI likes to add random unrelated bugs to an update...

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