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
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
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
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
Quoting Vladimir 'phcoder' Serbinenko, who wrote the following on Fri, 16...:
Seth Goldberg wrote:
Hi,
Quoting Pavel Pisa, who wrote the following on Fri, 16 Oct 2009:
Nobody can't use options 150 from DHCP, because GRUB2 don't have any
driver for network adapters. Network task are done on
Seth Goldberg wrote:
> Hi,
>
> Quoting Pavel Pisa, who wrote the following on Fri, 16 Oct 2009:
>
Nobody can't use options 150 from DHCP, because GRUB2 don't have any
driver for network adapters. Network task are done only through
adapters PXE firmware. PXE passes informations only a
Hi,
Quoting Pavel Pisa, who wrote the following on Fri, 16 Oct 2009:
Nobody can't use options 150 from DHCP, because GRUB2 don't have any
driver for network adapters. Network task are done only through
adapters PXE firmware. PXE passes informations only about IP
addresses, but no DHCP options.
Aleš Kapica wrote:
> Dear friends,
>
> You have missunderstood my previous post from Thu, 15 Oct 2009
> 08:52:01 +0200 when I post patch, which fixies problem with
> identification of the booting machine in network by IP address.
> The following discussion have nothing to do with my post. I want to
