Philip Rowlands wrote:
The pxelinux image must live on the "next-server" at "filename", but
there's no requirement that next-server == DHCP server.
I'll take your word for it and experiment with it tomorrow.
If what you say is true I see no reason not to do a PXELINUX
boot.
Not a big issue I guess. How would you go about passing the
location of the PXELINUX image? Is it possible to set those
arguments in the filename "" setting in DHCP?
An example might make this clearer:
shared-network EXAMPLE-DHCP {
use-host-decl-names on;
option domain-name "example.com";
subnet 10.1.1.0 netmask 255.255.255.0 {
option routers 10.1.1.1;
option domain-name-servers 10.1.3.2;
next-server 10.1.3.2;
filename "/tftpboot/pxelinux.0";
host nosuchmac {
hardware ethernet 00:11:00:33:22:11;
fixed-address 10.1.1.222;
}
}
}
But where does this tell pxelinux.0 where to find the
ks.cfg file then? Sorry I read over my question and I
formulated the question rather poorly.
Cheers,
Phil
Thanks a bunch already Phil :)