1) Different tftpds may respond differently with symlinks. If run chroot-style, it won't resolve the symlinks at all. I recall having to do a bind-mount which I think was for a tftpd configured to do a chroot after start.
2) If the tftpd has /netboot as its root and you want to boot /netboot/pxelinux, specifying "pxelinux.0" for the DHCP/BOOTP field file is perfect.
Hi genec,
In answer to #2 above: "If the tftpd has /netboot as its root..."
It does.
"...and you want to boot /netboot/pxelinux..."
I do.
I am including my udhcpd.conf file. Perhaps that is what you are refering to?
udhcpd.conf:
=========================
# The start and end of the IP lease block
start 192.168.0.111
end 192.168.0.122
# The interface that udhcpd will use
interface eth0
boot_file /pxelinux.0
opt dns 192.168.0.1
option subnet 255.255.255.0
opt router 192.168.0.1
option lease 864000 # 10 days of seconds
option tftp 192.168.0.17
siaddr 192.168.0.17
===========================
EoF
Of course pxelinux.0 is only part of the problem, core.gz and vmlinuz can't be found when symlinked, etiher. I don't know if that will make any difference or not in relationship to what you wrote.
Please know that what I say next is said with all kindness and admiration, no sarcasm here.
You are obviously highly intelligent and very knowledgeable about linux (which I admire and am envious of). But this mere mortal is way below your esoteric knowledge base. Could you, would you, translate what you just wrote into something I might be able to comprehend? Maybe with an example or two? I think I can almost make sense of it but a bit more help would maybe, just maybe get me over the top.
Thanks so much for taking the time to give the information you have already, and thanks for any further clarification you may give.