Presumably all the non-x86 images/ directories are missing README files. If we generate them in one place, we should consistently generate them in other places. (and perhaps before accepting patches to support ore arches, the patches have to include the generation of said README files).
Just checked with Jesse. He is not sure of the current condition.
The x86 images/README file is generated by scripts/mk-images.x86: cat > $TOPDESTPATH/images/README <<EOF This directory contains image files that can be used to create media capable of starting the $PRODUCT installation process. The boot.iso file is an ISO 9660 image of a bootable CD-ROM. It is useful in cases where the CD-ROM installation method is not desired, but the CD-ROM's boot speed would be an advantage. To use this image file, burn the file onto CD-R (or CD-RW) media as you normally would. The diskboot.img file is a VFAT filesystem image that can be written to a USB pendrive or other bootable media larger than a floppy. Note that booting via USB is dependent on your BIOS supporting this. It should be written to the device using dd. EOF There's nothing like this block in the mk-images.OTHER_ARCHES scripts. Is there a good place where these README blocks can be obtained, or do we just need to wing it and come up with something new?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I don't know if there are any good places to get such READMEs. You'd probably have to ask the interested arch parties to generate something based on the x86 example.
Duping to a future bug that is a superset of this one. *** This bug has been marked as a duplicate of bug 523403 ***