similar to: memdisk and iso

Sorry to bring this old thread up. I saw the note on the release of syslinux-5.10 which I have just finished installing. I would like some help here with configuration. I can move the iso into webserver's root directory but what should the configuration below be changed to load the iso via http? LABEL dell MENU LABEL dell LINUX memdisk INITRD dell.iso APPEND iso I have the lpxelinux.0 in the

On Wed, Jun 5, 2013 at 7:34 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Wed, Jun 5, 2013 at 7:25 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com> wrote: >> > On Wed, Jun 5, 2013 at 5:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Jun 5,

On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com> wrote: > On Wed, Jun 5, 2013 at 5:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Jun 5, 2013 6:13 PM, "upen" <upendra.gandhi at gmail.com> wrote: >> > >> > Thanks hpa. It looks like it's not able to find lpxelinux.0 files which >> > actually resides under

On Jun 5, 2013 6:13 PM, "upen" <upendra.gandhi at gmail.com> wrote: > > Thanks hpa. It looks like it's not able to find lpxelinux.0 files which > actually resides under /tftpboot/linux-install directory where the > pxelinux.0 existed before. > > ls -al /tftpboot/linux-install/lpxelinux.0 > -rwxr-xr-x 1 root root 81240 Jun 5 15:15 >

On 06/11/2013 10:06 AM, upen wrote: >> >> Good to see that 'site-option-space "pxelinux"' is added. >> I recommend using vendor-option-space instead. The server doesn't always force delivery of site-option-space options, but vendor-option-space options aren't negotiated and so are always sent. -hpa

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene

On Thu, Jun 6, 2013 at 7:02 PM, upen <upendra.gandhi at gmail.com> wrote: > On Thu, Jun 6, 2013 at 5:38 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Jun 6, 2013 5:42 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: >> > On 06/06/2013 02:40 PM, upen wrote: >> > > >> > > Some odd things I observed just now. >> > >

On 06/05/2013 02:46 PM, upen wrote: > > Thank you hpa and Gene. Currently I have: > filename "linux-install/lpxelinux.0" in DHCP server. > > I changed settings under pxelinux.cfg/default to > > LABEL dell > MENU LABEL dell > LINUX memdisk > INITRD http://192.168.0.100/dell.iso > APPEND iso > > I get error on theTFTP client machine after it

On 06/05/2013 02:34 PM, Gene Cumm wrote: > On Wed, Jun 5, 2013 at 4:18 PM, upen <upendra.gandhi at gmail.com> wrote: >> Sorry to bring this old thread up. I saw the note on the release of >> syslinux-5.10 which I have just finished installing. I would like some help >> here with configuration. I can move the iso into webserver's root directory >> but what

On Jun 6, 2013 5:42 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > On 06/06/2013 02:40 PM, upen wrote: > > > > Some odd things I observed just now. > > 1. Since yesterday, I have been reseting the client box from Virtualbox VM > > menu (Reset option). This always showed me com32 vesamenu.c32 message. > > 2. Some time ago, I decided I power

On Sat, Jun 8, 2013 at 1:44 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 12:20 schreef upen: > > On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> > wrote: > > > Op 2013-06-07 om 06:18 schreef upen: > > > > [ ... dhcp server configuration ... ] > > > > Everything has been always like this on

On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 06:18 schreef upen: > > On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > > > The tcpdump[1] shows strang HTTP

On 06/05/2013 04:49 PM, upen wrote: > > Before: This works > filename "linux-install/pxelinux.0"; <--dhcpd.conf > Location: /tftpboot/linux-install/pxelinux.0 > Confiugration: /tftpboot/linux-install/pxelinux.cfg/default > > After: This throws the errors I sent before about file not found. > filename "linux-install/lpxelinux.0"; <--dhcpd.conf.

Op 2013-06-10 om 09:48 schreef upen: <snip/> > > > My dhcpd.conf now looks like this: > host rhelclient { > site-option-space "pxelinux"; > next-server 192.168.0.100; > option pxelinux.magic f1:00:74:7e; > option pxelinux.configfile "linux-install/pxelinux.cfg/default"; > option pxelinux.pathprefix

On Thu, Jun 6, 2013 at 4:01 PM, H. Peter Anvin <hpa at zytor.com> wrote: > Very odd! > > This shows a TFTP connection being correctly established and then > disconnected, with all the negotiation involved. I'm wondering if it is > iPXE that is playing games with us here... > > -hpa > > Some odd things I observed just now. 1. Since yesterday, I have

On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > Sounds like it's losing lots of packets. > > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > It is TCP to port 80, but that

Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > On 06/06/2013 02:40 PM, upen wrote: > > > > Some odd things I observed just now. > > 1. Since yesterday, I have been reseting the client box from Virtualbox VM > > menu (Reset option). This always showed me com32 vesamenu.c32 > > message. > > 2. Some time ago, I decided I power off the client VM(

Hi, The method to boot an ISO using memdisk, memdiskfind and phram described in the wiki looks very promising to me. So, I looked into the sources trying to understand, how this works. Up to now, I could not find out how the memory containing the ISO image is preserved from being overwritten by the Linux kernel. Probably I'm missing something, could you please help me? Best regards, Bodo

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

I On Wed, Jun 5, 2013 at 7:41 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Wed, Jun 5, 2013 at 7:34 PM, upen <upendra.gandhi at gmail.com> wrote: > >> >> >> >> On Wed, Jun 5, 2013 at 7:25 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >>> On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com>