Public bug reported: In an project of replacing the classic pxelinux.0 with a uefi compatible one, I stumbled on a difference between grubnetx64 and pxelinux.0:
For pxelinux.0 we make heavy use of this feature: "Note that all filename references are relative to the directory pxelinux.0 lives in." (http://www.syslinux.org/old/pxe.php) Debugging "pxe" boots with grubnetx64 shows that it tries to load it's config files from the absolute root: (note that bootx64.efi is a link to grubnetx64.efi.signed) Mar 19 19:15:53 apc100 in.tftpd[7502]: RRQ from ::ffff:192.168.246.148 filename /macs/01-00-0c-29-5e-72-e3/bootx64.efi Mar 19 19:15:54 apc100 in.tftpd[7503]: RRQ from ::ffff:192.168.246.148 filename /grub/x86_64-efi/command.lst Mar 19 19:15:54 apc100 in.tftpd[7504]: RRQ from ::ffff:192.168.246.148 filename /grub/x86_64-efi/fs.lst Mar 19 19:15:54 apc100 in.tftpd[7505]: RRQ from ::ffff:192.168.246.148 filename /grub/x86_64-efi/crypto.lst Mar 19 19:15:54 apc100 in.tftpd[7506]: RRQ from ::ffff:192.168.246.148 filename /grub/x86_64-efi/terminal.lst Mar 19 19:15:54 apc100 in.tftpd[7507]: RRQ from ::ffff:192.168.246.148 filename /grub/grub.cfg Mar 19 19:15:54 apc100 in.tftpd[7508]: RRQ from ::ffff:192.168.246.148 filename /grub/grub.cfg Mar 19 19:15:59 apc100 in.tftpd[7509]: RRQ from ::ffff:192.168.246.148 filename coreos_production_pxe.vmlinuz Digging further shows the dhcp option 210 (path-prefix), which might help. Question is whether grubnetx64 supports this. ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434512 Title: grubnetx64.efi.signed does not handle shop option 210 (pathprefix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1434512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
