- This topic has 2 replies, 2 voices, and was last updated 17 years, 1 month ago by
knowmad.
-
AuthorPosts
-
March 6, 2008 at 2:20 pm #371795
knowmad
ParticipantSo here I am working on the InstaDMG setup for my company and I run a basic test:
Put 10.4 retail DVD into the BaseOS folder, put the basic instauser script in place, kick it off.
It runs but refuses to quit/finnish.
So I figure there are some items in the script that need to be changed or specifically stated.
I start reading the script.
Item 1) my scripting skills are woefully underused and underdeveloped
Item 2) I cannot tell how up to date the comments are.Several of the comments say “this will be automated in future releases” or something to that effect, and I am nearly certain some of those items are already automatic.
One comment/code line in particular has me very confused:
[code]# ASR target volume. Make sure you set it to the correct thing! In a future release this, and most variables, will be a getopts parameter.
ASR_TARGET_VOLUME=/Volumes/foo
[/code]It says to set it to the correct value….. I thought the target was going to be the disk image that the script is creating so that should really be a static or nearly static value….
(now for the super simple question that I am only asking because I would rather look stupid and get an answer than be stupid without one)
What am I supposed to set that line to? Am I supposed to change the caps section to the name of the target volume (that makes no sense) or the part that says foo (is foo some sort of universal place holder i am unaware of?)?I am certain people are rolling their eyes at me, but I am genuinely confused by this……
March 6, 2008 at 2:33 pm #371796akinspe
ParticipantThis target refers to the Volume you wish to restore your freshly cooked ASR image to. This is completely optional and is actually commented out if you use an unaltered version of the script. Basically this would allow you to start the instadmg process, go to sleep (or whatever), and wake up with not only a made ASR image, but a volume that you can immediately test on. In fact, there are also methods to bless the volume (thus making it the startup disk) and rebooting so you return to the new volume all ready to go.
Very astutely, the authors made all of these discrete functions so they can be easily commented out to suit your particular need. As the comment for this item mentioned, soon we’ll have getopts parameters so you could use switches like “-t /Volumes/foo”, etc instead of having to alter the script source
March 6, 2008 at 3:53 pm #371797knowmad
Participantakinspe –
thank you… oddly ia m working with an unaltered copy of the script so ia m uncertain as to why it is NOT commented out…. had it been commented out I would like to think I would be smart enough to understand it… ok, I asked the question and got the answer, learned something. Thank you a ton for the quick answerEDIT: so after reading the WHOLE script I realized it is commented out, i just didn’t read far enough. Upon finishing the read through, I find the whole script easier to understand, I know why mine did not complete (could not eject…. I think something else might have been trying to access that image) and I understand better where and how to change things.
Thanks again for the help. -
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed