From Fedora Project Wiki

I'm using Anaconda for Fedora22. There is only one or two things with one spoke that irritates me It is the spoke for disk selection.

Disk selection and Partition Layouts.

I select that spoke, and in the centre of the screen I always select the option to let me choose the partition configuration. I immediately am given the screen showing LVM as the default filesystem organization. I change it to "standard", and have to move up the page to click the "let me click the autoconfigure" stuff.

I believe that the order of fields on this page needs to be reviewed and placed in a better sequence.

When we select the page it presents the icons representing the disk(s) on my system (I have five disks on my desktop), it would be helpful to see a colour change for the icons representing the disks having adequate free disk space.

Do you really want to make the next screen functional in GUI mode? Refer to Gparted displays for disks. For each disk I can see all partitions. With this display in mind, anaconda could present a view of each disk over the display of the next disk. That is how it would present the layout. I could then slide the barriers to increase/decrease sizes for /, /home, swap, or even add /opt to the layout or put /swap /home etc. elsewhere on my system.

This kind of graphical presentation is more user friendly than the list of /, biosboot, /home /swap and other, as we see the current disk layout presentation.

Install without creating a flashdrive.

My situation is like many other Fedora users. We have Fedora-1 and we want to install Fedora+0 or Fedora+1. If I download the ISO, why can I not use an installer that boots from that ISO I downloaded and pass control to that ISO's anaconda? Why do I have to first burn the ISO to a flash drive?

My other comment which is important for debugging

Once anaconda has completed formatting the target disk, there is, on said disk, permanent free space (a /home partition, and a / partition). I would like anaconda to transfer all of the files from it's /tmp to the new /home, and to continue logging information to that /home location. Should anaconda crash before completing its job, after a reboot the log files will be present and available.

In a crash, my current debugging procedures are to use the anaconda's Linux to mount the new /home, and therein I create a /home/anaconda partition. Step 2 that I do is I transfer all the contents of /tmp to it. All contents are there after a reboot, and that is how I have arranged to provide bugzilla information.