2008/6/2 Ole Ersoy <ole.ersoy@xxxxxxxxx>:
That's right.
If your loader is at /tftpboot/loader/pxelinux.0 then dhcp would point at /loader/pxelinux.0
pxelinux.0 is the binary pxe loader. dhcp needs to point at pxelinux.0 (wherever it is*), as this is what the client needs to boot with.
default is the default pxe configuration which a request falls down to if the corresponding 01-aa-bb-cc-dd-ee-ff isn't found, and is generally found in pxelinux.cfg/
A client would expect to find it in /tftpboot/cobbler/loader/pxelinux.0....
Does that help?
I think so. Just want to make sure I'm clear. The file is currently here:
[root@localhost ole]# ls /tftpboot/
elilo-3.6-ia64.efi images menu.c32 pxelinux.0 pxelinux.cfg
So if I put "pxelinux.0" for the filename option it should resolve correctly right?
That's right.
If your loader is at /tftpboot/loader/pxelinux.0 then dhcp would point at /loader/pxelinux.0
I'll try to nuke the system and profile I added to see whether that caused the hiccup. It was syncing fine before that. Otherwise I'll start from scratch.
So I changed that to "pxelinux.0", and attempted to run cobbler
sync, which tells me:
[root@localhost ole]# cobbler sync
cannot find directory: -v
I tried restarting the cobbler daemon and doing cobbler sync and the
same message appears. Thoughts?
tbh your cobbler setup sounds a bit FUBAR. Purge and try again perhaps?
Thanks!
- Ole
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
--
Regards
Dan
_______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
