Avoid loading client config file

[Chris Nelson_1]

What is the difference between the config and the config.full files in the clients directory? Which of these attempts to load during the process?

And now the big question -- can a prevent it? I have a system here that uses Ignite to assist in installation of machines but the problem is the old setting in the client file are replacing out custom settings in INSTALLFS. Assuming I have limited read-only access to the Ignite server, is there anyway to tell Ignite NOT to load the client-specific file or alternatively can I wipe it out across the NFS mount created by the client before it is loaded?

[Steven E. Protter]

You need to have some restructuring done by the Ignite admin on the server.

Reason: It would appear that the image you are loading has more information than you need.

What you need is to load a more base image and customize what loads after the base image.

What you could do, is boot off the Ignite server, which must be using the client machines built in lan card.

Then you can interupt the Ignite process when prompted. This will get you an installation interface that looks like the HP-UX Install screen.

In that interface you can customize almost anything, logical volume layout, and even blow off client specific steps.

I've got some experience doing these things, as I'm an Ignite server admin.

SEP

[Chris Nelson_1]

I guess I didn't explain my needs clearly enough. You didn't tell me what the difference is between config and config.full. Obviously the .full contains more info than config but I was curious WHICH of these files is automatically added to the configuration?

I failed to mention that this system is fully automated so interaction with a UI is not an option. The goal was to supply Ignite with enough data to allow a non-interactive installation and bypass all need to ever interact with the HPUX install interface. The way I did it is to put all the required information in the INSTALLFS file. I realize this may not by the way Ignite was intended to be used but it was the most effecient solution and allows interaction with any Ignite server without the need for root access. It also allows much more flexibility and control than bootsys would provide. At the time I didn't realize that the config/config.full file stacks on top of INSTALLFS. I assumed this file was only used to do repeat installations and that INSTALLFS had the final word on settings.

I have figured out a work-around for this--simply delecting the config and config.full to prevent them from changing settings behind the scenes. This is not a very elegant solution and so I was hoping there was some way to just tell Ignite NOT to load these files. To me it seems that you can do that in the UI. When it prompts "Do you wish to load previous settings?" you can answer 'no' and it seems like all data in config/config.full is ignored. Therefore it would be nice if a non-interactive installation had the same option. So far I have not found such an option.