On Aug 17, 2012, at 1:18 PM, John Reiser wrote: > On 08/17/2012 09:38 AM, Máirín Duffy wrote: > >> You should always back up your data before running an installer, >> especially one that's under heavy development. :) > > The point is that the installer looked for LVM2, raid, multi-path, etc., > and did not find any. Please tell me so explicitly, so that > *I* can avoid perception mistakes (not seeing what I'm not expecting > even though it's there, …) I disagree. The issue is only arising due to lack of trust because this is a new UI, and all of its guts are likewise new and totally suspect. I think as alpha testers we need to know precisely what hardware we have, and its on-disk condition. If LVM or RAID are known to be present but the installer doesn't inform us, *that* is a legitimate complaint. What we should get to is trust that if it doesn't find these things, they are not to be found. It could be an open question how quickly this trust is gained. But to build UI that confirms negative discovery is almost certainly unnecessary work. Also legitimate is if the installer UI causes ambiguity in destination identification/selection. Not good for the reasons you mention. Another reason why I'd like to see partition/volume names (or labels, whatever they're called) if present. This is immediately and clearly discoverable information most of the time for users, especially in the very common case of dual-boot installations along side Windows (or Mac OS). Chris Murphy _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
