Most firmware implementations use the EFI specified EFI/BOOT/bootia32.efi (and similar) boot paths. Only broken firmware uses different paths for removable media. In those cases, the user can add their own startup.nsh.
For the compliant case, selecting "Shell" from the EFI boot menu should go to the shell. Signed-off-by: Darren Hart <[email protected]> --- scripts/contrib/mkefidisk.sh | 4 ---- 1 file changed, 4 deletions(-) diff --git a/scripts/contrib/mkefidisk.sh b/scripts/contrib/mkefidisk.sh index f8c08dd..6ff12af 100755 --- a/scripts/contrib/mkefidisk.sh +++ b/scripts/contrib/mkefidisk.sh @@ -255,10 +255,6 @@ sed -i "s/ LABEL=[^ ]*/ /" $GRUBCFG sed -i "s@ root=[^ ]*@ @" $GRUBCFG sed -i "s@vmlinuz @vmlinuz root=$TARGET_ROOTFS ro rootwait quiet @" $GRUBCFG -# Provide a startup.nsh script for older firmware with non-standard boot -# directories and paths. -echo "bootia32.efi" > $BOOTFS_MNT/startup.nsh - umount $BOOTFS_MNT umount $HDDIMG_MNT rm -rf $TMPDIR -- 1.8.1.2 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
