Displaying 20 results from an estimated 1000 matches similar to: "ipappend in pxelinux"
2002 Jan 16
1
help with syslinux config
I'm feeling really stupid here.... I seem to be missing something about the
syslinux config file. I'm booting a workstation via pxelinux. Everything
is cool, life is great, but I seem to be missing something about the config
file. I have:
display menu.dpy
timeout 35000
default netboot
label netboot
kernel vmlinuz.nfs
append root=/dev/nfs nfsroot=10.1.1.4:/home/image/1
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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"))) {
uint32_t s = strtoul(skipspace(ep), NULL,
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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:
2013 Jun 24
0
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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
2013 Jun 23
0
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
On 06/13/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
2013 Jun 24
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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
2013 Jun 26
2
[PATCH][git] IPAPPEND: standardize and document
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/ &
2005 Oct 10
1
IPAPPEND option?
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-server-ip:gw-ip:netmask
... based on the input from the DHCP/BOOTP or PXE
boot
2013 Jun 26
0
[PATCH][git] IPAPPEND: standardize and document
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
2013 Jun 24
0
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
On Sun, Jun 23, 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
2009 Nov 25
2
IPAPPEND breaks menu module
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
2002 Jan 06
28
Gre Tunneling Problem
Hello everyone, I have a problem regarding gre tunneling, I have two linux box both of them has a private network and the linux A is connected to the internet via wireless radio and the other linux B is connected to the internet via lease line. Here is the setup of my two linux box
Linux A
eth0 = 203.189.x.1 (internet)
eth1 = 192.168.1.1 (going to hub private network)
Linux B
eth0 = 205.198.x.1
2009 Jun 16
0
ifcpu64 & ipappend
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 addedd to the command line.
For now I
2013 Jun 26
0
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
On Sun, 23 Jun, at 11:21:45PM, Gene Cumm wrote:
> Correction: simple menu always does decimal (as should be expected).
>
> >> com32/elflink/ldlinux/readconfig.c:
> >> } else if ((ep = looking_at(p, "ipappend")) ||
> >> (ep = looking_at(p, "sysappend"))) {
> >> uint32_t s = strtoul(skipspace(ep),
2009 Jul 24
3
Problem with PXE, menu, and ipappend
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 commenting out the "ipappend 2" line
2007 Nov 07
1
IPAPPEND rewrite kernel argument list question
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
2003 Apr 05
1
ipappend with pxelinux
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-i386/current/
idepci/tftpboot.img
2004 Jun 09
3
ipappend and dos
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 anyone know a good way to parse each of these to individual variables in dos.
What
2004 Aug 19
2
ipappend on command line
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
2005 Jan 31
3
[Fwd: IPAPPEND on http://syslinux.zytor.com/faq.php#config]
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 boot).
I found reading the source that