You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the luna installer doesn't expose a lot of variables which can be used in the part script. However some variables are only filled in after the installer starts or not exported at all but they are known upfront.
For example LUNA_IMAGEFILE is filled in after the part script but when the node boots it is known, just not exported.
Could you make them available, e.g. in templ_nodeboot.cfg, so they can be picked up by the installer via /proc/cmdline:
not everything is available at the various stages in an attempt to be more optimized (overhead reduction). It would be helpful to have a list of variables to have so we can work towards it instead of trying to provide everything. I leave this one up to you.
By default, the luna installer doesn't expose a lot of variables which can be used in the part script. However some variables are only filled in after the installer starts or not exported at all but they are known upfront.
For example LUNA_IMAGEFILE is filled in after the part script but when the node boots it is known, just not exported.
Could you make them available, e.g. in
templ_nodeboot.cfg
, so they can be picked up by the installer via /proc/cmdline:Result should be something like
Or as export in the installer
templ_install.cfg
:There may be more which can be useful during boot:
The text was updated successfully, but these errors were encountered: