grubnetx64.efi.signed does not handle dhcp option 210 (pathprefix)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grub2-signed (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
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://
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.
Mar 19 19:15:53 apc100 in.tftpd[7502]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7503]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7504]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7505]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7506]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7507]: RRQ from ::ffff:
Mar 19 19:15:54 apc100 in.tftpd[7508]: RRQ from ::ffff:
Mar 19 19:15:59 apc100 in.tftpd[7509]: RRQ from ::ffff:
Digging further shows the dhcp option 210 (path-prefix), which might help. Question is whether grubnetx64 supports this.
| summary: |
- grubnetx64.efi.signed does not handle shop option 210 (pathprefix) + grubnetx64.efi.signed does not handle dhcp option 210 (pathprefix) |

Status changed to 'Confirmed' because the bug affects multiple users.