[I hate newUI.]
Chris Murphy wrote in Bug 872826:
Extlinux goes on /boot if it's a separate partition. This is possible with Fedora 19 netinst using the extlinux kernel parameter. It's not on the DVD or live media because there wasn't enough space for it, and once that was realized there wasn't enough time to figure out what should be dropped to make room. Keep in mind the extlinux option was for cloud/vm, not to solve the 'install to partition' request.
I don't know if specifying extlinux causes anaconda writes the syslinux mbr.bin to the MBR, and if so if there's a way to suppress it. I suspect it does because again the feature is for cloud/vm. So a.) UI code and translation would be needed to suppress this; or b.) backup your MBR and restore it post install. As precious as this MBR code appears to be, I'd guess you'd know how to do this considering how aggressive most OS's are about stomping on the MBR code.
I just started an F19 net installation using extlinux kernel option specifically to see what happens here. I'm already hung, not having found any detailed instructions how to proceed through Anaconda after initializing it this way. After selecting minimal install I went to destination, where I clicked "Full disk summary and bootloader", found the selected disks window and wondered what to do next. "Do not install bootloader" suggests exactly what it says will be the result, which I do not want. Actually clicking changes the button to "Set as Boot Device", which is even more ambiguous WRT the goal of getting extlinux onto the / target partition. I clicked set as and proceeded.
I got the target partition selected, clicked "+" button, selected /, clicked to finish the popup without filling in the size of the preselected partition, clicked the format button, selected type EXT4, typed a / in mount point, clicked label field, and "This file system does not support labels" pops up. I went ahead and typed one in anyway. Meanwhile at the bottom is the "Failed to add new device. Click for details." message, which when clicked tells me not enough space on disks, which unequivocally untrue. I tried again, this time not skipping the desired space field in the micro mount point window, even though its necessity is counter intuitive being that I already selected an existing 4.8GB partition to configure. I clicked done. It reported nothing accomplished. I tried again. Same thing. Over, and over. So I'm stuck unable to successfully proceed through this illegible mousetype manual partitioning screen:
http://fm.no-ip.com/SS/Fedora/anacondaF19manpart01.png -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
