[syslinux] Syslinux 5 (i)pxelinux.0 unnecessary PATH requests

Arends, R.R. r.r.arends at hr.nl
Wed Dec 12 08:48:06 PST 2012


On 12 dec. 2012, at 17:33, "Shao Miller <sha0.miller at gmail.com>" <sha0.miller at gmail.com> wrote:

> On 12/12/2012 11:17, Shao Miller wrote:
>> On 12/12/2012 10:48, Arends, R.R. wrote:
>>> 
>>> good idea, but imho this still involves in making extra requests to
>>> the backend and rather 'hacky' chain->chain->chain stuff to make it
>>> harder to understand for my fellow cowokers.
>>> 
>>> if anyone can point me to the right source files to edit and hardcode
>>> the path, i would really appreciate it. i know thats also hacky, but
>>> thats easy to do since we already have some custom patches which we
>>> always apply.
>> 
>> As mentioned elsethread, you are overriding the path by using 210.  That
>> is to say, you are setting the current working directory.  The current
>> working directory is used for opening files with relative paths (in a
>> few different operating systems, even).  If you don't want to do this,
>> don't do it. :)
>> 
> 
> For example, there is no reason for you to set 210 since you can 
> hard-code the iPXE script, which you are already doing:
> 
>   #!ipxe
>   #...
>   # Do not set 210
>   set filename http://boot.xxx.nl/mods/pxelinux.0
>   chain ${filename}
> 
> Then ldlinux.c32 is searched-for where pxelinux.0 lives.
> 
> - Shao Miller

That might work, will try what it does without setting option 210 and check the webservers logs.

Will report back next week.

- reni




More information about the Syslinux mailing list