[dead2sin]

That looks right. How about the script itself? Just clean up any sensitive info first 🙂

Nate

[dead2sin]

The best way to accomplish this is to use a installer choices file along with the iLife installer. This allows you to select which items get installed and which don’t…basically it simulates mouse clicks on the various install options.

You can get a list of the item names by running this command:

[code]installer -showChoicesXML -pkg [/code]

It will output all the InstallerChoices, you just need to dig through and find the proper name and put it in installerchoices just like you would for an OS X install. I know there is better documentation on this out there, I just cannot find it at the moment 🙁

Nate

[dead2sin]

Post your launchd item and your script and I’ll take a gander.

Nate

[dead2sin]

I’ll have to double check, but I just build an image this morning and tested it, everything in the firstboot seemed to run just fine.

Does the firstboot.sh script exist if you just mount the image and go to /Library/LaunchDaemons/ ?

Are any of the settings actually set that are present in the firstboot.sh script?

Nate

[dead2sin]

I will note iLife 09 can be installed using InstaDMG as is, fully updated, using the iLife09.catalog. For images that always have iLife09, I do it that way and it works well.

I use a repacked version of iLife 08 and 09 for my main faculty staff image, the correct version gets installed at image time via DepoyStudio.

Nate

[dead2sin]

importDisk.py has always worked for me using the default version of Python that comes with OS X. I’d try it on a fresh machine and see if it works.

Also as a side note, –legacy should no longer be used due to how InstaUp2Date functions. Just do –automatic now. (This is true if you got the latest SVN or even from the SVN in the past few months).

Let me know how it goes.

Nate

[dead2sin]

1. Yes, #!/bin/bash at the beginning of the script is desired. It indicates what type of script it is. This is common across all bash scripts.
2. Permissions are in step 6 towards the very end of the guide. Some others have run into this problem so I corrected the guide about a week ago with this info as follows:
[quote]Check the permissions on each item. Click each item on the left and select the contents section. The launchd item MUST be set to owner: root and group: wheel, permissions set to 644. If they are not set to this, the launchditem will never load the firstboot script. There are some issues with this and PackageMaker, so be 100% the permissions are set correctly and being applied correctly
[/quote]

3. If the firstboot script runs, it will apply settings and then delete itself. If it isn’t deleted, the the permissions are most likely wrong and it never ran. If it is not present and the settings are not set, I’d check InstaDMG logs to confirm it was installed correctly (Or you can mount the image that was created and check for the presence of the script, this is probably the easiest way to go about it).

If you still have issues, feel free to post the script here to have people look over it or hop on ##osx-server on irc.freenode.net. There are always people around that are willing to help 🙂

Nate

[dead2sin]

If you install iLife using InstaDMG, it requires you to reinstall 9.0.4 support (due to how iLife installs).

Basically, vanilla contains the 9.0.4 support update, but if you install iLife further down the build train, it wipes it out. The easiest solution is to add the 9.0.4 update as the last item on your iLife09.catalog file and it *should* resolve the issue.

I just build an image today with no iLife on it and I included the 9.0.4 update, it works perfectly so long as you don’t install iLife on it. Once you do, you *must* reinstall it after iLife is installed.

Nate

[dead2sin]

[QUOTE][u]Quote by: tristan_mason[/u][p]I can’t get anything to work at the minute. Something is not working when ejecting the temp files. Am just starting fresh with a new setup. The catalog passes but didn’t work when i went to process it but then nothing is so i’m not sure where the issue is.

Cheers

Tris[/p][/QUOTE]

Reboot. I sometimes have issues with not being able to eject anything in the GUI and a reboot always fixes it. Perhaps your build machine is having other issues if a reboot doesn’t fix it?

Nate

[dead2sin]

[QUOTE][u]Quote by: tristan_mason[/u][p]Hi All

I’ve been using a scratch disc set-up as outlined in the instadmg guide on osxdeployment.com and it seems to make a small difference in time to the whole processing. Is anyone else using a scratch disc and if so do you have any tips?

Regards

Tristan[/p][/QUOTE]

I used a scratch disk. I have 2 sets of raid 0 setup, one is the system drive and the second is used as a scratch drive. It has speed up my image builds going between two Raid 0 arrays.

Nate

[dead2sin]

Just a heads up, I edited this file after researching which updated were actually necessary. Don’t hate me, but you might want to run another build 🙂

Nate

[dead2sin]

No problem. There should be an updated 10.6_vanilla catalog hitting the SVN in the next day or so. This will make all our lives a bit easier 🙂

Nate

[dead2sin]

10.6.5 worked perfectly for me using InsatDMG. Make sure you have the Combo update and make sure you have the hash in there as well (provided on that page as well). Easiest way to update the 10.6_vanilla catalog is to right click and copy download link on the Combo Update page, paste that in over the 10.6.4 link, paste the new hash on from that page as well and then update the description.

You *will* need to test which updates are necessary and which are not.

I’d love to post a 10.6_vanilla catalog for you, but the forum keeps telling me it is spam, so I cannot give you any better info. I’ll try to add a dropbox link if the forum will allow me to.

Good luck!

Nate

*edit* Here is an updated catalog file that Martin Neumann came up with on the instadmg mailing list. It looks to be pretty accurate:
[url]http://dl.dropbox.com/u/11466/10.6_vanilla.catalog[/url]

[dead2sin]

[QUOTE][u]Quote by: tristan_mason[/u][p]Hi All

It seems as though instadmg only likes system updates when they come from apple. If I download say the 10.6.4 Combo Updater, check sum it and pop it in a workflow it errors but if it downloads from apple as per the example catalogs then there is no trouble. I’ve been putting it in the BaseUpdates folder and have tried the InstallerDiscs folder too but both fail. Anyone else have the same issues or am I doing something wrong? Do I need to flush the cache files perhaps?

Regards

Tristan [/p][/QUOTE]

Don’t manually place files into BaseUpdates. That is another working folder for InstaDMG. The only place you should ever place files manually is InstaUp2DatePackages and possibly InstallerDiscs. If you specify a link to a website, it’ll place it in caches automatically. Leave BaseOS, BaseUpdates and CustomPKG alone. Basically, just follow what the InstaUp2Date guide has outlined and you should be ok.

Nate

[dead2sin]

[QUOTE][u]Quote by: bw38[/u][p]Is this like the droplet for Office 2011 where one has to drop the Office Installer on it and it will do the rest?[/p][/QUOTE]

Correct. Just drop your update .mpkg on it and it patches it to work with InstaDMG

Nate

[Author]

Posts