- This topic has 8 replies, 3 voices, and was last updated 14 years, 10 months ago by
Allister Banks.
-
AuthorPosts
-
June 7, 2010 at 8:37 pm #378707snkParticipant
What’s the purpose of each? Going through the quickstart guide, the instadmg bash script isn’t even used, so I’m a bit confused on this note.
Are packages that I put in the CustomPKG folder installed when I run InstaUp2Date? Or do I need to run the instadmg bash script to get those to install?
I’d like to try most of this stuff before asking here, but I’m confused enough where I don’t think I can do that. (e.g. tried restoring a “vanilla” image created by InstaUp2Date, which resulted in a non-booting machine).
Any help is appreciated. 🙂
June 7, 2010 at 9:46 pm #378708Allister BanksParticipantThe difference between the two is: InstaUp2Date is a bit more finicky, but in the end requires less work and can enable more flexibility. It runs instadmg FOR you when you call it with the –process flag, it can’t make the image without it.
As a beginner, just making the folder structure described and calling instadmg.bash manually is the easiest way to wrap your head around what’s going on IMHO. The quick start is very useful, however, because you notice the cache file, and it gives you a very generic, updated image.
I have noticed that the Corei5/i7 MBP’s don’t boot from a vanilla10.6.3, so that may be waiting on 10.6.4 to be the same image as the rest of your environment. Let us know what model you were trying to image, I couldn’t even boot it with deploystudio until I built the netboot set on that model.Allister
June 9, 2010 at 6:12 pm #378711kwilsonParticipantHI there, I too am confused. I used the quickstart to create the vanilla 10.6.3 installer with updates, but as noted the restore wouldn’t boot. I cannot run the instadmg.bash, I keep getting “command not found”. I have put a couple of packages in the custom folder, but not sure how to run anything. If I use the lines from the quickstart, I end up with the same thing, not the additional packages.
thanks for the help.Instadmg 1.5 (Ithink)
Snow 10.6.3 on an iMac
site licences for snow, iwork09 and ilife 09June 9, 2010 at 6:51 pm #378712Allister BanksParticipantHey there,
If I can make the documentation clearer I will, but I think you just want your problem fixed/the tool working first. Feel free to explain your steps further here, but you can email me too(in my profile). There’s also an email address in the documentation if that’s easier.
Allister
June 9, 2010 at 6:56 pm #378714snkParticipantThought I had replied before, but it’s no longer here for some reason….
Anywho, thanks for clarifying Allister. I’ve created images now with both instaUp2Date as well as just plain instadmg, and I’ve got both producing booting images. My current scenario is creating images on a Macbook with instadmg, and deploying to an external hard drive. Things seem to be running smoothly (Patched 10.6.3).
June 9, 2010 at 8:54 pm #378715kwilsonParticipantThanks Alastair
I went back to the original quickstart, downloaded the version from the website and had it installed again. Then I started with the instaup2date step using my previously created snow dmg, it did indeed check to see if the updates were installed, but then exited with this message:
13:47:45 ###### InstaDMG build initiated ######
InstaDMG version 1.6b2 (svn revision: 300)
Host OS: Mac OS X 10.6.3
Host Hardware: iMac9,1
Output file name: 10.6.3 Vanilla
Output disk name: Macintosh HD
13:47:46 ###### Finding main MacOS X installer disk ######
###### Unable to find primary installer disk ######
13:47:46 ###### Cleaning up ######
Restoring normal installd daemon
Ejecting images
and did not build any new dmg files. At this point I have the Max OSX dmg in BaseOS, the createuser pkg in the CustomPKG folder and iWork 09 in the InstallerDiscs folder.
what am I doing wrong?
KeithJune 9, 2010 at 10:01 pm #378716Allister BanksParticipantHey there,
Please verify that your OSX image is named “Mac OS X Install DVD.dmg”, and iWork09 would not go in the InstallerDIscs folder. There is a flag you can pass ./importDisk.py for the ‘legacy’ naming convention so instadmg can find it, just checking. Additionally, iWork09 would be in a numbered folder in CustomPKGs if you’re calling instadmg manually, or InstaUp2DatePackages if called via instaup2date.py with the –process flag. Once AFP548 gets the downloads back online(I heard they were offline during the DR recently) please check out my fixer payload-free pkg(you may want to customize it as well) to make the iWork install behave.
Let us know as you get closer to the goal state,Allister
June 11, 2010 at 8:51 pm #378737snkParticipant[QUOTE][u]Quote by: Allister[/u][p]Hey there,
Additionally, iWork09 would be in a numbered folder in CustomPKGs if you’re calling instadmg manually, or InstaUp2DatePackages if called via instaup2date.py with the –process flag.
Allister[/p][/QUOTE]Hi Allister,
Could you clarify a bit here? Running instadmg.bash, my custom packages need to be in CustomPKG in 01, 02 , 03, etc subfolders in the order I want them installed. If I’m running instaUp2Date.py with –process, my custom packages need to be in InstaUp2DatePackages –> with or without the numbered subfolders in order to be installed?
June 12, 2010 at 4:29 pm #378740Allister BanksParticipantHey snk,
Without numbered folders for custom packages called by instaUp2Date, the order specified in the catalog file is what determines installation. I don’t think it’d be able to find the package inside a numbered folder unless you specified the full path in the catalog entry for it. Specifying the full path means you can relocate your instaUp2Date-included packages to other locally-mounted volumes, but instaUp2Date’s reliability at using the package becomes intermittent unless it’s in our two designated locations(/InstallerFiles/InstaUp2DatePackages or /Caches/instaUp2DateCache) which I’ve especially found to be the case with larger .mpkg’s.
More questions please! I know the subject can seem opaque until you do some trial and error, and the more things I can incorporate into the docs the better it’ll be for future admins.Allister
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed