search for: ipappend

core and the simple menu do not interpret the IPAPPEND/SYSAPPEND directives in the same way. Which is the proper way? Either way, this should be clarified in the documentation. com32/elflink/ldlinux/readconfig.c: } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) {...

On Sun, Jun 23, 2013 at 3:16 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > I guess the bug is here (com32/menu/readconfig.c) > > 910 } else if (looking_at(p, "ipappend") || looking_at(p, > "sysappend")) { > 911 if (ld.label) > 912 ld.ipappend = atoi(skipspace(p + 8)); > 913 else > 914 ipappend = atoi(skipspace(p + 8)); > > since the length of "sysappen...

The following changes since commit 4ff8fcac8e7b5046987dee15592ab510ab343aa8: Matt Fleming (1): Merge branch 'menu-ipappend-1-for-mfleming' of git://github.com/geneC/syslinux into elflink are available in the git repository at: git://github.com/geneC/syslinux.git ipappend-fix-for-mfleming Gene Cumm (2): core & menu: fix IPAPPEND/SYSAPPEND conversion doc/ & txt/: Document IPAPPEND/SYSAPPEND f...

On Sun, Jun 23, 2013 at 11:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND >> directives in the same way. Which is the proper way? Either way, >> this should be clarified in the documentation. > > To be clear: core treats the value as always hexidecimal while simple > menu treats it as decimal unless a 0x prefix is present. Correction: si...

I have been using PXELINUX with the "ipappend 2" option for a long time. To make things a little more user friendly, I decided to set up menus (text menus with menu.c32), but they wouldn't work (blank screen and corrupted menu flashes by when you hit a key). I went through all kinds of combinations of options, and finally found that...

Just spent a few hours going mad(der) wondering why my menu config wasn't working. It looks like the change in 3.74 ("Add IPAPPEND to com32 modules, especially needed for linux.c32") breaks menu.c32 (and possibly other modules) since they aren't expecting it. In particular menu.c32 uses that as an optional menu file, it then complains "Initial menu has no LABEL entries!" (note that this isn't the same a...

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue. >> >> --------------------------------------------------------------------- >> SERIAL 0 38400 >> UI boot/syslinux/ves...

If you want eth0 to be used and no dynamic IP configuration request should not occur in the Linux kernel, specify *both* APPEND and IPAPPEND options like: APPEND ip=:::::eth0:none IPAPPEND 1 It's very tricky but it works, at least Linux 2.4.18 which I tested. The IP-PNP routine in the kernel doesn't modify values if the option values are not explicitly specified. IPAPPEND doesn't provide the <device> option and &lt...

Is there a way to use IPAPPEND 1 on the pxelinux command line. I want to be able to pass the whole command line in my menu files and not use the config file. Thanks Aaron

does the IPAPPEND option still exist? If so I want clearification on it please. Out of the syslinux documentation it says the following. The flag_val is an OR of the following options: 1: indicates that an option of the following format should be generated and added to the kernel command line: ip=client-ip:boot-se...

On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > core and the simple menu do not interpret the IPAPPEND/SYSAPPEND > directives in the same way. Which is the proper way? Either way, > this should be clarified in the documentation. To be clear: core treats the value as always hexidecimal while simple menu treats it as decimal unless a 0x prefix is present. > com32/elflink/ldlinux/readconfi...

I'm using ipappend and getargs.com with a dos boot image to get the environment variables for the IP and MAC. The format of the %ip% environment variable is ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> Is there a way to tell ipappend to assign these to individual arguments. Or does anyo...

Hello Using pxelinux for so long time i don't want to use pxegrub to PXE boot solaris 10 on x86 . So i would like to use pxelinux to do this jobs . I use ipappend and mboot.c32 however i don't success to have the kernel argument appended with BOOTIF : here is what i use : LABEL solaris MENU DEFAULT MENU LABEL Solaris Jumpstart KERNEL mboot.c32 APPEND multiboot kernel/unix -v -m verbose install http://mywebserver/jumpstart.tar -B install_...

.../2013 11:06 PM, Gerardo Exequiel Pozzi wrote: > On 06/13/2013 10:15 PM, Gene Cumm wrote: >> On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi >> <vmlinuz386 at yahoo.com.ar> wrote: >>> Hello >>> >>> While testing PXE booting, I decided to change IPAPPEND to the new >>> SYSAPPEND and does not work: nothing is appended to command line. >>> >>> I tested using menu.c32 and vesamenu.c32, same issue. >>> >>> --------------------------------------------------------------------- >>> SERIAL 0 38400 >&...

Hello, I have not been able to get the IPAPPEND option to successfully set the ip parameters for a pxelinux install. I have LABEL install KERNEL pxelinux.cfg/tftpboot.img APPEND initrd=pxelinux.cfg/initrdfs.gz root=/dev/ram IPAPPEND 1 where tftpboot.img is either of http://ftp.debian.org/debian/dists/woody/main/disks...

On Wed, 26 Jun, at 12:02:46PM, Gene Cumm wrote: > The following changes since commit 4ff8fcac8e7b5046987dee15592ab510ab343aa8: > Matt Fleming (1): > Merge branch 'menu-ipappend-1-for-mfleming' of > git://github.com/geneC/syslinux into elflink > > are available in the git repository at: > > git://github.com/geneC/syslinux.git ipappend-fix-for-mfleming > > Gene Cumm (2): > core & menu: fix IPAPPEND/SYSAPPEND conversion > d...

...3, 2013 at 8:24 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 23, 2013 at 3:16 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> I guess the bug is here (com32/menu/readconfig.c) >> >> 910 } else if (looking_at(p, "ipappend") || looking_at(p, >> "sysappend")) { >> 911 if (ld.label) >> 912 ld.ipappend = atoi(skipspace(p + 8)); >> 913 else >> 914 ipappend = atoi(skipspace(p + 8)); >> >> since...

FYI -------- Original Message -------- Subject: IPAPPEND on http://syslinux.zytor.com/faq.php#config Date: Mon, 31 Jan 2005 15:20:00 +0100 From: Pascal Terjan <pterjan at mandrakesoft.com> Organization: Mandrakesoft To: david at weekly.org Hi, I needed to get the MAC from which we booted using pxelinux (in order to know which interface we used to...

Hi all :) that's my first post, he =) I need some help about having the IPAPPEND 3 in my freedos (odin) environnement after a PXE boot using PXELinux / Memdisk... i've been searching for few hours now, but didn't found anything.. Is there a way to get that done ? Thanks in advance J?r?mie 'ahFeel' BORDIER

Another issue which looks like a bug. If 'ipappend' is set globally (not uncommon in network/pxelinux environment), the last entry for ifcpu64.c32 gets messed up -- to the 2nd (or 3rd) label all the chars from ipappend gets appended, without spaces, resulting in a messy label. Adding -- after the 3rd entry does not help -- the minuses too gets...