Ignite-UX post installation scripts

[David Burgess]

Hi,

I'm adding post install scripts to my Ignite configuration. I want to copy files from the ignite server to the client.

Do I have to nfs mount the directory and then reference the mount point in the cp command or can I copy the files by referencing the the server and filesystem.

To clarify

cp -p /mountpoint/myscript /etc/

or

cp -p iguxsvr:/var/opt/ignite/scripts /etc/

I noticed that tftp has to have access to the directory via a mention in /etc/inetd.conf. It has /var/opt/ignite mentioned.

Should the script that contains the cp command be executable? What permissions and owner:group do I need?

Regards,

Dave.

[Steven E. Protter]

I have done lvm comands in my post configuration scripts.

The execuables were there without needed to do full path reference and the mirros looked right.

So as far as the cp command I think you are okay.

Can't help with the nfs mount part. I would test if possible because though the intial tftp boot and kernel transfer works, I'm not sure if nfs is active when you get to post configuration stage.

I just looked at a log and there does not seem to be a boot, so NFS might be available.

SEP

[Scot Bean · Accepted solution]

Basic networking is enabled during the "post_config_script" phase. We use scripts at this time to "rcp" standard config files over that we need.

We "rcp" files from any server with the proper .rhost permissions. Does not have to be the ignite server.

Recommend not relying on some NFS link that Ignite may or may not provide for you.

[David Burgess]

Thanks, got it working using rcp to copy over a directory containing the files and then did the updates from there.

I can add a user, but can't set a password. I guess this is secure. Is there a way to add a password without having it plain text in the finish script?

Regards,

Dave.