We image multiple servers using customized jumpstart and FLAR's. Here's a brief overview of what we do: - create appropriate jumpstart scripts based on HW - boot net - install - after reboot -- perform custom SVM - (step A) -- run site specific config. script1 only if (A) was successful - (step B) -- run site specific config. script2 only if (B) was successful - (step C)
i.e. run the subsequent scripts only if the current script has run successfully. Looks like a perfect job for SMF, right but wait there's more ;-) We perform SVM setup and site specific configuration using scripts in /etc/rc2.d because it's a pain to convert all of our scripts (we do have a lot) into SMF. Note: - I understand that Solaris install can do rudimentary SVM but that's not good enough for us (no custom metadevice naming convention). - We have implemented the above dependencies in pre Solaris 10 using run level scripts and exited when there was a fatal failure by doing a "exec ksh -o vi" which took us to a console prompt where we could debug the issue In Solaris 10 FCS and SMF world, we have kludged our run level scripts by doing the following: - sourced /lib/svc/share/smf_include.sh so that we can write to the console using "echo msg | smf_console" - since S99dtlogin is not a SMF service yet, we could exit to the console prompt using "exec /bin/ksh -o vi </dev/console >/dev/console 2>&1" One of the problems we face now is that when we exit it to the console prompt during a fatal error, it seems to be unfriendly for debugging i.e. can't use vi for long (maybe it has some buffer) and the "console login message" appears constantly. In future releases of Solaris 10, dtlogin maybe a service which means that my fatal exits in my rc2.d scripts would not work? What are my options to implement my custom scripts? TIA -- prasad This message posted from opensolaris.org
