hi,
Maybe this is not a perfect solution.
There is no domain network it was very interesting and very convenient.
You can add this functionality, plus a reminder to use the domain network users
do not use this function.
In the future there is a better scheme and then modify it.
在2010-03-21 09:53:49，"Michael Brown" <[email protected]> 写道：
>On Saturday 20 March 2010 23:21:24 Shao Miller wrote:
>> > ...However, I think it
>> > would be useful if sanbootconf could store the hostname *somewhere* in
>> > the registry; this would allow a user who wants auto-renaming machines to
>> > implement it without requiring specific knowledge of the iBFT.
>>
>> Agreed. A good place might be in sanbootconf's registry key,
>> Parameters\ subkey.
>
>From everything else you said, I think I'm decided that changing the actual
>hostname is a Bad Idea. The question is just then where to store the
>hostname so that other software could use it.
>
>One option is to store it under
>
> CCS\Services\sanbootconf\Parameters\iBFT\NIC\0\hostname
>
>i.e. store all of the parameters from the iBFT (or sBFT, or whatever firmware
>boot table we're using) in registry entries corresponding to the table
>structure. This has the advantage that it exposes all of the firmware boot
>table information, without requiring a user to parse the raw table. The
>disadvantage is that the user needs to be specifically aware of sanbootconf.
>
>Another option is to find a suitable generic registry entry to hold the
>DHCP-assigned hostname. This would have the advantage that the user does not
>need to be specifically aware of sanbootconf. Unfortunately, I don't know of
>any such registry entry.
>
>Michael
>_______________________________________________
>gPXE mailing list
>[email protected]
>http://etherboot.org/mailman/listinfo/gpxe
_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
