After a long discussion on Google+, I was asked to bring up the issue of intentionally degraded or degenerate (single disk) installs on this list. See bugzillas 188314 and 189316. The stance that is is not supported by policy denies the system administrator a number of very important valid use cases: [From the G+ thread] 1. The user doesn't trust you at all, and physically disconnects a RAID member from the set before allowing Anaconda to touch the disk. Anaconda will not see the disk because it is not there to be seen. 2. The user knows he wants to add redundancy later, or intends to run single disk but wants seamless transition to new hardware when needed (+Brendan Conoboy's scenario.) 3. The user wants to break the RAID in software during installation. This eliminates the need to crack the case, but assumes one trusts the software to not screw it up. This does have some nice features, but definitely requires a lot of UI work in order to prevent mistakes. Before 2006 or so this was possible to do because Anaconda simply allowed the user to shell out and set up the volumes manually, bypassing the Anaconda UI, but the current Anaconda stops any RAID volumes so configure and refuses to run. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
