Hi,
Update:
Now pxe fs exports PXE_MAC and PXE_IP on startup.
pxecfg can support multiple files, and the syntax is changed a bit:
ip {
192 {
168.2 {
command = "echo ip 192.168.2.*"
}
169 {
command = "echo ip 192.169.*.*"
}
command = "echo ip 192.*.*.*
Forwarding Pavel Pisa's e-mail to the subscribers only list.
On Friday 16 October 2009 13:57:47 Vladimir 'phcoder' Serbinenko wrote:
Aleš Kapica wrote:
> Dear friends,
Hello Vladimir and other GRUB2 developers,
I am replying to your review as one of the patch authors.
> Nobody can't use opt
Hi,
On Sat, Oct 17, 2009 at 4:42 AM, Pavel Pisa wrote:
> As for scalability, I agree, that use of single config file with checking
> for each IP is horrible hack, but there is no problem to source
> to another IP specific file (menu-xxx.xxx.xxx.xxx.lst) with separate
> menu configuration when own
Hi Michal,
sorry to contact you dircetly, but did you upload a binary somewhere? I
accidentially deleted to many emails, so I wasn't sure anymore if you
already posted a link...
kind regards,
Stefan
Michal Suchanek wrote:
> 2009/10/9 Stefan Bienert :
>> Hi again,
>>
>> thanks for that hint. I w
Hi,
Solaris has adopted the following search path for configuration files:
(1) DHCP Option 150
(2) menu.lst.01 (i.e. menu.lst.01)
(3) menu.lst. (where BootFile is the DHCP server-specified BootFile
option)
(4) menu.lst
This has served use and our customers very well and
Brendan Trotter wrote:
> Hi,
>
> On Sat, Oct 17, 2009 at 4:42 AM, Pavel Pisa wrote:
>
>> As for scalability, I agree, that use of single config file with checking
>> for each IP is horrible hack, but there is no problem to source
>> to another IP specific file (menu-xxx.xxx.xxx.xxx.lst) with se
On Tue, Oct 20, 2009 at 4:04 AM, Stefan Bienert
wrote:
> Hi Michal,
>
> sorry to contact you dircetly, but did you upload a binary somewhere? I
> accidentially deleted to many emails, so I wasn't sure anymore if you
> already posted a link...
Hi,
I have compiled a binary version and uploaded at
