search for: tftping

I've found a problem, and I think it is in syslinux (specifically when it tries to load ldlinux.e64 under hyper-V). I have a physical computer with a Gigabyte GA-P85-D3 motherboard that successfully pxeboots using the EFI images, and I hold that up as exhibit 1 that my deployment environment works. It also implies that the syslinux.efi image works in some cases, but not in all. My Hyper-V

...for pxelinux.cfg/[MACADDRESS] pxelinux.cfg/0A0000F0 and so on. On the server side I see in the syslog the client's DHCP-request and the client downloading pxelinux.0, but I never see a client asking for pxelinux.0/* . Just to see if I have a configuration problem I downloaded the configfile by tftping to my bootserver and asking for pxelinux.cfg/0A0000 which works fine. So dhcp and tftp apparently work fine, but where does is go wrong then? Any idea is welcome! Best regards, Lothar More information: $ /usr/sbin/dhcpd3 -V Internet Systems Consortium DHCP Server V3.0.3 Copyright 2004-2005 Int...

Question, Some Linux distributions I support show two approaches for pxe booting them. One uses memdisk to boot an ISO file. The other uses pxelinux to boot kernel and initrd a squashfs file. I'm unfamiliar with the impact to memory either approach has. Like, does using memdisk permanently squirrel away a chunk of memory for the ISO file that the OS will be unable to use? Is using initrd to

Hi, Peter Lister <P.Lister at sychron.com> schrieb am 06.02.02: > In way way better and easier? When I have criticised pxelinux I think > I've always stated *why* etherboot seems better for our environment. > > I'm not trying to be religious, or get anyone to change a working system > - I'm genuinely interested what differences others perceive. I've looked