Originally Posted by AlleyTrotter
Thanks for the clarification.
Just did an explodepkg also to see where it gets installed. So it seems that /boot will now be an efi partition.
That's unlikely. I was just looking for an obvious place to keep the binaries.
In many cases a machine will already have an EFI partition for use by Windows, and more than likely there will be enough extra space there to create a directory \efi\slackware to keep our files in. Otherwise, the user will probably have to make one with cgdisk before running setup. It would make sense for setup to warn the user about that if it finds no existing EFI partition on a machine using UEFI, too.
I'd rather stay away from trying to modify the machine's UEFI boot menu automatically in any way, so there will be extra steps that will need to be done, especially when setting up to dual boot.
Anyway, we're not really at the point where those things can be implemented yet. The next step is getting the installer bootable from UEFI, and this could be pretty tricky. Beyond the issues with just getting it to load (will an image load from a USB stick larger than the image? Is it possible to boot a disc conforming to the ISO9660 standards?), it appears the installer will need to support KMS for text output to work. That might end up resulting in that lovely tiny text for all installs, not just the UEFI ones. Passing a video= kernel option can't really be done by default since we don't know the native screen resolution up front. And I'm sure there are plenty more hurdles ahead.