198
edits
Changes
no edit summary
losetup -D
# All else fails, don't worry about it, a reboot will get rid of it.
</pre>
# Only use 1 cpu or it crashes(I don't know why...)
* Expand image or add extra space. You will need disk space equal to (pidora composed image size * 2) + pidora chroot size. I used about 20 GB, was enough for multiple composes.
* I used a pidora f17chroot inside the inside the arm qemu image, then installed anaconda and lorax inside the chroot. You can get the packages for pidora f17 chroot through yum or if that is an issue from the pidora koji instance.##[http://japan.proximity.on.ca/kojifiles/packages/lorax/17.17/1.fc17/armv6hl/lorax-17.17-1.fc17.armv6hl.rpm lorax-17.17-1.fc17]# [http://japan.proximity.on.ca/kojifiles/packages/anaconda/17.29/1.fc17/armv6hl/anaconda-17.29-1.fc17.armv6hl.rpm anaconda-17.29-1.fc17]* EXTRA NOTE: Using a pidora chroot might not be necessary(?) as long as you can use the following packages inside the qemu environment: anaconda(anaconda-17.29-1.fc17) and lorax(lorax-17.17-1.fc17), however this is a guess. Maybe people would have better luck using a fedora 17 rootfs instead of the f20 rootfs. (On that note, it might be worth it to try using the fedora 20 images /boot: kernel, initrd, and dtb with a fedora 17 arm image rootfs)* Before you chroot into the f17v6 chroot, make sure you bind mount the following directories. These are required by livemedia-creator. Don't forget to unmount them when you are done as well.<pre>mount -o bind /dev/ /path_to_chroot/f17v6/dev/mount -o bind /sys/ /path_to_chroot/f17v6/sys/mount -o bind /proc/ /path_to_chroot/f17v6/proc/</pre>* Finally you should now have everything setup to start composing. For more information on how to do a compose for pidora: [[Pidora_SOP#Composing_Images]]
