post_config_script

[Jun Zhang_4]

I'm making a custom install tape, will adding the line,
post_config_script += "/path/to/script"
to my core_cfg work?

Jun

[Mark Greene_1]

What are you using to drive the creation of the tape? (make_recovery, make_tape_recovery, make_net_recovery)

What environment will this run in? The "+=" syntax won't work in the posix shell or in ksh.

mark

[Jun Zhang_4]

Not many sysadmin have the need like I do, we have customers that are not network reachable.
Obviously the config file itself is not a shell script.


Jun

[doug hosking]

Mark, the question is in the context of Ignite-UX config files, which have their own scripting language, not tradtional shell script syntax. See 'man 4 instl_adm' (if installed) for the language definition.

I do something similar to the post_config_script line in one of my script-generated IUX config files and it works fine.

echo "post_config_cmd+=\"" >> $CONFIG
/usr/bin/cat $DIR/post_config_cmd >> $CONFIG
echo "\"" >> $CONFIG

(where post_config_cmd contains regular shell
syntax and $CONFIG is a new IUX config file I'm generating based on a number of variables that aren't important here)

My guess is that it would work, but most of my IUX knowledge is rather new, so don't quote me on it. I know the lines above work fine for me.

[Jun Zhang_4]

Added the post_config_script line to the core_cfg file, created the custom install tape, boot to tape, the scripts showed up in the Advanced area.
To answer my question, I need to choose Go! to see the result, but I'm waiting for such a box I can do so.
Thank you very much for the reply.

Jun