I found my issues were resolved via instructions, from, information, via the url:
Preconfiguring With the sysidcfg File (Solaris 10 8/07 Installation Guide: Network-Based Installations) - Sun Microsystems
Also, sysidcfg, rules etc, ought be in the correct place. The documents that were not bad, are available via the url:
2.Custom JumpStart (Overview) (Solaris 10 5/08 Installation Guide: Custom JumpStart and Advanced Installations) - Sun Microsystems
My issues turned out to be, among others:
1)having more than one dhcp server ( was installing so that the client when configured, get's it IP via dhcp), so that, when the client get's loaded with Solaris, and boots up, it is a dhcp client, unfortunately having two dhcp servers messed things somewhat.
3)Improperly named sysidcfg file.
2)Incomplete sysidcfg file. Despite the keyboard, being, perhaps, self-identifying, I went ahead and added values for it (US_English)
3)Not using the complete command(not sure about this), but stuff worked when, I, did, add_install_client with the -c <path>-s <path> -p <path> -e <mac address><hostname> <arch>
paths may be dsame or different. man add_install_client helped.
4)Searching on the internet, kinda showed some places where others's installs were failing, so I, simply completed the sysidcfg file....for instance I put in nfs4 dynamic.....stuff worked
I am not able to understand the "optional" requirement of teh sysidcfg file, it seems that for "hands off" installs, the sysidcfg file is a MUST.
I wonder how different sysidcfg files (different ones per server), may be created, I guess, one may have to, for more than one install client(each with unique sysidcfg requirements), have to, specify the path of the sysidcfg file(and keep it in different locations on the server), via, the -p option. In all this, I, may be incorrect. Maybe I missed something.
