Hi, > the EDK2/UEFI folks are more inclined to have the existing EDK2 code > drive the specs, especially for boot, than the opposite.
It really was supposed to be the other way round this time. :)) But well, firmware is as firmware is. As said, having a copy of the ESP tree in the ISO should be easy to achieve and not occupy too much space, except on CD sized images, where every MB matters. > the naming scheme used for the ISO-9660 content needs to be more > restrictive than what Rock-Ridge or Joliet allows, as, for instance, > case sensitivity and special characters have to carefully considered, > else a file name lookup that might work in an ISO-9660 environment might > be broken for content that was extracted to FAT32/exFAT. That might be a show stopper with Debian-ish distros. They have long package names and there is no guarantee that filenames truncated to 8.3 are still unique. Mounting ubuntu-19.04-desktop-amd64.iso and doing for i in $(find /mnt/iso/pool) ; do basename "$i" ; done | sort | less i get to these problematic name clusters: grub-efi-amd64-bin_2.02+dfsg1-12ubuntu2_amd64.deb grub-efi-amd64-signed_1.115+2.02+dfsg1-12ubuntu2_amd64.deb grub-efi-amd64_2.02+dfsg1-12ubuntu2_amd64.deb oem-config-gtk_19.04.9_all.deb oem-config-slideshow-ubuntu_146_all.deb oem-config_19.04.9_all.deb With a Debian 9 amd64 DVD-1 image it is much worse because of more packages. Of whatever you can convince debian-cd or debian-live, the package names are in the realm of the package maintainers. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895131 Title: Groovy Desktop *BREAKS* the most common method of creating UEFI bootable drives for Ubuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
