Re: [Etherboot-discuss] set identifiers
Brought to you by:
marty_connor,
stefanhajnoczi
From: Michael B. <mb...@fe...> - 2009-05-31 06:48:54
|
On Thursday 28 May 2009 22:51:53 Luca wrote: > Would it be possible to add a new identifier, which could be set only via > script or shell but not via DHCP? > > I have tried creating a new > > struct setting _new_identifier_ __setting = { > .name="new-identifier", > .description="New identifier description", > .type=&setting_type_string, > .tag=DHCP_EB_NEW_IDENTIFIER, > } > > and the > struct setting_applicator new_identifier_applicator __setting_applicator = > { .apply=my_new_identifier_apply; > } > > This way I can set/show the new_identifier. My understanding (but I might > be wrong) is that having the .tag, the new_identifier might be set also > via dhcp, which is something I don't want to happen. Is there a way to have > an identifier set only via script or shell? If you omit the .tag altogether, then you will end up with what you want to achieve, I think. Note that as of a few days ago, gPXE supports arbitrary identifier names anyway. If you are planning to access this variable only from within the shell (i.e. if you *don't* have an applicator), then you don't need to add any extra gPXE code at all, you can just do set new-identifier some-value .... .... echo ${new-identifier} Michael |