[syslinux] PXE Error Reporting

[Ady]

> Sebastian,
> 
> On 01/15/2015 12:49 AM, Sebastian Herbszt wrote:
> > which version of pxelinux were you trying? Looks like < 5.x.
> 
> the one from Fedora 20, syslinux-4.05.
> 
> It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports 
> "Failed to load ldlinux.c32" when ldlinux.c32 can't be read, and 
> "Loading <FILE>... failed: No such file or directory" when the TFTP 
> server replies with "Permission denied" for the kernel or initrd. So 
> this problem has slightly changed, but it hasn't been fixed.
> 
> Thanks,
> Andreas
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> 

 
About the "Permission denied" message, if read-permissions are not 
allowed for the kernel/initrd, then what else can Syslinux do? This 
message, as of version 6.03, seems to correspond to the real situation.

About the "failed to load" message... What exactly do you mean with 
"when ldlinux.c32 can't be read"?

The "failed to load ldlinux.c32" message is usually triggered when 
ldlinux.c32 is not located in the expected location (together with 
(l)pxelinux.0, or with the other Syslinux BIOS bootloaders). So, if 
ldlinux.c32 is adequately present and yet it cannot be read, what's the 
reason? Isn't it possible that some Syslinux-related package (or 
something else) in Fedora is over-complicating this matter?

IIRC, older Syslinux versions didn't care about file 
attributes/permissions of the bootloader files. If this is still 
valid/correct/adequate for Syslinux 6.03, then it shouldn't care about 
the respective attributes/permissions of the core module 
(ldlinux.{c32,e32,e64}) either. Perhaps I am misremembering, and/or 
perhaps this logic is inadequate/incorrect?

Regards,
Ady.