https://github.com/livecd-tools/livecd-tools/blob/master/tools/livecd-iso-to-disk.sh If you use the options: --efi --reset-mbr --format Pretty sure they're using extlinux for BIOS, and GRUB for UEFI. This combination of options looks like it's going to write syslinux/gptmbr.bin to point to the extlinux jump code in the ext4 /boot + / volume, which in turn loads extlinux. But only for BIOS systems. Whereas UEFI systems will find the EFI system partition, where shim and grub. The guts of that script includes a description why the overlay eventually blows up. To avoid that, you could rm -rf the contents of the ext4 volume on the stick after using this script; and then use rsync to copy over either a live system or a clean installed system in a VM, and then fix up the loose ends so it'll boot (initramfs, fstab, machine-id if you want, rename the kernel+initramfs filenames so they match the generic naming used by grub.cfg and extlinux.conf.... maybe I'm forgetting something). That way you have a real system installed rather than the loopback mounted live system with device mapper overlay. You can grep the /var/log/anaconda/program.log found on any Fedora Live installed system to get an idea what rsync command to use, what flags and what dirs to exclude. Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
