[dead2sin]

Congratulations on the new job. I definitely understand your decision and I hope that the new job is a dream for you.

I’ve been using InstaDMG for only about a year and a half but boy has it matured in that time frame. I’m really excited to see what you can get done before you have to call it quits and I do hope that someone will step up to the plate in order to keep InstaDMG going.

Thank you for all the word you’ve put in to InstaDMG, it really has made it the amazing tool that it is.

Nate

[dead2sin]

Honestly, if you have OD set up and you are binding them to OD, I would only set that type of thing via MCX. I could see wanting to make sure it is set on the image, but one of the main reasons to use OD is for the MCX functionality. If it was always set on your test box via MCX, it should be fair to say that it would be set when you deploy as well.

Nate

[dead2sin]

Postflight runs when the package itself is installed on to the image during the InstaDMG process. Adding all that to the firstboot.sh will definitely work (I did it that way for the longest time), but I think doing it in a postflight is the best practice (If it can be modified at image creation time, it should be, else it should be modified upon first boot).

I’m not familiar with using legacy VNC settings, so I am not of much help there. I can confirm the kickstart command on osxdeployment works perfectly, but anything beyond that I’d have to test.

Nate

[dead2sin]

I used the mdfind command and came up empty. Where are these files normally stored? Within the Word.app itself or elsewhere?

Nate

[dead2sin]

I’ve never messed with preference manifests before, but I’ll check it out Tomorrow.

Nate

[dead2sin]

I bought a Retail 10.6.3 OS X Snow Leopard disc at Best Buy and it shows as Build 10D575. It *should* be a standard build, so I thought I’d mention it.

Also, how do InstallerChoices.xml files work with the new setup? You put the build # in vanilla and it will use that build installer disc, but how do I specify InstallerChoices? Leave it in the BaseOS Folder or put it elsewhere?

Thanks,

Nate

[dead2sin]

So for each and every catalog, you can have a list of built numbers they apply to and it will only install that catalog of the build numbers match? Sounds nifty. I’ll have to explore this idea a little more so I fully understand it (and perhaps fuss with it a bit).

Also, to be clear, are you saying that a completely fresh 10.6 Vanilla catalog could be manually created for each special-case Model (Mac Mini, iMac, etc)?

I’ll modify the tutorial I wrote to discard the –legacy command so that the new build functionality can be used.

Nate

[dead2sin]

Larkost brings up a good point. I’d boot it up and see which updates it asks for and modify the 10.6_vanilla catalog specific to that model accordingly. I’ve installed all the same updates that 10.6_vanilla uses without issue (other then the point release that is model specific) without issue, but it is safer to only install exactly what you need.

Nate

[dead2sin]

golbiga:

If that iMac doesn’t work with the 10.6.3 Retail disc + the 10.6.4 update, you will want to use the Grey Install DVD it came with along with the iMac-specific 10.6.4 update from Apple’s website. The image you build with this would need to be completely seperate from your main workflow and used ONLY on that model iMac. I had to do this for the Mac Mini and basically made copies of my 10.6_vanilla catalog file and pointed it to the grey installed disc image and special 10.6.4 update. Then I reused all my other catalog files so it spit out a virtuall identical image to my main image, but it was for the Mac Mini only.

The goal is to make sure that you only ever use the Reference build retail discs (10.6.0 and 10.6.3 at the moment) for image that are installed on every model. When a specialized build of OS X comes out and specialized point releases, it is necessary to keep them separate and make sure they don’t get put on a model they were not meant for.

Does that clear it up?

Nate

[dead2sin]

Sounds great! Can’t wait to hear what you have to announce. I am unable to go to any of the conferences this year, so hopefully I’ll heard about it on afp548 🙂

Nate

[dead2sin]

I understand what he is doing with Reference builds, I was just curious where it was getting that info from. I am using a Reference build, yet it failed on it me (hence commenting out that line). I wanted to make sure my Mac OS X Install DVD.dmg was ripped in a way that would play nicely with InstaDMG without having to comment out that build line.

As far as the firstboot package goes, I think it would be feasible to make a very generic one that people could use, but we’d have to agree upon what format we want it to be in (pmdoc, iceberg project, etc). I think pmdoc makes the most sense though. I would be willing to go over the one I’ve made already and try to make one that would be acceptable for general use. (com.afp548.firstboot I think would be appropriate).

Nate

[dead2sin]

That is functionality of the SVN, but I’m not sure why it won’t let you just replace it. One thing you can try is moving the 10.6_vanilla.catalog to another folder and re-running it. SVN should see it is missing and just give you the latest version.

Nate

[dead2sin]

I noticed on one of the more recent SVNs you can specify which build numbers are valid. I had to comment that out to get my build working, is that because I didn’t import my disk using the importDisk.py script? If so, I’ll just re-import the disk using that script and everything should be peachy. I was curious how that piece of functionality worked (Where does it get the build # from, etc). I’m going to be rebuilding all the images our University uses, so I’ll update my current setup to the latest SVN before I do that and give feedback.

Thanks,

Nate

[dead2sin]

Two things to try:

1. int needs to be -int 1 as follows:

[code]$defaults write “${PREFS_DIR}/com.apple.alf” globalstate -int 1[/code]

Try wrapping the homepage for safari in quotes. I’m thinking the symbols might be confusing it (And if this fixes it, I’ll update the documentation on the wiki to reflect it).

[code]$defaults write “${USERPREFS_DIR}/com.apple.Safari” HomePage “http://website”%5B/code%5D

Nate

[dead2sin]

Could you remove any sensitive information from it and post it to pastebin or pastie and link it? I’d have to look over it to really see what is going on.

Nate

[Author]

Posts