gianpaolo.delmatto at genotec
Sep 19, 2007, 1:21 PM
Post #1 of 2
chaing freebsd pxeboot.0 from pxelinux.0
I have configured pxelinux.0 to allow chain-booting freebsd pxeboot.0
from it like this:
This works as expected, so no issue with that.
There's one weird thing however.
If I rename pxeboot.0 to pxeboot (omitting .0) and change the config
it throws this error at me:
Invalid or corrupt kernel image.
Same happens if I rename it to 'pxeboot.1' or if I try to do the same
itself by renaming it to 'pxelinux', 'pxelinux.abc' or some other name.
This is interresting as obviously a stock linux kernel can be named
This behaviour is only seen with pxe loaders.
While I've read the pxe specs which state the NBP may be split in two if
greater than 32k
thus leading to the .0 and eventually .1 in NBP filenames the behaviour
seen may be
Can you confirm this, Peter?
SYSLINUX mailing list
Submissions to SYSLINUX [at] zytor
Unsubscribe or set options at:
Please do not send private replies to mailing list traffic.