On Fri, 2013-06-14 at 05:24 -0400, Felix Miata wrote: > On 2013-06-13 15:42 (GMT-0700) Adam Williamson composed: > > > All existing partitions are shown in the tree > > view on the left hand side of custom partitioning. You can select one > > and assign a mount point to it on the right hand side, and choose > > whether or not to reformat it. > > Its unintuitive logic has me pretty well baffled. I started my first new > installation since December on Wednesday evening. Since then, all my F19s had > been the result of F18 upgrades, most of which were F17 upgrades, many of > which were F16 upgrades. I didn't like Fedora's old installer much. I like > the current one a lot less. > > I started with this partititon layout: > http://fm.no-ip.com/SS/Fedora/kt880L09.txt > > When I started, sda20 was a freshly created empty EXT3, and my target for > F19's /. In spite of a huge variety of difficulty, a few hours after > beginning I somehow managed to get a working "Basic Desktop" installed onto > it, followed by adding as much of KDE as I'll ever use, for a net 73% used of > the total 4.8G partition size. > > More than 60% of the gross time since beginning, at least 15 hours estimated > net, I was doing nothing unrelated to F19 installation, including trying > unsuccessfully to get a minimal installation onto the identically sized > sda19. Each time I got as far as > http://fm.no-ip.com/SS/Fedora/anaconda19tc3-06parts-0768.png and no further > than being told insufficient space > http://fm.no-ip.com/SS/Fedora/anaconda19tc3-11addfailure-1024.png & > http://fm.no-ip.com/SS/Fedora/anaconda19tc3-04partoptions-1200.png even > though available space for / on sda19 is identical to the successful and > larger http://fm.no-ip.com/SS/Fedora/fedora19tc3-KDEinstsum.png installation. > It let me select the empty 4.8G partitions for formatting, but no amount of > clicking on the add mount point or configure selected mount point buttons > would allow me any progress in attempting to fill in the partition > characteristics fields - until: in advance of beginning an installation > attempt, I put a filesystem on the never-used-previously target / > partition!?!?!?! > > Is absence of any filesystem on a target / supposed to block installation??? Well, no, but it seems pretty clear to me what you should have done at the point of http://fm.no-ip.com/SS/Fedora/anaconda19tc3-06parts-0768.png : changed the 'File System' drop down to whatever you wanted to use (ext4, whatever) and then entered / for the 'Mount Point'. That ought to have been sufficient. All you've done in the screenshot is tell anaconda to reformat the partition: you haven't told it you actually want to *use* it for anything. 'Add Mount Point' is for creating a new partition, and 'configure selected mount point' is only going to work for a partition that has been assigned a mount point. Did you try, at any point, reading the documentation? The F18 Installation Guide did a rather good job of documenting how newUI works. > http://fm.no-ip.com/SS/Fedora/ has screenshots mostly of the installation > process, in part because without them the problems have been too numerous to > for me to be able to remember. My difficulty with Anaconda's wheel logic is > compounded by the illegibility of its tiny gray text on gray background. If you're talking about http://fm.no-ip.com/SS/Fedora/anaconda19tc3-03destination-1024.png , it's not actually meant to be that small, I don't think. It doesn't look like that for me in VMs or on metal. What environment are you running the installer in, exactly? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
