summaryrefslogtreecommitdiffstats
path: root/answerfiles
Commit message (Collapse)AuthorAgeFilesLines
* Do not activate copySimo Sorce2012-09-111-3/+3
|
* use $SUDOCMD to run vm commands - add user SetupComplete as last stepRich Megginson2012-08-201-0/+3
| | | | | | | | | | | | | | One of the problems with make-ad-vm.sh is that there was no way to know when it was complete. setupscript99.cmd will create an AD user called SetupComplete as the very last step. When this user is present, the setup process is finished. The make-ad-vm.sh script will delete this user entry. Some of the virsh and vm commands can only be run by root. These commands are now prefixed with $SUDOCMD. If you are running the script as a non-root user, and you have sudo setup to allow that user to run the commands, you can use SUDOCMD=sudo ..othervars.. make-ad-vm.sh .... Otherwise, if you are running as root, just leave SUDOCMD blank.
* use cdrom instead of floppyRich Megginson2012-07-259-28/+51
| | | | | | | first pass at passsync installer split out AD installer from postinstall fixes for nextscript parameterize SETUP_PATH in all cmd files
* Parameterized install - added READMERich Megginson2012-07-2010-0/+1559